Results for “consigned_code”

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

Overview

POA_PQC_BS_J_MV is a materialized view owned by the APPS schema in Oracle E-Business Suite. It is catalogued under the FND – Application Object Library product family and carries a VALID status in both the 12.1.1 and 12.2.2 releases examined through the ETRM repository. Although the object is registered in the Applications Object Library namespace, its column inventory is unmistakably procurement-centric: the table aggregates purchasing quantities, purchase amounts, supplier reference data, commodity classifications, and a hierarchical date dimension (day, week, period, quarter, and year identifiers). The name suffix _MV confirms that the underlying object is a materialized view rather than a base transactional table, populated by a refresh process from the tables listed under its foreign-key schema.

The heuristic Data Vault classification mined from the documented FK structure is standalone. This suggests, as a modelling recommendation, that the object does not sit at the centre of a set of parent-child relationships within the source repository; instead it behaves as a self-contained aggregate. A standalone classification is consistent with a summary or reporting view that denormalises reference identifiers from several dimension tables (commodity, company, release) for read-optimised access, rather than serving as a link between transactional entities.

Key Information Stored

The documented physical schema for 12.1.1 exposes 35 columns. The most operationally significant are grouped below. No surrogate primary key is documented with a formal constraint, and no unique index columns are identified in the metadata, so any candidate key must be inferred. The leading identifier columns — FRID, CRID, COMRID, and MRID — appear first in the column list and are the most probable internal key components for the refresh and join logic of the underlying ETL.

• Organisational keys: ORG_ID, SHIP_TO_ORG_ID, and COMPANY_ID partition purchasing activity by operating unit, shipping location, and legal entity.
• Procurement references: PO_HEADER_ID, PO_LINE_ID, PO_RELEASE_ID, PO_DISTRIBUTION_ID, and LINE_LOCATION_ID trace each row back to the standard Purchasing document hierarchy.
• Supplier and item detail: SUPPLIER_ID, SUPPLIER_SITE_ID, CATEGORY_ID, PO_ITEM_ID, BUYER_ID, COMMODITY_ID, and BASE_UOM describe the trading relationship and the transacted item.
• Measures: QUANTITY, PURCHASE_AMT_B, PURCHASE_AMT_G, and PURCHASE_AMT_SG provide the base, group, and subgroup purchase amount figures that drive reporting.
• Date dimension columns: DAY_ID, WEEK_ID, ENT_PERIOD_ID, ENT_QTR_ID, ENT_YEAR_ID, and P_ENT_YEAR_ID support period-over-period aggregation.
• Classification flags: APPROVED_DATE, CONSIGNED_CODE, ORDER_TYPE, COMPLEX_WORK_FLAG, COST_CENTER_ID, and GLOBAL_CUR_CONV_RATE add status, currency-conversion, and organisational attribution.

Common Use Cases and Queries

The object is best suited to spend analysis, commodity-based procurement reporting, and period-trend dashboards. A typical query aggregates purchase amounts by commodity and period for a given operating unit:

• Commodity spend: SELECT COMMODITY_ID, ENT_PERIOD_ID, SUM(PURCHASE_AMT_B) FROM POA_PQC_BS_J_MV WHERE ORG_ID = :org GROUP BY COMMODITY_ID, ENT_PERIOD_ID;
• Supplier scorecards: aggregate QUANTITY and PURCHASE_AMT_G by SUPPLIER_ID and ENT_QTR_ID to compare suppliers across quarters.
• Consigned versus owned analysis: filter on CONSIGNED_CODE to separate consignment activity from standard purchasing.
• Document drill-down: join back to PO_HEADERS_ALL on PO_HEADER_ID and to PO_LINES_ALL on PO_LINE_ID to retrieve document numbers and descriptions.
• Complex-work monitoring: use COMPLEX_WORK_FLAG and ORDER_TYPE to isolate non-standard procurement routes.

Because the object is a materialized view, results reflect the last refresh; reporting should account for staleness in near-real-time scenarios.

Related Objects

The documented foreign-key relationships anchor this object to three reference tables, and normal EBS purchasing patterns connect it to the wider procurement schema.

• PO_COMMODITIES_B — joined via COMMODITY_ID; supplies the commodity description and category hierarchy.
• PN_COMPANIES_ALL — joined via COMPANY_ID; provides legal entity and company attributes.
• PO_RELEASES_ALL — joined via PO_RELEASE_ID; identifies the blanket-release document behind the spend.
• PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL — reached through PO_HEADER_ID, PO_LINE_ID, and LINE_LOCATION_ID.
• PO_DISTRIBUTIONS_ALL — reached through PO_DISTRIBUTION_ID for accounting distribution detail.
• PO_VENDORS / AP_SUPPLIERS — supplier master accessed via SUPPLIER_ID and SUPPLIER_SITE_ID.

No PL/SQL APIs are documented against this object; it should be treated as a read-only reporting artefact within the APPS schema.