Results for “province_code”

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

Overview

The JL_ZZ_AP_AWT_TYPES table is a configuration and reference object within the JL (Latin America Localizations) product family of Oracle E-Business Suite. It stores withholding tax type records specifically maintained for Argentina and Colombia, where statutory withholding regimes require granular, jurisdiction-aware tax type definitions before Payables transactions can be processed, reported, or remitted to the tax authority. The table is owned by the JL schema and is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2.

Under the documented ETRM metadata, the heuristic Data Vault classification for this object is standalone. From a modeling perspective, this suggests the table behaves as an independent reference or lookup hub rather than a dependent satellite or a transactional link. It has no mined foreign-key relationships to other objects, and its structure is dominated by descriptive and control attributes rather than foreign keys to external entities — consistent with a code-and-description reference table that other processes consult rather than one that participates in a transactional grain.

Key Information Stored

The table contains 45 documented columns. The most significant are summarized below:

• AWT_TYPE_CODE — the primary key column of the JL_ZZ_AP_AWT_TYPES_PK constraint. It is also the sole business-key candidate, enforced by the unique index JL_ZZ_AP_AWT_TYPES_U1. This is the user-facing identifier used across withholding calculations and reporting.
• DESCRIPTION — the human-readable name of the withholding tax type.
• JURISDICTION_TYPE — the level (national, provincial, or municipal) at which the withholding applies.
• PROVINCE_CODE and CITY_CODE — geographic scoping for provincial and municipal jurisdictions.
• TAX_AUTHORITY_ID — reference to the tax authority to which the withholding is remitted.
• TAXABLE_BASE_AMOUNT_BASIS and VAT_INCLUSIVE_FLAG — define how the taxable base is computed and whether VAT is included.
• MIN_TAX_AMOUNT, MIN_TAX_AMOUNT_LEVEL, MIN_WH_AMOUNT, MIN_WH_AMOUNT_LEVEL — minimum threshold rules for taxability and withholding.
• FOREIGN_SUPPLIER_FLAG, SUPPLIER_EXEMPT_LEVEL, SIMPLIFIED_REGIME_FLAG — supplier-eligibility controls.
• USER_DEFINED_FORMULA_FLAG and DGI_TAX_TYPE_CODE — control flags and the Argentine DGI-specific tax type mapping.
• START_DATE_ACTIVE and END_DATE_ACTIVE — effective-dating of the withholding type.
• The standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the extensibility block (ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15).

Common Use Cases and Queries

This table is predominantly used for configuration validation, withholding calculation setup, and localization reporting. Typical patterns include:

• Listing all currently active withholding types: SELECT AWT_TYPE_CODE, DESCRIPTION, JURISDICTION_TYPE FROM JL.JL_ZZ_AP_AWT_TYPES WHERE SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE);
• Filtering provincial or municipal rules for a given geographic scope using PROVINCE_CODE and CITY_CODE.
• Reporting withholding types mapped to a specific TAX_AUTHORITY_ID for remittance reconciliation.
• Auditing configuration changes by inspecting LAST_UPDATED_BY and LAST_UPDATE_DATE.

Related Objects

The documented metadata describes this table as standalone with no mined foreign keys. It is therefore consultative in nature: withholding calculation and reporting logic in the JL localization modules reference AWT_TYPE_CODE rather than enforcing referential integrity directly against this table. Significant objects interacting with it include the Payables withholding results and localization setup views, which join on AWT_TYPE_CODE to resolve the descriptive and threshold attributes defined here.