Results for “osp_order_number”

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

Overview

AHL_OSP_ORDERS_VL is an APPS-owned database view in Oracle E-Business Suite, part of the AHL (Complex Maintenance Repair and Overhaul) product family. Its purpose is to expose complete OutSide Processing (OSP) order information in a single, language-aware queryable interface. OSP orders represent work dispatched to an external vendor for repair, overhaul, or third-party processing — a core transaction type in aerospace and defense MRO operations.

The view is a "_VL" (View with Language) construct, meaning it joins a transactional base table to a translation table and filters by USERENV('LANG'). This design allows descriptions to be returned in the session's language while the operational attributes remain language-independent. The view is marked VALID in both Oracle EBS 12.1.1 and 12.2.2, and is documented in the ETRM metadata repository.

Because AHL_OSP_ORDERS_VL surfaces both OSP-specific fields and Oracle Purchasing cross-references (PO header, agent, batch, and interface identifiers), it acts as a bridging reporting object between the AHL module and Procurement. It is commonly used in custom reports, concurrent program queries, OAF-based pages, and integration extracts where a denormalized, translatable OSP order record is required.

Underlying Base Objects

The view is defined over two synonyms resolving to the following base tables in the APPS schema:

• AHL_OSP_ORDERS_B — the operational (non-translatable) table storing OSP order header records, financial attributes, and vendor/customer relationships.
• AHL_OSP_ORDERS_TL — the translation table holding language-specific descriptive text, joined on OSP_ORDER_ID and filtered by the session language via USERENV('LANG').

The view's text selects all columns from the "_B" table (aliased B) and the DESCRIPTION column from the "_TL" table (aliased T), joined by the common OSP_ORDER_ID key. It also exposes B.ROWID as ROW_ID to support row-level addressing. Because the join filters out translation rows that do not match the session language, callers should ensure the appropriate language context is active.

Key Columns

The view exposes more than forty columns. The most significant include:

• OSP_ORDER_ID — unique identifier of the OSP order; the primary key and join key to both base tables.
• OSP_ORDER_NUMBER — the user-visible OSP order number.
• ORDER_TYPE_CODE, STATUS_CODE — classification and lifecycle state of the order.
• PO_HEADER_ID, PO_AGENT_ID, PO_BATCH_ID, PO_REQUEST_ID, PO_SYNCH_FLAG, PO_INTERFACE_HEADER_ID — Purchasing linkage fields enabling reconciliation between the OSP order and its associated PO. PO_AGENT_ID identifies the buyer/agent responsible for the linked purchase order.
• VENDOR_ID, VENDOR_SITE_ID, CUSTOMER_ID, CONTRACT_ID, CONTRACT_TERMS — party and contractual context.
• ORDER_DATE, OPERATING_UNIT_ID — organizational and temporal attributes.
• SINGLE_INSTANCE_FLAG, OE_HEADER_ID — linkage to order entry and instance-level processing.
• ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY — the standard DFF extensibility block.
• DESCRIPTION — the translated descriptive text from AHL_OSP_ORDERS_TL.
• ROW_ID — the ROWID from the base table, useful for update-oriented logic.

Common Use Cases and Queries

Typical scenarios include listing open OSP orders, reconciling OSP orders to their purchasing documents, and reporting by buyer. To find OSP orders associated with a particular agent:

• SELECT o.osp_order_number, o.order_type_code, o.status_code, o.po_agent_id FROM ahl_osp_orders_vl o WHERE o.po_agent_id = :p_agent_id;
• Joining to PO_HEADERS_ALL on po_header_id to retrieve buyer and supplier details.
• Filtering by operating_unit_id and order_date for period-based reporting.
• Aggregating counts by status_code to monitor OSP pipeline volume.

Because the view joins to the translation table, all queries require a valid session language context; applications should not bypass the view when multilingual descriptions are required.