Search Results wsh_itm_items_s

Overview

The APPS.WSH_ITM_ITEM_SYNC package body is a shipping execution utility that synchronizes item master data into the Oracle Shipping (WSH) item infrastructure. It resides in the APPS schema and is a VALID, compiled PL/SQL package body with an API classification of OTHER. The package belongs to the Oracle Shipping Execution module (WSH) and specifically supports the Item Transportation Management (ITM) sub-component, which maintains shipping-specific item attributes, query customizations, and item validation rules used during move order, pick release, and shipping transactions.

Its principal role is to populate and refresh the Shipping item tables (WSH_ITM_ITEMS and the corresponding WSH_ITM_ITEMS_S sequence-friendly staging structure) from source item definitions, keyed to request-control records. The package therefore acts as a maintenance interface: other EBS processes and administrators use it to keep the shipping item registry consistent with the inventory item master and shipping configuration, without requiring manual DML.

Key Procedures and Functions

The ETRM documentation records a single documented program unit: POPULATE_DATA.

• POPULATE_DATA — The primary synchronization driver. Based on the package name and its dependencies, this procedure reads the shipping item request control records and loads or refreshes the corresponding rows in the WSH ITM item tables. It is not a parameter-documented public API in the ETRM; no parameter list is published in the metadata, and callers should consult the packaged specification before direct invocation.

The package body additionally depends heavily on the following private/supporting objects, indicating the broader logic implemented in POPULATE_DATA:

• WSH_ITM_CUSTOMIZE — applies shipping item customization settings.
• WSH_ITM_QUERY_CUSTOM — supplies query customization logic for item selection.
• WSH_DEBUG_INTERFACE and WSH_DEBUG_SV — provide debug logging and diagnostics.
• FND_CONCURRENT — supports concurrent program request context (request ID, concurrent program ID, and concurrent request status handling).
• FND_GLOBAL, FND_LANGUAGES, and FND_FLEX_KEY_API — supply session identity, language/MLS handling, and key flexfield validation for item segments.
• DBMS_SQL, STANDARD, PLITBLM, and DUAL — provide dynamic SQL execution, PL/SQL built-ins, and miscellaneous utility support.

Tables Accessed

The metadata lists the following tables accessed through APPS synonyms:

• WSH_ITM_REQUEST_CONTROL and WSH_ITM_REQUEST_CONTROL_S — the driving control structures. These record which item synchronization requests must be processed. The _S variant typically supplies sequence or staging rows for request numbering. Notably, this is the object the user searched for (wsh_itm_request_control_s), and it is a direct dependency of this package.
• WSH_ITM_ITEMS and WSH_ITM_ITEMS_S — the target shipping item tables populated by POPULATE_DATA. WSH_ITM_ITEMS holds the resolved shipping item rows; WSH_ITM_ITEMS_S provides the supporting staging/sequence structure for insert processing.
• FND_LANGUAGES — used for language-specific (MLS) item descriptions.
• DUAL — used for singleton selects and procedural control.

Dynamic SQL against additional dictionary or item-master tables is likely executed through DBMS_SQL, though the ETRM does not enumerate those SQL statements.

Usage Notes

WSH_ITM_ITEM_SYNC is typically invoked as part of a concurrent program in Oracle Shipping Execution, given its dependency on FND_CONCURRENT. Administrators schedule the synchronization after item master changes, shipping item attribute updates, or configuration changes affecting ITM query customization. It may also be called from custom code or Oracle Shipping forms that add or update shipping item records, provided the caller submits an appropriate request-control row in WSH_ITM_REQUEST_CONTROL and invokes POPULATE_DATA within a valid FND_GLOBAL session.

Because the package is not referenced by any other database object, it is an entry-point utility rather than a shared library. Direct calls should supply a concurrent request context; otherwise debug output and error handling provided by WSH_DEBUG_INTERFACE and WSH_DEBUG_SV may not be available. Standard EBS practice applies: test synchronization in a non-production instance, verify that no other item sync process is running, and review the request-control records for pending or errored entries before resubmission. No published public API contract exists in the ETRM, so integrators should validate behavior against the specific 12.1.1 or 12.2.2 release and consult Oracle Support before relying on the procedure in custom extensions.