Search Results csm_orders_pkg




Overview
Explore in AI Chat

Overview

APPS.CSM_ORDERS_PKG is a server-side PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Field Service / Service (CSM and CSP) family of APIs, which govern the service order lifecycle, receiving of materials against service orders, and the downstream propagation of order-related events to install-base and serial-number tracking. The package is documented as API classification OTHER, meaning it is a supporting internal API rather than a formally published public interface; nonetheless it is a valid, compiled object and forms part of the transactional backbone used when service orders are received and when client-side changes are applied to those orders.

Its principal responsibilities are to receive an order (and thereby record receipt of parts, requirements, and transactions) and to apply client changes to an existing order context. As a package body it encapsulates the private logic behind the specification, orchestrating calls into the receiving and transactions public APIs, serial number and system item event packages, and the common utility package.

Key Procedures and Functions

The ETRM metadata documents two procedures or functions in this package:

  • RECEIVE_ORDER — Handles the receipt of an order. This is the entry point through which an inbound order or its associated receipt is recorded, driving the creation of receiving headers and lines and the associated service transactions. It coordinates with the CSP receiving views and the CSP transactions public API to persist the receipt.
  • APPLY_CLIENT_CHANGES — Applies client-initiated changes to an order, reconciling the modified order data with the existing records in the service-order and requirement-line tables and propagating resulting events.

No parameter lists or signatures are reproduced here because the ETRM documentation does not expose them; consumers should inspect the package specification for the exact call signatures before invoking the routines.

Tables Accessed

The package accesses the following documented tables through APPS synonyms:

  • CSM_ORDER_LINES_INQ — the service order lines inquiry entity, read to resolve and validate the order lines being received or changed.
  • CSM_REQ_LINE_DETAILS_ACC — the requirement line details access table used to hold and update requirement-level detail for the order.
  • CSP_REQ_LINE_DETAILS — the CSP requirement line details table where line-level detail is persisted as part of the receiving flow.

In addition to these synonyms, the dependency list shows direct references to the CSP receiving views (CSP_RECEIVING_HEADERS_V, CSP_RECEIVING_LINES_V), which supply receipt header and line data, and to event packages (CSM_SERIAL_NUMBERS_EVENT_PKG, CSM_SYSTEM_ITEM_EVENT_PKG) that publish serial-number and system-item events once the order change or receipt is committed. Foundation layer dependencies include FND_API, FND_GLOBAL, FND_LOG, and FND_MSG_PUB, confirming that the package follows the standard EBS API conventions for message handling, logging, and session context.

Usage Notes

CSM_ORDERS_PKG is typically invoked from within the service-order application logic rather than called directly by end users. Common invocation paths include Oracle Forms-based service order and receiving screens, concurrent programs that process or reconcile service orders, and custom extensions that need to post a receipt or apply a client change programmatically. Because the package depends on FND_MSG_PUB and FND_API, callers should initialize the message stack and handle the standard return status before committing. The package is not referenced by any other database object per the ETRM metadata, and it is classified as an internal API; therefore, direct custom calls should be treated as unsupported and validated against each point release. Where the receipt or change must be propagated to install-base data, callers should allow the event packages to complete so that serial-number and system-item events fire correctly.