Results for “prc_header_id”

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

Overview

The FV_FACTS_PRC_DTL table is an Oracle E-Business Suite Federal Financials (FV) object owned by the FV schema. Per Oracle's ETRM documentation, it is described as a "Table used for Reporting Code Mapping," positioning it as the detail-level repository that records how programs, values, and reporting attributes are mapped within federal reporting structures. In EBS 12.1.1 and 12.2.2 the table is shipped with a VALID status and comprises 28 columns. It carries a single-column surrogate primary key, PRC_DETAIL_ID, exposed through the FV_FACTS_PRC_DTL_PK constraint, and a business-key candidate delivered via the unique index FV_FACTS_PRC_DTL_U1 on the same column.

From a heuristic Data Vault perspective, the metadata classifies this object as standalone. As a modeling suggestion, this implies the table behaves primarily as a satellite-like detail store attached to the header through a documented foreign key rather than as an independent hub or link; its referential reach is limited to two parent objects, reinforcing that classification.

Key Information Stored

The most significant columns in FV_FACTS_PRC_DTL are the following:

• PRC_DETAIL_ID — the surrogate primary key and the sole column of the PK constraint; also the column carried by unique index FV_FACTS_PRC_DTL_U1.
• PRC_HEADER_ID — foreign key to FV_FACTS_PRC_HDR, anchoring each detail row to its header record. It also participates in the composite unique index FV_FACTS_PRC_DTL_U2.
• SET_OF_BOOKS_ID — identifies the ledger (set of books) under which the mapping applies, and is part of the U2 business key.
• PROGRAM_VALUE — the program code associated with the mapping; completes the U2 unique index alongside PRC_HEADER_ID and SET_OF_BOOKS_ID.
• FLEX_VALUE_ID — foreign key to FND_FLEX_VALUES, linking the detail line to a defined key-flexfield value.
• REPORTING_DESC — descriptive text for the reporting mapping.
• REPORTING_CODE#1 — a reporting code identifier held on the detail row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) attribute block, providing extensible, context-driven storage for customer-specific reporting attributes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns tracking row creation and modification.

The distinction between the surrogate key (PRC_DETAIL_ID) and the composite business key (PRC_HEADER_ID, SET_OF_BOOKS_ID, PROGRAM_VALUE) matters for integration and de-duplication logic: the former is the technical row identity, while the latter enforces the natural uniqueness of a program-to-ledger mapping line.

Common Use Cases and Queries

Typical usage centers on validating and reporting federal reporting-code mappings. A frequent pattern joins the detail to its header to resolve the full mapping context:

• Retrieve all detail lines for a header: SELECT * FROM FV.FV_FACTS_PRC_DTL WHERE PRC_HEADER_ID = :p_header_id;
• Resolve the flexfield value description: join FLEX_VALUE_ID to FND_FLEX_VALUES to translate the stored ID into a displayable value.
• Enforce the business key: query by PRC_HEADER_ID, SET_OF_BOOKS_ID, and PROGRAM_VALUE, the columns of the U2 unique index, when performing upserts or duplicate checks.
• Report DFF attributes: pivot the ATTRIBUTE1..15 columns filtered by ATTRIBUTE_CATEGORY for customer-defined reporting dimensions.

Related Objects

• FV_FACTS_PRC_HDR — joined via FV_FACTS_PRC_DTL.PRC_HEADER_ID = FV_FACTS_PRC_HDR.PRC_HEADER_ID; the parent header for these detail mappings.
• FND_FLEX_VALUES — joined via FV_FACTS_PRC_DTL.FLEX_VALUE_ID = FND_FLEX_VALUES.FLEX_VALUE_ID; the key-flexfield value definition.

Because the metadata classifies the table as standalone with only these two documented foreign keys, its dependency surface is narrow; beyond FV_FACTS_PRC_HDR and FND_FLEX_VALUES, references generally arrive through the header and standard FND/WHO audit relationships rather than direct foreign keys.