Search Results rcv_interface_groups_s




Overview
Explore in AI Chat

Overview

JMF_SHIKYU_RCV_PVT is a private PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified as a private (PVT) application programming interface. The name derives from "Shikyu," the Japanese term for "payment" or "disbursement," indicating that the package supports receiving-related processing within Oracle's discrete manufacturing and shop floor execution modules (JMF). Its role is to accept receipt data staged in the Oracle Receiving open interface tables and move it into the receiving transaction and header interface structures so that the standard receiving transaction processor can validate and post it.

The package acts as a thin orchestration layer between external source systems and the core receiving APIs. Rather than exposing business logic to callers directly, it encapsulates the mapping and population of the RCV interface tables, thereby insulating upstream processes from structural changes in the receiving schema. Because it is a private package, it is not intended as a published integration point; it is consumed internally by other application modules.

Key Procedures and Functions

The package body exposes two documented program units:

  • PROCESS_RCV_HEADER — Handles the population and processing of receipt header information. It prepares header-level records destined for the receiving interface, ensuring that the source receipt data is properly staged before the receiving processor is invoked.
  • PROCESS_RCV_TRX — Handles receipt transaction (line and detail) processing. It stages individual transaction records so that quantities, items, and destination information are correctly represented in the interface before downstream validation.

No parameter lists are documented in the available metadata, and callers should refer to the actual package specification for signature details.

Tables Accessed

The package references the following objects through APPS synonyms:

  • RCV_HEADERS_INTERFACE and RCV_HEADERS_INTERFACE_S — the header-level staging table and its sequence, used to assign and persist receipt header interface records.
  • RCV_TRANSACTIONS_INTERFACE and RCV_TRANSACTIONS_INTERFACE_S — the transaction-level staging table and its sequence, used for receipt line and detail records.
  • RCV_INTERFACE_GROUPS_S — the sequence that generates interface group identifiers, allowing a batch of related header and transaction rows to be processed together and traced as a unit. This object is directly relevant to the search term "rcv_interface_groups_s," which users typically encounter when tracing how interface groups are numbered.
  • DUAL — used for simple single-row evaluations, such as sequence number retrieval.

The package also depends on FND_GLOBAL and FND_LOG for session context (user, responsibility, and organization identifiers) and for writing debug or diagnostic messages to the concurrent log.

Usage Notes

JMF_SHIKYU_RCV_PVT is typically invoked indirectly. It is referenced by two other packages and is not referenced by any database object outside that set, confirming its internal, private nature. Invocation normally occurs through receiving-related concurrent programs, shop floor or manufacturing forms, or custom PL/SQL routines that assemble receipt data and require the standard Receiving Open Interface to validate and post it.

When troubleshooting, developers commonly query RCV_INTERFACE_GROUPS_S and the interface tables to correlate an interface group with its staged headers and transactions. Because the package is private and undocumented at the parameter level in the ETRM, customizations should avoid calling it directly and instead rely on supported receiving APIs. Session context must be established via FND_GLOBAL before invocation, and FND_LOG entries provide the primary diagnostic trail for failed processing attempts.