Search Results arp_crol_pkg

Overview

ARP_CROL_PKG is an Oracle Applications (APPS) PL/SQL package that belongs to the Oracle Receivables (AR) module. The object is classified under the ETRM scheme as an OTHER API, a designation reserved for packages that encapsulate a discrete, low-level unit of business logic rather than exposing a public, versioned API surface. The package name derives from the Receivables "contact role" domain: it provides the maintenance logic for the relationship between a contact and the role it plays on a customer or prospect record. In practical terms, ARP_CROL_PKG supplies the procedural backbone that Forms-based maintenance screens and internal Receivables processing rely on when contact-role assignments are created, validated, amended, or removed. The package is documented with a status of VALID in both Oracle EBS 12.1.1 and 12.2.2 and resides entirely within the APPS schema, meaning its execution is governed by standard Oracle Applications grants and synonym resolution.

Key Procedures and Functions

The ETRM metadata documents eight named subprograms within the package. They fall into two functional groups: validation routines and data-manipulation routines.

• CHECK_UNIQUE — verifies that a contact-role assignment does not duplicate an existing record, enforcing the uniqueness constraint expected by the Receivables data model.
• CHECK_PRIMARY — validates the primary-contact-role designation, ensuring that any record flagged as primary is consistent with the rules governing primary contact assignments.
• CONTACT_ROLE_EXISTS — performs an existence check for a given contact-role combination, typically used before insert, update, or delete operations.
• INSERT_ROW — inserts a new contact-role record.
• LOCK_ROW — acquires a row-level lock on an existing contact-role record to serialize concurrent modification.
• UPDATE_ROW — applies changes to an existing contact-role record.
• DELETE_ROW — removes a contact-role record.

Together these subprograms form a classic Forms-style server-side maintenance package: validation precedes locking, and locking precedes write operations.

Tables Accessed

The ETRM excerpt does not enumerate specific underlying tables; it lists only SYS.STANDARD as a referenced dependency, indicating that the package body relies on standard PL/SQL built-ins and does not declare direct, hard-coded references to AR base tables within the documented metadata. In the Oracle Receivables schema, contact-role maintenance is conventionally performed against the AR contact-role intersection tables (the AR_CONTACT_ROLES family) and their associated contact tables. Because the package is documented as an OTHER API with no listed table references, the exact table set should be confirmed by inspecting the package body via the ETRM "show dependent code" link before any direct dependency is assumed.

Usage Notes

ARP_CROL_PKG is not a public API and is not referenced by any other documented package; the metadata explicitly records zero inbound package references. Its consumers are, therefore, Forms modules and custom extensions that require the guaranteed validation and locking behaviour the package provides. Typical invocation scenarios include Receivables customer and contact maintenance forms, where INSERT_ROW, UPDATE_ROW, and DELETE_ROW are called after CHECK_UNIQUE, CHECK_PRIMARY, and CONTACT_ROLE_EXISTS have validated the incoming data, and LOCK_ROW is used to protect the record against concurrent updates. Custom code that manipulates contact-role data directly is advised to call these subprograms rather than issuing raw DML, since the validation logic embodies Receivables business rules — particularly around uniqueness and the primary-role flag — that raw SQL would bypass. Because the package is internal and unversioned, custom callers should treat its signature as unstable across patches and should re-verify dependencies after each Receivables patchset application.