Search Results wsh_itm_parameter_setups_b_u1

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

Overview

WSH.WSH_ITM_PARAMETER_SETUPS_B is a seeded configuration table in the Oracle E-Business Suite Shipping (WSH) schema. It stores the non-translatable, language-independent attributes of the Parameter Setup records that govern the behavior of the Java middle-tier adapter used by Oracle Transportation Management and shipping integration components. Each row defines a single configurable parameter, its currently effective value, the seeded default value, and a flag indicating whether end users are permitted to override the seeded value.

The table resides in the APPS_TS_SEED tablespace, which confirms its role as reference and setup data delivered with the application rather than transactional data generated by users. The heuristic Data Vault classification for this object is hub-leaning: PARAMETER_ID functions as a stable surrogate key identifying each parameter, while the descriptive and value-bearing attributes (VALUE, DEFAULT_VALUE, USER_SETTABLE) behave like satellite attributes. In a Data Vault model, this table would most naturally decompose into a parameter hub keyed on PARAMETER_ID, with a satellite capturing the mutable value and user-settable attributes.

Key Information Stored

The most significant columns are:

• PARAMETER_ID — Surrogate primary key (NUMBER), uniquely identifying each parameter setup record. This is the single-column PK defining WSH_ITM_PARAMETER_SETUPS_B_PK.
• PARAMETER_NAME — VARCHAR2(30) business identifier for the adapter parameter.
• VALUE — VARCHAR2(240) current effective value applied by the middle tier.
• DEFAULT_VALUE — VARCHAR2(240) seeded default, used for comparison and reset purposes.
• USER_SETTABLE — Y/N flag; when 'N', the user cannot change the parameter value.
• ZD_EDITION_NAME — VARCHAR2(30) editioning column supporting Edition-Based Redefinition.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns tracking creation and modification.

Two unique index candidates are documented. The unique index WSH_ITM_PARAMETER_SETUPS_B_U1 covers (PARAMETER_ID, ZD_EDITION_NAME), and this same pair forms the business-key candidate under editioning. PARAMETER_ID also serves as the sole PK column, so the surrogate key and the edition-scoped business key are closely related.

Common Use Cases and Queries

Typical scenarios include auditing seeded versus user-modified parameters, identifying which parameters administrators are permitted to change, and diagnosing adapter configuration drift. A common query retrieves all parameters where the effective value diverges from the seeded default:

• SELECT parameter_name, value, default_value FROM wsh.wsh_itm_parameter_setups_b WHERE value <> default_value;
• SELECT parameter_name, value FROM wsh.wsh_itm_parameter_setups_b WHERE user_settable = 'Y';
• SELECT parameter_name, value FROM wsh.wsh_itm_parameter_setups_b WHERE parameter_id = :id;

Because ZD_EDITION_NAME participates in the unique key, queries run under Edition-Based Redefinition should filter or join on the active edition to avoid returning rows from non-current editions. Reporting use cases include setup reconciliation before patching, parameter inventory for documentation, and troubleshooting when the Java adapter behaves inconsistently after a clone or upgrade.

Related Objects

The primary documented relationship is with the translation table WSH_ITM_PARAMETER_SETUPS_TL, which references this base table through PARAMETER_ID. The translation table holds the language-specific descriptive text, while this base table holds the non-translatable parameter values. Additional related objects within the WSH shipping schema include the adapter configuration views and the parameter setup UI that read from these tables. When joining, always link WSH_ITM_PARAMETER_SETUPS_B.PARAMETER_ID to WSH_ITM_PARAMETER_SETUPS_TL.PARAMETER_ID to obtain translated names alongside the effective values.