Deferred mode versus Non-deferred mode batch request processing? in SAP NW gateway Odata

[#1]

Hi All,

Can any one explain me the difference between the deferred mode batch processing(CHANGESET_BEGIN() method's changing paramter CV_DEFER_MODE set to 'X') and non-deferred mode( CV_DEFER_MODE = abap_false), and at what scenarios we usually decide to go for each of these? in SAP Odata batch request processing.

What i know till now is :

when i send a batch request with CV_DEFER_MODE set to 'X', that is deferred mode , In DPC class control follows like changeset_begin==>Changeset_process==>Changeset_end, where changeset_process internally may call basic CRUD operations of entity sets methods,

When i send a batch request with no-deferred mode, CV_DEFER_MODE set to abap_flase, in DPC class control follows like changeset_begin==>Basic Modifying methods of entity set according to the related operations in change set==>Changeset_end,

So, since in both the ways we will be calling the same modifying methods of entity set , then what actually differentiates them which makes us to go choose them for batch processing.

Thanks in advance,

Avinash

[Andre_Fischer]

Using the deferred mode would allow you to implement the use of content id referencing as described here by my colleagues

kenichi.unnai :

https://blogs.sap.com/2016/03/09/how-to-implement-odata-batch-processing-with-content-id-in-sap-gate...

and it can help to improve the Performance as explained by my colleague mrajasekarana in his blog

https://blogs.sap.com/2018/05/06/batch-request-in-sap-gateway/

Regards,

Andre

[avinashd_m]

Hello Andre,

Thanks for the suggested link, i have already gone through those.

I agree content referencing is possible only in deferred mode.

In the blog i can see only that with deferred mode performance will be increased and related call stack, but i am not clear, based on what optimization happened or conditions met in the DPC class, it is been said that the performance will be increased with deferred mode?, than non-deferred mode.

Thanks,

Avinash