Results for “postal_code”

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

Overview

OE_SHIP_FROM_ORGS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and classified under the ONT (Order Management) product family. Its documented purpose is to expose "Ship From Organizations" — the set of inventory organizations that can legitimately be designated as the originating warehouse or facility on an order line, delivery, or shipment. Because shipping and fulfillment logic in Order Management depends on identifying a valid ship-from inventory organization, this view functions as a lightweight, security-filtered lookup rather than a transactional entity. It is commonly consumed in reports, concurrent programs, and integration layers that must resolve an organization identifier to a human-readable name and code before presenting or transmitting shipping information.

In both 12.1.1 and 12.2.2 the view remains a compatibility and convenience object. It abstracts the multi-table join required to confirm that an organization is an inventory-enabled organization, so callers do not need to re-implement that logic themselves.

Underlying Base Objects

The documented view text joins three sources. HR_ORGANIZATION_UNITS supplies the organization NAME and ORGANIZATION_ID. MTL_PARAMETERS supplies the companion inventory organization record and is joined on ORGANIZATION_ID, ensuring only organizations defined as inventory organizations are returned. HR_ORGANIZATION_INFORMATION supplies the classification rows, filtered by ORG_INFORMATION1 = 'INV' and ORG_INFORMATION2 = 'Y', which confirms the organization's inventory designation and active flag.

ETRM also records the following referenced base objects: HR_GENERAL (PACKAGE), HR_ORGANIZATION_INFORMATION (SYNONYM), HR_ORGANIZATION_UNITS (VIEW), HR_SECURITY (PACKAGE), and MTL_PARAMETERS (SYNONYM). The presence of HR_SECURITY and HR_GENERAL indicates that the view is subject to Oracle HRMS organization security, so the rows returned may be restricted by the security profile of the querying responsibility. This is significant for reporting, as two users with different HR security profiles can legitimately see different result sets from the same view.

Key Columns

• ORGANIZATION_ID — The inventory organization identifier, used as the foreign key in order, delivery, and shipping tables.
• ORGANIZATION_CODE — The short inventory organization code from MTL_PARAMETERS, typically the value users recognize on shipping documents.
• NAME — The descriptive organization name from HR_ORGANIZATION_UNITS.
• LOCATION_CODE, ADDRESS_LINE_1..3, REGION_1..3, TOWN_OR_CITY, POSTAL_CODE, COUNTRY, LOCATION_ID — Address-related columns defined in the view's column list. In the documented view text these columns are populated with NULL placeholders, meaning address data is not materialized by this definition and must be sourced from a dedicated location view if required.

Common Use Cases and Queries

Typical scenarios include populating ship-from organization list-of-values in custom forms, validation during order import or interface processing, and reporting on fulfillment activity by source warehouse. A representative query follows.

• List all valid ship-from organizations: SELECT organization_id, organization_code, name FROM oe_ship_from_orgs_v ORDER BY organization_code;
• Resolve a specific organization: SELECT name FROM oe_ship_from_orgs_v WHERE organization_id = :p_org_id;
• Drive a shipping report: join order lines or deliveries to this view on ORGANIZATION_ID to display the ship-from code and name.

Because HR security applies, developers should test queries under the target responsibility and confirm that address columns, where required, are obtained from an appropriate location source rather than from this view's placeholder columns.