When upgrading from R/3 4.6C to a more recent release, many companies encounter a severe error with user exit PBAS0001. You can fix it by following these steps.
Starting with SAP R/3 4.7 all SAP-delivered software meets Unicode compliance standards. Therefore, custom user exit code is subjected to the same Unicode compliance checks. In particular, your custom code in user exit PBAS0001 may cause an error after you upgrade from an R/3 4.6C system. User exit PBAS0001 causes a runtime syntax error in your upgraded system when you execute transaction PA30 and update any information in infotypes.
One of the problems that you may face after upgrading from R/3 4.6C is a problem in maintaining your infotypes. This error occurs immediately when you try to change and update any master data in infotypes. The system terminates transaction PA30 and shows a runtime error message: The current ABAP program “SAPFP50M” had to be terminated because one of the statements could not be executed (Figure 1). The error message also indicates that a syntax error exists in the program SAPLXPAD in the include ZXPADF01. This action prevents you from proceeding in your necessary testing phase before you deliver the system to the users. We will explain how this user exit problem occurs and show you how to fix it. This error appears with non-Unicode-compliant code in R/3 4.6C. If you upgrade from R/3 4.7 or mySAP ERP Central Component (ECC) 5.0 or 6.0, then you shouldn’t encounter this problem.