Milestone Interface
Goal is to keep SAP up to date with status information for each milestone in the transport process provided by the carrier. Additionally Viya will map towards the SAP source system.
Requirements:
- Send
Viya-Tracking-XML
milestone update to SAP system - Mapping of Carrier/Viya codes to SAP milestone codes
- Validation of SAP codes on SAP entry
- Retrigger functionality in case of failures
SAP CPI will provide an endpoint based on the XSD provided by Viya.
Endpoint Definition
Request
- Request-Urls: :
- Request-Method: POST
- Accept: application/xml; charset=utf-8
- Accept-encoding: gzip, deflate
- TBD
Request Body
Example:
Tracking XML - Milestone Update
Specific Milestone Events:
Tracking XML - BOOKING_CREATED
Tracking XML - AWB_UPDATE
Tracking XML - DELAYED with a reason code
Tracking XML - POD
Response
Response Headers
- Content-type: application/xml; charset=utf-8
Responses:
Technical Reponses
202 Accepted
- Payload: No Content
401 Unauthorized
- Payload: No Content
500 Server Error
- Payload: No Content
503 Service Unavailable
- Payload: No Content
Function Responses
TODO: Determine endpoint response structure
Potential errors:
- Milestone event already exist
- Mapping incorrect on line X