Results for “ap_awt_groups”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AP_AWT_GROUPS is the withholding tax (AWT) group definition table in the Oracle Payables (AP) schema. It stores the named withholding tax groups that determine which withholding tax codes apply to an invoice, invoice distribution, expense report, recurring payment, supplier, or Payables system default. Because withholding tax processing in Oracle EBS is driven by grouping one or more tax codes under a single AWT group, this table acts as the central reference point from which every withholding tax computation in Payables and Expense Reports derives its applicable tax rules.

Under the heuristic Data Vault classification mined from the foreign key structure, AP_AWT_GROUPS is hub-leaning. It is a relatively narrow, stable reference table keyed by a single surrogate identifier, and it is referenced by many dependent transactional and setup tables rather than referencing them itself. In a Data Vault model it would most naturally be treated as a hub, with the referencing tables (invoices, distributions, suppliers, expense reports) acting as links or satellites.

The table is valid in both Oracle EBS 12.1.1 and 12.2.2. The documented physical schema in ETRM 12.2.2 shows nine columns and one unique index, AP_AWT_GROUPS_U1, defined on GROUP_ID.

Key Information Stored

The most significant columns documented for this table are:

  • GROUP_ID — The surrogate primary key, defined by constraint AP_AWT_GROUPS_PK. Also carries the unique index AP_AWT_GROUPS_U1, making it both the primary key and the documented business-key candidate. All foreign key relationships to this table join on this column.
  • NAME — The user-defined name of the withholding tax group, as presented in the Payables withholding tax group LOV and setup windows.
  • DESCRIPTION — Free-text description clarifying the purpose or scope of the group.
  • INACTIVE_DATE — The date from which the group is no longer selectable for new transactions. Groups with a null or future INACTIVE_DATE remain active.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle WHO audit columns recording when the row was last modified and by which user and login session.
  • CREATION_DATE, CREATED_BY — Standard audit columns recording row creation.

Importantly, AP_AWT_GROUPS does not itself store the individual tax codes that belong to the group. That association is held in the child table AP_AWT_GROUP_TAXES_ALL, which joins back on GROUP_ID. This separation allows a single group to map to multiple withholding tax codes without altering the group definition.

Common Use Cases and Queries

Typical usage centers on identifying active withholding tax groups, resolving the group assigned to a supplier or invoice, and reporting on withholding tax configuration.

Listing active groups:

  • SELECT group_id, name, description, inactive_date FROM ap.ap_awt_groups WHERE inactive_date IS NULL OR inactive_date > SYSDATE;

Resolving the withholding tax group assigned to a supplier:

  • SELECT s.vendor_name, g.name FROM ap.ap_suppliers s, ap.ap_awt_groups g WHERE s.awt_group_id = g.group_id;

Auditing invoices against their withholding tax group:

  • SELECT i.invoice_num, i.awt_group_id, g.name FROM ap.ap_invoices_all i, ap.ap_awt_groups g WHERE i.awt_group_id = g.group_id;

Locating the Payables system-level default group:

  • SELECT p.default_awt_group_id, g.name FROM ap.ap_system_parameters_all p, ap.ap_awt_groups g WHERE p.default_awt_group_id = g.group_id;

Reporting use cases include withholding tax register extracts, configuration audits comparing groups across environments, and reconciliation of supplier-level versus invoice-level withholding tax assignments.

Related Objects

The following tables reference AP_AWT_GROUPS through documented foreign keys, and are the most significant dependents:

Because GROUP_ID is referenced so broadly across Payables, any change to a group's active status or to its member tax codes propagates into every transaction that references it.