Results for “common_bom_sequence_id”

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

Overview

APPS.ICX_EDM_WIP_JOB_V is a project-aware Work in Process (WIP) job view shipped in Oracle E-Business Suite 12.1.1 and 12.2.2 under the ICX (Oracle iProcurement) product. Its documented description is "Project Related WIP Job View," and it is registered in ETRM with a status of VALID. The view presents a flattened, self-contained projection of discrete WIP jobs enriched with project and task context, organization details, assembly item information, descriptive status, and job quantity metrics. Because the SELECT list joins project attributes against each WIP job, the view is typically consumed by reporting, iProcurement e-content, or integration programs that need to display or evaluate project-related manufacturing work without issuing their own multi-table joins.

Underlying Base Objects

The ETRM metadata lists the following referenced base objects for the 12.2.2 definition: HR_GENERAL (package), HR_ORGANIZATION_UNITS (view), HR_SECURITY (package), MFG_LOOKUPS (view), MRP_GET_PROJECT (package), MTL_PARAMETERS (synonym), MTL_SYSTEM_ITEMS_KFV (synonym), WIP_DISCRETE_JOBS (synonym), and WIP_ENTITIES (synonym). The view text confirms these relationships: WIP_ENTITIES supplies the entity name (WIP_JOB_NAME), and WIP_DISCRETE_JOBS supplies the job details, quantities, project, and task identifiers. HR_ORGANIZATION_UNITS and MTL_PARAMETERS provide the organization name and code, while MTL_SYSTEM_ITEMS_KFV resolves the assembly's concatenated item segments and description. MFG_LOOKUPS is outer-joined on lookup type WIP_JOB_STATUS to translate STATUS_TYPE into a meaning. MRP_GET_PROJECT.PROJECT and MRP_GET_PROJECT.TASK resolve the project and task numbers, and the HR_SECURITY and HR_GENERAL packages govern organization security and related HR utility logic.

Key Columns

The projected columns map directly to WIP execution semantics and are relevant to the user's search term, QUANTITY_SCRAPPED.

• PROJECT_ID / TASK_ID / PROJECT_NUMBER / TASK_NUMBER — Project and task identifiers returned by MRP_GET_PROJECT.PROJECT and MRP_GET_PROJECT.TASK, qualifying each job to a project.
• WIP_JOB / WIP_JOB_NAME, JOB_DESCRIPTION, CLASS, STATUS — The WIP entity name, description, class code, and the decoded job status from MFG_LOOKUPS.
• ORGANIZATION_CODE / ORGANIZATION_NAME — Organization identification from MTL_PARAMETERS and HR_ORGANIZATION_UNITS.
• ASSEMBLY / ASSEMBLY_DESCRIPTION / PRIMARY_UOM — The primary assembly's concatenated segments, description, and unit of measure from MTL_SYSTEM_ITEMS_KFV.
• START_DATE, START_QUANTITY, COMPLETION_DATE — Scheduled start/completion dates and the job's start quantity.
• QUANTITY_COMPLETED — NVL(WDJ.QUANTITY_COMPLETED, 0), the quantity completed to date.
• QUANTITY_SCRAPPED — NVL(WDJ.QUANTITY_SCRAPPED, 0), the quantity scrapped and reported against the job. This is the column most directly matched by the search term.
• QUANTITY_REMAINING — Computed as NVL(START_QUANTITY - QUANTITY_COMPLETED - QUANTITY_SCRAPPED, 0), showing the outstanding quantity still to be produced or accounted for.
• WIP_JOB_ID / ORGANIZATION_ID / PRIMARY_ITEM_ID / COMMON_BOM_SEQUENCE_ID — Keys linking back to WIP and inventory entities.

Common Use Cases and Queries

The view is used to report project-linked discrete WIP job status and yield performance, to monitor scrap against project jobs, and to feed iProcurement or integration displays that require assembly and organization context. A representative query targeting scrapped quantities is:

• SELECT project_number, task_number, wip_job, assembly, status, start_quantity, quantity_completed, quantity_scrapped, quantity_remaining FROM apps.icx_edm_wip_job_v WHERE quantity_scrapped > 0 ORDER BY organization_code, wip_job;
• SELECT organization_code, wip_job, quantity_scrapped, quantity_remaining FROM apps.icx_edm_wip_job_v WHERE project_id = :project_id AND task_id = :task_id;

Because the definition uses SELECT DISTINCT, callers should be aware that duplicate suppression is applied across the full column list; filtering on organization_id and project identifiers is recommended for performance and to scope results to the intended reporting context.