Search Results get_prj_loc_lov

Overview

APPS.WIP_DISCRETE_WS_MOVE is a server-side PL/SQL package that encapsulates the discrete manufacturing move transaction logic used by Oracle EBS Work in Process. It provides a programmatic entry point for moving assemblies between operations and steps on a discrete job, exploding the associated component requirements, and committing the resulting material and resource transactions. The package abstracts the underlying transaction engine so that callers — typically the discrete work-in-process move user interface, service-oriented integrations, and custom extensions — can perform a WIP move without directly manipulating the WIP transaction interface tables.

Functionally, the package supports the complete move flow: validating a requested move quantity against the job, determining the transaction mode and UOM, resolving the scrap account and QA collection context, exploding components for the quantity moved, and writing the resulting move and completion headers. It also performs auxiliary tasks required by the move, such as creating locators on demand and checking for overshipment against an order line.

Key Procedures and Functions

• EXPLODECOMPONENTS — Explodes the component requirements for a specified move quantity across a discrete job, producing the move transaction ID, completion transaction ID, transaction header, component header, batch, lot entry type, component information, material mode, and period. Returns status and error message outputs.
• PROCESSMOVE — Accepts a MoveData record describing the move (transaction mode, type, organization, WIP entity, from/to operation and step, quantity, UOM, scrap account, QA collection, period, headers, and material mode) and processes the transaction, returning status and error information.
• CREATELOCATOR — Creates a locator within a specified organization, subinventory, and locator name, returning the generated locator ID along with status and error message outputs.
• CHECKOVERSHIPMENT — Validates a proposed quantity against an item and order line to detect overshipment, accepting primary quantity and UOM and returning status and error information.
• CLIENTTOSERVERDATE — Converts a client-side date value to the corresponding server-side date, supporting timezone normalization.
• SERVERTOCLIENTDATE — Performs the inverse conversion, translating a server date to the client representation.
• INITTIMEZONE — Initializes the timezone context used by the date conversion routines.
• GET_PRJ_LOC_LOV — Added as a fix for bug 4568517, this procedure supplies the project locator list of values used when a move transaction must select a project-related locator.

Tables Accessed

The package references several WIP and inventory tables through APPS synonyms. WIP_DISCRETE_JOBS is read to validate the job and its operation/step structure, while WIP_MOVE_TXN_INTERFACE, WIP_TRANSACTIONS_S, and WIP_PERIOD_BALANCES carry the move transaction data and period balances. MTL_MATERIAL_TRANSACTIONS_S and MTL_RESERVATIONS support the material transaction and reservation side of component consumption, and MTL_SECONDARY_INVENTORIES plus MTL_SECONDARY_LOCATORS are used by the locator creation and lookup routines. PJM_ORG_PARAMETERS provides project organization parameters relevant to the project locator LOV, and QA_RESULTS stores quality collection outcomes. DUAL is used for lightweight scalar operations.

Usage Notes

WIP_DISCRETE_WS_MOVE is an internal application programming interface rather than a standalone concurrent program. It is typically invoked from the discrete WIP move forms and from integration or custom code that needs to simulate a discrete move transaction outside the standard UI. Because the procedures write into the WIP transaction interface and related transaction tables, callers should invoke them within a controlled transaction boundary and always inspect the returned status and error message outputs before committing.

The package header carries the identifier wipdsmvs.pls with a 2006 revision, and the metadata records one dependent package referencing it. Customizations should avoid direct DML against the underlying tables and instead call these procedures to preserve the standard validation, component explosion, and period balance logic.