Results for “tan_no”

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

Overview

JAI_AP_TDS_YEARS is a table owned by the JA schema (Asia/Pacific Localizations) in Oracle E-Business Suite 12.1.1 and 12.2.2. It holds setup information for financial periods used by the India Tax Deducted at Source (TDS) functionality within Oracle Payables. The table defines the fiscal year boundaries and associated TDS processing parameters that drive statutory withholding tax calculations and reporting for India-based legal entities.

Under a Data Vault modeling heuristic derived from its foreign key structure, JAI_AP_TDS_YEARS is classified as satellite-leaning. This suggests it is best understood as a descriptive, time-versioned attribute store that hangs off a parent business entity — here, the legal entity — rather than as a hub or link table in its own right. Its grain is defined by the combination of legal entity and financial year.

Key Information Stored

The table's primary key, JAI_AP_TDS_YEARS_PK, is composed of LEGAL_ENTITY_ID and FIN_YEAR. This composite is also the documented unique index and serves as the business-key candidate. LEGAL_ENTITY_ID is a foreign key to HZ_PARTIES, anchoring each row to a specific registered legal entity. FIN_YEAR identifies the financial period to which the setup applies.

The most important columns include:

• LEGAL_ENTITY_ID — the legal entity for which the financial period is defined.
• FIN_YEAR — the financial year label for the setup row.
• START_DATE and END_DATE — the effective date range of the period.
• TAN_NO — the Tax Deduction and Collection Account Number associated with the entity.
• TDS_ROUNDING_FACTOR — the rounding rule applied to TDS amounts.
• TDS_ROUNDING_START_DATE — the date from which the rounding rule takes effect.
• INCLUSIVE_TAX_FLAG — indicates whether tax is treated as inclusive in the taxable base.
• OBJECT_VERSION_NUMBER — optimistic locking control.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical reporting and validation scenarios resolve the active TDS period for a legal entity, confirm the TAN and rounding configuration, and reconcile threshold dates against transaction dates in Oracle Payables. A representative query retrieves the current setup for a given entity and year:

SELECT legal_entity_id, fin_year, start_date, end_date, tan_no,
tds_rounding_factor, tds_rounding_start_date, inclusive_tax_flag
FROM ja.jai_ap_tds_years
WHERE legal_entity_id = :p_legal_entity_id
AND fin_year = :p_fin_year;

For period-validity checks, filter by START_DATE and END_DATE to confirm whether a transaction falls within a defined financial period. For TAN verification, join to HZ_PARTIES on LEGAL_ENTITY_ID to resolve entity names in a report.

Related Objects

The documented foreign key references HZ_PARTIES via LEGAL_ENTITY_ID. Joining to HZ_PARTIES provides access to the party/legal entity name, party number, and status that contextualize each TDS year setup.

• HZ_PARTIES (via LEGAL_ENTITY_ID) — parent legal entity definition.
• JAI_AP_TDS_YEARS_PK — primary and unique index enforcing entity/year uniqueness.
• Oracle Payables (AP) invoice and withholding tax tables — consume the TDS period and rounding configuration during tax computation.
• Oracle Payables TDS reports and extracts — rely on this table for period and TAN validation.

Because the documented schema exposes only the primary key, unique index, and the HZ_PARTIES relationship, additional dependencies are inferred from the India TDS feature set. Implementations should treat this table as a setup/configuration object and avoid direct DML, preferring the standard Oracle localization setup forms.