Results for “edr_temp_data_cleanup”

4 results




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

Overview

The concurrent program EDR_PRINT_TEMP_DATA_CLEANUP is an administrative utility owned by the EDR - E-Records product module within Oracle E-Business Suite. Its user-facing name in the ETRM documentation is E-record Print Utility Temporary Data Cleanup, and its documented description states that it exists "to clean up data stored in temp tables for generating mega-pdf." In practice, the program removes transient rows that accumulate in EDR staging tables while large, consolidated PDF documents—commonly referred to as "mega-PDF" output—are assembled by the E-Records print utilities. Because the E-Records print process can serialize substantial volumes of records into a single output file, intermediate data is written to temporary tables; without periodic purging, this data can grow and degrade both storage utilization and subsequent print performance.

According to the documented metadata for ETRM 12.2.2, the program is not enabled (Enabled: No). Administrators should confirm the current enabled state in their environment, since a disabled concurrent program cannot be submitted from the Submit Requests window until it is activated.

Execution Details

The documented execution attributes are as follows:

  • Execution Method: PL/SQL Stored Procedure
  • Argument Method: Standard
  • Executable: EDR_TEMP_DATA_CLEANUP
  • Execution File: EDR_UTILITIES.TEMP_DATA_CLEANUP
  • User Name: EDR Temporary Data Cleanup
  • Description: EDR Temporary Data Clean up
  • Subroutine Name: Not specified

The execution file reference EDR_UTILITIES.TEMP_DATA_CLEANUP indicates that the cleanup logic resides in the EDR_UTILITIES PL/SQL package as a stored procedure invoked directly by the concurrent manager. No subroutine override is documented.

How to Run

The program is submitted through the standard Concurrent Programs > Submit Requests (SRS) flow: navigate to Submit a New Request, select Single Request, search for the name E-record Print Utility Temporary Data Cleanup, and submit. Because it is a maintenance utility rather than a business-facing report, it is typically scheduled rather than run interactively.

The Argument Method is documented as Standard, and no parameters are enumerated in the ETRM excerpt. Where no arguments are defined, the program operates with default scope—generally purging all eligible temporary or orphaned rows. Sites that require bounded cleanup windows should verify whether parameters exist in their specific patch level. Scheduling considerations include running the program outside active E-Records print windows to avoid contention with an in-flight mega-PDF generation, and reviewing the concurrent manager log for the count of purged rows.

Related Objects

The cleanup program is logically tied to the E-Records print utility that populates the temporary tables it purges. Relevant associations include:

  • EDR_UTILITIES package—the execution file containing TEMP_DATA_CLEANUP.
  • EDR temporary/staging tables used during mega-PDF assembly.
  • The E-Records print utility concurrent programs that generate consolidated PDF output and depend on those temp tables.
  • Concurrent manager and SRS infrastructure, which governs submission, scheduling, and logging.

Because the ETRM metadata is limited, administrators should validate these associations against their instance's concurrent program definition and package specification before relying on them operationally.