Event based Scheduling issue

[Former Member]

Hi All,

we have a requirement to run reports after the data loads to the warehouse are completed.

I use scheduled reports with file base event. After the load is completed i place a textfile on the BO-Server. The event is triggered once the textfile is placed. This runs ok.

But this is a poor solution, because i have to schedule the report before and i dont know on which time the data loads are done.

Of course i can schedule the reports every day but this is a overload. For a example if i schedule a report based on a event, every day this will generates a intance for everyday to wait for the event. Assuming that the event happens anytime monthly it can hold up to 30 intances for the the same report. And all this inctances will run when the event happens.

Is there any way  to plan the same file based schedeule when the schedule before runs successful?

Or is there any alternative way to run reports only on events without scheduling?

Best regards

Ömer Yazici

[Former Member]

When using event based scheduling, reports aren't like buses

Oemer Yazici wrote:

Of course i can schedule the reports every day but this is a overload. For a example if i schedule a report based on a event, every day this will generates a intance for everyday to wait for the event. Assuming that the event happens anytime monthly it can hold up to 30 intances for the the same report. And all this inctances will run when the event happens.

You're misunderstanding this; if the report is scheduled and that time passes without the event being triggered, the report will wait until the event is triggered (depending upon your scheduling settings). If this happens a week later, only one report will run - not 7. Instances are created by the event triggering the schedule - they don't accumulate and all run at once when the event is triggered.

In your example, if you schedule your report on a monthly basis and have it await a file based event, when the event is triggered the report will run; no instances are created for all of the days prior to the event occurring.

HTH

NMG

[Former Member]

Hello,

thank you for your help.

i think i have not explain my situation clear. I know the concept of the event based scheduling you have decribe i your reply

I want that the reports will run (be triggered by the event) every time, when the datawarehouse loads are done.

I dont want to schedule the report manual again after the schedule before is run.

I can not plan a monthly schedule, because i dont know the interval of data loads.

Best regards

Ömer

[Former Member]

Surely you just need to accommodate the smallest period that a data warehouse load can occur in? So if your event can be triggered daily, schedule on a daily basis?

Per the (XI3.1) Admin Guide:

When you schedule an object that waits for a specified event, the object will

run only when the event is triggered, and only when the rest of the schedule

conditions are met. If the event is triggered before the start date of the object,

the object will not run. If you have specified an end date for this object, and

if the event is not triggered before the end date occurs, the object will not

run because not all of the conditions will have been met. Also, if you choose

a weekly, monthly, or calendar schedule, the object will have a specified time

frame in which it can be processed. The event must be triggered within this

specified time for the object to run. For example, if you schedule a weekly

report object that runs every Tuesday, the event must be triggered before

the end date of the instance (the end of Monday, in this example).

My datawarehouse refreshes on an hourly basis, and triggers a file based event which kicks off my scheduled reports - these are scheduled to run every hour for 24 hours. If an event doesn't occur, the reports don't refresh. When the event occurs again, the reports recur - but only one will run (initially) as all of the others that would have occurred in the interim period have expired; essentially the schedule just resumes, it doesn't "pick up" where it left - which seems to be your concern.

NMG