Set Event Errors

The following errors may be encountered with the Set Event request message:

Error Code Error Messages Description
eventTime The Set Event Request cannot be processed. The eventTime is not specified. The error occurs if the source is empty or null.
The Set Event Request cannot be processed. The eventTime is not properly formatted (e.g. “2018-06-05T01:33:34.711Z”). The error occurs if the source is not in GMT dateTime format.
eventType The Set Event Request cannot be processed. The eventType is not specified. The error occurs if the source is empty or null.
The Set Event Request cannot be processed. The eventType is not valid. The eventType must be one of the following: VERIFYING, SHIPPED, RECEIVED, UNDER_INVESTIGATION, AVAILABLE, DAMAGED, DESTROYED, DISPENSED, STOLEN, SAMPLED_BY_AUTHORITIES, UNDO_SHIPPED, UNDO_RECEIVED, UNDO_UNDER_INVESTIGATION, UNDO_AVAILABLE, UNDO_DAMAGED, UNDO_DESTROYED, UNDO_DISPENSED, UNDO_STOLEN, or UNDO_SAMPLED_BY_AUTHORITIES. The error occurs if the source is present, but there is no matching entry in the lookup file.
expirationDate The Set Event Request cannot be processed. The expirationDate must be in YYMMDD format. The error occurs if the source is not in YYMMDD format.
extensionData The Set Event Request cannot be processed. The extensionData element contains invalid fields. The error occurs if the source contains any fields other than:
  • market
  • supplyType
  • po
  • salesOrder
  • return
  • transfer
  • asn
  • bol
  • packslip
  • invoice
  • destruction
  • notaFiscal
  • scriptId
locationType The Set Event Request cannot be processed. The locationType is not specified. The error occurs if the source is empty or null.
The Set Event Request cannot be processed. The locationType is not valid. The eventType must be one of the following: BR_CNES, BR_CNPJ, BR_CPF, BR_PROF_REG, COMPANYSITEID, DEA, DUNS, DUNS4, GLN, HIN, IN_LOCATION_ID, KR_BUS_REG_NUMBER, KR_PROVIDER_CODE, or SGLN. The error occurs if the source is present, but there is no matching entry in the lookup file.
locationValue The Set Event Request cannot be processed. The locationValue is not specified. The error occurs if the source is empty or null.
market The Set Event Request cannot be processed. The market is not valid. The market value must be a 2 letter ISO Code of country where event occurs. The error occurs if the source is present, but there is no matching entry in the lookup file.
productionDate The Set Event Request cannot be processed. The productionDate must be in YYMMDD format. The error occurs if the source is not in YYMMDD format.
serialNumberList The Set Event Request cannot be processed. The serialNumberList is not specified. The error occurs if the source is empty or null.
The Set Event Request cannot be processed. The serialNumberList must specify a single serial number with serialNumber, lotNumber, expirationDate, and packagingCode fields. The error occurs if the serialNumber, lotNumber, expirationDate, or packagingCode elements are empty or null.
The Set Event Request cannot be processed. The serialNumberList element contains invalid fields. The error occurs if the source contains any fields other than:
  • serialNumber
  • lotNumber
  • expirationDate
  • packagingCode
  • packagingCodeType
  • productionDate
  • variant
  • activePotency
  • nhrnPzn
  • nhrnCip
  • nhrnCn
  • nhrnDrn
  • nhrnAim
  • barcode
supplyType The Set Event Request cannot be processed. The supplyType is not valid. The eventType must be one of the following: EXPORT, FREE_SAMPLE, CIVIL_PROTECTION, EMERGENCY, DENTAL_PRACTITIONER, EMERGENCY_MEDICAL_PRACTITIONER, SPECIAL_MEDICAL_CARE_FACILITY, MEDICAL_PRACTITIONER, MEDICAL_CARE_FACILITY, MILITARY, OPTICAL_PRACTITIONER, PATIENT, PRISON, UNIVERSITY_RESEARCH_INSTITUTION, SCHOOL or VETERINARY. The error occurs if the source is present, but there is no matching entry in the lookup file.
Main Protocol Element The Set Event Request cannot be processed. The main protocol element contains invalid fields. The error occurs if the main protocol element contains any fields other than:
  • eventTime
  • serialNumberList
  • eventType
  • locationValue
  • locationType
  • extensionData
  • customData
The Set Event Request cannot be processed. The main protocol element fields found outside of the main protocol element. The error occurs if the following elements are found outside of the main protocol element:
  • eventTime
  • serialNumberList
  • locationValue
  • locationType
  • extensionData
  • customData
The Set Event Request cannot be processed. The serialNumberList fields found outside of the serialNumberList. The error occurs if the following elements are included outside of the serialNumberList element:
  • serialNumber
  • lotNumber
  • expirationDate
  • packagingCode
  • packagingCodeType
  • productionDate
  • variant
  • activePotency
  • nhrnPzn
  • nhrnCip
  • nhrnCn
  • nhrnDrn
  • nhrnAim
  • barcode
The Set Event Request cannot be processed. The extensionData element fields found outside of the extensionData The error occurs if the following elements are included outside of the extensionData element:
  • market
  • supplyType
  • po
  • salesOrder
  • return
  • transfer
  • asn
  • bol
  • packslip
  • invoice
  • destruction
  • notaFiscal
  • scriptId
The Set Event Request cannot be processed. The <duplicate namespace field> is specified more than once. The error occurs if any of the TraceLink namespace fields are specified more than once.

HTTP Response Status Codes

Smart Event Manager presents standard response codes to indicate whether or not a specific HTTP request was successful. Response status codes may include, but are not limited to, the following:

Successful response

200 OK. The request was successful. For GET, this means that the resource has been fetched.

Redirect message

307 Temporary Redirect. The client must get the requested resource at another URI with the same HTTP method that was used in the prior request.

Client error status codes

400 Bad Request. The server could not understand the request due to invalid syntax.
401 Unauthorized. The client is unauthenticated, not allowed access, and should re-request credentials.
403 Forbidden. The request is valid and the client is authenticated, but the client is not allowed access rights to the content for any reason.
404 Not Found. The server cannot find the requested item. This can also mean that the endpoint is valid but the resource does not exist.

Server error status codes

500 Internal Server Error. The server has encountered an unknown error.
502 Bad Gateway. The server is working as a gateway to handle the request and received an invalid response.
503 Service Unavailable. The server is not ready to handle the request.
504 Gateway Timeout. The server is acting as a gateway and cannot get a response in time.