Search Results jai_cmn_mtax_upd_dtls




Overview
Explore in AI Chat

Overview

The JAI_CMN_MTAX_UPD_DTLS table is a core data object within the JA (Asia/Pacific Localizations) module of Oracle E-Business Suite releases 12.1.1 and 12.2.2. It functions as a detailed transaction log for the Mass Tax Changes process. This process enables bulk updates to tax-related information across transactional documents, such as invoices and purchase orders. The table's primary role is to store a granular record for each individual line processed by a mass tax update run, capturing both the change details and any processing errors encountered. This provides a complete audit trail and is essential for troubleshooting and reconciliation.

Key Information Stored

The table stores a comprehensive set of attributes for each processed line. Its structure is defined by a primary key on MTAX_DTL_ID and a unique key that identifies a specific transaction line using BATCH_ID, DOCUMENT_NO, RELEASE_NO, DOCUMENT_LINE_NO, and SHIPMENT_NO. Key columns include BATCH_ID, which links to the parent header record (JAI_CMN_MTAX_HDRS_ALL), and OLD_TAX_CATEGORY_ID and NEW_TAX_CATEGORY_ID, which document the tax category change. The RELEASE_NO field, specifically noted in the user's search context, is critical for identifying the correct version or release of a document, particularly for complex transactions like blanket purchase order releases. Other important columns track the concurrent request (REQUEST_ID), program details (PROGRAM_ID, PROGRAM_APPLICATION_ID), and status or error messages resulting from the update attempt.

Common Use Cases and Queries

The primary use case is auditing and reporting on mass tax updates. Administrators query this table to verify the success of a batch run, identify lines that failed processing, and analyze the scope of changes. A common query involves joining to the header table to get summary batch information and filtering for errors.

  • Audit Report for a Batch: SELECT d.document_no, d.release_no, d.document_line_no, d.old_tax_category_id, d.new_tax_category_id, d.error_message FROM jai_cmn_mtax_upd_dtls d WHERE d.batch_id = :p_batch_id ORDER BY d.document_no, d.release_no;
  • Find Failed Lines: SELECT * FROM jai_cmn_mtax_upd_dtls WHERE error_message IS NOT NULL AND request_id = :p_request_id;
  • Track Changes for a Specific Document: SELECT * FROM jai_cmn_mtax_upd_dtls WHERE document_no = :p_doc_num AND release_no = :p_release_no;

Related Objects

JAI_CMN_MTAX_UPD_DTLS is centrally connected to several key EBS objects, primarily through foreign key relationships. The most direct link is to its parent header table, JAI_CMN_MTAX_HDRS_ALL, via the BATCH_ID column. It references the JAI_CMN_TAX_CTGS_ALL table twice: once for the OLD_TAX_CATEGORY_ID and once for the NEW_TAX_CATEGORY_ID, linking to the master list of tax categories. Integration with the EBS concurrent processing framework is established through foreign keys to FND_CONCURRENT_REQUESTS (REQUEST_ID), FND_CONCURRENT_PROGRAMS (PROGRAM_APPLICATION_ID, PROGRAM_ID), and FND_LOGINS (PROGRAM_LOGIN_ID). These relationships ensure the detail records are tied to the specific EBS job and user session that executed the mass update.