Send Error Messages to the Monitor in Update and Transfer Rules

  • by Gary Nolan, SAP BI Strategic Architect, Sapiex Associates LLC
  • July 1, 2005
Messaging functionality in SAP BW allows you to provide clear error messages to the monitor about why a data load failed. This helps with troubleshooting, making for a more efficient batch processing window as the BW administrator can more quickly identify and fix errors.
Key Concept
Data loads into SAP BW sometimes require advanced filtering or validation of data at the time of data load. This filtering and validation usually occur in the update or transfer rules. You can accomplish further filtering via start routines in the update or transfer rules.

BW data requirements sometimes make it necessary to abort or fail a data load if certain validations are not met. The failed packages are set to red to indicate the failed load. For example, say you expect to get flat files of data from an external source to feed a BW InfoCube. It should only contain data for division 10. If any other division appears in the flat file, you want to fail the load and set it to red to indicate an error with the source data.

You can set up a check in either the update rules or the transfer rules to validate the division field. If any other division shows, you would set the ABORT flag and fail the data load. The monitor would show a red light for this data load, and the data would not be loaded into the InfoCube.

Troubleshooting failed data loads can be difficult without communication of the failed load to the load monitor. In the example above, it would be helpful to know that an unexpected division came through on the flat file. I will explain how to send such messages so the results of validation in transfer or update rules are shown and communicated to the monitor.

Whoever monitors batches can then be given specific instructions on how to deal with each of the error messages that may appear in the monitor. This cuts down significantly on the time to troubleshoot because they do not have to research the actual data to determine why a specific package failed during batch processing. It is a good idea to use this messaging whenever you plan to abort a data package. I have used this technique multiple times and have found that it provides a very good method of communicating messages to the monitor.

You can send messages to the monitor in update rules, transfer rules, or start routines. The coding technique is a bit different for each. In my coding examples, I will use very simple filter criteria, filtering data loads to include only division 10. You can alter this code to your specific filtering and messaging criteria. My goal here is not to show how to filter, but how to communicate the results of a filtered record to the monitor.

Gary Nolan

Gary Nolan is an SAP NetWeaver BW-certified consultant and author of Efficient SAP NetWeaver BW Implementation and Upgrade Guide and Efficient SAP NetWeaver BI Implementation and Project Management. Gary specializes in gathering and evaluating requirements, configuring SAP NetWeaver BW, and providing project management, performance management, and data architecture and data modeling expertise. A former platinum consultant with SAP America, Inc., Gary has more than 20 years of SAP experience, working with SAP NetWeaver BW since version 1.2B.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.