Results for “exemption_start_date”

50+ results




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

Overview

JL_ZZ_AP_SUP_AWT_CD_ALL is a Latin America Localizations (JL) table that stores the withholding tax codes applicable to Argentine and Colombian suppliers within Oracle E-Business Suite. It functions as a configuration and master reference table, holding the supplier-level withholding code definitions that drive the calculation and application of supplier withholding during payables processing. The table resides in the JL schema and is marked VALID in the ETRM 12.2.2 physical schema, containing 31 documented columns.

Under the heuristic Data Vault classification mined from the foreign key structure, this object is modeled as a standalone entity. It is neither a pure hub, link, nor satellite in the classic sense: it carries its own surrogate primary key, a natural business key, effective-dating attributes, and descriptive columns within a single physical table. As a modeling suggestion, it can be treated as a self-contained reference dimension, with the effective-dated variants (EFFECTIVE_START_DATE and EFFECTIVE_END_DATE) supporting slowly changing dimension behavior.

Key Information Stored

The surrogate primary key is SUPP_AWT_CODE_ID, enforced by the JL_ZZ_AP_SUP_AWT_CD_ALL_PK constraint and reinforced by the unique index JL_ZZ_AP_SUP_AWT_CD_U1. Two additional business-key candidates are documented: JL_ZZ_AP_SUP_AWT_CD_U1 on SUPP_AWT_CODE_ID and JL_ZZ_AP_SUP_AWT_CD_U2 on the composite of SUPP_AWT_TYPE_ID, TAX_ID, and EFFECTIVE_START_DATE. The composite unique index U2 is the significant one, establishing that a given withholding type and tax identifier combination is unique per effective start date.

Among the most important columns:

Common Use Cases and Queries

The primary use case is resolving the effective withholding code for a supplier at a point in time, typically during payables invoice withholding calculation for Argentine and Colombian localizations. A common pattern joins the table to its type parent and filters on the effective date range:

  • Retrieve active withholding codes for a supplier by TAX_ID and SYSDATE between EFFECTIVE_START_DATE and EFFECTIVE_END_DATE.
  • Report suppliers with active exemptions by checking populated EXEMPTION_RATE and exemption date ranges.
  • Reconcile withholding applied on invoices by joining to JL_ZZ_AP_INV_DIS_WH_ALL on SUPP_AWT_CODE_ID.
  • Multi-org reporting filtered by ORG_ID.

Sample SQL pattern:

SELECT c.supp_awt_code_id, c.tax_id, c.exemption_rate
FROM jl_zz_ap_sup_awt_cd_all c
WHERE c.org_id = :p_org_id
AND TRUNC(SYSDATE) BETWEEN c.effective_start_date
AND NVL(c.effective_end_date, SYSDATE);

Related Objects

The most significant relationships documented in the metadata are:

  • JL_ZZ_AP_SUPP_AWT_TYPES — parent table referenced via SUPP_AWT_TYPE_ID, defining withholding type classifications.
  • JL_ZZ_AP_INV_DIS_WH_ALL — child table referencing this table via SUPP_AWT_CODE_ID; stores invoice distribution withholding details.
  • JL_ZZ_AP_SUP_AWT_CD_ALL_PK — the primary key constraint on SUPP_AWT_CODE_ID.
  • JL_ZZ_AP_SUP_AWT_CD_U1 — unique index on SUPP_AWT_CODE_ID.
  • JL_ZZ_AP_SUP_AWT_CD_U2 — composite unique index on SUPP_AWT_TYPE_ID, TAX_ID, EFFECTIVE_START_DATE.

These relationships establish the table as the central reference for supplier withholding code configuration within the Argentine and Colombian localization flows.