Search Results wsh_itm_customize




Overview
Explore in AI Chat

Overview

WSH_ITM_CUSTOMIZE is a PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports the Oracle Shipping execution module, specifically the "in-transit" or item movement (WSH_ITM) processing infrastructure. The package provides controlled customization hooks that allow implementers and technical consultants to modify the default behavior of item synchronization, party synchronization, and delivery marking logic without directly altering the seeded base code. In Oracle EBS 12.1.1 and 12.2.2, this object is registered in ETRM with an API classification of "OTHER" and carries a VALID status, confirming that it is compiled and available at runtime. Its role is to serve as an extension point within the shipping transaction processing chain; the base application invokes it during item and party sync operations so that site-specific logic can be layered on top of standard processing. Because it is referenced by core packages such as WSH_DELIVERY_VALIDATIONS, WSH_ITM_ITEM_SYNC, and WSH_ITM_PARTY_SYNC, it forms part of the interdependency graph that governs how shipping data is validated and propagated. The package itself depends on WSH_ITM_QUERY_CUSTOM, indicating that it draws on customized query definitions when executing its logic.

Key Procedures and Functions

The documented package exposes three procedures. Their names indicate the functional areas they govern, though the ETRM excerpt does not publish their parameter lists.

  • ALTER_ITEM_SYNC — Provides a customization point for item synchronization processing. It is invoked in the context of WSH_ITM_ITEM_SYNC, allowing the standard item sync flow to be altered or extended. Typical uses include applying site-specific rules that determine how item attributes are staged or transformed before they are synchronized across shipping entities.
  • ALTER_PARTY_SYNC — Provides the corresponding customization hook for party (trading partner) synchronization, associated with WSH_ITM_PARTY_SYNC. Implementers use this entry point to influence how party data is reconciled or propagated during shipping item processing.
  • ALTER_DELIVERY_MARK — Supports customization of delivery marking logic, relating to how deliveries and their line details are flagged or recorded during the shipping cycle. This procedure is the point at which site-specific marking behavior can be introduced while preserving the seeded validation path managed by WSH_DELIVERY_VALIDATIONS.

All three procedures follow the naming convention "ALTER_*," signalling that their intent is to modify or override default processing rather than to perform standalone business tasks.

Tables Accessed

The ETRM metadata for this object does not enumerate any directly referenced base tables accessed through APPS synonyms. The documented dependency information instead shows package-to-package relationships: WSH_ITM_CUSTOMIZE depends on WSH_ITM_QUERY_CUSTOM and on the SYS.STANDARD package, and it is referenced by WSH_DELIVERY_VALIDATIONS, WSH_ITM_ITEM_SYNC, and WSH_ITM_PARTY_SYNC. Because no table-level dependencies are published, the package's persistent data interactions are assumed to occur indirectly through the custom query package and the calling synchronization packages, which are responsible for reading and writing the underlying WSH shipping tables. Consultants should therefore trace table access through WSH_ITM_QUERY_CUSTOM rather than through this package directly, and should treat the absence of documented table references as a signal that the package is a logic-layer customization hook rather than a data-access component.

Usage Notes

WSH_ITM_CUSTOMIZE is not typically invoked directly by end users or from Oracle Forms. It is called programmatically by the Oracle Shipping synchronization and validation packages during concurrent program execution and transactional processing. Specifically, WSH_ITM_ITEM_SYNC and WSH_ITM_PARTY_SYNC invoke the ALTER_ITEM_SYNC and ALTER_PARTY_SYNC procedures respectively, while WSH_DELIVERY_VALIDATIONS references the package during delivery validation flows. WSH_ITM_CUSTOMIZE also references itself, which is consistent with internal, recursive, or helper-call patterns within the customization logic. Custom code deployments should modify this package only through supported extension mechanisms, since changes here affect the item and party synchronization chain across shipping. Because the package is VALID in both 12.1.1 and 12.2.2, any customer-specific alterations must be revalidated after patching or upgrades to avoid invalidating dependent packages such as WSH_DELIVERY_VALIDATIONS.