Amadeus Virtual MCO User Guide
Introduction to Amadeus Virtual MCO The Automated Miscellaneous Charges Order (MCO) solution, enabling agent to Provide to the customer services in addition to the trip, being based on a printing on OPATB coupons, is no more useful on the BSP markets. The Industry being not ready yet to implement the electronic solution Electronic Miscellaneous Document (EMD), the travel agencies need an interim solution. Amadeus decided to work on a transitional solution dedicated to travel agencies Until the EMD delivery: the Amadeus Virtual Miscellaneous Charges Order (MCO). Due to increasing demand for automation of the entire passenger reservation and ticketing process, Amadeus has developed a BSP and ARC compliant Automated MCO product. This smart, userfriendly product can simplify the process of issuing an MCO for travel agencies throughout the world. The 1st of June 2008, at the IATA 100% Electronic Ticketing deadline, Amadeus launched the Amadeus Virtual MCO in all the BSP Automated MCO markets. The solution is available for all Central Ticketing System (CTS) markets, including the non Automated MCO users and ARC markets who are interested in implementing it.
Executive Summary The Amadeus Virtual MCO solution fully integrated into the whole booking process permits the travel agents to create miscellaneous documents via the system, meaning a non insignificant time saving in the daily workflow. For the Automated MCO users, the Amadeus Virtual MCO, as having kept the same functionality, is a smooth way to move toward the electronic solution EMD. Amadeus Virtual MCOs can be issued for the following key travel services (amongst others): Air or surface transportation Excess baggage charges Reissue service fees Additional collections Tax payments Hotel Payments Amadeus Virtual MCO can be issued on plain paper A4. The document is composed of the following elements: Agent coupon Audit Coupon Passenger Receipt Credit Card Charge Form There is no Exchange Coupon as no more OPATB value coupon. The customer will present at the airport the Passenger Receipt printed on plain paper.
Benefits The Amadeus Virtual MCO solution provides CTS travel agencies with the following key benefits: Automatically integrated into the PNR, the Back Office System and the Sales Reports Increased productivity due to the automated process Increased efficiency due to logical transactions Especially for Automated MCO markets: No change in data processing: _ In the functional entries _ in the information transmitted to the Back Office System _ In the Sales Reports: same transaction code MD50 and Form code easy and quick to deploy no training no additional workload for the travel agents
Virtual MCO Functionality There are three basic stages to issuing an MCO, these are: Creation Completion Processing All of which are described in detail below. MCO Creation It is possible to create a MCO either in a PNR (TY Mode), in case the commands are the same. There are two main Stages, the first is to create the MCO and the second to add in the details and print the document. The command to create the MCO includes the airline, the date, the reason for issuance as well as the fare. Of these only the first four are mandatory as the fare can easily be added later on. IMCM A/ AF NCE 12SEP/ SAR 2000.00 Parameter Mandatory / Optional IMC MCO creation command M M Indicates that the document is an MCO M A Reason for issuance M EK Airline code M NCE Airport code where the MCO has to be M Presented 12SEP Date when the MCO has to be presented M SAR 2000.00 Amount of the MCO O
There is a choice of numerous reason codes, covering the various possibilities for issuing a MCO, those currently defined by IATA are: Reason For Issuance Code (RFIC) A B G H I K M N Q U Air Transportation Surface Transportation Upgrading Under Collection Taxes Refundable Balances Sundry Charges Cancellation Fee Rebooking Fee International Excess Baggage Once a MCO has been created it is possible to see which reason codes are Available by typing in >TMI/I? e.g. TMI / B 1251234567890 - ISSUED-IN-CONNECTION WITH This brings up the display shown below
PNR Displays When the creation entry has been processed the PNR is redisplayed, and the MCO can be seen immediately below the itinerary. An Amadeus Virtual MCO can be stored in a PNR that contains any type of active segment; for example Air segments, Hotel Segments, Car Segments and any multiple or variation of these. MCOs can also be stored in a PNR that does not contain active segments provided that at least one MCO is stored per passenger. Up to 999 MCOs can be stored in the PNR and they are automatically stored in the PNR at end of transaction. Transitional Stored MCO (TSM) Once the IMC entry has been accepted Amadeus stores a Transitional Stored MPD, much in the same way that a TST is stored. The TSM can be easily displayed using one of the following entries: Request >TQM Displays a single TSM >TQM/L6 Displays a TSM on a particular line of a PNR >TQM/P1 Displays a TSM for a particular Passenger >TQM/M2 Displays a particular TSM from a list
Fare Elements In addition to the MCO fields there are several fields stored in the front of the PNR; these are the same fields as a TST. The only difference is that these have to be associated to the MPD line number, the fields that have can be updated are: Field Mandatory / Optional Form of payment Endorsements Commission Tour code Original issue (FP) M (FE) O (FM) O (FT) O (FO) O Please note that the validating carrier is not necessary as the system takes this information from the Present to area in the TSM. In order to fill out these fields there are several ways of linking them to the correct MPD, for example: Request >4/FPCASH >FT IT2AF4TEST/L4 adding in a form of payment where 5 is the MPD Line in the PNR Adding a tour code for an MPD on line 8 of the PNR PNR The line specification has to be done even if there is only one MCO in the PNR otherwise the system will attach it to the TST. In panel mode it is possible to fill in all of these details within the TSM display. An example of the PNR with the MPD details stored can be seen below
To modify any or cancel any of the fields in the PNR but within an MPD there are a few options: Request >XE4.1 To cancel the first element in the MCO on line 4 >5.2/9 Changes the second element in the MCO on Line five to 9 >4/FEVALID IB ONLY Changes the FE element for the MCO on line 4 MCO Processing Once the TSM has been completed and all of the mandatory fields are present the MCO can be issued using the following command >TTM There are numerous options that can be included in the TTM command for example: Request >TTM/P1 >TTM/L8 >TTM/RT >TTM/TMN >TTM/EML email Address >TTM/EMLN nickname >TTM/EMLA Prints all MCOs for passenger one Prints the MCO on line 8 of the PNR Prints all MCOs and retains the PNR Prints the MCO and the supplementary name List all passengers receipts are sent to the specific Address mail each passenger receipt is sent to all email Addresses included in the nickname the passenger receipt for each passenger is Sent to all email addresses stored in the APE Elements associated to this passenger
As with the TTP command these options can be linked together, for a full list options please see HEVMCO. It is also possible to print tickets and MCOs at the same time, by entering >TTP/TTM Please note that the entry has to be in this order, TTM/TTP is not permitted. Once the MCO has been printed the PNR is updated with an FB and FA line, this appears under each individual MCO as can be seen below.
MCO Processing Once the TSM has been completed and all of the mandatory fields are present the MCO can be issued using the following command >TTM There are numerous options that can be included in the TTM command for example: Request >TTM/P1 >TTM/L8 >TTM/RT >TTM/TMN >TTM/EML - >TTM/EMLN >TTM/EMLA >TTP/TTM Prints all MCOs for passenger one Prints the MCO on line 8 of the PNR Prints all MCOs and retains the PNR Prints the MCO and the supplementary name list email Address All passengers receipts are sent to the specific Address mail nickname Each passenger receipt is sent to all email Addresses included in the nickname the passenger receipt for each passenger is sent to all email Addresses stored in the APE elements associated to this Passenger as with the TTP command these options can be Linked together, for a full list of options please see HEVMCO. It is also possible to print tickets and MCOs at the same time, by entering Please note that the entry has to be in this order, TTM/TTP is not permitted. Once the MCO has been printed the PNR is updated with an FB and FA line, this Appears under each individual MCO as can be seen below.
Amadeus Virtual MCO User Guide
Introduction to Amadeus Virtual MCO The Automated Miscellaneous Charges Order (MCO) solution, enabling agent to Provide to the customer services in addition to the trip, being based on a printing on OPATB coupons, is no more useful on the BSP markets. The Industry being not ready yet to implement the electronic solution Electronic Miscellaneous Document (EMD), the travel agencies need an interim solution. Amadeus decided to work on a transitional solution dedicated to travel agencies Until the EMD delivery: the Amadeus Virtual Miscellaneous Charges Order (MCO). Due to increasing demand for automation of the entire passenger reservation and ticketing process, Amadeus has developed a BSP and ARC compliant Automated MCO product. This smart, userfriendly product can simplify the process of issuing an MCO for travel agencies throughout the world. The 1st of June 2008, at the IATA 100% Electronic Ticketing deadline, Amadeus launched the Amadeus Virtual MCO in all the BSP Automated MCO markets. The solution is available for all Central Ticketing System (CTS) markets, including the non Automated MCO users and ARC markets who are interested in implementing it.
Executive Summary The Amadeus Virtual MCO solution fully integrated into the whole booking process permits the travel agents to create miscellaneous documents via the system, meaning a non insignificant time saving in the daily workflow. For the Automated MCO users, the Amadeus Virtual MCO, as having kept the same functionality, is a smooth way to move toward the electronic solution EMD. Amadeus Virtual MCOs can be issued for the following key travel services (amongst others): Air or surface transportation Excess baggage charges Reissue service fees Additional collections Tax payments Hotel Payments Amadeus Virtual MCO can be issued on plain paper A4. The document is composed of the following elements: Agent coupon Audit Coupon Passenger Receipt Credit Card Charge Form There is no Exchange Coupon as no more OPATB value coupon.
The customer will present at the airport the Passenger Receipt printed on plain paper. Benefits The Amadeus Virtual MCO solution provides CTS travel agencies with the following key benefits: Automatically integrated into the PNR, the Back Office System and the Sales Reports Increased productivity due to the automated process Increased efficiency due to logical transactions Especially for Automated MCO markets: No change in data processing: _ In the functional entries _ in the information transmitted to the Back Office System _ In the Sales Reports: same transaction code MD50 and Form code easy and quick to deploy no training no additional workload for the travel agents
Virtual MCO Functionality There are three basic stages to issuing an MCO, these are: Creation Completion Processing All of which are described in detail below. MCO Creation It is possible to create a MCO either in a PNR (TY Mode), in case the commands are the same. There are two main Stages, the first is to create the MCO and the second to add in the details and print the document. The command to create the MCO includes the airline, the date, the reason for issuance as well as the fare. Of these only the first four are mandatory as the fare can easily be added later on. IMCM A/ AF NCE 12SEP/ SAR 2000.00 Parameter Mandatory
/ Optional IMC MCO creation command M M Indicates that the document is an MCO M A Reason for issuance M EK Airline code M NCE Airport code where the MCO has to be M Presented 12SEP Date when the MCO has to be presented M SAR 2000.00 Amount of the MCO O There is a choice of numerous reason codes, covering the various possibilities for issuing a MCO, those currently defined by IATA are: Reason For Issuance Code (RFIC) A B G H I K M N Q U Air Transportation Surface Transportation Upgrading Under Collection Taxes Refundable Balances Sundry Charges Cancellation Fee Rebooking Fee International Excess Baggage Once a MCO has been created it is possible to see which reason codes are Available by typing in >TMI/I? e.g. TMI / B 1251234567890 - ISSUED-IN-CONNECTION WITH This brings up the display shown below
PNR Displays When the creation entry has been processed the PNR is redisplayed, and the MCO can be seen immediately below the itinerary. An Amadeus Virtual MCO can be stored in a PNR that contains any type of active segment; for example Air segments, Hotel Segments, Car Segments and any multiple or variation of these. MCOs can also be stored in a PNR that does not contain active segments provided that at least one MCO is stored per passenger. Up to 999 MCOs can be stored in the PNR and they are automatically stored in the PNR at end of transaction. Transitional Stored MCO (TSM)
Once the IMC entry has been accepted Amadeus stores a Transitional Stored MPD, much in the same way that a TST is stored. The TSM can be easily displayed using one of the following entries: Request >TQM Displays a single TSM >TQM/L6 Displays a TSM on a particular line of a PNR >TQM/P1 Displays a TSM for a particular Passenger >TQM/M2 Displays a particular TSM from a list Fare Elements In addition to the MCO fields there are several fields stored in the front of the PNR; these are the same fields as a TST. The only difference is that these have to be associated to the MPD line number, the fields that have can be updated are: Field Mandatory / Optional Form of payment Endorsements Commission Tour code Original issue (FP) M (FE) O (FM) O (FT) O (FO) O Please note that the validating carrier is not necessary as the system takes this information from the Present to area in the TSM. In order to
fill out these fields there are several ways of linking them to the correct MPD, for example: Request >4/FPCASH >FT IT2AF4TEST/L4 adding in a form of payment where 5 is the MPD Line in the PNR Adding a tour code for an MPD on line 8 of the PNR PNR The line specification has to be done even if there is only one MCO in the PNR otherwise the system will attach it to the TST. In panel mode it is possible to fill in all of these details within the TSM display. An example of the PNR with the MPD details stored can be seen below To modify any or cancel any of the fields in the PNR but within an MPD there are a few options: Request >XE4.1 To cancel the first element in the MCO on line 4 >5.2/9 Changes the second element in the MCO on Line five to 9 >4/FEVALID IB ONLY Changes the FE element for the MCO on line 4 MCO Processing
Once the TSM has been completed and all of the mandatory fields are present the MCO can be issued using the following command >TTM There are numerous options that can be included in the TTM command for example: Request >TTM/P1 >TTM/L8 >TTM/RT >TTM/TMN >TTM/EML email Address >TTM/EMLN nickname >TTM/EMLA Prints all MCOs for passenger one Prints the MCO on line 8 of the PNR Prints all MCOs and retains the PNR Prints the MCO and the supplementary name List all passengers receipts are sent to the specific Address mail each passenger receipt is sent to all email Addresses included in the nickname the passenger receipt for each passenger is Sent to all email addresses stored in the APE Elements associated to this passenger As with the TTP command these options can be linked together, for a full list options please see HEVMCO. It is also possible to print tickets and MCOs at the same time, by entering >TTP/TTM Please note that the entry has to be in this order, TTM/TTP is not permitted. Once the MCO has been printed the PNR is updated with an FB and FA line, this appears under each individual MCO as can be seen below.
MCO Processing Once the TSM has been completed and all of the mandatory fields are present the MCO can be issued using the following command >TTM There are numerous options that can be included in the TTM command for example:
Request >TTM/P1 >TTM/L8 >TTM/RT >TTM/TMN >TTM/EML - >TTM/EMLN >TTM/EMLA >TTP/TTM Prints all MCOs for passenger one Prints the MCO on line 8 of the PNR Prints all MCOs and retains the PNR Prints the MCO and the supplementary name list email Address All passengers receipts are sent to the specific Address mail nickname Each passenger receipt is sent to all email Addresses included in the nickname the passenger receipt for each passenger is sent to all email Addresses stored in the APE elements associated to this Passenger as with the TTP command these options can be Linked together, for a full list of options please see HEVMCO. It is also possible to print tickets and MCOs at the same time, by entering Please note that the entry has to be in this order, TTM/TTP is not permitted. Once the MCO has been printed the PNR is updated with an FB and FA line, this Appears under each individual MCO as can be seen below.