Refresh Dynamic Recipient's Report

I have a report which has been scheduled through publication. That publication has dynamic recipient report. And this report need to be refreshed every time before publication go out.

Any idea how can I refresh dynamic report automatically?

Thanks in advance
Viral Kapadia


vkapadia (BOB member since 2012-10-15)

Schedule the dynamic recipient report prior to the Publication.

You can create an Event which the successful scheduling of the dynamic recipient report will trigger, and set your publication to await this event (and remember to schedule the publication for a time prior to the dynamic recipient report scheduling so that the publication is waiting for the event to trigger it).

Take a look at the admin guide for how to create and use schedule based events - see chapter 23 “Managing Events” in this guide:
http://help.sap.com/businessobject/product_guides/boexir31SP3/en/xi31_sp3_bip_admin_en.pdf

Reply if you get stuck.

HTH

NMG


mcnelson :uk: (BOB member since 2008-10-09)

Hello,

I read chapter 23 on admin user guide. It was interesting to know about this event part.

I still have some doubt though. How can I link the event which I have created and dynamic recipient’s report? I do understand that while scheduling publication I can trigger that event to run. But how can an event know that it has been created for refreshing report data?

It will be very cleared if you can provide me in detail explanation with example. Thanks for all your help…

Viral Kapadia


vkapadia (BOB member since 2012-10-15)

When you schedule your dynamic recipient report, there is an option under the Events tab for “Events to trigger on completion”. This is where you note the schedule based event you create via the CMC.

Then when you schedule your publication, you enter the same event into the “Events to wait for” option.

So, when you schedule your Dynamic Recipient report, upon completion it triggers your schedule based event. Your publication is awaiting the schedule based event, and runs when it is detected.

Thus, the publication will only run when the Dynamic Recipient report is refreshed (and the schedule based event is triggered).

HTH

NMG


mcnelson :uk: (BOB member since 2008-10-09)

I got it and I am done with it. I have scheduled my report and publication with event. I will keep you posted if any problem occurs once a publication go out.

Thanks a ton for all your help!!!

Viral Kapadia


vkapadia (BOB member since 2012-10-15)

My experience using v3.1 Sp7…

There is no need or point to schedule the dynamic recipient report. The Publication refers to the ‘master’ dynamic recipient report, not a scheduled instance.

The Publication automatically refreshes the dynamic recipient report even if it is not set to ‘refresh on open’. However, this does not work if there is a prompt in the dynamic recipient report, and this is giving me a real problem! :hb:

Has this issue been rectified in v4?


anorak :uk: (BOB member since 2002-09-13)

Tested and confirmed with SP7 :slight_smile:

Not sure about your prompt issue though; have you specified a default value and it still fails, or is it an optional prompt?

NMG


mcnelson :uk: (BOB member since 2008-10-09)

The prompt is not optional, and it makes no difference is you have a default value.
Interestingly, I have discovered that you do not need to have a separate report to provide the list of dynamic recipients. You can extract them from the source report itself, as long as they are generated from a separate query. :lol:


anorak :uk: (BOB member since 2002-09-13)

Unfortunately my joy was short-lived :frowning: This solution does not seem to work 100% of the time, so I have had to revert to having a separate report to supply the dynamic recipient details.


anorak :uk: (BOB member since 2002-09-13)

I use this method for just about every publication and it seems to work fine -or should I say I’ve had no complaints… could it be something to do with the order in which your queries are run? We’re on v4.1 SP6


peacha :uk: (BOB member since 2008-07-31)

I’m sure that I tried forcing the recipient query to run first, and still had the problem on occasions. But we were using v3.1 SP7.

Unfortunately, I can’t carry on testing as my contract expired.


anorak :uk: (BOB member since 2002-09-13)