Search Results shipping




The WSH_PARAMETERS table in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 is a critical repository for configuration parameters used by the Oracle Shipping Execution module (WSH). This table stores system-wide and organization-specific settings that govern shipping operations, including freight calculations, carrier integrations, and delivery scheduling. Below is a detailed analysis of its structure, purpose, and significance in Oracle EBS.

Table Structure and Key Columns

The WSH_PARAMETERS table consists of columns that define shipping-related configurations. Key columns include:
  • ORGANIZATION_ID: Links parameters to specific inventory organizations (NULL indicates global settings).
  • PARAMETER_CODE: A unique identifier for each parameter (e.g., ENABLE_AUTO_PACKING).
  • PARAMETER_VALUE: Stores the configured value for the parameter (e.g., Y/N).
  • DESCRIPTION: Provides a brief explanation of the parameter's purpose.
  • LAST_UPDATE_DATE and LAST_UPDATED_BY: Audit columns tracking modifications.

Functional Role in Shipping Execution

The table acts as a central control point for shipping workflows. Examples of parameters include:
  • Freight Calculation: Parameters like FREIGHT_CALC_METHOD determine whether freight costs are computed manually or via integrated carriers (e.g., FedEx, UPS).
  • Packing Rules: AUTO_PACKING_RULE_ID dictates how items are grouped into containers during automated packing.
  • Delivery Scheduling: MAX_DELIVERY_LEAD_TIME sets thresholds for delivery date calculations.
  • Integration Flags: Parameters such as ENABLE_EDI_INVOICING control electronic data interchange (EDI) with trading partners.

Technical Implementation

Data in WSH_PARAMETERS is accessed via Oracle Shipping APIs (e.g., WSH_PARAMETERS_PKG), ensuring consistent parameter retrieval. The table is populated during module initialization or via administrative screens (e.g., Shipping Administrator responsibility). Default values are often seeded by Oracle during installation.

Customization and Extensions

Organizations can extend the table by adding custom parameters (prefixed with XX_ to avoid conflicts). For example, a custom parameter XX_ENABLE_CUSTOM_CARRIER could activate third-party carrier integrations. Modifications typically require PL/SQL triggers or concurrent programs to enforce business logic.

Impact on Upgrades and Patches

During EBS upgrades (e.g., 12.1.1 to 12.2.2), Oracle may introduce new parameters or deprecate obsolete ones. Custom parameters must be reviewed for compatibility. The table is preserved during upgrades, but parameter defaults may reset, necessitating post-upgrade validation.

Performance Considerations

Indexes on ORGANIZATION_ID and PARAMETER_CODE optimize query performance. Large parameter sets (e.g., multi-org deployments) may benefit from caching mechanisms like Oracle Application Object Library (FND) caching.

Conclusion

The WSH_PARAMETERS table is a foundational component of Oracle Shipping Execution, enabling flexible configuration of shipping workflows. Its design supports both out-of-the-box functionality and extensibility, making it indispensable for logistics operations in Oracle EBS 12.1.1 and 12.2.2. Proper management of this table ensures efficient shipping processes and seamless integration with external systems.