Results for “wip_operation_seq_num”

50+ results




Overview
Explore in AI Chat

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

Overview

The POS_ASN_WIP_JOB_V view is a reporting and integration object owned by the APPS schema within Oracle E-Business Suite, classified under the ICX product family (Oracle iProcurement). Its status is documented as VALID in ETRM 12.1.1 / 12.2.2. The view is designed to surface Work in Process (WIP) job context for purchase order distributions that have been associated with a discrete manufacturing job — specifically, job and operation details needed by iProcurement and related supply chain flows to describe the manufacturing target of a distribution. The view explicitly serves as a denormalised presentation layer, joining distribution records to WIP entity and line data and concatenating those elements into a single descriptive string. By exposing columns such as WIP_OPERATION_SEQ_NUM, it allows callers to distinguish which routing operation within a job a given distribution is intended for, a requirement that arises when components are issued, backflushed, or consumed at the operation level rather than the job level.

Underlying Base Objects

The view text is defined over three base objects, all referenced through APPS synonyms:

  • PO_DISTRIBUTIONS_ALL — the primary driving table, aliased POD. Filtering and joins originate here; the view is restricted to distributions that carry a non-null WIP_ENTITY_ID, ensuring only job-related distributions are returned.
  • WIP_ENTITIES — aliased WIPE, joined on POD.WIP_ENTITY_ID = WIPE.WIP_ENTITY_ID. This supplies the human-readable WIP_ENTITY_NAME (the job or work order name).
  • WIP_LINES — aliased WIPL, joined with an outer join on POD.WIP_LINE_ID = WIPL.LINE_ID (+). This supplies the assembly LINE_CODE. The outer join ensures distributions without a matching line still appear, with the line code resolving to NULL.

The concatenated expression WIPE.WIP_ENTITY_NAME || '-' || WIPL.LINE_CODE || '-' || POD.WIP_OPERATION_SEQ_NUM, trimmed of leading spaces, produces the derived JOB_INFO column.

Key Columns

  • JOB_INFO — derived text combining job name, assembly line code, and operation sequence number, delimited by hyphens. Provides a compact, display-ready identifier.
  • PO_DISTRIBUTION_ID — the unique identifier of the purchase order distribution, enabling joins back to PO distribution detail.
  • WIP_ENTITY_ID — identifier of the WIP job (WIP_ENTITIES) to which the distribution relates.
  • WIP_LINE_ID — identifier of the WIP line (assembly) within the job.
  • WIP_OPERATION_SEQ_NUM — the routing operation sequence number, indicating the specific operation within the job's routing at which the distribution applies.
  • LINE_LOCATION_ID — reference to the shipment/inventory location associated with the distribution line.

Common Use Cases and Queries

Typical usage includes iProcurement requisition and receipt processing for job-linked distributions, reporting on job-level demand against purchase documents, and integration extracts that must resolve a distribution to its WIP job and operation. The following query retrieves distribution-to-job mapping for a given job:

SELECT job_info, po_distribution_id, wip_entity_id, wip_line_id, wip_operation_seq_num, line_location_id FROM appS.pos_asn_wip_job_v WHERE wip_entity_id = :p_wip_entity_id ORDER BY wip_operation_seq_num;

To resolve a single distribution's job context:

SELECT job_info, wip_operation_seq_num FROM apps.pos_asn_wip_job_v WHERE po_distribution_id = :p_distribution_id;

Because the view filters on POD.WIP_ENTITY_ID IS NOT NULL, only job-associated distributions are returned; non-WIP distributions are excluded by design. Query performance depends on the indexing of WIP_ENTITY_ID and PO_DISTRIBUTION_ID on the underlying base tables, and callers should supply these predicates wherever possible.