Results for “process_printrecords”

8 results




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

Overview

The package body APPS.EDR_PRINT_PROCESS_PVT belongs to the Oracle E-Business Suite EDR (Electronic Document Review / Electronic Records) product family and is classified as a private (PVT) API within the APPS schema. Its stated purpose, taken directly from the header comment embedded in the source, is to act as the "Program to submit print job" together with related record-processing and acknowledgement logic. In EBS 12.1.1 and 12.2.2 this package forms part of the internal plumbing that EDR uses to move electronic records through a print lifecycle — submitting a print job, associating individual e-records to a print query, acknowledging completion of printing, and resolving hierarchical and descriptive metadata for those records.

The source version documented is 120.0.12000000.1 (dated 2007/01/18), which indicates the package has been stable across the 11i-to-12.x upgrade path and is carried forward unchanged into the 12.2.2 code line. The PVT classification is significant: Oracle does not publish this package as a supported public API, and all documented entry points are marked as private implementation detail.

Key Procedures and Functions

  • SUBMIT_PRINT_JOB — the primary entry point described as the "Program to submit print job." It accepts an API version, an initialization flag, and a query identifier, together with a wait-for-job boolean, and is intended to return a request ID and request status to the caller while populating the standard return status, message count, and message data outputs.
  • PROCESS_PRINTRECORDS — processes a collection of electronic record identifiers supplied as a table of VARCHAR2(255), with an option to include related records, and returns the resulting query identifier.
  • ACKNOWLEDGE_PRINT — acknowledges that a print request associated with a given query has been completed, following the standard API error-handling signature.
  • GET_PARENT_ERECORD_ID — returns the parent e-record identifier for a supplied child e-record, supporting hierarchy resolution during print processing.
  • GET_EVENT_DESCRIPTION — returns a human-readable description for a supplied event code.

Critically, every one of these procedures is stubbed. The bodies contain only a RETURN statement preceded by comments reading "-- stubbed." This means the documented behaviour is nominal; no business logic executes in the shipped 12.x version of this body.

Tables Accessed

The ETRM metadata lists no tables referenced via APPS synonyms for this package. This is consistent with the stub implementation: because no procedure performs any DML or query, no table dependencies are registered in the data dictionary. There are therefore no documented reads or writes to report, and the package holds no direct dependency on EDR record, query, or print tables in its shipped form.

Usage Notes

The package is referenced by zero other packages according to the documented metadata, which, combined with the stubbed bodies, confirms that it is effectively dormant in the standard 12.1.1 and 12.2.2 installations. Customers and integrators should not rely on it for custom print automation. Where EDR print processing is required, the supported route is through the EDR concurrent programs and the associated public EDR APIs, or through Oracle Document Management and the standard printing infrastructure. Any custom code that calls EDR_PRINT_PROCESS_PVT directly will receive a success return status but no functional outcome, since each procedure exits immediately. Modification of the package body is not advisable, as it is an Oracle-owned APPS object subject to patching; a stub-aware workaround is to implement required behaviour in a custom package that wraps the supported EDR public interfaces instead.