Search Results batch_rsrc_pk

Overview

PMI_EDW_BTCH_RSRC_F_IV is an interface (denoted by the "_IV" suffix) view within the Oracle Process Manufacturing Intelligence (PMI) product family, the analytical and data-warehouse-facing layer of Oracle E-Business Suite Process Manufacturing (OPM). The view exposes batch resource transaction and utilization facts in a denormalized, star-schema-oriented form suitable for extraction, transformation, and load (ETL) into the PMI enterprise data warehouse. It is not a transactional entry object; rather, it serves reporting and integration consumers, supplying plan-versus-actual resource consumption data at the batch step level.

Per the ETRM metadata documented for 12.2.2, this view is listed as "Not implemented in this database," meaning the definition is shipped as part of the PMI repository but the view object is not deployed by default in the referenced environment. Its owning schema and referenced base objects are not separately documented in the metadata provided. Functionally, the view layers a computed OPERATION_CODE column (aliased from USER_ATTRIBUTE15) and a ROWID-derived ROW_ID pseudocolumn over the stored resource fact table PMI_EDW_BTCH_RSRC_F, making surrogate and auditing information available to downstream warehouse processes.

Underlying Base Objects

The view definition, as documented in the ETRM metadata, is a straightforward projection over a single base object: PMI_EDW_BTCH_RSRC_F. Every column in the view originates from that table, with one column transformation applied at view level:

• OPERATION_CODE is exposed as an alias of USER_ATTRIBUTE15.
• ROW_ID is exposed as the ROWID pseudocolumn of the underlying fact row.

No additional joins, unions, or aggregations are recorded in the documented view text. As a "F" (fact) table suffix object, PMI_EDW_BTCH_RSRC_F is populated by the PMI batch-load and warehouse population programs, which stage OPM batch resource records and resolve dimension surrogate keys prior to insertion. Because the metadata does not document referential constraints, consumers should treat the various FK_KEY columns (BATCH_STATUS_FK_KEY, ITEM_FK_KEY, OPM_ORG_FK_KEY, RESOURCE_FK_KEY, TIME_FK_KEY, and the USER_FKn_KEY columns) as soft references resolved within the PMI star schema rather than enforced database foreign keys.

Key Columns

The view exposes nearly fifty columns reflecting the resource dimension of batch execution. The most significant include:

• BATCH_RSRC_PK / BATCH_RSRC_PK_KEY – Source primary key and its warehouse surrogate equivalent identifying the batch resource record.
• BATCH_NO, BATCH_STEP_NO, BATCHSTEPLINE_ID – Batch, batch step, and step-line identifiers providing the operational grain of the fact.
• ACTIVITY – The resource activity associated with the batch step.
• RESOURCE_FK_KEY, PRIM_RSRC_IND – Reference to the resource dimension and a flag indicating the primary resource for the step.
• PLAN_START_DATE, PLAN_CMPLT_DATE, PLAN_RSRC_COUNT, PLAN_RSRC_QTY, PLAN_RSRC_USAGE – Planned resource scheduling and quantities.
• ACTUAL_START_DATE, ACTUAL_CMPLT_DATE, ACTUAL_RSRC_COUNT, ACTUAL_RSRC_QTY, ACTUAL_RSRC_USAGE – Corresponding actual execution figures, supporting plan-versus-actual variance analysis.
• USAGE_UOM, SCALE_TYPE – Unit of measure and scaling basis for resource usage.
• OPM_ORG_FK_KEY, ITEM_FK_KEY, TIME_FK_KEY, BATCH_STATUS_FK_KEY – Conformed dimension keys for organization, item, time, and batch status.
• USER_ATTRIBUTE1–15, USER_FK1–5_KEY, USER_MEASURE1–5 – Extensible descriptive, key, and measure columns for customer-specific extensions, with USER_ATTRIBUTE15 repurposed as OPERATION_CODE.

Common Use Cases and Queries

Typical consumers include PMI batch analytics dashboards, resource utilization extracts, and OPM-to-warehouse ETL jobs. A representative query for resource consumption variance is:

SELECT batch_no,
       batch_step_no,
       resource_fk_key,
       plan_rsrc_qty,
       actual_rsrc_qty,
       actual_rsrc_usage,
       usage_uom
  FROM pmi_edw_btch_rsrc_f_iv
 WHERE opm_org_fk_key = :org_key
   AND actual_start_date >= :from_date;

Because the view is documented as not implemented in the database, DBAs must confirm its existence — and the existence of PMI_EDW_BTCH_RSRC_F — before use, and may need to deploy the view manually where PMI warehouse population has not been configured.