Search Results jai_cmn_rg_round_lines




Overview
Explore in AI Chat

Overview

The JAI_CMN_RG_ROUND_LINES table is a core data object within the Oracle E-Business Suite Asia/Pacific Localizations module (product JA). Its primary function is to store detailed transactional line-level data that has been specifically considered for tax rounding calculations. This table operates as a child or detail table, capturing the granular information for each rounding event managed by the system. Its existence is critical for compliance with regional tax regulations in supported Asia/Pacific countries, where specific rules govern how tax amounts are rounded on invoices, receipts, and other financial documents. The table ensures a detailed audit trail of the rounding process by linking source transaction lines to the rounding logic applied.

Key Information Stored

The table's structure is designed to link rounding events to their source transactions and execution context. The primary key is ROUNDING_LINE_ID, which uniquely identifies each record. The most significant foreign key column is ROUNDING_ID, which ties each line to its parent header record in the JAI_CMN_RG_ROUND_HDRS table. To establish the connection to the original business transaction, the table stores SRC_LINE_ID and SRC_TRANSACTION_ID, which reference RCV_SHIPMENT_LINES and RCV_TRANSACTIONS, respectively, indicating its strong integration with the Receiving transactions. Furthermore, it includes standard Oracle EBS program execution columns—PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_LOGIN_ID, and REQUEST_ID—linking to FND_CONCURRENT_PROGRAMS, FND_LOGINS, and FND_CONCURRENT_REQUESTS. This provides full visibility into which concurrent process or user session initiated the rounding calculation for audit purposes.

Common Use Cases and Queries

A primary use case is auditing and reconciling tax calculations on received shipments. Analysts may query this table to verify which transaction lines had rounding applied and trace the rounding amounts back to the source. A common reporting pattern involves joining to the related header and source transaction tables. For example, to list all rounded lines for a specific receiving transaction, one might use a query such as:

  • SELECT rl.*, rt.transaction_id, rt.transaction_date FROM jai_cmn_rg_round_lines rl, rcv_transactions rt WHERE rl.src_transaction_id = rt.transaction_id AND rt.transaction_id = :p_trx_id;

Another critical scenario is troubleshooting rounding discrepancies. Support personnel can join to FND_CONCURRENT_REQUESTS using REQUEST_ID to identify the specific job run that processed the rounding, reviewing logs and parameters for error analysis. The table is essential for generating localized tax reports that must explicitly show rounded versus unrounded tax amounts to meet statutory requirements.

Related Objects

The JAI_CMN_RG_ROUND_LINES table has defined foreign key relationships with several key EBS tables, as documented in the ETRM metadata. These relationships are fundamental to its operation:

  • JAI_CMN_RG_ROUND_HDRS: The parent header table. Joined via JAI_CMN_RG_ROUND_LINES.ROUNDING_ID = JAI_CMN_RG_ROUND_HDRS.ROUNDING_ID.
  • RCV_SHIPMENT_LINES: The source receiving shipment line. Joined via JAI_CMN_RG_ROUND_LINES.SRC_LINE_ID = RCV_SHIPMENT_LINES.SHIPMENT_LINE_ID.
  • RCV_TRANSACTIONS: The source receiving transaction. Joined via JAI_CMN_RG_ROUND_LINES.SRC_TRANSACTION_ID = RCV_TRANSACTIONS.TRANSACTION_ID.
  • FND_CONCURRENT_PROGRAMS: The concurrent program definition. Joined via JAI_CMN_RG_ROUND_LINES.PROGRAM_APPLICATION_ID, .PROGRAM_ID.
  • FND_LOGINS: The user session. Joined via JAI_CMN_RG_ROUND_LINES.PROGRAM_LOGIN_ID = FND_LOGINS.LOGIN_ID.
  • FND_CONCURRENT_REQUESTS: The specific concurrent request instance. Joined via JAI_CMN_RG_ROUND_LINES.REQUEST_ID = FND_CONCURRENT_REQUESTS.REQUEST_ID.