Search Results jai_cmn_rg_round_hdrs_pk

Overview

The JAI_CMN_RG_ROUND_HDRS table is a core data object within the Asia/Pacific Localizations (JA) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It functions as a header-level repository for tracking the rounding of excise duty amounts on transactional documents, specifically excise invoices. This table is critical for ensuring compliance with regional tax regulations that mandate specific rounding rules for excise calculations. By storing a consolidated record of the rounding operation, it provides an audit trail and serves as a parent entity for detailed line-level rounding data, ensuring accurate financial reporting and reconciliation for excise liabilities.

Key Information Stored

The table's primary purpose is to store a unique instance of an excise rounding calculation. Its central identifier is the ROUNDING_ID, which serves as the primary key (JAI_CMN_RG_ROUND_HDRS_PK). This ID uniquely identifies each rounding event. The table links to the transactional source document via the SOURCE_HEADER_ID, which references the RCV_SHIPMENT_HEADERS table, indicating the rounding is often associated with receipt transactions. It also maintains a relationship to excise register entries via the REGISTER_ID, which references the JAI_CMN_RG_23AC_II_TRXS table. For auditing and process tracking, it stores standard EBS Concurrent Program context columns: PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_LOGIN_ID, and REQUEST_ID, linking to FND_CONCURRENT_PROGRAMS, FND_LOGINS, and FND_CONCURRENT_REQUESTS, respectively.

Common Use Cases and Queries

This table is primarily accessed for excise reporting, audit inquiries, and reconciliation processes. A common scenario involves tracing the rounded excise amount for a specific purchase receipt or excise invoice to verify calculation accuracy. Developers and support personnel may query this table to diagnose issues with excise posting or rounding discrepancies. A typical analytical query would join this header to its related lines and the original transaction source.

• Sample Query: To find rounding details for a specific receipt shipment header:
  SELECT hdr.*, ln.* FROM jai_cmn_rg_round_hdrs hdr JOIN jai_cmn_rg_round_lines ln ON hdr.rounding_id = ln.rounding_id WHERE hdr.source_header_id = <shipment_header_id>;
• Reporting Use Case: Generating a report of all rounding operations performed by a specific concurrent request for period-end closing.

Related Objects

The JAI_CMN_RG_ROUND_HDRS table is central to the excise rounding sub-schema, with defined relationships to several key tables.

• Referenced by this table (Outgoing Foreign Keys):
  • JAI_CMN_RG_23AC_II_TRXS via REGISTER_ID
  • RCV_SHIPMENT_HEADERS via SOURCE_HEADER_ID
  • FND_CONCURRENT_PROGRAMS via PROGRAM_APPLICATION_ID and PROGRAM_ID
  • FND_LOGINS via PROGRAM_LOGIN_ID
  • FND_CONCURRENT_REQUESTS via REQUEST_ID
• References this table (Incoming Foreign Keys):
  • JAI_CMN_RG_23AC_II_TRXS via its ROUNDING_ID column
  • JAI_CMN_RG_PLA_TRXS via its ROUNDING_ID column
  • JAI_CMN_RG_ROUND_LINES via its ROUNDING_ID column (detail lines for the header)