Search Results matching_logic
Overview
INV_RCV_TXN_MATCH is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that centralizes the matching logic used during receiving and delivery transactions in Oracle Inventory and Oracle Purchasing. Its role is to correlate inbound and outbound supply records — shipment lines, lot and serial supply records, requisition and purchase order distributions, and order management lines — so that receipt, delivery, and return transactions decrement and create supply in a manner consistent with the underlying sourcing documents. In the context of Oracle EBS 12.1.1 and 12.2.2, the package is classified as an API of type OTHER, meaning it is intended for internal use by other receiving APIs rather than as a standalone public interface. It encapsulates the resolution rules that determine which order, distribution, lot, or serial a given receiving transaction applies against.
Key Procedures and Functions
The ETRM metadata documents a single public routine: MATCHING_LOGIC. This procedure performs the core matching operation for a receiving transaction. It evaluates the transaction context supplied by its callers — shipment header and line information, item and unit of measure details, requisition and purchase order distribution references, and lot or serial identifiers — and then identifies the corresponding supply records that must be consumed or created. Because the package is designed to be invoked by transactional APIs, MATCHING_LOGIC abstracts the detailed join and validation logic away from the individual receipt, delivery, and direct receipt APIs, allowing a single, consistent matching implementation to be reused across multiple transaction flows. No parameter list is documented in the metadata, and parameters should not be assumed.
Tables Accessed
INV_RCV_TXN_MATCH reads and writes a defined set of tables through APPS synonyms. Receiving and supply records are handled through RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, RCV_LOTS_SUPPLY, and RCV_SERIALS_SUPPLY, while inventory supply is represented in MTL_SUPPLY. Item and unit of measure validation uses MTL_SYSTEM_ITEMS and MTL_UNITS_OF_MEASURE, and lot validation uses MTL_LOT_NUMBERS. Sourcing references are resolved against PO_DISTRIBUTIONS, PO_DISTRIBUTIONS_ALL, PO_LINE_LOCATIONS, PO_REQUISITION_LINES, and PO_REQ_DISTRIBUTIONS_ALL. Where receiving originates from sales order demand, the package accesses OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL. These tables collectively provide the linkage between a physical receipt or delivery and the demand, requisition, or purchase order commitment it satisfies.
Usage Notes
This package is not a standalone user-facing interface. It is invoked indirectly by higher-level receiving APIs, including INV_RCV_STD_RCPT_APIS, INV_RCV_STD_DELIVER_APIS, INV_RCV_DIR_RCPT_APIS, and GML_RCV_DIR_RCPT_APIS, which are themselves called by Oracle Receiving forms, iProcurement receipt flows, and process manufacturing direct receipt programs. The package also references APPS.INV_RCV_COMMON_APIS and the SYS.STANDARD package, indicating that it depends on shared receiving utility code and standard PL/SQL constructs. In Oracle EBS 12.1.1 and 12.2.2, custom code should generally not call INV_RCV_TXN_MATCH directly; developers requiring receipt, delivery, or matching behavior should invoke the supported public receiving APIs, which in turn call this package. Because the matched supply logic underpins lot, serial, and distribution accounting, changes to this package should be treated as core receiving functionality and validated against standard receipt and delivery regression scenarios.
-
PACKAGE: APPS.INV_RCV_TXN_MATCH
12.2.2
-
PACKAGE: APPS.INV_RCV_TXN_MATCH
12.1.1
-
PACKAGE: APPS.INV_RCV_TXN_INTERFACE
12.1.1
-
PACKAGE: APPS.INV_RCV_TXN_INTERFACE
12.2.2
-
PACKAGE: APPS.GML_RCV_TXN_INTERFACE
12.1.1
-
PACKAGE: APPS.GML_RCV_TXN_INTERFACE
12.2.2
-
PACKAGE BODY: APPS.GML_RCV_TXN_INTERFACE
12.1.1
-
PACKAGE BODY: APPS.GML_RCV_TXN_INTERFACE
12.2.2
-
APPS.GML_RCV_TXN_INTERFACE dependencies on GML_RCV_TXN_INTERFACE
12.2.2
-
PACKAGE BODY: APPS.INV_RCV_TXN_MATCH
12.1.1
-
APPS.GML_RCV_TXN_INTERFACE dependencies on GML_RCV_TXN_INTERFACE
12.1.1
-
PACKAGE BODY: APPS.INV_RCV_TXN_MATCH
12.2.2
-
PACKAGE BODY: APPS.INV_RCV_TXN_INTERFACE
12.1.1
-
PACKAGE BODY: APPS.INV_RCV_TXN_INTERFACE
12.2.2
-
APPS.INV_RCV_TXN_MATCH dependencies on INV_RCV_COMMON_APIS
12.2.2
-
APPS.INV_RCV_TXN_MATCH dependencies on INV_RCV_COMMON_APIS
12.1.1
-
APPS.INV_RCV_TXN_INTERFACE dependencies on INV_RCV_COMMON_APIS
12.2.2
-
APPS.INV_RCV_TXN_INTERFACE dependencies on FND_PROFILE
12.2.2
-
APPS.INV_RCV_TXN_INTERFACE dependencies on INV_RCV_TXN_INTERFACE
12.2.2
-
APPS.INV_RCV_TXN_INTERFACE dependencies on INV_RCV_TXN_INTERFACE
12.1.1
-
APPS.INV_RCV_TXN_MATCH dependencies on INV_RCV_TXN_MATCH
12.1.1
-
APPS.INV_RCV_TXN_INTERFACE dependencies on FND_PROFILE
12.1.1
-
APPS.INV_RCV_TXN_INTERFACE dependencies on INV_RCV_COMMON_APIS
12.1.1
-
APPS.INV_RCV_TXN_MATCH dependencies on INV_RCV_TXN_MATCH
12.2.2
-
PACKAGE BODY: APPS.INV_RCV_DIR_RCPT_APIS
12.2.2
-
PACKAGE BODY: APPS.INV_RCV_DIR_RCPT_APIS
12.1.1
-
PACKAGE BODY: APPS.INV_RCV_STD_DELIVER_APIS
12.2.2
-
PACKAGE BODY: APPS.INV_RCV_STD_DELIVER_APIS
12.1.1