Results for “program_segment”

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

Overview

FV_FACTS_PRC_HDR is a Federal Financials (FV) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that supports FACTS (Financial Accounting and Control Tracking System) reporting code mapping. It serves as the header-level repository for the mapping rules that translate Oracle General Ledger accounting flexfield combinations into the Treasury reporting structures required for federal FACTS submissions. The table is owned by the FV schema and holds a VALID status in the ETRM 12.2.2 reference.

From a Data Vault modeling perspective, the mined foreign-key structure classifies FV_FACTS_PRC_HDR as a standalone entity. This is a heuristic suggestion: the table anchors a single dependent child (FV_FACTS_PRC_DTL) but is not itself joined upward by an FK to a parent, so it behaves functionally like a hub/root record with its own descriptive attributes rather than a pure link or satellite. Modelers adopting Data Vault conventions would typically treat PRC_HEADER_ID as the hub business key and push the descriptive and attribute columns into an adjacent satellite.

Key Information Stored

The table contains 32 documented columns. The most significant are:

• PRC_HEADER_ID — the surrogate primary key (FV_FACTS_PRC_HDR_PK) and also a unique-index candidate (FV_FACTS_PRC_HDR_U1). It uniquely identifies each mapping header.
• SET_OF_BOOKS_ID — the ledger context for the mapping rule.
• TREASURY_SYMBOL_ID and TREASURY_SYMBOL — the Treasury symbol (agency accounting identifier) targeted by the mapping.
• FUND_VALUE and FUND_VALUE_D — the fund value and its descriptive form used in the mapping.
• PROGRAM_SEGMENT and FLEX_VALUE_SET_ID — the program segment value and the flexfield value set that governs validation.
• PRC_MAPPING_FLAG — an indicator controlling whether the header participates in active PRC mapping.
• CODE_TYPE and CODE_TYPE_D — the reporting code type and its description.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — a standard Oracle descriptive flexfield (DFF) column set for customer-extensible attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle who-columns recording audit and concurrency information.

The business-key candidate identified by the second unique index, FV_FACTS_PRC_HDR_U2, is the combination of SET_OF_BOOKS_ID, TREASURY_SYMBOL_ID, and FUND_VALUE. This distinguishes the surrogate PK (PRC_HEADER_ID) from the natural/business key that enforces uniqueness of a mapping rule per ledger and Treasury symbol.

Common Use Cases and Queries

FV_FACTS_PRC_HDR is primarily consumed by FACTS reporting programs and federal financial reconciliation reports. Typical scenarios include retrieving all mapping headers for a given ledger, joining headers to their detail rules, and validating that a Treasury symbol is properly mapped before FACTS extract.

A representative query pattern:

• Selecting mapped Treasury symbols for a ledger: SELECT h.prc_header_id, h.treasury_symbol, h.fund_value, h.code_type FROM fv.fv_facts_prc_hdr h WHERE h.set_of_books_id = :ledger_id AND h.prc_mapping_flag = 'Y';
• Joining to detail rules: SELECT h.treasury_symbol, d.* FROM fv.fv_facts_prc_hdr h, fv.fv_facts_prc_dtl d WHERE h.prc_header_id = d.prc_header_id;
• Resolving DFF context: filter on attribute_category and the attribute columns for site-specific reporting rules.

Related Objects

• FV_FACTS_PRC_DTL — the dependent detail table, joined on PRC_HEADER_ID. This is the only documented FK relationship (FV_FACTS_PRC_DTL.PRC_HEADER_ID → FV_FACTS_PRC_HDR).
• GL_SETS_OF_BOOKS / GL_LEDGERS — referenced via SET_OF_BOOKS_ID to resolve ledger context.
• FND_FLEX_VALUE_SETS and FND_FLEX_VALUES — referenced via FLEX_VALUE_SET_ID for segment validation.
• HR_ALL_ORGANIZATION_UNITS and Treasury symbol maintenance objects — used to resolve TREASURY_SYMBOL_ID.
• FACTS reporting concurrent programs and federal financials extract processes consume both header and detail rows during report generation.

Because the table is standalone at the FK level, most dependencies are logical rather than enforced by database constraints, so referential integrity in reporting joins should be validated through the FND flexfield and ledger tables rather than assumed.