Search Results ahl_osp_orders_b




Overview
Explore in AI Chat

Overview

The AHL_OSP_ORDERS_B table is a core data object within the Oracle E-Business Suite (EBS) module for Complex Maintenance, Repair, and Overhaul (AHL). It functions as the primary header table for Outsource Service Provider (OSP) orders. An OSP order represents a formal business document used to manage and track maintenance, repair, or overhaul work that is outsourced to an external vendor or service provider. This table serves as the central repository for the administrative and transactional metadata of these orders, linking them to other critical EBS entities such as purchase orders, sales orders, contracts, and customer and supplier records. Its role is integral to the end-to-end process of managing outsourced service work within the AHL product family.

Key Information Stored

The table stores the header-level attributes for each OSP order. Its primary key is the OSP_ORDER_ID, which uniquely identifies each record. As indicated by its foreign key relationships, the table holds key reference identifiers that integrate the OSP order with other EBS modules. These include VENDOR_ID (linking to PO_VENDORS), CUSTOMER_ID (linking to HZ_PARTIES), PO_HEADER_ID (linking to PO_HEADERS_ALL), OE_HEADER_ID (linking to OE_ORDER_HEADERS_ALL), CONTRACT_ID (linking to OKC_K_HEADERS_B), and PO_AGENT_ID (linking to the purchasing agent in PO_AGENTS). This structure allows the OSP order to be a nexus point between procurement, sales, service contracts, and trading partner information.

Common Use Cases and Queries

This table is central to reporting and process flows involving outsourced service work. Common operational scenarios include tracking the status of all active OSP orders, reconciling OSP orders with their associated purchase orders or customer sales orders, and analyzing vendor performance for outsourced repairs. A typical reporting query might join AHL_OSP_ORDERS_B with its transactional child table, AHL_OSP_ORDER_LINES, and vendor or customer tables to create a detailed work order summary. For integration purposes, a common query pattern is to select OSP orders where the PO_HEADER_ID is null to identify orders pending procurement creation, or to find all OSP orders linked to a specific customer contract via the CONTRACT_ID.

Related Objects

The AHL_OSP_ORDERS_B table has several key dependencies. It is the parent table for AHL_OSP_ORDER_LINES, which stores the individual line items for each OSP order. Its translated descriptive flexfield (DFF) or language-specific descriptions are stored in the related AHL_OSP_ORDERS_TL table, linked via the OSP_ORDER_ID. As documented, it maintains foreign key relationships with fundamental EBS tables: PO_VENDORS and PO_AGENTS (Purchasing), HZ_PARTIES (Trading Community Architecture), OE_ORDER_HEADERS_ALL (Order Management), PO_HEADERS_ALL (Purchasing), and OKC_K_HEADERS_B (Contracts Core). These relationships are critical for the seamless operation of cross-modular business processes in EBS.