ORS-Pegasus Functionality for Reservation Transmitted from Pegasus CRS to ORS and V6/V7 PMS

We will refer to the unique handling of reservation transmission between Pegasus CRS through OXI to ORS and then through OXI-HUB to V6/V7 PMS. This interface, called ORS-Pegasus is installed and configured in the same way as any OXI interface but the following will outline what is unique when this flavour of OXI is incorporated into OXI-HUB.

Requirements before this functionality will work in ORS setting:

• The existing OXI_HUB 2-way interface between ORS and V6/V7 PMS is used. This interface provides full 2-way dataflow for reservations, profiles, blocks, rates, restrictions, inventory, and stay data records from the PMS to ORS.
• Inventory synchronization between ORS and Pegasus CRS has to be maintained manually in this project phase as only reservations are submitted through the interface.
• The OXI Pegasus 2-way interface for reservations, known as OXI-PEGASUS is used between ORS and Pegasus CRS. This interface version does not support multi segment reservations from Pegasus CRS.
• The ORS database is of version 2.5
• Pegasus CRS will only contain reservations that were originally made in Pegasus. These reservations will flow to ORS and from there to PMS. All three systems Pegasus CRS, ORS, and PMS are able to modify or cancel these reservations. Pegasus will only receive changes or cancellations of reservations that have originated in Pegasus.
• Reservations originating in ORS or PMS will only be transmitted between ORS and PMS and will not flow to Pegasus.
• Channel codes will be converted in OXI to determine that the ORS booking originated in Pegasus.

Pegasus Data Element	Description	Business Rules OPERA
gn>ALN	Airline Code	If ALN is sent, OXI will try to convert it using the OXI Channel conversion table.
pnot>LCL	Location Identifier	If no ALN is sent, OXI will use LCL and try to convert it using the OXI Channel conversion table.

Alternatively and based on OXI parameter PEGASUS_CHANNEL_UPDATE parameter setting:

Pegasus Data Element	Description	Business Rules OPERA
gn>ORD	Originating Res Center ID or Source code	If ORD is sent, OXI will try to convert it using the OXI Channel conversion table.
pnot>RID	Originating Res Center ID	If no ORD is sent, OXI will use RID and try to convert it using the OXI Channel conversion table.

Note: Channel codes will be visible in all three systems, PMS, ORS, and Pegasus CRS.

Pegasus CRS Creates, Changes, or Cancels a Reservation

• The reservation is sent to ORS with the Pegasus confirmation number in the XML message tag confirmationID.
• ORS will accept this reservation with the Pegasus confirmation number.
• ORS will create a business event to send this reservation on to PMS through OXI_HUB.
• PMS receives the reservation with the Pegasus CRS number and sends the PMS confirmation number back to ORS in the XML tag reservationID.
• PMS and Pegasus numbers are stored in PMS and ORS. Both systems can search the reservation by both numbers.

Pegasus CRS Creates, Changes, or Cancels a Reservation that Originated in GDS

• The reservation is sent to ORS with the Pegasus confirmation number and the GDS locator code.
• ORS will accept this reservation with the Pegasus confirmation number and GDS locator code.
• ORS will create a business event to send this reservation on to PMS through OXI_HUB.
• PMS receives the reservation with the Pegasus CRS number and GDS locator code and sends the PMS number back to ORS through OXI_HUB.
• PMS, Pegasus, and GDS numbers are stored in PMS and ORS.

  Note: It is not possible to search by GDS locator code in V6 PMS.

PMS Changes or Cancels a Reservation that Originated in Pegasus CRS

• The reservation change is sent to ORS .
• In ORS, a business event is created for the Pegasus interface, based on an identifier to be determined, indicating that the reservation has originated in Pegasus.
• OXI sends a reservation update to Pegasus.

ORS Changes or Cancels a Reservation that Originated in Pegasus CRS

• Two business events are created for this reservation in ORS: one for the V6 interface and one for the Pegasus interface.
• The reservation change is sent to PMS through OXI_HUB and to Pegasus through OXI.

Confirmation Number Handling

It is important to understand how confirmation numbers are stored in order to understand the flow of the messages.

• Pegasus CRS will send a booking to ORS and OXI will take the CNF and GNO elements from the GN segment in the CRS message and concatenate this into the RESERVATION_NAME table in the column CONFIRMATION_NO. Therefore the Pegasus CRS number becomes the ORS confirmation number.
• ORS will then pass this booking to OXI-HUB and then to the PMS.
• The PMS will take the confirmation_no from the ORS booking and write this number into the database GRES2 in the field CRSRESNR.

  Be Aware: Make sure this column CRSRESNR in GRES2 V6 table has setting C24 in length.

• PMS will then return the REGISTER number from GRES2 and this will be stored in ORS in then RESERVATION_NAME table in the column EXTERNAL_REFERENCE.

See Also

• Extended Byte Functionality for Profiles Transmitted from ORS to External Systems and Back
• ORS and OXI_HUB for Products on Rate Code
• Interfacing Shares Between ORS and V6 PMS
• Trace and Comments Handling Between ORS and V6 PMS