Search Results msg_cm_unit_overapp

Overview

ARP_CREDIT_MEMO_MODULE is a Receivables (AR) PL/SQL package body in the APPS schema that implements credit memo creation and application logic within Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business function is to generate and process credit memos against existing transactions, including rule-based and non-rule-based credit memo transactions, and to calculate net revenue and overapplication handling. The package header is defined as arp_credit_memo_module, and its body carries extensive private constants, exceptions, and translated messages that drive its internal validation and error reporting.

The package contains package-level constants that map to global values (e.g., CRLF, message levels, YES/NO, prorate/lifo/unit indicators) and user-defined exceptions such as invalid_parameters, invalid_mode, missing_periods, overapp_not_allowed, invalid_cm_method_for_rules, no_net_revenue, cm_unit_overapp, and inv_locked_by_another_session (error -54). These exceptions are paired with translated error message variables (MSG_INVALID_PARAMETERS, MSG_MISSING_PERIODS, MSG_OVERAPP_NOT_ALLOWED, MSG_NO_NET_REVENUE, MSG_INV_LOCKED, MSG_CM_UNIT_OVERAPP, MSG_INV_LOCKED_BY_JL) that are raised and surfaced to the caller.

Key Procedures and Functions

ETRM documents 11 public procedures/functions in the package:

• CREDIT_TRANSACTIONS — the main driver that performs credit memo processing, coordinating rule and non-rule credit transactions.
• INIT — initializes package-level state and setup before processing begins.
• GET_VALID_DATE — determines a valid date (e.g., GL date / period) used during credit memo creation.
• TEST_LOAD_NET_REVENUE — test/support routine that loads net revenue values for validation.
• TEST_BUILD_UPDATE_MODE_SQL — builds SQL for update-mode test scenarios.
• TEST_BUILD_NONRULE_SQL — builds SQL for non-rule-based credit memo test scenarios.
• TEST_BUILD_RULE_SQL — builds SQL for rule-based credit memo test scenarios.
• TEST_BUILD_NET_REVENUE_SQL — builds SQL to test net revenue calculations.
• TEST_CREDIT_NONRULE_TRXS — exercises non-rule credit transactions in testing.
• TEST_CREDIT_RULE_TRXS — exercises rule-based credit transactions in testing.

The TEST_* routines support development and QA validation of the credit memo logic; CREDIT_TRANSACTIONS and INIT represent the operational core.

Tables Accessed

The package reads and writes transaction and revenue data through APPS synonyms:

• RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES, RA_CUSTOMER_TRX_LINES_ALL — the credit memo header and line records being created or referenced.
• RA_CUST_TRX_LINE_GL_DIST — GL distribution lines associated with credit memo lines.
• RA_CUST_TRX_TYPES — transaction type definitions governing credit memo behavior.
• AR_CREDIT_MEMO_AMOUNTS — stored credit memo amount details.
• AR_PAYMENT_SCHEDULES — payment schedule and application balances affected by credit memos.
• AR_REVENUE_ASSIGNMENTS_GT — temporary/global temporary revenue assignment data.
• AR_SYSTEM_PARAMETERS — system-level AR setup controlling processing rules.
• RA_RULES — revenue recognition rules used for rule-based credit memos.
• GL_DATE_PERIOD_MAP — maps dates to GL periods for valid date determination.
• RA_INTERFACE_LINES, RA_INTERFACE_ERRORS — interface/write-back and error capture.
• DBMS_SQL — used dynamically to build and execute test SQL statements.

Usage Notes

ARP_CREDIT_MEMO_MODULE is invoked primarily by Oracle Receivables forms, concurrent programs, and internal AR APIs when credit memos are created or applied. It is referenced by four other packages, indicating it sits within the shared AR credit memo processing chain rather than being called directly by end users. The presence of DBMS_SQL-driven TEST_* builders suggests the production routines (CREDIT_TRANSACTIONS, INIT, GET_VALID_DATE) rely on dynamically constructed SQL for flexible rule versus non-rule processing.

Regarding the user search term "inv_unit_price": unit price is a core attribute of credit memo line amounts. Within this package's processing, unit price is relevant when computing net revenue and credit memo amounts for unit-based (UNIT constant 'U') credit memo methods. The package's use of AR_CREDIT_MEMO_AMOUNTS and RA_CUSTOMER_TRX_LINES means unit price values are read from or written to credit memo line records during CREDIT_TRANSACTIONS. Custom implementations extending credit memo logic should treat unit price as a line-level attribute reconciled against the extracted net revenue and credit memo amount calculations. The overapplication exceptions (overapp_not_allowed, cm_unit_overapp) further indicate unit price and quantity validation occur before credit memo application. Because the documented metadata does not define individual parameter lists, integrators should consult the package specification and AR user documentation before calling these routines directly.