Results for “boe_type”

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

Overview

JAI_CMN_WRITEOFFS_T is a table owned by the JA schema within the Oracle E-Business Suite Asia/Pacific Localizations product (JA). As documented in the ETRM repository for releases 12.1.1 and 12.2.2, it is a temporary (staging/working) table that stores write‑off entries corresponding to a Bill of Entry (BOE). The BOE is the customs document used in India‑localized trade and excise processing, and write‑offs represent the portion of a BOE quantity or value that has been consumed, utilized, or otherwise applied against a customs obligation.

Because this is a temporary table, records are typically populated, consumed, and purged within a single processing cycle rather than retained as durable transactional history. In Data Vault terms, the mined foreign‑key structure suggests a satellite‑leaning classification: the table appears to carry descriptive and measurable attributes that qualify a parent BOE (referenced through BOE_ID) rather than acting as an independent hub of business keys. This classification is offered as a modeling suggestion only, derived heuristically from the documented foreign‑key relationships, and should be validated against the actual application logic.

Key Information Stored

The documented physical schema contains 21 columns. The most significant are:

• BOE_ID — Foreign key to JAI_CMN_BOE_HDRS; links each write‑off record to its parent Bill of Entry.
• BOE_TYPE — Classifies the customs document type associated with the write‑off.
• BOE_AMOUNT — The total customs value of the referenced BOE against which write‑offs are applied.
• WRITE_OFF_AMOUNT — The amount being written off in this record.
• AMOUNT_APPLIED — The portion of the write‑off amount already applied or consumed.
• EARLIER_WRITTEN_OFF_AMOUNT — Cumulative amount previously written off, used to derive the remaining balance.
• WRITE_OFF_DATE — The effective date of the write‑off transaction.
• WRITE_OFF_REASON — Free‑text or coded explanation for the write‑off.
• CUSTOMS_WRITE_OFF_ACCOUNT — The accounting identifier used to post the customs write‑off.
• CHART_OF_ACCOUNTS_ID — Foreign key to GL_MGT_SEG_UPGRADE_H; identifies the chart of accounts context.
• ORGANIZATION_NAME, ADDRESS_LINE_1, ADDRESS_LINE_2, ADDRESS_LINE_3, LOCATION_CODE — Party and location details captured for the write‑off.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Framework (OA Framework) or concurrent programs.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.

The documented metadata does not identify a named surrogate primary key or a unique business‑key index. BOE_ID and CHART_OF_ACCOUNTS_ID function as foreign‑key business identifiers, while BOE_ID combined with WRITE_OFF_DATE and WRITE_OFF_AMOUNT may be candidate composite keys in practice.

Common Use Cases and Queries

Typical uses include reconciling write‑off activity against remaining BOE balances, validating applied versus written‑off amounts, and producing customs reporting extracts. A representative query joining to the BOE header is:

• Outstanding write‑off analysis: SELECT w.BOE_ID, w.WRITE_OFF_AMOUNT, w.AMOUNT_APPLIED, w.EARLIER_WRITTEN_OFF_AMOUNT FROM JA.JAI_CMN_WRITEOFFS_T w WHERE w.WRITE_OFF_DATE BETWEEN :start_date AND :end_date;
• Join to header: SELECT h.*, w.* FROM JA.JAI_CMN_WRITEOFFS_T w, JA.JAI_CMN_BOE_HDRS h WHERE w.BOE_ID = h.BOE_ID;
• Chart of accounts reconciliation: Join on CHART_OF_ACCOUNTS_ID to GL_MGT_SEG_UPGRADE_H to tie write‑off accounting to segment definitions.

Because it is a temporary table, reports should generally be run within the same processing window in which the data is populated.

Related Objects

• JAI_CMN_BOE_HDRS — Primary parent; joined on JAI_CMN_WRITEOFFS_T.BOE_ID = JAI_CMN_BOE_HDRS.BOE_ID.
• GL_MGT_SEG_UPGRADE_H — Referenced via CHART_OF_ACCOUNTS_ID for accounting segment context.
• JA_CMN_BOE_* concurrent programs and BOE APIs — Populate and consume this temporary table during BOE write‑off processing.
• GL_JE_LINES / GL_JE_HEADERS — Downstream targets of the customs write‑off accounting generated from CUSTOMS_WRITE_OFF_ACCOUNT.
• AP_INVOICES_ALL / AP_INVOICE_LINES_ALL — Frequently reconciled against write‑offs for duty and customs variance reporting.