Enterprise Resource Planning
System and Message Overviews
Document Version: 5.2
Date: March 3, 2014
Copyright © 2009-2021 Jeppesen. All rights reserved. Your use of the AIM Bookshelf and all supporting documentation is subject to a separate license agreement between you and Jeppesen, a copy of which is included in the zip file or can be obtained from Jeppesen. The AIM Bookshelf is delivered "AS IS" without warranty of any kind and is not guaranteed to be free from errors or defects. You rely on the AIM Bookshelf at your own risk. No support for the AIM Bookshelf is implied through its publication. The AIM Bookshelf is intended solely for use as a reference and examples of interfaces to Jeppesen systems. Jeppesen may revise, update or cease publication at any time, without notice. Building to the specifications set forth in the AIM Bookshelf does not mean that your intended integration needs will be met or that an interface will function as documented. We recommend contacting Jeppesen directly to discuss professional services options with respect to production application integration and validation efforts.
Document Revision History
The following revision history table reflects all substantive changes to this document.
Table Of Contents
This document defines the interfaces which govern the interchange of data between an ERP system and other systems within an Airline Operation Center (AOC). Each AOC interface is represented by a message described in an associated XSD (XML Schema Definition). The XSD defines and enforces the required, optional, and conditional data that can be included in a message.
ERP messages support new customer account creation and maintenance, and transaction billing.
The intended audience for this document includes existing and potential Jeppesen customers, integration partners, and personnel with roles associated with application architecture, application development, system testing, implementation, and application support within ERP.
This document discusses the ERP messages currently supported by the Jeppesen Solution Integrator. Each message description includes the following:
Other data interfaces or formats not included in this document will be considered custom and not supported.
The XML schema for this ICD is published in the following file: EnterpriseResourcePlanning.XSD
Table 2-1 lists the messages that can be sent or handled by the application. The messages originated by this application (messages that begin with “EP”) are further discussed in Section 3 AOC Interface Messages.
The following messages are processed by the ERP system.
3.1 EP001 – Create Customer Account
The tables presented in this section describe how customer account records are created. The content of each table describes a type of message that either requests an action or responds to the request. For example, a message type may request that a new data record be created. For each request message type, there is a corresponding response message.
This message interacts with the systems as shown in Figure 1.
The following table provides details on the message version and includes links to the message’s technical specification.
The tables presented in this section describe how customer account is verified for validity and currency. The content of each table describes a type of message that either requests an action or responds to the request. For example, a message type may request information concerning the validity and status of a user account. For each request message type, there is a corresponding response message.
This message interacts with the systems as shown in Figure 2.
The following table provides details on the message and includes links to the message’s technical specification.