Search Results qty_matched

Overview

JAI_OM_LC_MATCHING_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the JA — Asia/Pacific Localizations product family. Its status is VALID in both the 12.1.1 and 12.2.2 releases documented in the ETRM repository. The view exposes letter of credit (LC) matching data associated with order headers and order lines captured for Asia/Pacific localizations.

The view exists primarily to provide a read-consistent, denormalized projection of order-to-letter-of-credit matching activity. Instead of requiring report authors, integrations, or custom concurrent programs to interrogate the base matching entity directly, JAI_OM_LC_MATCHING_V surfaces the same columns under a stable, published name. Because the view exposes ORDER_HEADER_ID and ORDER_LINE_ID as first-class columns, it is a natural join point between Order Management data and LC-related localization processing.

Underlying Base Objects

The view is defined over a single base object: the synonym JAI_OM_LC_MATCHINGS, which resolves to the APPS-owned matching entity. The view text is a straightforward projection with no joins, filters, groupings, or expressions:

• Base object: JAI_OM_LC_MATCHINGS (SYNONYM) — the physical matching table holding LC-to-order allocation records.
• Relationship: One-to-one column mapping. Every row and column in the view corresponds directly to a source row in the base synonym; no rows are eliminated or synthesized.

Because the view introduces no predicate and no aggregation, it behaves as a pass-through presentation layer. DML written against the view would be forwarded to the underlying object, though the view is conventionally treated as read-only for reporting and integration purposes. Any change to the base table's structure must be reflected in the view definition to preserve validity.

Key Columns

The view publishes fourteen columns. The most operationally significant are:

• SLNO — Serial or sequence number identifying the matching record.
• CUSTOMER_ID — Identifier of the customer party associated with the LC and order.
• ORDER_HEADER_ID — Primary key of the originating sales order header in Order Management. This is the column most commonly used to drive lookups, since the search context for this object is explicitly order_header_id.
• ORDER_LINE_ID — Primary key of the specific order line to which the LC quantity is applied.
• QTY_RELEASED — Quantity of the order line released against the letter of credit.
• QTY_MATCHED — Quantity of the order line successfully matched to the LC.
• LC_TYPE — Classification of the letter of credit instrument.
• LC_NUMBER — Business-facing LC reference number.
• AMOUNT — Monetary value matched or associated with the record.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard Oracle EBS WHO columns recording audit trail information.

Common Use Cases and Queries

Typical usage involves reconciling orders against letters of credit for Asia/Pacific trading scenarios, reporting released versus matched quantities, and feeding downstream customs or banking interfaces. Because the view carries both header and line identifiers, it supports drill-down from the order header to line-level LC allocations.

Retrieving all LC matching rows for a given order header:

• SELECT slno, order_line_id, qty_released, qty_matched, lc_type, lc_number, amount FROM apps.jai_om_lc_matching_v WHERE order_header_id = :p_order_header_id ORDER BY order_line_id;

Summarizing matched quantities by LC number:

• SELECT lc_number, lc_type, SUM(qty_released) released, SUM(qty_matched) matched, SUM(amount) total_amount FROM apps.jai_om_lc_matching_v GROUP BY lc_number, lc_type;

Identifying unmatched or partially matched allocations for a customer:

• SELECT order_header_id, order_line_id, qty_released - qty_matched outstanding FROM apps.jai_om_lc_matching_v WHERE customer_id = :p_customer_id AND qty_released > qty_matched;

These patterns confirm the view's role as a lightweight, query-friendly interface for LC matching data, with ORDER_HEADER_ID serving as the primary driving column for both retrieval and integration logic.