OTL to Project Costing bridge
ConceptadvancedThe boundary where transferred time becomes project cost, including allocations to cost segments and the closed-project failure mode.
Recall it
Which time card actions does Oracle recommend validating for Project Costing, and what problem does that catch?
Submit and save, so people working on time cards know immediately if they are saving time entries to closed projects. Project Costing is one of the three time consumers, and Oracle publishes no attribute-level mapping between time entries and Project Costing fields, so the cost side of the boundary is tenant-specific.
Memory hook: Submit and save, for closed projects. The cost mapping is tenant-specific.
Rests on OTL-ACTION-062, OTL-CONSUMER-050, OTL-CONSUMER-053.
Taught in
No published lesson teaches this concept yet.
Related
- Terminology glossary — what a term means, and what people get wrong when they use it