Results for “ship_status”

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

Overview

The JAI_CMN_MATCH_RECEIPTS table is a component of the Oracle E-Business Suite Asia/Pacific Localizations module (product code JA), created under the JA schema. Its documented purpose is to store matching details of issues against receipts within a trading organization. In practice, this table supports the localization-specific business processes that reconcile material issued out of inventory with the receipts that originally brought that material in, enabling the matching logic required by regional trading and excise-related workflows.

The table is classified as VALID within the ETRM 12.2.2 physical schema and contains 16 documented columns. Based on a heuristic Data Vault classification mined from its foreign key structure, this object leans toward a satellite modeling role. That is a modeling suggestion rather than a functional designation: the table carries descriptive and transactional attributes keyed to a parent transaction entity rather than representing an independent business hub or a pure associative link between two hubs. This interpretation is consistent with the fact that its foreign key points outward to a single parent transaction table (JAI_CMN_RG_23D_TRXS), a pattern typical of satellite constructs that hold context around a core transaction.

Key Information Stored

The documented primary key is JAI_CMN_MATCH_RECEIPTS_PK, a composite of three columns: RECEIPT_ID, REF_LINE_ID, and ORDER_INVOICE. These three columns are also the documented business-key candidates. The primary key is not a system-generated surrogate; it is a composite natural key derived from the receipt, the referenced line, and the originating order or invoice context.

The most significant columns include:

• RECEIPT_ID — Identifier of the receipt being matched; also the foreign key to JAI_CMN_RG_23D_TRXS.
• REF_LINE_ID and REF_LINE_NO — Identify the referenced line within the source document.
• ORDER_INVOICE — The order or invoice reference forming part of the composite key.
• SUBINVENTORY — The subinventory context in which the matching occurs.
• QUANTITY_APPLIED and RECEIPT_QUANTITY_APPLIED — Quantities matched against the issue and against the receipt, respectively.
• ISSUE_UOM and RECEIPT_QUANTITY_UOM — Units of measure for the applied quantities.
• SHIP_STATUS — Status indicator for the shipment/receipt lifecycle.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns maintained by the concurrent manager or form.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by Oracle Application Framework (OAF) screens.

Common Use Cases and Queries

Typical scenarios include reconciling issued quantities against receipts in a trading organization, reporting on unmatched receipts, and auditing localization-specific matching activity. A common query joins this table to its parent transaction table and aggregates applied quantities by status:

• Identify all matching records for a given receipt: SELECT * FROM JA.JAI_CMN_MATCH_RECEIPTS WHERE RECEIPT_ID = :p_receipt_id;
• Report applied quantities and UOM by subinventory: SELECT SUBINVENTORY, SUM(QUANTITY_APPLIED), ISSUE_UOM FROM JA.JAI_CMN_MATCH_RECEIPTS GROUP BY SUBINVENTORY, ISSUE_UOM;
• Join to the parent transaction: SELECT m.* FROM JA.JAI_CMN_MATCH_RECEIPTS m, JA.JAI_CMN_RG_23D_TRXS t WHERE m.RECEIPT_ID = t.RECEIPT_ID;
• Find rows pending shipment confirmation using SHIP_STATUS.

Related Objects

The most significant related object is the parent transaction table, referenced through the documented foreign key:

• JAI_CMN_RG_23D_TRXS — Referenced via JAI_CMN_MATCH_RECEIPTS.RECEIPT_ID; the core transaction record against which matching is performed.
• The composite unique index JAI_CMN_MATCH_RECEIPTS_PK — enforces uniqueness across RECEIPT_ID, REF_LINE_ID, and ORDER_INVOICE.

Because the ETRM metadata documents only a single outbound foreign key, additional dependencies on standard inventory and purchasing tables (for example receipt and subinventory entities) are inferred rather than explicitly documented and should be validated against the specific 12.1.1 or 12.2.2 environment before being relied upon in custom reporting or integration logic.