Getting Started with Getting Started with Winshuttle TRANSACTION

ADSOTECH Finland

6.2.2013

Getting Started

TRANSACTION User interface

Creating the first script

Problem investigation

Reporting a Script problem to ADSOTECH

2

2

TRANSACTION User interface overview

3

3

User interface overviewCREATE NEW SCRIPT

OPEN SCRIPT FROM FILESYSTEM

RECENTRECENT SCRIPTS

FAVORITESCRIPTSSCRIPTS

4

4

User settings – Application defaults

Select Tools -> Options -> Application Defaults

You do not need to change these settings but especially the two first 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.

5

5

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.

6

6

y y g g g p

Creating the first TRANSACTION script

7

7

Creating the first TRANSACTION script

Transaction MM02U d b i d fi ld Update some basic data fields

Perform the script creation stepsC Create

Map Run Run

8

8

STEP 1STEP 1

Create the recordingCreate the recording

Start recordingg Connect to SAP Use the transaction to update fieldsp Finally save the data

9

9

Start recording

Press “New” to start recording, enter transaction code to record and then press “Go”

10

10

Connect to SAPFirst time when connecting to SAP, select correct system, check “Use selected system as default”

Provide SAP credentials.

11

11

Accept the default recording properties

The default recording mode is good in most cases.g

For special recording requirements you may be advised to use some other recording mode.

12

12

SAP – Enter material number

Enter the material number manually or use the popup to select an existing material.

13

13

SAP – Select Basic Data 1

Only select “Basic Data 1” on this ViewOnly 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 accessview at this point. Even if you need to access multiple views you should do it once you get into the actual transaction data screen.

14

14

SAP – Update fields

When you touch some fields in SAP, the TRANSACTION product will later in the pmapping 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) ( p )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. In this case however, you will first need to enable the field in the mapper.

15

15

pp

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. y

16

16

SAP – Change the Basic material

17

17

SAP – Press back and then Yes to save

18

18

Recording step is completed

19

19

STEP 2STEP 2

Map fieldsMap fields

Map SAP fields with Excel columnsp Mapping by drag-and-drop Save script and the newly created Excel templatep y p

20

20

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.

21

21

p pp

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

Mapping type

Values entered

22

22

Mapper – Excel content

Initially the Excel window shows an empty file. In this p yexample the mapping will be performed against this empty Excel file. This will result in a new Excel file being created in gaddition to the script file.

23

23

Mapper – Mapping

The purpose with the mapper is to map SAP fields with Excel pcolumns.

Easiest way to perform the mapping is by Drag-and-drop.pp g y g p

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)

24

24

Mapper – Mapping material number

Drag with your mouse from Column A to SAP field Material number.

25

25

Mapper – Mapped material number

Once mapped, the mapping type shows the data direction ypand 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 pp gwhat data was entered when the recording was made.

26

26

Mapper – Mapped all fields

This is the result when all fields are mapped in the same way, pp y,from Excel to SAP.

Note that the “Checkbox” field has not been mapped. This ppfield is the “Basic Data 1” entry which was selected on the initial “View selection” screen. It has not been mapped because ppthe 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

27

27

recording.

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 ysuggested by the product, simply provide the desired name for the file and store it in the folder suggested.gg

28

28

Save script file

You will also be asked to save the new script.p

Note: It is strongly recommended that you do NOT browse to any other folder than ysuggested by the product, simply provide the desired name for the file and store it in the folder suggested.gg

29

29

Map completed – user presented with Run window

30

30

DEMO

MM02 recording and mappingg pp g

31

STEP 3STEP 3

Run the recordingRun the recording

Prepare Excel datap Run script in test Once tested, run in production, p

32

32

Open Excel file

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

33

33

Prepare the Excel file

And save the excel file

34

34

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.

35

35

p y y p g

Result of first execution – some data error

S t t lSet 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”.

36

36

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.

37

37

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.

38

38

Running in production

Every time when you execute a script, you will be presented with the Logon y p gscreen. On this screen you always have the possibility to click on the “System” button and pick any target SAP system you like. y

For example executing a script in production only requires you to select the production SAP from here and pprovide authentication details for that system.

39

39

DEMO

MM02 running the scriptg p

40

TRANSACTION Problem investigation

41

41

TRANSACTION Problem investigation

The following slides contain important tips about how to investigate issues when a script does not perform as expected

You may for example get messages into Excel that does not explain anything about the nature of the problem or the script simply does not do its jobscript simply does not do its job

42

42

TRANSACTION Problem investigation

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 TRANSACTION online helpp Re-create using other recording mode (batch/non-batch) Knowledgebase: wise.winshuttle.comg

43

43

Extended Log

The feature helps you capture the warning messages, p y p g g ,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

This option is only available if the recording was made in “Non-batch input mode”

44

44

Extended Log in Excel

Additional Log Column which gives the detailed error

45

45

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

Run in foreground – Step by step execution

Use the step-by-step feature to find causes of errors in running a transaction or to simply playback a recording.running a transaction or to simply playback a recording.

The “Step-by-Step Run – Stop on all Screens” is usually the best way to find out exactly what is going on during execution. You will see every screen step and message retrieved from SAP.

46

46

Run in foreground – Step by step execution

Debug option which helps us to step through every i h discreen in the recording.

Useful in situations when you do not understand what is act all ha enin d rin e ec ti nactually happening during execution

You can drive the execution by working on the small “OK code” popup windowcode popup window

Only press enter in main sap window if needed If needed compare execution dialog with recorded dialog If needed, compare execution dialog with recorded dialog

in order to identify where there is a difference

47

47

Launch GUI option

Scripts that ONLY run successfully in step-by-step mode Transactions using file i/o dialog boxes or other Windows

resources and “Park” Accounting transactions Transactions which give run-time error messages:

“Transaction Terminated by User” “Protocol error when communicating with SAPGUI”

Try the option, it may help:

48

48

DEMO

MM02 showing extended log and step-by-step executiong g p y p

49

Reporting a Script problem to ADSOTECH

50

50

Reporting a script problem to ADSOTECH

Check the problem investigation recommendations first If you cannot solve the problem, please provide the

following information to Adsotech: Problem description, print screens etc. Problematic script file and related Excel file. The Excel file should

contain the execution result Also include the * bak file having the 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.D ib h f h “S b ll ” Describe the outcome of the “Step-by-step stop on all screens” run

TRANSACTION product version (showed on the startup screen)

51

51

Where to find more information

Product itselfS i Starting tour

Online helpP Product manual

www.winshuttle.com Step-by-step guides Case studies Etc.

wise.winshuttle.com

52

Knowledgebase

Further contacts in Nordic Countries

ADSOTECH Scandinavia OyPiispanportti 502240 ESPOOFINLAND+358 10 321 6260

Sales:Christer Mäkelä, +358 10 321 6262christer makela@adsotech com +358 40 900 9990christer.makela@adsotech.com +358 40 900 9990

Support:Jan Mattssonjan.mattsson@adsotech.com +358 40 900 9992support@adsotech.com +358 10 321 6266 –

- : : - 6270

53