Search Results wsh_itm_parameter_setups_b




Overview
Explore in AI Chat

Overview

WSH_ITM_PARAMETER_SETUPS_B is a Shipping Execution (WSH) base table in the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. It stores the non-translatable, language-independent attributes of Parameter Setup records used to configure the Java middle tier of the shipping adapter. Each row defines a named configuration parameter, its active value, its default value, and whether the parameter may be maintained by end users. In this respect the table functions as the operational registry that the adapter reads when it initializes or refreshes its runtime configuration.

Following heuristic Data Vault classification derived from the foreign-key structure, WSH_ITM_PARAMETER_SETUPS_B is hub-leaning. That is a modeling suggestion rather than a physical fact: PARAMETER_ID behaves as a durable business key around which descriptive and translatable attributes are organized, with WSH_ITM_PARAMETER_SETUPS_TL acting as a dependent satellite carrying the translated text. The presence of ZD_EDITION_NAME in the unique index reflects the editioning support introduced in the 12.2.x architecture, allowing multiple editions of the same logical parameter identifier to coexist.

Key Information Stored

The documented physical schema comprises eleven columns. The most significant are:

  • PARAMETER_ID — the surrogate primary key, enforced by WSH_ITM_PARAMETER_SETUPS_B_PK, and the column through which the translated table joins back to this base table.
  • PARAMETER_NAME — the internal name that identifies the configuration parameter to the adapter.
  • VALUE — the currently effective value applied to the Java middle tier configuration.
  • DEFAULT_VALUE — the seeded value restored when a setup is reset or when no override exists.
  • USER_SETTABLE — a flag indicating whether the parameter is exposed for user maintenance or is reserved for internal control.
  • ZD_EDITION_NAME — the edition discriminator; together with PARAMETER_ID it forms the unique business-key candidate WSH_ITM_PARAMETER_SETUPS_B_U1.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns used for change tracking and reconciliation.

The distinction between the surrogate key (PARAMETER_ID alone) and the business-key candidate (PARAMETER_ID plus ZD_EDITION_NAME) is important in 12.2.x, where edition-aware queries must include the edition column to avoid ambiguous matches.

Common Use Cases and Queries

Typical scenarios include auditing adapter configuration, comparing active values against seeded defaults, identifying parameters that have been customized, and verifying which parameters are eligible for user maintenance. A common diagnostic query lists parameters whose current value differs from the default:

  • SELECT parameter_id, parameter_name, value, default_value, user_settable FROM wsh.wsh_itm_parameter_setups_b WHERE value <> default_value ORDER BY parameter_name;
  • SELECT parameter_id, parameter_name, value FROM wsh.wsh_itm_parameter_setups_b WHERE user_settable = 'Y' ORDER BY parameter_name;
  • SELECT b.parameter_id, b.parameter_name, t.description FROM wsh.wsh_itm_parameter_setups_b b, wsh.wsh_itm_parameter_setups_tl t WHERE b.parameter_id = t.parameter_id AND t.language = USERENV('LANG');

Reporting is usually confined to setup validation and support investigation rather than transactional analytics, since the table holds configuration rather than shipment activity.

Related Objects

The documented relationships center on the translatable companion table and the adapter that consumes the configuration:

  • WSH_ITM_PARAMETER_SETUPS_TL — joined on WSH_ITM_PARAMETER_SETUPS_TL.PARAMETER_ID to WSH_ITM_PARAMETER_SETUPS_B.PARAMETER_ID; supplies language-specific parameter descriptions.
  • WSH_ITM_PARAMETER_SETUPS_B_PK — the primary key constraint on PARAMETER_ID.
  • WSH_ITM_PARAMETER_SETUPS_B_U1 — the unique index on PARAMETER_ID and ZD_EDITION_NAME.
  • Shipping Execution adapter configuration and setup user interfaces that read and update parameter values at runtime.
  • Standard audit and concurrency objects referenced through the CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN columns, such as FND_USER and the FND logins view.

Because the table is a base (non-translatable) repository, any query that requires user-facing text must join to WSH_ITM_PARAMETER_SETUPS_TL.