UpdateProcessedRFQResponseStatus (PUT)

Overview

This Acknowledgment API allows us to capture back the ERP processing status in processed RFQ response status into GEP SMART that is displayed to the user along with comments in case of failures.

URL Format: https://<Instance>/SmartInterfaceAPI/api/RFX/RFXResponseAcknowledgment

Request

[
   {
      "key": "String",
      "description": "String"
   }
]

Response

{
   "data": {},
   "statusCode": "String",
   "errorDetails": [
      {
         "key": "string",
         "errors": [
            {
               "errorCode": "string",
               "errorDescription": "string"
            }
         ]
      }
   ],
   "successDetails": [
      {
         "key": "String"
      }
   ]
}

Examples

Success Scenario – Request

[
   {
      "key": "MSRFX051119_01|PC-2017.008373",
      "description": ""
   }
]

Success Scenario – Response

{
   "data": null,
   "statusCode": "200",
   "errorDetails": [],
   "successDetails": [
      {
         "key": "MSRFX051119_01|PC-2017.008373"
      }
   ]
}

Error Scenario – Request

[
   {
      "key": "MSRFX051119_01|PC-2018.009049",
      "description": "test"
   },
   {
      "key": "MSRFX051119_01|PC-2017ac.008418",
      "description": ""
   }
]

Error Scenario – Response

{
   "data": null,
   "statusCode": "400",
   "errorDetails": [
      {
         "key": "MSRFX051119_01|PC-2017ac.008418",
         "errors": [
            {
               "errorCode": "Exception",
               "errorDescription": "ValidationException: Invalid Partner Code PC-2017ac.008418"
            }
         ]
      }
   ],
   "successDetails": [
      {
         "key": "MSRFX051119_01|PC-2018.009049"
      }
   ]
}

Data Elements

	Update processed RFQ Response status
S.No.	Property	Required?	Data type	Description	Validations/Exceptions
1	Key	Yes	String	Key of the entity	Key is mandatory RFQ Number and Partner Code are mandatory Invalid Partner Code RFQ Number is invalid
2	Description	No	String	Description of the entity