Search Results maintain_cost_keyflex

Overview

APPS.PAY_COST_ALLOCATIONS_F_PKG is a payroll cost allocation maintenance package belonging to the Oracle Payroll module of Oracle E-Business Suite. It encapsulates the row-level data manipulation logic for the PAY_COST_ALLOCATIONS_F table, which stores the effective-dated allocation of an assignment's payroll costs across one or more cost allocation keyflex segments. Each row associates an assignment with a cost allocation keyflex combination and a proportion, thereby determining how the employer's payroll cost burden is distributed among general ledger accounts, cost centres, or projects.

The package follows the standard Oracle EBS table-handler pattern: it provides primitive insert, update, delete, and lock operations against the underlying table, plus a specialised routine, MAINTAIN_COST_KEYFLEX, which manages the relationship between cost allocation records and their keyflex segment values. Because the object is an internal table handler rather than a public business API, it is not intended to be called directly by external integrations; it is invoked by the payroll forms and concurrent processes that own the cost allocation entity. The header comment indicates the source was last revised under patch file pycsa01t.pkb, consistent with Oracle Payroll code delivered under the APPS schema.

Key Procedures and Functions

• INSERT_ROW — Inserts a new effective-dated cost allocation row into PAY_COST_ALLOCATIONS_F. The procedure accepts the primary key components (cost allocation identifier and effective dates) together with business group, assignment, cost allocation keyflex identifier, proportion, and the standard WHO audit columns (request id, program application id, program id, program update date). It subsequently retrieves and returns the ROWID of the newly created row.
• UPDATE_ROW — Modifies an existing cost allocation row, keyed by its ROWID, updating the cost allocation attributes and audit columns in place. This supports corrections to effective dates, proportions, or keyflex assignment on a record already stored.
• DELETE_ROW — Removes a cost allocation row identified by ROWID, used when an allocation is no longer required or is superseded.
• LOCK_ROW — Acquires a row-level lock on the specified cost allocation record, serialising concurrent modifications and enforcing the optimistic locking discipline typical of Oracle Forms-based maintenance.
• MAINTAIN_COST_KEYFLEX — The routine referenced by the search term "maintain_cost_keyflex". It is the dedicated handler for cost allocation keyflex data associated with the allocation row, ensuring that the keyflex combination referenced by COST_ALLOCATION_KEYFLEX_ID remains consistent when allocation rows are created, changed, or removed. This procedure centralises the logic that would otherwise be duplicated across the insert, update, and delete paths.

Tables Accessed

The package's documented operations reference a single table through its APPS synonym: PAY_COST_ALLOCATIONS_F. All insert, update, delete, and lock activity is directed at this table. Its columns include COST_ALLOCATION_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, BUSINESS_GROUP_ID, COST_ALLOCATION_KEYFLEX_ID, ASSIGNMENT_ID, PROPORTION, and the audit columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE. The table is date-tracked, meaning multiple rows may exist for the same assignment across different effective periods, which is why the primary key and the row-fetch logic in INSERT_ROW include both effective start and end dates.

Usage Notes

PAY_COST_ALLOCATIONS_F_PKG is a low-level maintenance package and is not exposed as a public API. It is typically invoked from Oracle Forms maintaining assignment cost allocations, and from payroll concurrent processes and internal PL/SQL that need to create or amend allocation rows and their keyflex references. The ETRM metadata records no other packages referencing it, confirming that it is a terminal table handler within the payroll code stack. Customisations should avoid direct calls to these procedures where a supported business API exists; where they are used, callers must supply valid keyflex identifiers, correct effective date ranges, and the WHO audit context so that the standard audit columns are populated. Because the routines manipulate date-tracked rows, callers should handle overlapping effective periods deliberately and rely on LOCK_ROW to avoid concurrent update conflicts.