ORS Routing Instructions

ORS (OPR <version number>ORS license code) has functionality where users can enter Window or Room routing instructions while creating and modifying reservations, before the reservation has been checked in. Routing instructions let you automatically forward charges for specific routing codes (defined groups of transaction codes) incurred by one or more guests to another guest's bill at the time of posting. This functionality had previously only been available in PMS. Now, it exists between OPERA to OPERA: ORS to OPMS.

Once the reservation is checked in, users will not be able to make further routing changes. Neither will any payment details or changes that occurred in PMS appear in ORS. ORS will just transfer the routing instructions, while all payments are handled in the PMS system. To accommodate this functionality, the OXIHUB Interface has a conversion code called Routing Code where the mappings of routing codes between ORS and PMS are set up. In addition, a report is available that will print billing instruction configuration, Cf_billinginstruction - Routing Codes.

From the Routing Instructions screen, you can use routing instructions from one reservation to another reservation. These routing instructions will be transferred between ORS and OPMS through the OXI interface.

Application Settings

The following application settings must be activated.

Select Application Settings>Cashiering>Function>Routing. When this function is activated, the following parameter becomes visible.
Select Application Settings> Cashiering>Parameter>Allow Routing of Tax Transaction.

User Permissions

The following user permissions will be activated based on the Routing parameter. Assign users these permissions:

Routing under Cashiering group
View Routing under Cashiering group
Routing Codes under Cashiering Config group

Routing Codes Configuration

Select Configuration>Cashiering>Routing Codes. The Routing Codes screen appears. Refer to Routing Codes. Users can configure one routing code as a group of multiple transaction codes on the Routing Codes screen.
When making a new reservation (Reservations>Sales Screen>New), on the new Reservation Screen, the Option menu contains a Routing button. It allows users to attach a Window routing to the reservation. Reservation charges can be instructed to route to a different profile attached to the reservation. Once entered, the routing instructions Routing lamp will be lit on the reservation screen. Refer to Routing Transactions.
A Profile can have default routing instruction codes attached to it (Profiles>Profiles>Property>More Fields). The user has to select the property on the profile screen before going to the routing code field. When the user goes to the Profile screen/More Fields tab, the routing instruction field will be visible and user can select one or more routing codes and transaction codes. Refer to More Fields Tab. During a reservation, when the user selects this profile the system will ask if the default routing instruction exists on the profile, do you want to attach?
A Rate Code (Configuration>Rate Management>Rate Classifications>Rate Codes) can have default routing instruction codes attached to it. When users go to the Rate Setup screen/ More Tab, the routing instructions field will be visible and the user can select one or more routing codes and transaction codes. Refer to Rate More Tab. For example, GBPRATE has routing code Beverages attached to it. When the user selects this rate code while saving the reservation, the system will ask if you want to attach the default routing instruction that exists on the rate code.

Note: In a PMS and ORS environment (when the OPR<version number>ORS license code is active) routing codes can be transferred between the two programs for shared contact, company, travel agent, source, or vendor profiles (this does not apply to transaction codes - only routing codes). When a routing code is added to a profile in PMS, in ORS that same profile is updated with the routing code. Likewise, in ORS when a routing code is set for the profile, that profile in PMS will update and contain the routing code from ORS. For this process to occur, either a) identical routing codes must already be configured in both programs or b) routing code conversion codes must be set up between the two systems in OXI-HUB (Interface Conversion>Conversion Codes). If identical routing codes do not exist in both programs, or if conversion codes have not been set up, the profile will stage when the system validates the routing codes during the transfer. The profiles can be matched and merged through Profile Merge (Options>Merge) or in ORS>Suspended Profiles. When routing codes are removed from one profile (in ORS or PMS), the codes will be removed from the other profile. When routing codes are removed, the system makes them inactive and they are not visible to the user anywhere in the application.