This capability allows the delivery provider to request and receive the order information from the airline for the fulfillment of services without using tickets and EMDs..
Not applicable
Concepts: Orders: https://standards.atlassian.net/wiki/spaces/EASD/pages/574717963
Capabilities: Orders: https://standards.atlassian.net/wiki/spaces/EASD/pages/574259560
Worked Examples: Orders: https://standards.atlassian.net/wiki/spaces/EASD/pages/574619770
For all capabilities, please also consult the list of general guidelines for adherence to best practices that span across several capabilities and messages: |
Demonstrate passing the Delivery Provider(s) the order information and delivery service statuses from the airline for the fulfillment of services.
Flow of service delivery status can be referenced in the EASD Implementation Guide: https://guides.developer.iata.org/v212/docs/esd-def
XML message traces and screenshots of order management will be required for verification. Messages and screenshots should demonstrate the change of delivery service statuses and the change within the Order due to the change in delivery service status.
For capability ORDDEL, airline must reach READY TO PROCEED delivery service status.
Minimum Requirements | Optional Messages |
---|---|
ServiceDeliveryNotifRQ | ServiceDeliveryRQ/RS |
Acknowledgement | UpdateServiceNotifRQ |