How to Configure and Trouble Shoot Notification for Process Control 2.5

Transcription

1 SAP SOLUTIONS FOR GOVERNANCE, RISK, AND COMPLIANCE How-To Guide How to Configure and Trouble Shoot Notification for Process Control 2.5 SAP GRC Regional Implementation Group Applicable Releases: SAP GRC Process Control 2.5 IT Practice / Topic Area: GRC GRC / Process Control IT Scenario / Capability: GRC / Process Control September 2008

2 Copyright 2008 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted 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, Informix, i5/os, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated 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 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, SAP NetWeaver, 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 their respective 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. Should you 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 SAP intentionally or grossly negligent. Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAP s Support Services and may not be modified or altered in any way.

3 Document History Document Version Description 1.20 Add in optional items information 1.10 Update to use the template 1.00 Document created

4 Typographic Conventions Icons Type Style Description Icon Description Example Text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Caution Note or Important Example Recommendation or Tip Cross-references to other documentation Example text Emphasized words or phrases in body text, graphic titles, and table titles Example text File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Example text User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation. <Example text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. EXAMPLE TEXT Keys on the keyboard, for example, F2 orenter.

5 Table of Contents 1. Business Scenario and Background Information Prerequisites Step-by-Step Procedure Configure SAPconnect Schedule Job for Sending User Account setup Trouble Shoot Q&A Comments and Feedback... 17

6 1. Business Scenario and Background Information SAP GRC Process Control is a solution for internal controls management that enables members of audit and internal controls teams to gain better visibility into key business processes and ensure a high level of reliability in financial statement reporting. When preconfigured for SAP GRC Process Control, SAP Workflow ensures that the right users get the right tasks in the right order at the right time. Workflow is delivered to user task lists within the application. In addition, workflow can be optionally routed through batched or individual s. In this documentation, we will discuss in details concerning how to configure the notification for the workflow. And how to trouble shoot for issues. 2. Prerequisites PC 2.5 has successfully installed and the workflow configuration has been done. Workflow items could be received from users Inbox from NWBC My Home work center.

7 Step-by-Step Procedure There are two major steps that need to perform for notification configuration from the IMG. First is to configure the SAPconnect. Second is to schedule job for sending s. 3.1 Configure SAPconnect In this IMG activity, you configure the communication interface SAPconnect to enable you to send external s from the SAP System. For more information about SAPconnect, see the documentation in the SAP Library for your SAP Web Application Server under Basis Services / Communication Interface (BC-SRV) -> Communication Interface (BC-SRV-COM) -> SAPconnect. 1. Log on to Process Control 2.5 system. 2. Go to the IMG by executing transaction code SPRO -> SAP Reference IMG. 3. Expand the node of GRC Process Control -> Workflow -> Notifications.

8 4. Execute Configuration SAPconnect. 5. Open Internet -> SMTP. Double-click on SMTP icon. The SAPconnect General node data dialog screen appears.

9 6. Check Mail Server settings. 7. Set the Node in Use indicator. 8. In the Supported Address Types pane, select Internet and click Set. The SAPconnect Address type for node dialog screen appears.

10 9. In the Address Area, enter an asterisk (*) and confirm all entries in the dialog boxes. 10. In the Jobs, ensure that the send job is scheduled for address type INT. If not, then create such a job. See 3.2 Schedule Job for Sending Select Settings -> Confirmation of Receipt from the menu.

11 It is highly recommended that you only send a receipt confirmation while you are testing the e- mail message function. You should then deactivate this option in the live system. 3.2 Schedule Job for Sending In this IMG activity, you schedule program GRPC_WF_NOTIFICATION. This program checks whether there are new work items for Process Control and determines the addresses of the work item recipients. This program is a Process Control-specific adjustment to program RSWUWFML2. SAP delivers a text as a proposal for the message. This text is stored in the Dialog Text GRPC_NOTIF_INBOX. With transaction SE61, you can create your own Dialog Text and store it as a variant for program GRPC_WF_NOTIFICATION. To schedule the program, proceed as follows: 1. Log on to Process Control 2.5 system. 2. Go to the IMG by executing transaction code SPRO -> SAP Reference IMG. Expand the node of GRC Process Control -> Workflow -> Notifications. Execute Schedule Job for Sending .

12 3. Specify a job name and choose Start Condition. 4. Choose Date/Time, specify a start date, and set the Schedule Job Periodically indicator.

13 5. Under Period Values, select a value, and confirm all entries. 6. Choose Step.

14 7. Under User, enter WF-BATCH or the relevant service user for your workflow system.

15 8. Choose ABAP Program. 9. Under Name, enter program GRPC_WF_NOTIFICATION. 10. Under Variant, enter SAP&PC_NOTIF or your own variant. 11. Enter the language in which the message is to be sent. 12. Save your entries.

16 User Account setup Make sure WF-BATCH and the users need to receive notification have proper accounts configured. 1. Log on to Process Control 2.5 system. 2. Go to transaction SU Enter WF-BATCH for the user and click on display.

17 Make sure that the address has been maintained correctly. 5. All notification will be sending out from the account of WF-BATCH. 6. Repeat the checking steps for other business users such as Internal Control manager, Process Owner, Subprocess Owner, Control Owner, Organization Owner, testers, etc 3.4 Trouble Shoot Where should we start to check if notification does not arrive. 1. Check if the workflow item has arrived in user s Inbox. If it is not, then it might not be notification issue. 2. Double check the configuration stated in section 3.1 to Check Inbox Overview. From the SAPconnect: Administration (system status) page, drop down Utilities (M) menu -> Inbox Overview. Or access transaction SCOT.

18

19 4. Check overview of send orders. Or execute transaction SOST.

20 On Send status tab, check Transmitted. Hit Execute. And check if there is error status. 3.5 Q&A 1. notification has been sent out by the user account other than the WF-BATCH. [Feedback] Please check the scheduling job of GRPC_WF_NOTIFICATION. Make sure that WF-BATCH is entered as the service user for your workflow system. If notification has been sent out by WF-BATCH user account plus other user account, the system might have more than one scheduling jobs for notification. And the server user entered for the jobs are different. Thus, cause the in consistency. 2. Do we only support SMTP for notification? [Feedback] Process Control uses the SAPconnect from NetWeaver. SAPconnect provides a standard interface for external communication, which supports sending using telecommunication services, such as FAX, text messages (pager/sms), Internet mail and X.400, as well as sending to printers and between different SAP Systems. It enables external communication components to be connected to the SAP System. For detail information, please check on the following link: BD925BF4B8A11D1894C0000E8323C4F&&TMP_IWB_TASK=DISPLAY&RELEASE=6763&LANGUA GE=EN 3. Is the notification format type txt only? How about html and rich text? [Feedback] The notification format sending out from Outlook is determined by the setting of the sender account, which is the WF-BATCH user account. If this account is configured to send out in html format, all will be sending out using this format. 4. How could the customer edit the notification to fit their need? [Feedback] Please refer to the Process Control 2.5_How to edit the content of notification documentation.

21 5. If customer has one system with more than one PC clients, should customer configure the notification on every single client? Can it be shared? [Feedback] No, the configuration could not be shared. It has to be configured on every single client.

22 4. Comments and Feedback Both comments and feedback are very welcome. Please send them to: Jennifer Cha RIG Process Control Raj Behera RIG Manager