Results for “ahl_osp_orders_v”

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

Overview

APPS.AHL_OSP_ORDERS_V is a reporting view within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments, owned by the APPS schema and defined over the Complex Maintenance Repair and Overhaul (AHL) product family. Its purpose is to consolidate all header-level attributes associated with an Outside Processing (OSP) order into a single denormalized result set, resolving foreign keys into their user-facing descriptive values. The view joins the OSP base and translation tables with purchasing, order management, contract, customer, vendor, and lookup sources so that a single query returns the OSP order number, its type and status meanings, the linked shipment, vendor and vendor site, customer party, contract, buyer, and descriptive text.

This view is typically consumed by OSP workbench inquiries, custom concurrent programs, and reporting extracts that need a flattened picture of OSP orders without traversing the individual transactional tables. The searched term po_agents_name_v is relevant here because that view supplies the buyer name: AHL_OSP_ORDERS_V joins PO_AGENTS_NAME_V as the alias BUYERS on PO_AGENT_ID, which is how the BUYER column is derived.

Underlying Base Objects

The documented view text selects from AHL_OSP_ORDERS_B (alias B) and AHL_OSP_ORDERS_TL (alias T), joined on OSP_ORDER_ID with the language condition T.LANGUAGE = USERENV('LANG'). The metadata further lists AHL_OSP_ORDERS_VL, PO_HEADERS_V, OE_ORDER_HEADERS_ALL, and FND_LOOKUP_VALUES_VL among the joined sources in the descriptive summary. Additional documented base objects include PO_AGENTS_NAME_V (buyer), HZ_PARTIES (customer), PO_VENDORS and PO_VENDOR_SITES_ALL (supplier and site), OKC_K_HEADERS_B (contract), and FND_LOOKUP_VALUES three times (aliases FND, FND1, FND2) for status and order type meanings. Supporting packages and objects referenced in the dependency list are FND_GLOBAL, HR_GENERAL, HR_SECURITY, MO_GLOBAL, and PO_BUYER_WORKLOAD_SV.

Two structural characteristics are significant. First, the view enforces operating unit security through the predicate on OPERATING_UNIT_ID derived from USERENV('CLIENT_INFO'), with a default of -99 when client information is absent. Second, an explicit filter B.PO_HEADER_ID IS NULL constrains the result to OSP orders that have not yet been linked to a purchase order header; the PO_NUMBER column is consequently selected as a literal NULL in this definition.

Key Columns

• OSP_ORDER_ID, OSP_ORDER_NUMBER, ORDER_TYPE_CODE, ORDER_TYPE — unique identifier, order number, and its decoded lookup meaning.
• STATUS_CODE, STATUS — OSP order status code and its FND lookup meaning.
• ORDER_DATE, SINGLE_INSTANCE_FLAG, SINGLE_INSTANCE_MEANING — creation context and single-instance indicator.
• OE_HEADER_ID, SHIPMENT_NUMBER — link to OE_ORDER_HEADERS_ALL and the associated order number.
• VENDOR_ID, VENDOR, VENDOR_SITE_ID, VENDOR_LOCATION — supplier party, name, site, and site code.
• CUSTOMER_ID, CUSTOMER — customer party identifier and party name from HZ_PARTIES.
• CONTRACT_ID, CONTRACT_NUMBER, CONTRACT_TERMS — service contract linkage.
• PO_AGENT_ID, BUYER — purchasing agent identifier and buyer full name resolved through PO_AGENTS_NAME_V.
• PO_SYNCH_FLAG, PO_BATCH_ID, PO_REQUEST_ID, PO_INTERFACE_HEADER_ID — purchasing synchronization and interface tracking.
• ROW_ID, OBJECT_VERSION_NUMBER, audit columns, ATTRIBUTE1–15, SECURITY_GROUP_ID, DESCRIPTION — concurrency control, audit trail, descriptive flexfields, and translated description.

Common Use Cases and Queries

The view supports OSP order monitoring, buyer workload analysis, and supplier-facing extracts. A typical inquiry filters by operating unit implicitly and returns decoded status and buyer for a given vendor.

SELECT osp_order_number, order_type, status, buyer, vendor,
       vendor_location, order_date
FROM   apps.ahl_osp_orders_v
WHERE  vendor_id = :p_vendor_id
ORDER  BY order_date DESC;

Because BUYER originates from PO_AGENTS_NAME_V, the view is frequently used in place of a manual join to that object when reporting on purchasing responsibility. Integration use cases include populating custom staging tables for downstream procurement analytics and feeding workload dashboards that aggregate open OSP orders by buyer or status. Queries should respect the operating unit predicate and treat the PO_NUMBER column as non-populated in this definition.