Search Results insert_f_notes

Overview

ARP_CC_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, declared with AUTHID CURRENT_USER so that its unqualified references to AR tables resolve through the calling user's synonym set. In the Receivables data model, "CC" denotes Customer Calls, and the package supplies the programmatic interface for creating and maintaining customer call records together with their associated notes, topics, actions, and action notifications. The package header ($Header: ARCIECCS.pls 115.2, dated 2002/11/15) predates the 12.1.1 and 12.2.2 releases and remains unchanged in both, indicating a stable, low-churn API surface.

Functionally, the package occupies the middle tier between the Customer Calls user interface or collection workflow and the underlying AR base tables. It performs the record-level inserts and updates that the Customer Calls window and the collections (dunning) process require, including the denormalized note record that many users reference by the entry point name insert_f_notes. ETRM classifies the package as API classification OTHER rather than a formal public interface, which reflects its role as an internal helper for the customer calls feature rather than a supported integration point.

Key Procedures and Functions

The documented interface comprises nine callable units:

• insert_p — Creates a customer call header row and returns the generated customer_call_id.
• insert_f_notes — Inserts a note record associated with a customer call and returns the generated note_id. This is the procedure users most commonly search for when working with call notes.
• insert_f_topics — Inserts a customer call topic row and returns the generated customer_call_topic_id.
• insert_f_actions — Inserts a call action row and returns the generated call_action_id.
• insert_f_notifications — Inserts action notification records; unlike the other insert procedures it does not return an identifier.
• update_p — Updates the customer call header, identified by the supplied rowid.
• update_f_topics — Updates a customer call topic row by rowid.
• update_f_actions — Updates a call action row by rowid.
• check_dunning — A BOOLEAN function that reports whether dunning conditions apply, allowing the calls or collections logic to gate processing.

The naming convention distinguishes the primary call record (the _p suffix on insert_p and update_p) from the dependent child records (the _f_ infix), and the header exposes no delete procedures.

Tables Accessed

Through APPS synonyms the package reads and writes the core customer calls tables: AR_CUSTOMER_CALLS for call headers, AR_NOTES for notes attached to calls, AR_CUSTOMER_CALL_TOPICS for call subjects, AR_CALL_ACTIONS for follow-up actions, and AR_ACTION_NOTIFICATIONS for action-related notifications. Each of these has a companion _S (shadow) table — AR_CUSTOMER_CALLS_S, AR_NOTES_S, AR_CUSTOMER_CALL_TOPICS_S, AR_CALL_ACTIONS_S, and AR_ACTION_NOTIFICATIONS_S — maintained by Oracle's seed data / audit shadow-table mechanism, so DML against the base tables also propagates to the _S copies. AR_SYSTEM_PARAMETERS supplies Receivables system options, and DUAL supports trivial single-row selections, most plausibly within check_dunning. The insert procedures on AR_NOTES and AR_ACTION_NOTIFICATIONS account directly for the common search term insert_f_notes.

Usage Notes

ARP_CC_PKG is invoked from the Receivables Customer Calls form and from collections logic that creates or maintains call activities. Because the header carries no ORGANIZATION_ID or similar operating-unit parameter, calls are created in the context of the session's current Receivables system parameters rather than an explicit ledger context. The package also serves two other dependent packages, which call it to persist call-related data on behalf of their own flows.

Consistent with its OTHER API classification, ARP_CC_PKG is not documented by Oracle as a supported extension API. Customizations that require call creation or note insertion should be developed against the documented public interfaces (such as the Notes APIs) where these exist, and any direct invocation of insert_f_notes or its sibling procedures should be treated as a version-sensitive, unsupported dependency. Where direct use is unavoidable, callers should supply the complete record structures expected by the base tables, honor the OUT identifier parameters to capture the newly generated primary keys, perform DML inside the caller's transaction with explicit commit or rollback, and re-validate the package after applying 12.1.1 or 12.2.2 patches, since the source line numbers in the ETRM excerpt reflect an early code line.