advertisement
TRANSACTION Script Command Reference
+BI0
Runs the transaction in Non-Batch Input mode. This is similar to running the transaction in GUI.
See Recording Modes for more information.
+DBnnnnnn (Delay before SAP log on)
Optional command.
This command delays the log on to SAP by nnnnnn milliseconds. Use this command to maintain the delay between various TRANSACTION sessions such as when the Scheduler cannot schedule sessions less than one minute apart, and sessions must be launched within that time frame. See
Scheduling runs for more information.
This TRANSACTION script command can be passed from the command line as a parameter. If this is done, the command line parameters take precedence over the values specified in the
TRANSACTION Scripts.
+DLnnnnnn (Delay between transaction run)
Optional command.
This command delays the calls to SAP between transactions by nnnnnn milliseconds. This command can be used to slow down the processing of the TRANSACTION scripts.
+Do-While Loop
Optional command.
This command provides a Do...While Loop mechanism for processing multiline transactions.
TRANSACTION enters the Do...While Loop when the specified condition is met. Normally, this condition is determined dynamically. Fixed value <Check value> is compared against the value in the Excel column as indicated by <Excel identifier column id>.
Recommendation: Use the Mapper to manage your Do-While Loop and avoid manual changes.
Example 1:
97
Winshuttle TRANSACTION Advanced User Guide
+Do While <A:Excel record type identifier column ID>,<H:Header identifier string>,<L:Line Item identifier string>
...
*Fv!<Excel column id>
......
@Fv!<Excel column id>
...
+Fv<Fixed Value>
...
*Fv!<Excel column id>
...
+Fv<Fixed Vale>
...
+LOOP
Example 2:
This example shows that column A in Excel has item records for looping as identified with character D in that column. TRANSACTION loops through all of the rows in Excel spreadsheet, while the value of column A for that row is filled with D.
+DO WHILE A,H,L
'Start Do While loop from next line, Row Identifier is stored in Excel column A, value of "H" indicates Header row while value of "L" indicates line item row
'----------------------------------------------------------------------------
+SpSAPMF05A
+Sn1200
-SpMain Screen for Single-Screen Transaction: Outgoing Invoice
+FnBDC_OKCODE
?
-FnOK Code for this screen
+Fv=0005
+FnACGL_ITEM-HKONT(01)
-FnGeneral ledger account
@Fv!C
98
TRANSACTION Script Command Reference
+FnACGL_ITEM-WRBTR(01)
-FnAmount in document currency
@Fv!F
+FnACGL_ITEM-MWSKZ(01)
-FnTax
@Fv!G
+FnACGL_ITEM-MARKSP(01)
+FvX
+LOOP
'End do while loop here..
'----------------------------------------------------------------------------
+SpSAPMF05A
+Sn1200
-SpMain Screen for Single-Screen Transaction: Outgoing Invoice
+FnBDC_OKCODE
-FnOK Code for this screen
+Fv=BU
'----------------------------------------------------------------------------
Key Points:
There must be separate Header and Line Item (detail) rows in Excel. There can be only one
Header record, followed by one or more line item records.
Header and Line Item records should be clearly marked in the identifier Excel column.
TRANSACTION ignores the case, while validating the Excel identifier value for Header or Line Item rows. Also, the loop row cannot contain data for Header. However, Header information can be used in each Line Item.
TRANSACTION starts building the transaction from the row identified as a Header. If a value other than H or D is encountered, TRANSACTION skips all rows until it finds the next Header row.
Do not leave an empty row between Line Item records.
While using the Do...While Loop, avoid making unnecessary key fields. (Skip the transaction if empty or *FV#<Column ID>). TRANSACTION uses the row type identifier column as the key column. If this column is left blank in any of the rows, TRANSACTION ignores the entire row and continue to the next record.
Key field (skip row, if value in Excel is empty for the field) has priority over Header/Line Item row types during the Do...While Loop. In other words, TRANSACTION first checks whether the row is selectable based on the key field settings. Then it performs validation based on the row type for
Do...While Loop processing. If the row is skipped due to key field validation, it is not used as part of Do...While Loop processing.
NOTE: Do not mark any of the fields used inside the Do-While Loop as a key field. If any of the fields inside the Do...While Loop is marked as a key field, there can be unexpected results.
If you want to use incremental Excel rows, use identifier @ instead of + or * while inside the
Do...While loop. The chart below shows which row in Excel is used to retrieve the data.
TRANSACTION script element falling between
Do- While Loop statement
Read from
99
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
advertisement
Table of contents
- 11 New Features in version
- 13 Winshuttle Customer Support
- 13 Finding out which build you are using
- 14 Contacting Customer Support
- 14 Winshuttle Community
- 14 Using the Customer Center
- 15 Auto logon
- 15 Auto logon details
- 16 Auto update
- 16 Application defaults
- 16 Path defaults
- 17 Microsoft Excel defaults
- 17 Data read preferences
- 17 Usage defaults
- 18 SAP defaults
- 19 Error management and trace files
- 19 Default indicators for errors in messages
- 19 Trace
- 20 Client Connection Settings
- 20 Proxy settings for Connect
- 21 Restore defaults
- 21 Enable GUI scripting
- 21 Enabling Scripting on the Server Side
- 21 Method
- 22 Enabling Scripting in your SAP client GUI
- 23 SAP GUI
- 24 Production versus non-production servers
- 24 Unicode implementation for TRANSACTION scripts
- 26 Winshuttle Function Module for TRANSACTION
- 26 What caused this problem?
- 27 What is the significance of eCATT in this context?
- 27 How is Winshuttle Addressing this problem?
- 29 Production Server Warning (Prod. Svr. Warning)
- 29 Using SSO and EP logon
- 29 Locating 64-bit SSO libraries on the computer
- 30 How to configure Winshuttle 64-bit product to work with SSO
- 30 EP Logon
- 30 Using EP logon
- 32 Recording modes
- 32 Batch Input Mode
- 33 Non-Batch Input Mode
- 33 GUI Scripting
- 33 Properties
- 34 Using templates in TRANSACTION
- 35 Recording long text
- 36 Backing up data and files in Winshuttle
- 36 Backing up the recording
- 36 Backing up SAP data
- 37 Preserving log files before uninstalling TRANSACTION
- 39 Editing in the Mapper
- 40 Cell-based mapping and column-based mapping
- 40 Filtering mapper setting
- 41 Advanced looping capability
- 41 Handling multiline transactions
- 42 Do...While Loop
- 43 Mapping nested loops
- 43 Preparing your workbook for indented data
- 43 Loop data for column-based mapping
- 45 Easily check loops
- 45 Copying and cutting rows with loops and conditions
- 45 Loop data on multiple sheets
- 45 Invalid mapping
- 46 New sheets and single sheet mapping
- 46 Loops and changing from cell-based mapping to column-based mapping
- 46 Using the Do...While Loop Feature with Access
- 48 Using Multiple and Nested Loops
- 48 Recording and Mapping Long Text
- 49 Setting conditions
- 49 Adding Conditional Run statements
- 51 Adding notes
- 51 Validating data
- 52 Validation on loops
- 52 Validating for cell-based mapping
- 52 Validating linked scripts
- 52 Validate in the Run pane
- 53 Validate by list
- 54 Undo and Undo All
- 54 Undo mapping
- 54 Undo All
- 54 Update mapping
- 54 Undo on multisheet mapping
- 54 Mapping long text
- 55 Compensating for missing SAP screens and fields
- 56 Skip Transaction if Empty
- 57 Editing a TRANSACTION script
- 57 Auto mapping
- 58 Auto mapping from the three-panel screen
- 59 Auto Mapping from the Mapper
- 59 Auto Mapping for cell-based items
- 59 Downloading from SAP
- 61 Approving and rejecting files
- 61 Submitting a file for approval
- 61 Step 1. Complete script file information
- 61 Files with a production status
- 61 Files with non-production status or another file creator
- 61 Multiple script files
- 62 Linked script files
- 62 Step 2. Complete data template information
- 62 Step 3. Complete supporting documents information
- 62 Summary: Submit
- 62 Assigning a data review process and a reviewer
- 63 Revising multiple and linked scripts that are in production
- 63 Autopost
- 64 Why wasn't a task created?
- 64 Approving, rejecting, and reassigning .TXR files
- 64 Submitting a file that has been rejected and then updated
- 64 Approving and rejecting files
- 65 Reassigning files
- 65 Running scripts
- 65 Approving, rejecting, and reassigning data files
- 66 Submitting a file that has been rejected and then updated
- 66 Reviewing and running files when the review process is marked "No data review
- 66 Supporting documents
- 66 Working files from within Excel
- 66 Submitting a file for approval
- 67 Approving, rejecting, or reassigning a file in Excel
- 67 Running a file in Excel
- 67 Completed files
- 68 Other features in RUNNER for Excel
- 68 Working with CENTRAL
- 68 Synchronize logs to CENTRAL
- 69 Changing a server for the TRANSACTION client
- 69 Signing in with a different user name
- 69 Viewing the user profile
- 71 Running multiple or linked files
- 71 Approval process and linked scripts
- 71 Validating linked scripts
- 72 Revising multiple or linked files that are in production
- 72 Scheduling runs
- 74 Run Later on SERVER
- 75 Using the Scheduler
- 75 Run options and troubleshooting errors
- 76 Key considerations for using the Step-By-Step Run Options
- 76 Advanced run settings
- 78 Writing headers
- 78 Write headers in cell-based mapping
- 79 Approval processes and writing headers
- 79 Reviewing transaction history
- 80 ROI chart
- 81 Uploading long text
- 81 Windows scripting
- 83 Winshuttle DIRECT
- 84 A1 Dataloader
- 87 Publishing a TRANSACTION script as a web service
- 88 Publishing a script as a web service
- 89 Testing
- 89 Validate form data
- 90 Running forms
- 90 Posting data
- 90 Using TRANSACTION with Virsa Firefighter
- 90 Recording the transaction
- 90 Running the transaction
- 93 TRANSACTION Script Command Reference
- 94 #F1InputExcelFileName
- 94 #L1LogColumn
- 94 #NTNext linked
- 96 #S1SheetName
- 96 #XS{ 0 | nnnnn | End } , [CLOSE]
- 97 *Fv!FieldValue (read value from the spreadsheet column)
-
97
*Fv?
- 98 +ALautologin file.ALF
- 99 +DBnnnnnn (Delay before SAP log on)
- 99 +DLnnnnnn (Delay between transaction run)
- 99 +Do-While Loop
- 102 +EL[!ExtendedLogColumn]
- 103 &EndSession
- 103 +FvFieldValue (Fixed)
- 103 +HTHeader Text
- 104 +IF!Condition
- 105 +MTMsgID-MsgNo
- 105 +NE[encrypted password]
- 106 +RS (Global Read SAP option)
- 106 +SAnnn: StopAfter Transaction nnn
- 108 +SnScreenNumber
- 108 +SpScreenProgramName
- 108 +SRStartFromRow
- 108 +TxSAPR/3TransactionCode
- 109 TRANSACTION and the command line
- 111 Cursor field XXXXXX does not exist in the screen
- 111 ERROR_CNTL????? Exception condition "Error" raised
- 111 Evaluate button is disabled
- 112 Function Code cannot be found
- 112 Log error messages in my Excel worksheet are different from the ones I get in SAP
- 113 Long text fields are not getting captured
- 114 Must have at least one field mapped to an Excel Upload
- 114 No batch input data for screen XXXXXX
- 115 Program terminated by User
- 115 Protocol error when communicating with SAP GUI
- 115 TRANSACTION terminated by User
- 115 Read From SAP feature is not working
- 116 RFC subsystem not initialized
- 116 SAP data type not supported
- 116 TRANSACTION
- 119 Use Transaction to extract from SAP
- 119 Can I toggle between batch and non-batch modes while running a script?
- 119 Double-clicking in the Mapper is not making the field editable. What can I do?
- 119 After mapping, can I go back to my original recording?
- 119 Commit code caution
- 120 I submitted my script for approval: why wasn't a task created?
- 120 How can I learn what version of TRANSACTION a script was built with?