Search Results user_fk1




Overview
Explore in AI Chat

Overview

POA_EDW_CONTRACT_AGRMNTS_FCV is a fact collection view owned by the APPS schema in Oracle E-Business Suite, classified under the Purchasing (PO) product family. It serves as the extract layer for the Enterprise Data Warehouse (EDW) star-schema model for purchasing contract agreements. The view flattens contract header data into a denormalized structure composed of surrogate foreign keys (the *_FK columns), numeric measures (the *_T and *_G columns for transactional and global currency amounts), and descriptive attributes such as contract numbers and comments.

In EBS 12.1.1 and 12.2.2 the object is a presentation-layer view rather than a transactional table. Its role is to feed EDW fact loads and downstream analytics: purchasing spend analysis, contract compliance reporting, buyer performance measurement, and supplier agreement tracking. The view text is a straightforward projection over an underlying staging view, POABV_EDW_CONTRACT_AGRMNTS_FCV, which performs the heavy lifting of joining and resolving the contract data. The APPS synonym or view referenced here therefore acts as the published, stable interface consumed by ETL jobs and BI tools.

Underlying Base Objects

The documented definition of POA_EDW_CONTRACT_AGRMNTS_FCV is a SELECT from POABV_EDW_CONTRACT_AGRMNTS_FCV. This "BV" (base view) layer is the object that in turn resolves against Purchasing contract tables — principally the purchasing document headers and their associated lookup and reference tables that supply the surrogate keys. The metadata notes no separately documented base tables for this wrapper view, so the definitive join logic resides in the POABV layer.

Key implications follow from this two-tier design. First, the outer view is intentionally thin and stable, insulating EDW consumers from changes in the underlying 11i/12.x Purchasing schema. Second, hard-coded placeholders such as 'NA_EDW' for USER_FK1 through USER_FK5 and TO_NUMBER(NULL) for USER_MEASURE1 through USER_MEASURE5 indicate that the fact model reserves user-extension slots that are not currently populated by Purchasing. Third, the NULL USER_ATTRIBUTE1-15 columns follow the same pattern, providing schema-compatible columns without data until a source is mapped.

Key Columns

Common Use Cases and Queries

Typical consumption patterns join the fact view to EDW dimension views on the *_FK columns. For supplier industry analysis, SIC_CODE_FK is resolved to the supplier SIC dimension; for currency reporting, TXN_CUR_CODE_FK and TXN_CUR_RATE_TYPE determine whether the transactional or global measure is used.

Representative query — contract value by supplier SIC code:

  • SELECT f.SIC_CODE_FK, SUM(f.AMT_AGREED_G) total_agreed FROM POA_EDW_CONTRACT_AGRMNTS_FCV f WHERE f.COLLECTION_STATUS = 'COMPLETE' GROUP BY f.SIC_CODE_FK;

Representative query — released amounts by buyer and operating unit:

  • SELECT f.BUYER_FK, f.OPERATING_UNIT_FK, SUM(f.AMT_RELEASED_T) released FROM POA_EDW_CONTRACT_AGRMNTS_FCV f GROUP BY f.BUYER_FK, f.OPERATING_UNIT_FK;

Because the placeholder columns return fixed values, queries should not filter on USER_FK1-5 or USER_MEASURE1-5. Direct joins to EBS 12.1.1/12.2.2 base Purchasing tables should be avoided in favor of the EDW dimension keys, preserving the separation of concerns that the two-tier view design enforces.