Search Results trans_ass_costs

Overview

PAY_TRGL_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, with a VALID status as documented in ETRM for releases 12.1.1 and 12.2.2. The package name uses the TRGL mnemonic, which in Oracle Payroll denotes Transfer to General Ledger processing. Its business purpose is to move payroll costing results — the amounts accumulated against assignments, elements, and payment methods — into the General Ledger interface so that they can be posted to the accounting flexfield. This places PAY_TRGL_PKG within the payroll-to-GL transfer and costing architecture, alongside the payroll action, cost, and GL interface entities it touches.

The package is classified as API classification OTHER in the documented metadata. It is referenced by no other packages, and its dependency section shows only a reference to SYS.STANDARD, indicating a self-contained body that relies on the schema-level tables and synonyms of Oracle Payroll rather than on other PL/SQL packages. It exposes three documented program units, all concerned with transferring or deriving payroll cost distributions.

Key Procedures and Functions

The documented procedures and functions are as follows:

• TRANS_PAY_COSTS — Transfers payment-related payroll costs into the appropriate costing or GL interface structures. This is the core routine for moving payment cost data during the transfer to General Ledger process.
• TRANS_PAY_COSTS_MT — A multi-threaded or multi-organization variant of the payment cost transfer routine. The MT suffix conventionally denotes an entry point designed to process data across multiple threads or organizational contexts, allowing parallel or batched handling of payment cost transfers.
• TRANS_ASS_COSTS — Transfers assignment-level payroll costs. This routine handles the cost distributions calculated against assignments, feeding them into the costing and GL interface tables.

The ETRM metadata does not document parameter lists for these units, so no signatures are asserted here. Their names and the table dependencies collectively establish their role in the payroll costing and GL transfer flow.

Tables Accessed

The documented table references, resolved through APPS synonyms, describe a coherent costing and transfer model:

• Cost and payment data: PAY_COSTS, PAY_PAYMENT_COSTS, PAY_GL_INTERFACE, PAY_COSTS and PAY_PAYMENT_COSTS hold the calculated cost and payment cost distributions, while PAY_GL_INTERFACE receives the summarized amounts destined for General Ledger.
• Payroll and assignment context: PAY_PAYROLL_ACTIONS, PAY_ASSIGNMENT_ACTIONS, PAY_ALL_PAYROLLS_F, PAY_ASSIGNMENT_LINK_USAGES_F, and PAY_ORG_PAYMENT_METHODS_F supply the run, assignment, payroll, and payment method context required to select and stratify cost rows.
• Element and input value definitions: PAY_ELEMENT_TYPES_F, PAY_ELEMENT_LINKS_F, PAY_ELEMENT_ENTRIES_F, and PAY_INPUT_VALUES_F provide the element definitions, links, entries, and input values that determine how costs are classified and mapped.
• Processing controls: PAY_ACTION_CLASSIFICATIONS, PAY_ACTION_INTERLOCKS, and PAY_PAYROLL_GL_FLEX_MAPS define action classes, interlock handling for process sequencing, and the mappings that translate payroll costing to the GL accounting flexfield.

Usage Notes

PAY_TRGL_PKG is an internal Oracle Payroll component rather than a public API intended for direct customer invocation. It is typically executed as part of the Transfer to General Ledger and related payroll costing processes, including the cost transfer steps associated with payroll run completion and payment processing. Because it is referenced by no other packages, it functions as an end-point routine invoked from the payroll processing framework rather than as a shared utility.

Customers and implementers generally encounter this package indirectly, through standard payroll concurrent programs and the Costing and Transfer to GL flows, rather than through forms or custom code. Customizations should avoid calling it directly; where adjustments to payroll costing or GL transfer behavior are required, the supported extension points are the configured costing, element, and GL flexfield mapping setups rather than modifications to this package. Any diagnostic activity should rely on the documented dependencies and the valid status confirmed in ETRM for 12.1.1 and 12.2.2.