When using the backup data sheet, you may find that for some transactions the data is offset by a row.
Studio 11.4 and higher, WFM 11.4 and higher
Winshuttle now provides a custom table named /WINSHTLQ/TRNBAK as a part of the Winshuttle Function Module installation package. You can create a new entry in table /WINSHTLQ/TRNBAK for the problematic Transaction Code. The entry should contain the name of transaction code, along with the technical name of the field which is skipped:
The following t-codes i.e. PA30, IA12, IE02 and PO13 are already part of this table in the version 12 Winshuttle Function Module.