Invoking the Financials Invoices REST API from OIC fails with a HTTP 400 Bad Request Error
(Doc ID 2786226.1)
Last updated on JUNE 21, 2021
Applies to:
Oracle Integration-OIC - Version 18.2.5 and laterInformation in this document applies to any platform.
Symptoms
Invoking the Financials Invoices REST API from OIC fails with a HTTP 400 Bad Request Error
The request content does not represent an action or it has an invalid structure..A 400 Bad Request Error indicates that the target service is unable (or refuses) to process the request sent by the client (Oracle Integration Cloud), due to an issue that is perceived by the server to be a client problem. You can trace the cURL representation of the request sent to the target service from the Oracle Integration Cloud server logs. Try invoking the target service using cURL. It may also be that one of the intermediaries (proxy, LBR) could be returning this code.
The sample JSON provided to the REST Adapter was:
{
"name" : "validateInvoice",
"parameters" : [
{
"InvoiceNumber" : "MY-INVOICE-1"
},
{
"BusinessUnit" : "MY-BIZ-UNIT"
},
{
"Supplier" : "MY-SUPPLIER-1"
},
{
"ProcessAction" : "Validate"
} ]
}
"name" : "validateInvoice",
"parameters" : [
{
"InvoiceNumber" : "MY-INVOICE-1"
},
{
"BusinessUnit" : "MY-BIZ-UNIT"
},
{
"Supplier" : "MY-SUPPLIER-1"
},
{
"ProcessAction" : "Validate"
} ]
}
and the same REST API can be invoked from 3rd party tools such as Postman.
The REST API being invoked is:
fscmRestApi/resources/latest/invoices
See: https://docs.oracle.com/en/cloud/saas/financials/21b/farfa/op-invoices-x-operations-3.html
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |