Results for “port_type”

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

Overview

JAI_AP_BOE_AEL_V is a view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the JA (Asia/Pacific Localizations) product family. It is documented in ETRM as the "Base view of BOE" — a Bill of Entry reporting structure. The view exposes Bill of Entry header, agent, vendor, port, and vessel attributes side by side with the corresponding Oracle General Ledger journal header and journal line columns, so that BOE-related accounting entries (BOE writeoff and BOE rounding events) can be reconciled and reported against their source documents. In releases 12.1.1 and 12.2.2 the object holds VALID status in APPS and is a read-only reporting view rather than a transaction entry surface. Its accounting-event lineage (the "AEL" suffix, the hard-coded APPLICATION_ID of 7000, and the TRX_CLASS value 'JAI_BOE_WRITEOFF'/'JAI BOE WRITEOFF') indicates it is intended to feed Subledger Accounting-style reporting and audit extracts for Indian and wider Asia/Pacific BOE processing.

Underlying Base Objects

The documented base objects span four areas:

• Bill of Entry localizations: JAI_CMN_BOE_HDRS_ALL (header, aliased JCBH) and JAI_CMN_BOE_AGENTS (agent, aliased JCBA).
• General Ledger: GL_JE_HEADERS, GL_JE_LINES, GL_JE_CATEGORIES, GL_JE_SOURCES, GL_IMPORT_REFERENCES, GL_DAILY_CONVERSION_TYPES, and the GL_LOOKUPS view.
• Payables and HR setup: PO_VENDORS, PO_VENDOR_SITES_ALL, HR_LOCATIONS_ALL, ORG_ORGANIZATION_DEFINITIONS, and JA_LOOKUPS.
• Security/context functions: FND_GLOBAL, HR_GENERAL, and HR_SECURITY packages.

The header table is the driving object; GL_JE_HEADERS and GL_JE_LINES are joined through GL_IMPORT_REFERENCES, which is the standard bridge between subledger accounting events and GL journal lines. Vendor and site attributes are denormalized in from the Payables views, while HR_SECURITY and HR_GENERAL supply organization-level security enforcement, which is why the view appears to be org-secured in practice.

Key Columns

The column list is dominated by accounting-event attributes and BOE descriptive attributes. Core identification columns include APPLICATION_ID (7000), EVENT_TYPE (derived from the GL journal category — 'BOE WRITEOFF' or 'BOE ROUNDING'), TRX_CLASS ('JAI_BOE_WRITEOFF'), TRX_CLASS_NAME ('JAI BOE WRITEOFF'), TRX_HDR_ID (the BOE_ID value), TRX_HDR_TABLE ('JAI_CMN_BOE_HDRS') and SOURCE_TABLE. GL keys exposed are LEDGER_ID, JE_BATCH_ID, JE_HEADER_ID, JE_LINE_NUM, JE_CATEGORY, JE_SOURCE, and their user-facing names. Amount columns are ENTERED_CR, ENTERED_DR, ACCOUNTED_CR, ACCOUNTED_DR, alongside CURRENCY_CODE, CURRENCY_CONVERSION_DATE, CURRENCY_CONVERSION_RATE and CURRENCY_CONVERSION_TYPE. Accounting context is provided by CODE_COMBINATION_ID and ACCOUNTING_DATE (mapped from GJL.EFFECTIVE_DATE), with GL_TRANSFER_STATUS hard-coded to 'Y'. BOE-specific descriptive columns include BOE_NUMBER (aliased from JCBH.BOE_ID), BOE_TYPE, VENDOR_NAME, VENDOR_SITE_CODE, AGENT_CODE, AGENT_NAME, VESSEL_NAME, PORT_TYPE, PORT_NAME, COUNTRY_CONSIGNMNT, COUNTRY_ORIGIN, BOL_DATE, ORGANIZATION_NAME and LOCATION. Users searching on "boe_number" will find it exposed as BOE_NUMBER, which is the aliased BOE_ID column.

Common Use Cases and Queries

Typical uses include BOE writeoff reconciliation, GST/customs audit extracts, and tying BOE numbers to GL postings. Because the view enforces organization security through HR packages, queries should be run under a valid APPS responsibility with the correct operating unit context.

• Locate all GL lines for a specific BOE: SELECT boe_number, je_header_id, je_line_num, account ed_dr, accounted_cr, accounting_date FROM app s.jai_ap_boe_ael_v WHERE boe_number = :p_boe_number;
• Summarize writeoff versus rounding by ledger: SELECT ledger_id, event_type, SUM(accounted_dr), SUM(accounted_cr) FROM app s.jai_ap_boe_ael_v GROUP BY ledger_id, event_type;
• List BOEs by vendor and agent: SELECT boe_number, vendor_name, agent_name, port_name, bol_date FROM app s.jai_ap_boe_ael_v WHERE vendor_name = :p_vendor ORDER BY bol_date;
• Extract unaccounted amounts by source: SELECT boe_number, user_je_source_name, entered_dr, entered_cr FROM app s.jai_ap_boe_ael_v WHERE gl_transfer_status = 'Y' AND je_source = :p_source;

These queries illustrate the view's dual nature: it is both a BOE register (header, agent, vendor, port, vessel data) and an accounting-event ledger (GL journal headers and lines) joined through the import reference bridge, which makes it well-suited to reconciliation reporting that must trace a BOE number to its GL impact.