3775025 - HTTP 500 timeout on service contract ODATA V4 $batch requests due to large contract processing time - SAP S/4HANA Cloud Public Edition

OData V4 $batch request on a service contract exceeds 10 minutes and fails with HTTP 500 connection timed out.

SAP S/4HANA Cloud Public Edition

• The batch processing time exceeded a hard‑coded 10‑minute API timeout due to heavy recalculation and repricing in large service contracts (many items and/or long duration generating numerous billing request lines).
• The 10‑minute API timeout is hard coded at the framework level and cannot be changed per tenant.

1. Reduce the number of PATCH operations per $batch request (split into smaller batches) for typical‑sized contracts.
2. For large contracts, reduce processing complexity by splitting contract items or shortening contract duration to decrease the number of billing request lines that must be recalculated.
3. Validate and fine‑tune batch sizes and change scope in the target environment, and consider running changes during periods of lower system load.

odata v4, service contract, $batch, patch, http 500, timeout, 10-minute timeout, performance, long processing time, billing request lines, recalculation, many items, long duration, api time limit, batch size , KBA , CRM-S4-SRV-CTR-2CL , S4CRM: Service Contract (Public Cloud) , Problem