Symptom
DUMP below is raised:
Category: ABAP programming error
Runtime Errors: AMDP_UNCOMMITTED_DBPROC_CALLED
ABAP Program: CL_PPH_FCDM_AMDP_PIR==========CP
Application Component: PP-MRP
Environment
SAP S/4HANA Cloud Public Edition 1808
Cause
A previous call from the SADL framework to CL_ABAP_BEHV_LOAD=>GET_LOAD has triggered a GENERATE REPORT for the requested "xxx===...===BD". This binds the process to do this and all future generations locally, not (as would be the default) in a separate process including a commit. So these generations are not yet committed when the AMDP is to be executed, a situation which is refused by the AMDP runtime.
Resolution
SAP provided a permanent fix for the issue in SAP Note 2695847, however, on cases where the dump was already generated it is necessary to generate the class CL_PPH_FCDM_AMDP_PIR from SE24.
How to do it:
- Open the back end system
- Go to SE24
- Enter class CL_PPH_FCDM_AMDP_PIR
- Display it and hit activation button
See Also
SAP Note 2695847 - Avoid (AMDP) dumps due to forced local generation in RAP runtime
Keywords
dump, S4, S4HANA, AMDP_UNCOMMITTED_DBPROC_CALLED, CL_PPH_FCDM_AMDP_PIR==========CP, App Maintain PIRs F3445, application, Runtime Error , KBA , BC-ABA-LA , Syntax, Compiler, Runtime , Problem