My Oracle Support Banner

Problems invoking sender: Unprocessable Entity, status code (422) (Doc ID 2885271.1)

Last updated on AUGUST 01, 2022

Applies to:

Oracle Utilities Customer to Meter Base - Version 2.7.0.3.0 and later
Information in this document applies to any platform.

Goal

When we are getting the response from Boomi API, if any invalid(fault responses), C2M is appending some error messages in Base Code.

The Error was returned by the C2M Base Code, not by Boomi, Below is the sample
example of request and response

Response from Boomi for Success scenario

{
  "outcome": "success.payment.bank-details-validated",
  "result": {
  "account": "xxxxxxx",
  "sortCode": "xxxxxx",
  "bankName": "xxxx BANK PLC",
  "bankBranch": "xxxxxx WESTGATE"
  }
}
C2M Conversion after receiving the response from Boomi


  success.payment.bank-details-validated
  
  XXXXXXX
  XXXXX
  XXXX BANK PLC
  XXXXXXX WESTGATE
  


Response from Boomi for the Failure scenario

{
  "outcome": "error.payment.accountno.not-numeric-or-<>8-characters",
  "result": {
  "account": "XXXXXX",
  "sortCode": "XXXXX"
  }
}


C2M Conversion after receiving the response from Boomi

Problems invoking sender: Unprocessable Entity, status code (422). Error
message: {
  "outcome" : "error.payment.bank-details-not-valid",
 "result" : {
  "account" : "XXXXX",
  "sortCode" : "XXXX8"
  }

Expected:


   error.payment.bank-details-not-valid
  
  XXXXXX
  XXXX
  

 

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.