Results for “jai_boe_writeoff”

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

Overview

APPS.JAI_AP_BOE_AEL_V is a reporting view in the Oracle E-Business Suite localization layer for India (the JAI/ETRM schema). Its name follows the Subledger Accounting (SLA) "AEL" convention — Accounting Event Lines — and it is designed to expose Bill of Entry (BOE) write-off and rounding accounting entries in a flattened, query-ready form. It presents the accounting events associated with BOE adjustments alongside descriptive attributes of the originating Bill of Entry and its vendor, agent, port, and organization context.

The view functions as a bridge between the India BOE data model (JAI_CMN_BOE_* tables) and the Oracle General Ledger posting tables (GL_JE_HEADERS, GL_JE_LINES). It consistently identifies the event as 'JAI_BOE_WRITEOFF' or 'BOE Rounding' via a decode on the GL journal category, and tags every row with TRX_CLASS = 'JAI_BOE_WRITEOFF' and Application_Id = 7000. This makes it suitable for reconciliation reports, audit extracts, and custom dashboards that need to trace posted BOE write-off entries back to their source documents.

Underlying Base Objects

The view is defined over a join of ETRM BOE tables and standard Oracle subledger/GL dictionary objects. Documented base objects include:

• JAI_CMN_BOE_HDRS_ALL — the primary BOE header table, supplying BOE number, type, vessel, port, country of consignment/origin, BOL date, and audit columns.
• JAI_CMN_BOE_AGENTS — provides agent code and agent name linked to the BOE.
• GL_JE_HEADERS / GL_JE_LINES — the journal header and line detail for the posting, supplying JE header ID, line number, entered/accounted amounts, and code combination.
• GL_JE_CATEGORIES / GL_JE_SOURCES — dictionary tables used to derive user-facing category and source names.
• GL_IMPORT_REFERENCES — links GL lines back to the import (BOE) source.
• GL_DAILY_CONVERSION_TYPES — resolves the currency conversion type.
• GL_LOOKUPS / JA_LOOKUPS — value sets for GL transfer status and port type descriptions.
• PO_VENDORS / PO_VENDOR_SITES_ALL — vendor name and site code for the BOE supplier.
• ORG_ORGANIZATION_DEFINITIONS / HR_LOCATIONS_ALL — operating unit and location context.
• Packages referenced indirectly: FND_GLOBAL, HR_GENERAL, and HR_SECURITY, used for session/security context and descriptive flexfield resolution.

Key Columns

• Application_Id, Trx_Class, Trx_Class_Name — constant identifiers marking the row as a BOE write-off event.
• Event_Type — decoded from the GL journal category to 'BOE Writeoff' or 'BOE Rounding'.
• Trx_Hdr_Id / Trx_Hdr_Table — BOE_ID and the source table name (JAI_CMN_BOE_HDRS), enabling drill-back.
• Je_Category, Je_Source, User_Je_Category_Name, User_Je_Source_Name — human-readable GL category and source.
• Je_Header_Id, Je_Line_Num, Ledger_Id, Je_Batch_Id — GL posting keys and ledger context.
• Entered_Dr / Entered_Cr / Accounted_Dr / Accounted_Cr — debit and credit amounts at both entered and accounted levels.
• Currency_Code, Currency_Conversion_Date, Currency_Conversion_Rate, Currency_Conversion_Type — currency and conversion detail.
• Code_Combination_Id, Accounting_Date, Gl_Transfer_Status — accounting flexfield, effective date, and transfer status ('Y' = transferred).
• Boe_Number, Boe_Type, Vendor_Name, Vendor_Site_Code, Agent_Code, Agent_Name — BOE and party descriptors.
• Vessel_Name, Port_Type, Port_Name, Country_Consignmnt, Country_Origin, Bol_Date — shipment and customs attributes.
• Organization_Name, Location, Creation/Last_Update audit columns — organizational and audit context.

Common Use Cases and Queries

Typical uses include BOE write-off reconciliation, GST/customs audit trails, and subledger-to-GL tie-outs. A common pattern filters by event type and ledger:

SELECT boe_number, event_type, je_header_id, je_line_num,
  entered_dr, entered_cr, accounted_dr, accounted_cr, gl_transfer_status
FROM apps.jai_ap_boe_ael_v
WHERE ledger_id = :p_ledger
  AND event_type = 'BOE Writeoff'
  AND accounting_date BETWEEN :p_from AND :p_to;

To trace a specific BOE back to its GL posting, filter on boe_number or trx_hdr_id. For rounding-only analyses, filter event_type = 'BOE Rounding'. Because the view already resolves user-facing names for category, source, lookup, and location, it reduces the need for additional joins in downstream reports.