Search Results jai_ap_tds_pan_changes




Overview
Explore in AI Chat

Overview

JAI_AP_TDS_PAN_CHANGES is a transactional history table owned by the JA schema within Oracle E-Business Suite, delivered as part of the Asia/Pacific Localizations (JA) product family. It records the audit trail of Permanent Account Number (PAN) changes applied to supplier (vendor) records, together with the withholding tax configuration attributes that were modified during the same event. In the Indian localization context, PAN is the statutory taxpayer identifier issued by the Income Tax Department and is mandatory for TDS (Tax Deducted at Source) processing; therefore, any update to a vendor's PAN must be captured in a form that survives the overwrite of the current value on the vendor master. This table provides that historical persistence, allowing tax and audit teams to reconstruct which PAN applied to a payee at a given point in time and what threshold or exemption settings changed alongside it.

From a data-modeling perspective, the heuristic Data Vault classification for this object is link. The classification is derived from its foreign key topology: the table resolves relationships between vendor parties and concurrent programs rather than holding a single immutable business entity. It should be viewed as an associative record that ties a change event to the vendor, the request that performed the change, and the tax attributes affected.

Key Information Stored

The table contains fifteen documented columns. The surrogate primary key is PAN_CHANGE_ID, which uniquely identifies each change event and is the column to use in joins and de-duplication logic. The principal business attributes are:

  • PAN_CHANGE_ID — surrogate primary key for the change record.
  • VENDOR_ID — foreign key to HZ_PARTIES, identifying the supplier party whose PAN was altered.
  • OLD_PAN_NUM — the PAN value held on the vendor record before the change.
  • NEW_PAN_NUM — the PAN value written to the vendor record by the change.
  • REQUEST_ID — foreign key to FND_CONCURRENT_REQUESTS, identifying the concurrent program run that executed the update.
  • REQUEST_DATE — the date the change request was processed, providing the effective timestamp for the history entry.
  • VENDOR_SITE_ID_UPDATED — indicates whether the vendor site-level record was also updated as part of the same operation.
  • THHOLD_GRP_ID_UPDATED — records whether the withholding tax threshold group assignment was modified.
  • THHOLD_XCEP_ID_UPDATED — records whether the withholding tax threshold exception assignment was modified.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the OA Framework and concurrent processing to detect concurrent modification.

The audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN follow standard EBS WHO-column conventions and are populated automatically by the application tier.

Common Use Cases and Queries

The most frequent application of this table is statutory audit reconstruction: proving which PAN was on file for a supplier when a particular TDS deduction was made. A typical query joins the history to the payee to present a chronological change log:

  • Extracting the full PAN change history for a supplier: SELECT old_pan_num, new_pan_num, request_date FROM jai_ap_tds_pan_changes WHERE vendor_id = :p_vendor_id ORDER BY request_date DESC;
  • Identifying suppliers whose PAN changed during a reporting period for TDS return reconciliation: filter on REQUEST_DATE between the return period start and end dates.
  • Tracing the originating concurrent request: join REQUEST_ID to FND_CONCURRENT_REQUESTS to retrieve the program name, requesting user, and completion status, which supports SOX-style change attribution.
  • Detecting whether a PAN update also triggered withholding threshold reconfiguration, using the THHOLD_GRP_ID_UPDATED and THHOLD_XCEP_ID_UPDATED flags.
  • Data-quality monitoring for duplicate or blank PAN values introduced by mass updates, by grouping on NEW_PAN_NUM.

Related Objects

The documented foreign keys establish two direct dependencies, and adjacent JA and AP objects complete the functional picture:

  • HZ_PARTIES — joined on JAI_AP_TDS_PAN_CHANGES.VENDOR_ID to HZ_PARTIES.PARTY_ID; supplies the current party name, party number, and tax registration context.
  • FND_CONCURRENT_REQUESTS — joined on JAI_AP_TDS_PAN_CHANGES.REQUEST_ID to FND_CONCURRENT_REQUESTS.REQUEST_ID; provides program, phase, and status detail.
  • AP_SUPPLIERS — the vendor master that stores the current PAN and is the target of the update recorded here.
  • AP_SUPPLIER_SITES_ALL — site-level vendor records referenced by the site update indicator.
  • JAI_AP_TDS_THHOLD_GROUPS and JAI_AP_TDS_THHOLD_EXCEPTIONS — the withholding threshold and exception definitions associated with the updated identifiers.
  • JAI_AP_TDS_DEDUCTIONS — the applied deduction records that consume PAN for TDS computation and cross-reference the change history during audit.

Together these relationships make JAI_AP_TDS_PAN_CHANGES the authoritative audit link between supplier party identity, withholding tax configuration, and the concurrent process that altered them.