Results for “master_organization_id”

50+ results




Overview
Explore in AI Chat

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

Overview

WSH_ITM_SERVICE_PREFERENCES_V is an APPS-owned database view in the Oracle E-Business Suite Shipping Execution (WSH) module. It is a denormalized, reporting-oriented wrapper around the base service preference table WSH_ITM_SERVICE_PREFERENCES. The base table stores item-level service preference assignments that determine how shipping charges, freight terms, and carrier service levels are applied to items during outbound shipment processing. The view enriches those raw keys with human-readable descriptions so that operational users, reports, and integrations do not need to resolve organization and application identifiers manually.

The view is registered as VALID in ALL_OBJECTS and is present in both EBS 12.1.1 and 12.2.2. Its primary role is to support inquiry and reporting: it resolves the master organization name from HR_ORGANIZATION_UNITS and the owning application name from FND_APPLICATION_VL, producing a readable presentation of service preference configuration across inventory organizations and Oracle applications.

Underlying Base Objects

The view is defined as a GROUP BY … UNION ALL query over three object families, as documented in the ETRM metadata:

  • WSH_ITM_SERVICE_PREFERENCES (referenced in APPS as a SYNONYM over the WSH base table). This is the driving object, supplying MASTER_ORGANIZATION_ID and APPLICATION_ID.
  • HR_ORGANIZATION_UNITS (VIEW). Joined on MASTER_ORGANIZATION_ID = ORGANIZATION_ID to derive MASTER_ORGANIZATION_NAME.
  • FND_APPLICATION_VL (VIEW). Joined on APPLICATION_ID = APPLICATION_ID to derive APPLICATION_NAME. Because this is the VL (translated) view, the application name is returned in the session language.

The documented base-object list also includes HR_GENERAL and HR_SECURITY packages. These are referenced indirectly through HR_ORGANIZATION_UNITS, which is a secured view honoring organization-level access (MO: Security Profile, MO: Operating Unit, and related HR security profiles). Effective row visibility therefore depends on the organization security model applied to the querying user, not solely on grants to the view itself. Referenced HR_ORGANIZATION_UNITS is a view, not a table, so the organization name resolution inherits whatever business-group and classification filters that view applies.

Key Columns

  • MASTER_ORGANIZATION_ID — Numeric identifier of the inventory master organization associated with the service preference row.
  • MASTER_ORGANIZATION_NAME — Organization name from HR_ORGANIZATION_UNITS. The view's second UNION ALL branch explicitly returns TO_CHAR(NULL) here when the base row has a null MASTER_ORGANIZATION_ID, so NULL in this column is a meaningful state representing a preference that is not scoped to any specific master organization.
  • APPLICATION_ID — Identifier of the Oracle application that owns the service preference.
  • APPLICATION_NAME — Translated application name from FND_APPLICATION_VL.

The GROUP BY clauses guarantee distinct combinations of organization and application, eliminating duplicate key pairs that may exist in the base table.

Common Use Cases and Queries

Typical uses include validating service preference setup before a shipping run, auditing which applications have preferences defined for a given warehouse, and feeding the identifiers into downstream WSH APIs. A representative query is:

  • SELECT master_organization_name, application_name FROM apps.wsh_itm_service_preferences_v ORDER BY 1, 2;
  • SELECT * FROM apps.wsh_itm_service_preferences_v WHERE master_organization_id = :org_id;
  • SELECT * FROM apps.wsh_itm_service_preferences_v WHERE master_organization_name IS NULL; — isolates global, organization-independent preferences.
  • SELECT application_name, COUNT(*) FROM apps.wsh_itm_service_preferences_v GROUP BY application_name; — reports the distribution of preferences by owning application.

Because the view exposes only four columns, it is intended for key-and-name lookup rather than full item-level detail. For the underlying preference attributes, query the base table WSH_ITM_SERVICE_PREFERENCES directly, joining the view for descriptive labels.