Results for “jai_cmn_boe_writeoffs”

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

Overview

JAI_CMN_BOE_WRITEOFFS is a transactional table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite, validated in both 12.1.1 and 12.2.2. It stores writeoff entries associated with Bills of Exchange (BOEs), the negotiable instruments used extensively in Oracle Financials for Asia/Pacific localization scenarios such as import/export financing and supplier settlement. Each row captures a discrete writeoff event applied against a BOE header, recording the amount written off, the effective date, and the stated business reason.

The table participates in the Oracle Payments and Receivables BOE lifecycle, where partial or full amounts on a BOE may be written off when they become uncollectible, disputed, or otherwise unrecoverable. Writeoff processing is a controlled financial activity, so this table preserves the audit trail required both for reconciliation and for regulatory reporting in JA-localized implementations.

Under a heuristic Data Vault classification mined from its foreign-key structure, this object is satellite-leaning. It references a parent hub-like entity (JAI_CMN_BOE_HDRS) via a foreign key and carries descriptive, time-stamped attributes (writeoff date, reason, amount) that describe the parent. This suggests modeling the table as a satellite on the BOE hub rather than a hub or link in its own right.

Key Information Stored

The documented schema contains 11 columns. The most operationally significant are listed below.

• BOE_WRITEOFF_ID — Surrogate primary key (JAI_CMN_BOE_WRITEOFFS_PK) uniquely identifying each writeoff entry.
• BOE_ID — Foreign key to JAI_CMN_BOE_HDRS, identifying the parent BOE to which the writeoff applies.
• WRITE_OFF_AMOUNT — The monetary value being written off against the BOE.
• WRITE_OFF_DATE — The effective accounting date of the writeoff; drives period and reconciliation logic.
• WRITE_OFF_REASON — Free-form or coded justification for the writeoff, supporting audit and reporting.
• OBJECT_VERSION_NUMBER — Optimistic-locking column used by the OAF/ADF framework during concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO-column audit trail.

No business-key unique index is documented on this table beyond the primary key; BOE_WRITEOFF_ID therefore serves as the surrogate identifier, while the (BOE_ID, WRITE_OFF_DATE) pairing is frequently used in practice as a de facto business locator.

Common Use Cases and Queries

Typical usage centers on reconciliation, aging, and audit reporting. A common pattern retrieves all writeoffs for a given BOE, ordered by date, to trace the writeoff history:

• BOE writeoff history — join JAI_CMN_BOE_WRITEOFFS to JAI_CMN_BOE_HDRS on BOE_ID to return writeoff details alongside BOE identifying attributes.
• Period writeoff reconciliation — SUM(WRITE_OFF_AMOUNT) grouped by WRITE_OFF_DATE within a GL period, compared against subledger postings.
• Reason-code analysis — aggregation by WRITE_OFF_REASON to identify recurring causes for management reporting.
• Tax detail drill-down — joining to JAI_BOE_WRITEOFF_TAXES on BOE_WRITEOFF_ID to present the tax breakdown of each writeoff for statutory filings.

A representative query joining header and tax details supports both subledger audit and external regulatory submissions.

Related Objects

• JAI_CMN_BOE_HDRS — Parent BOE header; joined on JAI_CMN_BOE_WRITEOFFS.BOE_ID = JAI_CMN_BOE_HDRS.BOE_ID.
• JAI_BOE_WRITEOFF_TAXES — Child table holding the tax breakdown; joined on BOE_WRITEOFF_ID.
• JAI_CMN_BOE_LINES — BOE line detail that contextualizes the writeoff against specific instruments.
• Receivables (AR) writeoff-adjacent objects — AR writeoff and adjustment logic that consumes BOE writeoff results in JA localizations.
• Oracle Payments (IBY) BOE processing logic — the functional framework that invokes writeoff creation and updates.

Together these objects form the JA BOE writeoff sub-model, with JAI_CMN_BOE_WRITEOFFS acting as the central satellite of descriptive writeoff activity.