Internal Error Codes
This section lists the error messages handled in Arrangement microservice with description.
The following are the API error code and messages.
|
Error Codes |
Error Messages |
|---|---|
|
AMS-0001 |
The request is invalid |
|
AMS-0002 |
Success |
|
AMS-0003 |
Mandatory query parameter is missing |
|
AMS-0004 |
At least a query parameter is required |
|
AMS-0005 |
Request header is missing |
|
AMS-0006 |
Request body is Missing |
|
AMS-0007 |
Duplicate Request |
|
AMS-0008 |
Empty Request. Incase of multiple requests, all or any of the request is empty |
|
AMS-0009 |
Internal Server Error |
|
AMS-0010 |
Arrangement id is not necessary. It will be auto generated |
|
AMS-0011 |
Arrangement Already Exists |
|
AMS-0012 |
Transformation failed |
|
AMS-0013 |
Invalid |
|
AMS-0014 |
Missing |
|
AMS-0015 |
Record already exists |
|
AMS-0016 |
Display message |
|
AMS-0017 |
Record created Successfully |
|
AMS-0018 |
Mismatch of %s in URL and Body |
|
AMS-0019 |
Record Not Found |
|
AMS-0020 |
Party Arrangement unavailable |
|
AMS-0021 |
Account Not Found for the Arrangement |
|
AMS-0022 |
Unable to persist |
|
AMS-0023 |
Too Many Query Parameter |
The following are the ingester error code and messages.
|
Error Codes |
Error Messages |
|
AMS-2001 |
<companyId> - Company record missing (during ingestion of customer and arrangement) |
|
AMS-2002 |
<companyId> - Ingestion Failed for company - Reason : <Exception Message> |
|
AMS-2003 |
<productId> - Ingestion Failed for Product - Reason : <Exception Message> |
|
AMS-2004 |
<restrictId> - Ingestion Failed for Posting Restrict - Reason: <Exception Message> |
|
AMS-2005 |
<officerId> - Ingestion Failed for Officer - Reason: <Exception Message> |
|
AMS-2006 |
<customerId> - Ingestion Failed for Customer - Reason: <Exception Message> |
|
AMS-2007 |
<arrangementId> - Ingestion Failed for Arrangement (AA_ARRANGEMENT Event) - Reason: <Exception Message> |
|
AMS-2008 |
<arrangementId> - Ingestion Failed for Arrangement (AA_ACCOUNT_DETAILS Event) - Reason: <Exception Message> |
|
AMS-2009 |
<arrangementId> - Ingestion Failed for Arrangement (AA_ARR_OFFICER Event) - Reason: <Exception Message> |
|
AMS-2010 |
<arrangementId> - Ingestion Failed for Arrangement (AA_ARR_ACCOUNT Event) - Reason: <Exception Message> |
|
AMS-2011 |
<arrangementId> - Ingestion Failed for Arrangement (AA_ARR_CUSTOMER Event) - Reason: <Exception Message> |
|
AMS-2012 |
<arrangementId> - Ingestion Failed for Arrangement (Updating product line based fields and ACCOUNT_CLOSED Event) - Reason: <Exception Message> |
|
AMS-2013 |
<arrangementId> - Ingestion failed For Arrangement (Extension Data mapping failures) - Reason: <Exception Message> |
|
AMS-2014 |
<accountId> - Ingestion failed for Schedules(EB_CASHFLOW Event) - Reason: <Exception Message> |
|
AMS-2015 |
<arrangementId> - Ingestion failed for Schedules(AA_BILL_DETAILS Event) - Reason: <Exception Message> |
In this topic
