OTL to Payroll bridge
ConceptadvancedThe boundary where validated, calculated and transferred time becomes pay, and where the tenant-specific attribute mapping lives.
What people get wrong
The confusions are the difficulty. Each one is a belief that sounds right and is not.
- That Oracle documents the time-entry-to-payroll-element mapping. It does not publish that mapping.
Recall it
Name the products that consume transferred Time and Labor data, and say what Oracle publishes about the attribute mapping that turns time into pay.
Global Payroll, Project Costing, and the Project Execution Management offering of Project Portfolio Management. A time consumer set is where the consumer validation rules, approval periods and transfer rules for a group of people are configured. Oracle publishes no attribute-level mapping between time entries and Global Payroll or Project Costing fields, so any mapping taught is tenant-specific.
Memory hook: Pay, Cost, Staff. The field mapping is yours to define; Oracle deliberately does not publish it.
Rests on OTL-CONSUMER-050, OTL-CONSUMER-051, 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