Results for “parameter_value”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The WSH.WSH_ITM_VENDOR_PARAMETERS table is a Shipping Execution (WSH) module object that stores extended, vendor-specific configuration attributes as name-value pairs. Rather than dedicating discrete columns to every configurable option a carrier or integration vendor may expose, the table captures these settings in a generic PARAMETER_NAME / PARAMETER_VALUE structure. This design accommodates third-party logistics providers and shipping integration vendors whose parameter sets vary widely and evolve independently of the Oracle schema.

The name-value pattern is particularly significant in the Shipping Execution context. Oracle Transportation/Shipping integrations with external vendors — manifesting systems, rating engines, carrier connectivity platforms — each expose different request semantics. Examples documented by ETRM include Request Version and Request Handler, which govern how the application constructs and dispatches vendor-specific request payloads. Centralizing these in a parameter table allows new vendor capabilities to be enabled through data configuration rather than schema modification.

The ETRM metadata annotates this object with a Data Vault classification of satellite-leaning, derived heuristically from its foreign key structure. As a modeling suggestion, this reflects the table's role as a descriptive, attribute-bearing companion to a parent entity: it holds mutable descriptive detail about a vendor rather than defining a hub (business key registry) or a link (many-to-many association between hubs). The parent it describes is WSH_ITM_VENDORS.

Key Information Stored

• VENDOR_PARAMETER_ID — the surrogate primary key, enforced by WSH_ITM_VENDOR_PARAMETERS_PK and additionally backed by unique index WSH_ITM_VENDOR_PARAMETERS_U1. It uniquely identifies each parameter row and serves as the documented business-key candidate.
• VENDOR_ID — the foreign key to WSH_ITM_VENDORS, tying each parameter to its owning vendor record.
• PARAMETER_NAME — the identifier of the setting (for example, Request Version or Request Handler).
• PARAMETER_VALUE — the value assigned to that setting for the specific vendor.
• LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns recording when and by whom the parameter was most recently modified.
• CREATION_DATE, CREATED_BY — standard audit columns recording initial insertion.
• LAST_UPDATE_LOGIN — the login identifier associated with the last update, supporting session-level traceability.

The nine documented columns follow the standard Oracle EBS "WHO" audit convention, enabling full change tracking without additional columns. Because parameters are stored generically, report authors should treat PARAMETER_VALUE as free-form text unless vendor-specific parsing rules are known.

Common Use Cases and Queries

Typical usage centers on vendor onboarding and troubleshooting. When configuring a new carrier integration, administrators insert parameter rows to declare request format versions or handler identifiers. During diagnosis, support teams query parameter values to confirm that a vendor is wired to the expected request handler.

A frequent pattern pivots the name-value rows into a readable columnar layout for a given vendor:

• SELECT VENDOR_ID, PARAMETER_NAME, PARAMETER_VALUE FROM WSH.WSH_ITM_VENDOR_PARAMETERS WHERE VENDOR_ID = :vendor_id;
• SELECT p.VENDOR_ID, p.PARAMETER_VALUE FROM WSH_ITM_VENDOR_PARAMETERS p WHERE p.PARAMETER_NAME = 'REQUEST_VERSION'; — to identify all vendors on a specific request version.
• Joining to the parent to enrich reporting: SELECT v.VENDOR_NAME, p.PARAMETER_NAME, p.PARAMETER_VALUE FROM WSH_ITM_VENDORS v JOIN WSH_ITM_VENDOR_PARAMETERS p ON v.VENDOR_ID = p.VENDOR_ID;

Reporting use cases include auditing which vendors have non-default parameters, tracking configuration drift after upgrades, and validating that mandatory parameters exist before enabling a vendor for live shipping.

Related Objects

• WSH_ITM_VENDORS — the parent table; joined on WSH_ITM_VENDOR_PARAMETERS.VENDOR_ID = WSH_ITM_VENDORS.VENDOR_ID. This is the only documented foreign key relationship and the primary dependency.
• WSH_ITM_VENDOR_PARAMETERS_PK — the primary key constraint on VENDOR_PARAMETER_ID.
• WSH_ITM_VENDOR_PARAMETERS_U1 — the unique index on VENDOR_PARAMETER_ID, supporting efficient single-row retrieval.
• Shipping Execution vendor/integration APIs and concurrent programs that consume vendor parameters when constructing outbound requests to carriers and logistics providers.

Because the metadata documents only the WSH_ITM_VENDORS relationship, integrators should validate additional dependencies against their specific 12.1.1 or 12.2.2 instance before assuming broader referential scope.