Results for “ahl_osp_order_lines_v”

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

Overview

AHL_OSP_ORDER_LINES_V is an Oracle E-Business Suite 12.1.1 / 12.2.2 view owned by the APPS schema within the AHL (Complex Maintenance Repair and Overhaul) product family. It presents comprehensive information about outside processing (OSP) order lines — the line-level detail of work that is sent to an external supplier for processing as part of a maintenance or overhaul work order. The view joins the base order-line repository table AHL_OSP_ORDER_LINES to the work-order view AHL_WORKORDERS_OSP_V and to item-instance and item-master sources to enrich each row with descriptive context. Because it consolidates status descriptions, purchase-order line information, work-order identifiers, project references, and item numbering in a single denormalized result set, the view functions as the primary reporting and integration surface for OSP order-line data. Its use of the MO_GLOBAL and HR_SECURITY packages in the documented dependency list confirms that it participates in Oracle's multi-org and security-group access model, making it suitable for use both in operational reporting and in custom integrations that must respect organizational access controls.

Underlying Base Objects

The view is defined over a mix of base tables, synonyms, and other views. The driving table is AHL_OSP_ORDER_LINES (aliased LI), which stores the OSP order-line records themselves. Each line is joined to AHL_WORKORDERS_OSP_V (WO) on WORKORDER_ID, supplying the parent work-order attributes. Scalar subqueries against FND_LOOKUP_VALUES_VL translate STATUS_CODE into a user-facing status meaning via the AHL_OSP_LINE_STATUS_TYPE lookup, and against PO_LINE_TYPES to resolve the purchase-order line type description. The item number is derived by a correlated lookup on MTL_SYSTEM_ITEMS_KFV using SERVICE_ITEM_ID and the work order's organization. An outer join to CSI_ITEM_INSTANCES (CSI) relates exchanged or returned item instances through EXCHANGE_INSTANCE_ID. Additional documented references include AHL_OSP_ORDERS_B, HR_GENERAL, HR_SECURITY, and MO_GLOBAL, which supply organizational and security context to the view's results.

Key Columns

• OSP_ORDER_LINE_ID, OSP_ORDER_ID, OSP_LINE_NUMBER — primary identifiers for the order line and its parent OSP order.
• STATUS_CODE and derived STATUS — the line's processing status and its translated meaning.
• SERVICE_ITEM_ID, SERVICE_ITEM_NUMBER, SERVICE_ITEM_DESCRIPTION, SERVICE_ITEM_UOM_CODE — the service item requested; SERVICE_ITEM_NUMBER is resolved from MTL_SYSTEM_ITEMS_KFV.CONCATENATED_SEGMENTS, which is why a search on service_item_number returns this view rather than a base table.
• QUANTITY, NEED_BY_DATE, SHIP_BY_DATE — quantity and scheduling attributes for the OSP line.
• PO_LINE_TYPE_ID and PO_LINE_TYPE, PO_LINE_ID, OE_SHIP_LINE_ID, OE_RETURN_LINE_ID — purchasing and order-entry linkage used for supplier execution.
• WORKORDER_ID, OPERATION_ID, and the WO-derived JOB_NUMBER, WO_PART_NUMBER, SERIAL_NUMBER, ITEM_INSTANCE_NUMBER — work-order and asset context.
• PROJECT_ID, PROJECT_NAME, PROJECT_TASK_ID, PROJECT_TASK_NAME — project and task charging information.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard DFF flexfield columns for extensibility.
• SECURITY_GROUP_ID, LAST_UPDATE_DATE, CREATED_BY — audit and security columns.

Common Use Cases and Queries

The view is typically queried to report on OSP work-in-progress, to reconcile service items routed to suppliers, and to expose OSP line detail to external systems. A common requirement is to locate lines by service item number:

SELECT osp_line_number, service_item_number, service_item_description, quantity, status, need_by_date FROM ahl_osp_order_lines_v WHERE service_item_number = :item_number;

Reporting by work order and status is equally common:

SELECT job_number, osp_line_number, service_item_number, serial_number, status FROM ahl_osp_order_lines_v WHERE workorder_id = :workorder_id ORDER BY osp_line_number;

Note the view's built-in filter: it returns only lines where PO_LINE_ID IS NULL or the status is PO_DELETED, so it is best suited to pre-purchasing or cancelled-line reporting rather than to committed PO lines. Because MO_GLOBAL and HR_SECURITY govern access, queries should be run after initializing the appropriate organization or security context to avoid cross-operating-unit leakage.