Message Data Elements for Pegasus OXI

This topic contains the following Message data elements for custom interfaces in OXI:

Pegasus – used by Fairmont Hotels, Le Meridien Hotels, and others

Segments in Pegasus AMF messages for Reservations:

• NOT.Notification type
• pnot.Identifies operator ID, location, reservation center – always 1
• gn.Reservation segment – always 1
• nm.Name segment – 1 to 9
• ad.Address segment – 1 to 3
• dep.Deposit segment – optional 1
• phone.Phone segment – optional 1 to 5
• email.Email segment – optional 1 to 4
• cost.Cost segment – always 1
• curseg.Currency segment – always 1
• bseg.Booking segment – can be 1 to 25
• rtseg.Rate segment – at least one per bseg
• bkmsg.Booking message segment – optional, many possible
• faxto.Fax segment – always 1

FM_GDW – used by Fairmont Hotels in combination with the Pegasus 2-way interface

This interface creates the following files after the CLOSE BUSINESS DATE business event has been created:

FID_RYH_EOS_0802199800DHR114.DAT

• This file contains a record for every guest with a departure date for the date for which the file is created. This includes cancellation and no show for the same date.

FID_RYH_GBX_YYYYMMDD.DAT

• This file contains a record for every group block that has an active date.

FID_RYH_PKX_YYYYMMDD.DAT

• This file contains a record for all packages built in the PMS.

FID_RYH_RCX_YYYYMMDD.DAT

• This file will contain a listing of all defined Rate Codes.

FID_RYH_RTX_YYYYMMDD.DAT

• This file will contain a listing of all defined Room Types.

FID_RYH_SRX_YYYYMMDD.DAT

• This file will contain a listing of all defined Special Service Codes.

FID_RYH_FOLIO_YYYYMMDD.DAT

• This file will contain a listing of all folios.