What's new in Customer Journeys?

Connect and learn more!
Does invoice REST-API in 23D require language header? — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Does invoice REST-API in 23D require language header?



After upgrading our TEST and DEV environments to 23D, some of our REST-calls to ERP started failing with the message:

ORA-20000: Applying List binding LOV_Type with given set of values leads to no matching row for a row of type :InvoiceHeaderEO_InvoiceLine2_InvoiceHeaderVOToInvoiceLineVO_InvoiceLineVO, key oracle.jbo.Key[1308929 1 ]

We discovered that adding an http header (Accept-Language and set it to "en-US") to the REST-call resolved the issue.

Below is an example of one of the REST calls where the header is apparently needed:


Can anyone point me to where in the documentation that this requirement is listed? Or if possible, provide an explanation as to why this is suddenly a requirement?

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!