Search Results ship_to_org_name




Overview
Explore in AI Chat

Overview

APPS.POA_BIS_SAVINGS_ORG_LOV_V is a supplementary database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is registered in the Oracle E-Business Suite data model under FND Design Data identifier PO.POA_BIS_SAVINGS_ORG_LOV_V and currently holds a VALID status. The view belongs to the Procurement (PO) product family and serves the Oracle Procurement and Spend Analytics (BIS — Business Intelligence System) module, as indicated by the POA_BIS naming convention. Its design intent is to simplify form-based coding by providing a pre-joined List of Values (LOV) source for ship-to organization selection.

The view is explicitly classified by Oracle as an internal-use object. Oracle does not support direct access to application data through this object except from standard Oracle Applications programs, and Oracle does not recommend that customers query or alter data using it. Because it is a supplementary view, its definition may change materially across minor or major releases without prior notice, so any custom dependency on its column set carries upgrade risk.

The user search term "ship_to_org_name" corresponds directly to one of the two columns exposed by this view, confirming that this object is the correct reference for resolving ship-to organization names within the analytics LOV context.

Underlying Base Objects

The ETRM dependency listing documents that APPS.POA_BIS_SAVINGS_ORG_LOV_V references the following objects:

The presence of HR_ORGANIZATION_UNITS establishes that ship-to organizations are resolved from the Human Resources organization hierarchy, where inventory organizations and operating units are maintained as organization unit records. HR_SECURITY supplies the organization security profile logic, restricting the LOV to organizations the querying user is authorized to access. HR_GENERAL provides supporting HR utility logic used in the view definition or its function-based components. Notably, the view is not referenced by any other database object, confirming it functions as a terminal LOV source rather than an intermediate layer in a dependency chain. The documented metadata for ETRM 12.2.2 lists no additional base tables beyond these, and the view is not documented as a synonym or materialized variant.

Key Columns

The view exposes exactly two columns, which are listed in the ETRM column specification:

  • SHIP_TO_ORG_ID (NUMBER, length 15) — The unique identifier of the ship-to organization. This is the value typically stored as the foreign key in transactional tables such as purchase orders, requisitions, or receipts. It is sourced from the organization unit identifier in HR_ORGANIZATION_UNITS.
  • SHIP_TO_ORG_NAME (VARCHAR2, length 240) — The descriptive name of the ship-to organization, presented for display in LOV windows and analytical reports. This is the column matching the user search term.

Neither column is marked mandatory in the metadata, reflecting the outer-join behavior typical of LOV views, where an organization may lack a resolved name in edge cases. The name column's 240-character length aligns with the standard organization name width in HR_ORGANIZATION_UNITS.

Common Use Cases and Queries

This view is used primarily to populate ship-to organization LOV fields on Oracle Procurement and Spend Analytics dashboards and on internal forms that require an organization selection list filtered by HR security. A typical query retrieves the identifier and name for presentation:

  • SELECT SHIP_TO_ORG_ID, SHIP_TO_ORG_NAME FROM APPS.POA_BIS_SAVINGS_ORG_LOV_V;
  • Joining transactional data to resolve names: SELECT po.segment1, v.ship_to_org_name FROM po_headers_all po, apps.poa_bis_savings_org_lov_v v WHERE po.ship_to_org_id = v.ship_to_org_id;
  • Filtering by name for a specific location: SELECT ship_to_org_id FROM apps.poa_bis_savings_org_lov_v WHERE ship_to_org_name LIKE 'WH%';

Because the view applies HR_SECURITY logic, results are implicitly limited to organizations the session user may access, which makes it convenient for secured LOVs but unsuitable for unrestricted data extraction. When a stable, documented source is required for custom reporting, the underlying HR_ORGANIZATION_UNITS table with an explicit security predicate is generally preferred over direct use of this internal view.