Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 12 · Project Costing: the Accounting Setup
What breaks
Lesson 130 of 198 · 3 min
"The accounting is wrong or missing." Check in this order. One. Is a transaction account definition associated with this ledger, effective on this date? Two. Does the definition cover this transaction account type? Three. Did every segment rule derive a value? Four. Is the input value present in the mapping set — or did it hit the default? Five. Was the flexfield deployed after the last change? Six. Does the derived combination exist, and is it enabled in the chart of accounts? Then eight cases. One. "Costs post to a default account." An unmapped input in a mapping set. Two. "No accounting was created at all." No ledger association — or the transaction account type is not covered. Three. "Accounting worked yesterday and not today." A new expenditure type added with no mapping. Lesson 5's runbook item, not built. Four. "The account combination is invalid." Cross-validation rules in the chart…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue, with a certificate on completion and a fourteen-day refund window.
In this module: Module 12 · Project Costing: the Accounting Setup
- 1The accounting problem
- 2The project costing details flexfield
- 3Cost collection and the additional segment
- 4Value sets for the flexfield
- 5Transaction account definitions explained
- 6Mapping sets
- 7Building a transaction account definition
- 8Associating the definition to a ledger
- 9Proving the accounting works
- 10What breaks
- 11Lab: a mapping a controller could sign