Search Results jai_cmn_boe_hdrs




Overview
Explore in AI Chat

Overview

The JAI_CMN_BOE_HDRS table is a core data object within the Oracle E-Business Suite Asia/Pacific Localizations module (product code JA). It serves as the primary repository for Bill of Entry (BOE) header information. Its specific functional role is to store this header data when a BOE Invoice is created through the Invoice Lifecycle (IL) process. This table is integral to localization compliance for countries, particularly in the Asia/Pacific region, that require detailed tracking of import documentation for tax and regulatory purposes. As a master transactional table, it is central to the BOE management sub-system, linking key entities like suppliers, organizations, and related BOE details.

Key Information Stored

The table's primary key is the BOE_ID, a unique identifier for each BOE document. Based on its documented foreign key relationships, the table stores several critical reference points. The VENDOR_ID and VENDOR_SITE_ID columns link the BOE to the supplier and supplier site in the Trading Community Architecture (HZ_PARTIES and HZ_PARTY_SITES). The ORGANIZATION_ID associates the BOE with the specific inventory or operating organization within the enterprise (HR_ALL_ORGANIZATION_UNITS). The LOCATION_ID ties the BOE to a physical place (HR_LOCATIONS_ALL). Finally, the AGENT_ID references a customs agent or broker record stored in the related JAI_CMN_BOE_AGENTS table. While the full column list is not provided, the structure indicates the table holds header-level attributes such as BOE number, date, port of entry, and status, which are then elaborated upon in child detail tables.

Common Use Cases and Queries

This table is primarily accessed for generating regulatory reports on import activities, reconciling BOE data with AP invoices, and troubleshooting the BOE creation process. Common operational queries involve joining the header with its detail lines and related master data. For instance, to retrieve a comprehensive BOE report for a specific vendor, a query would join JAI_CMN_BOE_HDRS with JAI_CMN_BOE_DTLS and party information. Another critical use case is identifying unmatched BOEs for financial accruals, which involves querying the header table and left-joining to the JAI_CMN_BOE_MATCHINGS table to find records without corresponding matches. Support and implementation teams often query this table to verify data integrity by checking for orphaned records where foreign key references to HZ_PARTIES or HR_ALL_ORGANIZATION_UNITS are invalid.

Related Objects

The JAI_CMN_BOE_HDRS table maintains extensive relationships within the localization schema and core EBS applications, as documented in the provided metadata.

  • Primary Key: JAI_CMN_BOE_HDRS_PK on BOE_ID.
  • Foreign Keys (Referenced by this table):
    • HZ_PARTIES via JAI_CMN_BOE_HDRS.VENDOR_ID
    • HZ_PARTY_SITES via JAI_CMN_BOE_HDRS.VENDOR_SITE_ID
    • HR_ALL_ORGANIZATION_UNITS via JAI_CMN_BOE_HDRS.ORGANIZATION_ID
    • HR_LOCATIONS_ALL via JAI_CMN_BOE_HDRS.LOCATION_ID
    • JAI_CMN_BOE_AGENTS via JAI_CMN_BOE_HDRS.AGENT_ID
  • Foreign Keys (Referencing this table):
    • JAI_CMN_BOE_DTLS via JAI_CMN_BOE_DTLS.BOE_ID
    • JAI_CMN_BOE_MATCHINGS via JAI_CMN_BOE_MATCHINGS.BOE_ID
    • JAI_CMN_BOE_WRITEOFFS via JAI_CMN_BOE_WRITEOFFS.BOE_ID
    • JAI_CMN_WRITEOFFS_T via JAI_CMN_WRITEOFFS_T.BOE_ID

This relationship map confirms JAI_CMN_BOE_HDRS as the central hub, with child tables storing line details, invoice matching records, and write-off transactions for each BOE header.