Results for “so_header_id”

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

Overview

ICX_ENG_WEB_SCHEDULE_SO_V is a database view belonging to the Oracle iProcurement (ICX) product family within Oracle E-Business Suite. It functions as a join layer that correlates engineering web-schedule data with open sales order lines. The view combines the item revision context exposed by ENG_WEB_SCHEDULE_V with the sales order line context exposed by SO_LINES (the base table underlying OE_ORDER_LINES_ALL), producing a unique correlation of revised item, inventory organization, and sales order header.

Its specific purpose is to identify, for a given revised inventory item and organization, the sales order headers that reference that item through open lines. This is relevant to iProcurement and related engineering/order visibility flows, where a user or concurrent process needs to know whether a revised item is actively carried on open sales orders before presenting scheduling or sourcing information. The view is read-only reference metadata; ETRM documentation records it as "Not implemented in this database" in the source environment, meaning the definition is catalogued from Oracle's shipped metadata rather than an editable business object.

Underlying Base Objects

The view is defined over two objects, per the documented view text:

• ENG_WEB_SCHEDULE_V — an engineering schedule view supplying the revised item identifier (REVISED_ITEM_ID) and organization (ORGANIZATION_ID).
• SO_LINES — the sales order lines base table, supplying the sales order HEADER_ID and the open-flag filter.

The join condition equates ENG.REVISED_ITEM_ID with SOL.INVENTORY_ITEM_ID, ensuring only sales order lines whose inventory item matches the engineering revised item are returned. The predicate SOL.OPEN_FLAG = 'Y' restricts output to lines that are still open, excluding closed or cancelled order lines. No additional base objects are documented for this view in ETRM 12.2.2, and no owner is recorded in the catalogued metadata.

Key Columns

Three columns are exposed:

• ITEM_ID — corresponds to ENG.REVISED_ITEM_ID, the identifier of the revised inventory item from the engineering schedule view. This is the join key against SO_LINES.INVENTORY_ITEM_ID.
• ORGANIZATION_ID — the inventory organization from ENG_WEB_SCHEDULE_V, scoping the item to a specific operating unit/inventory organization context.
• SO_HEADER_ID — the sales order header identifier from SO_LINES, indicating which sales order the open line belongs to.

The SELECT uses SELECT UNIQUE, so duplicate combinations of (ITEM_ID, ORGANIZATION_ID, SO_HEADER_ID) are collapsed to a single row. Multiple open lines on the same header referencing the same item will therefore yield one row, not one per line.

Common Use Cases and Queries

Typical uses include identifying open sales order headers tied to a revised engineering item, and feeding iProcurement or scheduling workflows that must know whether an item is committed to open orders. A representative query:

• Open order headers for an item: SELECT ITEM_ID, ORGANIZATION_ID, SO_HEADER_ID FROM ICX_ENG_WEB_SCHEDULE_SO_V WHERE ITEM_ID = :p_item_id AND ORGANIZATION_ID = :p_org_id;
• Distinct items on open sales orders: SELECT DISTINCT ITEM_ID, ORGANIZATION_ID FROM ICX_ENG_WEB_SCHEDULE_SO_V ORDER BY ITEM_ID;
• Count of open order headers per item: SELECT ITEM_ID, ORGANIZATION_ID, COUNT(SO_HEADER_ID) FROM ICX_ENG_WEB_SCHEDULE_SO_V GROUP BY ITEM_ID, ORGANIZATION_ID;

Because the view emits UNIQUE rows and only keys, it is best used as a correlation or existence check rather than a source of order-line quantities, dates, or prices. For those attributes, join SO_HEADER_ID back to OE_ORDER_HEADERS_ALL and the item back to engineering schedule detail tables.