Search Results dump_item_control_rec

Overview

APPS.CSI_RMA_RECEIPT_PUB is a public PL/SQL package body in Oracle E-Business Suite that supports Return Merchandise Authorization (RMA) receipt processing within the Oracle Installed Base / CSI (Customer Service Intelligence) module. Its primary business function is to reconcile and record the return of customer-owned items into inventory, capturing item instance information, transaction details, and the associated accounting attributes required when an RMA is received. The package bridges the Receivables/Order Management RMA workflow with Installed Base instance tracking and the underlying inventory transaction layer in Oracle Inventory.

The package is classified as a PUB (public) API, meaning it is intended for direct invocation by external modules, concurrent programs, or customizations, and its signature is treated as a supported interface. The header comment "$Header: csipirmb.pls 120.10.12000000.3 2007/06/25" indicates the source belongs to the CSI installed base product family and was last revised in 2007, with the package continuing to ship across EBS 12.1.1 and 12.2.2. Several local debug procedures (DEBUG, API_LOG, DUMP_ITEM_CONTROL_REC, DUMP_MTL_TXN_REC) exist only to trace execution and dump item control and material transaction record structures during development and diagnostics.

Key Procedures and Functions

• RMA_RECEIPT — The central procedure that performs the actual RMA receipt. It validates the item, resolves control attributes (serial, lot, revision), records the material transaction, and creates or updates the corresponding Installed Base item instance for the returned unit.
• GET_RMA_INFO — Retrieves the header and line information associated with a given RMA, providing the context (customer, order line, item) required before a receipt can be processed.
• GET_SUB_TYPE_REC — Derives the subscriber/party subtype record used when associating the returned item with the correct Installed Base party and account structure.
• DECODE_MESSAGE — Translates internal status or error codes into user-readable messages, typically surfaced through the calling form or concurrent program log.
• CHECK_AND_BREAK_RELATION — Evaluates and, where appropriate, breaks existing Installed Base relationships (for example parent-child or component linkages) when a returned item is received.

Tables Accessed

The package reads and writes a broad set of tables through APPS synonyms covering Installed Base, inventory, and trading partner data:

• CSI_ITEM_INSTANCES, CSI_I_PARTIES, CSI_IP_ACCOUNTS — Core Installed Base tables used to create/update the returned item instance, its owning party, and account associations.
• CSI_SOURCE_IB_TYPES, CSI_T_TRANSACTION_LINES, CSI_T_TXN_LINE_DETAILS — CSI transaction and source-type structures that record the detail of the RMA receipt event.
• MTL_MATERIAL_TRANSACTIONS, MTL_PARAMETERS, MTL_SECONDARY_INVENTORIES, MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_B — Inventory tables used to validate item control attributes (serial/lot/revision), resolve the receiving subinventory, and post the material transaction.
• HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL — Trading Community Architecture (TCA) tables that resolve the customer and ship-to/site information for the return.
• HR_ALL_ORGANIZATION_UNITS — Supplies the inventory organization definition used during receipt validation.

Usage Notes

CSI_RMA_RECEIPT_PUB is typically invoked from the Oracle Installed Base or Service RMA forms during the return-receipt step, and may also be called from concurrent programs or custom PL/SQL that automate RMA processing. Because the business logic is exposed as public procedures, customization developers commonly call RMA_RECEIPT after first resolving context via GET_RMA_INFO. The presence of extensive debug dumps for item control and material transaction records — including mtl_attribute-related item control data such as serial_control_code, lot_control_code, and revision_control_code — makes the package well suited for tracing attribute resolution when RMA receipts fail item validation. All invocations should supply the inventory organization and RMA identifiers expected by the documented procedures; callers should not assume the internal debug procedures are part of the supported interface. Status and error conditions are reported through DECODE_MESSAGE, so calling code should surface these messages to end users or capture them in the concurrent request log.