Search Results check_shipto_enforcement




Overview
Explore in AI Chat

Overview

RCV_TRANSACTIONS_INTERFACE_SV is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as an "OTHER" API object within the ETRM documentation for release 12.2.2 (and available in 12.1.1). The package encapsulates server-side validation and data-normalization logic used by the receiving open interface. Its central purpose is to inspect and pre-process rows staged in the RCV_TRANSACTIONS_INTERFACE table before the Receiving Transaction Processor converts them into actual receiving transactions. By performing validation, unit-of-measure conversion, date tolerance checking, and reference lookups at the interface layer, the package helps ensure that interface rows satisfy the business rules of the underlying receiving model prior to processing, thereby reducing downstream errors and rejected records.

The object is not a formal public API in the sense of a documented external call interface; rather it is a supporting service package invoked by other receiving-related packages and concurrent processing logic. It maintains two-way dependencies with shipment-related server-side views and packages such as RCV_SHIPMENT_HEADER_SV, RCV_SHIPMENT_LINE_SV, and RCV_SHIPMENT_OBJECT_SV, and it is referenced by eleven other packages within the APPS schema.

Key Procedures and Functions

ETRM documents eighteen procedures and functions in the package. The principal ones and their business purposes are:

  • NAME — helper routine used within the package, consistent with naming conventions applied to interface service logic.
  • CHECK_DATE_TOLERANCE — verifies that an interface transaction's dates fall within acceptable tolerances, guarding against receipts posted outside permitted windows.
  • CHECK_SHIPTO_ENFORCEMENT — validates that the ship-to destination specified on the interface record is permitted, enforcing ship-to constraints for the receiving transaction.
  • EXCHANGE_SUB_ITEM — handles substitution of sub-inventory or item references on the interface row before processing.
  • CONVERT_INTO_CORRECT_QTY — converts the interface quantity into the correct unit of measure quantity expected by the receiving transaction processor.
  • GET_ORG_ID_FROM_HR_LOC_ID — derives the inventory organization identifier from an HR location identifier, resolving the operating context for the interface record.

Tables Accessed

Through APPS synonyms the package reads and writes several base and interface tables. It inserts and updates RCV_TRANSACTIONS_INTERFACE and RCV_HEADERS_INTERFACE, which hold the staged receiving transactions and header information. It reads PO_HEADERS, PO_LINES, and PO_DISTRIBUTIONS to validate purchase order references, and MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_KFV for item validation. Unit-of-measure conversion uses MTL_UNITS_OF_MEASURE. Reason codes come from MTL_TRANSACTION_REASONS, organization defaulting from MTL_PARAMETERS, and tax handling from AP_TAX_CODES. FINANCIALS_SYSTEM_PARAMETERS supplies ledger and system configuration defaults, and RCV_ROUTING_STEPS provides routing information. The PLITBLM table is used for temporary storage of character data during processing.

Usage Notes

This package is invoked indirectly rather than directly by end users. Primary callers include RCV_PROCESSOR_PVT, INV_RCV_TXN_INTERFACE, INV_RCV_DIR_RCPT_APIS, INV_RCV_TXN_MATCH, CSP_RECEIVE_PVT, GML_RCV_TXN_INTERFACE, and GML_RCV_DIR_RCPT_APIS, along with RCV_RMA_TRANSACTIONS and the RCV_ROI transaction and return packages. It also participates in the Receiving Open Interface concurrent program flow, where data submitted via the Receiving Transactions Open Interface is validated and normalized before the Receiving Transaction Processor executes. Custom code that populates RCV_TRANSACTIONS_INTERFACE directly may indirectly rely on this package's validations; however, because it is not a published external API, customization should target the supported Receiving Open Interface and its documented public APIs rather than calling RCV_TRANSACTIONS_INTERFACE_SV directly. Its dependency on RCV_SHIPMENT_*_SV packages reflects tight coupling with the shipment data model in Oracle Purchasing and Inventory.