Results for “pay_cost_allocation_keyflex”

50+ results




Overview
Explore in AI Chat

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

Overview

PAY_COST_ALLOCATION_KEYFLEX is the Cost Allocation key flexfield combinations table in the Oracle E-Business Suite Payroll (PAY) module, owned by the HR schema. It stores the valid, instantiated combinations of the Cost Allocation key flexfield (KFF), which is the accounting distribution construct used throughout Payroll to determine where labor costs, employer contributions, and payroll charges are posted in the General Ledger. Every payroll run, element entry, element link, cost allocation record, and payroll line ultimately resolves to a row in this table via the COST_ALLOCATION_KEYFLEX_ID surrogate key.

The table is defined with two documented functional constraints: a primary key on COST_ALLOCATION_KEYFLEX_ID (constraint PAY_COST_ALLOCATION_KEYFLE_PK) and a rich set of inbound foreign keys from both Payroll and Budget/Position Control (PQH) tables. Based on the foreign-key topology — many child tables referencing a single surrogate key with no documented parent keys from this table outward — the Data Vault modeling heuristic classifies PAY_COST_ALLOCATION_KEYFLEX as hub-leaning: a candidate business-key hub whose natural key is the concatenated flexfield segmentation rather than the surrogate ID. This classification is a modeling suggestion only; Oracle does not implement Data Vault semantics.

Key Information Stored

The table contains 42 documented columns in release 12.2.2, a subset of which carry the substantive business meaning:

  • COST_ALLOCATION_KEYFLEX_ID — the surrogate primary key (PAY_COST_ALLOCATION_KEYFLE_PK) referenced by all child tables.
  • CONCATENATED_SEGMENTS — the fully concatenated, display-formatted flexfield combination; the practical business identifier for reports and GL transfer.
  • ID_FLEX_NUM — identifies which key flexfield definition (structure) the combination belongs to, allowing multiple structures within one KFF.
  • SEGMENT1 through SEGMENT30 — the individual segment values that, taken together, form the accounting distribution (typically balancing segment, cost center, natural account, and similar qualifiers, per the customer's KFF configuration).
  • SUMMARY_FLAG and ENABLED_FLAG — control whether the combination is a summary/parent value and whether it is currently active for new transactions.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the effective-dating window for the combination.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard Oracle WHO/audit columns.

The documented unique index and primary key both key on COST_ALLOCATION_KEYFLEX_ID; a business-key candidate would logically be the combination of ID_FLEX_NUM plus CONCATENATED_SEGMENTS (or the individual SEGMENTn values with effective dates), which is how downstream reporting typically joins to this table.

Common Use Cases and Queries

Typical reporting scenarios include tracing payroll charges to their GL account, validating that a distribution used on an element entry or link is still enabled, and reconciling cost allocations across payroll runs. The user's search term pqh_worksheet_fund_srcs is a direct child table: PQH_WORKSHEET_FUND_SRCS.COST_ALLOCATION_KEYFLEX_ID references this table, so a common query pattern joins funding-source worksheets to their underlying cost allocation combination.

  • Look up a combination's readable account: SELECT COST_ALLOCATION_KEYFLEX_ID, CONCATENATED_SEGMENTS FROM PAY_COST_ALLOCATION_KEYFLEX WHERE ENABLED_FLAG = 'Y';
  • Join worksheet funding sources to their KFF: SELECT w.*, k.CONCATENATED_SEGMENTS FROM PQH_WORKSHEET_FUND_SRCS w, PAY_COST_ALLOCATION_KEYFLEX k WHERE w.COST_ALLOCATION_KEYFLEX_ID = k.COST_ALLOCATION_KEYFLEX_ID;
  • Trace payroll line costs: join PSP_PAYROLL_LINES.COST_ALLOCATION_KEYFLEX_ID to retrieve the GL-relevant segment string for each payroll line.
  • Audit element links: PAY_ELEMENT_LINKS_F references this table twice — once via COST_ALLOCATION_KEYFLEX_ID and once via BALANCING_KEYFLEX_ID — so a single element link can carry both a cost allocation account and a balancing account; reporting must disambiguate the two joins.
  • Reconcile GL interface: join PAY_GL_INTERFACE.COST_ALLOCATION_KEYFLEX_ID to validate that every interfaced distribution resolves to a valid, enabled combination.

Related Objects

The table is a heavily referenced hub. The most significant dependent objects, with their documented join columns, are:

  • PQH_WORKSHEET_FUND_SRCS — funding source on position control worksheets (COST_ALLOCATION_KEYFLEX_ID).
  • PQH_BUDGET_FUND_SRCS and PQH_DFLT_FUND_SRCS — budget and default funding sources (COST_ALLOCATION_KEYFLEX_ID).
  • PAY_ELEMENT_LINKS_F — element link costing and balancing accounts (COST_ALLOCATION_KEYFLEX_ID, BALANCING_KEYFLEX_ID).
  • PAY_ELEMENT_ENTRIES_F — element entry-level cost allocation (COST_ALLOCATION_KEYFLEX_ID).
  • PAY_ALL_PAYROLLS_F — payroll-level cost allocation and suspense account (COST_ALLOCATION_KEYFLEX_ID, SUSPENSE_ACCOUNT_KEYFLEX_ID).
  • PSP_PAYROLL_LINES — payroll line distributions (COST_ALLOCATION_KEYFLEX_ID).
  • PAY_GL_INTERFACE and PQH_GL_INTERFACE — GL transfer/interfacing of costing results (COST_ALLOCATION_KEYFLEX_ID).
  • HR_ALL_ORGANIZATION_UNITS — default organization cost allocation (COST_ALLOCATION_KEYFLEX_ID).

These relationships confirm the table's role as the canonical reference for accounting distributions across Payroll and Position Control, and any reporting layer that reconstructs costs should treat it as the primary hub for flexfield combinations.