Search Results master_organization_name




Overview
Explore in AI Chat

Overview

APPS.WSH_ITM_SERVICE_PREFERENCES_V is a reporting and integration view in the Oracle E-Business Suite Shipping (WSH) module. It exposes item-level service preference configuration, associating each service preference record with a Master Organization and a source application. The view resolves the numeric master_organization_id stored on the underlying table into a human-readable master_organization_name, which is precisely the column a user searches for when they need to identify which inventory master organization a given service preference belongs to. Because the base table WSH_ITM_SERVICE_PREFERENCES holds only the organization identifier, this view is the standard means by which Oracle shipping/order-management reports and concurrent programs present service preference data in a legible form. The view remains consistent across Oracle EBS 12.1.1 and 12.2.2; the ETRM metadata is documented at the 12.2.2 level.

Underlying Base Objects

The view is defined over the following documented objects:

  • WSH_ITM_SERVICE_PREFERENCES (SYNONYM) — the driving table containing the service preference rows, including master_organization_id and application_id.
  • HR_ORGANIZATION_UNITS (VIEW) — the organization definition source. Joined on organization_id = master_organization_id to supply NAME as master_organization_name. This view is itself subject to HR security, and therefore also references HR_GENERAL and HR_SECURITY (both PACKAGEs).
  • FND_APPLICATION_VL (VIEW) — the application lookup, joined on application_id to return APPLICATION_NAME.

The view text is constructed as a UNION ALL of two branches. The first branch inner-joins WSH_ITM_SERVICE_PREFERENCES to HR_ORGANIZATION_UNITS and FND_APPLICATION_VL, returning the organization name. The second branch handles rows where master_organization_id IS NULL, joining only to FND_APPLICATION_VL and returning TO_CHAR(NULL) in the master_organization_name position. Both branches apply a GROUP BY over the selected columns, so the view returns a distinct set of organization/application combinations.

Key Columns

  • MASTER_ORGANIZATION_ID — the organization identifier carried on the base service preference record; the primary key of interest for organization-scoped configuration.
  • MASTER_ORGANIZATION_NAME — the resolved organization name from HR_ORGANIZATION_UNITS.NAME, or NULL when no master organization is assigned. This is the searched column and the principal reason to use the view rather than the base table.
  • APPLICATION_ID — identifier of the application that owns or contextualizes the service preference (for example Order Management or Shipping).
  • APPLICATION_NAME — the application name resolved from FND_APPLICATION_VL.

Common Use Cases and Queries

Typical usage includes validating which master organizations have service preferences defined, building shipping configuration reports, and diagnosing why a preference is not being applied because it is scoped to an unexpected organization or to no organization at all.

List all preferences with organization and application context:

  • SELECT master_organization_id, master_organization_name, application_id, application_name FROM apps.wsh_itm_service_preferences_v ORDER BY master_organization_name, application_name;

Restrict to a single master organization by name:

  • SELECT * FROM apps.wsh_itm_service_preferences_v WHERE master_organization_name = :p_org_name;

Identify global (unassigned) preferences where no master organization exists:

  • SELECT application_id, application_name FROM apps.wsh_itm_service_preferences_v WHERE master_organization_name IS NULL;

Because the view already applies GROUP BY and a UNION ALL, queries should treat it as a read-only reporting source and avoid expecting row-level detail from the base table. Access is subject to the HR security rules applied through HR_ORGANIZATION_UNITS, so the organization names returned are limited to those visible to the querying responsibility.