7/31/2019 Creating Custom Alerts http://slidepdf.com/reader/full/creating-custom-alerts 1/17 1 Creating Custom Alerts and Adding Them to the Alert Monitor in SAP SNC SNC Extension Guide 1 ALERT CREATION SCENARIO ......................................................................... 2 2 DETAILED STEPS ON HOW TO CREATE THE NEW ALERT .......................... 2 2.1 Step 1: Create Alert Structure for New Alert ....................................................................................... 2 2.2 Step 2: Create Alert Object Type .......................................................................................................... 6 2.3 Step 3: Create New Alert Type .............................................................................................................. 6 2.4 Step 4: Create Alert Category and Alert Type Assignment .................................................................. 8 2.5 Step 5: Activate the Alert Type Database Tables................................................................................ 11 2.6 Step 6: Activate the New Alert in SAP SNC Customizing .................................................................. 12 2.7 Testing the New Alert .......................................................................................................................... 14 Ve rs ion: 2 .0 Date 15.12.2009
2 DETAILED STEPS ON HOW TO CREATE THE NEW ALERT .......................... 2
2.1 Step 1: Create Alert Structure for New Alert ....................................................................................... 2
2.2 Step 2: Create Alert Object Type .......................................................................................................... 6
2.3 Step 3: Create New Alert Type .............................................................................................................. 6
2.4 Step 4: Create Alert Category and Alert Type Assignment .................................................................. 8
2.5 Step 5: Activate the Alert Type Database Tables ................................................................................ 11
2.6 Step 6: Activate the New Alert in SAP SNC Customizing .................................................................. 12
2.7 Testing the New Alert .......................................................................................................................... 14
The SNC Extension Guide is a collection of tips and tricks on how to extend SAP Supply Network Collaboration to meet your specific business requirements. It is based on SNC 7.0. Consultants,Developers and Solution Managers have worked together to build this content based on customer experiences. We invite you to actively participate in the content - share your experiences, comments and questions.
Disclaimer: SAP is not liable for any discrepancies in the content or code in the documents.
1 Alert Creation Scenario
Often customers need specific alerts that are not provided in the standard SAP SNC delivery. Thepurpose of this document is to provide you with an example of how to create a custom alert and add itto the SAP SNC Alert Monitor.
In the standard system, when the supplier creates a note to communicate purchase order relatedinformation to a buyer, the standard alert 7059 - New note for order is created. Both supplier andbuyer see this new note alert and there is no way to distinguish between a supplier-created note and abuyer-created note.
In this document we will provide step-by-step instructions on how you can create a custom alert typethat will be triggered when a supplier creates a new purchase order note. This new alert type will be9991 and called Supplier Generated Notes .
2 Detailed Steps on How to Create the New Alert
2.1 Step 1: Create Alert Structure for New Alert
The first step is to create an alert structure for the alert. An alert structure is the set of parameters for aparticular alert type.
Click Copy All . This would copy all the parameters associated with the structure. In this case since weare making the copy of structure 51, all parameters associated with structure 51 will be copied to thecustom alert structure 9991.
Click Save . You should be able to see your new Alert structure
The second step is to create an alert object type.
The alert object type is used in the Alert Engine (SAP SNC alert management is based on this) andhas to be maintained only due to historical reasons.
Click on the New Entries button.
Enter the values as specified below.
Click Save .
2.3 Step 3: Create New Alert Type
The third step is to create the new alert type.
An alert type is a type of exceptional situation (such as a problematic planning situation) about whichthe system can notify you through alerts. An alert is a problem message that notifies you about aconcrete exceptional situation that has occurred, for example, for a particular location product or anorder document in a particular process.
Click Alert Type . Click on the New Entries button.Enter values as provided in the screenshot below.
2.4 Step 4: Create Alert Category and Alert Type Assignment
The fourth step is to create an alert category and assign your new alert type to it.
An alert category is a means of grouping the alert types for the SAP SNC Alert Monitor. It controls on
which Alert Monitor tabpage alert types are displayed.
Create Alert Category and Alert Type Assignment.
Enter T-code /SCF/ALERTCATCFG
Click on Alert Category Description to create new alert categories. Since the example is for alertsrelated to purchase orders, we will not require this step.
Please note that the parameters of the alert structure must be a subset of the alert category parameters New Alerts created must ensure that the parameters of the alert type are available in the alert category parameters before we assign the alert type to the category.
If alert history is not necessary for the new alert type, do not check the alert history flag on the corresponding transactions (Tx /SCMB/ALENCFG and Active Alert Types in Customizing). Switching off the unnecessary history handling will improve the performance significantly in case of mass alert processing.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission ofSAP 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 softwarevendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9,z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 ParallelEnterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower,PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2,Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registeredtrademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated 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 MultiWin are trademarks or registeredtrademarks 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 byNetscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and othercountries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence,Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarksor registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAPcompany.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in thisdocument 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 beliable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are thosethat are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein shouldbe construed as constituting an additional warranty.
