Created by Jerry Wang, last modified on Mar 04, 2014
The real problem could be reproduced by following the four steps below:
After clicking back button we return to product overview page, and then click the save button there, we could see the dump in UI and also in ST22:
Here below is the steps to analyze the root cause.
From the callstack we could observe there is a nested PERFORM XXX ON COMMIT, as is also mentioned in ST22:
In callstack 19 the application trigger a COMMIT WORK AND WAIT which is executed in stack 22.
And in callstack 53, there is a nested PERFORM XXX ON COMMIT again:
So the dump is made deliberately. However this issue could not be reproduced in another system. By debugging the different handling has been found in method below:
The logic is: if the parameter CRM_CM_COMMIT is not set as X, the save mode will be the “direct update mode”, or else the save will only be triggered in commit mode, as explained in comment between line 15 and line 16.
We can first find the value of function profile PARAMETERS is TPM_PROF,
Then set its value as space. After that the dump is gone.
in SPRO there are more detail description about this parameter: