Booking Name Booking Travel Date Booking Agent Name Booking Consultant Name System Date. :t Include current time Fixed Text Booking Travel Date (Repeated) Booking Header Total Adult Pax Booking Header Total Children Booking Header Total Infants Full Booking Reference (Branch, Department, Reference Number) Booking Agent Reference Booking Currency (Code) Booking Total Retail Amount (From) Booking Travel Date (To) Booking Last Service Date Fixed Text Indicates begining of Body/Lines Section of message. Supressed on output. Indicates begining of Default lines format. Supressed on output. Service day of the week. :cp - Output is not repeated for subsequent services on the same day/date.<rms:row> will remove the entire row if there is no substitutable data in the entire row. Date of Service. :cp - The output is not repeated for subsequent services on the same date. Service Location Description. :cp - The output is not repeated for subsequent services on the same day/date/location. Product Service Type Description Product description/name Service Currency Code Service Retail Amount. :tl = Total for all components of the service Service Line Status Description Product Supplier Name Number of adult passengers having this service Additional Items available with the product and included. <rms:row> - If no data is substituted, completely remove the table row. Passenger name title - Mr, Mrs, Master, Ms, etc. <<names:start>>/<<names:end>> Indicators to show where pax names are to be output. Passenger Christian/Forename Passenger Surname/Family Name Passenger Type - Adult, Child or Infant The row containing the <<AC>> format code is removed on message output Service day of the week. :cp - The day name is not repeated for subsequent services on the same day/date.<rms:row> will remove the entire row if there is no substitutable data in the entire row. Date of Service. :cp - The date is not repeated for subsequent services on the same date. Service Location Description. :cp - The output is not repeated for subsequent services on the same day/date/location. Service Second Charge Unit Quantity (2) and Description (Night). Service Supplier Name - in conjunction with fixed text. Product Description. Because of the length of the line, the name has wrapped to the next line. Quantity & type(s) of room. TW=Twin, DB=Double, SG=Single, TR=Triple, QD=Quad, OT=Other. :0 = If room type is not used, suppress output. Number of adult passengers having this service Additional Items available with the product and included. <rms:row> - If no data is substituted, completely remove the data row. Passenger name title - Mr, Mrs, Master, Ms, etc. <<names:start>>/<<names:end>> Indicators to show where pax names are to be output. Passenger Christian/Forename Passenger Surname Passenger Type - Adult, Child or Infant User full name. The row with <<SERVICES:END>> (above 'End of Tour Arrangements') has been removed.

Template Configuration

The message template consists of three basic parts - the Header, the Body (or "Lines") and the Tail. The Header and Tail are where text and data which relates to the Booking is formatted, and the Body is where detail relating to the individual services of the booking is formatted.

The Header and Tail are not identified in any way in the template - they are assumed to exist in the context of the document type. So for example, in a booking agent message, the area outside of the body/lines is assumed to be the header and/or tail.

The substitution codes which output specific fields of data are enclosed in single chevron brackets - < > - e.g. <bn> will substitute the Booking Name.

A higher level of codes - enclosed in dual chevron brackets - << >> - are used to define sections within the template that have specific data types in them - e.g. optional services, or to indicate specific sections of the message - e.g., pax names.

In addition to section codes and substitution codes, there are conditional codes which are used to assist with the formatting and output of the message - e.g., removing blank rows or containing email send commands.

The message template Body (Lines) Section can have different Line formats to suit different types of message and different types of service. In addition to information such as supplier name and address etc., services like Transfers need to show a pick-up date, time and place and a drop-off date, time and place; Sightseeing services need a service date (and possibly time); accommodation services need in date, out date, room types, meals etc. Products have a Message Format Type Code attached to them which tells the system which format type to use for each product when the message is being generated. In the event that a product does not have a Service Format Code attached, a "Default" format type must be included in each message template to allow some detail to be output for those products.

The example message in Message Configuration was created using this template.

Although there are Default, AC (Accommodation), EF (Entry Fees), ME (Meals), TF (Transfers) and PK (Package Tour) in the template, only the Default and AC service formats were used in the booking. They are detailed below, since only products with those message format codes were in the simple booking.

Hover the mouse over the <SUBSTITUTION> codes in the template sections below to see a description. Click the code to see the substituted text. Not all template service formats have been included.
Those codes that have double chevron brackets around them - e.g. <<SERVICES:START>>, <<SERVICES:END>>, <<DEFAULT>>, <<AC>>, <<EF>> etc are automatically removed during message generation. They are indicators in the template that show where specific formatting or data types are to be output. See Messaging Template Sections.

The code <rms:row> does not have any output and is not featured in the graphics below. It is used to remove an entire row from a table if there is no data returned by any substitution code that follows it.

Message Header Section

Message Body Section - <<Default>> Service Format

Message Body Section - <<AC>> Accommodation Service Format

Message Tail Section

The Tail section starts immediately after the <<SERVICES:END>> tag. The booking conditions mentioned in the tail are fixed text and have been removed to conserve space.