Results for “igm_number”

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

Overview

The table JA.JAI_CMN_BOE_HDRS_ALL is a core transactional entity within the JA — Asia/Pacific Localizations product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores Bill of Entry (BOE) header information that is generated whenever a BOE Invoice is created through the India Localization (IL) invoicing flow. In markets where customs clearance, import duty, and excise documentation are governed by local statutory rules, the BOE serves as the legal record of an import transaction, and this table is the master container for that record. Each row represents a single BOE header, tying together customs references, shipment logistics, supplier information, and monetary values that downstream BOE line and tax calculation logic consumes.

Because the object is an _ALL table, it participates in the standard multi-org filtering model, with ORG_ID and ORGANIZATION_ID columns present to segregate data by operating unit and inventory organization respectively. From a Data Vault modeling perspective, the heuristic classification identified in the metadata is standalone. That suggests the table functions effectively as an independent hub-like record, since its foreign key footprint is narrow and it does not sit inside a dense network of dependent links. Modeling efforts that normalize this table should treat BOE_ID as the natural business key anchor.

Key Information Stored

The table is documented with 72 physical columns in the 12.2.2 schema. The most operationally significant are summarized below.

• BOE_ID — The surrogate primary key, enforced by the unique index JAI_CMN_BOE_HDRS_PK. This is the single business-key candidate documented for the table and is the value that child BOE line records reference.
• ORGANIZATION_ID and ORG_ID — Multi-org and inventory organization context for the transaction.
• LEGAL_ENTITY_ID — Foreign key to FV_LEGAL_ENTITIES, identifying the legal entity that owns the import.
• BOE_TYPE, BOE_DATE, and BOE_WITHOUT_REFER_FLAG — Classify the BOE document and indicate whether it was created without a prior reference document.
• PORT_CODE, PORT_NAME, and PORT_OF_SHIPMENT — Customs port information.
• BOL_DATE and BOL_NUMBER — Bill of Lading date and reference, the shipping document underpinning the BOE.
• VESSEL_NAME, ROTATION_NO, and ROTATION_DATE — Vessel and voyage rotation details.
• IMPORT_SR_NUM and IMPORT_DATE — Import serial number and date assigned by customs.
• BOE_AMOUNT, AMOUNT_APPLIED, and AMOUNT_WRITTEN_OFF — Monetary totals tracking the assessed BOE value and its application against invoices.
• VENDOR_ID and VENDOR_SITE_ID — Supplier identification for the associated import invoice.
• CURRENCY_CODE, CURRENCY_RATE, CURRENCY_RATE_TYPE, and CURRENCY_RATE_DATE — Currency conversion context for the BOE amounts.
• STATUS — Lifecycle state of the BOE header (for example, open, applied, or closed).
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY — Standard EBS audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The extensibility (flexfield) block used for localization-specific custom data.

Common Use Cases and Queries

Functional and technical consultants query this table most often for customs reporting, duty reconciliation, and troubleshooting the IL BOE creation flow. A frequent starting point joins the header to the legal entity to produce a period-wise BOE register:

• BOE register by legal entity and date: filter on BOE_DATE and LEGAL_ENTITY_ID, then join FV_LEGAL_ENTITIES for the entity name.
• Outstanding duty exposure: compare BOE_AMOUNT against AMOUNT_APPLIED and AMOUNT_WRITTEN_OFF to identify unapplied balances.
• Customs documentation retrieval: select by BOL_NUMBER, IMPORT_SR_NUM, LICENSE_NUM, or IGM_NUMBER when auditing a shipment.
• Currency variance analysis: group by CURRENCY_CODE and CURRENCY_RATE_TYPE to review rate application across periods.
• Multi-org reporting: always constrain by ORG_ID when querying through the _ALL view to respect operating unit security.

A representative pattern joins the header to its detail lines and the legal entity:

• SELECT h.BOE_ID, h.BOE_DATE, h.BOE_AMOUNT, h.STATUS FROM JA.JAI_CMN_BOE_HDRS_ALL h, FV_LEGAL_ENTITIES le WHERE h.LEGAL_ENTITY_ID = le.LEGAL_ENTITY_ID AND h.ORG_ID = :p_org_id AND h.BOE_DATE BETWEEN :p_from AND :p_to;

Related Objects

The FK metadata establishes a small but critical relationship set. The primary relationships are:

• JAI_CMN_BOE_HDRS — Referenced through BOE_ID. This is the base header table underlying the _ALL variant and the primary anchor for joins.
• FV_LEGAL_ENTITIES — Referenced through LEGAL_ENTITY_ID; supplies legal entity attributes for reporting and security.
• BOE line / detail tables within the JA localization family — depend on BOE_ID to attach line-level duty and tax details to the header.
• Vendor tables (AP_SUPPLIERS / PO_VENDORS and vendor sites) — linked via VENDOR_ID and VENDOR_SITE_ID for supplier context on the import invoice.
• IL BOE Invoice process (JA_CMN_BOE_PKG and related PL/SQL APIs) — the programmatic layer that inserts and updates header rows when a BOE invoice is created.
• Multi-org views (for example, JAI_CMN_BOE_HDRS_V and _ALL secured synonyms) — the reporting layer over the base table, filtered by ORG_ID.

Together these objects form the customs processing footprint in the India Localization module, with JAI_CMN_BOE_HDRS_ALL acting as the header hub that other localization components reference through BOE_ID.