SAP NetWeaver How-To Guide How to use Process Execution Manager Using SAP Test Data Migration Server

Transcription

1 SAP NetWeaver How-To Guide How to use Process Execution Manager Using SAP Test Data Migration Server Applicable Releases: SAP Test Data Migration Server 4.0 SP03 Version 1.0 October 2012

2 Copyright 2012 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.00 First official release of this guide

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

5 Table of Contents 1. Business Scenario Background Information Preconditions: PEM (Process Execution Manager) PEM Plan calculation PEM Plan Recalculation PEM Plan Manual Settings Split/Merge Set Optional Activity as Active... 11

6 List of Figures Figure 1: PEM Plan View... 2 Figure 2: PEM Dialog Block... 3 Figure 3: View all Activities of a Dialog Block... 3 Figure 4: Scheduling Process Execution... 4 Figure 5: Information Dialog Box... 4 Figure 6: View the Stop Execution Pushbutton... 5 Figure 7: Check the status of the Blocks... 5 Figure 8: PEM Configuration View... 6 Figure 9: Activities of Package Settings 02 Block... 6 Figure 10: Status and Activity Completion Percentage of PEM Plan View Dialog Block... 7 Figure 11: View of a Terminated Activity... 7 Figure 12: Status of the Terminated Activity... 8 Figure 13: View Merge Blocks and Split Blocks Pushbutton... 9 Figure 14: Choose the Row for Split Block... 9 Figure 15: Select Activities to be moved to the New Block Figure 16: Choose Add Pushbutton to move the Activities to the New Block Figure 17: View Activities moved in the New Block Figure 18: New Blocks Data Transfer 09-1 and 09-2 are Created Figure 19: View the Opt. and Act. Activities Figure 20: Select the Opt. Activity as Act. Activity Figure 21: Select Two Activities to be Merged Figure 22: Choose Yes to Merge the Activity Figure 23: Blocks Data Transfer are Merged... 13

7 1. Business Scenario SAP TDMS run requires constant monitoring and manual intervention. The Process Execution Manager (PEM) is a funtionaility of SAP TDMS that minimises the overall manual intervention needed to execute a TDMS run. The PEM consist of a Plan, Groups, and Blocks. The PEM Plan represents the process tree with focus on executable activities. Non executable activities will not be considered for the PEM Plan calculation. SAP TDMS offers a default PEM plan for every migration solution based on the sequence and interrelationships of activitiies. The TDMS process structure helps you execute specific activities in a TDMS migration package and track the activity status. 2. Background Information The Process Execution Manager (PEM) helps you to carry out an optimal execution of SAP TDMS with minimal user interaction. 3. Preconditions: You have carried out the following activities: Created a project Assigned a system landscape Loaded a migration package Switched to the Process Execution Manager tab page. 3.1 The Process Execution Manager (PEM) The PEM creates a processing plan based on the process tree, the process phases, and the process activities. The processing plan aims at an optimal level of processing with minimal user interaction, while taking into consideration the interrelationships between activities. You can view the plan calculations in the Plan view. The process tree is divided into groups and blocks. Groups contain blocks and blocks contain activities. All groups belong to a Plan. One or more groups correspond to a phase (known from the process tree/process structure). A block can be dialog or batch. A batch block is performed without user interaction. Dialog blocks require user interaction if they are not optional. In the following pages, we demonstrate the processing of a solution/package serving as a model to show what you have to do to process the PEM and what user interaction is expected from you. You are in the process tree of your package. After calling the Package overview, the Process Structure tab page appears. Switch to the Process Execution Manager tab page. When you access the tab page for the first time, the PEM plan is created. In the screenshot below, you see the Plan view. You can change to another view, the Configuration View, which is described in detail later. October

8 Figure 1: PEM Plan View Check if there are dialog activities to be executed by looking for the Execute Dialog Block pushbutton. If there are no dialog activities to be executed, the pushbutton does not appear. Choose the pushbutton. A window appears with the dialog blocks you have to process. Click the dialog block (underlined text) you want to process. October

9 Figure 2: PEM Dialog Block A new window appears where you can see all activities belonging to the dialog block. Figure 3: View all Activities of a Dialog Block You are not required to execute optional activities. An activity is executable if it is selected under the column Act. Execute the dialog block. To begin the execution, you need to provide the inputs using dialog blocks. The Execute Dialog Block pushbutton display all activities requiring input from users. October

10 After you process all the required dialog activities, the Execute Dialog Blocks pushbutton is not visible until new required dialog activities are available for processing. Scheduling Execution You can set parameters for the plan and the blocks. With these parameters you can define start and re-start options. You can organize when the Plan should be executed. With the re-start options you can determine that restart does not happen after failures. You can also determine how many times after failures should the restart be possible. The value 0 indicates that there are no restrictions in the number of executions and the activity can restart infinite times in case of failure in execution. Figure 4: Scheduling Process Execution Start the plan execution by choosing the Start Execution pushbutton. An information box appears with information that the execution has started. Confirm this message by choosing OK. Figure 5: Information Dialog Box Execution is controled by the batch job CNV_MBT_RUN_PLAN_<your_package_id> in the control system. The Start Execution pushbutton is no longer visible. Instead, you can view the Stop Execution October

11 pushbutton. You can choose this pushbutton to stop the execution of new activities. Activities that are already running are not stopped. Figure 6: View the Stop Execution Pushbutton When you choose the Stop Execution pushbutton, the batch job with the Plan execution is finished and the Start Execution pushbutton is available again. In the Plan view for Group 1 Package Settings 02, you can see that the status icon changes to a van symbol, the status text to Running and the process indicator to 7 %. For the latest information, you can occasionally choose the Refresh pushbutton. Figure 7: Check the status of the Blocks October

12 When you choose the Switch to Configuration View pushbutton, you get the same information as in the Plan view but in a table format. Figure 8: PEM Configuration View If you want to see the activities of the Block Package Settings 02 you can click the text Package Settings 02 in the Block. This is available in both views. Figure 9: Activities of Package Settings 02 Block You see all activities assigned to that block with the same information as in the process tree/process structure. The following screenshot shows a cutout of the Plan view during the plan execution. You can see that in Group 5 the Dialog Block (icon with the little person in upper left corner of the Block) is successfully (green state and 100 %) executed. You also see that the batch block is running with a processing of 8 %, while the dialog blocks in Group 6 and Group 7 are already processed to 100 %. If a dialog block only contains optional activities, the activities are not relevant for the calculation of the progress and completion is displayed as 100 % and successfully finished. From this information you can understand that the next set of dialog activities that you have to process comes after finishing the Block Data Transfer 09 at the earliest. Because the completion is 0 % and this shows that this Dialog October

13 Block contains required activities. Figure 10: Status and Activity Completion Percentage of PEM Plan View Dialog Block If the Processing Gets Stuck The Plan execution could be running but without any progress. Reasons You may have to execute the required dialog activities. Some activities may have terminated. The Plan execution tries to restart the terminated activities if your activity settings allow this. If at least one activity is terminated, you can see the Aborted icon in the batch block. Figure 11: View of a Terminated Activity Click the underlined block name. You can view a table with all related activities. You can enable more October

14 details by selecting the different options in the pull-down menus Activity Display and Columns. Figure 12: Status of the Terminated Activity After you locate the aborted activity in the table, you can see that the PEM execution tried to restart the activity 85 times without success. It would be the best to Stop the Plan execution and fix the problem. To locate the issue, follow the same steps as from the process tree (check log, check batch job (aborted, log), check SM21, check ST22, ). 3.2 PEM Plan calculation Optional activities are registered in the PEM content table as inactive. Inactive activities are not executed with the PEM plan execution. Activities that are not executable are not written into the PEM content table PEM Plan Recalculation If after the first calculation something changes in the PCL process tree, a re-calculation of the PEM plan is required. PEM carries out the recalculation automatically. If something changes that requires a recalculation, but the PCL process tree is not changed (for example, imported corrections from a note), you can recalculate the PEM plan by calling the transaction CNV_MBT_PEP_REPAIR PEM Plan Manual Settings In the SAP LT Workcenter in the PEM area, you can change the Block settings to your requirements. You can split/merge blocks of the same group and you can set an optional activity to active (so that it is executed by PEM) Split/Merge Split a Block Split a block into two blocks. We want to move a selection of activities from the Block Data Transfer 09 into a new block. The reason could be that we want to schedule these activities differently than the other block. Choose the Edit pushbutton in the overview mode. The Merge Blocks and Split Blocks pushbuttons are visible on the screen after the Edit pushbutton is selected. October

15 Figure 13: View Merge Blocks and Split Blocks Pushbutton We want to split the Block Data Transfer 09, hence we select this row in the table and choose the Split Block pushbutton. Figure 14: Choose the Row for Split Block A screen appears with the activities of the block displayed in the left table (source block). The activities we want in the new block have to be moved from left to right to the Split Block table. To do this, select the activity and move it to the right by choosing the Add pushbutton. October

16 Figure 15: Select Activities to be moved to the New Block In the screenshot below, the last five activities are selected as an example. Choose Add. Figure 16: Choose Add Pushbutton to move the Activities to the New Block To confirm the new Block, save your selections by choosing the Save pushbutton at the bottom right. October

17 Figure 17: View Activities moved in the New Block We have now derived two blocks from the original one. This is recognizable by the sequence number in the Block name. Figure 18: New Blocks Data Transfer 09-1 and 09-2 are Created Set Optional Activity as Active The PEM Plan execution only executes active activities. If you want activities that are not active to be executed, you can set them as active in the overview of all activities in a block. This overview screen appears if you are on the Process Execution Manager tab page in the Plan view or Configuration view and if you click the package name (represented as link). October

18 Figure 19: View the Opt. and Act. Activities You see that the last activity - Refresh of Data Deletion Cluster for the Current Transfer (PC002_DTL_CLUSTER_DELETE_SND) - is optional and not active. This activity is not executed by PEM. To select the checkbox, choose the Edit pushbutton. Select the checkbox in the column Act. Figure 20: Select the Opt. Activity as Act. Activity Save your settings to make them valid. The activity is automatically executed by PEM. Merge Blocks You can merge blocks in the same group. We use our previous example and merge the splitted block again. To do this, we have to select the rows with the two blocks. October

19 Figure 21: Select Two Activities to be Merged Next, choose the Merge Blocks pushbutton to make one block out of two. A dialog box appears where you can confirm that you want to merge the two blocks. Choose Yes. Figure 22: Choose Yes to Merge the Activity The result is that both blocks are merged into the Block Data Transfer Figure 23: Blocks Data Transfer are Merged October