TRANSACTION Developer Basic Training. Copyright ADSOTECH Scandinavia Oy 2014

Transcription

1 TRANSACTION Developer Basic Training 1 Copyright ADSOTECH Scandinavia Oy 2014

2 Contents Winshuttle TRANSACTION Developer Basic Training TRANSACTION User Interface Creating the First Script Problem Investigation Recording Modes Reporting a Script Problem to ADSOTECH Winshuttle TRANSACTION Developer Advanced Training I Multi-line Recordings (Loop Functionality) Script Linking Backup SAP Data Data Validation Read From SAP Winshuttle TRANSACTION Developer Cell-Based Mapping Dynamic Recordings (Conditions) Managing Long Texts (Read and Update) Making Scripts Available for RUNNER Users GUI Scripting (Optional) 2

3 Today s Agenda TRANSACTION User Interface Creating the First Script Problem Investigation Recording Modes Reporting a Script Problem to ADSOTECH 3

4 TRANSACTION User Interface Overview 4

5 User interface overview Create new script Open Script from filesystem Recent Scripts Favorite Scripts 5

6 User settings Application defaults Select Tools -> Options -> Application Defaults You do not need to change these settings! The first two paths are important to know because all your Excel files and Script files (*.txr) that you create will by default be stored in these folders. 6

7 User settings SAP Defaults Select Tools -> Options -> SAP Defaults This option causes TRANSACTION to remember the last SAP password you entered as long as the TRANSACTION product is kept open. Without this option the password needs to be entered manually every time when starting a recording or executing a script. 7

8 Creating the First TRANSACTION Script 8

9 Creating the first TRANSACTION script Transaction MM02 Update some basic data fields Perform the script creation steps Record Map Run Tips! Know your transaction, rehearse the steps on SAP before recording Know your data, know what materials to use Check for transaction s tips and tricks from support.winshuttle.com 9

10 STEP 1 Create the recording Start recording Connect to SAP Use the transaction to update fields Finally save the data 10

11 Start recording Press New to start recording, enter transaction code to record and then press Go 11

12 Connect to SAP First time when connecting to SAP, select correct system, then check Use selected system as default. This mean all scripts will be run against this system by default. Otherwise, you have to select the system every time connecting to SAP. Note: The scripts are not system dependent. Provide SAP credentials. 12

13 Accept the default recording properties The default recording mode is good in most cases. For special recording requirements you may be advised to use some other recording mode. 13

14 SAP Enter material number Enter the material number manually. 14

15 SAP Select Basic Data 1 Only select Basic Data 1 on this View selection screen. It is always recommended to only select this first view at this point. Even if you need to access multiple views you should do it once you get into the actual transaction data screen. 15

16 SAP Update fields When you touch some fields in SAP, the TRANSACTION product will later in the mapping step recommend that these fields will be the ones that you should map against your Excel file. Note that touching a field means more than just placing the cursor in a field. Not until you change the actual value or simply overwrite one of the characters (for example with same value) in a field the action will be registered as a change and field will be recommended by TRANSACTION. Note also that even if you do NOT touch a field, you can still map it in TRANSACTION (for the screen you have visited). In this case however, you will first need to enable the field in the mapper. 16

17 SAP Go to Basic Data 2 Note: If you have so many views that not all view tabs are visible simultaneously then a dropdown list icon will appear. If this icon appears, always use this dropdown list to select the next view. If there are less views and there is no dropdown list possibility, simply click on the Basic Data 2 tab directly. 17

18 SAP Change the Basic material 18

19 SAP Press back and then Yes to save 19

20 Recording step is completed 20

21 STEP 2 Map fields Map SAP fields with Excel columns Mapping by drag-and-drop Save script and the newly created Excel template 21

22 Select Create Mapping The Auto Mapping feature can be used to automatically map all enabled fields. It is a very quick way to perform the mapping. We will use the Create Mapping option since it provides full control over how the fields are mapped. 22

23 Mapper SAP fields The Mapper shows by default all the Enabled SAP fields. In practice this means fields which were touched during the recording. Field descriptions Technical names Values entered Mapping type 23

24 Mapper Excel content Initially the Excel window shows an empty file. In this example the mapping will be performed against this empty Excel file. This will result in a new Excel file being created in addition to the script file. 24

25 Mapper Mapping The purpose with the mapper is to map SAP fields with Excel columns. Easiest way to perform the mapping is by Drag-and-drop. Note that the Drag-and-drop action must be performed in the correct direction. Dragging from Excel to SAP means data is transferred from Excel to SAP. Dragging from SAP to Excel means data is transferred from SAP to Excel (=Read from SAP) 25

26 Mapper Mapping material number Drag with your mouse from Column A to SAP field Material number. Drag-and-drop... 26

27 Mapper Mapped material number Once mapped, the mapping type shows the data direction and value A indicates data is taken from Excel Cell A. Because we started with an empty Excel file, the Excel header and first data row is also automatically filled based on the mapping and based on what data was entered when the recording was made. It is also possible to map the fields to excel file containing existing data. 27

28 Mapper Mapped all fields This is the result when all fields are mapped in the same way, from Excel to SAP. Note that the Checkbox field has not been mapped. This field is the Basic Data 1 entry which was selected on the initial View selection screen. It has not been mapped because the mapping type is Fixed value (red icon) and we want the recording to always do this on the View selection screen. In this way you can simply leave a field unmapped and enforce a fixed value in the recording. 28

29 Save Excel file Click on the Back arrow and then save the new Excel file. Note: It is strongly recommended that you do NOT browse to any other folder than suggested by the product, simply provide the desired name for the file and store it in the folder suggested. 29

30 Save script file You will also be asked to save the new script. Note: It is strongly recommended that you do NOT browse to any other folder than suggested by the product, simply provide the desired name for the file and store it in the folder suggested. 30

31 Map completed user presented with Run window 31

32 DEMO MM02 recording and mapping 32

33 STEP 3 Run the recording Prepare Excel data Run script in test Once tested, run in production 33

34 Open Excel file The Excel file can be opened from the Run window by pressing the small green Excel icon. 34

35 Prepare the Excel file And save the excel file 35

36 Execute the recording You may keep the Excel file open when you start the execution. Open the TRANSACTION window and press Run. SAP Logon screen appears but if you did set the Remember last login password at the start you only need to press enter on the login screen. 36

37 Result of first execution some data error Set correct value. Most rows were ok. On row 4 there was a data error. The error message was retrieved from SAP. We attempt to fix it by setting the correct value for Base unit of measure. 37

38 Rerun rows in error after Excel fixed The Run on errors option means re-run only rows with errors. Select this option and then press Run again. 38

39 Result of the second execution everything ok The Green row indicates execution was successful after a re-run. At this point all rows have been successfully updated. 39

40 Running in production Every time when you execute a script, you will be presented with the Logon screen. On this screen you always have the possibility to click on the System button and pick any target SAP system you like. For example executing a script in production only requires you to select the production SAP from here and provide authentication details for that system. 40

41 DEMO MM02 running the script 41

42 Problem investigation 42

43 Problem investigation First things to check: The excel log column Retrieve all messages from SAP Extended log Run in foreground Step-by-step stop on all screens In some cases Launch GUI option helps First excel row ok, others always fail: Step-by-step mode, see problem diagnosis guide 43

44 Problem investigation More help: TRANSACTION online help Re-create using other recording mode (batch/nonbatch) Knowledgebase support.winshuttle.com 44

45 Extended Log in the Excel The feature helps you capture the warning messages, information messages and other messages that appear during the execution of a transaction The extended Log can be obtained in a different column in the excel or as a comment in the Log column 45

46 Extended Log in the Excel Additional Log Column which gives the detailed error obtained while the transaction ran in SAP 46

47 Error Handling Fix Error in Excel File Choose Run on Errors Only the records with errors will be selected and run. Use the step-by-step feature to find causes of errors in running a transaction or to simply playback a recording. Debugging & Troubleshooting options in case of errors 47

48 Debug Run Options Step-by-Step Stop on all Screens Debug option which helps us to step through every screen in the recording. Useful in situations when you do not understand what is actually happening during execution You can drive the execution by working on the OK code window Only press enter in main sap window if needed to accept information and warning messages. In other cases if you do not get a pop-up window for the OK code, then it is probably an issue. Carefully compare execution dialog with recorded dialog in order to identify where there is a difference 48

49 When to use Launch GUI? Use default setting. If there re issue with the run, then change the setting Park Accounting Transactions Transactions using file input/output dialog boxes or other Windows resources Transactions that run successfully in step-by-step mode, but not in normal runs Transactions which give run-time error messages: Transaction Terminated by User Protocol error when communicating with SAPGUI 49

50 DEMO Problem investigation using MM02 50

51 Recording modes 51

52 Recording Modes Non Batch Input Mode - Default Upload, Download(Read Data), Dynamic actions & User parameters involved, Extended Logging, Long Texts Batch Input Mode Upload only, Most transactions for creation of data GUI Scripting Scripting must be enabled in the SAP system Special recording requirements Tips! Check Winshuttle Support site for recording mode recommendations before recording your transactions. 52

53 Why use Batch Input mode? Batch input mode: Some of the SAP transactions are optimized to run in this mode. Does not remember individual user settings if sharing the scripts The beginning and input screens are different (remove this line) Messages may be different in the transaction Suppressing the Information pop-up 53

54 Batch Input mode Do not use batch input : If need to read from SAP If need to remember your user settings Batch input mode examples Material Classification Characteristics MM02 Bill of material CS01, CS02 54

55 Why use Function Module? Only available from Winshuttle version and above Recommended for use with SAP BASIS 7.00 Support Package 24/ EHP5 or later 55

56 Why use GUI Scripting mode? When nothing else works For example using the dynamic treeview control in PA40 etc. transactions works only in this mode Link to other scripts to add features Details GUI scripting must be enabled for user in SAP Execution slower, always in foreground Recording more technical, low-level, more error-prone All screens and popups are recorded Index based looping feature 56

57 DEMO MM02 using GUI scripting 57

58 ? 58

59 Reporting a Script problem to ADSOTECH 59

60 Reporting a script problem to ADSOTECH Check the problem investigation recommendations first Slide If you cannot solve the problem, please provide the following information to support@adsotech.com Problem description, print screens, transaction code etc. 60 Problematic script file and related Excel file. The Excel file should contain the execution result. Also include the *.bak file having the same name as the script file and which is located in the same folder as the script file.

61 Where to find more information Product itself Starting tour Online help Product manual Step-by-step guides Case studies Etc. support.winshuttle.com Knowledgebase 61

62 Adsotech s services Training Tailored on-site training Certification training at Espoo, Finland Web trainings Consultancy Script/Workflow development Best practices Installation services Winshuttle User Group meetings User Groups in Finland, Denmark, Norway & Sweden 62

63 Further contacts in Nordic Countries ADSOTECH Scandinavia Oy Piispanportti Espoo Finland Sales: Christer Mäkelä christer.makela@adsotech.com Support: support@adsotech.com