Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 12 · Project Costing: the Accounting Setup
Lab: a mapping a controller could sign
Lesson 131 of 198 · 2 min
Ninety minutes, and the first deliverable is the one this module is really about. A written account mapping specification — expenditure type to account, organization to cost center — AS YOU WOULD PRESENT IT TO FINANCE FOR SIGNATURE. Not a configuration export. A document a controller reads and signs. Then the build. The costing details flexfield reviewed and deployed. One additional cost collection segment with a value set, justified. At least two mapping sets, each with a default. Account rules covering all segments. A transaction account definition covering raw cost and burden cost. The definition associated to the ledger. And the evidence: three transactions of different shapes, each with its account traced segment by segment to the rule that derived it, and a deliberately unmapped transaction showing the default account — then corrected. Two criteria worth reading twice. Every mapping set has a default that is REVIEWABLE, not a live…
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