Results for “boe_writeoff_id”

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

Overview

JAI_BOE_WRITEOFF_TAXES is a table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. Its documented purpose is to store tax-level detail associated with Bank of Exchange (BOE) write-off transactions processed by the Oracle Financials for Asia/Pacific localization. A BOE in this context refers to the documentary credit instrument used in import/export settlements, and the write-off process records the accounting treatment applied when an outstanding BOE liability or related tax component is reduced, settled, or otherwise discharged. This table acts as the tax breakout of a write-off event, allowing the localization to hold one or more tax lines per write-off.

From a dimensional modeling perspective, the heuristic Data Vault classification supplied in the ETRM metadata is satellite-leaning. This suggests the table behaves as a descriptive detail store attached to a parent transaction rather than as an independent hub or a pure link. In practice, the object can be modeled as a satellite of the BOE write-off (parented through BOE_WRITEOFF_ID) and, at the tax-line grain, as a link associating a write-off with a specific tax identifier. The classification is heuristic and should be validated against actual usage patterns before being adopted in a warehouse design.

Key Information Stored

The documented physical schema for 12.2.2 comprises ten columns. The most significant are:

• WRITEOFF_TAX_ID — the surrogate primary key, enforced by the unique index JAI_BOE_WRITEOFF_TAXES_PK. It uniquely identifies each tax detail row.
• BOE_WRITEOFF_ID — the foreign key to JAI_CMN_BOE_WRITEOFFS, tying each tax line back to its parent write-off. Together with TAX_ID, it forms the business-key candidate JAI_BOE_WRITEOFF_TAXES_U2.
• TAX_ID — identifies the tax (tax regime, rate, or tax code reference) applied to the write-off. The composite unique index on (BOE_WRITEOFF_ID, TAX_ID) enforces one row per tax per write-off.
• TAX_AMOUNT — the monetary tax value written off for the given tax line; this is the principal reporting measure.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the OA Framework and PL/SQL APIs to detect concurrent updates.
• Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — record who created and last modified the row and when.

The surrogate key (WRITEOFF_TAX_ID) is distinct from the business-key candidates exposed by the two unique indexes, meaning integration logic should rely on (BOE_WRITEOFF_ID, TAX_ID) for idempotent matching rather than the generated identifier.

Common Use Cases and Queries

Typical usage centers on tax reconciliation, write-off reporting, and localization audits. A common pattern retrieves all tax lines for a given parent write-off:

• SELECT writeoff_tax_id, tax_id, tax_amount FROM ja.jai_boe_writeoff_taxes WHERE boe_writeoff_id = :p_writeoff_id;
• Aggregating tax written off over a period: join to JAI_CMN_BOE_WRITEOFFS on BOE_WRITEOFF_ID and filter on the parent's creation or write-off date, summing TAX_AMOUNT grouped by TAX_ID.
• Reconciliation to the tax repository: joining TAX_ID to the tax setup tables to validate that each applied tax exists and carries the expected rate.
• Audit trails: selecting CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE for change-tracking and SOX compliance reporting.

Related Objects

• JAI_CMN_BOE_WRITEOFFS — the parent table; joined via JAI_BOE_WRITEOFF_TAXES.BOE_WRITEOFF_ID = JAI_CMN_BOE_WRITEOFFS.BOE_WRITEOFF_ID. This is the only documented foreign key relationship.
• JAI_BOE_WRITEOFF_TAXES_PK and JAI_BOE_WRITEOFF_TAXES_U1/U2 — the primary and unique indexes governing uniqueness and access paths.
• Tax setup objects referenced through TAX_ID — the tax definition tables used for validation and rate lookup, which depend on this table for write-off tax facts.
• The BOE write-off concurrent programs and PL/SQL APIs that populate this table at write-off time, and any write-off inquiry or reporting views in the JA module that read it.