Transaction account definitions explained

Four building blocks. Learn these before touching anything, because the build assumes all four. Account rule — how one segment of the account combination is derived. Mapping set — a lookup table translating a project attribute into an account value. Transaction account type — the kind of accounting event being derived — raw cost, burden cost, and so on. Transaction account definition — the package assembling rules for each account type. How a rule derives a value. A constant. A value from the transaction. Or a mapping set lookup. Segment by segment. The definition builds the combination piece by piece — and different segments can come from different sources. This is the part that confuses people: one account, three segments, three mechanisms. If you took the Financials course, this is structurally similar to AutoAccounting in Receivables. Same idea, different implementation. Naming the parallel turns an unfamiliar object into a familiar…

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