Retrieving EMDs

Fulfillment of Optional Services for which an ASVC SSR was created, and which indicates EMD-A issuance is required via a KD status, is done via EMD. Universal API supports the issuance, listing, displaying of Associated EMDs (EMD-A).

As of Air v45.0, EMD Issuance supports issuing Stand-Alone EMDs (EMD-S) for Worldspan (1P). Release 18.3

As of Air v45.0, EMD Issuance supports issuing a single or multiple EMD-S in a single transaction. However, you cannot issue both EMD-S and EMD-A in a single request. Release 18.3

After an EMD is issued or retrieved, the Universal Record is updated with basic EMD details, as part of the Universal Record synchronization (UniversalRecordRetrieveRsp). If EMDs are issued using terminal commands and then imported from the provider into a Universal Record in Universal API, the EMD details are also imported and display in the response (UniversalRecordImportRsp). EMD details are captured in the Universal Record History.

EMD Issuance and the Security services (role management and creation) do not support emulation.

Schemas

Located in AirReqRsp.xsd:

• EMDRetrieveReq
• EMDRetrieveRsp

How To

1. Use EMDRetrieveReq to retrieve the Universal Record and view the details of the association between the EMD and the Optional Service. Note that settings in EMDIssuanceReq affect the association of the EMD and Optional Service in the EMD that is retrieved:
   • If EMDIssuaneReq@ShowDetails=“false”:

   The list of EMDs is returned. In the EMDIssuanceRsp, EMD coupon level details are not available, so only the EMD reference is added to OptionalService/ServiceData.

   • If EMDIssuaneReq@ShowDetails="true":

   Complete details of the EMDs are returned, and both Reference and EMD Coupon reference are added to OptionalService/ServiceData.

2. Retrieving a List of EMDs in the PNR

   Use EMDRetrieveReq to retrieve a of list of EMD transactions for a provider PNR. Optionally, if the PNR does not exist within a Universal Record, it may be imported before retrieving a list of EMDs. If a UR has already been created, the below warning will be returned:
   <common_v50_0:ResponseMessage Code="0" Type="Warning" ProviderCode="1G">PNR already exists in Universal Record XXXXXX</common_v50_0:ResponseMessage>

   Although issuing an EMD-S is not available at this time, the EMD list returns EMD-S as well as EMD-A. The Universal Record is updated with the basic EMD data for any new EMD numbers that are returned in the list response. The Universal Record History is updated with the EMD numbers that are added to Universal Record as part of EMDRetrieveReq and EMDRetrieveRsp.

   When EMDRetrieveReq is sent to list all EMDs, it must contain the ProviderLocatorCode and the Provider. The EMD retrieve list response returns the following in EMDSummary:

   • Number: The EMD number.
   • PrimaryDocumentIndicator: "True" indicates the primary EMD. "False" indicates a conjunctive EMD.
   • InConjunctionWith: The primary EMD number, if the EMD is conjunctive.
   • AssociatedTicketNumber: The e-Ticket number associated with the EMD.
   • PlatingCarrier: The carrier code for which the EMD is issued.
   • IssueDate: The date the EMD is issued.
   • EMDTravelerInfo: The traveler’s information, such as name and traveler type.
3. Retrieving Specific EMD Details

   Use EMDRetrieveReq to retrieve specific details of an EMD and each of its coupons. When EMDs are conjuncted, retrieving one EMD retrieves all the coupons for all the EMDs in the set.

   At a minimum, EMDRetrieveReq for specific details must contain the EMD number. The EMD is synchronized with the provider PNR when the specific details are returned in EMDRetrieveRsp.

   EMD details can be retrieved for an EMD in a PNR outside of a Universal Record (UR) using EMDNumber in the request. In that scenario, no EMD details are saved in any Universal Record. If EMD details are retrieved from a PNR that is part of a Universal Record, the UR is updated with the basic EMD data and the new EMD number that is returned in the detail retrieve response.

   Note: Retrieving an EMD-S list is not currently available, but EMD-S details can be retrieved. Universal API provides no specific support for EMD-S retrieval at this time.

Notes:

• If new EMDs are added to the Universal Record using EMDRetrieveReq or when the Universal Record is synchronized, the EMD is associated with the Optional Service.
  • If an EMD list is retrieved, only the EMDSummary reference is added to OptionalService/ServiceData.
  • If EMD detail is retrieved, both EMDSummary and EMDCoupon reference are added to OptionalService/ServiceData.
• If an EMD is re-issued, the EMD reference is changed in the OptionalService/ServiceData to reflect the newly re-issued EMD for that optional service.
• In the EMDRetrieveRsp, An enhancement in Universal API 20.4.2 allows the ability to show credit/debit card information when retrieving e-ticket and EMD information through Universal API to reconcile data with BSP. For example, in an AirDocumentRetrieve request, when credit/debit card information is present in the booking and the customer opts in for unmask functionality, Universal API returns credit/debit card information unmasked ONLY if the agency or signon settings allow. Otherwise, credit/debit card information returns masked. This functionality is applicable in Air Retrieve Document, Air Merchandising Fulfillment, and EMD Issuance / Retrieve Release 20.4

  • xPath = EMDRetrieveRsp/EMDInfo/FormOfPayment/CreditCard

  • For EMDIssuance and EMDRetrieve, Universal API will continue to show masked credit/debit card information until an enhancement is completed in the EMD application.

  • The EMD enhancement is scheduled for Q1, 2021.

  • This is limited release functionality . Please contact your Travelport representative to activate this enhancement.

Exceptions

Airline Content Hub (ACH) does not support the EMD Issuance functionality.