Exception Broadcasting

8/4/2019 Exception Broadcasting

1/11

How-to GuideHow-to Guide

SAP NetWeaver 2004sSAP NetWeaver 2004s

How To

How ToDo ExceptionBroadcasting

Version 1.00 October 2006

Applicable Releases:SAP NetWeaver 2004s


2/11

Copyright 2006 SAP AG. All rights reserved.

No part of this publication may be reproduced ortransmitted in any form or for any purpose without the

express permission of SAP AG. The information

contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its

distributors contain proprietary software components of

other software vendors.

Microsoft, Windows, Outlook,and PowerPoint

are

registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel

Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400,

iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent

Miner, WebSphere, Netfinity, Tivoli, and Informix are

trademarks or registered trademarks of IBM Corporation

in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered

trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame,

WinFrame, VideoFrame, and MultiWinare trademarks

or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or

registered trademarks of W3C, World Wide Web

Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems,Inc., used under license for technology invented and

implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other

SAP products and services mentioned herein as well as

their respective logos are trademarks or registered

trademarks of SAP AG in Germany and in several other

countries all over the world. All other product and

service names mentioned are the trademarks of theirrespective companies. Data

contained in this document serves informational

purposes only. National product specifications may vary.

These materials are subject to change without notice.

These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes

only, without representation or warranty of any

kind, and SAP Group shall not be liable for errors or

omissions with respect to the materials. The only

warranties for SAP Group products and services are those

that are set forth in the express warranty statements

accompanying such products and services, if any.

Nothing herein should be construed as constituting an

additional warranty.

These materials are provided as is without a warranty

of any kind, either express or implied, including but not

limited to, the implied warranties of merchantability,

fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind including

without limitation direct, special, indirect, or

consequential damages that may result from the use of

these materials.

SAP does not warrant the accuracy or completeness of

the information, text, graphics, links or other items

contained within these materials. SAP has no control

over the information that you may access through the

use of hot links contained in these materials and does not

endorse your use of third party web pages nor provide

any warranty whatsoever relating to third party web

pages.

SAP NetWeaver How-to Guides are intended to

simplify the product implementation. While specific

product features and procedures typically are explained

in a practical business context, it is not implied that those

features and procedures are the only approach in solving

a specific business problem using SAP NetWeaver. Shouldyou wish to receive additional information, clarification

or support, please refer to SAP Consulting.

Any software coding and/or code lines / strings (Code)

included in this documentation are only examples and

are not intended to be used in a productive system

environment. The Code is only intended better explain

and visualize the syntax and phrasing rules of certain

coding. SAP does not warrant the correctness and

completeness of the Code given herein, and SAP shall

not be liable for errors or damages caused by the usage of

the Code, except if such damages were caused by SAPintentionally or grossly negligent.


3/11

1 Scenario

You want to search BI queries for exceptions that have occurred and distribute these

exceptions to the end users by Email or via the central alert framework. This functionalityis called Exception Broadcasting. If you use the central alert framework, the exceptionswill be displayed in the Universal Work list in the Enterprise Portal.

2 Introduction

The solution presented here is based on SAP NetWeaver 2004s. The query that will beused must have at least one exception. Once you defined and executed (directly or inscheduled in the backend) an Information broadcasting setting of type Distributeaccording to exceptions, the BEx Broadcaster checks, if the thresholds defined in thequery exception have been exceeded or not reached. In that case the BEx Broadcasterimmediately generates a document in accordance with the criteria defined by you anddistributes this to the recipients by email, to the portal, or as an alert.

- 1 -


4/11

3 The Step By Step Solution

1.

2.

As the first step you have to start theQuery Designer and open the Querythat should be checked forexceptions.

Then you have to create theexceptions for the query. In theexample we created 3 different alertlevels (Good 1, Critical 2, Bad 3)based on the key figure sales.

- 2 -


5/11

3. If you want to use the central alertframework you have to go to yourbackend system and call thetransaction ALRTCATDEF. Thereyou have to create a new alert

category. First you have to enter adescription and to maintain the basicproperties for the alert category.

4.

5.

In the next step you have to createcontainer elements for BIparameters that you want to transfervia Information Broadcasting. Go tothe tab and press the icon Create.

For each container element that youwant to map to a BI parameter youhave to define a description and theobject type. You can choose thesetting not defined as object type.

- 3 -


6/11

6. In the next step you have to providea text for the alert message. Thismessage will be displayed in anEmail or in the Universal Worklist.You can use variables in the

message text that you have createdas container element before. Youcan include those variables in thefollowing way: &dist_channel&

7. Then you can enter a text and aURL for a subsequent activity(optionally). E.g. you can add a linkto a BI Query which should bechecked by the recipient in order to

react to the alert.

- 4 -


7/11

8.

9.

10.

In the last step of the alert categoryconfiguration you have to assign thealert to the end users. You can enterfixed recipients or roles. If you entera role, all users that are assigned to

that role will get the alert. You canalso enter roles, if you press thebutton Subscription Authorization.In that case the assigned users willhave the option to subscribe for thealert later.

In the next step you have to call theBEx Broadcaster and create anInformation broadcasting settingbased on the query, on which theexception has been defined on. Asdistribution type you have to chooseDistribute according to exceptions.In the details you can either choosethe distribution type Send Email or

Create Alert, if you want todistribute the alert via the UniversalWorklist. As selection criterion youcan either choose to distribute allexceptions or you can choose aspecific alert level. In our examplewe only want to distribute alerts,which have the level Bad 3.

Then you have to assign thecorresponding alert category youhave created before to yourInformation broadcasting setting.

- 5 -


8/11

11. In the next step you have to do themapping between the BI parametersof the Query and the alert containerelements. These parameters willthen be passed over to the alert.

12.

13.

In the last step you have to save theInformation Broadcasting setting.You can execute the setting directlyor you can schedule the executione.g. periodically each week.

If you execute the InformationBroadcasting setting directly, you willget an information, whether thesetting has been executedsuccessfully or not. In our example 2Alerts have been triggered.

- 6 -


9/11

As a result you will see 2 new alertsin the Universal Worklist for all userswhich have been assigned to thealert corresponding alert category.You can access the Universal

Worklist in the Enterprise Portal:Business IntelligenceBusinessExplorer Universal Worklist.

14.

- 7 -


10/11

4 Appendix

The following picture gives you an overview about the integration of Information

Broadcasting and the central alert framework:

You can find more information how to configure the Universal Worklist in the onlinedocumentation. Further information regarding Information Broadcasting can be foundhere.

- 8 -
http://help.sap.com/saphelp_nw2004s/helpdata/de/39/a1bb5c4c0d4ab4a417e87ef35f1efa/frameset.htmhttp://help.sap.com/saphelp_nw2004s/helpdata/de/39/a1bb5c4c0d4ab4a417e87ef35f1efa/frameset.htmhttp://help.sap.com/saphelp_nw2004s/helpdata/en/a5/359840dfa5a160e10000000a1550b0/frameset.htmhttp://help.sap.com/saphelp_nw2004s/helpdata/en/a5/359840dfa5a160e10000000a1550b0/frameset.htmhttp://help.sap.com/saphelp_nw2004s/helpdata/de/39/a1bb5c4c0d4ab4a417e87ef35f1efa/frameset.htmhttp://help.sap.com/saphelp_nw2004s/helpdata/de/39/a1bb5c4c0d4ab4a417e87ef35f1efa/frameset.htm


11/11

http://service.sap.com/nw2004s-howtoguides
http://service.sap.com/nw2004s-howtoguideshttp://service.sap.com/nw2004s-howtoguides

Exception Broadcasting

Documents

Transcript of Exception Broadcasting