Search Results pk_per_ca_ee_report_lines

Overview

PER_CA_EE_REPORT_LINES is a table owned by the HR schema within the Oracle E-Business Suite Human Resources (PER) product family. It functions as a staging and reporting structure that holds line-level detail for compensation and eligibility (CA/EE) reporting output generated by Oracle HR processes. Rows are written by concurrent programs and stored against a REQUEST_ID, allowing each run of a report or process to be isolated and re-queried independently. The table is classified as VALID in the ETRM 12.1.1 / 12.2.2 data model.

The heuristic Data Vault classification derived from its foreign key structure is standalone. In modeling terms, this suggests the object does not behave as a classic hub, link, or satellite: it carries no documented foreign keys to other entities and is best treated as an independent, self-contained reporting or staging table keyed on its own composite identifier. The documented physical schema in ETRM 12.2.2 comprises 33 columns under the HR owner.

Key Information Stored

The primary key is the composite PK_PER_CA_EE_REPORT_LINES, defined over the columns REQUEST_ID and LINE_NUMBER. These are the only surrogate/business-key candidates documented; no separate unique index or alternate key is recorded, so the composite of these two columns is the sole guaranteed identifier for a row.

• REQUEST_ID — identifies the concurrent request or process run that produced the row; the dominant partitioning column.
• LINE_NUMBER — the sequence of the row within a given request, completing the primary key.
• CONTEXT — the descriptive context, typically the key flexfield structure name associated with the report.
• SEGMENT1 through SEGMENT30 — thirty generic reporting segments holding the flexfield or report-line values. These supply the substantive payload of each line and are populated by the generating program according to the report's context.

In practice, REQUEST_ID and CONTEXT act as the effective business-key grouping, while LINE_NUMBER orders the output.

Common Use Cases and Queries

Because data is tagged by request, the dominant access pattern is retrieval of all lines for a single report execution. This supports reconciliation, downstream reporting extracts, audit of a specific run, and rapid diagnosis of why a given compensation or eligibility report produced particular output.

Typical query — pull all output lines for a request:

• SELECT line_number, context, segment1, segment2, segment3 FROM per_ca_ee_report_lines WHERE request_id = :p_request_id ORDER BY line_number;

Typical query — count and range of lines per run:

• SELECT request_id, COUNT(*) lines, MIN(line_number) first_line, MAX(line_number) last_line FROM per_ca_ee_report_lines GROUP BY request_id;

Extracting flexfield-style output joins the segments together after filtering on CONTEXT, which determines the meaning of each segment. Reporting use cases include building external extracts, comparing output across successive requests, and feeding the lines into downstream payroll or eligibility analysis.

Related Objects

The ETRM metadata records no explicit foreign keys for this table; its relationship classification is standalone, so joins are driven by the shared REQUEST_ID convention rather than declarative constraints. Significant related objects include:

• FND_CONCURRENT_REQUESTS — joined via PER_CA_EE_REPORT_LINES.REQUEST_ID = FND_CONCURRENT_REQUESTS.REQUEST_ID to obtain program name, run date, and status.
• FND_CONCURRENT_PROGRAMS — linked through the concurrent request to identify the generating report.
• FND_USER — retrieved through the concurrent request to attribute the run to a user.
• PER_ALL_PEOPLE_F — commonly joined where a segment carries a person identifier for compensation and eligibility analysis.
• PER_ALL_ASSIGNMENTS_F — joined where report lines reflect assignment-level detail.
• FND_FLEX_VALUES / FND_ID_FLEX_SEGMENTS — used to translate CONTEXT and segment values into descriptive meanings.

These objects, combined with REQUEST_ID, provide the practical context for interpreting the report lines that this table stores.