Search Results get_work_order

Overview

APPS.WIP_WORK_ORDER_PUB is a public PL/SQL API package body that exposes a standard, supported interface for interrogating Work in Process (WIP) work order data within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. The package is owned by the APPS schema and is classified as a "PUB" (public) API, meaning it forms part of Oracle's documented, callable integration surface rather than an internal helper unit. Its principal role is to provide a single entry point through which callers can retrieve the full set of attributes associated with a work order, abstracting the underlying WIP entity, flow schedule, discrete job, and repetitive schedule structures into strongly typed PL/SQL collections. Because the header carries a legacy revision marker ($Header: WIPPWORB.pls 115.10), it is a long-standing component of the WIP module and is referenced by eleven other packages in the ETRM inventory, indicating that it operates as a foundational read API within the WIP technical stack.

Key Procedures and Functions

The package body documents exactly one public routine:

• GET_WORK_ORDER — The sole documented procedure in the package. It retrieves work order information for a given WIP entity and returns the results across a set of parallel OUT NOCOPY collections. These output tables are specialized to each work order category: WIP entities, flow schedules, discrete jobs, and repetitive schedules, each accompanied by a corresponding "_VAL" validation table that carries descriptive (value) attributes as opposed to internal identifiers. The procedure accepts standard FND_API control parameters for API version negotiation, message-list initialization, conditional return of values, and standardized return status, message count, and message data. The procedural body performs the conventional compatibility check through FND_API.Compatible_API_Call against an internal version constant of 1.0, raising FND_API.G_EXC_UNEXPECTED_ERROR when the caller's version is incompatible, and then applies the standard ID/validation conversion logic.

No other procedures or functions are documented for this package body.

Tables Accessed

The ETRM metadata does not enumerate specific base tables or APPS synonyms accessed by WIP_WORK_ORDER_PUB. The signature itself, however, shows that the procedure operates over the principal WIP work order entities — WIP entities, flow schedules, discrete jobs, and repetitive schedules — and the returned value collections imply joins against their respective descriptive/validation views. Consistent with standard EBS API conventions, the routine reads the WIP entity tables and their translations for the ID-to-value conversion performed after the API version check.

Usage Notes

WIP_WORK_ORDER_PUB.GET_WORK_ORDER is typically invoked from custom PL/SQL that needs to query work order details without issuing direct SQL against WIP base tables, thereby preserving upgrade safety and honoring Oracle's supported API boundary. Because the procedure exposes FND_API standard parameters, callers must pass a valid API version and be prepared to interpret x_return_status along with the message stack. The package is a natural dependency for forms, concurrent programs, and integration routines that must resolve a WIP entity ID into discrete job, flow schedule, or repetitive schedule attributes. Its use by eleven other packages confirms that it is frequently called as an upstream service by higher-level WIP and manufacturing APIs. Developers searching for "get_work_order" should treat this procedure as the canonical, version-checked entry point for work order retrieval in the WIP module.