Results for “boe_detail_id”

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

Overview

JAI_CMN_BOE_MATCHINGS is a transactional table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. Its documented purpose is to store Bank of Exchange (BOE) matchings together with receipt information. In the India localization workflow, a BOE is a customs document associated with imported goods, and the localization requires that the BOE be reconciled against the actual receipt of those goods in Oracle Purchasing and Receiving. This table is the association record that captures that reconciliation.

Based on the foreign key structure mined from the ETRM metadata, the object behaves like a link (junction) table in a Data Vault style model. It resolves a many-to-many relationship between the BOE header and the receiving transactions that consume or satisfy that BOE. Each row ties one BOE header to one shipment header, one shipment line, and one receiving transaction, carrying the matched amount. This classification is a heuristic modeling suggestion, not an Oracle-designated attribute; the physical table is a conventional relational entity with a surrogate primary key.

Key Information Stored

The table has fourteen documented columns. The most operationally significant ones are listed below.

• BOE_MATCHING_ID — the surrogate primary key, uniquely identifying each matching row. It is the sole unique index documented (JAI_CMN_BOE_MATCHINGS_PK). No separate business-key unique index is documented, so the business key is effectively the composite of the foreign key columns below.
• BOE_ID — foreign key to JAI_CMN_BOE_HDRS, identifying the BOE header to which this matching belongs.
• SHIPMENT_HEADER_ID — foreign key to RCV_SHIPMENT_HEADERS, identifying the receipt shipment header.
• SHIPMENT_LINE_ID — foreign key to RCV_SHIPMENT_LINES, identifying the specific receipt line matched.
• TRANSACTION_ID — foreign key to RCV_TRANSACTIONS, linking the matching to the inventory receiving transaction that generated the receipt quantity.
• AMOUNT — the value matched against the BOE for the associated receipt line or transaction; central to localization valuation and duty calculations.
• BOE_DETAIL_ID — associates the matching with the applicable BOE detail record, allowing matching at a finer granularity than the BOE header alone.
• REF_SEQ_NO — a sequence or reference number used for ordering and traceability of matchings.
• OBJECT_VERSION_NUMBER — the standard EBS optimistic locking column, incremented on each update.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS audit columns recording who created and last modified the row and when.

Common Use Cases and Queries

Typical reporting scenarios include reconciling BOEs to receipts for customs and excise reporting, identifying unmatched or partially matched BOEs, and auditing duty valuation by shipment. A representative query joins the matching rows to the BOE header and the receipt shipment header:

• SELECT m.boe_matching_id, m.boe_id, m.amount, h.boe_number FROM ja.jai_cmn_boe_matchings m, ja.jai_cmn_boe_hdrs h WHERE m.boe_id = h.boe_id;
• To find receipts matched to a BOE: join SHIPMENT_HEADER_ID to RCV_SHIPMENT_HEADERS and SHIPMENT_LINE_ID to RCV_SHIPMENT_LINES.
• To trace the inventory movement behind a matching: join TRANSACTION_ID to RCV_TRANSACTIONS.
• Totalled matching amounts per BOE support duty and valuation reports: SELECT boe_id, SUM(amount) FROM ja.jai_cmn_boe_matchings GROUP BY boe_id;

When querying, always qualify with the JA schema or use a synonym/APPS login, since the object is owned by JA. Concurrent extraction reports should filter on LAST_UPDATE_DATE for incremental loads.

Related Objects

The following objects are directly related through the documented primary and foreign key structure.

• JAI_CMN_BOE_HDRS — parent BOE header table, joined on BOE_ID.
• RCV_SHIPMENT_HEADERS — receipt shipment header, joined on SHIPMENT_HEADER_ID.
• RCV_SHIPMENT_LINES — receipt shipment line, joined on SHIPMENT_LINE_ID.
• RCV_TRANSACTIONS — receiving transaction, joined on TRANSACTION_ID.
• JAI_CMN_BOE_MATCHINGS_PK — the unique index enforcing the surrogate key on BOE_MATCHING_ID.
• Related JA localization objects such as BOE detail and BOE tax/valuation entities, which participate in the broader BOE reconciliation data model.

As a junction table, JAI_CMN_BOE_MATCHINGS has no dependent children of its own; it is consumed by localization reports and by the BOE reconciliation processes that read both the BOE side and the receiving side.