In OData implementation for batch processing, a changeset might contain multiple CUD (CREATE/UPDATE/DELETE) operations. This can be problematic in combination with eTags because one operation can change data that is about to be processed by consecutive operations. In this case, eTags of these operations might not be valid anymore. You have to redefine the changeset methods and enable defer mode. When using defer mode the automatic eTag check will be done for all operations before any operations have been processed.
Please refer to the below SAP documents for more details on ETag handling in batch processing.
#NW ABAP Gateway (OData) #OData