Search Results wsh_parameters




Overview
Explore in AI Chat

Overview

WSH_PARAMETERS is the Shipping Parameters table owned by the OE schema in Oracle E-Business Suite (validated in 12.1.1 and 12.2.2). It stores the operational and printing configuration that drives Oracle Shipping execution at the organization (warehouse) level. Each row corresponds to a single inventory organization and defines how that organization plans shipments, handles weight and volume calculations, controls container and packing behavior, sequences releases, selects pick slip and release rules, and determines report sets for departure and delivery documentation. The table is a foundational setup object: Shipping execution logic, AutoCreate, Pick Release, and Delivery workflows read these parameters at runtime to determine default behavior. Because WSH_PARAMETERS governs behavior across many downstream processes, its values directly affect picking, packing, manifesting, and shipping confirmation.

From a Data Vault modeling perspective, the ETRM metadata classifies this table heuristically as standalone. In practice it functions most naturally as a satellite keyed by ORGANIZATION_ID (the business key), with the remaining descriptive columns (rules, flags, report sets) captured as dependent attributes. It is not a hub or link, as it holds no unique business transaction identity of its own beyond the organization.

Key Information Stored

The documented physical schema contains 42 columns. The most operationally significant are summarized below. Note that the FK metadata identifies RELEASE_SEQ_RULE_ID and PICK_SLIP_RULE_ID as references into their respective rule tables; these, alongside ORGANIZATION_ID, are the principal business-key candidates, though no unique index is documented in the excerpt.

Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_ID, REQUEST_ID, etc.) follow standard EBS WHO-column conventions.

Common Use Cases and Queries

Typical uses include reviewing or auditing shipping setup per organization, comparing parameters across warehouses, and troubleshooting unexpected Pick Release or ship-confirm behavior. A frequent query retrieves the configuration for a specific warehouse:

SELECT organization_id,
       planning_method_flag,
       enforce_packing_flag,
       inv_controls_container_flag,
       weight_volume_sc_flag,
       release_seq_rule_id,
       pick_slip_rule_id
FROM   oe.wsh_parameters
WHERE  organization_id = :p_org_id;

Reporting queries often join to the rule tables to translate rule IDs into descriptions. Auditing whether AutoCreate or packing enforcement is enabled across all shipping organizations is another common pattern, as is validating that each active organization has a populated parameter row.

Related Objects

  • WSH_RELEASE_SEQ_RULES — joined via WSH_PARAMETERS.RELEASE_SEQ_RULE_ID = WSH_RELEASE_SEQ_RULES.RELEASE_SEQ_RULE_ID.
  • WSH_PICK_SLIP_RULES — joined via WSH_PARAMETERS.PICK_SLIP_RULE_ID = WSH_PICK_SLIP_RULES.PICK_SLIP_RULE_ID.
  • WSH_NEW_DELIVERIES — delivery records governed by these parameters.
  • WSH_DELIVERY_ASSIGNMENTS — associations driven by grouping/packing parameters.
  • WSH_TRIPS — trip and departure reporting reference these settings.
  • MTL_PARAMETERS — the analogous inventory-organization parameter table, sharing ORGANIZATION_ID.
  • ORG_ORGANIZATION_DEFINITIONS / HR_ALL_ORGANIZATION_UNITS — resolve organization names for reporting.

Shipping-related concurrent programs and the Oracle Shipping public APIs consume these parameters implicitly during execution, making WSH_PARAMETERS a critical setup dependency for shipping transaction accuracy.