Search Results purchasing_cost_g1

Overview

ISC.ISC_DBI_SUPPLIES_SNAPSHOTS is a snapshot fact table within the Oracle E-Business Suite 12.1.1 and 12.2.2 environment owned by the ISC schema (Supply Chain Intelligence / Daily Business Intelligence). The table stores point-in-time captures of supplier sourcing and purchasing cost metrics, keyed to inventory items, organizations, suppliers, and reporting periods. It is part of the Oracle DBI (Daily Business Intelligence) infrastructure that feeds operational analytics for procurement and supply base performance, and its content is materialized into the ISC_DBI_PM_0000_MV materialized view, which surfaces these metrics to the DBI dashboards. The table is documented as an Oracle Internal Use Only object; Oracle does not support direct data access except through standard Oracle Applications programs.

From a Data Vault modeling perspective, the metadata presents this object as standalone, with no foreign key relationships to other tables and no dependent child tables recorded. Heuristically, the table is best understood as a satellite — a descriptive snapshot of measured purchasing cost values attached to a snapshot context (source item, organization, supplier, and period). The single documented FK-style dependency, SNAPSHOT_ID referencing AHL_SNAPSHOTS, reinforces the satellite interpretation, since SNAPSHOT_ID serves as the link back to the parent snapshot definition.

Key Information Stored

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

• SNAPSHOT_ID (NUMBER) — The surrogate/primary key of the row and the identifier of the snapshot run that produced the record. It is the FK to AHL_SNAPSHOTS.
• SR_INVENTORY_ITEM_ID (NUMBER) — The sourced inventory item identifier, a primary business-key candidate.
• ORGANIZATION_ID (NUMBER) — The inventory organization context in which the item and supplier relationship is measured, also a business-key candidate.
• SR_SUPPLIER_ID (NUMBER) — The sourced supplier identifier, forming the third business-key dimension.
• PERIOD_TYPE_ID (NUMBER) — The reporting period type (e.g., day, week, month) that defines the aggregation grain.
• START_DATE (DATE) — The effective start date of the snapshot period, used for time-trend reporting.
• PURCHASING_COST (NUMBER) — Primary purchasing cost measure in the ledger currency.
• PURCHASING_COST_G (NUMBER) — Purchasing cost expressed in the global (primary reporting) currency, enabling cross-organization comparison.
• PURCHASING_COST_G1 (NUMBER) — Purchasing cost in the secondary global currency.
• UOM_CODE (VARCHAR2) — Unit of measure associated with the cost figures.

The composite of SNAPSHOT_ID, SR_INVENTORY_ITEM_ID, ORGANIZATION_ID, SR_SUPPLIER_ID, PERIOD_TYPE_ID, and START_DATE constitutes the effective unique key for a snapshot row.

Common Use Cases and Queries

The table supports supply-base spend analysis, supplier price trending, and purchasing cost variance reporting across periods. A typical query retrieves the purchasing cost in the global currency for a specific supplier and item over time:

• Supplier spend ranking by period: SELECT SR_SUPPLIER_ID, PERIOD_TYPE_ID, SUM(PURCHASING_COST_G) FROM ISC.ISC_DBI_SUPPLIES_SNAPSHOTS GROUP BY SR_SUPPLIER_ID, PERIOD_TYPE_ID;
• Item-level cost trend: filter on SR_INVENTORY_ITEM_ID and ORGANIZATION_ID, order by START_DATE, and project PURCHASING_COST and PURCHASING_COST_G.
• Currency comparison: compare PURCHASING_COST_G against PURCHASING_COST_G1 to assess secondary-currency exposure.
• Snapshot audit: join back to AHL_SNAPSHOTS on SNAPSHOT_ID to identify snapshot run dates, refining the period dimension.

Because the underlying object is internal, reporting should preferentially target the materialized view ISC_DBI_PM_0000_MV rather than the base table.

Related Objects

• AHL_SNAPSHOTS — Referenced via SNAPSHOT_ID; defines the snapshot header and run metadata.
• ISC_DBI_PM_0000_MV — Materialized view that consumes ISC_DBI_SUPPLIES_SNAPSHOTS and exposes purchasing metrics to DBI dashboards.
• ISC_DBI_SUPPLIES_SNAPSHOTS — Self-referenced within the dependency listing, indicating internal snapshot lineage.
• APPS schema synonyms — Provide the supported access path to these objects for standard applications programs.

No other FK-referenced base tables are documented, so joins beyond SNAPSHOT_ID and the materialized view should be validated against the deployed schema before use.