oData service batch call gives "statusCode : 500, Error when processing resource"

[Andre_Fischer]

I am trying to consume the oData Service by binding Table with oDataModel which fetch data and its count using $batch.

This will give me error

saying "Error when processing resource".

If I disable batch call by setUseBatch to false the odata will start working.

Since it was directly consuming data from CDS views and it was working earlier, there is no implementation issue.

I doubt some configuration is missing which is disabling the batch call and preventing it from reaching the Gateway server itself as there is no error shown in Error log as well.

With Regards,

Ramesh Shrestha

[Andre_Fischer]

have you checked the error log on the SAP Fiori Frontend Server and the SAP Backend?

/iwfnd/error_log

/iwbep/error_log

There you might find hints what went wrong when processing your $batch request.

Regards,

Andre

[olde]

Hi Ramesh, Hi Andree

I'm facing a similar issue. We have an Odata service which is running fine in batch mode, even in production, since years.

Now I try migrate the eclipse based UI5 application to WEB IDE full stack using master-detail template of webide.

And I'm getting the same error you have described, also no hints in the error log. Other Z-Odata services work fine with webide in batch mode.

Did you solve your problem and could give me a hint what is the cause?

Regards

Heiko

[RameshShrestha · Accepted solution]

Configuration was changed in the backend which was blocking the batch call. On changing the configuration is was resolved.

[poluvamsee · Accepted solution]

What was the configuration to check

[former_member278239]

Dear Team,

What is the use of C Co-deployed only, Routing-based, I Inherited in Odata Services.

Regards

[RameshShrestha]

Thanks Andre for your response,

I have checked both, and there is no error there. I doubt the batch call even reached the gateway service method. I kept breakpoint at the Init method of service which did not trigger. The service was working fine before some migration changes done.

With Regards,

Ramesh Shrestha