Search Results write_off_amount

Overview

JAI_BOE_WRITEOFF_TAXES_V is a reporting view owned by the APPS schema within the JA (Asia/Pacific Localizations) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes tax-level rounding and write-off information associated with Bank of England (BOE) rounding transactions processed by the Asia/Pacific localization routines. The view presents a consolidated projection of tax identifiers alongside the corresponding BOE identifier, the total BOE amount, and a write-off amount column. Because the object status is VALID, it can be queried directly in production environments without recompilation concerns.

The view is intended primarily for reporting and downstream integration, allowing localization logic, tax reconciliation reports, and custom extensions to query write-off data through a stable, simplified interface rather than joining the base rounding table directly. For users investigating the field write_off_amount, this view represents the standard access path in the JA schema.

Underlying Base Objects

The view is defined over a single referenced object: JAI_BOE_ROUNDINGS, exposed through a synonym in the APPS schema. The documented ETRM metadata for 12.2.2 lists only this one base object, and the view text confirms that all selected columns originate from the JAI_BOE_ROUNDINGS alias BR.

The definition of the view is:

• SELECT BR.TAX_ID, BR.BOE_ID, BR.TOTAL_AMOUNT BOE_AMOUNT, NULL WRITE_OFF_AMOUNT FROM JAI_BOE_ROUNDINGS BR

Notably, the WRITE_OFF_AMOUNT column is not sourced from a physical column in JAI_BOE_ROUNDINGS; it is projected as a literal NULL. This indicates that the view currently serves as a placeholder or forward-compatibility structure, preserving the column contract for consumers that expect a write-off amount even where no value is stored in the underlying table. TAX_ID, BOE_ID, and TOTAL_AMOUNT are the only genuinely sourced attributes.

Key Columns

• TAX_ID — The tax identifier associated with the BOE rounding record. This links the row to the tax configuration used during rounding.
• BOE_ID — The identifier of the BOE rounding transaction or document header. It is the primary grouping key for rounding activity.
• BOE_AMOUNT — Aliased from BR.TOTAL_AMOUNT, this column reports the total amount subject to BOE rounding for the given tax and BOE combination.
• WRITE_OFF_AMOUNT — Exposed as a NULL literal in the current definition. Queries referencing write_off_amount will return no values unless the view definition is subsequently revised to source an actual write-off figure.

Common Use Cases and Queries

Typical scenarios include tax reconciliation reports, BOE rounding variance analysis, and reconciliation of rounding outcomes against tax lines. Because WRITE_OFF_AMOUNT resolves to NULL, the view is most useful for retrieving BOE totals and identifiers by tax.

Example query returning all rounding rows for a specific tax:

• SELECT tax_id, boe_id, boe_amount, write_off_amount FROM apps.jai_boe_writeoff_taxes_v WHERE tax_id = :p_tax_id;

Example aggregating BOE amounts by BOE identifier:

• SELECT boe_id, SUM(boe_amount) total_boe_amount FROM apps.jai_boe_writeoff_taxes_v GROUP BY boe_id;

Example detecting potential write-off candidates (returns all rows, since the column is NULL):

• SELECT boe_id, tax_id, boe_amount FROM apps.jai_boe_writeoff_taxes_v WHERE write_off_amount IS NOT NULL;

Developers should treat WRITE_OFF_AMOUNT as reserved for future use and avoid dependent logic that assumes populated values. For confirmed write-off data, verify the current view definition in the target environment, as localization patches may alter the projection over the 12.1.1 to 12.2.2 upgrade path.