Search Results gross_amount_to_date




Overview

The APPS.AP_AWT_BUCKETS_V view is a reporting and inquiry object in Oracle E-Business Suite that presents withholding tax accumulation data for suppliers. It joins the withholding tax buckets table to the supplier master to expose vendor identity alongside period-by-period and cumulative withholding figures. The view belongs to the Payables (AP) module's withholding tax (AWT) functionality, which tracks tax withheld from supplier payments and accrues that liability against the supplier and tax authority.

Because it is an APPS-owned view built on top of already-processed withholding data, it serves primarily as a read-only presentation layer. It is used in period-end and reconciliation reporting, supplier withholding analysis, and downstream integrations that require the withheld-to-date and gross-to-date positions for a given vendor, period, and tax. The view is not a transactional entry point; it summarizes the state maintained by the withholding tax bucket records themselves.

Underlying Base Objects

The view is defined over two referenced objects as documented in ETRM 12.2.2:

  • AP_AWT_BUCKETS (SYNONYM) — the core withholding tax bucket table that stores accumulated withholding amounts keyed to vendor, period, and tax. This table carries the transactional and audit columns (dates, who-columns, request/program identifiers, and ORG_ID) that the view surfaces.
  • PO_VENDORS (VIEW) — the supplier master view, which provides the vendor name and vendor number (SEGMENT1). It is joined on VENDOR_ID.

The join condition is a simple equijoin: PO_VENDORS.VENDOR_ID = AP_AWT_BUCKETS.VENDOR_ID. Supplier attributes come from PO_VENDORS, while all withholding figures and audit metadata come from AP_AWT_BUCKETS. The view inherits multi-org context through the ORG_ID column exposed from the buckets table.

Key Columns

Common Use Cases and Queries

Typical usage includes supplier withholding reconciliation, period-level withholding reporting, and extract feeds for tax authority filings. Because the view pre-joins supplier name and number, it avoids the need to resolve vendors separately in reporting SQL.

Withholding position for a specific supplier and period:

  • SELECT vendor_name, segment1, period_name, tax_name, withheld_amount_to_date, gross_amount_to_date FROM ap_awt_buckets_v WHERE vendor_id = :p_vendor_id AND period_name = :p_period ORDER BY tax_name;

Cumulative withholding by tax for an operating unit:

  • SELECT tax_name, SUM(withheld_amount_to_date) withheld, SUM(gross_amount_to_date) gross FROM ap_awt_buckets_v WHERE org_id = :p_org_id GROUP BY tax_name;

Suppliers with withholding activity in a period:

  • SELECT vendor_name, segment1, SUM(withheld_amount_to_date) total_withheld FROM ap_awt_buckets_v WHERE period_name = :p_period GROUP BY vendor_name, segment1 HAVING SUM(withheld_amount_to_date) > 0 ORDER BY 3 DESC;

These patterns support both operational reconciliation and analytical reporting against the Payables withholding tax subsystem.