Results for “inventory_item_id_new”

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

Overview

MSC_WIP_JOB_COMPONENTS_V is a VALID view owned by the APPS schema within the MSC (Advanced Supply Chain Planning) product of Oracle E-Business Suite 12.1.1 and 12.2.2. It presents requests to add, delete, or modify material associated with existing discrete jobs or repetitive schedules. In practice, the view functions as the outbound XML interface layer: rows represent component-level work-in-process (WIP) material transactions that are consumed by XML outbound processing to communicate planned or requested material changes to external planning and execution systems. Because it is a view rather than a table, no data is stored within it; each query dynamically joins interface and trading-partner data, which keeps the definition aligned with the underlying MSC staging structures.

Underlying Base Objects

The view is defined over the following documented base objects:

• MSC_WIP_JOB_DTLS_INTERFACE (SYNONYM) — the primary source of job/component detail records.
• MSC_TRADING_PARTNERS (SYNONYM) — supplies trading-partner context and organization code derivation.
• MSC_APPS_INSTANCES (SYNONYM) — supplies the application instance identity.
• MSC_ST_UTIL (PACKAGE) — provides the RET_CODE function used for code-to-name resolution.

The FROM clause joins MSC_WIP_JOB_DTLS_INTERFACE to MSC_TRADING_PARTNERS on ORGANIZATION_ID = SR_TP_ID with PARTNER_TYPE = 2, and to MSC_APPS_INSTANCES on SR_INSTANCE_ID = INSTANCE_ID. Critically, the join chain requires MTP.SR_INSTANCE_ID = MJD.SR_INSTANCE_ID and filters MJD.LOAD_TYPE = 2, restricting output to the specific outbound load category for WIP job component changes.

Key Columns

• PARENT_HEADER_ID — identifier of the parent discrete job or repetitive schedule header.
• ORGANIZATION_ID / ORGANIZATION_CODE — the inventory organization; the code is derived via SUBSTR/INSTR on the trading-partner organization code.
• OPERATION_SEQ_NUM / OPERATION_SEQ_ID / OPERATION_SEQ_CODE — operation sequence identification, with the code resolved through MSC_ST_UTIL.RET_CODE ('OPERATION_SEQUENCE_ID', …).
• INVENTORY_ITEM_ID_NEW — the user's search term; the new inventory item being introduced to the job component, with ITEM_NAME_NEW resolved through RET_CODE ('SR_INVENTORY_ITEM_ID', …).
• QUANTITY_PER_ASSEMBLY — component usage per unit of assembly.
• DEPARTMENT_ID / DEPARTMENT_CODE — department where the component is consumed.
• WIP_SUPPLY_TYPE — the supply type of the component line.
• DATE_REQUIRED / REQUIRED_QUANTITY / QUANTITY_ISSUED — demand date and quantities required versus issued.
• UOM_CODE / SUPPLY_SUBINVENTORY / SUPPLY_LOCATOR_ID — unit of measure and supply sourcing location.
• SR_INSTANCE_ID / INSTANCE_CODE — source application instance identifier and its code.

Common Use Cases and Queries

The view is typically queried to audit outbound component-change requests, to troubleshoot why a job component change did not reach the external system, or to resolve an item identifier. A representative query retrieving new-item component requests is:

SELECT parent_header_id, organization_code, inventory_item_id_new, item_name_new, date_required, required_quantity FROM msc_wip_job_components_v WHERE inventory_item_id_new IS NOT NULL;

To isolate changes for a specific organization and job:

SELECT parent_header_id, operation_seq_code, inventory_item_id_new, item_name_new, wip_supply_type, uom_code FROM msc_wip_job_components_v WHERE organization_code = :org AND parent_header_id = :job;

Because the view filters on LOAD_TYPE = 2 and resolves codes dynamically, results reflect only current staging contents at query time; the RET_CODE calls are evaluated per row, so external naming behavior depends on the state of MSC_ST_UTIL and the referenced lookup data.