Results for “isc_dbi_full_pegging_f”

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

Overview

ISC_DBI_FULL_PEGGING_F is a table owned by the ISC schema within the Oracle E-Business Suite Supply Chain Intelligence module. It functions as a pre-aggregated or staging structure that supports full pegging analysis in Oracle Advanced Supply Chain Planning (ASCP). Pegging is the process by which Oracle planning engines trace a supply order back through intermediate demand and supply nodes to its originating independent demand. The results of that traversal are materialized for high-volume reporting and dashboard consumption through this table.

The table is documented as VALID under the ISC - Supply Chain Intelligence product umbrella and exists in both EBS 12.1.1 and 12.2.2. It carries a reference constraint (pegging_id) to MRP_FULL_PEGGING, which is the canonical planning pegging repository. In Data Vault terms, the heuristic classification returned from the foreign key structure is standalone; this suggests a modeling choice that treats ISC_DBI_FULL_PEGGING_F as neither a classic hub nor a pure link, but rather a denormalized reporting satellite anchored indirectly to planning pegging data.

Key Information Stored

The table contains ten documented columns. The most significant of these include:

• PLAN_ID — Identifies the ASCP plan under which the pegging analysis was executed. It is a primary filter for isolating one planning run's output from another.
• PEGGING_ID — The pegging identifier that links back to MRP_FULL_PEGGING. This is the documented foreign key and the most important business-key candidate for joining back to native planning pegging.
• DEMAND_ID — The originating demand entity, typically a sales order line, forecast, or MDS entry, to which supply is ultimately pegged.
• END_PEGGING_ID — The terminal pegging node, often the independent demand end-point of the pegging chain.
• TRANSACTION_ID — A reference to the transaction that triggered the pegging relationship, useful for traceability to the source transaction.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns used to track who inserted or modified the record and when.

No documented surrogate primary key or unique index is provided in the metadata, so the combination of PLAN_ID and PEGGING_ID is the practical business-key candidate for row uniqueness.

Common Use Cases and Queries

The primary use case is full-pegging reporting in Supply Chain Intelligence. Analysts use this table to answer which supplies satisfy which demands across an ASCP plan. A typical query joins the table to MRP_FULL_PEGGING to resolve pegging detail:

SELECT f.PLAN_ID, f.PEGGING_ID, f.DEMAND_ID, f.END_PEGGING_ID, f.TRANSACTION_ID FROM ISC.ISC_DBI_FULL_PEGGING_F f, MRP.MRP_FULL_PEGGING m WHERE f.PEGGING_ID = m.PEGGING_ID AND f.PLAN_ID = :plan_id;

Other common patterns include end-to-end supply chain visibility dashboards, demand-versus-supply reconciliation, exception reporting where peg chains are broken or incomplete, and audit trails showing how a specific TRANSACTION_ID influenced planning outcomes. Because the table carries a PLAN_ID filter, plan-to-plan comparison is a frequent reporting scenario.

Related Objects

• MRP_FULL_PEGGING — The parent reference via PEGGING_ID; holds the full pegging detail that ISC_DBI_FULL_PEGGING_F denormalizes for reporting.
• MRP_SYSTEM_ITEMS / MRP_ITEM_SCHEDULES — Frequently joined for item-level pegging context.
• MSC_PLANS — Provides plan definition for PLAN_ID lookups.
• MRP_SCHEDULING_SUPPLY / MRP_SCHEDULING_DEMAND — Supply and demand scheduling tables used to enrich pegging chains.
• ISC_DBI_% views and DBI collections — Supply Chain Intelligence materialized structures that consume this table for dashboard presentation.