Search Results ap_prepay_history_s

Overview

AP_ACCOUNTING_EVENTS_PKG is a core Oracle Payables (AP) package body in the APPS schema that governs the creation, maintenance, and status management of accounting events used by the Subledger Accounting (SLA) architecture (XLA). In Oracle E-Business Suite 12.1.1 and 12.2.2, Subledger Accounting relies on the accurate and timely registration of transaction events before journal entries can be generated for invoices, payments, prepayments, and withholding. This package encapsulates the business logic that detects changes to source Payables documents, determines whether a corresponding accounting event is required, and drives event creation into the XLA_EVENTS infrastructure.

Because Payables transactions span invoices, distributions, checks, payment history, and prepayment applications, the package serves as the principal bridge between the operational AP tables and the SLA event model. It also handles multi-organization sweeps and reconciles event status where partial processing or batch operations are involved.

Key Procedures and Functions

The documented interface exposes the following entry points:

• CREATE_EVENTS — Creates accounting events for the applicable Payables transactions, registering them with the SLA event infrastructure.
• DELETE_INVOICE_EVENT — Removes or reverses the accounting event associated with a specific invoice.
• UPDATE_INVOICE_EVENTS_STATUS — Updates the processing status of invoice-related accounting events.
• UPDATE_PAYMENT_EVENTS_STATUS — Updates the status of payment-related accounting events.
• UPDATE_PMT_BATCH_EVENT_STATUS — Manages event status at the payment batch level.
• CREATE_PAYMENT_BATCH_EVENTS — Generates accounting events for an entire payment batch.
• UPDATE_AWT_INT_DISTS — Adjusts withholding and interest distributions as they relate to event accounting.
• BATCH_UPDATE_PAYMENT_INFO — Performs bulk updates to payment information supporting batch event processing.
• MULTI_ORG_EVENTS_SWEEP — Sweeps across multiple operating units to identify and process pending events.
• SINGLE_ORG_EVENTS_SWEEP — Performs the same event sweep restricted to a single operating unit.
• SET_PREPAY_EVENT_NOACTION — Marks prepayment events so that no further accounting action is taken, typically during netting or application logic.

Tables Accessed

The package reads and writes a broad set of Payables source tables. Invoice-level processing touches AP_INVOICES/AP_INVOICES_ALL, AP_INVOICE_LINES, and AP_INVOICE_DISTRIBUTIONS/AP_INVOICE_DISTRIBUTIONS_ALL. Payment-related logic accesses AP_CHECKS/AP_CHECKS_ALL, AP_INVOICE_PAYMENTS/AP_INVOICE_PAYMENTS_ALL, and AP_PAYMENT_HISTORY, AP_PAYMENT_HISTORY_ALL, and AP_PAYMENT_HISTORY_S. Prepayment handling references AP_PREPAY_HISTORY, AP_PREPAY_HISTORY_ALL, AP_PREPAY_HISTORY_S, and AP_PREPAY_APP_DISTS. Hold logic consults AP_HOLDS and AP_HOLD_CODES. System and financials parameters are read from AP_SYSTEM_PARAMETERS/AP_SYSTEM_PARAMETERS_ALL and FINANCIALS_SYSTEM_PARAMETERS, while SLA event output is written through XLA_EVENTS, XLA_EVENTS_INT_GT, XLA_AE_HEADERS, and XLA_AE_LINES. Notably, the dependency on AP_PAYMENT_HISTORY_S and AP_PREPAY_HISTORY_S reflects the intersection tables used during SLA event generation.

Usage Notes

This package is invoked primarily by Payables concurrent programs and internal processing routines rather than being called directly by end users. The invoice and payment event sweeps (MULTI_ORG_EVENTS_SWEEP and SINGLE_ORG_EVENTS_SWEEP) are typically scheduled or triggered during accounting program runs so that newly approved invoices and confirmed payments are propagated into Subledger Accounting. Individual status-update procedures support online form actions, such as voiding or cancelling a payment, where the associated event must be invalidated. The package is referenced by numerous other APPS packages (sixteen or more), indicating it is a shared dependency across Payables and related accounting flows. Custom code should not generally call this package directly; instead, standard SLA APIs (for example XLA_EVENTS_PUB_PKG) should be used where event manipulation is required, preserving backward compatibility across 12.1.1 and 12.2.2.