Search Results cb_create

Overview

AR_BUS_EVENT_SUB_PVT is a private PL/SQL package owned by APPS in the Oracle E-Business Suite Receivables (AR) module. Its name reflects its role: a business event subscriber package. It implements the standard Oracle Workflow Business Event System subscription interface, which requires a subscription-handling function that accepts a subscription GUID and an event payload of type WF_EVENT_T and returns a status code. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, and it is classified as a private (PVT) API, so it is not part of the supported public interface for Oracle EBS and is intended solely for internal use by Receivables and Oracle Workflow.

The core purpose of AR_BUS_EVENT_SUB_PVT is to react to Receivables business events. When transactions, receipts, adjustments, deposits, chargebacks, guarantees, or credit memos are created, modified, completed, or reversed, the Business Event System raises a corresponding event. This package subscribes to those events and performs the internal bookkeeping Receivables requires, such as maintaining transaction balances, refreshing summary and history tables, and keeping the audit trail consistent. Because it is invoked automatically by the event system rather than by end users, it is a background integration and maintenance component.

Key Procedures and Functions

The package exposes 42 documented functions, all sharing the same signature pattern: they accept p_subscription_guid (RAW) and p_event (WF_EVENT_T, an IN OUT NOCOPY parameter) and return a VARCHAR2 status. This uniform interface is what allows the Workflow Business Event System to call any of them generically. The functions are grouped by Receivables document family:

• Invoice events: INV_COMPLETE, INV_INCOMPLETE, INV_MODIFY, and INV_DEPOSITAPPLY handle invoice completion, uncompletion (reversal of completion), modification, and the application of deposits against invoices.
• Credit memo events: CM_COMPLETE, CM_INCOMPLETE, and CM_MODIFY respond to credit memo completion, reversal, and updates.
• Debit memo events: DM_COMPLETE, DM_INCOMPLETE, and DM_MODIFY perform the equivalent processing for debit memos.
• Deposit events: DEP_COMPLETE, DEP_INCOMPLETE, and DEP_MODIFY track deposit lifecycle changes.
• Chargeback events: CB_CREATE and CB_MODIFY handle chargeback creation and modification.
• Guarantee events: GUAR_COMPLETE, GUAR_INCOMPLETE, and GUAR_MODIFY process guarantee completion, reversal, and changes.
• Cash receipt events: CASHRECEIPT_CREATE and CASHRECEIPT_REVERSE handle creation and reversal of cash receipts.

The complete/incomplete pairs are complementary: completion triggers balance and summary updates, while incompletion reverses them.

Tables Accessed

The package reads and writes the principal Receivables transaction and receipt tables, accessed through APPS synonyms. Transaction data is held in RA_CUSTOMER_TRX_ALL, with balances and schedules in AR_PAYMENT_SCHEDULES and AR_PAYMENT_SCHEDULES_ALL. Cash receipt processing involves AR_CASH_RECEIPTS, AR_CASH_RECEIPTS_ALL, and AR_CASH_RECEIPT_HISTORY / AR_CASH_RECEIPT_HISTORY_ALL. Application of receipts to transactions uses AR_RECEIVABLE_APPLICATIONS and AR_RECEIVABLE_APPLICATIONS_ALL, while adjustments are recorded in AR_ADJUSTMENTS. Aggregated and reporting-oriented data is maintained in AR_TRX_BAL_SUMMARY, AR_TRX_SUMMARY, and AR_TRX_SUMMARY_HIST. Audit changes are logged to AR_RAMC_AUDIT_TRAIL, and WF_EVENT_T carries the event payload itself. These accesses are necessary because each business event ultimately changes the financial state of a transaction or receipt, requiring corresponding updates to balances, applications, summaries, and audit records.

Usage Notes

AR_BUS_EVENT_SUB_PVT is not intended for direct invocation. It is called by the Oracle Workflow Business Event System when an event subscription defined against receivables events fires. The subscription GUID identifies which subscription invoked the function, and the WF_EVENT_T parameter carries the event name and data. Typical triggers are Receivables forms and Receivables' own internal APIs that complete, modify, or reverse transactions and receipts. Because the package is private and AUTHID CURRENT_USER, custom code should not call these functions directly; developers seeking supported functionality should use the public Receivables APIs. This package is referenced by two other packages, reinforcing its internal, dependency-driven role. Its behavior is tied to the AR event model in both 12.1.1 and 12.2.2.