Issuing Electronic Miscellaneous Documents (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.

Notes on general use:

Notes on implementation and testing:

Merchandising transactions should not be mixed between the provider system and Universal API in the copy (pre-production) system. The pre-production terminal system and Universal API pre-production system point to different environments, which causes the following two bi-directional behaviors:

Schemas

Located in AirReqRsp.xsd:

How To

An Associated EMD (EMD-A) can be issued after an Optional Service that requires fulfillment via EMD-A is sold and saved in the reservation. At least one ASVC SSR with "KD" status requiring EMD-A fulfillment must also be present. Additionally, a ticket must already have been issued for the traveler and flights for which the EMD is being issued. An ASVC SSR with a status of "KK" indicates that no EMD is required.

As of Air v45.0, EMD Issuance can be used to issue an EMD-S.

  1. Use EMDIssuanceReq to issue an EMD.

    • An EMD-A is issued to fulfill an Optional Service. An EMD-A Issuance request can be sent for a single passenger name, only after a ticket has been issued for the booking.
    • As of Air v45.0, an EMD-S is issued to collect voluntary change fees from an exchange. Release 18.3

  2. At a minimum, provide:

    • UniversalRecordLocatorCode
    • ProviderLocatorCode
    • TicketNumber (for EMD-A)

  3. For an EMD-S request, you can include the ticket number and/or SelectionModifiers/SvcSegmentRef. You can also use EMDIssuanceReq @IssueAllOpenSVC="true" to specify that all unissued SVC segments in the itinerary will be issued an EMD-S. Release 18.3

    This code snippet issues a single EMD-S and includes ticketing information and an SVC segment reference.

    <com:TicketNumber>0068667479146</com:TicketNumber>
<air:SelectionModifiers>
  <air:SvcSegmentRef Key="jhjhbjhvgjh"/>
</air:SelectionModifiers>

    This code snippet issues a single EMD-S without ticketing information. From the SVC segment reference, Universal API finds the associated passenger and ticket information. This method can only be used if the passenger has one ticket. 

    <air:SelectionModifiers>
  <air:SvcSegmentRef Key="jhjhbjhvgjh"/>
</air:SelectionModifiers>

    This code snippet issues multiple EMD-S and includes SVC segment references:

    <air:SelectionModifiers>
    <air:SvcSegmentRef Key="jhjhbjhvgjh1"/>
    <air:SvcSegmentRef Key="jhjhbjhvgjh2"/>
    <air:SvcSegmentRef Key="jhjhbjhvgjh3"/>
</air:SelectionModifiers>

    This code snippet issues EMD-S for all unissued SVC segments in the itinerary (even those created manually on Worldspan):

    <air:EMDIssuanceReq TargetBranch="ABC" TraceId="12345" 
RetrieveProviderReservationDetails="false" UniversalRecordLocatorCode="ABC123" 
ShowDetails="false" IssueAllOpenSVC="true">

     

  4. For an EMD-A request, include optional modifiers to refine the request. Note that SelectionModifiers @SupplierCode and @RFIC are optional only in some circumstances:

    • SupplierCode: Optional. Selects only the ASVC SSR for a specific carrier or supplier code. Use @SupplierCode to include the Supplier Code in the request.

      • If multiple carrier codes exist in the provider PNR for the optional services (ASVC SSR), SupplierCode must be specified or an error is returned: "ERB-NEED CARRIER SELECT TO ISSUE EMD".

      Because Interline EMDs are not supported, the SupplierCode that is specified must be for the same carrier as the TicketNumber of EMDIssuanceReq, otherwise EMD issuance fails and an error is returned: "INVALID EMD VALIDATING CARRIER".

    • AirSegmentRef: Selects the ASVC SSR for specific itinerary segments. Use AirSegmentRef @Key to include actual segment numbers, based on the Key, in EMDIssuanceReq.
    • Reason For Issuance Code (RFIC): Optional. Selects the ASVC SSR for a specific RFIC. Use @RFIC to include the RFIC in an EMD issuance request.

      • If more than one ASVC SSR exists for an optional service with different RFICs in the provider PNR, the specific RFIC code must be sent in EMDIssuanceReq or an error is returned: "ERB-EMD MUST BE SINGLE RFIC".

      • More than one Optional Service may have the same Issuance code (RFIC).
      • If multiple Optional Service have the same RFIC, an EMD is issued for all Optional Services with the same RFIC at one time. Note:
      • One, or multiple, EMDs may be issued for each Optional Service with the same RFIC number.
      • An EMD-A cannot be issued for a specific Optional Service that has the same RFIC as another Optional Service.
      • All Optional Services with the same RFIC must be fulfilled at one time, in a single EMD Issuance request. If this does not occur, the provider system will not process the additional Optional Services.

        • For example, a second checked bag Optional Service exists in a PNR, and has already been fulfilled through an EMD. Then, a new optional Service for a third checked bag, which has the same RFIC as the second checked bag, is sold for the same PNR. The provider EMD system does not allow an EMD to be issued for the third checked bag.

    • CustomerReceiptInfo: Provides the option to email the EMD customer receipt for the traveler. Use this modifier to input the email reference of the booking traveler. If an invalid Booking Traveler reference or email reference is specified in the request, an error message is returned: BookingTravelerRef or EmailRef not found.
    • EMDEndorsement: Use this modifier to send an endorsement for EMD Issuance.
    • EMDCommission: Use this modifier to enter commission.
      • @Type specifies applied value is percentage or actual amount.
      • @Value provided the value of the commission applied for EMD.
      • @CurrencyCode specifies the currency code.

    • FormOfPayment (FOP): If the FOP modifier is specified, it overrides the default form of payment in the PNR. If no FOP is specified, the default PNR FOP is chosen for EMD issuance. The FOP in the Universal Record can also be referenced in FormOfPaymentRef.

      • Notes:

      • FormOfPayment is saved in the Universal Record when it is returned in the response. See ShowDetails for information on returning Payment details.
      • When FormOfPayment in the Universal Record has Reusable="false", it cannot be referenced in EMDIssuanceReq and an error, "Form Of Payment is not reusable" is returned.
      • To reuse stored CreditCard FOP from booking in EMDIssuanceReq, credit card masking should be disabled in the PCC, otherwise this attribute will always return false.

      Universal API allows customers to provide a specific FormOfPayment element or provide any of the existing FOP references in the Universal Record. For a Credit Card FOP, CreditCard @ApprovalCode is obtained automatically, but can optionally be manually input to override the automatic process.

    Notes:

    • Split or multiple forms of payment are not valid for EMD issuance.
    • Agent FOP is not in scope for Worldspan (1P) or Galileo (1G) because the provider EMD systems restrict its use.

    A warning message is returned in EMDIssuanceRsp if an FOP is not supported by the provider:

    Different FOP might be used by carrier for EMD issuance than the one specified in the input.

    The following are unsupported FOPs, by Provider:

    • Worldspan (1P): AccountRecievable and AgentNonRefundable.
    • Galileo (1G)/Apollo (1V): MiscFormofPayment@Category = "CreditCard", Requisition @Category=Government and @Type=Credit

    If ShowDetails=false (default) or is not included:

    • A follow-up EMD list request is sent by Universal API and the EMDSummaryInfo element is returned in EMDIssuanceRsp.
    • The Payment and FormOfPayment are not returned in the EMDIssuanceRsp.

    If ShowDetails=true:

    • A follow up EMD Details is sent by Universal API for each of the primary EMDs issued in the response and the EMDInfo element is returned in EMDIssuanceRsp.
    • The Payment and FOP are returned in the EMDIssuanceRsp. Payment and FormOfPayment are saved in the Universal Record.

  5. By default, the ticketing form of payment is used to collect an EMD. Specify a different form of payment using IssuanceModifiers/FormOfPayment.

  6. Universal API retrieves the PNR and synchronizes the Universal Record (UR) when the EMDIssuanceRsp is returned.

Response Details

Exceptions

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