Search Results mtl_sales_orders_s

Overview

INV_SALESORDER is a public PL/SQL package body owned by the APPS schema that bridges Oracle Inventory and Oracle Order Management in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to create, query, and synchronize sales order records held in the MTL_SALES_ORDERS table — the Inventory-side repository that stores order number and source information for material transactions such as sales order issues, RMA receipts, and internal requisitions — with the authoritative order headers and lines maintained by Order Management.

Because Inventory transactions and Order Management transactions are logically the same business event viewed from two perspectives, the package provides the API layer that keeps both storehouses consistent. It resolves cross-references in both directions, translates a sales order identifier into the corresponding OE_ORDER_HEADERS identifier and back, supports language-translated lookups through FND_LANGUAGES, and raises errors through the standard FND message stack. ETRM classifies it as an "OTHER" API category, and its status is documented as VALID. The package exists as a standalone entity: it is not referenced by any database object, but it is referenced by 41 other packages, all of which depend on its synchronization and lookup services.

Key Procedures and Functions

Seven documented programs make up the package interface:

• CREATE_SALESORDER — Creates a sales order and its associated Inventory-side sales order record. This is the principal entry point used when an order must be established in both MTL_SALES_ORDERS and Oracle Order Management.
• GET_OEHEADER_FOR_SALESORDER — Returns the Order Management order header identifier that corresponds to a given Inventory sales order, enabling foreign-key resolution from Inventory to Order Management.
• GET_SALESORDER_FOR_OEHEADER — Performs the reverse lookup, returning the Inventory sales order record for a supplied Order Management order header.
• SYNCH_SALESORDERS_WITH_OM — The synchronization routine. It reconciles Inventory sales order rows with their Order Management counterparts, ensuring order numbers, order types, and header references remain aligned after changes in Order Management.
• GET_HEADER_ID — A utility function that resolves a header identifier from the supplied order identity, supporting the cross-reference operations above.
• CREATE_MTL_SALES_ORDERS_BULK — The bulk variant of sales order creation, loading multiple MTL_SALES_ORDERS records in a single invocation for performance and volume processing.
• DELETE_MTL_SALES_ORDERS_BULK — The bulk counterpart for removal, purging multiple Inventory sales order records at once.

No parameter signatures are published in the ETRM metadata; the descriptions above reflect documented purpose only.

Tables Accessed

The package operates against the following tables, reached through APPS synonyms:

• MTL_SALES_ORDERS and MTL_SALES_ORDERS_S — the primary Inventory-side targets of the create, bulk create, and bulk delete operations, together with their translation table.
• OE_ORDER_HEADERS and OE_ORDER_HEADERS_ALL — the Order Management order records that the get/synchronize routines read and align with Inventory.
• OE_TRANSACTION_TYPES_ALL and OE_TRANSACTION_TYPES_TL — the order transaction type definitions used to classify and validate sales orders.
• FND_LANGUAGES — supplies installed language information, supporting multilingual retrieval.
• DUAL — providing a single-row context for utility computations.

These accesses align with the package's dependencies on OE_HEADER_UTIL, OE_ORDER_HEADERS, and OE_TRANSACTION_TYPES in the ETRM reference list.

Usage Notes

INV_SALESORDER is not a form-level user API; it is invoked from PL/SQL, from other API packages, and from concurrent or batch processing. Its 41 referencing packages indicate heavy reuse inside the EBS code base, particularly for Order Management to Inventory integration. Typical invocations are: creating a sales order through CREATE_SALESORDER or CREATE_MTL_SALES_ORDERS_BULK during order import or interface activity; resolving an order header with GET_HEADER_ID or GET_OEHEADER_FOR_SALESORDER when a downstream process holds an Inventory sales order reference but requires the Order Management header; and running SYCHRONIZATION logic to repair discrepancies between MTL_SALES_ORDERS and OE_ORDER_HEADERS after corrections or changes in Order Management. Custom code that maintains both tables should call this package rather than inserting into MTL_SALES_ORDERS directly, to avoid breaking Order Management consistency. All calls execute under APPS schema privileges.