Results for “source_invoice_id”
31 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The JAI_AP_TDS_REPOSITORY table is a core data object within the JA — Asia/Pacific Localizations product family in Oracle E-Business Suite. It resides in the JA schema and stores TDS (Tax Deducted at Source) repository information, capturing the full lifecycle of withholding tax computation, application, and adjustment against Oracle Payables invoices. The table serves as the central ledger that links tax deducted on a source invoice to the invoices and payments against which that tax is applied, resolved, or written back, including handling of supplier credit memos and unapplied amounts.
From a modeling standpoint, the metadata classifies this object heuristically as standalone within a Data Vault framework. Although it carries several foreign key references that would normally suggest a link or satellite role, the standalone classification reflects the table's function as a denormalized transaction repository rather than a normalized relational bridge. In practice, JAI_AP_TDS_REPOSITORY behaves as a transaction fact store keyed by TDS_REPOSITORY_ID and is populated during TDS calculation and adjustment processing for India and other Asia/Pacific localization regimes.
Key Information Stored
The table contains 66 documented columns. The most significant include:
- TDS_REPOSITORY_ID — the surrogate primary key, enforced by unique index
JAI_AP_TDS_REPOSITORY_U1. This is the sole documented business-key candidate and the primary join key for downstream consumers. - INVOICE_ID / INVOICE_NUMBER — the AP invoice on which the TDS event occurred.
- TDS_AUTHORITY_ID / TDS_AUTHORITY_SITE_ID — the tax authority and its site receiving the deduction.
- THRESHOLD_GRP_ID, THRESHOLD_HDR_ID, THRESHOLD_TYPE_ID, THRESHOLD_SLAB_ID — the threshold configuration chain that determined whether and how much tax applied.
- REGIME_ID / REGIME_CODE — the tax regime (from
JAI_RGM_DEFINITIONS) governing the calculation. - SOURCE_INVOICE_AMT, APPLIED_AMOUNT, UNAPPLIED_AMOUNT, BASE_TAX_AMOUNT — the monetary measures underpinning reconciliation.
- ORG_ID — the operating unit, essential for multi-org security and reporting.
- LEGAL_ENTITY_ID, ORG_TAN_NUMBER — the legal entity and its TAN registration used on the withholding certificate.
- SECTION_TYPE / SECTION_CODE, TAX_RATE, TAX_ID, TAX_CATEGORY_ID — the statutory section and rate applied.
- CHALLAN_NUMBER, CHECK_DATE, CHECK_DEPOSIT_DATE, BSR_CODE — remittance and bank deposit tracking information.
- PAYMENT_REFERENCE_ID, TDS_PAID — linkage to payment and the paid-flag status.
- MIGRATED, REQUIRED_FOR_ETDS — flags indicating legacy migration and e-TDS reporting eligibility.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
Common Use Cases and Queries
Typical use cases include TDS reconciliation reporting, statutory certificate generation (Form 16A / e-TDS returns), threshold-slab analysis, and supplier withholding audits. A common query traces all TDS rows for an invoice:
SELECT tds_repository_id, invoice_number, applied_amount, unapplied_amount, section_code, challan_number FROM ja.jai_ap_tds_repository WHERE invoice_id = :p_invoice_id;- For regime-wise totals:
SELECT regime_code, SUM(applied_amount), SUM(tds_paid) FROM ja.jai_ap_tds_repository WHERE org_id = :p_org_id AND accounting_date BETWEEN :p_from AND :p_to GROUP BY regime_code; - For pending remittances: filter on
TDS_PAID = 'N'and group byCHALLAN_NUMBERorLEGAL_ENTITY_ID. - For migrated records requiring review:
WHERE MIGRATED = 'Y'.
Related Objects
The following objects are most significant to JAI_AP_TDS_REPOSITORY, joined on the foreign keys documented in the ETRM metadata:
- JAI_AP_TDS_THHOLD_GRPS — joined on
THRESHOLD_GRP_ID; defines the threshold group. - JAI_AP_TDS_THHOLD_HDRS — joined on
THRESHOLD_HDR_ID; threshold header definition. - JAI_AP_TDS_THHOLD_TYPES — joined on
THRESHOLD_TYPE_ID; threshold type master. - JAI_AP_TDS_THHOLD_SLABS — joined on
THRESHOLD_SLAB_ID; slab rate details. - JAI_RGM_DEFINITIONS — joined on
REGIME_ID; the tax regime master. - FV_LEGAL_ENTITIES — joined on
LEGAL_ENTITY_ID; legal entity and TAN context. - AP_INVOICES_ALL — joined on
INVOICE_ID; source AP invoice details.
-
This table stores TDS repository information
-
View: IGS_FI_CREDITS 12.1.1
This view is a multi-org filter flat view based on table IGS_FI_CREDITS_ALL.
APPS.IGS_FI_CREDITS·↳ IGS_FI_CREDITS_ALL·Explore IGS module →
-
Commercial Receivables Open Interface table.
-
This table contains information about all credit or payment transactions and is the central repository for all credits and payments related information in Student Finance.
-
View: IGS_FI_CREDITS_V 12.1.1
This is a multi-org view based on org filtered view IGS_FI_CREDITS and join with view IGS_LOOKUPS_VIEW and IGS_FI_CR_TYPES view to resolve Lookup Meaning and Credit Type Names from IDs
APPS.IGS_FI_CREDITS_V·↳ IGF_LOOKUPS_VIEW·↳ IGS_CA_INST·↳ IGS_EN_GEN_003·Explore IGS module →
-
View: IGS_FI_CREDITS 12.2.2
This view is a multi-org filter flat view based on table IGS_FI_CREDITS_ALL.
Not implemented in this database·Explore IGS module →
-
VIEW: APPS.IGS_FI_CREDITS 12.1.1
-
VIEW: APPS.IGS_FI_CREDITS 12.1.1
-
View: IGS_FI_CREDITS_V 12.2.2
This is a multi-org view based on org filtered view IGS_FI_CREDITS and join with view IGS_LOOKUPS_VIEW and IGS_FI_CR_TYPES view to resolve Lookup Meaning and Credit Type Names from IDs
Not implemented in this database·Explore IGS module →
-
VIEW: APPS.IGS_FI_CREDITS_V 12.1.1
-
eTRM - JA Tables and Views 12.2.2
The 'JA_CN_VOUCHER_NUMBER' table stores the voucher number of GL journal lines.
-
eTRM - IGS Tables and Views 12.1.1
Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'.