Search Results ahl_osp_order_lines




Overview
Explore in AI Chat

Overview

The AHL_OSP_ORDER_LINES table is a core data object within the Oracle E-Business Suite (EBS) module for Complex Maintenance, Repair, and Overhaul (CMRO), designated by the AHL product code. This table serves as the central repository for storing individual line items associated with Outside Processing (OSP) orders. In the CMRO context, OSP orders are used to procure services or materials from external suppliers for specific work orders, such as specialized repairs, part refurbishment, or testing. The table's primary role is to establish and maintain the detailed linkage between a work order's requirements, the procurement documents (purchase orders or requisitions), and any associated sales order lines for returns or shipments, thereby enabling end-to-end tracking of outsourced service activities.

Key Information Stored

The table's structure is defined by its primary and foreign key relationships, which indicate the critical data points it manages. The primary key, OSP_ORDER_LINE_ID, uniquely identifies each record. The most significant columns are foreign keys that create essential integrations with other EBS modules. The OSP_ORDER_ID links the line to its parent header in the AHL_OSP_ORDERS_B table. The WORKORDER_ID ties the line to a specific maintenance work order in the AHL_WORKORDERS table. For procurement integration, PO_LINE_ID and PO_REQ_LINE_ID connect the OSP line to a finalized purchase order line (PO_LINES_ALL) or a purchase requisition line (PO_REQUISITION_LINES_ALL), respectively. Furthermore, OE_SHIP_LINE_ID and OE_RETURN_LINE_ID provide integration with Order Management (OE_ORDER_LINES_ALL) for scenarios involving the shipment of assets for service or their return.

Common Use Cases and Queries

This table is pivotal for reporting and process tracking in CMRO operations. Common use cases include generating reports on all outsourced services for a given work order, reconciling supplier invoices against OSP order lines, and tracking the status of parts sent out for service. A typical query would join AHL_OSP_ORDER_LINES to its related tables to provide a comprehensive view. For example, to list all OSP lines for a specific work order with their procurement status:

  • SELECT aool.osp_order_line_id, aool.osp_order_id, aob.order_number, pol.segment1 po_number, awo.workorder_number FROM ahl_osp_order_lines aool JOIN ahl_workorders awo ON aool.workorder_id = awo.workorder_id JOIN ahl_osp_orders_b aob ON aool.osp_order_id = aob.osp_order_id LEFT JOIN po_lines_all pol ON aool.po_line_id = pol.po_line_id WHERE awo.workorder_number = 'WO-12345';

Another critical scenario involves warranty recovery, where the table is referenced by AHL_WARRANTY_ENTITLEMENTS to determine if an OSP service cost is covered under warranty.

Related Objects

The AHL_OSP_ORDER_LINES table sits at a major integration nexus within EBS. Its primary relationships, as documented, are:

  • Parent Table: AHL_OSP_ORDERS_B (via OSP_ORDER_ID).
  • Core CMRO Link: AHL_WORKORDERS (via WORKORDER_ID).
  • Procurement Integration: PO_LINES_ALL, PO_REQUISITION_LINES_ALL, and PO_LINE_TYPES_B.
  • Order Management Integration: OE_ORDER_LINES_ALL (for both shipment and return lines).
  • Child/Dependent Object: AHL_WARRANTY_ENTITLEMENTS, which uses the OSP_ORDER_LINE_ID to associate warranty claims with specific OSP services.

These relationships underscore the table's function in orchestrating the flow of information between maintenance execution, procurement, and order fulfillment processes.