Search Results matching_id




Overview
Explore in AI Chat

Overview

JAI_OM_LC_MATCHINGS is a table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a localization-specific data object that stores the association between Letters of Credit (LC) and the order, line, and delivery entities to which they have been matched. The table functions as the transactional intersection that records how much of an LC has been released and matched against specific order lines and delivery details, enabling compliance with LC-driven trade finance requirements common in Asia/Pacific deployments. Each matched record links a customer, an order header, an order line, and a delivery detail to a specific LC number and type.

From a Data Vault modeling perspective, the heuristic classification of this object is a link. This is inferred from its structure: it is dominated by foreign key relationships (CUSTOMER_ID, ORDER_HEADER_ID, ORDER_LINE_ID, DELIVERY_DETAIL_ID, LC_NUMBER) and carries transactional measures (QTY_RELEASED, QTY_MATCHED, AMOUNT). This suggests it behaves as a relationship table joining multiple business entities rather than a standalone hub or a descriptive satellite.

Key Information Stored

The table contains 20 documented columns. The most significant are:

  • MATCHING_ID — Surrogate primary key (JAI_OM_LC_MATCHINGS_PK) uniquely identifying each matching record.
  • LC_NUMBER — Foreign key to JAI_OM_LC_HDRS; identifies the Letter of Credit being matched.
  • LC_TYPE — Categorizes the nature of the LC (for example, sight or usance), driving matching rules.
  • CUSTOMER_ID — Foreign key to HZ_PARTIES; the party holding the LC.
  • ORDER_HEADER_ID — Foreign key to OE_ORDER_HEADERS_ALL; the order header against which the LC is matched.
  • ORDER_LINE_ID — Foreign key to OE_ORDER_LINES_ALL; the specific order line matched to the LC.
  • DELIVERY_DETAIL_ID — Foreign key to WSH_DELIVERY_DETAILS; the shipment/delivery line linked to the match.
  • QTY_RELEASED — Quantity released against the order line under the LC.
  • QTY_MATCHED — Quantity matched to the LC, supporting balance and shortfall analysis.
  • AMOUNT — Monetary value matched against the LC.
  • RELEASE_FLAG — Indicator of whether the quantity has been released.
  • SLNO — Serial/reference number used for ordering or grouping within the matching set.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF framework for concurrent updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns.
  • ATTRIBUTE1, ATTRIBUTE2 — Descriptive flexfield (DFF) columns for customerspecific extensions.

Common Use Cases and Queries

Typical usage centers on LC reconciliation, order fulfillment reporting, and outstanding LC balance analysis. A common query joins matching records back to the LC header and order header to report LC utilization:

  • Identifying all orders matched to a given LC: SELECT ORDER_HEADER_ID, ORDER_LINE_ID, QTY_MATCHED FROM JAI_OM_LC_MATCHINGS WHERE LC_NUMBER = :lc_no;
  • Reconciling matched versus released quantities per order line to detect discrepancies between QTY_MATCHED and QTY_RELEASED.
  • Reporting LC balance by customer: aggregating AMOUNT by CUSTOMER_ID and LC_NUMBER, joined to JAI_OM_LC_HDRS.
  • Delivery-level traceability: linking DELIVERY_DETAIL_ID to WSH_DELIVERY_DETAILS to confirm shipped quantities against LC-matched quantities.
  • Audit and version tracking using CREATED_BY, CREATION_DATE, and OBJECT_VERSION_NUMBER.

Related Objects

The table participates in a tightly coupled localization data model. The most significant related objects and their join columns are:

  • JAI_OM_LC_HDRS — via LC_NUMBER; parent LC header holding LC terms and customer.
  • HZ_PARTIES — via CUSTOMER_ID; the party (customer) associated with the LC.
  • OE_ORDER_HEADERS_ALL — via ORDER_HEADER_ID; the order to which the LC is applied.
  • OE_ORDER_LINES_ALL — via ORDER_LINE_ID; line-level matching detail.
  • WSH_DELIVERY_DETAILS — via DELIVERY_DETAIL_ID; shipping/delivery detail linkage.
  • OE_ORDER_LINES_ALL / OE_ORDER_HEADERS_ALL — the standard Order Management interface and APIs, which consumers use to validate LC-matched quantities during order entry and shipment.

Because the table is owned by JA and referenced across Order Management and Shipping, any purge, archival, or migration activity should respect referential integrity with these parent tables to preserve LC-to-order traceability.