Scheduled report issue

Question

Hi,
I scheduled a work book with multiple worksheets in discoverer 4.1.47. After scheduling when am I opening, I found there is a sheet with no data. I checked the query from SQL inspector and its not showing the original query and its showing the below query . I normally opened the worksheet from discoverer desktop and its showing the query correctly, where as in scheduled report SQL inspector is showing the below..
Remaing all sheets are scheduled correctly.
Please let me know, why
SELECT BRVC2 as E_300, BRVC1 as E_308, BRVC3 as E214082, BRN1 as E214083, BRN2 as E214094, BRN3 as E214095, BRVC4 as E214097, BRVC5 as E214098, BRN4 as E214099, BRVC6 as E214100, BRVC7 as E214101, BRVC8 as E214103, BRVC9 as E214106, BRVC10 as E214107, BRVC11 as E214109, BRN5 as E214110, BRVC12 as E214111, BRN6 as E214112, BRN7 as E214114, BRVC13 as E214115, BRVC14 as E214116, BRD1 as E214127, BRVC15 as E214130, BRVC16 as E214131, BRVC17 as E214144, BRVC18 as E214146, BRVC19 as E215360 FROM APPS.EUL4_B100714054016Q2R1;
BR
Uma

Answer 1

Hi Uma
In standard Discoverer, when you create and run a worksheet the results are created dynamically. This means that the data is only available within the session that is running the worksheet. More importantly, the data is NOT available to any other worksheet whether within that session or not. However, if you use a scheduled workbook then the results from the worksheet are held in a temporary table until you remove the results or you delete the scheduled workbook.
Tables look like this: EUL5_B060914015847Q1R1
Views look like this: EUL5_B060914015847Q1V1
Note: these temporary tables are stored within the schema of the user who owns the workbook - not within the standard EUL schema. The format of the table is as follows:
EUL5_B060914015847Q1R1 which can be broken into six separate pieces.
These pieces are as follows:
EUL5_ B YYMMDD HHMISS Q9 R9, where
EUL5_ is a fixed name
B means Batch and is a constant
YYMMDD is the date that the worksheet was run,
HHMISS is the time when the worksheet was run, the time is in the 24 hour clock format,
Q9 means this is the letter Q followed by a number - E.g. Q1, which signifies the query number. I believe Oracle have some plans to allow multiple queries but for now this is always Q1,
R9 means this is the letter R followed by a number - E.g. R1, R2 and so on. This is the run number.
Using the above logic therefore, here is your example: APPS.EUL4_B100714054016Q2R1
This means this is result set number 1 for query 2, run at 5:50:16 AM on 14th July 2010.
So if you can figure out which worksheet was scheduled and when it was run you can build a view that sits on top of the latest table to give you the latest results. Something else which adds interest here is that the column names within the table do not match the column names as in your original query. The scheduled results column names use generic names such as BRVC1, BRVC2, BRD1, BRD2, BRN1 and BRN2.
These are codes and can be interpreted as follows:
BRCV1 and BRCV2 mean Batch Result Varchar (aka string) 1 and 2,
BRD1 and BED2 mean Batch Result Date 1 and 2,
BRN1 and BEN2 mean Batch Result Number 1 and 2
In SQL, try this: SELECT * FROM APPS.EUL4_B100714054016Q2R1 - do you see anything? If yes, there is data in the result set. If no, this means Discoverer found no data when it ran the scheduled workbook.
If you have no data in the results you have to determine why. Perhaps you are pulling from a secure view using a specific responsibility that was needed get at the data? A responsibility that would be needed during the scheduled run.
Hopefully this helps
Best wishes
Michael