Search Results qp_sourcesystem_fnarea_map




Overview
Explore in AI Chat

Overview

The QP_SOURCESYSTEM_FNAREA_MAP table resides in the QP schema and belongs to the Advanced Pricing module (QP) of Oracle E-Business Suite, as documented in ETRM 12.1.1 and 12.2.2. It stores the mapping between source system code combinations and the functional areas (business flows) in which those source systems participate within Oracle Pricing. This mapping is central to the Pricing Transaction Entity (PTE) architecture, which allows pricing data originating from external or adjacent applications to be routed to the correct pricing functional area.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. In Data Vault modeling terms, this suggests the table functions primarily as a reference or cross-reference construct rather than a conventional hub, link, or satellite. It holds no outbound foreign keys to other hubs in the documented relationship data, so it can be treated as an independent mapping reference in analytical models.

Key Information Stored

The table comprises 31 documented columns. The most significant are:

Common Use Cases and Queries

Typical usage scenarios include verifying which functional areas a given source system feeds, and diagnosing pricing failures where the source system is not enabled for the intended flow. A representative query for enabled, seeded mappings is:

  • SELECT pte_source_system_id, functional_area_id, enabled_flag, seeded_flag FROM qp.qp_sourcesystem_fnarea_map WHERE enabled_flag = 'Y' ORDER BY pte_source_system_id;
  • Joining the two unique-index columns (PTE_SOURCE_SYSTEM_ID, FUNCTIONAL_AREA_ID) as the natural lookup key rather than the surrogate PTE_SOURCESYSTEM_FNAREA_ID.
  • Reporting the count of mappings per functional area, or auditing rows where SEEDED_FLAG = 'N' to detect customer customizations.
  • Filtering by ZD_EDITION_NAME in 12.2.2 environments to isolate the active edition of the reference data.

Related Objects

Because the documented FK structure classifies this object as standalone, no direct foreign-key dependencies are recorded. Conceptually, the mapping links source-system definitions and pricing functional areas, and is consumed by the Advanced Pricing transaction engine and related QP views and APIs that resolve PTE routing. The unique indexes QP_SOURCESYSTEM_FNAREA_MAP_PK and QP_SOURCESYSTEM_FNAREA_MAP_U1 are the primary relational anchors, while FUNCTIONAL_AREA_ID and PTE_SOURCE_SYSTEM_ID connect logically to the functional-area and source-system reference data used throughout QP pricing setup.