Search Results pay_action_parameter




Overview

APPS.PAY_TRGL_PKG is the Oracle Payroll cost transfer package responsible for moving calculated payroll costs into the General Ledger interface. The package header comment defines its purpose concisely: it is the "Procedure to transfer pay costs to General Ledger." The business function it serves is the summation of costs for each cost centre across all payroll runs that fall within a defined transfer period. Summation is performed across assignments, while distinct journal entries are created for debit and credit for each currency, preserving the accounting integrity of the transfer.

The package is classified as OTHER in the ETRM repository and is owned by APPS. The current source header (pytrangl.pkb 120.17.12020000.3, dated 10-JAN-2013) reflects an extensive lineage of bug fixes and performance tuning reaching back through version 115.x. These modifications include the insertion of null rather than zero for the opposing side of debit/credit values in PAY_GL_INTERFACE and GL_INTERFACE (Bug 14528715), the addition of the ledger_id column for Release 12 GL_INTERFACE inserts (115.47), suppression of segment column population for payment costings (Bug 6169000), elimination of double postings for consolidation sets and tax unit balance adjustments, and a series of performance-related hints and query refinements across releases 12.0 and 12.1.

Key Procedures and Functions

ETRM documents three callable units within the package body:

  • TRANS_PAY_COSTS — The primary transfer routine for payroll costs. It aggregates costs by cost centre over the transfer period and writes the resulting debit and credit entries, segregated by currency, to the GL interface tables. Its post-Release 12 form includes ledger identifier handling and the null-versus-zero convention for the contra side of each Dr/Cr pair.
  • TRANS_PAY_COSTS_MT — A variant of the payroll cost transfer, historically the focus of significant performance work. Version 115.49 records a query change introduced for better performance (Bug 8278294), and version 115.48 added an OR condition for binding SQL variables in the context of costing of payments (Bug 7401269). The "_MT" designation indicates a multi-threaded or multi-org execution path used when transfer is performed across more than one organization or thread.
  • TRANS_ASS_COSTS — The assignment-level cost transfer routine. Whereas TRANS_PAY_COSTS operates on cost centre aggregates, TRANS_ASS_COSTS addresses assignment cost detail used in the transfer process.

Parameter lists for these units are not published in the ETRM metadata and are therefore intentionally not restated here. The user's search term, "pay_action_parameter," reflects the package's dependence on payroll action context — the payroll action being transferred, its classification, and its parameter set — which drives the selection of runs included in the transfer period.

Tables Accessed

The package reads and writes the following documented tables through APPS synonyms:

GL_INTERFACE is populated as the downstream general ledger staging table, with segment columns deliberately bypassed in the payment costing path per Bug 6169000.

Usage Notes

PAY_TRGL_PKG is invoked during the payroll cost transfer to General Ledger, typically as the PL/SQL engine behind the Transfer to General Ledger concurrent program in Oracle Payroll. It is called after payroll costing has been run and costs exist in PAY_COSTS, and it is also reached through the payment costing flow. The metadata records zero other packages referencing this one, indicating that it is an entry-point package rather than a shared utility; its callers are concurrent program definitions and internal payroll processes rather than dependent PL/SQL APIs.

Custom code should not call this package directly, because it assumes fully validated payroll action and cost state and writes directly into the GL interface tables. The correct integration point for extensions is the standard cost transfer concurrent process, with any customization limited to GL flexfield mapping via the supporting mapping tables.