Results for “deductor_name”

16 results




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

Overview

JAI_AP_ETDS_REQUESTS is a table owned by the JA schema within the Oracle E-Business Suite Asia/Pacific Localizations (JA) product family. It stores the header-level details of each electronic Tax Deducted at Source (eTDS) request submitted from Oracle Payables, capturing the run parameters, organizational context, tax authority information, and output file details used when a deductee return is generated. In Oracle EBS 12.1.1 and 12.2.2, the table functions as the persistent record of a single eTDS generation event, anchoring the detailed deductee lines held in JAI_AP_ETDS_T through the shared BATCH_ID.

The ETRM metadata classifies this object heuristically as satellite-leaning in a Data Vault modeling sense. It holds descriptive, run-specific attributes around a business key (BATCH_ID) rather than acting as a pure transactional hub, although the presence of multiple foreign keys to master and transactional entities gives it some link-like characteristics. In practice, JAI_AP_ETDS_REQUESTS is best treated as a header or run-registration entity for eTDS processing rather than as a reference or master table.

Key Information Stored

The table contains 29 documented columns. The surrogate primary key is BATCH_ID, enforced through the unique index JAI_AP_ETDS_REQUESTS_PK. BATCH_ID is also the only documented business-key candidate and serves as the join pivot to JAI_AP_ETDS_T.

The most significant columns include:

Common Use Cases and Queries

Typical reporting scenarios include auditing eTDS runs by financial year, reconciling concurrent request output files, and validating deductor attributes against the tax authority and legal entity setup. Common SQL patterns join the table to FND_CONCURRENT_REQUESTS for submission status, to HR_ALL_ORGANIZATION_UNITS for organization names, and to JAI_AP_ETDS_T for deductee details.

  • Retrieve runs for a financial year: SELECT BATCH_ID, REQUEST_ID, ORG_TAN_NUMBER, FILENAME FROM JA.JAI_AP_ETDS_REQUESTS WHERE FINANCIAL_YEAR = :year;
  • Join to deductee lines: SELECT r.BATCH_ID, r.ORG_TAN_NUMBER, t.* FROM JA.JAI_AP_ETDS_REQUESTS r, JA.JAI_AP_ETDS_T t WHERE r.BATCH_ID = t.BATCH_ID;
  • Check concurrent request status: SELECT r.BATCH_ID, c.REQUEST_ID, c.PHASE_CODE, c.STATUS_CODE FROM JA.JAI_AP_ETDS_REQUESTS r, FND_CONCURRENT_REQUESTS c WHERE r.REQUEST_ID = c.REQUEST_ID;
  • List output files by organization: SELECT ORGANIZATION_ID, FILENAME, FILE_PATH, CREATION_DATE FROM JA.JAI_AP_ETDS_REQUESTS ORDER BY CREATION_DATE DESC;

Related Objects

  • JAI_AP_ETDS_T — child detail table joined on BATCH_ID, holding deductee-level eTDS lines.
  • FND_CONCURRENT_REQUESTS — concurrent request instance via REQUEST_ID.
  • FND_CONCURRENT_PROGRAMS — program definition via PROGRAM_APPLICATION_ID and PROGRAM_ID.
  • FND_LOGINS — execution login via PROGRAM_LOGIN_ID.
  • HZ_PARTIES — tax authority via TAX_AUTHORITY_ID.
  • HZ_PARTY_SITES — tax authority site via TAX_AUTHORITY_SITE_ID.
  • HR_ALL_ORGANIZATION_UNITS — three foreign keys covering LEGAL_ENTITY_ID, OPERATING_UNIT_ID and ORGANIZATION_ID.