Search Results delete_ib_transaction

Overview

APPS.AHL_OSP_SHIPMENT_PUB is a public PL/SQL API package that belongs to the Oracle Enterprise Asset Management (eAM) and Depot Repair / Service family of modules. Its identifier prefix, AHL, identifies it as part of the Oracle Advanced Service / Service Logistics schema, and the suffix PUB confirms it is a published API intended for external invocation. The package governs the shipment lifecycle of Outside Processing (OSP) orders — work orders in which part of the manufacturing or repair activity is performed by an external vendor or supplier rather than in-house.

The header comment of the source file (AHLPOSHB.pls) indicates the package was last revised in the 12.2.x code line, consistent with its availability across Oracle EBS 12.1.1 and 12.2.2. Internally the package manipulates Order Management (OM) structures through OE_ORDER_PUB record and table types, and it treats OE_ORDER_LINES_ALL as the source transaction table. Dispatch and return movements are represented through the transaction types OM_SHIPMENT and RMA_RECEIPT respectively, and Install Base (CSI) relationships are tagged with the source line reference AHL_OSP_ORDER_LINES.

Key Procedures and Functions

• PROCESS_ORDER — the principal entry point for creating and processing an OSP shipment order; it assembles the Order Management header, line, adjustment, price attribute, and sales credit structures used by OE_ORDER_PUB.
• BOOK_ORDER — drives the OSP order to booked status once the shipment data has been validated and processed.
• DELETE_CANCEL_ORDER — removes or cancels an existing OSP shipment order, typically when the underlying service or loan/borrow demand is no longer required.
• IS_ORDER_HEADER_CLOSED — a predicate used to determine whether the OSP order header is in a closed state, gating further ship or return processing.
• CONVERT_SUBTXN_TYPE — translates business sub-transaction types (such as ship-loaner or return-for-repair categorisation, held as internal constants) into the values expected by the Order Management transaction type model.
• HANDLE_VENDOR_CHANGE — manages the impact of changing the performing vendor on an existing OSP order, keeping vendor-customer and item-vendor relationships in step.
• IS_PART_CHG_VALID_FOR_OSPLINE — validates whether a proposed item substitution is permissible for a given OSP order line.
• PROCESS_OSP_SERIALNUM_CHANGE — orchestrates the change of serial number on an OSP line, which requires corresponding updates to item instances and their lot/serial attributes.
• CREATE_IB_TRANSACTION — creates the Install Base transaction associated with a shipment, linking the dispatched item instance to its order line reference.
• DELETE_IB_TRANSACTION — reverses or removes the Install Base transaction when a shipment is cancelled or returned.

Tables Accessed

The package reads and writes a consistent set of operational and configuration tables through APPS synonyms. OSP order structure is held in AHL_OSP_ORDERS_B and AHL_OSP_ORDER_LINES, with AHL_VISITS_B and AHL_VISIT_TASKS_B supplying the service visit context and AHL_WORKORDERS the parent work order. Vendor and item configuration is validated against AHL_ITEM_VENDOR_RELS, AHL_VENDOR_CUSTOMER_RELS, and AHL_INV_SERVICE_ITEM_RELS. Install Base activity is recorded in CSI_ITEM_INSTANCES, CSI_I_PARTIES, CSI_II_RELATIONSHIPS, CSI_INSTALL_PARAMETERS, CSI_TXN_TYPES, and CSI_IEA_VALUES. Serial-controlled inventory references are confirmed via MTL_LOT_NUMBERS. Order Management data itself is accessed through OE_ORDER_LINES_ALL.

Usage Notes

AHL_OSP_SHIPMENT_PUB is normally invoked indirectly — from the Outside Processing shipment and receipt forms in the Service / Depot Repair responsibility, from concurrent programs that batch-process OSP dispatches and returns, or from other AHL packages (the metadata records that it is referenced by five additional packages). Custom code should call the documented procedures rather than manipulating the underlying tables, so that Order Management, Install Base, and serial/lot records remain synchronised. Because shipped OSP lines are tied to OE_ORDER_LINES_ALL and to an Install Base transaction, callers must respect the package's transaction-type constants and must invoke the corresponding delete or cancel routines when a shipment is reversed.