Search Results wip_osp_shp_i_wf




Overview
Explore in AI Chat

Overview

WIP_OSP_SHP_I_WF is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports Outside Processing (OSP) shipping workflows within Oracle Work in Process. Outside Processing allows a discrete or repetitive manufacturing job to send components or assemblies to an external supplier for a value-added operation before the item returns to the shop floor. This package supplies the workflow-facing logic that (a) gathers requisition and purchase order information tied to an OSP operation, (b) drives the shipping and receiving interaction with the supplier, and (c) coordinates concurrent request execution and waiting behavior so that workflow activities can advance only after downstream processing completes.

The package is part of the tightly coupled OSP family that also includes POS_ASN, POS_CREATE_ASN, POS_ASN_CREATE_PVT, WIP_OSP, and WIP_MOVPROC_PRIV. The dependency metadata confirms a bidirectional relationship: WIP_OSP_SHP_I_WF depends on STANDARD, and it is referenced by five packages, including POS_ASN and WIP_MOVPROC_PRIV, reflecting its role as a shared utility layer for OSP shipping and receiving workflow transactions.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions that fall into four functional groups.

  • Workflow startup and setup: STARTWFPROCESS, STARTWFPROCTOANOTHERSUPPLIER, SETSTARTUPWFATTRIBUTES, and GETSTARTUPWFATTRIBUTES initialize and retrieve the workflow attributes required to launch an OSP shipping process, including the alternate-supplier path.
  • Requisition and PO data access: GETREQIMPORT, STARTREQIMPORT, WAITFORREQIMPORT, GETPODATA, SETPODATA, GETAPPROVEDPO, and COPYPOATTR handle requisition import, retrieve and store purchase order details, obtain approved POs, and copy PO attributes forward. MULTIPLEPO supports scenarios where more than one purchase order is associated with the OSP transaction.
  • Validation and routing: VALIDATE performs data checks before processing, while SELECTSHIPPINGMANAGER determines the correct shipping manager (for example, based on organization or supplier context) and GETSHIPTOADDRESS returns the ship-to address used on the OSP shipment.
  • Process orchestration: STARTDETAILPROCESSES launches the detailed sub-processes that follow the initial setup, and WAITFORREQIMPORT suspends workflow progression until the requisition import concurrent request finishes.

Because parameter signatures are not published in the metadata, callers should reference the package specification for exact argument lists.

Tables Accessed

The package reads and writes through APPS synonyms to several core EBS tables. Purchasing tables dominate: PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, PO_RELEASES_ALL, PO_REQUISITIONS_INTERFACE_ALL, PO_REQUISITION_HEADERS_ALL, and PO_REQUISITION_LINES_ALL supply the requisition and purchase order data that drives OSP shipping. The location tables PO_LOCATION_ASSOCIATIONS and PO_LOCATION_ASSOCIATIONS_ALL resolve ship-to and supplier-location information used by GETSHIPTOADDRESS and SELECTSHIPPINGMANAGER.

Manufacturing and inventory context comes from BOM_RESOURCES, MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_KFV (item and resource lookups), and HR_ORGANIZATION_INFORMATION for organization-level attributes. Finally, FND_CONCURRENT_REQUESTS is queried to monitor the status of the requisition import concurrent program, supporting WAITFORREQIMPORT.

Usage Notes

WIP_OSP_SHP_I_WF is a workflow support package rather than an end-user entry point. It is invoked by the Oracle Workflow engine as OSP shipping orchestration functions execute, and by peer packages—POS_ASN, POS_ASN_CREATE_PVT, POS_CREATE_ASN, WIP_OSP, and WIP_MOVPROC_PRIV—that participate in the OSP shipping and receiving cycle. Its status is VALID and its API classification is OTHER, indicating it is intended for internal EBS use rather than published customization.

Custom code should avoid direct invocation where possible and instead rely on supported OSP entry points such as the WIP Outside Processing forms or the standard ASN shipping flow. Integrations that must call it directly should be regression-tested on both 12.1.1 and 12.2.2, since workflow attribute and concurrent manager interactions can differ across releases. As with all APPS-schema packages, changes should be made only through Oracle patches.