SalesOrderHub PATCH API related to BillToCustomerId and BillToSiteUseId validation
Summary:
Hi Everyone,
We are facing an issue with the SalesOrderHub PATCH API related to BillToCustomerId and BillToSiteUseId validation.
We have two different payloads where the Bill-to related fields are exactly the same (same Bill-to customer details in the payload), but:
One payload works without any errors
The other payload fails with errors like:
The request couldn't be completed because either it doesn't include a value for the BillToSiteUseId attribute, or the value of *******731462 that it does provide isn't valid.
What is confusing is that these values are not even present in the payload for both cases. Only the AccountNumber differs between the two payloads. Still, Oracle returns the error only for one of them.
Tagged:
0