Search Results pay_cost_allocations_f_pkg
Overview
PAY_COST_ALLOCATIONS_F_PKG is an Oracle Applications (APPS) PL/SQL package that encapsulates the core data manipulation logic for the PAY_COST_ALLOCATIONS_F table within the Oracle E-Business Suite Payroll (PAY) module. In Oracle EBS 12.1.1 and 12.2.2, this package operates as a table handler or "foundation" package, providing the procedural interface through which cost allocation records are inserted, updated, deleted, locked, and validated. Cost allocations in Oracle Payroll define how payroll run results are distributed across general ledger accounts, cost centers, and balancing segments. Because this distribution logic is closely tied to the payroll costing process, the package abstracts the low-level DML operations so that higher-level costing programs and forms do not manipulate the base table directly. The package resides in the APPS schema, is documented as VALID, and is classified under the general API category "OTHER" rather than as a public, supported business API. This distinction is significant: it indicates that the package is intended primarily for internal use by Oracle Payroll components, though it can be referenced by custom extensions with appropriate caution.
Key Procedures and Functions
The ETRM metadata documents five procedures and functions within PAY_COST_ALLOCATIONS_F_PKG. Each serves a distinct role in the lifecycle of a cost allocation record:
- INSERT_ROW — Creates a new row in the PAY_COST_ALLOCATIONS_F table, populating the cost allocation definition and its associated attributes. It is the entry point for adding new allocation records.
- UPDATE_ROW — Modifies an existing cost allocation record, allowing changes to be persisted to the base table.
- DELETE_ROW — Removes a cost allocation record from the table, supporting the maintenance and cleanup of obsolete allocation definitions.
- LOCK_ROW — Obtains a lock on a specific row to ensure concurrency control, preventing simultaneous modification of the same allocation record by multiple sessions.
- MAINTAIN_COST_KEYFLEX — Manages and maintains the cost key flexfield values associated with the allocation, ensuring that the accounting flexfield segments assigned to the cost allocation remain consistent and valid.
No parameter lists are reproduced here, as the metadata does not document them; consumers should inspect the package specification in the database for exact signatures.
Tables Accessed
The package references a single documented table via its APPS synonym: PAY_COST_ALLOCATIONS_F. This table stores the "F" (foundation) definitions of cost allocations used by Oracle Payroll costing. The INSERT_ROW, UPDATE_ROW, and DELETE_ROW procedures perform the corresponding DML against this table, while LOCK_ROW reads and locks the relevant record to serialize concurrent access. MAINTAIN_COST_KEYFLEX interacts with the key flexfield structure underlying the allocation, ensuring the cost allocation's accounting flexfield values are consistently registered in the base table. No other base tables are listed in the documented dependency set, which confirms that the package is narrowly scoped to the maintenance of cost allocation foundation data.
Usage Notes
PAY_COST_ALLOCATIONS_F_PKG is typically invoked by the Oracle Payroll forms and internal costing processes that present and maintain cost allocation definitions, rather than being called directly by end users. The presence of a LOCK_ROW procedure indicates that it is used in an interactive, multi-user environment where record locking is required—characteristic of a Forms-based maintenance screen. Because the ETRM documentation lists zero referencing packages, the package is not exposed as a dependency for other PL/SQL APIs within APPS, reinforcing its role as a private implementation detail of the cost allocation maintenance layer. Custom developers should treat it as an internal handler: direct invocation is possible but unsupported, and upgrades in 12.1.1 or 12.2.2 may change its behavior without notice. Where custom integrations require cost allocation maintenance, Oracle recommends using the supported Cost Allocation APIs or the standard Payroll costing concurrent programs instead of calling this foundation package directly. Its primary value to technical consultants lies in understanding how the PAY_COST_ALLOCATIONS_F table is populated and maintained when troubleshooting costing and general ledger transfer issues.
-
PACKAGE: APPS.PAY_COST_ALLOCATIONS_F_PKG
12.2.2
owner:APPS, object_type:PACKAGE, object_name:PAY_COST_ALLOCATIONS_F_PKG, status:VALID,
-
PACKAGE BODY: APPS.PAY_COST_ALLOCATIONS_F_PKG
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:PAY_COST_ALLOCATIONS_F_PKG, status:VALID,
-
PACKAGE: APPS.PAY_COST_ALLOCATIONS_F_PKG
12.1.1
owner:APPS, object_type:PACKAGE, object_name:PAY_COST_ALLOCATIONS_F_PKG, status:VALID,
-
PACKAGE BODY: APPS.PAY_COST_ALLOCATIONS_F_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:PAY_COST_ALLOCATIONS_F_PKG, status:VALID,
-
PACKAGE: APPS.PAY_COST_ALLOCATIONS_F_PKG
12.1.1
-
PACKAGE: APPS.PAY_COST_ALLOCATIONS_F_PKG
12.2.2
-
SYNONYM: APPS.PAY_COST_ALLOCATIONS_F
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PAY_COST_ALLOCATIONS_F, status:VALID,
-
SYNONYM: APPS.PAY_COST_ALLOCATIONS_F
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PAY_COST_ALLOCATIONS_F, status:VALID,
-
PACKAGE: APPS.HR_ENTRY
12.2.2
owner:APPS, object_type:PACKAGE, object_name:HR_ENTRY, status:VALID,
-
PACKAGE: APPS.HR_ENTRY
12.1.1
owner:APPS, object_type:PACKAGE, object_name:HR_ENTRY, status:VALID,
-
PACKAGE BODY: APPS.PAY_COST_ALLOCATIONS_F_PKG
12.1.1
-
PACKAGE BODY: APPS.PAY_COST_ALLOCATIONS_F_PKG
12.2.2
-
APPS.PAY_COST_ALLOCATIONS_F_PKG dependencies on PAY_COST_ALLOCATIONS_F_PKG
12.2.2
-
APPS.PAY_COST_ALLOCATIONS_F_PKG dependencies on PAY_COST_ALLOCATIONS_F_PKG
12.1.1
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
APPS.PAY_COST_ALLOCATIONS_F_PKG dependencies on PAY_COST_ALLOCATIONS_F
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
APPS.PAY_COST_ALLOCATIONS_F_PKG dependencies on PAY_COST_ALLOCATIONS_F
12.2.2
-
PACKAGE: APPS.APP_EXCEPTION
12.2.2
owner:APPS, object_type:PACKAGE, object_name:APP_EXCEPTION, status:VALID,
-
PACKAGE: APPS.APP_EXCEPTION
12.1.1
owner:APPS, object_type:PACKAGE, object_name:APP_EXCEPTION, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
PACKAGE: APPS.FND_MESSAGE
12.2.2
owner:APPS, object_type:PACKAGE, object_name:FND_MESSAGE, status:VALID,
-
PACKAGE: APPS.FND_MESSAGE
12.1.1
owner:APPS, object_type:PACKAGE, object_name:FND_MESSAGE, status:VALID,
-
PACKAGE: SYS.STANDARD
12.1.1
owner:SYS, object_type:PACKAGE, object_name:STANDARD, status:VALID,