Exception Endpoint
Exception Responses / process
Exceptions for the GS1-TI endpoints will result in a callback to a status endpoint and/or an mail to the person responsible for the process.
Depending on the exception a change in ERP can be made and the process can be retried or a issues is raised to resolve the technical problem.
Most common exceptions:
Exception Endpoint
- Request-Urls:
- Request-Method: POST
- Accept: application/xml; charset=utf-8
- Accept-encoding: gzip, deflate
- x-api-pat:: {{PAT_TOKEN}}
- messageId: Unique id for this message
Exception example
Exception XSD
Exception Structure:
- originalMessageId = MessageID as provided by the incoming messageID header from SAP
- resourceReference = EntityIdentification as provided by SAP GS1-TI (optional)
- title = A short, human-readable summary of the problem type.
- status = The HTTP status code generated by the origin server for this occurrence of the problem.
- detail = A human-readable explanation specific to this occurrence of the problem.
- instance = A URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
- type = A URI reference that identifies the problem type. (mostly
about:blank
) - timestamp = datetime the exception occurred
- errors = Optional array of errors
- error
- code = Error Code provided by Viya or Carrier
- message = Human readable summary of the error description
- explanation = Optional explanation with suggestion for recovery
- error
To Be Discussed:
Exception list:
- InvalidXML
- InvalidXMLAccordingToSchema
- InvalidXMlNamespace
- ComsignmentNodeNotFound
- ConsignorBuilding not present
- ConsignorBuilding ‘XXX’ not found
- ConsigneeBuildingNotFound
- ConsgineeBuilding < 4 Characters
- ConsgineeBuilding ‘XXX’ Not Found
- InvalidAWB
- InvalidModeOfTransport
- InvalidGS1TiContentException
- AlreadyBookedException
- RefusedByCarrier (+ reason)