Results for “rounding_id”

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

Overview

JAI_BOE_ROUNDINGS is a table owned by the JA schema within the Asia/Pacific Localizations product family of Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store BOE (Bill of Exchange) rounding data — the small residual amounts that arise when tax and total values on a Bill of Exchange are calculated and must be reconciled to a payable whole. Rather than discarding or reallocating these residuals silently, the table records them explicitly, preserving an auditable trail between the calculated tax amount, the rounding adjustment applied, and the resulting total amount.

The object is described in the ETRM metadata as standalone, and a heuristic Data Vault classification therefore suggests it behaves as a satellite-style detail table attached to a parent BOE header, rather than as a pure hub or link. This is a modeling suggestion only; the physical foreign key to JAI_CMN_BOE_HDRS confirms a dependent, subordinate relationship in the operational schema. The table is marked VALID and contains twelve documented columns.

Key Information Stored

The surrogate primary key is ROUNDING_ID, enforced by the JAI_BOE_ROUNDINGS_PK constraint and mirrored by the unique index JAI_BOE_ROUNDINGS_U1. A second unique index, JAI_BOE_ROUNDINGS_U2, covers the combination of BOE_ID and TAX_ID, which is the true business-key candidate: it guarantees that a given tax line on a given Bill of Exchange carries at most one rounding record.

• ROUNDING_ID — surrogate primary key for the rounding record.
• BOE_ID — foreign key to JAI_CMN_BOE_HDRS, identifying the parent Bill of Exchange.
• TAX_ID — identifies the tax line to which the rounding applies; combined with BOE_ID it forms the unique business key.
• TAX_AMOUNT — the calculated tax value prior to rounding.
• ROUNDING_AMOUNT — the adjustment applied to reach a payable figure.
• TOTAL_AMOUNT — the resulting post-rounding total for the line.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OA Framework and concurrent programs.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS who-columns providing audit attribution.

Common Use Cases and Queries

The most frequent requirement is reconciliation reporting: proving that TAX_AMOUNT plus ROUNDING_AMOUNT equals TOTAL_AMOUNT for each BOE. A representative query joins the parent header and isolates non-zero adjustments:

• SELECT r.BOE_ID, r.TAX_ID, r.TAX_AMOUNT, r.ROUNDING_AMOUNT, r.TOTAL_AMOUNT FROM JA.JAI_BOE_ROUNDINGS r WHERE r.ROUNDING_AMOUNT <> 0 ORDER BY r.BOE_ID, r.TAX_ID;
• Aggregate rounding per Bill of Exchange: SELECT BOE_ID, SUM(ROUNDING_AMOUNT) FROM JA.JAI_BOE_ROUNDINGS GROUP BY BOE_ID;
• Detect orphan or duplicate business keys by grouping on BOE_ID, TAX_ID and filtering counts greater than one.
• Audit-driven extracts filtered on LAST_UPDATE_DATE and LAST_UPDATED_BY to trace who adjusted a rounding figure and when.

Typical consumers include period-end tax reconciliation reports, BOE printing programs, and localization support diagnostics where a total on a printed instrument does not agree with the underlying tax computation.

Related Objects

• JAI_CMN_BOE_HDRS — parent header table; joined via JAI_BOE_ROUNDINGS.BOE_ID = JAI_CMN_BOE_HDRS.BOE_ID. This is the only documented foreign key.
• JAI_CMN_BOE_LINES — line-level detail for the same Bill of Exchange, commonly joined through BOE_ID to align rounding with invoice lines.
• JAI_CMN_BOE_TAXES — tax detail carrying the TAX_ID referenced in the unique business key.
• JAI_BOE_ROUNDINGS_PK and JAI_BOE_ROUNDINGS_U1, JAI_BOE_ROUNDINGS_U2 — the enforcing constraints and unique indexes rather than separate data objects.
• Asia/Pacific localization tax and BOE concurrent programs that populate and validate these rows during BOE generation.

Because the table is classified as standalone with a single outbound foreign key, no downstream table depends on it directly; it is a leaf detail object within the BOE localization model.