Odata batch processing...how to perform check only and skip commit in CHANGESET_END ?

[former_member701830]

hi guys

in SAP backend, some of the bapi contains Import parameter IV_COMMIT, and when you supplied IV_COMMIT = space, it will just do a simulation run and return the results to you without committing. If there is no issue, you can execute the same bapi again and this time you put IV_COMMIT = 'X'.

How do i achieve the same in Odata batch processing? It seems that in /IWBEP/IF_MGW_APPL_SRV_RUNTIME~CHANGESET_END, there is no import parameter that i can use to skip the COMMIT call.

I can purposely throw an exception in /IWBEP/IF_MGW_APPL_SRV_RUNTIME~CHANGESET_PROCESS and this will skip the CHANGESET_END, but this will not return any response to me which i need them!

Please advise.

Thanks

[ritam_de1997_29]

I have the same question. Facing the exact same challenge.