Search Results create_holds

Overview

APPS.AP_INVOICES_POST_PROCESS_PKG is an internal Oracle Payables (AP) PL/SQL package that supports the invoice posting and validation lifecycle in Oracle E-Business Suite 12.1.1 and 12.2.2. The package is classified as an "OTHER" API, indicating that it is not part of the officially published, supported public API surface, but rather a supporting component invoked by core Payables processing logic. Its primary responsibility is to perform post-processing actions once an invoice has been entered, validated, or matched — including the creation of system holds, the maintenance of invoice line children, and the synchronization of transaction state during form-driven and concurrent posting flows.

Because the package is referenced by AP_INVOICES_PKG, AP_ISP_UTILITIES_PKG, and AP_WORKFLOW_PKG, it occupies a central position in the invoice processing chain. It bridges the invoice header, distributions, and payment schedules with the hold and workflow subsystems, ensuring that data integrity is maintained when invoices are committed.

Key Procedures and Functions

The ETRM metadata documents six procedures and functions within this package:

• CREATE_HOLDS — Evaluates invoice and validation criteria and applies the appropriate system holds against an invoice. This is central to Payables validation, where matching, tax, or policy violations result in holds that block payment.
• INSERT_CHILDREN — Inserts the dependent child rows associated with an invoice, such as invoice lines, distributions, and payment schedules, preserving the parent-child relationship expected by the Payables data model.
• INVOICE_PRE_UPDATE — Executes logic immediately before an invoice record is updated, typically to capture the current state, perform validation, and prepare dependent data for the pending change.
• INVOICE_POST_UPDATE — Executes logic immediately after the invoice record is updated, completing downstream tasks such as recalculating holds, refreshing derived attributes, and triggering related workflow activity.
• POST_FORMS_COMMIT — Handles the actions required after the Oracle Forms commit cycle completes, ensuring that holds, children, and status flags are consistent with the committed invoice data.
• SELECT_SUMMARY — Retrieves summary invoice information for display or downstream processing, consolidating header-level attributes required by the calling component.

All routines operate on the APPS schema and are used internally; parameter lists are not documented and should not be assumed by external callers.

Tables Accessed

The package reads and writes a well-defined set of Payables tables through APPS synonyms:

• AP_INVOICES / AP_INVOICES_ALL — The invoice header, the primary subject of the pre- and post-update logic and the source for hold evaluation.
• AP_INVOICE_LINES — Invoice distributions and lines inserted by INSERT_CHILDREN and validated during posting.
• AP_PAYMENT_SCHEDULES / AP_PAYMENT_SCHEDULES_ALL — Payment schedules created and maintained as children of the invoice.
• AP_HOLDS — The hold repository to which CREATE_HOLDS writes validation and policy holds.
• AP_BATCHES / AP_BATCHES_ALL — Batch context used when invoices are processed within an invoice batch.
• AP_SYSTEM_PARAMETERS / AP_SYSTEM_PARAMETERS_ALL and FINANCIALS_SYSTEM_PARAMETERS — Configuration sources that govern validation, hold, and posting behavior.

These accesses reflect the package's role in synchronizing header, line, schedule, and hold data within a single committed transaction.

Usage Notes

AP_INVOICES_POST_PROCESS_PKG is not intended for direct invocation by external applications or custom code. It is called by Oracle Payables forms and concurrent programs through AP_INVOICES_PKG and related components, particularly during invoice entry, validation, matching, and posting. Because it is classified as an "OTHER" API and is referenced by AP_WORKFLOW_PKG and AP_ISP_UTILITIES_PKG, its behavior is tightly coupled to the standard validation and hold engine. Customizations should avoid calling these procedures directly; instead, rely on documented public APIs such as AP_INVOICES_PKG or the Invoice Validation and Payables Open Interface programs. Any modification risk should be assessed through ETRM, since the package is VALID and actively referenced in both 12.1.1 and 12.2.2 environments.