Results for “arp_crm_pkg”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ARP_CRM_PKG is a PL/SQL package in the APPS schema that provides the core data-access layer for customer receipt methods in Oracle Receivables. Customer receipt methods define how a specific customer, or a specific customer site use, is permitted to remit payment — for example by check, wire, credit card, or any other receipt method defined at the operating unit level. The package encapsulates the insert, update, lock, and validation logic required to maintain these customer-specific receipt method assignments safely and consistently.

The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute under the privileges of the calling session rather than the owner of the package. This is the standard convention for Oracle E-Business Suite PL/SQL APIs exposed to Oracle Forms, concurrent programs, and customization code, and it ensures that Row Level Security and operating unit (MOAC) enforcement remain in effect for every caller. Its fairly early header signature (115.0) indicates that the package has been stable across many releases and continues to be shipped in both 12.1.1 and 12.2.2.

Key Procedures and Functions

• CHECK_UNIQUE — Validates that a candidate customer receipt method assignment does not duplicate an existing effective-dated row. It is the enforcement point for the uniqueness rule across customer, receipt method, method type, and the date range, and is normally called before an insert or update is committed.
• CHECK_PRIMARY — Enforces the rule that only one receipt method may be flagged as the primary method for a given customer or site use within a valid date range. This preserves the single-primary-method business constraint relied upon by downstream payment and collections processing.
• INSERT_ROW — Creates a new row in the customer receipt methods entity. It accepts the full descriptive flexfield attribute set (attribute category plus ATTRIBUTE1 through ATTRIBUTE15), identifying keys, primary flag, receipt method, and effective start and end dates, and returns the generated rowid and primary key.
• LOCK_ROW — Obtains a pessimistic lock on an existing customer receipt method row and verifies that the persisted values have not changed since the caller read them. This provides optimistic concurrency protection for Forms-based maintenance.
• UPDATE_ROW — Modifies an existing customer receipt method record, working against the locked row to update dates, primary flag, attributes, and audit columns.

Tables Accessed

• RA_CUST_RECEIPT_METHODS — The primary transactional table holding customer and site-use level receipt method assignments, including the primary flag, effective dates, and the descriptive flexfield columns. The package performs inserts, updates, and row locking against this table.
• RA_CUST_RECEIPT_METHODS_S — The companion sequence/primary key table used to obtain the next CUST_RECEIPT_METHOD_ID value during insert processing.
• DUAL — Used for scalar lookups and single-row validation queries within the check procedures.

All tables are referenced through APPS synonyms, so the package relies on standard EBS synonym resolution rather than fully qualified schema names.

Usage Notes

The package is the underlying program unit for the Customer Receipt Methods form and for the Receivables customer standard interfaces that maintain payment method assignments. It is also referenced by one other package within the Applications schema, indicating layered reuse rather than direct end-user invocation.

Custom code should not manipulate RA_CUST_RECEIPT_METHODS directly. Instead, callers should invoke INSERT_ROW, UPDATE_ROW, LOCK_ROW, and the two validation procedures in the documented sequence: validate uniqueness and primary-method status, lock the target row for updates, then perform the insert or update. Respecting this order preserves effective dating integrity and avoids concurrent-update conflicts. Because of the AUTHID CURRENT_USER declaration, callers must ensure that the operating unit context is set correctly before invocation so that the correct customer receipt method records are visible and writable.