SIAMEASE SCRIPTING
Contents
1. RUN STEP ITERATION RESULT RESULT RESULT RESULT RESULT RESULT COUNT al 2 3 4 5 6 1 002 1 100 Assetl i 002 2 TOT Asset2 Ji 002 3 102 Asset3 il 003 di 100 000000100 1 003 2 101 000000101 di 003 3 102 000000102 18 34 INBOUND RULE The inbound rules determine where the source of data is coming from how input fields vary their values how many records are to be processed what previous data is referenced step Gylvariant S RefStep item ABAP Program TCode Transaction Description 2l e poo NER one Cae 002 Pa MANUALTEST ZAM_4S601_001 A501 Create Asset Master Record tapi ZAM AS02 001 ASO2 Change Asset Master Record 03 falLOOPTEST Primarily a SAP variant defines the inbound rules Data for each business scenario can either be referenced by a variant or can be captured explicitly into Manual Parameters against each specific task The script therefore needs to only refer to the inbound rules by specifying a relevant variant The variant icon allows a variant to be configured for each task When tasks are imported the tasks default variant is imported as the default script variant ia 19 34 DATA SOURCE The data source defines from where data is being loaded and can be one of the following MANUAL Manual parameter values are captured and saved as a variant UPLOAD data is read from a text data file that will be uploaded CLIPBOARD data is impo2. EFFECTIVE TODAY ESSENTIAL TOMORROW SIAMEASE SCRIPTING Simmonds and Associates Copyright 2001 Scripting and the Management thereof Functional User Manual SIAMEASE 3 0 SAP R 3 Automation SIMMONDS AND ASSOCIATES COPYRIGHT 2001 2 34 CONTENTS Chapter 1 FOREWORD Chapter 2 DOCUMENT SPECIFICATIONS Chapter 3 METHODOLOGY Chapter 4 SIAMEASE SCRIPTS OVERVIEW Chapter 5 SIAMEASE SCRIPT BUILDER OVERVIEW CREATE A SCRIPT STEPS ADDING AND REMOVING TASKS REPEATING STEPS NAVIGATION ADDING ATTACHMENTS ADDING MEMO TEXT Chapter 6 SCRIPT RULES SCRIPT VARIABLES OUTBOUND RULES INBOUND RULE ENHANCED VARIANT CONSIDERATIONS LINKING SCRIPTS SCRIPT RULE SUMMARY Chapter 7 SIAMEASE SCRIPT MANAGER 6 OVERVIEW CREATING AND CHANGING SCRIPTS EXECUTING SCRIPTS VIEW RUN RESULTS Chapter 8 APPENDIX A CASE STUDIES THE TRAINING CLIENT SCENARIO TESTING STRESS TESTING oa A k 25 26 27 27 28 28 31 33 33 34 34 3 34 Chapter 1 FOREWORD Special thanks to all the people who have helped with the development and testing of Siamease Many specialist consultants have volunteered their business and technical advice to make Siamease a product that most SAP projects cannot be without Siamease provides a wide range of functionality It does this by exploiting SAP automation thus allowing users to execute SAP transactions in bulk using data that has either been uploaded from a legacy system or
3. SD Sales and Distribution D LI Prototyping PROTOTYPIN EXECUTING SCRIPTS Scripts can be executed via the Script Manager or the Script Builder Press the execute icon On the execution screen a counter can be set to repeat the entire script a number of times A starting number can also be specified The results of the run can be saved and are visible from the Script manager or by pressing VIEW RESULTS from the Script Builder Results need only be stored if they need to be viewed at a later stage Specifically useful for integration testing where previous test results are helpful for comparisons EXECUTE SCRIPT 2 Execute To execute e Select the desired script as above 28 34 e Press the EXECUTE icon Siamease Project Test Run 29 34 SELECTING TASKS SCRIPTS e The script executor can run a single script or many It also has the ability to run selected tasks or all tasks within a project Enter any combination of the following fields to select the desired task list Siamease Script No 500006 to EE Alternative Test Project to gt Task a ta a Er RUN PARAMETERS e The run parameters allow the script to be executed more than once By specify a high value a stress test can be initiated e If the selection screens visible option is checked then each task in the script once executed will display its own selection screen one after the other e Save results to database ensures that the test results a
4. the number of times that this step has run e L LINE the number of transactions that have been created by this item COUNTER The Siamease script executor can execute a script a number of times The C counter variable will increment for each iteration of the entire script The script executor can also specify a starting point for this counter Testing snd Training 25rameters Numoacr of imes o run script Se serpicountarto scart at STEP A Script defines which tasks are to be run Each task is assigned a step number which determines the order in which the tasks are run The execution of a step will set this counter to the step number If the first task that runs is in step 3 i e the first 2 steps are commenis then this counter will be set to 3 even though it is the first step to run The reason for this is to allow easy reference to the data created by that step at a later stage ITEM 8 LINE ITEM will increment each time a specific step is called The script can specify that a step must be repeated 4 times This time the step is executed the ITEM counter will increment and the LINE counter will reset to 1 If a specific step were to run with 4 input records it would then increment the LINE counter for each transaction posted to SAP If a step were to load data from a spreadsheet then each row loaded from the spreadsheet would be referenced by a LINE value Item would remain constant since the step was only called once 1
5. 20 34 INBOUND VARIANT COMMANDS The MANUAL data source is available to all Siamease tasks Using normal SAP logic it allows a single set of scenario data to be stored by capturing the Manual Parameters and saving as a VARIANT To extend standard SAP logic Siamease provides Inbound Variant Commands that will allow formulae and script variables to be embedded into the manual parameters Each time the task is run new values can now be substituted into the manual parameters fields amp Refers to the script variables and can be embedded anywhere in a field value A formula where a string can be passed to the formula for processing Results from previous runs can be accessed VARIABLE SUBSTITUTION a TEXT amp C amp S amp I amp L Any manual parameter value containing a amp C amp S amp l or amp L will automatically be substituted with the current script variables Each variable is a 3 digit number i e 001 to 999 The inbound variant command can be found anywhere in a string and is useful for varying descriptive information Serial number 999 amp C amp Customer name Joe Soap amp I for class group amp C In the example above a step may be configured to repeat 4 times Each iteration will increment the amp l counter and will therefore results in creating 4 transactions each with a different serial number and customer name Will result in serial number 999001001 and Joe Soap 002 for class group 001 Serial Number C
6. and can be referenced by the variant for input After a transaction has run a system message is usually presented to the user The contents of that message are stored within system variables SSY MSGV2 If a material was created using transaction MMO01 After the material was saved the user would see the message MATERIAL 123 HAS BEEN CREATED SUCCESSFULLY 17 34 Each part of the message would be available in the following fields SY MSGV1 MATERIAL SY MSGV3 HAS BEEN CREATED SUCCESSFULLY STORE INPUT DATA n 12 stores the 12th column parameter loaded This option refers to the column from the input data that you wish to save If the data is loaded from a spreadsheet then n refers to the column number to be saved This option will also make any field conversions visible in the results E g if an input field utilises an inbound conversion rule then the value after the conversion will be available in the results table ILLUSTRATED oA Rule 1 oa Rule 2 N Rule 3 da Rule 4 oA Rule 5 h Xref Rule B01 B02 AN1 003 AN1 004 In the illustration above Step 2 is configured to run 3 times Each iteration will create an asset that is required in step 3 Step 3 has an inbound rule that references the old asset number in results 6 and returns the corresponding new asset number stored in results 1 The results of step 1 are stored in a results table illustrated below RESULTS TABLE
7. data that already exists within the customer SAP database Users are therefore able to perform data migration build interfaces maintain live customer data build training systems and build test scripts This document explains all options available within Siamease Separate documents exist that walk through business scenarios Siamease consists of 4 components a Task Builder a Task Manager a Script Builder and a Script Manager Please feel free to email your comments to us at simmonds global co za Chapter 2 DOCUMENT SPECIFICATIONS Prepared by Simmonds and Associates Released 2001 04 27 SAP Versions 4 6 Audience SAP Implementation Teams Super Users Development team Functional Consultants Data Administrators Training Teams Basis stress testers Project Managers Trademarks Microsoft Excel is a trademark of Microsoft 4 34 Chapter 3 METHODOLOGY Siamease is based on a methodology that empowers the business It does this by bridging the gap between the functional and the technical environments Most technical development starts with a functional specification which indicates that if we shorten this process or eliminate its need altogether then we are on the right track Siamease provides a comprehensive and complete solution to functional team members and does all the technical stuff for them leaving them to apply business decisions in their area of expertise in respect of data migration interfacing maintenance
8. have very little time having to prepare within the last hour The Siamease Scripting tool allows tasks defined for data migration to be reused for defining the training client If defined correctly and completely a script would be quite capable of creating all the data required to train the class Quite often the team that is training in one business module application area will be dependant on another to prepare the data for their class e g The Sales team may have to create customers finished products sales orders deliveries and invoices before the Finance team can train around the financial aspects of Sales such as clearing open items against an incoming payment or processing an unpaid for an invoice already cleared Scripting allows a complete business process to be documented and implemented a number of times over Each time the script runs it can create a free set of data that not only allows the trainer to prepare for training but also allows the playground client to be populated with clinically correct data that will allow new users to practice 33 34 SCENARIO TESTING Testing is often seen as a once off activity and in many cases projects learn the hard way that this is just not so Business processes need to be documented and expected results needs to be stored so that future testing can be done quickly and efficiently Usually manual scripts are created and testing is done manually covering as many processes that can be manual
9. script would then look as follows RULE 1 Note that both materials will have stock added without explicitly stating material 1 or 2 STEP4 Capture a sales order for customer 1 S 001 Capture a line item referencing 1st material 1 I 001 with reference step 002 Capture a line item referencing 2nd material 1 I 002 with reference step 002 22 34 n search string This option searches the 6th results field and returns the results specified by n 1 oldno001 When creating a customer master we may define 2 tasks one to create the basic customer master and another to add additional bank details to a customer This process was split into two because there are an unknown number of bank details for each customer lt makes sense to split into two tasks but creates the problem that the bank detail load does not know the customer numbers that are created in the first task The script is created to solve this problem After executing task 1 the basic customer master the outbound rule saves the newly created internally assigned customer number The outbound rule also specifies that the previous customer number must be stored in RESULTS using the command i e rule 6 equals 12 discussed in the outbound variant commands The results table will therefore contain the new customer number and the previous customer number Subsequent steps can then lookup results 6 and retrieve the new SAP number In the example the second
10. step would have defined a field in the upload spreadsheet that has the value 1 980001 Each line in the spreadsheet containing bank details can have a value referring to the relevant customer by means ofits previous customer number FORMULA FM text string This option allows parameters to be passed to a Form routine that will process the input data and pass a result back FM represents the form name to be called All forms are stored in the Siamease ABAP program ZCSEZEFM that contains a suite of formulae that can be referenced Refer to VARIANT FORMULA to maintain When the task is being run in a script script variables can also be embedded in the text string e g CT Some text with amp C amp S 8L amp l counters Refer to SCRIPT VARIABLES WORKINGDAYS 10 The above example calls a form that determines the date 10 working days from the current date The parameter 10 is passes to the form called WORKINGDAYS This means that the input parameter has defined a rule where the value will vary from day to day Unfortunately this feature is only available to Siamease tasks 23 34 ENHANCED VARIANT CONSIDERATIONS ADDING SIAMEASE FORMULAE TO SPREADSHEET DATA By default the Enhanced Variant functionality is only available to the sources MANUAL and RESULTS If you wish to include these options in the other sources then the VE option must be specified on the INCLUDE tab when generating the task Specific functionality can also be
11. to flow from one transaction to another With its intelligent data handling it eliminates the need to build lookup tables in the middle of a business process or data migration Scripting also focuses on the activities around the business process thus acting as a repository for documentation and data that can be used within the process Refer to Scripting Case studies to see how scripting is used creating training clients scenario testing and data migration SIAMEASE Secript Builder 6 34 Chapter 5 SIAMEASE SCRIPT BUILDER OVERVIEW Scripts are created with unique document script numbers and are classified under projects and application areas very much like tasks are A script is built using the Script Builder and managed via the Script Manager that makes all scripts visible to users and tracks results created by each scripts Scripting allows scenarios to be formulated and documented It allows a Functional Team to create an electronic procedure that can be executed to either create scenario data or to test a business scenario If executed more than once the same procedure can be used to measure system performance in a stress test In order to simplify certain data loads several tasks are created Each however performs a specific task if supplied with the right data to capture Scripting fundamentally allows data created by one task to be available for input in subsequent tasks This allows processes to be built as well as allowing p
12. within the system training and testing Siamease helps to break complex problems down to smaller manageable units Each unit is known as a Task within Siamease and is created using the Siamease Task Builder and managed and controlled via the Siamease Task Manager The Siamease Scripting tool allows these smaller components or tasks to be chained together to form complete comprehensive solutions Each script is built via the Siamease Script builder and managed and controlled by the Siamease Script Manager Where a Siamease Task focuses on individual transactions Scripts focus on processes and building master data by applying several Tasks The complete methodology is monitored and controlled via Managers that allow visibility of Tasks and Scripts as well as providing a repository or workplace where scenario data and documentation can be linked to the Tasks at hand In a live environment the Managers provide users with the workplace where Tasks and Scripts can be executed and results stored and monitored 5 34 Chapter 4 SIAMEASE SCRIPTS OVERVIEW Using the Siamease Task builder and Task manager Tasks are created Each Task representing a specific business operation performed using a SAP transaction Script Manager extends Siamease functionality by allowing Tasks to be linked or chained together to process a business scenario Business Scenarios consists of several transactions that follow each other Scripting primarily allows data
13. 2 Data Migration MIGRATION 1 SD Sales and Distribution D C 500004 Fgrey Test sz 500005 Fgrey Test 2 lt Cj 005 000083 MB1C Z5D MB1C 001 ZMB1C 001 E 17 04 2001 19 56 41 Document 4990000317 posted E 17 04 2001 19 59 45 Document 4900000319 posted B 17 04 2001 19 59 47 Document 4900000319 posted E 17 04 2001 20 00 52 Document 4900000320 posted E 17 04 2001 20 01 18 Document 4900000321 posted B 23 04 2001 03 16 57 Document 4900000322 posted ZOLI Prototyping PROTOTYPIN 1 SD Sales and Distribution gt C 500000 standard order sz CJ 500001 Standard Order Processing gt 005 000005 MEZI ZPT_ME21_D05 2010 000017 YAN3 ZPT vAO3 O02 b gt 4015 000001 vant ZPT_V A01_001 gt 4 500002 Standard Order Processing gt LI 500003 Standard Order Processing 27 34 CREATING AND CHANGING SCRIPTS CREATING NEW SCRIPTS gi Create Press the create button to execute the Siamease Script Builder refer to Script builder for more information CHANGING EXISTING SCRIPT Select a script to be maintained by expanding the tree and single clicking on the script line Press the change detail icon in the application toolbar Siamease will execute the Script Builder and recall the script details SIAMEASE SCRIPT BUILDER s2 L Data Migration MIGRATION 2 MM Materials Management sz LI 500006 Fgrey Test 3 gt 005 000075 MB1C ZMM MB1C 001 gt 010 000017 VA03 zPT_VAB3_002 gt
14. 5 34 It is possible for a step to be repeated and for it to process multiple lines of data In this case both variables would be changing These counters reset for each step and run item OUTBOUND RULES A The outbound rules are specified in the script builder Scroll the step table right to view the rule fields The outbound rules determine what data is to be saved after a transaction is posted into SAP This allows subsequent steps to utilise that data to continue the business process Each step has 6 rule fields that are configurable The reason for storing results would be to either report the results of a data load or to use the results later in the script Xref Rule O02 34N1 a O03 sAN1 5Y MSGY2 RESULTS TABLE After Siamease posts a transaction into SAP it interprets the steps rules and stores the result using the current script variables Saved data is stored in a matrix or table called RESULTS which is then available as a data source in subsequent steps The RESULTS table is available at the end of the script run for interrogation and can be exported to ExcelTM with a single button click Note that the results table is only available as a data source from within a script Results however can be saved after a run Results are stored in table ZCSRESULTS and can be referenced by a task In this case the task must be defined upfront to access the SAP table ZCSRESULTS when generating the task 16 34 OUTBOUND VARIANT COM
15. ACHMENT PATH Each script has a default path from which each attachment can be referenced The script builder will take the path of the first attachment as the default script path All other attachments are then compared to the first to determine if the same path is used If so then only the relative position to the script path is stored The default script path is visible and can be captured manually in the PATH field on the bottom of the script builder detail screen S http www sy datum com testsd txt itestsd2 txt In the example above the second step has an attachment that refers to C My Documents testsd2 txt 12 34 ADDING MEMO TEXT Scripts are rerun over time The Memo text allows empirical data to be stored alongside the script The Memo text can even store scenario data that can be copied into the clipboard and imported into the scenario Z weme To add memo text press the MEMO icon on the application toolbar Change Script Header 500012 Siamease Script Builder Language EN ROR Ge Formats e Character formats EB A lt E Paragraph left aligned a IPS and HINTS 1 Don t forget to switch PC screen resolution to 800x600 for overhead projection 2 Examples CD is kept in secretaries bottom draw AQ How do I reclaim VAT on wear and tear on ASSETS another time another place 13 34 Chapter 6 SCRIPT RULES Scripts contain rules that determine what data is required for subseq
16. JO saldoo z J days Bulouaiajas ayi fig payeaso sp103al z alam asau souls sins3y 3J4nos Z000000 i 9 Saj Ul paloys Uulrijoo ANdui 1514 ayi av T Squawayou Bul ann Wall d31S 43iNnoJ sinsqy TT de15 ul paye ayo Siaquinu jeuayew aeudosdde ayi yia pal aq sny NA pue AN poy SUNses IS ayy o siaa UIE H HSSIINN Tell vin TE as WHS NOUNBIYLSIO Z que yen ENUEW vi anjen papoopiey 1000 540 5314S l EE jenuew ayi GUISN pajeayo aje Spy0JaJ dul om days aoual yaj ayi fiq pajealo alam sp109al z sous sins3y 32408 zoo TOO TetIsiey 1sa Dd c TOU TOQ TertzaieN 158 Jd 1000000 sawau Way ann Wall dais 43iNnoJ sinsa3y SIQEUEA j JYI Ul JEEE osu EYI pue Jaqurioo W31 941 awau uone a l PELE l9 S EUa l NOLLJadjH353I30 l yenen jenuew vi anjen papoopsey Jd aaa painoak sI days SIY TANTA 26 34 Chapter 7 SIAMEASE SCRIPT MANAGER OVERVIEW The Script manager provides control over Siamease scripts Providing functionality to build execute and maintain scripts The Siamease Script Manager behaves in a similar fashion to the Siamease Task Manager As with task Scripts are classified according to projects and applications not sub application To execute the script manager press the icon available on all Siamease screens or execute transaction code ZESB aI 6 GHEE 200i AF eB SIAMEASE Script Manager g Create YZ SQ Execute E View Results mm fa 8 9
17. MANDS The objective of the outbound variant commands is to determine what document or object number has just been created SAP usually sets a system variable or a Parameter ID to the value of the document or object that has just been created The Outbound variant commanas allow access to either of the two and are discussed in detail below Yo Refers to a Parameter ID Inbound input data after conversions can be stored along with new result data A System variable or any other runtime variable PARAMETER ID pid Most key fields within SAP have a parameter id assigned to them This parameter id stores the last document or number that was used or created to assist users and programs with the process flow If a customer was created the user will see the customer number filled in if they went to the change customer transaction Parameter IDs can be found by requesting help and technical details on a particular input field Usually in the form of a 3 character code Siamease allows this parameter id to be used as input by prefixing the PID with a If a task were to create a single material and the next task required that material number as input the second task would have a variant that specified MAT as the value of the material number A PID will usually only be used and defined on a Change transaction SYSTEM VARIABLES SY FIELDNAME System variables are set by the system at runtime It is SAP s way of keeping track of what is happening
18. added by add PI SY or FM By default these options are switched off when processing spreadsheets due to performance issues when no formulae is being utilised VARIANT FORMULA Formulae are coded in program ZCSEZEFM To access this program execute the task builder zeze ka Maintain variant Formulae select the INCLUDE code tab and press the button The example below is a typical formula e Value field is used to pass a value to the formula and to send a value back to the screen field e Return code is used to identify errors If the formula were to detect an error i e master data already exists then a return code of 8 would abort the load of that particular row of data 2 FORMULA NWEEK The purpose of this form is to return next weeks date form NWEEK changing valuefield returncode data nextweek like sy datum clear returncode nextweek sy datum 7 write nextweek to valuefield endform Please note that program ZCSEZEFM must be transported to the live environment after any changes 24 34 LINKING SCRIPTS It may make business sense to separate certain data loads into different scripts Although the results source is only available during the execution of a script specific results can however be saved permanently and referenced to by other scripts at a later stage To save results data the specific step to be saved must have a SAVE name specified on the script This data is then accessible to o
19. ly achieved within the budgeted time frame The downfall however is that in many cases the project hopes that everything will work because the budgeted time frame usually does not cater for time spent on reengineering a business process The Siamease scripting tool allows business processes to be documented and implemented Once defined completely and correctly integration testing can be done as simply as running a series of scripts Any script that fails clearly identifies where the process has changed and where most of the time and effort must be applied This results in more time spend on problem solving and allows more processes to be tested within the budgeted time frame These tests can also be performed on a routine basis without any additional cost implication Results of previous tests can be compared against current tests and deviations can be detected and addressed STRESS TESTING Stress testing is usually done manually or estimated based on the stress created during data migration This often skews results due to the type of transaction posted but more than anything else is usually the Basis teams responsibility Effective stress testing should be done with comprehensive business processes that simulate the real working environment Using the Siamese Scripting tool scripts can be defined that replicate real business processes Scripting allows input data to be generated and allows data to flow from one transaction to another Scripts defi
20. ned for data migration and or defining training clients can be reused to process a sequence of transactions Each script however can be run as many as 1000 times Many different scripts can be run simultaneously and together a live working environment can be simulated Buffers can be tested queues monitored and testing can continue until the Basis Team are happy that instance and client parameters are set accurately END OF DOCUMENT 34 34
21. r scripts bip A task imported from the task manager v Asset Create 9 34 ADDING AND REMOVING TASKS Adding a task creates a unique step number Enter the desired task number into the task column to create a new step Click on the icon next to the step number to insert a step between two steps Adding and removing steps can also achieved by pressing the and buttons on the bottom left of the script builder screen ENEN Import Tasks It is suggested to press the IMPORT Tasks button Siamease will then present all available Tasks for selection To select click on the relevant Task and press F9 or the select deselect icon on the bottom of the screen The selected task will be highlighted in yellow Sianeas2 Repository a ata Kicrazior PIGRATION Mater als Nanagenett Benare ED NBIC Ozer Gode Rezeip Sales and I stributicn E rctozyging FROTITYPIN El rctozype d velopnert FT_DEVELOP 059003 HB31 HOT a Display sales Ircer 403 Cisplay Sales order TE Sales and D stributicn leygraind FT PAY Test Scrip Process TESTSCR IPT IG WA seldtiDaest E A X Once complete press the green tick icon to continue The selected tasks will be copied back to the script and presented as follows 10 34 O00131 Asset Create ai 083 v d00132 Asset Change 1 ealLOOPTEST re e Step numbers can be manipulated to allow tasks
22. re logged and will appear in the Script managers results log e For stress testing switch save results to database off save runtime timing on and display run results on Run parameters Show each individial task Save results to database Save Runtime Timing Display run results log 30 34 VIEW RUN RESULTS View Results Click on a script run result header yellow line and press the results icon The results are displayed in a tabular format The Script results log has functionality to create a spreadsheet or mail merge with results data Select the appropriate function from the application toolbar el aho ese DAME anan AA om SIAMEASE Script Manager PO BajFGREY s mjo ssoooost cT 31 34 32 34 Chapter 8 APPENDIX A CASE STUDIES THE TRAINING CLIENT A Typical SAP implementation requires a Sandpit client where newly trained users can practice transactions learnt during the training course The unfortunate reality is that this client will probably be filled with either the wrong data or with nothing at all Even trainers who have prepared a training class are faced with the daunting task of creating prerequisite data in a client before training can commence With skillful planning one training course can be planned before another so that the class has data created by the previous class to continue their business process training Unfortunately training teams usually
23. roblems that have been broken down to be built back to the complete cohesive level SIAMEASE Script Builder B Execute G view Results GY lt B Documentation 27 Memo B LIB 500015 5 PROTOTYPING Script Details CS ee ie o ann Asset Create Te 009 I B 0132 ase chang Sr oes bow esl CI ne onn n A a A m e na igh m mm 7 34 CREATE A SCRIPT e Execute transaction ZESB or select the script builder from any Siamease screen e Enter a Script description e Assign the script to a Functional Area or Application e Assign the script to a Project e Press the CREATE icon SIAMEASE Script Builder D 2 BA B Becu 00015 LIVE Asset Master Create and Change Seript Classification Application AM Asset Management Project PROTOTYPING Prototyping PROTOTYPING 8 34 STEPS A Task represents a business operation performed on a SAP transaction Tasks added into a script are known as STEPS Steps influence the data that is to be used in that operation as well as the sequence of events within a business process Each step has rules defined to determine what data is passed to a task and what data is stored as a result of a task Each step is numbered and can have data or documentation attached to it in the form of an attachment for later reference A Step can be Git A comment used to document the process E A reference script that executes othe
24. rted from the windows clipboard MEMORY data is received from another ABAP program interfacing In addition to this Scripting introduces another data source RESULTS data created by previous steps is made available in the form of 6 variables Data Source Data Source RESULTS Data file HOW MANY RECORDS TO PROCESS The MANUAL data source will only process one input record per Step iteration The script can however repeat a step a number of times and thus create volume data In each case the ITEM counter will increment and the LINE counter will reset to one on each call The RESULTS data source will refer to the last step that was executed and determine the number of records created by that It will then copy the Manual Parameters input values for each result record Each will then be processed individually From this point on the task will behave as if it had uploaded a number of rows of data to be processed The script counters will therefore increment the LINE counter whilst the ITEM counter remains constant Since the script variables are incrementing the manual parameter values can also vary provided that the INBOUND VARIANT COMMANDS are used see below By default a step will refer to the result data created in the previous step Other step results can be referenced either through inbound variant commands or by specifying the reference step or item on the Steps Inbound rules S Ref Step Item
25. ther scripts that specify a read name in the inbound rules section of the script When data is referenced via a save name the results are loaded into Step 000 for access This data is then available to all steps that refer to RESULTS as the data source or those steps that utilise variant commands with the VE include option If a step does not want to refer to step 000 when a read name has been specified then a reference step should be supplied to overrule the step determination Use table maintenance sm30 on table zcsresults to delete or maintain results data created in error Please note that if multiple scripts use the same save name then resultant data is appended to the results table i e one scripts results do not replace another E g Local customers loaded in one script in several steps foreign customers loaded in another script Each script can save the old and new customer number into the results table under the SAVE name CUSTOMERS Another script can then reference ALL customers loaded by specifying CUSTOMERS as the read name Note that if a READ name is specified then RESULTS does not have to be the data source Data can however be referenced using the commands 25 34 SCRIPT RULE SUMMARY 6000000T 8000000T sivawayou aul NTa ann WALI dais YH3LNNOD 11nssauy de Ul paleala S EUSIEW SSWES ayi 0 YEG Jayaj VIEDE 39U0 UES Hadir Tvi93lviw l que yen jenuew Ul anjen papoopsey 0z IN 1d li pajeayo suenen enyew ayy
26. to be reordered Change the value of Step press Enter and Siamease will reorder the tasks accordingly e The status checkbox indicates whether this task will run if the script is executed e Task details are e All steps should run with a variant unless all selection screens are made visible during the execution e Documentation or data can be attached to each step via the attachment icon P REPEATING STEPS A step can be executed more than once as well as the overall script being executed more than once Referring to the REPEAT column above this value will execute step 3 4 times Each iteration increments counter variables Each time a step is repeated it increments the ITEM counter amp I All results from each step are also separated by this variable Refer to Script Variables for more details NAVIGATION These buttons simply allow the user to move to the appropriate columns in the script for easier navigation around the script l4 TaskDtis gt Inbound gt gt Outbound bl Attachments 11 34 ADDING ATTACHMENTS Each step can have an attachment linked to it This allows documentation presentation material or scenario data to be linked to a specific task 2 If a step has no attachment then a paper clip icon will appear on the step line Press this icon to add a hyperlink to the document in question File name Press F4 to find the attachment using the normal windows file explorer DEFAULT ATT
27. uent processing thus allowing a script to prepare data at runtime to be used for subsequent steps Since each Task can load data into SAP from different data sources e g clipboard manual memory etc the script step must specify the source of data when the step runs This is done by creating a variant on the task to be executed Each step has inbound and outbound rules 3 separate results created RULE RESULTS TEY STEP ITEM LINE RULE RESULTS 001 001 001 XXX 001 001 002 yyy 001 001 003 ZZZ Scripting provides a set of variables counter which are used by the inbound and outbound rules enhanced variant commands that extend SAP functionality to define inbound rules outbound rules that allows specific data created by the task to be saved for later use dynamic table lookups to assist with data migration and helps to tie legacy data to SAP data To define scripting rules script variables will be explained and then the concept of the outbound rules will be explained leading into the inbound rules Scripting also assumes that the user is familiar with the Task and its capabilities 14 34 SCRIPT VARIABLES Scripting introduces 4 variables that are automatically incremented when a script is executed These variables are used to store results and to change field values at runtime VARIABLES e C COUNTER is incremented for each iteration of a complete script e S STEP the current step that is being run e ITEM
28. ustomer Name 999001001 Manual Parameters Asset Serial number SERIAL I 21 34 RESULTS INPUT 1 6 n C counter S step l item L line Results Input is the key for linking steps together The command allows the result of a previous step to be captured into an input field on the next step Each step has an outbound rule that determines how the results table will be populated There are 6 rules that determine 6 results fields The command has access to these 6 results fields within the results table By default the results of the previous step are referenced This can be overridden by specifying a reference step against the step This allows step 2 and 3 to refer to the results created in step 1 If a particular field needs to deviate further then it can reference the results table right down to the individual line in the results table If a step is processing multiple records then the command will use the current row offset in the step to determine the results record unless otherwise instructed A script may be setup to create a few materials a few customers and then create sales orders using these same customers and materials There are 3 tasks one to create customers one for materials and one for sales orders The customer and material numbers are not known until they are created The script would define outbound rules to ensure that the customer and material numbers were saved into the results table The
Download Pdf Manuals
Related Search