Messages


Cursor field XXXXXX does not exist in the screen
Description	This message is displayed in Log column of the Excel worksheet after you run the script file.
Reason	This error occurs when TRANSACTION attempts to place the cursor in a field that does not exist on a given screen.
Response	Use this procedure to resolve this problem: On the Mapper, uncheck the Hide system fields (BDC_CURSOR AND BDC_OKCODE) setting to allow the cursor fields to be displayed. Find the BDC_CURSOR field. It is set to the field that is causing the error. You can then either disable that BDC_CURSOR row or set it to another field that is always present.


ERROR_CNTL????? Exception condition "Error" raised
Description	This message is shown in the Excel Log column or Access Log field after you run the script file.
Reason	The reason for this error is not completely known, but may result from the script file using local system resources.
Response	Use the Launch GUI setting on the Run screen and re-run the script file. (Re-recording is not required).


Evaluate button is disabled
Description	This message is displayed when you download the Trial version of TRANSACTION and attempt to start the program.
Reason	This error occurs when the Trial version of TRANSACTION is installed on the computer for the second time. Since the software has already been evaluated on that computer, it cannot be evaluated again.
Response	Contact the Winshuttle Support Team at support@winshuttle.com to request an Evaluation extension key for the Trial version.


Function Code cannot be found
Description	This message is displayed when the Function Code cannot be found.
Reason	This error occurs for a number of reasons: User is running an old script file on a new system. The transaction in question has changed in SAP. User is running an old script file on a new system.
Response	Choose one of these possible solutions: Re-record the script file. Record and run the script file in the same mode — Batch Input Mode or Non-Batch Input Mode. If you encounter this error while trying to save a report to a local file, use the Mapper and uncheck the Hide system fields (BDC_CURSOR AND BDC_OKCODE) setting to allow the cursor fields to be displayed. See "Expert Tab: Filter Settings" for more information. Alternatively, you can try replacing =%PC with =&PC or =PC.


Log error messages in my Excel worksheet are different from the ones I get in SAP
Description	When running the script file, the error messages logged in the Excel worksheet are different from the those provided by SAP.
Reason	This error occurs when the transaction is recorded and run in Batch Input Mode, which uses a set of messages that differ from the messages used during Non-Batch Input Mode in SAP.
Response	Record the transaction in Non-Batch Input Mode. See "Recording Modes" for more information.


Log error messages in my Excel worksheet are different from the ones I get in SAP
Description	Log error messages in my Excel worksheet are different from the ones I get in SAP
Reason	This error occurs when the transaction is recorded and run in Batch Input Mode, which uses a set of messages that differ from the messages used during Non-Batch Input Mode in SAP.
Response	Record the transaction in Non-Batch Input Mode. See "Recording mode" for more information.


Long text fields are not getting captured
Description	When recording a transaction to upload long text, the Long Text field is not captured.
Reason	This problem occurs in some transactions where SAP opens a free text editor for any long text to be entered. Information entered in the editor is not captured by TRANSACTION.
Response	Use Batch Input Mode to capture the Long Text fields. See Recording long text in the "Advanced looping capability" for more information.


MC86 - Entering Capacity information - cannot scroll down to the next page of the table
Description	This message is displayed when there is a SAP program error.
Reason	This is actually a SAP program error, which was corrected in SAP. See SAP Note 117420: "Symptom - The PgUp and PgDn keys don't work in the Planning Table. Additional Key Words - MC93, MC94, MC95, SOP, MC86. Solution".
Response	Change the source code as indicated in SAP Note 117420. Request this modification from your Basis staff. When this change is made, you can then use TRANSACTION to perform this transaction.


ME21N - Cannot find a New Line or Insert Line button or a menu item for multi-line recording
Description	When recording the ME21N transaction, a method to increment the row cannot be found.
Reason	This error typically occurs because new line functionality is simply not available in the ME21N transaction. In order to record line items in multi-line transactions, there must be a way to capture the row increment. This is generally done by using the New Row button (or alternates).
Response	Filter by line number by requesting line 999 and then always use the first empty line available to enter line item data.


Must have at least one field mapped to an Excel Upload
Description	This message is displayed when you download data from SAP using the Read From SAP setting.
Reason	This error occurs because you must upload at least one field from the Excel worksheet in order to download data from SAP.
Response	Map one field to be uploaded from the Excel worksheet into SAP to allow the data to be downloaded from SAP. If you want to only download the data from a given table, you can use Winshuttle tableSHUTTLE as an alternative.


No batch input data for screen XXXXXX
Description	When you run a script file, this error is shown in the Excel Log column or Access Log field.
Reason	This error can occurs in TRANSACTION for several reasons: Erroneous recording of the script file. Encounters an unexpected field during the execution of the script file. Encounters an unexpected screen that either does not have an OKCode or has an incorrect OKCode
Response	Choose one of these suggested solutions: Use the Run Step-by-Step (Stop on Errors Only) Run option on the Run screen to determine which field or screen is causing the error. Re-record the TRANSACTION script with the least possible redundant actions while recording. Re-record the TRANSACTION script in Non-Batch Input Mode. See "Enter the Recording Properties" for more information.


No batch input data for screen XXXXXX
Description	When you run a script file, this error is shown in the Excel Log column or Access Log field.
Reason	For the CO and FI transactions, this error typically occurs because an SAP dialog box is used to enter certain fields only the first time the transaction is executed, and SAP retains this information for subsequent access to the transaction. For example, this issue occurs when an SAP dialog box is used to enter information such as the Controlling Area and Company Code. In this case, TRANSACTION performs correctly on the first entry and then returns this message for all the other entries.
Response	Use the Mapper and set the Start Row, End Row, and IF first transaction setting on the Conditional Run options on the script file to run these transactions. See "Expert Tab: Conditional Run" for more information.


Program terminated by User Protocol error when communicating with SAP GUI TRANSACTION terminated by User
Description	When you run a script file, this message is displayed in the Log column of the Excel worksheet or Log field of the Access database. (The transaction might run successfully in troubleshooting mode, but not in the normal run mode.).
Reason	This error occurs when TRANSACTION requires SAP GUI to be launched for certain types of transactions such as file input/output dialog boxes, report generation, and uploading files (images, PDF).
Response	On the Run screen, mark the Launch GUI check box to run the transaction.


Read From SAP feature is not working
Description	This error occurs when you attempt to use the script file to download data using Read From SAP.
Reason	This error occurs when a transaction is recorded in Batch Input Mode and does not perform the intended Read From SAP function.
Response	Record the transaction in Non-Batch Input Mode. See "Recording Modes" for more information.


RFC subsystem not initialized
Description	This message is displayed when you select the SAP system for logon, get this message, and TRANSACTION aborts
Reason	When connecting to SAP, an unusual SAP logon screen is displayed. This error occurs when the SAPlogon.ini file has a different format as compared to the older version of SAP. (See SAP GUI 6.20 patch 36).
Response	Build a new SAPlogon.ini file with the new version of SAP GUI installed. If you cannot change SAPlogon.ini file, change the system by using the Server tab on the SAP Shuttle Logon dialog box. See "SAP SHUTTLE Logon" for more information.


SAP data type not supported
Description	This message is displayed when you record or run a script file.
Reason	This error occurs when the SAP function control (wdtfuncs.ocx) version and SAP R/3 version have inconsistencies.
Response	Contact the Winshuttle Support Team at support@winshuttle.com for assistance. Follow the steps outlined by the Winshuttle Support Team and use the Winshuttle-supplied .ocx file.


TRANSACTION behaves differently when run manually than when run through TRANSACTION
Description	This message is displayed when you run the transaction manually, move back to the first screen, and press Save to complete the transaction. When you use TRANSACTION to record the same transaction again, its behavior is different. The Back Arrow button does not follow the same screen sequence.
Reason	This error occurs when TRANSACTION allows users to record and run transactions in either Batch Input Mode or Non-Batch Input Mode. In Batch Input Mode, the actual screens and the flow of the screens might differ from those shown in Non-Batch Input Mode.
Response	Record the transaction in Non-Batch Input Mode. See Recording Modes for more information.


A ‘Fill in all required fields’ error message appears in SAP GUI at the start of a recording
Description	This message is displayed in the SAP GUI when you select the recording properties in TRANSACTION and launch the SAP GUI.
Reason	This error usually happens when the SAP GUI window is not set to Maximum size and has just been changed before the logon.
Response	Open Appotions.xml file from App data folder. Change the values of DEFSIZE to "X" and NOBIEND to " "(Blank)