Search Results batch_status_code

Overview

PMI_BATCH_STATUS is a table owned by the PMI schema within the Oracle Process Manufacturing Intelligence (PMI) product family. It stores batch status aggregations that associate items (products and ingredients) with a plant, warehouse, and reporting period, capturing the batch count observed for a given batch status code in that context. In Oracle EBS 12.1.1 and 12.2.2, the table supports process manufacturing reporting and analysis, allowing planners and analysts to track how many batches of a given item fall under each status across the manufacturing network.

From a dimensional modeling perspective, the documented structure — a composite key over plant, warehouse, fiscal period, item, and batch status, together with a numeric measure (BATCH_COUNT) — suggests this object behaves as a satellite or fact-style table rather than a pure hub or link. The ETRM metadata classifies it heuristically as standalone, meaning no foreign key relationships were mined from the catalog. The batch_status_code column, which the user searched for, is one of the six columns comprising the primary key PK_BATCH_STATUS and serves as the status discriminator within each aggregated row.

Key Information Stored

The table contains 10 documented columns. The most significant are the primary key components and the measure:

• PLANT_CODE — identifies the manufacturing plant associated with the batch aggregation.
• WHSE_CODE — identifies the warehouse within the plant context.
• FISCAL_YEAR — the fiscal year to which the reporting period belongs.
• PERIOD_NUM — the numeric period within the fiscal year.
• PERIOD_NAME — the descriptive name of the period, provided for reporting convenience.
• ITEM_ID — the inventory item (product or ingredient) to which the batch count applies.
• BATCH_STATUS_CODE — the batch status classification being aggregated; this is the column most commonly filtered in user queries.
• CO_CODE — the company (operating unit) code providing organizational context.
• BATCH_COUNT — the aggregated number of batches matching the row's dimensional combination; this is the primary measure.
• LAST_UPDATE_DATE — the timestamp of the most recent modification to the row.

The surrogate primary key is PK_BATCH_STATUS, composed of PLANT_CODE, WHSE_CODE, FISCAL_YEAR, PERIOD_NUM, ITEM_ID, and BATCH_STATUS_CODE. Because the primary key is also the sole documented unique index, it doubles as the business-key candidate for this table; there is no separate system-generated surrogate column.

Common Use Cases and Queries

Typical usage centers on period-over-period batch status reporting — for example, counting how many batches of a specific item were in a given status during a fiscal period, or comparing plant performance across warehouses. A representative query retrieves batch counts filtered by status code and period:

• SELECT plant_code, whse_code, item_id, batch_status_code, batch_count FROM pmi.pmi_batch_status WHERE batch_status_code = :status AND fiscal_year = :year AND period_num = :period;
• Aggregating across items to obtain total batches per status: SELECT batch_status_code, SUM(batch_count) FROM pmi.pmi_batch_status WHERE plant_code = :plant GROUP BY batch_status_code;
• Trend analysis joining PERIOD_NAME for readable labels across FISCAL_YEAR and PERIOD_NUM.

Reporting use cases include operations dashboards, batch yield analysis, status distribution studies, and reconciliation of batch activity against inventory and production records.

Related Objects

The ETRM metadata records no foreign keys, so relationships to other objects are inferred through the shared business columns rather than enforced constraints. The most significant related objects are joined on those columns:

• MTL_SYSTEM_ITEMS_B — joined on ITEM_ID to resolve item descriptions and attributes.
• MTL_PARAMETERS — joined on PLANT_CODE / WHSE_CODE to obtain organization and warehouse names.
• GL_PERIODS or FND_CALENDAR_PERIODS — joined on FISCAL_YEAR and PERIOD_NUM for calendar context.
• PMI_BATCH_STATUS itself is referenced by PMI reporting views and concurrent programs within the Process Manufacturing Intelligence module.
• GME_BATCH_HEADER — the OPM batch header table, whose status values conceptually correspond to BATCH_STATUS_CODE for cross-validation.

Because PMI_BATCH_STATUS is classified as standalone, integration is driven by shared column semantics rather than declarative referential integrity.