Search Results no_of_samples_taken

Overview

The view PMI_EDW_BTCH_DTL_F_IV is a Process Manufacturing Intelligence (PMI) database object delivered as part of the Oracle E-Business Suite Process Manufacturing (OPM) reporting and integration layer. It is classified within the ETRM metadata repository as an obsolete PMI object, and it is documented as not implemented in the reference database. The suffix _IV denotes an Integration View, a construct used by the PMI/EDW (Enterprise Data Warehouse) extraction mechanism to expose batch detail fact data in a flattened, denormalized form suitable for downstream analytical consumption.

The view is defined over the base object PMI_EDW_BTCH_DTL_F (Batch Detail Fact). It presents one row per batch detail fact record, combining execution-related attributes (actual start, completion, yield, and ingredient values) with planning-related attributes (planned start, completion, yield) alongside cost method, formula, routing, item, and organization foreign keys. The view also exposes fifteen user attribute columns and a series of user foreign key and measure columns, providing extensibility for site-specific batch data. Its primary role is to feed PMI analytics and external data warehouse loads for process manufacturing batch analysis in EBS 12.1.1 and 12.2.2.

Underlying Base Objects

Per the documented ETRM metadata, the only referenced base object is PMI_EDW_BTCH_DTL_F. The view text is a straightforward projection: each column of the view maps directly to a same-named column of the base fact table, with two notable derivations.

• ROW_ID is derived from the base table's ROWID pseudo-column, providing a physical row identifier for the fact record.
• OPERATION_CODE is an alias of USER_ATTRIBUTE1, repurposing the first user attribute column as an operation code indicator for the extract.

No additional joins, filters, or aggregations are documented. Because the base object is an EDW fact table rather than a transactional OPM table, the view does not participate in the standard OPM online transaction path; it exists purely as a reporting and extraction interface.

Key Columns

The columns of principal analytical interest include the following:

• Batch identifiers: BATCH_DETAIL_PK, BATCH_DETAIL_PK_KEY, and BATCH_NO uniquely identify the batch detail record and the batch number.
• Dates: ACTUAL_START_DATE, ACTUAL_CMPLT_DATE, PLAN_START_DATE, and PLAN_CMPLT_DATE support variance and cycle-time analysis.
• Yield and ingredient metrics: ACTUAL_YIELD_QTY / ACTUAL_YIELD_VALUE, PLAN_YIELD_QTY / PLAN_YIELD_VALUE, and ACTUAL_ING_VALUE / PLAN_ING_VALUE provide the core planning-versus-actual comparisons.
• STD_QTY and STD_TIME: the standard quantity and standard time associated with the batch detail, used for standard-cost and efficiency measurement. STD_QTY is the column most directly relevant to the search term std_qty.
• Sample counts: NO_OF_SAMPLES_TAKEN, NO_OF_SAMPLES_COMPLETED, NO_OF_SAMPLES_PASSED, and NO_OF_SAMPLES_ADJUSTED support quality sampling analysis.
• Keys: FORMULA_FK_KEY, ROUTING_FK_KEY, ITEM_FK_KEY, OPM_ORG_FK_KEY, TIME_FK_KEY, and BATCH_STATUS_FK_KEY link the fact to PMI dimensions.
• Extensibility: USER_ATTRIBUTE1 through USER_ATTRIBUTE15, USER_FK1_KEY through USER_FK5_KEY, and USER_MEASURE1 through USER_MEASURE5.

Common Use Cases and Queries

Typical usage involves extracting batch performance metrics for the EDW, and performing standard-versus-actual variance reporting. The following query illustrates a standard batch yield and standard quantity comparison:

SELECT BATCH_NO,
       OPM_ORG_FK_KEY,
       ITEM_FK_KEY,
       ACTUAL_START_DATE,
       ACTUAL_CMPLT_DATE,
       STD_QTY,
       STD_TIME,
       ACTUAL_YIELD_QTY,
       PLAN_YIELD_QTY,
       ACTUAL_YIELD_VALUE,
       BASE_CURRENCY
FROM   PMI_EDW_BTCH_DTL_F_IV
WHERE  ACTUAL_CMPLT_DATE >= :from_date
AND    ACTUAL_CMPLT_DATE <  :to_date
ORDER  BY OPM_ORG_FK_KEY, BATCH_NO;

Additional scenarios include aggregating STD_QTY against ACTUAL_YIELD_QTY by organization to measure batch efficiency, joining FORMULA_FK_KEY and ROUTING_FK_KEY to PMI dimension views for recipe-level reporting, and filtering on OPERATION_CODE (the aliased USER_ATTRIBUTE1) to isolate operation types during extraction. Because the object is obsolete and not implemented in the current database, these queries are relevant primarily for legacy PMI/EDW environments or migration assessment.