Results for “ahl_osp_orders_b”

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

Overview

AHL_OSP_ORDERS_B is the base (language-independent) header table within the Oracle E-Business Suite Complex Maintenance Repair and Overhaul (AHL) module, responsible for storing Outside Processing (OSP) order header information. In Oracle EBS 12.1.1 and 12.2.2, this table anchors the OSP order lifecycle, capturing the relationships between a maintenance work order and the third-party supplier who will perform depot-level repair or outside processing on an asset. It is owned by the AHL schema and holds 44 documented columns, with the primary key enforced by AHLOSP_ORDERS_B_PK on OSP_ORDER_ID.

From a Data Vault modeling perspective, the mined relationship structure classifies this table as satellite-leaning. The OSP_ORDER_ID surrogate key, the extensive descriptive attributes (status codes, flags, attributes), and the effectivity-style audit columns suggest a design best modeled as a satellite positioned around an implicit hub of OSP order identity, rather than as a true business hub or junction link.

Key Information Stored

The surrogate primary key is OSP_ORDER_ID. Several unique indexes identify business-key candidates: AHL_OSP_ORDERS_B_U1 (OSP_ORDER_ID), U2 (PO_HEADER_ID), U3 (OE_HEADER_ID), U4 (OSP_ORDER_NUMBER), and U5 (PO_REQ_HEADER_ID). The most significant columns include:

• OSP_ORDER_ID — Surrogate primary key identifying each OSP order header.
• OSP_ORDER_NUMBER — Business-facing user-visible order number (unique).
• ORDER_TYPE_CODE / STATUS_CODE — Classify the OSP order and track its workflow state.
• ORDER_DATE — Date the OSP order was created.
• VENDOR_ID / VENDOR_SITE_ID / VENDOR_CONTACT_ID — Supplier performing the outside processing.
• CUSTOMER_ID — Party (HZ_PARTIES) on whose behalf the order is raised.
• CONTRACT_ID / CONTRACT_TERMS — Service contract governing the repair.
• PO_HEADER_ID / PO_REQ_HEADER_ID / PO_AGENT_ID / PO_SYNCH_FLAG — Purchasing linkage and synchronization state.
• OE_HEADER_ID — Associated order entry (sales order) header.
• OPERATING_UNIT_ID / SECURITY_GROUP_ID — Multi-org and security context.
• ATTRIBUTE1–15 and ATTRIBUTE_CATEGORY — Descriptive Flexfield (DFF) extensibility.
• OBJECT_VERSION_NUMBER / audit columns — Optimistic locking and standard WHO audit tracking.

Common Use Cases and Queries

Typical reporting scenarios include tracking open OSP orders by vendor, reconciling OSP orders against their source PO or OE documents, and measuring cycle time between ORDER_DATE and status transitions. A representative query joining the header to its supplier:

• SELECT o.osp_order_number, o.status_code, v.vendor_name FROM ahl_osp_orders_b o, po_vendors v WHERE o.vendor_id = v.vendor_id;
• Reconciliation between OSP and Purchasing: join on PO_HEADER_ID to PO_HEADERS_ALL to confirm PO_SYNCH_FLAG status.
• Contract compliance reporting by joining CONTRACT_ID to OKC_K_HEADERS_B.
• Line-level expansion via AHL_OSP_ORDER_LINES for item and quantity analysis.

Related Objects

The following objects are most significant for joins and dependency analysis:

• AHL_OSP_ORDERS_TL — Holds translatable (language) columns; joined on OSP_ORDER_ID.
• AHL_OSP_ORDER_LINES — Child detail lines; joined on OSP_ORDER_ID.
• PO_VENDORS — Supplier master; joined on VENDOR_ID.
• PO_HEADERS_ALL — Purchasing document; joined on PO_HEADER_ID.
• OE_ORDER_HEADERS_ALL — Sales order header; joined on OE_HEADER_ID.
• OKC_K_HEADERS_B — Service contract header; joined on CONTRACT_ID.
• HZ_PARTIES — Trading partner/customer; joined on CUSTOMER_ID.
• PO_AGENTS — Buyer; joined on PO_AGENT_ID.
• FND_SECURITY_GROUPS — Security context; joined on SECURITY_GROUP_ID.