on 03-24-2023 4:52 AM
Hi Experts,
I have a RAP based app for IW32, in the user exits of IW32, BAPI_PROJECT_GETINFO is called, and it has a submit and return statement. This application works fine in S/4HANA 1909 version. But it throws a dump "BEHAVIOR_ILLEGAL_STATEMENT" for the Submit statement. Can anyone explain why does this happen?
Issue is fixed by replacing the BAPI with select query. But I'm curious to know, why RAP based transactional apps throws dumps if there are any commit/submit statement in the underlying business processes in the new version.
Commit work, is not allowed in any piece logic called in the RAP programming App. Even if it is calling any standard business process. So, having this as limitation RAP application should Designed & built accordingly.
If update function is mandate, then use a separate LUW, logically without impacting the RAP commit.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Veeresh,
The RAP framework manages the ABAP Logical unit of work (LUW). This LUW ensures that all changes made to the database are consistent and atomic, meaning that either all changes are committed or none of them are committed. This helps to prevent inconsistencies in the data.
Additionally, COMMIT WORK is not necessary in RAP applications as the framework automatically handles database transactions in a consistent and reliable way.
Thanks,
Pavan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Veeresh,
Please check the below link. Dealing with Legacy Code and Transactional Consistency in RAP
Regards,
Naveen Kumar Chikkanna.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.