Search Results st_dtl_id




Overview
Explore in AI Chat

Overview

The table JAI_CMN_ST_MATCH_DTLS is a core data object within the Asia/Pacific Localizations (product code JA) of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It functions as a detailed transactional repository for sales tax reconciliation, specifically storing the matched relationships between individual tax lines from source transactions and the corresponding entries on statutory sales tax forms. Its primary role is to maintain a granular audit trail, ensuring that every tax liability or credit reported on a government form can be traced back to its original transaction within the EBS system. This linkage is critical for compliance, reporting accuracy, and supporting tax audits in jurisdictions requiring detailed form-based reporting.

Key Information Stored

The table's structure is defined by a composite primary key and foreign key relationships that enforce data integrity. The key columns are:

  • ST_HDR_ID: A foreign key referencing JAI_CMN_STFORM_HDRS_ALL. This column links the matched detail record to the specific header of the statutory sales tax form.
  • ST_DTL_ID: A foreign key, likely referencing a detail line identifier from a related transaction or tax table (though the exact foreign table is not fully specified in the provided metadata). This identifies the specific source transaction tax line being matched.
  • FORM_ID: A foreign key, potentially referencing a master list of form types or templates. This further qualifies the type of statutory form being populated.
Together, these columns create a unique record that pins a transaction detail (ST_DTL_ID) to a specific line or section on a specific instance of a tax form (identified by ST_HDR_ID and FORM_ID).

Common Use Cases and Queries

This table is central to reporting and reconciliation processes. A primary use case is generating or verifying the detailed supporting schedule for a filed tax return. For example, auditors or accountants may need to list all invoice lines that contributed to the total tax reported on a specific form line. A typical query would join this table to the form header and transaction detail tables using the foreign keys. Another critical use case is troubleshooting: if a tax amount on a form appears incorrect, this table allows tracing back to the source transactions for validation. A common SQL pattern involves filtering by ST_HDR_ID to retrieve all matched details for a given form submission.

Related Objects

JAI_CMN_ST_MATCH_DTLS is part of a tightly integrated schema for statutory tax reporting. Its primary relationships, as defined by its foreign keys, are:

  • JAI_CMN_STFORM_HDRS_ALL: This is the parent table for form submissions. The ST_HDR_ID foreign key establishes that every matched detail belongs to a single form header.
  • Transaction Tax Detail Tables: While the metadata excerpt does not explicitly name the foreign table for ST_DTL_ID, it logically points to transaction tax line tables within the JA localization, such as those storing invoice or journal entry tax lines.
This table is typically accessed via localization-specific programs and reports that automate the population and reporting of statutory tax forms, rather than being modified directly by end-users.