Description

When sales return orders are created manually through the UI, the system correctly defaults the returned quantity as not available for reservation. However, when the same scenario is executed through standard OData entities (ReturnOrderHeadersV2 / ReturnOrderLinesV2), this default logic is not applied unless the field IsReturnedQuantityAvailableForReservation is explicitly provided in the payload.

This creates an inconsistency between manual and automated processes and increases integration complexity. Customers expect the same default business logic to apply regardless of whether return orders are created via the UI or through supported integration APIs.

Requested Improvement

Apply the same defaulting logic for OData‑created return orders as is applied during manual/UI creation when the field is not explicitly provided.