Search Results arp_cc_pkg




Overview
Explore in AI Chat

Overview

The ARP_CC_PKG package body, owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2, supports the Customer Calls and Collections functionality within Oracle Receivables. Its principal business role is to manage the persistence logic behind customer call records, their associated notes, topics, actions, and action notifications. The package acts as the data-access layer through which call-related components—particularly the Customer Calls and Collection workflow—write transactional data into the underlying call and notes tables.

The package is classified under the ETRM as an OTHER API rather than a formally published public API. It is not referenced by any database object per the dependency metadata, though it is reported to be referenced by two other packages. This indicates it functions as an internal implementation package rather than a supported integration entry point.

Key Procedures and Functions

The ETRM metadata documents nine procedures and functions in ARP_CC_PKG. Their purposes are as follows:

Tables Accessed

The package reads and writes the following documented tables (via APPS synonyms):

  • AR_CUSTOMER_CALLS / _S — The master call record; the base table and its sequence supply the primary key.
  • AR_CUSTOMER_CALL_TOPICS / _S — Topic links for each call.
  • AR_CALL_ACTIONS / _S — Individual actions logged against a call.
  • AR_ACTION_NOTIFICATIONS / _S — Notification records generated for call actions.
  • AR_NOTES / AR_NOTES_S — Free-text notes attached to calls; AR_NOTES_S provides the note identifier.
  • AR_SYSTEM_PARAMETERS — Read for Receivables system-level settings, such as defaulting and dunning configuration.
  • DUAL — Used for single-row queries and sequence lookups.

Usage Notes

ARP_CC_PKG is invoked internally by the Oracle Receivables Customer Calls forms and by serviced components that create or maintain call records. Because the ETRM classifies it as OTHER and no database object depends on it, it should not be treated as a supported public API; customizations should instead call the supported call-management interfaces where available. Direct invocation from custom PL/SQL is possible but unsupported, and callers must respect the sequence-driven keys, the dependent INSERT_F_* and UPDATE_F_* routines, and the AR_SYSTEM_PARAMETERS-derived defaults. The package is most relevant to administrators and developers investigating how call, topic, action, notification, and note data are persisted in the Customer Calls schema, and to those searching for the AR_NOTES_S synonym that underpins note creation.