Deleting a Schedules Request

How to delete the saved schedules, which were saved from the ‘Schedules’ tab of the ‘Submit Request’ window.
There is no standard functionality to delete any saved schedule.

The saved schedules are being stored in the table fnd_conc_release_classes_vl.
Select release_class_id, application_id, release_class_name schedule_name,
description, class_type schedule_type
from fnd_conc_release_classes_vl
where owner_req_id is null
and enabled_flag != ‘N’
and nvl(start_date_active,sysdate) <= sysdate
and nvl(end_date_active, sysdate) >= sysdate
order by release_class_name

If you want to delete any saved schedule from the LOV, then you can perform any of the following:
Delete the row from the table FND_CONC_RELEASE_CLASSES_VL for the saved schedule.
It will be better to update the ENABLED_FLAG = ‘N’ for the saved schedule instead of deleting the row from the table FND_CONC_RELEASE_CLASSES_VL.

thanks – shivmohan

Overview of Concurrent Programs and Requests

Overview of Concurrent Programs and Requests

A concurrent program is an executable file that runs simultaneously with other concurrent programs and with online operations, fully utilizing your hardware capacity. Typically, a concurrent program is a long-running, data-intensive task, such as posting a journal or generating a report.

Request Groups and Request Sets

Reports and concurrent programs can be assembled into request groups and request sets.

o A request group is a collection of reports or concurrent programs. A System Administrator defines report groups in order to control user access to reports and concurrent programs. Only a System Administrator can create a request group.

o Request sets define run and print options, and possibly, parameter values, for a collection of reports or concurrent program. End users and System Administrators can define request sets. A System Administrator has request set privileges beyond those of an end user.

Standard Request Submission and Request Groups

Standard Request Submission is an Oracle Applications feature that allows you to select and run all your reports and other concurrent programs from a single, standard form. The standard submission form is called Submit Request, although it can be customized to display a different title.

o The reports and concurrent programs that may be selected from the Submit Requests form belong to a request security group, which is a request group assigned to a responsibility.

o The reports and concurrent programs that may be selected from a customized Submit Request form belong to a request group that uses a code.

As System Administrator you can limit the number of requests that may be active (status of Running) for an individual user. This ensures that a user cannot monopolize the request queue. For example, if a user with an Active Request Limit of 5 submits 20 requests, only 5 requests will be run at the same time. The remaining requests will be run when the number of active requests for the user drops below 5. Use the Profile Options window to set the Concurrent: Active Request Limit profile. To set a global limit for all users, set this option at the site level. You can then modify limits for individual users by setting this profile option at the User level.

do share you feedback and comments. thanks – shivmohan purohit

How to Find a Particular Scheduled Workbook’s Result Set Table in Discoverer

hello discoverer friends, here a good technical insight within oracle discoverer for scheduled report, what are the tables behind and how they linked. hope you would like n find it useful. do share ur feedback to improve future articles.



How to Find a Particular Scheduled Workbook’s Result Set Table in Discoverer

1. Create a simple Discoverer workbook based on SCOTT.DEPT table, workbook name is ‘DEPT’
2. Schedule DEPT workbook as ‘SCOTT’ user
3. Wait until the scheduled job has completed; in the Scheduling Manager the report status is ‘Ready’
4. Connect to SQLPlus as the EUL owner 




203443      DEPT

6. Select BS_ID, BS_BR_ID, BS_SHEET_NAME from EUL5_BATCH_SHEETS where BS_BR_ID=’203443‘;

SQL> select BS_ID, BS_BR_ID, BS_SHEET_NAME from EUL5_BATCH_SHEETS where BS_BR_ID=’203443′;

203444      203443             Sheet 1


7. Select BQ_ID, BQ_BS_ID from EUL5_BATCH_QUERIES where BQ_BS_ID=’203444‘;

select BQ_ID, BQ_BS_ID from EUL5_BATCH_QUERIES where BQ_BS_ID=’203444′;

——————– ———
203445      203444


8. Select BQT_ID, BQT_BQ_ID, BQT_TABLE_NAME from EUL5_BQ_TABLES where BQT_BQ_ID=’203445‘;

select BQT_ID, BQT_BQ_ID, BQT_TABLE_NAME from EUL5_BQ_TABLES where BQT_BQ_ID=’203445′;

203454         203445                EUL5_B070924102545Q1R1

This shows that the scheduled workbook ‘DEPT: sheet1’ is associated with the Result Set table


SQL> select * from EUL5_B070924102545Q1R1;

BRN1 BRVC1                BRVC2
20        RESEARCH       DALLAS
30        SALES                 CHICAGO


9. Information about when the table was created, the creator, last updated date and who updated it can be obtained from EUL5_BQ_TABLES;


EUL5_B070924102545Q1R1      SCOTT                              24-SEP-07




 Thanks – Shivmohan Purohit —



How to delete scheduled workbooks and results in Discoverer

hello dear friend,

Here is a very good piece on discoverer, how to know the results of schedule reports and insight into it

How to delete scheduled workbooks and results in Discoverer.


A scheduled workbook can be setup to run at a particular frequency, e.g. daily, weekly, etc., or it can be set to never repeat. When a workbook is scheduled the following database objects are created:


A view is created containing the select statement to create the result tables (e.g. EUL5_B011206161506Q1V1)


A table is created for each run with the results (e.g. EUL5_B011206161506Q1R1)


A package is created with the run information (e.g. EUL5_BATCH_PACKAGE011206161506 )


A job is created to call package at specified schedule intervals (e.g. EUL5_BATCH_PACKAGE011206161506.RUN)


All objects have the same unique sequence number in the name.  The R1 tables hold the results of a particular run of a scheduled workbook. A scheduled workbook can have a number of R1 tables, because a new table is created every time the scheduled workbook runs. If deleting the result sets for a scheduled workbook through the Discoverer Plus or Desktop then the R1 tables will be deleted from the database. If deleting the scheduled workbook from the Scheduling Manager then all the database objects will be deleted.


Shivmohan Purohit ———— share your feedback