Information Broadcasting as Background Processing

When BW objects are precalculated and distributed using background processing, BEx Web applications are executed, and the generated HTML documents are stored in the Knowledge Management folder or distributed by e-mail.

Broadcast settings are made in the background

• if they were registered for execution at a specific time
• if they were registered for execution when data was changed, and the data change event was triggered from a process chain
• if they were scheduled directly in background processing

A scheduling user has registered or scheduled broadcast settings for another user.

This is the case if:

• the authorized user in the broadcast setting is not the scheduling user
• the broadcast setting requires user-specific execution for users other than the scheduling user

For security reasons, the system runs a check during processing to ensure that the scheduling user is authorized to schedule background tasks for the other user(s) (authorization object S_BTCH_NAM).

A job can be executed in the background under various user names, which means the HTML documents are generated according to user-specific authorizations.

Storage in a Knowledge Management folder is triggered using an RFC call from ABAP to Java. Authentication is performed by automatically generating SAP logon tickets. Automatic generation is defined in the RFC destination. The corresponding user must have write authorization for the selected Knowledge Management folder.

When using distribution by e-mail and precalculation of BEx workbooks with Microsoft Excel, no portal functions are required.

Overview

More information: Broadcasting BEx Objects.