Winshuttle

Several customers have found that after applying SAP BASIS 7.00 Support Package 24 (and related notes or packages in other SAP BASIS versions) that their non-batch input recordings ceased to work.SAP patch levels affected
Software Component
SAP_BASIS SAP_BASIS SAP_BASIS SAP_BASIS SAP_BASIS SAP_BASIS SAP_BASIS SAP_BASIS SAP_BASIS SAP_BASIS

Release Support
620 640 700 701 702 710 711 720730 731

Package
SAPKB62070 SAPKB64028 SAPKB70024 SAPKB70109 SAPKB70207 SAPKB71012 SAPKB71107 SAPKB72005 SAPKB73002 SAPKB73101

SAP’s official position regarding the changes is outlined in amessage to Winshuttle that paraphrased, states: “The latest changes to function module CAT_TCD_CAL were part of a security initiative, fixing security issues in component SAP basis. For this reason,undoing those changes [from a base product perspective] is not an option. One change was the new authorization check [we] mentioned. S_DEVELOP was used because it is the standard authorization object for(e)CATT tasks, widely used in the application already. Although the name of the authorization object implies a relationship to development tasks, it is also used to grant execution rights for specificdevelopment objects. In our case it is used in combination with object ‘ECSC’ (eCATT script) and activity ‘16’ (execute). Another change is the check on customizing flag T000-CCIMAILDIS (Flag: eCATTallowed in client?). Even if a user had authorization to run eCATT scripts - execution would fail if the flag was disabled. This could be even more of concern here, as this functionality is usuallydisabled on production systems. CAT_TCD_CAT is an internal module generally only intended for use by CATT and eCATT, accordingly SAP recommended the creation of a custom Function Module.” We offer twopotential solutions to this problem: The first solution to this requires two settings to be made in SAP, one at system level and one at individual user authorization profile level. The second...