Search Results opi_edw_margin_perd_ilog

Overview

OPI_EDW_MARGIN_PERD_ILOG is a table owned by the OPI schema within the Oracle E-Business Suite Operations Intelligence module. Operations Intelligence provides the analytical and data-warehouse layer that extracts, transforms, and stages operational data from EBS transactional systems for margin, cost, and profitability reporting. The physical object documented here for ETRM 12.1.1 and applicable to 12.2.2 is a lightweight staging or interface log table, containing only two documented columns: ROW_ID and STATUS.

From a modeling perspective, the metadata's heuristic Data Vault classification identifies this object as standalone. This classification suggests that the table is not a conventional hub, link, or satellite within a normalized Data Vault model, but rather a self-contained control or status-tracking structure. Its narrow column set and single foreign key relationship support the interpretation that it functions as an auxiliary or orchestration artifact rather than a core fact or dimension table. Note that this classification is a mined heuristic and should be treated as a modeling suggestion rather than an authoritative declaration of design intent.

Key Information Stored

The documented physical schema comprises only two columns, both of which are significant:

• ROW_ID — The surrogate primary key of the table. It is the sole column participating in the unique index OPI_EDW_MARGIN_PERD_ILOG_U1, making it both the technical identifier and the single documented business-key candidate. ROW_ID also carries a foreign key reference to CS_SYSTEMS_ALL_B_TEMP, indicating that each row is anchored to a system or source record defined in that related table.
• STATUS — A status indicator that records the processing or lifecycle state of the associated ROW_ID. In OPI/EDW staging contexts, such a column typically tracks phases such as loaded, validated, processed, or failed, supporting restartability and error diagnostics.

No additional columns are documented in the ETRM metadata for this object. The absence of descriptive attributes, timestamps, or measure columns reinforces the conclusion that this is a control-oriented structure rather than an analytical data store.

Common Use Cases and Queries

Because the table holds only an identifier and a status flag, its practical use centers on processing control and reconciliation. Typical scenarios include identifying records that remain in an unprocessed state, verifying that all expected ROW_ID values have advanced to a terminal status, and diagnosing stalled or failed loads in the margin-by-period interface pipeline.

A representative query to list outstanding items:

• SELECT ROW_ID, STATUS FROM OPI.OPI_EDW_MARGIN_PERD_ILOG WHERE STATUS <> 'PROCESSED';

A reconciliation pattern that joins to the referenced system table:

• SELECT i.ROW_ID, i.STATUS, s.* FROM OPI.OPI_EDW_MARGIN_PERD_ILOG i, CS_SYSTEMS_ALL_B_TEMP s WHERE i.ROW_ID = s.ROW_ID;

Aggregate status counts are also useful during period-close processing to confirm that the interface log has drained completely before downstream margin calculations execute.

Related Objects

The ETRM metadata documents a single foreign key relationship from this table. The most significant related object is therefore:

• CS_SYSTEMS_ALL_B_TEMP — referenced by OPI_EDW_MARGIN_PERD_ILOG.ROW_ID. This join column links each interface log row to a corresponding system record, and it is the primary integration point for this table.

Beyond the documented relationship, the table's narrow structure and OPI ownership suggest it participates in the broader Operations Intelligence margin-by-period data flow, depending on OPI_EDW margin fact and period dimension objects for context. However, since the ETRM metadata provides no further FK or view dependencies, these associations should be verified against the actual database catalog before use in production queries.