Search Results credit_transactions

Overview

ARP_CREDIT_MEMO_MODULE is an Oracle Receivables server-side PL/SQL package (ARTECMMS.pls) that implements the credit memo (CM) creation and maintenance logic within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its primary business function is to accept credit transaction data pushed from the AutoInvoice/credit memo user interface and persist it into the Receivables transaction schema, including the revenue assignment and accounting distribution rows generated for each credit line. The package encapsulates the CM module entry point, credit_transactions, which operates in either Insert or Update mode as directed by the caller, so that the same code path services the creation of new credit memos and the reversion/updating of existing ones.

Because the package is exposed through public procedures called from the Receivables forms layer, it carries a controlled error contract. It raises arp_credit_memo_module.no_ccid when autoaccounting cannot derive a valid code combination, and it populates the public buffer g_error_buffer with diagnostic detail for both Oracle errors and fatal application errors delivered via APP_EXCEPTION and the AOL message stack.

Key Procedures and Functions

Eleven documented program units are catalogued for this package under ETRM 12.2.2. The production entry point is credit_transactions, the server-side entry point for the CM module, taking the current and previous transaction/line identifiers plus a request identifier, maintaining an IN OUT failure count, and accepting a process mode defaulting to Insert. The remaining units fall into service and diagnostic groups:

• INIT — package initialization, establishing the session state used by the module.
• GET_VALID_DATE — returns a valid date, typically derived from the general ledger period mapping, for use when stamping transaction or accounting dates.
• TEST_BUILD_UPDATE_MODE_SQL, TEST_BUILD_NONRULE_SQL, TEST_BUILD_RULE_SQL, TEST_BUILD_NET_REVENUE_SQL — test/diagnostic utilities that construct the dynamic SQL used for update-mode processing, for non-rule based revenue handling, for rule based revenue handling, and for net revenue derivation respectively.
• TEST_LOAD_NET_REVENUE, TEST_CREDIT_NONRULE_TRXS, TEST_CREDIT_RULE_TRXS — test harnesses that load net revenue data and exercise credit transaction processing for the non-rule and rule based paths.

The test_build_net_revenue_sql entry returned by the user's search corresponds to the TEST_BUILD_NET_REVENUE_SQL unit above; it is a test-only helper rather than a supported production API.

Tables Accessed

The package reads and writes Receivables core tables through APPS synonyms. Transaction headers and lines are maintained in RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES, and RA_CUSTOMER_TRX_LINES_ALL; transaction types come from RA_CUST_TRX_TYPES. Credit memo amounts are stored in AR_CREDIT_MEMO_AMOUNTS, and payment schedule/term information is read from AR_PAYMENT_SCHEDULES. Revenue generation relies on RA_RULES and the global temporary table AR_REVENUE_ASSIGNMENTS_GT. Accounting distributions are written to RA_CUST_TRX_LINE_GL_DIST. System-level defaults and period validation draw on AR_SYSTEM_PARAMETERS and GL_DATE_PERIOD_MAP. Interface and error tracking use RA_INTERFACE_LINES and RA_INTERFACE_ERRORS. Dynamic SQL for the test builders is executed through DBMS_SQL.

Usage Notes

ARP_CREDIT_MEMO_MODULE is invoked from the Receivables credit memo forms as the server-side handler for transaction save and update actions, and it is referenced by four other packages in the ETRM repository. It is not a general-purpose public API and is not intended for direct customer integration; external callers should use the supported AutoInvoice and Receivables open interfaces (RA_INTERFACE_LINES) instead. The TEST_* procedures exist only for development verification of the dynamically constructed SQL and should not be scheduled as concurrent programs or called from production customization. All output should be validated against the AOL message stack and the g_error_buffer contents when an exception is caught.