Enabling Broadcast Features and Root cause Analysis for Broadcasts Failure in SAP C4C

[sudarshanmc]

Hey All,

I am writing this blog to serve as central information on how to make use of Broadcast Bursting and User Specific features while creating Broadcasts for Reports or Dashboards and the Root cause analysis for Broadcast Failure. Here you will find the steps to achieve in your system and get to know about how they work technically.

Introduction

• I hope you are aware that we can create broadcasts for Reports and Dashboards.
• Defining the recipients who are going to receive the broadcasts is important, and it is mandatory while creating the broadcasts.
• There are two ways available to determine the recipients. 
  
  • Broadcast Bursting.
  • User Specific.

First, let us see the broadcast bursting feature. 

• Bursting feature allows you to broadcast reports to multiple recipients by e-mail.

Prerequisite

•  We have to maintain the addresses of the recipients in the master data, so that we can select a characteristic in which the e-mail addresses are maintained. The system can determine the recipients from this information.

Getting Started

• As you can see from the below screenshot, I have created new Report (UserEmployeeLogon) and I have added E-Mail standalone field, and it shows the E- mail address.

Fig 1. Report View

• let's create the new Broadcast for this report as shown below.

Fig 2. Broadcast Creation

• Select the checkbox Use Broadcast Bursting, the section to add e-mail addresses of the recipients is hidden.
• For the new field Attribute for Email, select a characteristic, in which you have maintained the email address. Now, the report will be automatically sent to all the relevant recipients, without you having to add each individual e-mail addresses separately.
• Unlike a normal broadcast, entire data is not sent to all recipients. The report data is filtered for each recipient based on their e-mail addresses, which is identified by the values of the attribute you select. This ensures that every recipient only receives the data filtered for their e-mail address.Fig 3. Adding the field attributeFig 4. Broadcast Creation Details
• Click on Save and CloseFig 5. Broadcast List screen
• Click on Start Now button as shown below to start the broadcast.
• You can see the status under the Last Run column (yellow indicates broadcast is in progress and green indicates successful run).Fig 6. Start Broadcast
• Fig 7. Broadcast Runs Status
• Broadcast email sent to user as shown below.Fig 8. Broadcast E-mail received

Now let's see the Broadcasting by User Specific Data.

• We can decide if the recipients are to receive data according to their authorizations. To do this, select the User specific checkbox.
• This field is visible only when the object type is a report, and the recipient is a Business User in the system.Fig 9. User Specific Feature
• Broadcast email sent to user as shown below.
• Fig 10. Broadcast E-mail recieved
• Note that when the checkbox is unselected, the data is broadcast using the authorizations of the user who creates the broadcast. Ensure that the user has access rights to the work center views to which the report is assigned in order to start the report.

Note: - If you use the broadcast bursting feature, the system cannot check if the recipients have a valid user. For this reason, it is not possible to use the User specific and the broadcast bursting feature together - please either use the broadcast bursting or make the broadcast user specific (after selecting users as recipients).

Now let us see the Root cause analysis for Broadcasts failures.

1. If the creator of the broadcasts is locked or inactive, then the broadcast will not run, so make sure that the creator of the broadcast is active and unlocked or create a new broadcast.
2. The creator of the broadcast must have access to the report involved and also make sure that the user can see the report in the analysis work center.
3. The user who created broadcast doesn't have access to the Workcenter view that the report is assigned to so check into the Access Rights of the user who created Broadcast and see if they have access to the Workcenter view that the report (Broadcasted) is assigned to.
4. Multiple broadcasts scheduled at the same time: Check how many broadcasts scheduled at the same time in background jobs (it's advised not to schedule multiple broadcasts at the same time).

If the broadcast is still failing not due to any of the reasons mentioned above, then kindly create the incident with SAP.

Kindly note that all these information gathered from SAP Help documentations/KBA's.

Conclusion: - With this note, I’d like to conclude my blogpost on Enabling Broadcast Features and Root cause Analysis for Broadcasts Failure in SAP C4C.

I hope the information provided in this blog post was useful to you. In case if you are looking for more details on this topic you can find it on SAP documentation https://help.sap.com/docs/sap-cloud-for-customer/sap-cloud-for-customer-analytics-guide/broadcasts . Please feel free to provide your feedback or ask question in the comments section and I’ll be glad to respond to you. Happy Learning!

Regards,
Sudarshan