Search Results send_confirmation




Overview
Explore in AI Chat

Overview

APPS.RCV_RECEIPT_CONFIRMATION is a public PL/SQL package within the Oracle E-Business Suite Receiving module. The package is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the invoking session rather than the definer, which allows it to inherit the security context of the calling user or concurrent program. Its header carries a release-specific RCS identifier (RCVRCCNS.pls 120.0.12010000.6, dated 2010/04/13), indicating it is a shipping component of the EBS 12.1.1 and 12.2.2 code lines.

The package addresses two closely related business needs in the receiving flow. First, it generates and transmits receipt confirmation notifications to suppliers or trading partners, driving the outbound communication that tells a counterparty that goods have been received. Second, it resolves the operating unit name associated with a given organization identifier, a lookup that is frequently required when assembling notification content or validating the context in which a receipt confirmation is dispatched. The package therefore acts as a focused utility layer rather than a general-purpose receiving API.

Key Procedures and Functions

The ETRM metadata documents two procedures for this package.

  • SEND_CONFIRMATION — The primary entry point for the package. It carries the standard concurrent program interface signature (an out error buffer and an out numeric return code) followed by a set of parameters that scope the run. The documented parameters indicate that callers supply organizational context (operating unit / org identifier), optional deployment and client routing values, a transaction date range, and a receipt number range, with an optional XML document identifier. This signature shape is characteristic of a concurrent-program-capable entry point: the date and receipt ranges are used to select the population of receipts to confirm, while the organization parameter anchors the operating unit whose receipts are in scope. The procedure performs the selection, formatting, and dispatch of confirmation output for the matched receipts.
  • GET_OU_NAME — A resolution utility that accepts an organization identifier and returns the corresponding operating unit name through an out parameter. The organization identifier is optional in the signature, and when it is not supplied the procedure derives an appropriate value from the current execution context. This is the routine that answers the user query "get_ou_name" directly: it converts a numeric org identifier into the human-readable operating unit name that appears on confirmation documents and notifications.

Tables Accessed

The package reads three receiving tables, all through APPS synonyms:

  • RCV_SHIPMENT_HEADERS — The shipment header records that group received goods. These rows supply header-level attributes such as supplier, shipment number, and receiving organization, which define the scope and identity of each confirmation.
  • RCV_SHIPMENT_LINES — The shipment line detail, providing the item-level information that populates the body of the confirmation output.
  • RCV_TRANSACTIONS — The receipt transaction rows that record what was actually received. These drive the date-range and receipt-number-range filtering used by SEND_CONFIRMATION, since receipt activity is timestamped and identified here.

Together these tables provide the shipment context, line detail, and transaction evidence needed to build an accurate confirmation. The package is documented as referenced by zero other packages, indicating it is a top-level consumer rather than a shared library dependency.

Usage Notes

RCV_RECEIPT_CONFIRMATION is most commonly invoked in two ways. First, as a concurrent program: the SEND_CONFIRMATION signature is designed to satisfy the standard concurrent manager interface, so it can be scheduled or submitted from the Receiving responsibility to batch-notify trading partners of receipts within a specified date or receipt range. Second, from custom code: developers building extensions to the receiving flow call GET_OU_NAME whenever an org identifier must be translated into an operating unit name, and call SEND_CONFIRMATION when a bespoke process needs to emit confirmations outside the standard program controls.

Because the package is declared AUTHID CURRENT_USER, callers must ensure the invoking session or concurrent request has the necessary privileges on the underlying RCV tables. When invoking SEND_CONFIRMATION, supplying the organization identifier and at least one of the date or receipt ranges is essential to bound the selection; omitting them can result in an unbounded or context-defaulted run. GET_OU_NAME is safe to call repeatedly and is commonly used as a lightweight lookup before or during confirmation assembly.