Search Results delivery_erecord




Overview
Explore in AI Chat

Overview

QA_ERES_SHIPPING is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports electronic records (eRecord) and electronic signature (eSignature) processing for outbound shipment and delivery transactions. Its central role is to bridge Oracle Warehouse Management and Shipping execution data with the Oracle Quality electronic records and electronic signatures framework, enabling organizations to satisfy regulatory compliance requirements such as 21 CFR Part 11. The package associates delivery records with digitally signed documents, and it exposes a programmatic event that other components can raise when a shipment is delivered.

The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, and it defines a constant for the event name oracle.apps.wsh.eres.delivery.shipment. This constant identifies the business event that the package raises through Oracle Workflow when a delivery eRecord is generated. The package dates from early EBS releases and remains present in 12.1.1 and 12.2.2, though it is marked noship in its header, indicating it is not shipped as a standalone product artifact but is instead a supporting internal object.

Key Procedures and Functions

  • WRAPPER — A concurrent-program style entry point that accepts standard concurrent request arguments and returns a completion status. It serves as the invocation shell through which the delivery eRecord process is submitted as a batch or on-demand request. It orchestrates the call to the core delivery eRecord logic.
  • DELIVERY_ERECORD — The core processing routine. It accepts a from-date and to-date range and returns a status indicator. It selects deliveries falling within the specified window, determines which require an electronic record, and drives the creation of the associated quality eRecord and electronic signature entries.
  • RAISE_DELIVERY_EVENT — Raises the shipment delivery business event for a specific delivery. It takes a delivery identifier and an optional delivery name, and returns an eRecord identifier along with a status. This procedure is the mechanism by which downstream subscribers are notified that a delivery eRecord has been produced.

Tables Accessed

  • EDR_PSIG_DOCUMENTS — Stores the electronic signature document records. The package reads and writes here to persist the signed document metadata associated with a delivery, linking the signature to the shipment transaction.
  • WSH_NEW_DELIVERIES — The shipping execution delivery header table. The package queries this table to identify deliveries in scope for eRecord generation and to obtain the delivery identifiers and names used in event raising.

Usage Notes

QA_ERES_SHIPPING is typically invoked in one of two ways. First, DELIVERY_ERECORD (often through WRAPPER) is submitted as a concurrent program, allowing scheduled or on-demand batch generation of delivery eRecords for a date range. Second, RAISE_DELIVERY_EVENT is called from custom code, workflow processes, or shipping confirmation logic when a discrete delivery must be signed and recorded in real time. Because the package is classified as OTHER and is not referenced by any other documented PL/SQL package, it is generally consumed directly by concurrent programs, forms personalizations, or bespoke integrations rather than through a documented public API layer. Implementers integrating courier or delivery services should treat the package as an internal eRecord generator for the shipping module and should not modify it, as it is an Oracle-owned object.