Results for “process_rcv_interface”

8 results




Overview
Explore in AI Chat

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

Overview

APPS.JMF_SHIKYU_AUTO_RCV_PROC is the package body of the Oracle E-Business Suite Auto-Receive Subcontracting Components Processor, delivered as part of the Oracle Manufacturing (Shikyu) subcontracting functionality. In the EBS 12.1.1 and 12.2.2 environments, the package performs automatic receipt of subcontracting components for outsourced manufacturing assemblies into the Manufacturing Partner organization. The receipt is triggered only after the predefined in-transit lead time has elapsed, ensuring that component ownership and inventory reflect the physical movement of goods between the shipping organization and the partner organization.

The source header identifies the file as JMFRSKUB.pls (version 120.26, dated 2010/11/29) and describes the package as the body file of the Auto-Receive Subcontracting Components Processor. The package is classified as OTHER in the ETRM repository and is owned by APPS. It is not referenced by any other documented package, indicating that it is invoked directly rather than through a dependency chain of PL/SQL wrappers.

Key Procedures and Functions

The documented interface comprises twelve procedures and functions. The principal entry point is AUTO_RCV_SUBCON_COMP, which drives the overall automatic receiving cycle for subcontracting components. AUTO_RECEIVE_BY_INVENTORY and AUTO_RECEIVE provide the inventory-scoped and receive-level processing paths, respectively.

  • VALIDATE_SHIP_FROM_TO — Verifies that the ship-from and ship-to organization pairing is valid before receipt processing proceeds.
  • VALIDATE_RECEIVE_DATE — Confirms that the computed receive date satisfies the required in-transit timing rules.
  • VALIDATE_RCV_ERROR — Interprets receiving interface errors so that failed rows are identified and handled.
  • COMPARE_LINES_QUANTITY — Compares ordered and shipped or received line quantities to determine what remains to be received.
  • GET_BACKORDER_SHIPPED_QUANTITY — Retrieves the shipped quantity associated with backordered lines; the history notes an added method for backordered lines in December 2005.
  • GET_IN_TRANSIT — Determines in-transit status, drawing transit dates from the shipping network as noted in the November 2005 history entries.
  • GET_CUSTOMER_ID — Resolves the customer identifier used in the receiving transaction context.
  • GET_SUPPLIER_ID — Resolves the supplier identifier necessary for the subcontracting receipt.
  • PROCESS_RCV_INTERFACE — Invokes JMF_SHIKYU_RCV_PVT.process_rcv_trx to post the receiving interface rows, including the po_line_location_id parameter added in October 2005.

Tables Accessed

The package reads and writes through APPS synonyms. JMF_SHIKYU_REPLENISHMENTS holds the replenishment records that identify the components to receive and the shipping method derived from the replenishment sales order header. OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL (with OE_ORDER_LINES) supply replenishment sales order detail. PO_DISTRIBUTIONS_ALL and PO_LINE_LOCATIONS_ALL provide purchasing distribution and line location context used when calling the receiving private API. RCV_HEADERS_INTERFACE is the staging table into which receiving records are inserted; bug fix 4961147 addressed duplicate inserts into this interface. MTL_PARAMETERS, MTL_SECONDARY_INVENTORIES, MTL_UNITS_OF_MEASURE, MTL_UNITS_OF_MEASURE_TL and MTL_INTERORG_SHIP_METHODS supply organization and unit-of-measure data and shipping method definitions. HR_ALL_ORGANIZATION_UNITS, HR_ALL_ORGANIZATION_UNITS_TL and HR_ORGANIZATION_INFORMATION resolve organization identifiers and attributes for the partner and shipping organizations.

Usage Notes

The package is designed for unattended, scheduled execution rather than interactive use. It is typically invoked by a concurrent program or a scheduled concurrent request that processes eligible replenishment lines after the in-transit lead time expires. Because the header history records removal of all fnd_file.put_line() debug calls and elimination of full table scans for performance, later versions favor set-based access over per-row logging. Customizations should call the documented entry points, such as AUTO_RCV_SUBCON_COMP or AUTO_RECEIVE_BY_INVENTORY, rather than internal validators, and should avoid direct inserts into RCV_HEADERS_INTERFACE given the historical duplicate-record defect.