Winshuttle STUDIO 11 TRANSACTION Developer · PDF fileWinshuttle Studio 11 TRANSACTION Developer Basic Training ... XK02. Basic Training Advanced Training 1 Advanced Training II 25

Copyright ADSOTECH Scandinavia Oy 2016

Winshuttle STUDIO 11

TRANSACTION Developer

Advanced Training 21

Copyright ADSOTECH Scandinavia Oy 2014

Basic Training Advanced Training IIAdvanced Training 1

Contents

2

Winshuttle Studio 11


Basic Training

User Interface

Creating the First Script

Problem Investigation

Recording Modes

Reporting a Script Problem to ADSOTECH



Advanced Training I

Multiline Recordings (Loops)

Script Linking

Backup SAP Data

Data Validation

Read From SAP



Advanced Training II

Cell Based Mapping

Dynamic Recordings (Conditions)

Managing Long Texts

Making Scripts Available for Runner Users


3

Today’s Agenda

Cell Based Mapping

Dynamic Recordings (Conditions)

Managing Long Texts

Making Scripts Available for Runner Users


4

Cell Based Mapping


5

What is Cell Based Mapping

• User friendly form

• No mass upload

• Single document entry

• SAP fields mapped to Excell cells

• Fields within loop still mapped to Excel columns


6

Cell Based Mapping

• Recording process remains the same

• Will use a loop for line items

• Remember the recording specifics

First things after recording:

• Click Column Mapping

• Open your existing Excel template

Map menu


7

Cell Based – Loop

To create the loop, find the repeating pattern in

the script and select one section of that pattern.

Click Create Loop.


8

Cell Based – Loop

In the popup,

select Specify row range.

Then give Start and End Row for the

line items in your Excel template.


9

Cell Based – Loop

The loop is defined. Now disable the other line item(s) in the script.

Select the unnecessary lines

and right click. Select Disable.


Cell Based MappingSwitch to Basic View for drag-and-drop

Drag the header level

fields from specific

Excel cells

For line items you need

to drag from the correct

column.

The start row of the line

item data has been set,

so dragging from a row

above the start row is

fine, the correct column

is essential.


11

Demo

• Cell Based Mapping for FB50


12

Dynamic Recordings – Conditions


Recording vs. script execution

13

By default, the dialog appearing during

script execution must match the

recorded dialog. The screens must

appear in the recorded order and each

enabled field in the script must exist on

the respective screen.

If the above does not

happen, the run will fail.

Screen A

Screen B

Screen C

Screen D

Screen E

RECORD RUN

Screen A

Screen B

Screen C

Screen D

Screen E


14

Using conditions

Screen A

Screen B

Screen C

Screen D

Screen E

RECORD RUN

If first transaction...

If Excel column Y...

If SAP field Z...

Screen A

Screen B

Screen C

Screen D

Screen E

If Excel column X...

When you know what will happen in

SAP based on data in Excel or SAP.

Or what you want the script to do in

SAP depends on data in Excel or SAP.

Different condition types

are available. A condition

can contain 1 to n fields,

1 to n screens.

Select the script lines

and click Create If

Condition.


15

Conditional execution

Logical If or If-Else

conditions

Based on Excel data

Based on SAP data

Specific SAP behavior for first

or subsequent Excel row(s)

Control when to

perform a specific

part of the script

First Transaction –

initial screen different

first time / subsequent


16

Condition definition

Define condition:

When to perform

this part of the script

And / Or operators

can combine

conditions for more

complex scenarios

If Column E < 100

or

If Col E = Col F

Map menu

Expert View

Select script row(s)

Create If Condition


17

Skip If Not Present

Screen A

Screen B

Screen C

Screen D

Screen E

RECORD RUN

Skip If Not Present

Screen A

Screen B

Screen C

Screen D

Screen E

Screen level condition

Usually a popup that appears in some

cases and not in others. The behavior

cannot be figured out based on the data

in Excel or in the used SAP transaction.

Not to be used inside a loop


18

Skip If Not Present Map menu, Expert View

Select the screen row

Skip If Not Present

Also available in Properties panel


19

Skip If Not Present – Example

• Transaction TK11 –

Create condition

• Screen ”Overlapping

validity periods”

• Don’t know before the

run if it will appear

• Skip If Not Present

solves the issue


20

DEMO

• If condition


21

DEMO

• FB50 with/without Company Code prompting

Debug run to show what the script does

Run by another user / in another system

Fix to fit different users / systems


22

Managing long texts


23

Managing Long Texts

• Long Text fields can be updated or read

• Sales Text, Purchasing Text, Item Text...

• Traditional recording

• Consider recording mode

• Consider SAP view

• Automatically for certain Tcodes

• No need to record Long Text fields

• Long Text fields fetched automatically


24

Automatically – Add Long Text

• No need to navigate to long texts when recording

• Map menu – Add Long Text

• Only for certain Tcodes

FB02, FB03

IW22

IW32

ME22N

ME52N

MM02

VA02

XD02

XK02


25

Automatically – Add Long Text

• Texts added at the end of the script

• The text + key information, like Sales Doc number

• Also Long Text Log message added

• Next to Run Log

• Displays issues with added text


26

Traditionally in SAP

Default View: One block of text

Line View:

Each line treated as a separate SAP field


27

Traditionally – Recording Modes

• Standard

• Update in Default View

• Update in Line View

• Read in Line View

• Batch

• Update in Line View

• GUI Scripting

• Update and read in any view


28

Traditionally – Default View

• Requires Standard recording mode

• Update only

• Fields listed at the end of the script

• Can not be used inside a loop or condition

• One text mapped to one Excel column


29

Default View in SAP

Standard recording mode


30

Traditionally – Line View

• Each line of text is considered an SAP field

• Field name RSTXT_TXLINE(nn)

• Each line mapped to different Excel column

• Update or read

• Reading requires Standard recording mode

• Update with Standard or Batch


31

Line View in SAPDetails

Goto

Change Editor


32

DEMO

• MM02 long text automatically

• MM02 long text recording


33

Making scripts available for

Runner users


34

Script execution alternatives

• Studio application

• With Developer license

• With Runner license

• From Excel with add-in

• With Developer license

• With Runner license

• Studio application installed

• Best used when script(s) published to Excel file


35

The Excel Add-in

• Installed and activated when installing Studio

• New menu appears in Excel

• If not, check settings in Studio

• File – Options – Data –

• Run script directly from Excel

• No need to open Studio

• Best when Developer published script(s) to Excel file

• Usable without published script(s)


36

Publish Script

• Embed the script in Excel to make running easier

• Developer’s task

Run – Publish

Check script,

Excel file and

Sheet names.

Click Publish.


37

Using the Add-in

• Winshuttle Run – Logon to Winshuttle – Logon to SAP

• Excel file may contain multiple scripts

• Run by row numbers, selected, filtered

• SAP Values pick list – Lookup Values


38

DEMO

• Publish a script to Excel – Developer

• Use add-in to run a script – Runner/Developer


ADSOTECH Scandinavia OyPiispanportti 502240 EspooFinland+358 10 321 6260

Sales:Christer Mäkelä +358 10 321 [email protected] +358 40 900 9990

Support:[email protected] +358 10 321 6267

39

Contacts in the Nordics

mailto:[email protected]

mailto:[email protected]

Documents

Winshuttle STUDIO 11 TRANSACTION Developer · PDF fileWinshuttle Studio 11 TRANSACTION Developer Basic Training ... XK02. Basic Training Advanced Training 1 Advanced Training II 25