Академический Документы
Профессиональный Документы
Культура Документы
OCTOBER 2017
V2.92
Document Use
The following is intended to outline our general product direction. It is intended for information purposes only, and
may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and
should not be relied upon in making purchasing decision. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of Oracle.
DOCUMENT VERSION
Document Use 1
1 Features and Requirements 1
1.1 Posting 1
1.2 Inquiries 1
1.3 Setup 2
1.4 Update 2
2 EMC Configuration 3
2.1 Extension Application 3
2.1.1 Create a record 3
2.1.2 Insert the content 4
2.1.3 Configure the content 4
2.1.4 Multi Tenant Environments 5
2.2 Content Information 6
2.2.1 Posting related configuration 7
2.2.2 Guest-Locator and Guest-Message related configuration 8
2.3 Interfaces 9
2.3.1 Extension application Interface option 11
2.4 Revenue Center Configuration 12
2.5 Data Extensions – Add the Tender Media Extra Column 12
2.6 Tender Medias 13
2.6.1 Room Charge Payment setup 14
2.6.2 Enable the Room Charge option 15
2.7 Page Design 15
2.8 Features and Revisions as of version 2.70 and higher 17
Hardware/Software:
1.1 Posting
Up to 16 Sales Itemizer
Up to 64 Tax Itemizer
16 Discount Itemizer if "Full Discount and Service Charge breakdown" is configured accordingly, otherwise 1
Discount Itemizer
Up to 14 Service Charge Itemizer if "Full Discount and Service Charge breakdown" is configured accordingly,
otherwise 2 Service Charge Itemizer
Check Details in the final tender event.
1.2 Inquiries
Enhanced inquiry by name or room number returning the following information (varies and depends on the
setup on the PMS):
Guest last name, first name and title
Arrival and departure dates
Room number and room type
Display of guest reservation detail
Display of guest history
Display / printing of guest messages
Entry of guest messages
Display of guest locator
Entry of guest locator
Start the setup application on the Simphony Application Server and follow the instructions shown. This will verify
the Simphony installation and copy the required files into the folder \MICROS\Custom\EnhancedInterface.
If you are unable to run the setup application on the Simphony Application Server because of access or user right
limitations but if you can access EMC from your local PC you will also be able to start the setup application with the
parameter /LOCAL, i.e. assuming version number 270:
SIMPH2_ENH_IFC270.exe /LOCAL
This will not verify the Simphony installation and it is your responsibility to ensure that the Simphony requirements
are met. This will copy the required files into the sub-folder Custom\EnhancedInterface below the folder you
selected in the setup application.
Files:
1. CONTENT_EnhIFC_Config.txt
2. McrsExtDialogsML.dll
3. MF_ENH.isl
4. MF_ENH_Android.isl
5. android.htm
1.4 Update
To update an available installation, it is required to execute the provided setup application on the Simphony server.
The application will update/create the custom folder under \MICROS.
Follow step 2.1.3 to reimport the ISL and DLL files into the extension application
(Only the import file procedure).
Double check the installation manual, if additional data extensions are required
(step 2), if yes create this/them.
Follow the steps below to configure and install the SIM Opera Interface within the Enterprise Management Console
(EMC).
1. Navigate to the EMC | Setup tab | under Custom Content | Extension Application
2. Select the 'Insert' icon and add a record (record number of your choice).
3. For the record name, any name will suffice. In this example, the record was named Opera.
4. Select the 'OK' button.
Open the new record in Form view (by double-clicking the record).
Select the 'Insert Application Content' button. It is required to insert 4 application content records:
Select the 'Content Type: 19 - SimScript' and click on the 'Import from a file' link.
Select the SIM file MF_ENH.isl (*.isl), press the OPEN button.
Set the target to WIN32.
Insert a new application content for the DLL file named McrsExtDialogsML.dll, content type “3 - DLL”. Zoneable
Key, Description = “McrsExtDialogsML”.
Insert a new application content for the Android form file named android.htm, content type “23 - Text”. Zoneable
Key, Description = “html”.
For the SIM files MF_ENH.isl and MF_ENH_ANDROID.isl records, click on the ellipsis (...) symbol under the
'Options Bits' column and enable Option [2 - Main SIM Content] and click the 'OK' button.
For each file, type in their entire file name under the 'Disk File Name' column and Save all changes.
NOTES:
The Disk File Name must match (Case sensitive) the name of the SIM scripts and DLL file names!
The Zoneable Key for the android.htm file must match “html”, case sensitive!
For multi-tenant environments it is required to configure the content information (outlined in chapter 2.2) as
Extension Application content as in such environments the content feature cannot be used.
Create a new Application Content for the enhanced interface, selecting the “Insert Application Content” button.
The ZoneableKey must be set to “EnhIFC_Config” (case sensitive), the description must be set to
“EnhIFC_Config” (case sensitive).
Select the content type “23 –Text”, insert the content information as outlined in chapter 2.2 Content Information.
Apply the configuration settings as required.
#-----------------------------
# Posting related settings
#-----------------------------
#Magnetic Card required for Posting (0 or 1)
MAGCARDONLY=0
#if above enabled, excl. RVC Numbers (separated by comma)
MAGCARDOVRWRT=
#Suppress Guest-Messages during Postings
SUPPRESSGSTMSG=1
#Suppress References of non-Roomcharge Tenders
SUPPRESSNFOREF=0
# Do not display Guest Confirmation during Postings
NO_CONFIRM_GST=0
#Send negative Guest Count if payment is negative
REVERSEGST=1
#Full Discount and Service Charge breakdown
FULL_DSVC=1
#Use 64 Taxes for posting (0 or 1) or just 8 Taxes
POST_64TAXES=1
#Determines which information to be posted, 0 = Serving Period, 1 = Trans.Cashier,
# 2 = Order-Type, 3 = Custom for Philippines ONLY. Default = Serving Period
POSTING_ADD_INFO=0
# Send all CheckDetails on non-Roomcharge Tenders
SendAllDtls=0
#-----------------------------
# Locator related settings
#-----------------------------
#Use RVC Name as Locator Line #1
RVCNAMELOC=1
#Default Locator Validity in Minutes
LOCVALIDMIN=30
#--------------------------------
# Guest Message related settings
#--------------------------------
#Populate first line of Message using Date/Time, RVC# and Trans.Employee#
EMPLINFO_IN_MSG=1
#-----------------------------
# Restricted Posting for Kiosk Environment
#-----------------------------
RESTRICTED_POSTING=1
#Must match the ISL Employee Option in Employee Class
RESTR_POSTING_EMPL=8
The Content can be overwritten per Zone, Location or RVC. If overwritten, please ensure that you select the
Option "Use Existing Record":
Navigate to the EMC on the Enterprise level under the Setup tab | Hardware/Interfaces | Interfaces and insert a
record for the Opera 'PMS' interface.
* The screenshot above is an example, please utilize a name which outlines the property using the interface.
To avoid double postings the PING Frequency must be 0 (Zero), it is required to create an interface for each
property.
Click on the 'Options' tab and enable the desired options and enter the Opera PMS application server's
connection information under the 'TCP Communications' header and Save all changes.
Click on the 'Properties' tab and enable the Opera PMS interface for each desired Property and Save all changes.
Click on the 'Service Host' tab and select the desired Service Host for the Opera PMS interface and click the 'OK'
button and Save all changes.
Note: The service host can be any workstation that has enough power to handle the incoming queries.
Navigate to the EMC Enterprise level | Setup tab | Custom Content | Extension Application file and under the
'Interface' column, select the PMS interface to link it to the Opera Extension Application record and Save all
changes.
Navigate to the Property level | Configuration tab | Sales | Tender/Media | and create a Room Charge Tender
Media record. Configure the generic options as required.
Click on the 'Options' tab | Interface Options tab and select the PMS interface from the 'Interface Link' dropdown
menu (The name of the interface link and the option “View Interafce Names for RVC” are only available when the
Tender Media configuration has been done at property level.
The Interface link must be set for all of the payments that need to be auto balanced (e.g. Cash, Credit
Cards, .etc)
The value must be checked for the room charge tender media(s) (see above), uncheck for all of the other tender
medias. But not greyed out, see sample screenshot below.
Add the inquire buttons on any required page/tab, normally the inquire buttons are created on the payment and/or
function page/tab.
remark (1): Amount of any PERCENTAGE based Service-Charges based on the SVC Itemizer (1-8) and the
Menu-Items present on the check. For AMOUNT based Service-Charge based on the FIRST active SVC Itemizer
found (if any).
remark (2): Only used with AMOUNT based Service-Charges with no SVC Itemizer enabled.
Please note that enabling a more detailed breakdown of Service-Charges will require related changes on the
PMS/IFC8 side. As such coordinate any change with the PMS team.
CONNECT W ITH US
blogs.oracle.com/oracle Copyright © 2015, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
facebook.com/oracle warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means,
twitter.com/oracle electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
oracle.com
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0615