3785223 - Duplicate check returns fewer or no matches when requests are run in parallel (api_business_partner)

When calling the DuplicateCheck action of API_BUSINESS_PARTNER in parallel (e.g., concurrency=2 or concurrency=4), the number of returned duplicate candidates decreases as concurrency increases and eventually drops to zero, while HTTP responses still return 200 success.

SAP S/4HANA Cloud Public Edition

1. Run DuplicateCheck requests in parallel using the Business Partner OData API (for example, by launching multiple curl requests concurrently).
2. Compare results when running sequentially (concurrency = 1) versus in parallel (for example, concurrency = 2 and 4) and observe that result counts decrease as concurrency increases.

The DuplicateCheck action is designed only for single duplicate check runs (originally intended for the SBN scenario), and does not support mass or concurrent invocations by design.

Please invoke the DuplicateCheck action sequentially (one request at a time). Mass or concurrent execution is not supported.

• Refer to: Duplicate Check

Duplicate Check, API_BUSINESS_PARTNER, Business Partner OData, parallel requests, concurrency, empty results, HTTP 200, duplicate candidates, sequential, throttling, race condition, temporary view, mdg duplicate check, odata action, bulk processing , KBA , LO-MD-BP-ODT , OData Service for Business Partner , Problem