Search Results wsh_new_deliveries_n7

Overview

QA_ERES_SHIPPING is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that supports electronic records and electronic signatures (ERES) processing for shipping and delivery transactions. Its principal business purpose is to identify deliveries that satisfy a defined pickup-date window, evaluate the associated electronic signature and document records, and raise delivery-level events where compliance evidence is required. The package is relevant to regulated industries — most notably pharmaceutical, medical device, and food and beverage manufacturing — where 21 CFR Part 11 and equivalent electronic-record regulations require auditable evidence of shipment release and handling.

The package operates conditionally. All substantive processing is gated by the EDR_ERES_ENABLED profile option; when that profile is null or set to a value other than Y, the wrapper exits without performing delivery processing. This design allows ERES functionality to be enabled per responsibility, site, or user without modifying code.

Key Procedures and Functions

• WRAPPER — The public entry point, implemented as a concurrent-program style procedure with standard ERRBUF and RETCODE OUT parameters plus two IN arguments interpreted as a From Date and a To Date. It reads the EDR_ERES_ENABLED profile, converts the canonical date arguments using FND_DATE.CANONICAL_TO_DATE, and validates them. Per Bug 3352407, the From Date must be strictly less than the To Date, and the overall range may not exceed five days. Violations cause an immediate return with RETCODE of 2 and a descriptive ERRBUF message. On success it invokes DELIVERY_ERECORD and maps the returned status to RETCODE 0 (success) or 1 (warning, when some eRecords failed).
• DELIVERY_ERECORD — The internal worker procedure that performs the delivery-level eRecord processing for the validated date range. It accepts the From and To pickup dates and returns an out status flag initialized to FND_API.G_RET_STS_SUCCESS. It is responsible for selecting the qualifying delivery records and generating or updating the corresponding electronic record entries.
• RAISE_DELIVERY_EVENT — Raises the business event associated with a delivery eRecord, propagating the ERES outcome to the Oracle Workflow Business Event System so that downstream subscribers, notifications, or integrations can respond to the event.

The wrapper produces detailed progress and diagnostic output to the concurrent manager log via FND_FILE.PUT_LINE, including entry and exit markers, profile value, date-fetch confirmation, and validation errors.

Tables Accessed

• WSH_NEW_DELIVERIES — The shipping execution delivery header table accessed through an APPS synonym. It supplies the delivery records, including pickup dates, that fall within the requested date range. This is the primary driving table and the source of the "wsh_new_deliveries_n1" index referenced in user searches, which typically supports querying deliveries by organization, status, or date columns used by this package's date filter.
• EDR_PSIG_DOCUMENTS — The electronic signature and document table storing signature and document artifacts attached to ERES-controlled transactions. QA_ERES_SHIPPING reads and/or writes this table to associate, retrieve, or validate the electronic signature evidence tied to each qualifying delivery.

Usage Notes

QA_ERES_SHIPPING is normally invoked as a concurrent program submitted from the Shipping Transactions or ERES administration menus, passing the From and To pickup dates as concurrent program parameters. Because the range is restricted to five days, it is typically scheduled on a short recurring interval — often daily or several times per shift — rather than as a wide historical backfill. The From Date requirement is strict; passing null arguments causes the procedure to skip processing silently.

Programmatic invocation is possible from custom PL/SQL by calling QA_ERES_SHIPPING.WRAPPER directly with canonical date strings, but callers must handle the return-code convention: 0 for success, 1 for warning when one or more eRecords errored, and 2 for a validation failure. Note that when the ERES profile is disabled, the procedure returns success without having processed anything, so callers should not treat a zero return code as proof that records were evaluated. The package is not referenced by any other documented package, so its integration surface is limited to concurrent program submission and event subscribers listening for raised delivery events.