MSAMM
Back to course

Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 12 · Project Costing: the Accounting Setup

Building a transaction account definition

Lesson 127 of 198 · 15 min

Create account rules for each segment — one constant, one from a transaction attribute, one from a mapping set. Create a transaction account definition. Assign rules to the raw cost transaction account type, then to the burden cost account type — connecting to Module 11 — then the remaining account types in scope. Review the complete definition and show a preview of the derived account for a sample transaction. Build one account type completely before starting the next. Half-built definitions are hard to debug. COVER EVERY TRANSACTION ACCOUNT TYPE THE CLIENT WILL GENERATE. A missing one means those transactions have no accounting — failure case two, and it is silent. Name rules for what they do, not for the project they were built on.

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.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 12 · Project Costing: the Accounting Setup

  1. 1The accounting problem
  2. 2The project costing details flexfield
  3. 3Cost collection and the additional segment
  4. 4Value sets for the flexfield
  5. 5Transaction account definitions explained
  6. 6Mapping sets
  7. 7Building a transaction account definition
  8. 8Associating the definition to a ledger
  9. 9Proving the accounting works
  10. 10What breaks
  11. 11Lab: a mapping a controller could sign