WFM Benefits
Adaptive query throttling
- Checks dialog processes
- Check system resources
- Stop Explicitly Query Execution for an Un-optimized Query (Adaptive Query Throttling - U.S. Patent No. 8321447)
Chunking
- With WFM , Client Chunking can be used in which data extraction with chunks resulting in faster processing
- WFM uses Server-side Chunking. In this process, ABAP memory is utilized in compressed way, which results in processing of large data set without ABAP memory dump
Background processing
- With WFM , large query can execute as background work process (in "Background Mode")
- Saves dialog work processes
- Large query can be scheduled overnight
Query with t-code recording - Query can be created with underlined tables used behind any t-code. Expert knowledge is not required.
Query with Logical Databases - Query can be created for SAP Logical Database as well.
Transaction Validation
- For data with no Loops: Data is passed per row; the data is read and validated.
- For data in Loops:
- A single call per data set is passed from the RFC client to the FM
- The FM will make <n> recursive calls to the transaction code using the “call transaction” function until the list of items is exhausted
- The FM will deliver a single aggregated result of errors to the RFC client, thereby reducing the number of RFC calls and reducing latency
- Support for more than 10,000 line items
Comparison of validation times
Insert image from original Word doc here.
Transaction Simulation
- Certain transactions in SAP provide a simulate or whole document check option (typically financial documents)
- Script recordings cannot easily incorporate this feature
- Simulate will return messages that would typically only appear at the attempted commit of the data set
- Types of results detected with Simulate
- Balance checking on documents
- Input tax and tax on sales and purchases, are generated
- Profit & Cost Center checking
Document Attachment
- More options for Document Attachment
- Attachment can be saved to External Repository, saving SAP DB
- Requires FM configuration
- Covers GOS, BDS, DMS
- If the WFM is absent- then only BDS is supported
- Feature will be supported for all t-codes that can be configured (for specific attachment method)
Add/Retrieve/Update long text
- An additional long text option
- User can create and change the long texts
- User can read the existing long text
- Length of long texts can be updated
- Recording steps of long text is not required to update or read
- Long text will only be updated if document changes get executed successfully
- Easy steps for long text read or update
- Works with all SAP versions
- Works with the following important transactions:
1. FB02
2. FB03
3. ME22N
4. ME52N
5. MM02
6. VA02
7. XD02
8. XK02
9. BP
10. FK02
11. FK03
12. MK02
13. MK03
14. ME32K
15. VD02
16. FD02
17. VD02
18. IW32
19. IW32
20. IE02
21. IL02
22. IP02
23. AS02
24. KS02
25. ME12
26. CV02N
27. VA42
28. MM42
29. VA12
30. VA32
31. VA22
Skip Screen WFM-only functionality
- In one call from client, Skip Screen “if not found” functionality can be achieved through WFM
- Reducing the number of RFC calls from Client and hence reducing latency resulting in faster Execution
- Debug with Skip Screen is also supported for all t-codes except PA30/PA40
- Support available for “Read from SAP” functionality with skip screen
User administration control page
- A dedicated Winshuttle Custom T-code /n/WINSHTLQ/ADMPANEL to maintain all Winshuttle tables and tab pages for query authorizations, WFM admin parameters, and other options
- Provision to define Storage Category for a DMS attachment in Winshuttle Admin Panel, providing them feasibility to define external repository
- Easy to handle all Winshuttle parameters, as it uses SAPGUI
Vendor payment data handling
- Generation of Bank Details from IBAN & vice-versa
- Creation, Change & Deletion of IBAN/Bank data for mentioned Vendor
- Creation of New bank on user selection
- Check for Bank Master data
- Have also been made compatible with transaction code BP on releases S/4 HANA 1610 onwards
Customer master features
- Add/Delete partner functions
- Email ID insert or delete in customer
- IBAN create/Delete
- Replace/Add bank to given IBAN
- Delete bank for given customer
- Bank creation
- Update the tax classifications of customer
- Functionality to update Sales Data and Tax Classification with the same script
- Have also been made compatible with Transaction code BP on releases S/4 HANA 1610 onwards
What’s happening behind the scenes
- Asynchronous processes
- Improved Run performance
- Plug-and-play architecture
- More than 10% throughput performance improvement
Changes with SAP S/4HANA for Extended Material Number
- With SAP S/4HANA, the maximum length for Material Number was extended from 18 to 40 characters
- All external interfaces (BAPIs, IDOCs, RFCs) containing Material Number still have the usual technical field MATNR with length 18. This is for compatibility reasons
- These interfaces have been enhanced by a new field: MATNR_LONG
Changes to accommodate Customer and Vendor master into one new transaction called BP
- Customer/Vendor masters have now been replaced by Business Partner (i.e. a common t-code, BP)
- All Customer/Vendor related t-codes are obsolete. These include XD01/XD02/XD03, XK01/XK02/XK03, FD01/FD02/FD03, etc.
Additional Benefits
- SAP certified for S/4 HANA 1610, 1709, 1809, 1909 and 2020
- Winshuttle Tested for S/4 HANA 1610, 1709, 1809, 1909 and 2020
- Feasibility to give Multiple Currency and/or CO-PA values into linear rather than hierarchical structure
- Purchase Requisition Number updating in Studio Logs after ME51N run
- Support for WHERE criteria on Right Tables with Left Outer Join
- Query Support with SAP Logon Group based Load Balancing
- Supported across all ERP, S/4 HANA and Non-ERP (BASIS releases 700 and above)
- Detailed SAP Traces
- Support of all Winshuttle features on SAP EHP7/EHP8 environments as well
- Winshuttle Memory Management to avoid system runtime errors during large Transaction/Query execution