Search Results wsh_itm_item_sync




Overview
Explore in AI Chat

Overview

The concurrent program WSH_ITM_ITEM_SYNC — presented to end users as Item Synchronization — is owned by the WSH: Shipping Execution product family within Oracle E-Business Suite. Its documented description is "ITM Item Synchronization," and it is enabled for use in both Oracle EBS 12.1.1 and 12.2.2. The program is responsible for synchronizing item-related data between the Shipping Execution schema and the underlying Inventory item master so that shipping-eligible items, their attributes, and associated freight or handling classifications remain consistent across the two modules. Because Shipping Execution relies heavily on inventory item definitions, any divergence between the item master and the shipping data structures can cause failures during pick release, ship confirm, and manifesting. This program serves as the corrective and preventive mechanism that reconciles those structures.

Execution Details

Per the documented ETRM metadata for release 12.2.2, the program is configured with the following execution attributes:

  • User-facing name: Item Synchronization
  • Product: WSH – Shipping Execution
  • Enabled: Yes
  • Execution Method: PL/SQL Stored Procedure
  • Argument Method: Standard
  • Executable: WSH_ITM_SYNC_ITEM
  • Execution Filename: WSH_ITM_ITEM_SYNC.POPULATE_DATA

Because the execution method is a PL/SQL stored procedure, the program runs entirely within the database tier and does not invoke a concurrent manager report or host script. The executable WSH_ITM_SYNC_ITEM calls the packaged routine WSH_ITM_ITEM_SYNC.POPULATE_DATA, which performs the actual population and reconciliation logic against the item synchronization tables. The Standard argument method indicates that parameters, if defined on the concurrent program definition, are passed positionally rather than through a token-based or named convention.

How to Run

Users submit Item Synchronization through the standard Submit Requests (SRS) window, typically by navigating to Shipping Execution > Requests > Run, or by using the generic View > Requests > Submit a New Request path if Shipping responsibility menus expose the program. Administrators can also launch it via the Concurrent Programs form or schedule it as a recurring request when large item master changes occur.

Because the documented Argument Method is Standard, the program may expose one or more positional parameters — commonly an organization or inventory organization context — to scope the synchronization to a specific warehouse or operating unit. Where no parameters are defined, the program processes items system-wide. It is good practice to run the program after bulk item imports, new item category assignments, or changes to shipping-relevant item attributes, and to schedule it during low-activity windows because synchronization touches large item populations.

Related Objects

The synchronization logic executed by WSH_ITM_ITEM_SYNC.POPULATE_DATA interacts with item and shipping interface structures. Commonly associated objects include:

  • WSH_ITM_ITEM_SYNC — the PL/SQL package containing the POPULATE_DATA routine.
  • WSH_ITM_SYNC_ITEM — the executable definition registered against the concurrent program.
  • MTL_SYSTEM_ITEMS_B / MTL_SYSTEM_ITEMS_TL — the Inventory item master tables from which item attributes are read.
  • Shipping item-related staging or interface tables used by WSH to hold shipping-eligible item attributes.
  • INV Item APIs and shipping item attribute APIs that may be invoked as part of reconciliation.

Correct and timely execution of this program helps ensure that pick release and ship confirm operations reflect the current state of the item master across both EBS 12.1.1 and 12.2.2 environments.