Skip to Content

BO attempts to retrieve From value on report scheduling

Oct 24, 2017 at 03:27 PM


avatar image
Former Member


we are working on SAP BusinessObjects 4.1 SP7.

We want to configure the mail services using the %SI_EMAIL_ADDRESS% placeholder.

We know by the "Business Intelligence Platform Administrator Guide", Document Version: 4.1 Support Package 7 – 2015-11-24, at page 596 that the actual policy is:

"Enables or disables the From field when scheduling an object to a destination. Default: SMTPFrom=true

When the value is set to false the From field will not be displayed and the system attempts to retrieve the From email value in the following order:

1.First, from the report default for a report object.

2.Second, from the email address on the user profile of the logged on user.

3.Lastly, from the Job server default."

We point out that all our BO enterprise users have own email configured.

To prevent the BO user email from appearing in the sender field when scheduling an istance of report, for Firewall Policy, we ask you if is possible to change the priority order.

We would like the following policy:

1.First, from the Job server default.

2.Second, from the report default for a report object.

3.Lastly, from the email address on the user profile of the logged on user."

Is it possible? How could we achive this?

Thank you for you reply,

Best Regards.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Venkateswara Y Guptha
Oct 25, 2017 at 12:30 PM


This is an enhancement / change request, and I recommend you to enter this in the following customer influence section of

SAP BusinessObjects BI Platform. And there, this will be reviewed and will be answered whether the change requested can be implemented or not.

And as a quick fix, I can suggest the following workaround, please use, if it is feasible to you.

  • We can have dummy user created in BI system, with the email-id configured as same as what is configured at the job server level.
  • And use the "Schedule For" option and select eh dummy user created in the above step, and then schedule the document with destination as email with default options selected.

In this way, we can prevent the email id of the user getting exposed.

Note: In this workaround, little catch is that, all the schedules created by multiple users using the schedule for option with dummy user, will be created as that of dummy user. As schedule for option makes the user selected in that as the owner of the schedule.



10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Oct 30, 2017 at 10:41 AM

Hi Venkat,

thanks for you reply.

We have try your work around, but the customer does not want to give the CMC access to their BO users.

We have entered the change request on the customer influence section, as you suggested.

Thanks and Best Regards.

Show 1 Share
10 |10000 characters needed characters left characters exceeded

But in the workaround I proposed, I do not think, we need to give the access of CMC to BO users. Some BO administrator can create a minimum required dummy users for their users and distribute those newly created dummy users to their users, who does the scheduling.