Search Results jai_cmn_boe_matchings




Overview
Explore in AI Chat

Overview

The JAI_CMN_BOE_MATCHINGS table is a core data object within the Asia/Pacific Localizations (JA) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It serves as a critical junction table that establishes and stores the matching relationships between Bills of Entry (BOE) and inbound receipt transactions. In the context of localized logistics and tax compliance for several Asia/Pacific countries, a Bill of Entry is a mandatory customs document. This table's primary role is to provide an auditable link between the customs declaration (the BOE) and the actual physical or financial receipt of goods within the Oracle Purchasing and Inventory modules, ensuring compliance with local regulatory reporting requirements.

Key Information Stored

The table's structure is designed to capture the essential foreign key relationships that define a matching. Its primary key is a system-generated identifier, BOE_MATCHING_ID. The most significant columns are foreign keys that link to the core transactional entities. The BOE_ID column references the JAI_CMN_BOE_HDRS table, identifying the specific Bill of Entry document. The transactional receipt side is captured through links to the Receiving module: SHIPMENT_HEADER_ID points to RCV_SHIPMENT_HEADERS, SHIPMENT_LINE_ID to RCV_SHIPMENT_LINES, and TRANSACTION_ID to RCV_TRANSACTIONS. This multi-faceted linkage allows the system to track the BOE association at the shipment header, line, and individual transaction level, providing granularity for matching and reporting.

Common Use Cases and Queries

The primary use case is to support reporting and reconciliation for customs compliance. Auditors or logistics personnel can query this table to verify which received goods have been declared on a BOE and vice-versa. A common query pattern involves joining to the BOE header and receipt transaction details to generate a reconciliation report. For example, to list all matchings for a specific BOE, one might use a SQL pattern such as: SELECT * FROM JAI_CMN_BOE_MATCHINGS m, JAI_CMN_BOE_HDRS b, RCV_TRANSACTIONS r WHERE m.BOE_ID = b.BOE_ID AND m.TRANSACTION_ID = r.TRANSACTION_ID AND b.BOE_NUMBER = '<BOE_NUMBER>';. Another critical use case is during the receipt process itself, where the application logic may reference this table to validate or enforce BOE matching rules before completing a transaction.

Related Objects

The JAI_CMN_BOE_MATCHINGS table sits at the intersection of the localization's BOE structure and Oracle's standard Receiving entities. Its documented foreign key relationships are fundamental:

  • JAI_CMN_BOE_HDRS: Linked via BOE_ID. This is the parent table for Bill of Entry header information.
  • RCV_SHIPMENT_HEADERS: Linked via SHIPMENT_HEADER_ID. The standard Oracle table for receipt shipment headers.
  • RCV_SHIPMENT_LINES: Linked via SHIPMENT_LINE_ID. The standard Oracle table for receipt shipment lines.
  • RCV_TRANSACTIONS: Linked via TRANSACTION_ID. The standard Oracle table for detailed receipt transactions (e.g., DELIVER, REJECT).

These relationships ensure data integrity and enable comprehensive joins for reporting across both localized and core EBS functionality.