Search Results ra_cust_receipt_methods_s

Overview

ARP_CRM_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite (validated against 12.1.1 and 12.2.2). Its name and dependency profile identify it as the customer receipt methods maintenance package within the Oracle Receivables (AR) module. It provides the server-side programmatic interface for creating, validating, and maintaining rows in RA_CUST_RECEIPT_METHODS, the table that stores the receipt methods a customer is permitted to use — for example, check, wire, credit card, or cash — together with the associated remittance bank account, receipt class, and defaulting attributes. The package acts as a thin business-logic layer over the table and its translated/secure views, ensuring that inserts and updates enforce uniqueness, primary-method rules, and concurrency control before data reaches the base table. The ETRM metadata classifies it as API type OTHER and confirms status VALID with no compilation errors.

Key Procedures and Functions

The documented package exposes five procedures, all of which support the standard insert/update pattern used by Receivables maintenance APIs:

• CHECK_UNIQUE — Verifies that the combination of identifying columns supplied for a customer receipt method (typically customer, receipt method, and currency) does not already exist in RA_CUST_RECEIPT_METHODS, preventing duplicate method assignments.
• CHECK_PRIMARY — Enforces the rule that only one receipt method can be flagged as primary for a given customer and currency combination, validating the PRIMARY_FLAG value before it is written.
• INSERT_ROW — Performs the actual insertion of a new customer receipt method record, applying WHO-column defaults and any required derived values.
• LOCK_ROW — Issues a SELECT ... FOR UPDATE against the target row to serialize concurrent modifications and support optimistic locking semantics.
• UPDATE_ROW — Applies changes to an existing customer receipt method record after the lock and validation steps have completed successfully.

Tables Accessed

The dependency listing shows direct references to two APPS objects and one public utility:

• RA_CUST_RECEIPT_METHODS — The base table holding customer-level receipt method assignments. It is the primary target of INSERT_ROW and UPDATE_ROW and the source for the validation queries in CHECK_UNIQUE and CHECK_PRIMARY.
• RA_CUST_RECEIPT_METHODS_S — The secure (row-level security) view over the base table. This is the same object the user searched for, and its presence confirms that the package performs its DML and validation through the Multi-Org–enabled synonym/view rather than the base table, so Org_ID security is respected.
• DUAL — Used for scalar evaluations and simple PL/SQL constructs.

Additional dependency references include FND_MESSAGE (for localized error and message text) and APP_EXCEPTION (for standardized exception handling and error propagation).

Usage Notes

ARP_CRM_PKG is invoked almost exclusively from Oracle Receivables forms — most notably the Customer Standard and Receipt Methods setup screens — where the form's server-side triggers delegate insert, update, and validation work to this package instead of issuing DML directly. It is also available to concurrent programs, Oracle Workflow activities, and custom PL/SQL that must create or amend customer receipt methods while preserving Receivables' validation and concurrency rules. Callers should expect the conventional sequence: CHECK_UNIQUE and CHECK_PRIMARY first, LOCK_ROW before modification, then INSERT_ROW or UPDATE_ROW, with errors raised via FND_MESSAGE and APP_EXCEPTION. Because the metadata records that ARP_CRM_PKG is referenced by one other database object and does not reference ARP_CRM_PKG recursively, it is a leaf-level utility package; it is not itself called by any further dependent object, so customizations invoking it should do so directly rather than through a wrapper.