Results for “cost_allocation_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PAY_COST_ALLOCATIONS_X is a date-effective (X) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PAY — Payroll product family. It exposes the currently effective rows of the cost allocation entity used by Oracle Payroll to distribute an assignment's payroll costs across multiple cost centers, accounts, or key flexfield combinations. In Oracle EBS, the "_X" suffix denotes a date-effective view that filters the underlying "_F" (date-effective) table so that only records whose effective date range brackets the current date are visible at runtime. The view is documented as VALID in both release 12.1.1 and 12.2.2.

Because the view applies the SYSDATE-based predicate internally, it presents a "live" snapshot of cost allocation records rather than the full historical datastore. This makes it the standard reference object for reporting and integration logic that needs to know how payroll costs are split at any given point in time — for example, general ledger cost distribution, payroll costing reports, and third-party or custom extracts that need to resolve the currently valid cost allocation for a given assignment.

Underlying Base Objects

The view is defined over a single documented base object, the synonym PAY_COST_ALLOCATIONS_F. This table is the date-effective ("_F") table that stores every dated version of a cost allocation row, keyed by COST_ALLOCATION_ID together with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. The view's defining SQL is:

• SELECTs the core columns of PAY_COST_ALLOCATIONS_F
• WHERE TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE

The TRUNC on SYSDATE removes the time component, so membership is evaluated against the calendar date. Any rows whose effective range does not include the current date — future-dated changes, historical rows superseded by a later datetrack change, or records closed off by an END date in the past — are excluded. Consequently, PAY_COST_ALLOCATIONS_X behaves as a strict subset of PAY_COST_ALLOCATIONS_F at query time, and cannot be used to reconstruct prior or planned allocation states.

Key Columns

• COST_ALLOCATION_ID — Primary identifier of the cost allocation record; the same ID is shared by all dated versions in the _F table.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The date range over which the row is valid; the view predicate compares these to TRUNC(SYSDATE).
• BUSINESS_GROUP_ID — The business group (legislative data group) that owns the record; essential for multi-org aware queries.
• COST_ALLOCATION_KEYFLEX_ID — The foreign key to the cost allocation key flexfield combination. This is the value most often used to resolve the accounting/flexfield segment combination to which a proportion of payroll cost is posted.
• ASSIGNMENT_ID — The assignment to which the allocation applies; links the record to the payroll assignment, person, and its costing setup.
• PROPORTION — The percentage or fraction of cost assigned to the referenced keyflex combination; allocations for an assignment typically sum to 100%.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program audit columns identifying the request and program that created or last updated the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard WHO (audit) columns.

Common Use Cases and Queries

Typical scenarios involve resolving the active cost split for assignments, validating allocation coverage before a payroll costing run, and reconciling payroll results to General Ledger. A user searching on "cost_allocation_keyflex_id" is generally trying to join the view to the flexfield combination table to retrieve segment values, or to reconcile an assignment's allocation percentages.

Example — retrieve current allocations with their keyflex combination for a business group:

• SELECT ca.COST_ALLOCATION_ID, ca.ASSIGNMENT_ID, ca.COST_ALLOCATION_KEYFLEX_ID, ca.PROPORTION, ca.EFFECTIVE_START_DATE, ca.EFFECTIVE_END_DATE FROM APPS.PAY_COST_ALLOCATIONS_X ca WHERE ca.BUSINESS_GROUP_ID = :p_business_group_id ORDER BY ca.ASSIGNMENT_ID;

Example — verify that allocations for an assignment sum to 100%:

• SELECT ASSIGNMENT_ID, SUM(PROPORTION) FROM APPS.PAY_COST_ALLOCATIONS_X WHERE ASSIGNMENT_ID = :p_assignment_id GROUP BY ASSIGNMENT_ID HAVING SUM(PROPORTION) <> 1;

Example — resolve the keyflex combination to its segments using FND_FLEX_VALUES / FND_KF_STRUC_INSTANCES_V: join COST_ALLOCATION_KEYFLEX_ID to the cost allocation key flexfield structure to translate the surrogate ID into descriptive segment values for reporting. Because the view already filters on SYSDATE, no additional datetrack predicate is required; however, queries intended for historical costing should read PAY_COST_ALLOCATIONS_F directly and supply an explicit effective date.