Results for “sic_code_fk”

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

Overview

The view POA_EDW_RECEIVING_TXN_FCV is a Purchasing module reporting object within Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the POA (Purchasing) EDW family of views, which are designed to expose receiving transaction data in a flattened, warehouse-friendly format suitable for extract, transform, and load (ETL) processes and operational reporting. The suffix "FCV" indicates a fact-style collection view, and "EDW" signals that the object is intended for Enterprise Data Warehouse consumption rather than transactional online processing.

This view presents one row per receiving transaction, combining foreign key references to conformed dimensions (dates, suppliers, organizations, items, currencies) with numeric measures such as quantities and prices, plus descriptive attributes such as receipt numbers and bill of lading references. It is a reporting and integration construct, and the ETRM metadata notes that it is "Not implemented in this database," meaning the view may be documented for referential purposes without existing as a deployed object in the current instance.

Underlying Base Objects

Per the documentation, the view is defined over the single base object POABV_EDW_RECEIVING_TXN_FCV, which acts as the underlying business view supplying the projected columns. No additional base tables are documented against this view in the ETRM metadata. In practice, the "BV" (business view) naming convention suggests an intermediate layer that itself resolves against the receiving transactions and related dimension tables, but this dependency is not asserted in the provided metadata. The view text uses an ALL_ROWS optimizer hint, reflecting its intended use as a bulk, set-oriented reporting query rather than a targeted lookup.

Key Columns

• FREIGHT_TERMS_FK — A foreign key linking each receiving transaction to the freight terms dimension. This is the column referenced in the user's search and is used to attribute shipping/freight cost responsibility to a receiving line.
• RCV_TXN_PK, INSTANCE_FK, TXN_TYPE_FK — Primary identifier, instance reference, and transaction type classification for the receipt event.
• SUPPLIER_SITE_FK, SUP_SITE_GEOG_FK, DUNS_FK — Dimension keys tying the transaction to supplier sites and geographic or DUNS identifiers.
• BUYER_FK, RCV_DEL_TO_ORG_FK, RCV_LOCATION_FK — Keys identifying the responsible buyer and delivery organization or location.
• TXN_DATE_FK, TXN_CREAT_FK, EXPCT_RCV_DATE_FK, PROMISED_DATE_FK — Date dimension foreign keys for transaction, creation, expected receipt, and promised dates.
• QTY_TXN, QTY_RECEIVED, QTY_ACCEPT, QTY_REJECT, QTY_DELIVER — Core receiving quantities forming the measurable facts of the view.
• PRICE_T, PRICE_G — Transaction and base price measures.
• SHIPMENT_NUM, INVOICE_NUM, RECEIPT_NUM_INST, BILL_OF_LADING, PACKING_SLIP — Descriptive document attributes.

Common Use Cases and Queries

The view supports receivable analytics such as freight term attribution, supplier delivery performance, and quantity reconciliation across receipt stages. A representative query filtering by freight terms follows:

• SELECT RCV_TXN_PK, FREIGHT_TERMS_FK, QTY_RECEIVED, QTY_ACCEPT FROM POA_EDW_RECEIVING_TXN_FCV WHERE FREIGHT_TERMS_FK IS NOT NULL;
• Aggregating reject quantities by supplier site: SELECT SUPPLIER_SITE_FK, SUM(QTY_REJECT) FROM POA_EDW_RECEIVING_TXN_FCV GROUP BY SUPPLIER_SITE_FK;
• Joining to a date dimension via TXN_DATE_FK to produce period-based receiving trends.

Because the object is documented as not implemented in the reference database, availability should be validated in the target instance before reliance.