When using the backup data sheet, you may find that for some transactions the data is offset by a row
Studio 11.4, 12, WFM 11.4, 12
Winshuttle now provides a custom table named /WINSHTLQ/TRNBAK as a part of its Winshuttle Function Module installation package. If you face this issue, 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 WFM.