Search Results ap_holds_all




Overview
Explore in AI Chat

Overview

The AP_HOLDS_ALL table is a core transactional table within the Oracle E-Business Suite Payables (AP) module. It serves as the central repository for all invoice hold information, a critical control mechanism for managing the invoice approval and payment workflow. When an invoice is placed on hold, either manually by a user or automatically by the system based on predefined business rules, a corresponding record is created in this table. Each record tracks a specific hold applied to a specific invoice, detailing the reason, the responsible party, and the resolution status. Its role is integral to ensuring financial controls, preventing erroneous payments, and enforcing compliance before an invoice can be approved for payment. As an "ALL" table, it is designed to support the multi-org architecture of Oracle EBS, storing data partitioned by operating unit.

Key Information Stored

The table's structure captures the complete lifecycle of an invoice hold. While the specific column list is not detailed in the provided metadata, the foreign key relationships indicate the presence of critical fields. The INVOICE_ID column links the hold to the specific invoice in AP_INVOICES_ALL. The HOLD_LOOKUP_CODE and RELEASE_LOOKUP_CODE columns define the reason for the hold and the reason for its release, respectively, referencing codes in the AP_HOLD_CODES table. The HELD_BY column identifies the user who applied the hold, linked to FND_USER. For purchase order matching holds, the LINE_LOCATION_ID and RCV_TRANSACTION_ID columns link to the purchasing and receiving modules (PO_LINE_LOCATIONS_ALL and RCV_TRANSACTIONS). Additional columns typically found include creation and last update dates, hold and release dates, and a status indicator to show if the hold is currently active or has been released.

Common Use Cases and Queries

Primary use cases include auditing hold activity, troubleshooting payment blocks, and generating operational reports. A common query is to identify all invoices currently on hold for a specific operating unit or hold reason to facilitate resolution. For example:

  • SELECT aia.invoice_num, aia.invoice_amount, ah.hold_lookup_code, ah.held_by FROM ap_holds_all ah, ap_invoices_all aia WHERE ah.invoice_id = aia.invoice_id AND ah.status = 'A' AND aia.org_id = :org_id;

Another critical scenario is analyzing the duration of holds to assess process efficiency, joining AP_HOLDS_ALL to AP_INVOICES_ALL and using date columns to calculate hold time. System administrators and functional consultants also query this table to verify that automatic hold releases have processed correctly after related actions, such as completing goods receipt for a matching hold.

Related Objects

As documented by its foreign keys, AP_HOLDS_ALL has direct relationships with several key EBS tables. The primary parent is AP_INVOICES_ALL (via INVOICE_ID), anchoring the hold to the invoice. It references AP_HOLD_CODES twice: once for the hold reason (HOLD_LOOKUP_CODE) and once for the release reason (RELEASE_LOOKUP_CODE). For procurement card and matching holds, it links to PO_LINE_LOCATIONS_ALL (via LINE_LOCATION_ID) and RCV_TRANSACTIONS (via RCV_TRANSACTION_ID). The identity of the user applying the hold is maintained via a foreign key to FND_USER (HELD_BY). This network of relationships situates AP_HOLDS_ALL at the intersection of Payables, Purchasing, and system security data.