GDS Remarks — Basics & remark types
Notation conventions and the core remark types Midoco reads from GDS bookings.
Notation Conventions
- Optional text – {optional text}
- Any sequence of characters (it can have length zero) – [.*]
- Any character - [.]
- Any sequence of characters with length greater or equal than 1 - [.+]
- Any digit – [d]
- At least one digit - [d+]
- GDS key – RM* or DI.FT- or M7 (bold and italic )
- GDS Remark key used in Midoco – CUSTOMER_ID: (bold and underlined)
Sabre Remark Agent Input
IUR-M7 (Itinerary Remark)
We discuourage you to use this remark in Sabre for Remarks that intend to trigger processes in Midoco. Reason: Itinerary Remarks (5¥) will appear on itinerary documents printed in Sabre and thus this information is shown on the itinerary to your travellers.
- Agent Input: 5¥ITINERARY REMARK
- example: IUR content: M701ITINERARY REMARK
IUR-M8 (Invoice Remark)
We strongly recommend to make use of this remark only in context with Midoco Midoffice.
- Agent Input: 5.INVOICE REMARK
- example: IUR content: M801INVOICE REMARK
IUR-M9 (Interface Remark)
- Agent Input: 5X/-INTERFACE REMARK
- example: IUR content: M901INTERFACE REMARK
Customer Related Remarks
Agent Remark
The agent code will be used to look up a user in Midoco Midoffice, that will be assigned to order and sell items.
In Midoco the remark value needs to be set up in User Management for the source system in this place:
AMADEUS
RM*EXPEDIENT:1234
Travelport
The segments A14 and A15 are respected.
A14FT-EXPEDIENT:1234
SABRE
The segments M7, M8 and M9 are respected.
M7[dd]EXPEDIENT-1234
Task Remark
From Release 18.0 (21. FEB 2024) this remark got extended by a task due date and can now be used by any Midoco client without the need of an additional ruleset (which was required up until that release).
As a default, the task which is created in Midoco using this remark will be of the task type 'Other' (DE: Wiedervorlage).
However, if you desire to specify a (exactly one) task type to go with the remark created tasks, please set up the task type in Task Management and ask our Helpdesk (please create ticket) to set this task type in a backgound setting for you.
This will result in any of the remark created tasks to be linked to this specific task type (regardless of GDS).
AMADEUS
- RM*TASK:DDMMMYY/NOTICETEXT
Example: RM*TASK:23NOV24/CALL CUSTOMER
Travelport
The segments A14 and A15 are respected.
- DI.FT-TASK:DDMMMYY/NOTICETEXT
Example: DI.FT-TASK:23NOV24/CALL CUSTOMER
- A14[dd]TASK:23NOV24/CALL CUSTOMER
SABRE
The segments M7, M8 and M9 are respected.
- 5.TASK-DDMMMYY-NOTICETEXT
Example: 5.TASK-23NOV24-CALL CUSTOMER
Resulting in the output in the IUR message:
- M8[dd]TASK-23NOV24-CALL CUSTOMER
User ID Remarks
If this remark is present then the creation user will be set for the following item types with the user from the remark:
- Flight
- Ticket
- Car
- Hotel
AMADEUS
- RM*USER_ID:user id
- e.g. RM*USER_ID:100
Travelport
Remark Entry in Travelport:
- DI.FT-USER-ID:user id
- A02[.*]USER-ID:user id
- A12[.*]USER-ID:user id
- A14[.*]USER-ID:user id
- A15[.*]USER-ID:user id
- A19[.*]USER-ID:user id
e.g.
A02MMEMBE/FREDMR 092860496355926807750102 ADT 01 Y
NR:USER-ID:100
A12LUNT USER-ID:100
A14USER-ID:100
A1500USER-ID:100
A190001234567890123456789012345678901234567890
R1:USER-ID:100
SABRE
- M7[dd]USER*ID-user id
- M8[dd]USER*ID-user id
- M9[dd]USER*ID-user id
e.g. M901USER_ID-100
General Note: these remarks will be added to the order
Text Remarks
Using TEXT remarks you can add predefined texts by ID as remarks to the whole order or specific sell items.
The IDs (e.g. 01) must be defined in Midoco Order Master Data → Tab DE “Bemerkungen”/EN “Remarks”. An ID, that is not found in the Master Data, will be ignored silently.
The Remarks defined in Midoco Order Master Data could be unit assigned to define a unit specific remark otherwise the remark is as global defined.
When matching the remarks by ID, a hierarchical lookup is made.
In general the syntax is: TEXT:d+{,d+{,d+}}{/Sd+}
Examples
AMADEUS | Travelport | SABRE | |
Considered Elements | RM | A14, A15 | M7, M8, M9 |
Order Remark | RM*TEXT:01 | A14[.*]TEXT:01 | M7[dd]TEXT-01 |
Multiple Order Remarks | RM*TEXT:01,02,03 | A14[.*]TEXT:01,02,03 | M7[dd]TEXT-01,02,03 |
Item/Segment Remark | RM*TEXT:01/S1 | A14[.*]TEXT:01/S1 | M7[dd]TEXT-01/S1 |
Multiple Item/Segment Remarks | RM*TEXT:01,02,03/S1 | A14[.*]TEXT:01,02,03/S1 | M7[dd]TEXT-01,02,03/S1 |
Supplier Remark
There are three remarks used to set the supplier id of flight, car or hotel items respectively.
| Remark | Description | Notes |
|---|---|---|
| SUPPLIER | set the flight supplier | segment related: changed to also work for specific segments only |
| SUPPLIER_CAR | set the car supplier | segment related: changes the car supplier for a specific segment |
| SUPPLIER_HOTEL | set the hotel supplier | segment related: changes the accommodation supplier for a specific segment |
Special Treatment for IATA EIGEN
If supplier_id is set to IATA EIGEN the Payment Type of the generated Order will be “Cash”
If supplier_id is set to IATA EIGEN:CC the generated Order is set to Payment Type CC with the Creditcard of the Ticket. If the Customer has CC-Information stored in CRM the first Creditcard will be taken.
If supplier_id is set to e.g. IATA EIGEN:CCXXXXXXXX the generated Order is set to Payment Type CC and the Creditcard which has the XXXXXXXX in the Field “Verwendung” in CRM will be taken.
AMADEUS
- RM*SUPPLIER:supplier_id
- RM*SUPPLIER_CAR:supplier_id
- RM*SUPPLIER_HOTEL:supplier_id
Travelport
- DI.FT-SUPPLIER:supplier_id
- DI.FT-SUPPLIER-CAR:supplier_id
- DI.FT-SUPPLIER-HOTEL:supplier_id
- A14FT-SUPPLIER:supplier_id
- A14FT-SUPPLIER-CAR:supplier_id
- A14FT-SUPPLIER-HOTEL:supplier_id
SABRE
- M7[dd]SUPPLIER-supplier_id
- M8[dd]SUPPLIER-supplier_id
- M9[dd]SUPPLIER-supplier_id
- M7[dd]SUPPLIER*CAR-supplier_id
- M8[dd]SUPPLIER*CAR-supplier_id
- M9[dd]SUPPLIER*CAR-supplier_id
- M7[dd]SUPPLIER*HOTEL-supplier_id/S1
- M8[dd]SUPPLIER*HOTEL-supplier_id/S1
- M9[dd]SUPPLIER*HOTEL-supplier_id/S1
Creating a Generic Item by Remark
This remark creates a generic item in Midoco.
Please make sure to always provide the VATSP information in the Remark - even if the Sales VAT is 0. It is important both for the Sales side as well as for the Purchase Accrual creation.
Additionally, please do not apply a segment relation to this remark as it is supposed to create a completely new item from scratch without any relation to any segments in the PNR. So please do not append any /Sx or /Px or /Tx at all when creating the remark in GDS.
AMADEUS - GERMAN Version (used in combination with specific backoffice suppliers)
- RM*[.*]ALLG:[SupplierID]+RD-[Start date DDMMM]-[End date DDMMM]+CF-[Booking ID]+EUR[brutto price in EUR]+UST[vatamount_vatbase]+BESCHREIBUNG[description of item] [optional: /P1]
- Examples:RM*ALLG:VISA+RD-22AUG-25AUG+CF-ZYXY45+EUR11.90+UST11.90_19+BESCHREIBUNGTICKET
- in this case a generic item is created with supplier VISA and ID ZYXY45 starting from 22.08, ending 25.08 with the description "Ticket" and a total amount of 11.90€ which are vatable with 19%
- note: if applicable there can be entered several vat bases (values) e.g. UST100_19+UST20_7 →100€ with 19% und 20€ with 7%
AMADEUS - International Version
- RM*MISC:[SupplierID]+TD-[Start date ddMMMyy]-[End date ddMMMyy]+CF-[Booking ID]+PP-[items original amount]+DESC-[description]+SP-[sales price]+VATSP[price section on which to apply VAT]_[VAT percent]+[price section on which to apply 2nd VAT rate]_[2nd VAT percent]+SETTLEMENT_TYPE-[Settlement Type]+SETTLEMENT_TYPE_DEBT-[Settlement Type Debit]
- Example:RM*MISC:TORONA+TD-22AUG20-25AUG20+CF-47TEST12+PP-1000+DESC-Lodge TEST REISE+SP-700.00+VATSP300_20+100_5+STC-CA-GBP6378+STD-CA-GBP1234+PT-HOTELEU
Travelport
- unknown
SABRE
Sabre Remarks can only contain up to 64 chars. When working with the below remark trying to transmit all the possible elements, you might find that Sabre does not allow that. So concatenating all the possible elements will most likely fail in Sabre due to the restrictions.
In this case we recommend working with templates for such items in Midoco (manually creating them) or restricting the information to a number of chars that Sabre is able to work with and than editing the item in Midoco providing the missing information. Maybe adding a Remark that creates a task in Midoco helps detecting the orders which contain items that need editing.
- M7[dd]MISC-[SupplierID]*TD-[Start date ddMMMyy]-[End date ddMMMyy]*CF-[Booking ID]*PP-[items original amount]*DESC-[description]*SP-[sales price]*VATSP[price section on which to apply VAT]_[VAT percent]*[price section on which to apply 2nd VAT rate]_[2nd VAT percent]*SETTLEMENTTYPE-[Settlement Type]*SETTLEMENTTYPEDEBT-[Settlement Type Debit]
Example: M703MISC-TORONA*TD-22AUG20-25AUG20*CF-479111*PP-2000.10*DESC-Lodge Access Airport Newark*SP-700.00*VATSP300_20*100_5*STC-CA-GBP6378*STD-CA-GBP1234*PT-HOTELEU
The Remark Elements are:
| Element | Purpose |
|---|---|
| SupplierID | set the Midoco supplier ID for the item |
| TD | Travel Dates |
| CF | Confirmation Number/Booking ID of the supplier → the one the supplier will use in their purchase invoice |
| PP | The Purchase Price of the item in the suppliers currency. (The suppliers currency is determined by the currency code set with the suppliers account payable in Chart of Accounts in Midoco. |
| DESC | The item description |
| SP | The Sales Price of the item in the units base currency. (if you are trading to an FX customer, Midoco is converting that value int |
| VATSP | The Sales Price portion and the VAT Ratio for which to apply this VAT rate The Sales Price portion and the second VAT Ratio which applies to the Sales Price |
| SETTLEMENT_TYPE / SETTLEMENTTYPE / STC | The Settlement-type credit of the item |
| SETTLEMENT_TYPE_DEBT / SETTLEMENTTYPEDEBT / STD | The Settlement-type-debit of the item |
| PT | The Product Type of the item |
Free Text Remarks
With the FTEXT remark you can add a remark with the given free text to the whole order or a specific item.
In general the syntax is: FTEXT:d+{,d+{,d+}}{/Sd+}
Examples
AMADEUS | Travelport | SABRE | |
Considered Elements | RM | A14, A15 | M7, M8, M9 |
Order Remark | RM*FTEXT:free text | A14FT-FTEXT:free text | M7[dd]FTEXT-free text |
Item/Segment Remark | RM*FTEXT:free text1;S1 | A14FT-FTEXT:free text/S1 | M7[dd]FTEXT-free text/S1 |
Settlement Type
Define the Settlement Type of an item in Midoco Midoffice - requires segment assignment of the remark.
The used settlement type value in the remark needs to be defined in Order Master Data → Settlement Types first and an according Settlement Account needs to be created for the supplier of this item to make use of that remark successfully.
AMADEUS
RM*SETTLEMENT_TYPE:settlement type;S[d+]
Travelport
The segments A14 and A15 are respected.
A14FT-SETTLEMENT-TYPE:settlement type/S[d+]
SABRE
The segments M7, M8 and M9 are respected.
M7[dd]SETTLEMENT*TYPE-settlement type/S[d+]
Settlement Type Debit
Define the Settlement Type Debit of an item in Midoco Midoffice - requires segment assignment of the remark.
The used settlement type debit value in the remark needs to be defined in Order Master Data → Settlement Types first and an according Settlement Account needs to be created for the supplier of this item to make use of that remark successfully.
AMADEUS
RM*SETTLEMENT_TYPE_DEBT:settlement type;S[d+]
Travelport
The segments A14 and A15 are respected.
A14FT-SETTLEMENT-TYPE-DEBT:settlement type/S[d+]
SABRE
The segments M7, M8 and M9 are respected.
M7[dd]SETTLEMENT*TYPE*DEBT-settlement type/S[d+]
Product Type
Using this remark you are able to set the Product Type for an item in Midoco Midoffice.
Please make sure you always work with segment assignment to successfully use this remark.
AMADEUS:
RM*PRODUCT_TYPE:<product-type>;S[d+]
Travelport:
A14FT-PRODUCT-TYPE:<product type>/S[d+]
A15FT-PRODUCT-TYPE:<product type>/S[d+]
SABRE:
M7[dd]PRODUCT*TYPE-<product type>/S[d+]
M8[dd]PRODUCT*TYPE-<product type>/S[d+]
M9[dd]PRODUCT*TYPE-<product type>/S[d+]
2 Letter Country Code
Set the County Code for passive Hotel bookings. When creating passive Hotels this additional remark offers the possibility to parse the 2-letter-Country Code of the location.
Segment assignment required.
AMADEUS
- RM*2LCOUNTRY:[value];S[SegmentNumber]
Travelport
- A14FT-2LCOUNTRY:[value]/S[SegmentNumber]
- A15FT-2LCOUNTRY:[value]/S[SegmentNumber]
SABRE
- M7[dd]2LCOUNTRY-[value]/S[SegmentNumber]
- M8[dd]2LCOUNTRY-[value]/S[SegmentNumber]
- M9[dd]2LCOUNTRY-[value]/S[SegmentNumber]
Commission Percent
Make Midoco calculate the 'expected' (calculated) commission value for an item by transmitting the commission percentage (eg. 5). Midoco will take that percentage value and calculate the expected commission value based on the item´s purchase price.
IMPORTANT: for HHL HK segments the COM-[value] information within the segment is interpreted, the below shown remark is intended to be used for GK content where there is no flat commission agreement with the supplier but where commission(percentage) is granted on an item per item decision.
AMADEUS
- RM*COMMISSIONPERCENT:[value];S[SegmentNumber]
- example: RM*COMMISSIONPERCENT:5;S1
Travelport
- A14FT-COMMISSIONPERCENT:[value]/S[SegmentNumber]
- A15FT-COMMISSIONPERCENT:[value]/S[SegmentNumber]
- example: A14FT-COMMISSIONPERCENT:5/S1
SABRE
- M7[dd]COMMISSIONPERCENT-[value]/S[SegmentNumber]
- M8[dd]COMMISSIONPERCENT-[value]/S[SegmentNumber]
- M9[dd]COMMISSIONPERCENT-[value]/S[SegmentNumber]
- example: M7COMMISSIONPERCENT-5/S1