Results for “last_unit_completion_date”

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

Overview

The MSC_WIP_JOB_OPERATIONS_V view is an Advanced Supply Chain Planning (MSC) reporting object residing in the APPS schema. It exposes operation-level detail for existing discrete jobs and repetitive schedules, drawing its content from the work-in-process interface layer used by the MSC module. The view's stated purpose is to supply operation information in an XML outbound context, making it a component of the outbound integration flow that transmits WIP job operation data to external planning or execution systems.

The object is a VIEW, carries VALID status, and is documented under ETRM 12.2.2 with an equivalent presence in 12.1.1. Because it is a view rather than a table, it stores no data of its own; it projects and transforms columns from the underlying WIP job details interface and joins them to trading partner and application instance metadata. This design supports the XML outbound requirement of associating each operation record with the correct source instance and trading partner context.

Underlying Base Objects

The view is defined over four documented base objects:

• MSC_WIP_JOB_DTLS_INTERFACE (synonym) — the primary source of operation records, supplying header, operation sequence, and date columns.
• MSC_TRADING_PARTNERS (synonym) — joined to resolve the organization as a trading partner where PARTNER_TYPE = 3.
• MSC_APPS_INSTANCES (synonym) — joined on SR_INSTANCE_ID to provide the instance code.
• MSC_ST_UTIL (package) — invoked via the function RET_CODE to resolve the operation sequence code.

Internally, the view aliases MSC_WIP_JOB_DTLS_INTERFACE as MJD, MSC_TRADING_PARTNERS as MTP, and MSC_APPS_INSTANCES as MAI. The joins require MJD.ORGANIZATION_ID = MTP.SR_TP_ID, MTP.SR_INSTANCE_ID = MJD.SR_INSTANCE_ID, and MJD.SR_INSTANCE_ID = MAI.INSTANCE_ID, with the filters MTP.PARTNER_TYPE = 3 and MJD.LOAD_TYPE = 3 applied.

Key Columns

• PARENT_HEADER_ID — identifier of the parent job or schedule header to which the operation belongs.
• ORGANIZATION_ID — inventory organization identifier for the job.
• ORGANIZATION_CODE — organization code derived by substringing MTP.ORGANIZATION_CODE after the colon delimiter.
• OPERATION_SEQ_NUM — numeric operation sequence from the interface.
• OPERATION_SEQ_ID — surrogate key for the operation sequence.
• OPERATION_SEQ_CODE — the operation sequence code. When OPERATION_SEQ_ID is null the value is null; otherwise it returns the RET_CODE result, defaulting to OPERATION_SEQ_NUM when no code is resolved. This is the column users target when searching operation_seq_code.
• FIRST_UNIT_START_DATE / FIRST_UNIT_COMPLETION_DATE — start and completion dates for the first unit.
• LAST_UNIT_START_DATE / LAST_UNIT_COMPLETION_DATE — start and completion dates for the last unit.
• SR_INSTANCE_ID — source application instance identifier.
• INSTANCE_CODE — instance code from MSC_APPS_INSTANCES.

Common Use Cases and Queries

Typical scenarios include validating outbound XML payloads, reconciling operation schedules against source jobs, and reporting operation timelines by organization and instance. A representative query filtering on the searched column follows:

• SELECT PARENT_HEADER_ID, ORGANIZATION_CODE, OPERATION_SEQ_NUM, OPERATION_SEQ_CODE, FIRST_UNIT_START_DATE, LAST_UNIT_COMPLETION_DATE FROM MSC_WIP_JOB_OPERATIONS_V WHERE OPERATION_SEQ_CODE = :operation_seq_code;
• SELECT ORGANIZATION_CODE, COUNT(*) FROM MSC_WIP_JOB_OPERATIONS_V GROUP BY ORGANIZATION_CODE;
• SELECT * FROM MSC_WIP_JOB_OPERATIONS_V WHERE SR_INSTANCE_ID = :instance_id ORDER BY PARENT_HEADER_ID, OPERATION_SEQ_NUM;

Because OPERATION_SEQ_CODE derives from MSC_ST_UTIL.RET_CODE with a fallback to OPERATION_SEQ_NUM, users should account for null or fallback values when filtering. The view remains read-only and is intended for query and integration consumption rather than direct DML.