Search Results exclude_open_hold

Overview

APPS.WIP_ICX_OSP_WORKBENCH_V is a Work in Process (WIP) view that presents outside processing (OSP) purchase order information for the Oracle E-Business Suite Outside Processing Workbench and associated Oracle iProcurement / self-service flows. It consolidates purchasing, receiving, item, vendor, and shop-floor routing data into a single flattened row per OSP distribution, so that buyers, planners, and shop-floor supervisors can review supplier commitments tied to discrete jobs, repetitive schedules, and EAM work orders without navigating multiple purchasing and manufacturing windows. The view is validated and owned by APPS, and it is a reporting and integration construct rather than a transactional entity.

The user search term exclude_open_hold does not correspond to a column or filter embedded in the view text. It is not exposed here. Open-hold exclusion is typically applied by the consuming Workbench logic or by the calling form/report using the purchasing hold columns on the source PO tables, not by this view itself.

Underlying Base Objects

The view is defined over a join of purchasing and WIP objects. Documented base objects include the PO synonyms PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_RELEASES_ALL, PO_DISTRIBUTIONS_ALL, and PO_DOCUMENT_TYPES_ALL; the WIP synonyms WIP_ENTITIES, WIP_DISCRETE_JOBS, WIP_LINES, WIP_OPERATIONS, WIP_REPETITIVE_SCHEDULES, and WIP_OPERATION_RESOURCES; and the item and supplier views MTL_SYSTEM_ITEMS_KFV, PO_VENDORS, HR_ALL_ORGANIZATION_UNITS_TL, and MFG_LOOKUPS. It also calls the PL/SQL packages WIP_OSP, WIP_WORK_ORDER_PVT, QA_SS_OSP, BOM_REVISIONS, FND_ATTACHMENT_UTIL_PKG, and FND_MESSAGE.

The packages drive derived columns: WIP_WORK_ORDER_PVT.COMPONENT_EXIST flags component availability, FND_ATTACHMENT_UTIL_PKG.GET_ATCHMT_EXISTS signals routing attachments, and FND_MESSAGE.GET_STRING supplies the Available message text. Join keys tie OSP distributions to the WIP entity via WIP_ENTITY_ID, WIP_OPERATION_SEQ_NUM, and WIP_REPETITIVE_SCHEDULE_ID.

Key Columns

• PO_NUMBER-derived expression — DECODE(PH.TYPE_LOOKUP_CODE,'STANDARD',PH.SEGMENT1,'BLANKET',PH.SEGMENT1||'-'||PR.RELEASE_NUM), showing the PO or blanket-release number.
• CONCATENATED_SEGMENTS (from MTL_SYSTEM_ITEMS_KFV) — the OSP item identifier.
• VENDOR_PRODUCT_NUM, ITEM_DESCRIPTION, VENDOR_ID, VENDOR_SITE_ID, VENDOR_CONTACT_ID, AGENT_ID — supplier and buyer details.
• NEED_BY_DATE, PROMISED_DATE — scheduling dates for the OSP line location.
• QUANTITY_ORDERED, QUANTITY_DELIVERED, UNIT_MEAS_LOOKUP_CODE — ordered versus received quantities.
• WIP_ENTITY_NAME, ENTITY_TYPE, LINE_CODE, WIP_OPERATION_SEQ_NUM, WIP_REPETITIVE_SCHEDULE_ID — shop-floor context.
• Component/attachment availability flags — derived via the WIP and FND packages described above.
• Identifiers — PO_HEADER_ID, PO_RELEASE_ID, PO_LINE_ID, LINE_LOCATION_ID, PO_DISTRIBUTION_ID, WIP_ENTITY_ID, WIP_LINE_ID, ORG_ID, DESTINATION_ORGANIZATION_ID.
• TYPE_NAME (from PO_DOCUMENT_TYPES_ALL) and shipping attributes such as SHIP_TO_LOCATION_ID, SHIP_VIA_LOOKUP_CODE.

Common Use Cases and Queries

Typical uses include OSP Workbench result sets, open supplier commitment reports by job or schedule, and identifying OSP operations blocked by missing components or attachments. A representative query:

SELECT wip_entity_name, entity_type, line_code,
       wip_operation_seq_num, vendor_product_num,
       need_by_date, promised_date,
       quantity_ordered, quantity_delivered
FROM   apps.wip_icx_osp_workbench_v
WHERE  wip_entity_name = :job_name
ORDER  BY wip_operation_seq_num;

To trace purchasing detail for a distribution, query by po_distribution_id. To filter by supplier, join on vendor_id. Because the view does not itself exclude open holds, consumers requiring that behavior should add a hold-status predicate against PO_DISTRIBUTIONS_ALL or the PO hold tables, or use the Workbench UI, which applies such filtering externally.