Task: EMD Issuance

Section 1: Short Answer

Transaction Name:

DocProdEMDIssuance_10

Can any other transaction(s) perform this same task

No, only DocProdEMDIssuance_10 can perform this task.

Can this task be performed in a sessionless environment? I

Yes.

Are the request and response identical on both the Apollo and Galileo systems?

Yes, both the request and response are identical.

Industry-specific knowledge required to understand this task:

The end user must have an understanding of the booking process. The end user should also have an understanding of the Ancillary Service and EMD issuance processes.

Special limits or distinct restrictions:

Section 2: Detailed Description

Request

Unless otherwise specified, use ALL CAPS in any request data.

To issue an EMD:

  1. Retrieve the Booking.
  2. Determine and populate any Selection Criteria to be used:
  3. Determine and populate any Modifiers to be used:
  4. Submit all XML Tags in a single request.

Prerequisite tasks:

  • Book the itinerary.
  • For an Associated EMD you must also ticket the itinerary.

    • Expected response(s):

    The host in conjunction with the EMD system determines if the Issuance Request is valid. If not valid an <ErrText> element will be returned.

  • If the request is deemed valid additional data will be gathered from the booking as well as the associated PNR/BF and the EMD issuance will be performed. Up to 'n' number of EMD numbers can be generated with up to 4 coupons per EMD number.
  • The amount of data returned will depend on the Issuance request and the data in the booking as well as the rules for the carrier or carriers involved. There is really no way to define the actual high end number because the scenarios are so varied. Currently it is an average of 1-6 EMD generated per issuance entry.

    • Error and warning responses:

  • Error messages are a maximum of 64 characters and returned in the format: ERROR # - descriptive text.
  • Error messages are common to both cores. Users can find an udated list at Ask Travelport.

    • Follow-on requests:

    None.

    Section 3: Tables

    Request (Input) Tags

    <EMDIssuanceMods>

    Terminal Equivalents:

    Apollo: *rloc

    Galileo: *rloc

    Ordering

    KLR

    Min/Max

    XML Tag

    Any

    BP02

    1-1

    <PNRAddr>

     

    <EligibilityMods>

    Terminal Equivalents:

    Apollo: EMDI

    Galileo: EMDI

    Ordering

    KLR

    Min/Max

    XML Tag

    Any

    DP0H

    0-1

    <PlatingAirVMod>

    Any

    DPII

    0-99

    <AssocSegs>

    Any

    DPPI

    0-9

    <AssocPsgrs>

    Any

    DPEC

    0-1

    <EMDRFICSelData>

    Any

    DPT1

    0-1

    <TicketNumber>

    Any

    DP10

    0-1

    <CommissionMod>

    Any

    DPP1

    0-1

    <CheckFOP>

    Any

    DPP0

    0-1

    <CreditCardFOP>

    Any

    DPP9

    0-1

    <OtherFOP>

    Any

    DPEM

    0-1

    <EMDEmailSelData>

    Any

    DPEE

    0-1

    <EMDEndorsementData>

     

    Response (Output) Tags

    <PNRRetrieve>

     

    Ordering

    KLR

    Min/Max

    XML Tag

     

    See Task PNRBF Retrieve by Record Locator for details on tags returned in the PNR Retrieve response.

     

    <EMDIssuance>

     

    Ordering

    KLR

    Min/Max

    XML Tag

     

    EROR

    0-1

    <ErrText>

     

    DPET

    0-n

    <EMDIssuance>

     

    Related Samples

    DocProdEMDIssuance_10_1