Search Results lock_work_order

Overview

APPS.WIP_WORK_ORDER_PVT is a private PL/SQL package within the Oracle E-Business Suite Work in Process (WIP) module. It functions as the internal companion layer to the public API package WIP_Work_Order_PUB, and is typically designated with AUTHID CURRENT_USER in its specification header. Its primary business purpose is to support the creation, retrieval, locking, and validation of work orders across the three WIP work order models: discrete jobs, repetitive schedules, and flow schedules, along with their associated WIP entities and kanban details.

Because it is classified as a PVT (private) API, it is not intended for direct invocation by external or customer code. Instead, the public package WIP_Work_Order_PUB delegates internal processing — row locking, record retrieval, and business rule checks — to this package. The two packages share the same record type definitions (such as Wip_Entities_Tbl_Type, Flowschedule_Tbl_Type, Discretejob_Tbl_Type, and Repschedule_Tbl_Type), allowing standardized, multi-row (table-based) input and output for work order transactions. The package is referenced by four other packages, confirming its role as a shared internal utility within the WIP processing stack.

Key Procedures and Functions

The documented API exposes six procedures:

• LOCK_WORK_ORDER — Obtains locks on work order records using the WIP entity, flow schedule, discrete job, and repetitive schedule PL/SQL tables. It follows the standard EBS API parameter convention (API version, init message list, and return status/message count/message data outputs) and works with both input and in-out table parameters.
• GET_WORK_ORDER — Retrieves work order details for a specified WIP entity, returning results through the shared WIP entity table structure.
• GET_KANBAN_DETAILS — Returns kanban-related information associated with a work order, supporting kanban-driven replenishment scenarios.
• CHECK_BUILD_SEQUENCE — Validates the build sequence assigned to a work order, enforcing sequencing rules before a job or schedule is processed.
• COMPONENT_EXIST — Determines whether components (material requirements) exist for a given work order or operation, supporting validation logic before material issue or completion activities.

Tables Accessed

The package accesses the following documented tables via APPS synonyms:

• WIP_REQUIREMENT_OPERATIONS — The core WIP table holding component requirements tied to work order operations. It is read primarily to support the COMPONENT_EXIST check, verifying that material requirements are defined for the work order or operation being validated.
• DUAL — Oracle's single-row utility table, commonly used for PL/SQL variable initialization, existence checks, or lightweight lookups.
• PLITBLM — Part of the Oracle Forms/PL/SQL table infrastructure (the PL/SQL table manager package/table), used for managing the table-type parameters passed into and out of the API procedures.

Usage Notes

WIP_WORK_ORDER_PVT is an internal implementation package and should not be called directly by custom integrations. Standard practice is to invoke the public counterpart, WIP_Work_Order_PUB, which in turn calls this private package for locking, retrieval, and validation. The package is typically triggered from WIP-related Oracle Forms (such as the Discrete Jobs, Repetitive Schedules, and Flow Scheduling forms), from WIP concurrent programs, and from other internal WIP APIs that require work order lookups or validation. Because its procedures use the shared Wip_Entities_Tbl_Type, Discretejob_Tbl_Type, Repschedule_Tbl_Type, and Flowschedule_Tbl_Type structures, any custom code should reference the public package record types rather than binding directly to this private API. On both Oracle EBS 12.1.1 and 12.2.2, customizations should treat WIP_WORK_Order_PVT as an unsupported, version-sensitive internals layer subject to change during patching.