UpdateProcessedRequisitionStatus (PUT)

Overview

This Acknowledgment API allows us to capture back the ERP processing status in the processed Requisition in GEP SMART.

URL Format: https://<Instance>/SmartInterfaceAPI/api/Requisition/UpdateProcessedRequisitionStatus

Request

{
  "model": [
    {
      "key": "string",
      "description": "string",
      "status": "string",
      "sourceSystemName": "string",
      "sourceSystemValue": "string",
      "lob": "string",
      "errorCode": "string"
    }
  ]
}

Response

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

Examples

Examples

Success Scenario - Request

{
 "model": [
 {
 "Key": "REQ-2020.001420",
 "Description": "SUCCESS"
 }
 ]
}

Success Scenario - Response

{
"data": null,
"statusCode": "400",
"errorDetails": [],
"successDetails": [
{
"key": " REQ-2020.001420"
}
]
}

Error Scenario - Request

{
 "model": [
 {
 "Key": " REQ-2020.002080",
 "Description": "SUCCESS"
 }
 ]
}

Error Scenario - Response

{
 "data": null,
 "statusCode": "400",
 "errorDetails": [
 {
 "key": "REQ-2020.002080",
 "errors": [
 {
 "errorCode": "SystemException",
 "errorDescription": "Validation: Requisition number does not exist"
 }
 ]
 }
 ],
 "successDetails": []
}

Data Elements

UpdateProcessedRequisitionStatus
Property	Required?	Data type	Description	Validations/Exceptions
Model		List of UpdateProcessedDocumentStatusModel object

Model
Property	Required?	Data type	Description	Validations/Exceptions
Key	Yes	String	Key of the entity	· Key is mandatory · Invalid Requisition Number
Description	No	String	Description of the entity
Status	No	String
SourceSystemName	No	String	Name of the entity
SourceSystemValue	No	String	Value of the entity
LOB	No	String	Line-of-business
ErrorCode	No	String