WFM Features

Version-12.1

Table of Contents

WFM New Features in 12.0 over 10.x .................................................................................................... 1

Enhancements ......................................................................................... Error! Bookmark not defined.
Transaction Specific Improvements ...................................................................................................... 3
A. Attachment ..................................................................................................................................... 3
B. Validation ........................................................................................................................................ 4
C. Skip Screen - Transaction skip screen improvement ...................................................................... 5
D. Long Text- Long text improvements ............................................................................................... 5
E. WFM User Authority Roles ............................................................................................................. 6
F. Message Improvement in Transaction Run .................................................................................... 6
G. PR Number in ME51N logs .............................................................................................................. 6
Query Specific Improvements ................................................................................................................ 7
Direct Specific Improvements ................................................................................................................ 7
A. Wrapper FMs- Remote Wrapper WFM for Standard FMs .............................................................. 7
B. Utility WFMs ................................................................................................................................... 8
C. Customer WFM - /WINSHTLQ/TRN_FUNC_CUSTOMER ............................................................... 8
D. Vendor WFM - /WINSHTLQ/TRN_VENDOR_BANK ......................................................................... 9
WFM Add-On Improvements ................................................................................................................. 9
Admin Panel Improvements .................................................................................................................. 9
Knowledge Based Articles (Support Articles/Help Document)

Document History
Contributor Reviewer Document Version Created On Last Updated
Rahul Gupta Gurpreet Sidhu 1.0 01-Apr-2019 01-Apr-2019
General Features with WFM 12.1
 Support for EHP8
 Support for S/4 HANA 1610
 Support for S/4 HANA 1709
 Support for S/4 HANA 1809
 Overall better performance in Record, Map and Run
 S4-HANA Specific issue with Material field length due to change in length to 40 characters is
supported now
 While getting the field length with Record WFM performance is improved
 Detailed SAP Traces
 Added Winshuttle Memory Management to avoid system runtime errors/short dumps during
large Query execution.
 Added Winshuttle Memory Management to avoid system runtime errors during Transaction Run
feature.
 Improvements for lists of values (LOVs) for custom fields specific to some FI Transactions
 Virtual forge SAP ABAP code profiler compliance for mandatory fixes
 Long text issues fixed on EHP7 and EHP8 for VA01 and VA02
 Ready-to-use authorization roles for WFM and Non-WFM
 New WFM installer that supports installation on Non-ERP APO/SRM and EWM systems for 70x-
731-740-750.
 Tables specific to S/4 HANA have been added to the Studio QUERY -Master Data Dictionary.
 F4 Help for BP transaction scripts- Since BP transaction used to have fields name on screen such
that , it does not show the F4 Help or Description for some of fields even after same is available
in SAP.
 Configuration Table for F4 and Description handling of BP transaction has been added in Admin
Panel page.
 SO10 Long Text can be maintained with new Wrapper FM /WINSHTLQ/TRN_CREATE_TEXT’.
 Issue “Call Back Server Null” or Error “C” has been fixed. This usually comes when there is a call
back routine in Customer’s SAP code.
 Transaction Specific Features

A. Attachment
The WFM supports 4 different document attachment options
1. BDS – Business Document Server (Attachment done via Transaction – OAER)

2. GOS-Archive- Generic Object Services (Available in sapgui menu as ‘Store Business

Document’)

3. GOS-Office - Generic Object Services (Available in sapgui menu as ‘Create Attachment’)

4. DMS – Document Management Services (Avalable in SAP GUI via T-codes CV01N, CV02N)

Leverages the already configured document attachment option on the sap server, available via SAPGUI
Default attachment option for WFM can be set in the WFM ADMIN CONSOLE PAGE per sap server.
 User feasibility to provide GOS Document Type (SAEOBJART) at script level, in Attachment type
GOS
 File attachment can now be performed for all Finance related Create transaction codes (e.g. FB50,
FB75, FBS1 etc.) and MM01/ML81/ML81N also along with change transactions.
 Attachment Support for CJ02
 DMS attachment to CV02N is now self-attached i.e. file is attached in the existing CV02N
document only (earlier it was creating a new document via CV01N), WIN-17936
 Customers can now define Storage Category for a DMS attachment in Winshuttle Admin Panel,
providing them feasibility to define external repository.
 Attached File Title and Creator name will be displayed in attachment list.

B. Validation

Transaction Simulation

Certain transactions in SAP provide a simulate or whole document check option (typically financial
documents)

 FB50, FB60, FB70, ME21N, ME22N, ME51N, VA01, VA02, PA30, PA40
 These supported T-codes have native validation check options at full document level
 These can be invoked as simulate and are processed via this WFM feature
 Simulate will return messages that would typically only appear at the attempted commit of the
data set
 Simulate feature has been extended further to t-codes FB01, FBD1 & FBS1.
 Relevant message is returned now where Simulate feature is not supported. This feature has been
identified only for t-code FBD1 as-of-now.

Transaction Validations

 Validation calls when processed via WFM reduced the calls and hence improve the performance
 The validations processes scripts with loops and without loops
 The entire data per document is sent in one go to the WFM from client
 The WFM returns a single consolidated message to the client
 Multiple Commit Codes handling has been done in WFM. We have made sure that data is not
saved to SAP in case more than one Save Ok-codes are present in mapper.
 Support of Validation/Simulation for more than 10,000-line items
 When Simulate is not available for FBD1, a relevant error message is returned.
 WFM now supports validation for PA30 and PA40 scripts even though they contain multiple
commit codes. For other transaction codes, data is not saved to SAP when more than one Save OK
code is present in the Mapper.

C. Skip Screen - Transaction skip screen improvement

 In a one call from client Skip Screen “if not found” functionality can be achieved through WFM,
Results Faster Execution.
 Debug with Skip Screen is now supported for all t-codes except PA30/PA40.
 Performance is improved when skip screen is selected inside loop its Available only with STUDIO
11.4.0, User can select the option in Mapper - script property -Skip screen in loop - > Skip Once
 Support added for “Read from SAP” functionality with skip screen

D. Long Text- Long text improvements

This is addition to normal/legacy way of recording long text and then updating.
WFM provides a stable way to add create and change long text fields – wherein available fields per
transaction can picked without recording, at the time of mapping Long text scripts are most prone to
issues and problems – WFM resolves this by using FM calls to sap server.

The supported tcodes via WFM are:

FB02 FD02 VA22

FB03 VD02 MM03
ME22N IW32 MM43
ME52N IW32 VA03
MM02 IE02 XD03
VA02 IL02 XK03
XD02 IP02 ME23N
XK02 AS02 ME53N
BP KS02 IW33
 FK02 ME12 ME33K
FK03 CV02N IW23
MK02 VA42 VF03
MK03 MM42 IE03
ME32K VA12 IL03
VD02 VA32 KS03
ME13 IP06 AS03
IP03 VD03 CV03N
FD03

Note –For display transaction scripts While executing, user must have authority for respective create
or change (e.g. MM01 or MM02 for MM03) transactions else he will get authorization error.

E. WFM User Authority Roles

Pre-Shipped ready to use authorization roles
Three authorization roles are shipped as part of WFM installer
These are ready to use for the roles of Admin, Author, Runner and sap users can be assigned to these.
 /WINSHTLQ/CMN_ADMIN_ROLE Winshuttle role for ADMIN
 /WINSHTLQ/CMN_AUTHOR_ROLE Winshuttle role for AUTHOR
 /WINSHTLQ/CMN_RUNNER_ROLE Winshuttle role for RUNNER

F. Message Improvement in Transaction Run

We improved the message when we get the message “No batch input for screen” comes. It now
mentions the screen title too.

G. PR Number in ME51N logs

Purchase Requisition Number addition update in Studio Logs after ME51N run
 Query Specific Improvements

 Removal of 65,536-character length limitation in Query

 Performance Improvement in Query Execution (compared to v11)
 Enabled WHERE criteria on Right Tables with Left Outer Join
 Support of Non-EAQT Query Having joins on different fields (Mismatch Joins)
 Added Winshuttle Memory Management to avoid system runtime errors during large Query
execution.
 Enabling Query Support with sap Logon Group based Load Balancing
 Performance Improvement in Query, if the where any criteria on text table language field
 Enhanced Trace along with host and active connections strings In Query.
 As a performance improvement, Enabling Query to get the most optimized table sequencing code.
 Ability to Identify Conversion Exit during Query Metadata Selection
 Enabled Sorted data downloading to Excel from SAP
 Execution of Query even when user provides input criteria values as per External Display format
(via Conversion Exits)
 Output of Query values in External Display format which is easy to understand for end user

Direct Specific Improvements

A. Wrapper FMs- Remote Wrapper WFM for Standard FMs

 /WINSHTLQ/BPAR_C_A_VAT_NUMBER – for - BPAR_C_A_VAT_NUMBER

Business Partner: Check Additional Data

 /WINSHTLQ/BANK_ACCOUNT_CHECK - for - BANK_ACCOUNT_CHECK

Check of Bank Account Number

 /WINSHTLQ/BUSINESS_NUMBER_CHEK - for - BUSINESS_NUMBER_CHECK

Check of international location number (ILN)

 /WINSHTLQ/BPAR_C_A_VAT_NUMBER - for- BPAR_C_A_VAT_NUMBER

Business Partner: Check Additional Data

 /WINSHTLQ/EU_TAX_NUMBER_CHECK - for- EU_TAX_NUMBER_CHECK

Check of VAT registration number (EU tax number)

 /WINSHTLQ/TAX_NUMBER_CHECK – for - TAX_NUMBER_CHECK

Check Tax Numbers

 /WINSHTLQ/POSTAL_CODE_CHECK -for - POSTAL_CODE_CHECK

Check of postal code and region

 /WINSHTLQ/RPC_CALCULATE_PRICES – for -BAPI_RPC_CALCULATE_PRICES

Request Calculations and Adjust Requested Calculations

 /WINSHTLQ/TRN_TAX_TXJCD_TABLE -for- TAX_TXJCD_DETERMINE_TABLE

TXJCD Determination

 /WINSHTLQ/SD_CUST_MAINTAIN_ALL -for- SD_CUSTOMER_MAINTAIN_ALL

Customer Master Update
 /WINSHTLQ/TRN_CREATE_TEXT -for- CREATE_TEXT
Create Long Text
 /WINSHTLQ/MATERIAL_GET_NEXT-for- MATERIAL_NUMBER_GET_NEXT
Functions for Material Number

B. Utility WFMs
 /WINSHTLQ/ACC_DOC_COPA_POST
1. Post or Park Account document with CO-PA fields.
2. It gives feasibility to give CO-PA values into Linear way instead of hierarchical
3. Remote Wrapper WFM for Standard FM - BAPI_ACC_DOCUMENT_POST
4. Perform Commit also for successful executions PARK/POST.

 /WINSHTLQ/POST_ACDOC_MULT_CURR
1. Post or Check Account document.
2. It gives feasibility to give Multiple Currency values into Linear way instead of hierarchical
3. Remote Wrapper WFM for Standard FM - BAPI_ACC_DOCUMENT_POST
4. Perform Commit also for successful execution POST.
5. If the posting is in Multiple Companies, the return message will have both document numbers.
6. Multiple currencies and extended to support
7. Tables for ACCOUNT RECEIVABLE, ACCOUNT PAYABLE and ACCOUNT TAX tables
8. Validation BAPI

 /WINSHTLQ/WFM_MAT_EXTEND -
1. Arrange multi liner messages per record in to single line for better readability
2. Remote Wrapper WFM for Standard FM - BAPI_MATERIAL_SAVEREPLICA
3. Perform Commit also for successful executions.

C. Customer WFM - /WINSHTLQ/TRN_FUNC_CUSTOMER

 Message improvement for /WINSHTLQ/TRN_FUNC_CUSTOMER WFM
 Support for S/4 HANA, Business Partner
1. Email ID insert or delete
2. IBAN Create, Delete and Modify
3. Tax Classification
4. Partner Function
 Handling of special cases for customer master such as "IBAN" bank data handling, maintaining
partner functions, Tax Classifications and adding email information.

D. Vendor WFM - /WINSHTLQ/TRN_VENDOR_BANK

 Handling of special cases for vendor master, such as "IBAN" bank data handling,
 Support for S/4 HANA, Business Partner
1. Confirming the existing bank
2. Add new Bank details to Vendor
3. Modify existing Bank details for Vendor
4. Deletion of existing Bank for Vendor

E. F4 Help for BAPI

Prior to 12.1 (Studio +WFM) there was no F4 help in Direct (BAPI) scripts which now available
wherever it is there in SAP.

WFM Add-On
 WFM Add-Ons are now De-Installable starting from 11.1.1 (Excluding SAP 4.7 and ECC5)
 WFM Add-Ons are now can be used during SAP Upgrade (SUM) for WFM upgrade starting from
11.3 (Excluding SAP 4.7 and ECC5)

Admin Panel
 Dedicated t-code /n/WINSHUTLQ/ADMPANEL for controlling all Winshuttle tables and tab pages
for query authorizations, WFM admin parameters, and other options
 Customers can now define Storage Category for a DMS attachment in Winshuttle Admin Panel,
providing them feasibility to define external repository
 Detailed SAP system trace can be generated
 Knowledge Base Articles

1) Accelerate Finance recorded scripts

1. First Suggestion for faster posting –

Go to FB50, enter Company Code

Enter dates and press enter to remove warning messages

Go to Environment and then Complex Posting

Enter Posting Key and GL account and then Press enter.

Enter New Comp- Code if want to record script for multi company posting
Enter Amount for Line 1.

Enter posting key and GL Account for next line and press enter again
Enter Amount for Line number 2.

And press save for posting the document.

This posts the document in lesser time.
2. Second Suggestion for further improving the posting time.
Click on Fast Data Entry
Enter values in each line up to 10 lines and then press enter.

Press enter again

Click on Fast Data Entry Again

Save and post document

2) WFM for 12.0.1 and 12.0.2

Information – Customer is installing or upgrading to Studio 12.0.1 or 12.0.2 and want to know
corresponding supported WFM version for the same.

Reason – WFM 12.0.2 is not available

Related JIRA – WIN-34362

Affected Products – Transaction/Query/Direct/Studio

Solution –

WFM 12.0.1 is to be used for both 12.0.1 and 12.0.2 Studio.

3) Finding Function Module Version

Description –
Occasionally, users and administrators will need to find the Winshuttle Function Module (WFM)
version number, so that they can determine whether an upgrade is needed. This can easily be
done via Studio or directly from SAPGUI.

Applies to -
Studio: Winshuttle Function Module

Solution –
Method 1 – Finding WFM version from SAPGUI
 Log on to the SAP system.

 In the Menu-bar, go to System -> Status.

 Now press the Component Information (lens icon)

  On the next displayed screen, scroll to bottom to find the Software Component
‘WINSHTLQ’ to get the exact WFM version.

Method 2 – Finding WFM version from Studio

 Open Winshuttle Studio. Click on New -> Query. Then choose any of the creation
method.
  Sign in to the SAP system in question.

 In Studio, click the arrow next to the system number that is displayed in the status bar.
The WFM version is displayed.

The status bar, displaying the SAP system in use and the WFM version.

4) Importing Query or Transaction Function Module Transport Error

Description –
User is getting error "X of X requests do not match the component version of the target system"
while applying any Winshuttle transport to their system
Applies to -
Any of the Winshuttle provided SAP transports

Solution –
Re-run the import with the following option(s) selected:

 Leave Transport Request in Queue

 Import Transport Request Again
 Ignore Invalid Component Version

If the versions of the components are newer on the customer system, select this final option to
override SAP and complete the import.

5) Validate does not function correctly when a loop starts with in a loop
immediately

Description –
User is getting improper message(s) in Validation Log column, when there are nested loops
present in script, and customer has Winshuttle Function Module (WFM) installed.

Applies to -
Studio: Scripts with Nested Loops for any of the SAP Transaction Code
Cause -
Because of Immediate Nesting of loops, data of internal loop is passed to WFM followed by outer
loop data. That is not the expected input pattern to WFM as per its design. Hence, there is a
Technical limitation because of which validation can’t be handled.

Solution –
A small change in script will fix this issue, as per which we need to insert at least one field (that
can be anything, but not the BDC Cursor) between two loops. Same is shown below-

6) Support Article - syntax error in long text v12

Description –
There may be an issue with creating or updating long text in some of the SAP transactions after
upgrading to Winshuttle Function Module (WFM) 12.0 or above
An SAP dump may be getting generated on SAP server.

Applies to -
Studio: Long Text update for any Transaction Code

Cause -
There are few standard SAP structures that do not exist in lower versions of SAP. WFM require
to include those structures programmatically to resolve the errors.
So due to internal SAP changes with run in effect tcodes, long text could not be entered or
updated.

Solution –
The fix for these issues has been added in the WFM. User just need to import the mentioned
transports on relevant SAP server.

7) Support Article - Long Text Objects are Not Available for this transaction
Description –

There may be an issue with Add long text feature in some of the SAP transactions with Winshuttle
Function Module (WFM) 11.0 or above.

Winshuttle User getting studio popup that long text objects are not available for this transaction.

Applies to -

Studio: Add Long Text feature for any Transaction Code

Cause-

User can get studio popup error message from any of reasons below.

1. User did not import the Winshuttle provided transport files-

 For Add long text feature, some table entries required to import into Winshuttle tables.
These table entries are provided as transport files and are provided along with installer files.

2. User has imported the required transport files into wrong client-

For Add long text feature, some table entries required to import into Winshuttle tables.
These table entries are provided as transport files and are provided along with installer files.

As these table entries are client dependent, it is expected that end user should always
import these transports into User Client or where the studio scripts require to run.

3. Winshuttle does not support the tcode for Add long text functionality (see below link)-

For v11.0 to v11.x WFM

https://winshuttle-help.s3.amazonaws.com/studio/en/connect-sap/help/11/Record-long-text.htm

For v12.0 WFM

https://winshuttle-help.s3.amazonaws.com/studio/en/connect-sap/help/12/Record-long-text.htm

Solution-

Solution for Cause 1 & 2-

To Confirm, End user can check tables entries in SE16N/SE16 for table '/WINSHTLQ/LTXMAP' and
'/WINSHTLQ/MANDTX’ at user Client and If no table data exist into any of these table then to fix this
issue, please follow the Step 1 and Step 2.

Step 1.
Please import sap transports into user client.

These transports are provided along with installer files GA links and always present into Upgrade
folder.
Step 2.
Go to SA38/SE38 and run the program "/WINSHTLQ/TRN_UPGRADE_TABLE" for all listed tables i.e.
/WINSHTLQ/QREPRM, /WINSHTLQ/QRSAOB and /WINSHTLQ/TRCTAB.
This program creates client-dependent entries in a table. Please run this program on SAP client,
where the changes are expected.

Solution for Cause 3-

If Transaction code is not present on Winshuttle supported tcode list.

Please contact to Winshuttle support team.

8) Validation showing success for alphabetical value for a numeric field

Description –
User is getting success message in Validation Log column, even when there is/are data error(s)
present, in one or more input fields.

Applies to -
Studio: Transaction Code MM02 Validation/Simulation

Cause -
Reason for this error is standard SAP behaviour. We can’t validate data of last screen, as we
must provide SAP exit code to prevent any saving of data. Hence, we need to introduce an
additional screen before exit.

Solution –
 Script needs to be recorded again in this case.
 During re-recording of script, once all the details are entered, end user should not press
the ‘Save’ button directly. User should first press enter, following screen will be
displayed-
  Now, button ‘Yes’ should be clicked to save the data (complete the recording) and exit
out of the transaction.

9) Backup data is offset by 1 row

Studio: Transaction Script, Data Back-up Error
Description –
User is running any script and using the Backup Data option. When the data gets downloaded it
skips the First field however it retrieves the rest of the information. Scenario is observed for
certain Transaction Codes (not for all).

Applies to -
Studio: Run of T-code recorded script

Solution –
Solution for the same is provided from Winshuttle Studio 12.0 onward (along with Winshuttle
Function Module 11.4 or above). Winshuttle now provides a custom table named
/WINSHTLQ/TRNBAK as a part of its installation package. Few identified t-codes i.e. PA30,
IA12, IE02 and PO13 are already part of this table (as shown below in attachment section).
If user faces mentioned issue, he/she can go ahead and create a new entry in table
/WINSHTLQ/TRNBAK for that problematic Transaction Code. Entry should contain the name of
transaction code, along with the technical name of the field which is skipped.

Attachment 1 -
 10) Long Text not working after upgrade to EHP7 or EHP8

Description
There may be an issue with updating long text in some SAP transactions after upgrading to SAP ECC 6
Enhancement Pack 7 or Enhancement Pack 8

 Supported with Studio 10.7 and Winshuttle Function Module 10.7 or above
 Not supported with any version before 10.7

After upgrading to enhancement package 7 or enhancement package 8 of ERP6 you are not able to update
or enter long text.

Applies to
SAP ECC 6 with EHP7 or EHP8

Cause
The control data used in the automation queue for rendering on SAPGUI is handled differently in EHP7
and EHP8 than in previous releases. This led to inconsistency on EHP7 and EHP8 when using the
longstanding way of recording and running these t-codes.

So due to internal SAP changes with record and run in effect tcodes, long text could not be entered or
updated.

Solution
The fix for these t-codes has been added in the Winshuttle Function Module (WFM).
1. Upgrade to 11 WFM or higher (the fixes for Steps 2 and 3 are already included in this release)
2. On WFM, import transport EH7K900104
3. Use t-code SM30 to add the affected t-codes in the table /WINSHTLQ/TRCTAB.
Example values:
LTEXT VA01 0 3
LTEXT VA02 0 3

4. Re-record the scripts in WFM mode.

These t-codes may be affected - CO02, FB02, IW21, IW31, IW32, IW36, ME21N, ME22N, VA01, VA02,
MM01, MM02

Additional Information
For upgrades follow the link for SAP BASIS release 740
TAGS
CO02; FB02; IW21; IW31; IW32; IW36; ME21N; ME22N; VA01; VA02;EHP7
ATTACHMENT 1
K900104.EH7

ATTACHMENT 2
R900104.EH7
11) Support Article-WFM Installation Logs

Description –
User is running any scenario and not aware of the fact whether Winshuttle Function Module
(WFM) is installed properly on their SAP server

Applies to -
All Winshuttle use cases

Solution –
SAP Transaction Code – SAINT
1. Execute SAINT.
2. Select the proper Winshuttle Add-on/PCS.
3. Scroll to the right to the OCS package data.
4. Copy SAPK-xxxx.
1. Click Go-To > Import Logs > Single Package.

2. Paste the SAPK-xxxx value.

3. Execute.
 4. Confirm that the transport(s) were successfully imported.

12) Support Article- No Message is Return from SAP’ or ‘Control data is

obsolete, rerecord (VERBS-NAME: CreateObjectCATT: <none>Callno: 000001)’
message appears with Studio or Transaction
Information-
‘No Message is Return from SAP’ or ‘Control data is obsolete’ logs appear with Studio or Transaction
after any upgrade or installations.

This error is received when running a Winshuttle script for Any TCode.

Reasons-
1-This problem is caused by transactions that contain the controls data and error can occur due to
“Screen Controls" in application program.

2-Sometimes after applying a sap Basis support package, it is possible that it will contain changes to
one or more of the user interface controls of the SAP Control Framework. Such changes to the
internal implementation of controls can invalidate the recorded control data. Consequently, the
module fails when you try to replay it under the new support package level.

Related Jira ids.

WIN-8781, WIN-8825, WIN-11684, WIN-10371, WIN-9672, WIN-11200.

Affected Environment-
Transaction/Studio

10.7/11.0/11.1/11.1.1/11.2 WFM
Pre-requisite-
WFM should be installed.

Solution-

Fix for these Issue has been added in the Winshuttle Function Module (WFM) and transport files has been
released for respective versions.

1-WFM 10.7 or 10.HF2 (10K) 70x-731-740-750 ERP

2-WFM 11.0(10L) 70x-731-740-750 ERP

3-WFM 11.1.1(10N) 70x-731-740-750 ERP

4-WFM 11.1.1(90M) 70x-730-740 ‘Non-ERP’

5-WFM 11.2(10O) 70x-731-740-750 ERP

6-WFM 11.2(90N) 70x-730-740 ‘Non-ERP’

13) Support Article- Backup Data is not working

Information-
Winshuttle Backup Data feature not working for some field.

Reasons-
Field Parameter value need to define at user level to resolve this issue.

Related Jira id’s

WIN-11677

Affected Environment-
Transaction/Studio

Solution-
Please perform below steps.
1. Open Saplogon pad.
2. Go to "SU3" tcode.
3. Open "parameter" tab in the next screen.
4. Add an entry for "BUK" with parameter value "?".
5. Save the Changes.
6. Once Above steps has been completed, please record a new script and run it with backup data.

Note- above parameter value “BUK” is for Company code which will different for other fields.
How to get the parameter for any field-
Press F1 at field and go to technical Information.

14) Support Article- No Message return from sap with v10.5(10I) WFM
Information-
Customer scripts are not working with Non batch mode (with controls/without controls) and No
Action performed at sap.

Reasons-
Customer production environment Ecatt and Catt are not allowed

Affected Environment-
Transaction

Solution-
Please go to Tcode SCC4 and select Login client and go to Details.

Here eCatt and CATT mode should Allowed.

15) Support Article- No PAT07 entries for package
Information-

Reasons-
SAP have included some extra checks in the latest version of SAINT (63) resulting error message

Related Jira ids.

WIN-8734
WIN-8276
.

Affected Environment-
Transaction/Studio

Solution-
Apply SAP correction note 2378346 to resolve this issue.

16) Support Article- Unable to add Long Text when creating a MM02 script
Information-
Unable to add "Long Text" when creating a MM02 script.
Reasons-
Transport files containing table values does not imported at customer environment.

Related Jira ids.

WIN-9565 , WIN-14105

Affected Environment-
Transaction/Studio

Pre-requisite-
WFM should be installed.

Solution-
Please ensure that transport files provided along with SAR files should be imported into local
customer client.
17) Support Article- Winshuttle add-on not shown in SAINT
Information-
Winshuttle installer components does not shown in SAINT tcodes.

Related Jira id.

WIN-9263

Solution-
Please follow below steps to show Installer files in the add-on.
1-Go to T-Code- SAINT.

2- De-Activate the Filter .

3- Add-on files will display.
18) Support Article- Wrong installers has been applied

‘Cannot reset the queue for import phase ‘DDIC_ACTIVATION’.

Reasons-
Customer has installed ERP installer for WFM on Non-ERP system and while installing SAINT stuck at
DDIC activation phase.

Details-
If the log displays the below snapshot

The reason is missing FKNVI include in structure ‘/WINSHTLQ/CUST_TAX_CLASF_MSG’ and missing of

data elements for fields KUNN2_NEW as well as KUNN2_OLD from the structure
/WINSHTLQ/CUST_PF.

Solution-:
Step-1

Delete the Highlighted fields from the structure. -Delete/remove Include FKNVI from
structure – ‘/WINSHTLQ/CUST_TAX_CLASF_MSG’ and activate the structure.
Delete the Highlighted fields from the structure; - /WINSHTLQ/CUST_PF. (Please
avoid this step if not getting error for this structure).

It will ask for access key. Provide access key and delete the fields. (Note there will be no effect on
sap system as these fields are not physically available in Sap system.)

After the deletion of these fields. Activate the structures and go to transaction SAINT and proceed
with the process of Installation.

Once the installation has been done. Uninstall the Winshuttle installer and then install the correct
installer. Ie:- Installer for Non-ERP servers.
19) Support Article- Customer Upgrading SAP system to S4 HANA 1610
Issue – While customer is doing SAP server conversion (Migration/Upgrade/Conversion) to S/4
HANA 1610 via SUM (Software Upgrade Manager) on an SAP system where Winshuttle Add – On is
installed then they get following message/error

Solution – If a WINSHTLQ add-on is installed and customer want to upgrade to S4 HANA 1610 then

1. They can un-install the WFM/WINSHTLQ Add-On and proceed.

2. They can use the attached file WNSC65AI.SAR and WNSC65AI_ACP.SAR.
These files are to install WINSHTLQ Add-On v11.2, on S/4 HANA 1610.
Steps -
1. They need to upload WNSC65AI.SAR first via SAINT transaction.
2. When they have uploaded WNSC65AI.SAR, they need to upload WNSC65AI_ACP.SAR via
SAINT transaction.
3. Ensure that they perform this on their Sand Box or Dev system first and if successful then
go for other systems.

Once they have uploaded the files then rest, they can do via their Software Upgrade Manager
(SUM).

WNSC65AI_ACP.SAR WNSC65AI.SAR
20) Support Article- SAP Upgrade Stopped due to Winshuttle Add-On
Scenario: -

Customer is in process to upgrade their SAP system from some old release to newer release. Since
older release already have a WFM installed on it, they get an error during SAP upgrade.

Description: -
Customer requesting for Winshuttle vendor key during SAP upgrade.

Applies to: -
All versions

Solution: -
As per sap note "1324996 - Vendor keys for manufacturers of ABAP add-ons". Sap stopped providing
vendor keys for manufacturers of ABAP-Ons.

Note is attached here, please visit the https://support.sap.com/en/index.html for latest version of
this.

1324996.pdf

Now there can be following scenarios

1. If customer SAP version is SAP4.7 or ECC5

 This SAP version do not support “Un-Install” hence Delete Add-On is also not the option.
 Please use first option from SUM and after uploading targeted WFM version in the
SAINT.

2. If they have SAP version higher than SAP4.7 and ECC5

 This version of SAP support Uninstallation but with SAINT version 53 or higher.
 Please uninstall the WFM first via SAINT then install the relevant WFM via SAINT.
Note –

o All WFMs with version >= 11.1.1 are already “De-installable”

o All versions<11.1.1 are not de-installable by default, please connect with WFM team
for the ACP files which will make these versions also De-Installable.
o If target WFM version is WFM 11.3 or higher then No ACP is required, WFM – Add
on is enough.
o If target WFM version is lower than 11.3 then WFM Add-On plus ACP file would be
required, please connect with WFM team for the ACP files.
o If SAINT is lower than version 53, then this SAINT version would need to upgrade as
well for doing “Uninstallation”. Refer attached file for more detail.

Server Side
Uninstallation WINSHTLQ components WFM.docx

21) Support Article- Studio 11 - Adding Long Text functionality with EHP7
Studio 11 - Adding Long Text functionality with EHP7
“Long Text Objects are not available for this transaction code. To find out how to record
long text, please see”

Information-
While trying to create VA02 script and adding long text in mapper, user gets following error.

“Long Text Objects are not available for this transaction code. To find out how to record long text,
please see”

Reasons-
' Add Long Text ' feature was not working for VA02 transaction on EH7 server due to missing table
entries in config tables.
Related Jira ids.
WIN-10208

Affected Environment-
Transaction/Studio

Solution-
Maintained the table entries in configuration tables.

22) Support Article- Function Module issue after installing 11.2 NW APO
Information-
Function Module issues after installing 11.2 NW APO
Reasons-
User used wrong installer for APO system, they installed " WFM 11.2 for NW (APO)-70x-731-740"
and instead that they installed "WFM 11.2 for ERP6-70x-731-740-750".

Related Jira ids.

WIN-9798

Affected Environment-
Transaction/Studio/WFM

Solution-
User needs to De-Install the current WFM and then need to install "WFM 11.2 for NW (APO)-
70x-731-740".

23) Support Article- Error in transport and not able to install WFM
Information-
Error in transport and not able to install WFM due to that.

Reasons-
For custom transports, WFM must be installed first in system. User tried with applying custom
transports first be WFM installation hence the error.

Related Jira ids.

WIN-10115

Affected Environment-
Transaction/Studio/WFM
Solution-
For custom transports, WFM must be installed first in system.

Install WFM first then apply the transports.

24) Support Article- Table data not populated

Configuration tables data not populated even after applying the

custom transports and gives error.
Information-
Configuration tables data not populated even after applying the custom transports and gives error.

Reasons-
Transport applying steps are not correct here.

Related Jira ids.

WIN-10593

Affected Environment-
Transaction/Studio/WFM
Solution-
Check all the flags apart from first as shown in screenshot in transaction STMS and apply the
transport.

25) Support Article- Error during an SAP server conversion

Error during an SAP server conversion

(Migration+Upgrade+Conversion) from ERP6 EHP7 (NW7.40) on
MSSQL Server to S/4HANA 1610 (NW7.51)

Information-
Error during an SAP server conversion (Migration+Upgrade+Conversion) from ERP6 EHP7 (NW7.40)
on MSSQL Server to S/4HANA 1610 (NW7.51).
Reasons-
During SAP server upgrade from ERP6 EHP7 (NW7.40) on MSSQL Server to S/4HANA 1610 (NW7.51) ,
System asked for Upgrade file for Winshuttle Addon too.
It asks for either deletion of Winshuttle addon or Upgrade file for Winshuttle addon.

Related Jira ids.

WIN-10687

Affected Environment-
Transaction/Studio

Solution-
Provide the deletion files for Winshuttle addon.
Also provide the exchange file for Winshuttle addon.
Note- These files are WFM version dependent. Here deletion files are for WFM v11.2 on Basis
70x/731/740/750 release.

WNSC10OU_ACP.SA WNSC65AX.SAR WNSC10OI_ACP.SA

R R
26) Support Article- Errors in WFM installation-Installation upgrade

Errors in WFM installation-Installation/upgrade package for add-on

SAP_ABA/ Release 75 B does not exist

Information-
Errors in WFM installation-Installation/upgrade package for add-on SAP_ABA/ Release 75 B does not
exist

Reasons-
Installer of S/4 HANA 1610 was being used on S/4 HANA 1511 system

Related Jira ids.

WIN-11117

Affected Environment-
Transaction/Studio

Solution-
Use installer of S/4 HANA 1511 instead of S/4 HANA 1610.

27) Support Article- Runtime error MESSAGE_TYPE_X has occurred in IW22

Runtime error MESSAGE_TYPE_X has occurred in IW22

Information-
Runtime error MESSAGE_TYPE_X has occurred in IW22
Reasons-
"Start SAP GUI" was enabled, needed to disable.

Related Jira ids.

WIN-11512

Affected Environment-
Transaction/Studio/WFM

Solution-
Disable the "Start SAP GUI" from script and Run again. Please see the screenshot as follows
28) Support Article- Duplicate values are being displayed in lookup
Duplicate values are being displayed in lookup

Information-
Duplicate values are being displayed in lookup

Reasons-
Duplicate values were not coming, instead description field was also carrying the Values only.

Related Jira ids.

WIN-14930

Affected Environment-
Transaction/Studio/WFM
Solution-
For some fields, there is no text table, so program is unable to identify the description field for the
field on which F4 is being fetched.
This is as designed.

29) Support Article- Issue with Authorizations missing

Information-
A user has upgraded their Test environment from WFM 10.5 Query to WFM 11.2 after which
their Transaction scripts which was reading data from SAP to a form is no longer working.

Authorization check comes successful for the user.

Reasons-
User has upgraded WFM from 10.5 to 10.7 but related authorizations were not upgraded.

Related Jira ids.

WIN-15761

Affected Environment-
Transaction/Studio/WFM

Solution-
Upgrade the required authorizations as per the WFM version.

30) Support Article- WFM Upgrade issue 11.0 to 11.3 Component not visible in
SAINT
Information-
WFM Upgrade issue: 11.0 to 11.3 Component not visible in SAINT

Reasons-
User is not able to see the WFM 11.3 as their filter was activated in SAINT transaction.

Related Jira ids.

WIN-15853

Affected Environment-
Transaction/Studio/WFM
Solution-
1. As the system was not an APO system, remove the WFM's APO version from their system
first.
2. For that, ask for ACP files.
3. Then install 11.3 once installed WFM on APO has been removed.

31) Support Article- 11.3 WFM - ADD_TO_BUFFER error

Information-
11.3 WFM - ADD_TO_BUFFER error

Reasons-
Error due to system issue at customer end.

Related Jira ids.

WIN-16830

Affected Environment-
Transaction/Studio/WFM

Solution-
Error due to system issue at customer end. Coordinate with SAP to get the error solved.
32) Support Article- Script for T Code FV50 fails only for a particular user
Information-
Script for T Code FV50 fails only for only one user
Script fails while running and gives error message .

Reasons-
Error due to system issue at customer end. For the said user, customer was using the screen
variants and that was causing the error.
Screen of the user with screen variant which results an error.

Screen of the all other users without screen variant which results successful.
Related Jira ids.
WIN-18528

Affected Environment-
Transaction/Studio/WFM

Solution-
Error due to system issue at customer end. Please use No Variant or right variant to get it
worked.