Results for “matched_amount”

19 results




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

Overview

JA.JAI_CMN_ST_MATCH_DTLS is a transactional detail table within the JA — Asia/Pacific Localizations product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store information pertaining to Sales Tax Matched Details, providing the association between a Sales Tax header record and the underlying matched document form. In practice, this table acts as a matching bridge: it records which tax form (identified by FORM_ID) has been reconciled or matched against a given Sales Tax header (ST_HDR_ID) and a corresponding tax detail line (ST_DTL_ID), together with the amount that was matched.

From a data modelling perspective, the mined Data Vault classification for this object is link. This heuristic suggests treating JAI_CMN_ST_MATCH_DTLS as a relationship (link) entity connecting the Sales Tax header, the Sales Tax detail, and the tax reporting form, rather than as a standalone hub or a descriptive satellite. The composite primary key JAI_CMN_ST_MATCH_DTLS_PK over (ST_HDR_ID, ST_DTL_ID, FORM_ID) reinforces this interpretation, since it defines the uniqueness of the association itself.

Key Information Stored

The table contains ten documented columns in the 12.2.2 physical schema. The most significant are the three key columns and the matched amount attribute.

  • ST_HDR_ID — Foreign key to JA.JAI_CMN_STFORM_HDRS_ALL, identifying the Sales Tax header under which the matching occurred. This is the column most frequently referenced by users searching on st_hdr_id and is the first component of the composite primary key.
  • ST_DTL_ID — Identifies the Sales Tax detail line participating in the match; part of the composite primary key.
  • FORM_ID — Identifies the tax reporting form associated with the matched record; the third component of the composite primary key.
  • MATCHED_AMOUNT — The monetary value attributed to the matched relationship between the header, detail, and form. This is the principal non-key business attribute.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle EBS framework to control concurrent updates.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle WHO columns capturing audit trail information: when and by whom the row was created, last modified, and the login session responsible.

The surrogate primary key is the composite JAI_CMN_ST_MATCH_DTLS_PK spanning ST_HDR_ID, ST_DTL_ID, and FORM_ID. Business-key candidates are effectively these same three columns, since together they determine uniqueness of a matched detail record; no separate single-column unique index is documented.

Common Use Cases and Queries

Typical usage centres on reconciling tax header data against reported forms and on auditing matched amounts. A common pattern is to retrieve all matches for a given Sales Tax header:

  • SELECT st_hdr_id, st_dtl_id, form_id, matched_amount FROM ja.jai_cmn_st_match_dtls WHERE st_hdr_id = :p_hdr_id;
  • Joining to the header table to obtain header context: SELECT m.*, h.* FROM ja.jai_cmn_st_match_dtls m, ja.jai_cmn_stform_hdrs_all h WHERE m.st_hdr_id = h.st_hdr_id;
  • Aggregating matched amounts per form: SELECT form_id, SUM(matched_amount) FROM ja.jai_cmn_st_match_dtls GROUP BY form_id;
  • Audit reporting on recent changes using last_update_date and last_updated_by.

Because the table is Asia/Pacific localisation specific, queries are generally scoped to tax reporting and statutory form reconciliation rather than standard AR or AP subledger reporting.

Related Objects

The following objects are significant in relation to JAI_CMN_ST_MATCH_DTLS:

  • JA.JAI_CMN_STFORM_HDRS_ALL — Referenced through the foreign key on ST_HDR_ID; supplies the Sales Tax header against which matched details are recorded.
  • JAI_CMN_ST_MATCH_DTLS (self-referencing keys) — The ST_DTL_ID and FORM_ID foreign keys are documented as referencing this same table, indicating detail and form relationship columns.
  • JA.JAI_CMN_STFORM_HDRS_ALL and associated Sales Tax setup tables — Provide the form and header definitions that qualify the matched records.
  • JAI_CMN_ST_DETAILS / ST detail tables — Source of the ST_DTL_ID line values matched here.
  • Oracle EBS JA localisation concurrent programs and reports — Consume this table to produce statutory Sales Tax matched reports.

Overall, JAI_CMN_ST_MATCH_DTLS functions as a focused link table capturing the matched amount relationships required for Asia/Pacific Sales Tax reporting in Oracle EBS.