Oracle® Hospitality Simphony

Fiscal Layer
Simphony Norway Installation Manual

Version 4.0.1.3.
Oracle Hospitality Simphony Norway Fiscal
February 2019
Oracle Hospitality Oracle® Hospitality Simphony Fiscal Layer Simphony Norway Installation Manual, Release
4.0.1.3.
Oracle Hospitality Simphony Norway Fiscal
Copyright © 2013, 2019, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use
and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license
agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit,
distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you
find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of
the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any
programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific
supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs,
including any operating system, integrated software, any programs installed on the hardware, and/or
documentation, shall be subject to license terms and license restrictions applicable to the programs. No other
rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It
is not developed or intended for use in any inherently dangerous applications, including applications that may
create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be
responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.
Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or
hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
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.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise
set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be
responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,
products, or services, except as set forth in an applicable agreement between you and Oracle.
Contents
Preface 4

1 Requirements 1-1
Installer Rights & Privileges 1-1
System Requirements 1-1

2 Introduction 2-1

3 Installation 3-1
Data Extensions 3-1
CAL Package 3-3
Extension Application Installation 3-4

4 Simphony EMC Configuration 4-1

Workstation Setup 4-1
X or Z Reports 4-1
Tender Media - Setup 4-5
Tax Rates - Setup 4-7
Enterprise Level Setup 4-7
Page Design 4-9
SAF-T (Standard Audit File – Tax) 4-10

5 Backup 5-1
Backup Setup 5-1

6 Fiscal Service Standalone Installer 6-1

7 Extended Data Posting - Reporting & Analytics 7-1

Application Server Settings 7-1

8 Effective Reporting 8-1

Reporting 8-1

Troubleshooting A-1
Fiscal Layer Architecture A-1
Logging A-3

iii
 Preface

Preface
Purpose
This document outlines installation steps and features included in the Oracle Hospitality
Fiscal Interface for Oracle Hospitality Simphony for the Norway market.
This document does not describe the installation nor configuration process for third party
fiscal devices. For those information refer to the documentation provided by
manufacturer.
Audience
This document is intended for all consultants installing and configuring Oracle
Hospitality Simphony in Norway, as well as to the employees providing software
support for mentioned product.
Customer Support
To contact Oracle Customer Support, access My Oracle Support at the following URL:
https://support.oracle.com
When contacting Customer Support, please provide the following:
• Product version and program/module name
• Functional and technical description of the problem (include business impact)
• Detailed step-by-step instructions to re-create
• Exact error message received and any associated log files
• Screenshots of each step you take
Documentation
Product documentation is available on the Oracle Help Center at
https://docs.oracle.com/en/industries/food-beverage/
Revision History

Date Description of Change

16-Feb-2018 • Initial publication (GR)

19-Sep-2018 • Documentation update

05-Oct-2018 • Changes to Tax Mapping

• New function introduced Reprint Closed Check with Extension
Application
• Data Extension update, naming changed to
FLC_NO_ServiceChargeCode
• Order Types support Tax Classes with multiple Tax Rates
enabled

05-Dec-2018 • Added data extension (FLC_RecCopyCount)

21-Jan-2019 • Support for Transaction Services has been introduced

iv
 Preface

Date Description of Change

• New button which allows user to perform reprint of previously
printed Z-Report’s
• New alignment method for Article Group Codes added
(Micros.FiscalClient.Mapping.xml)
• Added new Data Extensions for an automatic backup of Fiscal
Data (FCR Journal table), NO_BackupAuditExportTime,
• NO_BackupAuditExportPath,
• NO_BackupAuditImportPath, NO_BackupAuditEnabled
• Added new data extension FLC_UsedForChangeDue to be set
as the payment which is used to issue change due
• Updated Tender Media – Setup chapter with explanation of data
extension for this module

04-Feb-2019 • Extention Application Installation section updated – File

SQLLite.Interop.dll was excluded from the list.

20-Feb-2019 • Export from backup section updated - default SAF-T Audit Table
Export Path provided.

v
 Chapter 1
Requirements

1
Requirements
The following chapter outlines user privilege level to successfully implement Oracle
Hospitality Simphony Norway Fiscal.zip software and system requirements.

Installer Rights & Privileges

Before starting installation process, installer should ensure if following rights and
privileges are granted. Especially for hosted environments, it is necessary to request
assistance from a Cloud Operations Team in case of required modifications on the
Enterprise or Zone levels.
• Access to the Simphony Enterprise Management Console (EMC)
• Adding and editing Extensibility Application on the Property or Zone levels
• Adding and editing Content on the Property or Zone levels
• Access to the Page Design module
• Installation package Oracle Hospitality Simphony Norway Fiscal.zip

System Requirements
The solution was tested with the following components, which should be considered as
the system requirements. Usage of any other hardware or software version, even if
compatible, require a separate quality assurance process.
• Oracle Hospitality Simphony 2.9 or later
• Oracle Micros Workstation 6 (Windows 8.1 Embedded Industry Pro and Windows 10
64-bit)
• Other Oracle Micros Workstation units running one of the following operating system:
o Windows 8.1 Industry Pro
o Windows POSReady 7
o Windows POSReady 2009

1-1
 Chapter 2
Introduction

2
Introduction
This manual is intended to be used as a guide by all consultants who install and
configure Oracle Hospitality Simphony Norway Fiscal Layer -4.0.1.3
The purpose of this manual is to be a reference providing detailed information to support
a successful installation and to complete all mandatory configurations in order to comply
with Norway Regulations.
After a successful installation, the enhancements listed below should work properly:
Receipt Printing Control: Sales receipts must be printed each time. Only one copy of the
sales receipt can be printed as on demand. Each printed documentation has electronic
signature assigned by the system. The printout will have the header and identifier for the
workstation.
Fiscal Reports: It is required to print X / Z Report on demand. When a Z-Report is run /
printed the counters and sales figures in Current Total Set should be set to zero except
for The Grand Totals. The X and Z reports should be printed / displayed on any Cash
Register. The Z-Report has a unique counter increased every time it is run.
Electronic Journal: allows to export on demand report, which is called SAF-T Export
which includes all sales transactions and all data related to those transactions. Besides
fiscal related transactions the export contains also configuration changes (e.g. Vat rate
changes, Menu Item / Service Charge name change or Menu Item Price change). SAF-T
Export might be asked and checked by the auditor.
Functions to be removed: There are not allowed functionalities which are listed below
should be removed. It is not enough to check if prohibited function is disabled, it must be
ensured that not allowed function will not be executed.
• Reopen closed check
• Adjust closed check
• Have positive and negative transactions printed on the same check
• Possibility to carry out registrations in the cash register system if the integrated cash
drawer is open

2-1
 Chapter 3
Installation

3
Installation
Data Extensions
Installation starts by adding Data Extensions at the Enterprise level to extend and meet all legal requirements.
1. Open EMC and log onto providing username and password
2. Go to Enterprise | Configuration | Reporting and Data | Data Extensions
3. Click Insert and add the following rows as listed in the table below
4. Remember to provide the exact name into the Extra Column Name as this field is case sensitive and will not work if
mismatched.

Table 3-1 - Data Extension

Is Downloadable
Extra Column

Translatable

Translatable
Sort Priority
Constraints

Is Viewable
Is Editable
Display
Width
Name

Name
Table

Type
Nr. #

Help
Data

1. 41 - Workstation FLC_NO_CashRegisterId 0 - Text Max Chars: 0 150 [NO] Cash Register [NO] Cash Register Identifier   
128 Identifier

2. 70 - Service Charge FLC_NO_ServiceChargeCode 2- Range: 0- 0 150 [NO] SAF-T Service [NO] Service Charge Code   
Number 999999999 Charge Code

3. 71 – Tender Media FLC_NO_PaymentCode 2- Range: 0- 0 150 [NO] SAF-T Payment [NO] Payment Code   
Number 999999999 Code

4. 71 – Tender Media FLC_PaymentType 2– Range: 0- 0 150 [FLC] Fiscal Payment [FLC] Fiscal Payment Type. 0 –Cash, 1 – Credit   
Number 999 Type Card, 2 – Other, 3 – Room Charge

5. 71 – Tender Media FLC_RecCopyCount 2- Range: 0-9 0 150 [FLC] Number of [FLC] Allows to specify how many copies of the   
Number Receipts Count same fiscal receipt can be printed

6. 71 – Tender Media FLC_UsedForChangeDue 2- Range: 0-1 0 150 [FLC] Change Due [FLC] Allows to set a payment (usually cash) which   
Number should be used to issue change due

3-1
 Chapter 3
Installation

Is Downloadable
Extra Column

Translatable

Translatable
Sort Priority
Constraints

Is Viewable
Is Editable
Display
Width
Name

Name
Table

Type
Nr. #

Help
Data
7. 1001 – Property FLC_NO_OrgNumber 0 – Text Max Chars: 0 150 [NO] Official [NO] Official Organization No.   
128 Organization No.

8. 1001 – Property FLC_NO_OrgName 0 – Text Max Chars: 0 150 [NO] Official [NO] Official Organization Name   
128 Organization Name

9. 1001 – Property FLC_NO_Passphrase 0 - Text Max Chars: 0 150 [NO] Unique [NO] Unique Passphrase   
128 Passphrase

10. 1001 – Property FLC_ZReportNoPrintTender 2– Range: 0- 0 150 [FLC] Z Report No [FLC] This tender is utilized by X/Z Reports to   
Number 999999999 Print Tender create zero receipt thus entire report will be
recorded in POS Journal

11. 1001 – Property FLC_ZReportPrintTender 2- Range: 0- 0 150 [FLC] Z Report Print [FLC] This tender is utilized by X/Z Reports to   
Number 999999999 Tender create zero receipt thus entire report will be
recorded in POS Journal

12. 1001 - Property FLC_AnonymousChkTtlTrsh 2- Range: 0- 0 150 [FLC] Check Total [FLC] Check Total Amount Threshold   
Number 999999999 Amount Threshold

13. 1001 - Property NO_BackupAuditExportTime 6 - Time HH:mm 0 150 [NO] SAF-T Audit [NO] SAF-T Audit Table Export Time   
Table Export Time

14. 1001 - Property NO_BackupAuditExportPath 0 - Text Max Chars: 0 200 [NO] SAF-T Audit [NO] SAF-T Audit Table Export Path   
200 Table Export Path

15. 1001 - Property NO_BackupAuditImportPath 0 - Text Max Chars: 0 200 [NO] SAF-T Audit [NO] SAF-T Audit Table Import Path   
200 Table Import Path

16. 1001 - Property NO_BackupAuditEnabled 2- Range: 0-1 0 150 [NO] Enable/Disable [NO] Option for enabling/disabling backup audit   
Number Backup Audit Export export. 0 – Disabled, 1- - Enabled.

3-2
 Chapter 3
Installation

CAL Package
The custom CAL Package is responsible for distributing and installing Oracle Fiscal
Layer Service (a.k.a. the MICROS Fiscal Service) on the workstation in the property set
in their Deployment Schedule.
This part of configuration should be performed on Enterprise level and may need an
assistance from Cloud Operation Team in case the installer has no proper rights granted.
The CAL Package files are included into Fiscal Layer Installation Package Oracle
Hospitality Simphony Norway Fiscal archive.

Create New CAL Package

How to import a new custom CAL Package:
1. Navigate to the EMC | Enterprise | Setup | CAL Packages from the
Hardware/Interfaces module.
2. Expand the tree and highlight the Custom node.
3. Select Add Custom CAL Package from the options available at the bottom.
4. Select the folder NOOracleFiscalService in the unzipped archive and click OK. The
folder can be found under Oracle Hospitality Fiscal
Service\WIN32\Packages\NOOracleFiscalService.

Figure 3-1 - Add Custom CAL Package Location

5. From the Confirm CAL package upload window, use the default values that are
suggested by the EMC (NOOracleFiscalService).
6. Once the import of the new CAL Package is finished, set the Deployment Order
value to 2 on the CAL Package Configuration tab.
7. Next, move to the Deployment Schedules tab and Add Deployment for properties
which are obligated to use this interface.
8. Click Save. All workstations are rebooted after a successful installation.

3-3
 Chapter 3
Installation

Extension Application Installation

The Micros Fiscal Layer Client Extensibility Application is responsible for connecting
operations in an Oracle Hospitality Simphony Service Host with a Fiscal Layer
Service.
The extensibility application files are included in Oracle Hospitality Simphony Norway
Fiscal Layer.zip archive under the Extension Application folder.
The following section describes installation steps of the Extension Application for
Oracle Hospitality Simphony.
1. Copy the file, for example, Oracle Hospitality Simphony Norway Fiscal.zip to your
local hard drive.
2. Unzip the installation package folder.
3. Open EMC and logon providing your username and password.
4. An Extension Application can be added at the Enterprise, Property, Revenue
Center, or Zone levels. It is up to you to decide at which level or zone the Extension
Application is added.
5. Choose your desired level (listed on step 4) and navigate to Setup | Custom
Content | Extension Application.
6. From Extension Application click Insert.
7. Provide Record Name(s): Micros.FiscalLayerClient. This name is case sensitive
and must be entered as presented, and click OK.
8. From Table view, enter the value of 2 in the Type column.

Figure 3-2 - Extension Application Module

9. Enter the previously created record, Micros.FiscalLayerClient, and click Insert

Application Content to add the first file, BouncyCastle.Crypto.dll.
a. Enter the same exact name to the ZoneableKey field, for example,
BouncyCastle.Crypto and enter the same name for the Description field,
BouncyCastle.Crypto.
b. Click OK.
c. From the new window, select 3-DLL from drop-down list in the line Content
Type.
d. From the right side of the window, click the Import from a file link.

3-4
 Chapter 3
Installation

e. Find the BouncyCastle.Crypto.dll file on the server or on your local hard drive.
f. Click Open.
g. From the same window, click the General tab.
h. From the Disk File Name column, enter the exact name of the file and its
extension, BouncyCastle.Crypto.dll.
10. Repeat the same steps from points 9-a through 9-h (above) for the next four files:
• FiscalLayerClient.Common.dll
• Micros.FiscalLayerClient.dll
• Micros.KeyManagerService.dll
• System.Data.SQLite.dll
11. Once again double-click the Micros.FiscalLayerClient record and add three more
files. Set the Content Type to 23-Text for all three files and repeat the same steps
from points 9-a through 9-h (above).
a. Micros.FiscalClient.Properties.xml template (the fiscal client configuration
template Micros.FiscalClient.Properties.xml stores the country specific
configuration for Fiscal Layer Client application as well as message translation.
This configuration is set on the release level and this is not recommended to
modify the content, because its content structure is validated by the application
and must match to expected).
b. Micros.FiscalService.Properties.xml template (the fiscal service configuration
template Micros.FiscalService.Properties.xml stores the template of the
configuration for Fiscal Layer Service that is deployed by CAL Package. Some of
the configuration settings that are not exposed to end user, as such security
device specific settings, maximum log file size, location and others are
configured only inside this template and should be manually modified before
loading content into EMC).

3-5
 Chapter 3
Installation

c. Micros.FiscalClient.Mapping.xml template. More information is available in

SAF-T – Article Group Codes (Family Groups)

Figure 3-3 - Extension Application Designer

WARNING:
Note that the extensibility application is initialized when a ServiceHost starts.
To ensure that the extensibility application is loaded properly, run a full reload
of the database on each workstation, and then restart the terminal. After that,
verify the version of the application using a configurable built in function (see
Page Design section).

3-6
 Chapter 4
Simphony EMC Configuration

4
Simphony EMC Configuration
This chapter describes the configuration process that is performed through the Simphony
Enterprise Management Console (EMC). The following sections are mandatory.

WARNING:
Performing sales operations are not possible if any of the following areas of
configuration are not performed or skipped!

Workstation Setup
It is absolutely necessary to insert an additional row in the Data Extension module called
[NO] Cash Register Identifier. This row identifies workstations in the fiscal interface and
is required by the interface to properly function.
Follow these steps to set up the fiscal enhancement (data extensions) for each
workstation:
1. Navigate to EMC | Setup | Workstations from Hardware/Interfaces module at the
Property level.
2. Double-click on the workstation record and navigate to the Data Extensions tab.
3. Set the cash register identifier in the row [NO] Cash Register Identifier (max 128
characters).
4. Repeat for each workstation.
5. Click Save.

X or Z Reports
There are two reports introduced:
• X-Report
• Z-Report
The intention of these reports is to give you the ability to print reports without closing a
business date or to allow you close a business date. When one business date ends you
are forced by the system to execute a Z-Report before any sales can be booked. If the Z-
Report is executed more than once during the same business date, you need to keep in
mind that each time, the totals on the report are generated from zero.
If for any reason a Z-Report is not executed for a number of days, the system reminds
you that before any sales can be booked, you are forced to close as many days as the
number of Z-Reports that are missing.

4-1
 Chapter 4
Simphony EMC Configuration

The X-Report allows you to preview sales during the day. There are no additional
functions behind this report. It can be printed as many times as you want.
Once the X/Z Reports are generated, a database table in the CheckPostingDB is
populated with the content of the printed report to the POS_JOURNAL table.
Like any other additional functionality, this one requires two data extensions (they were
added few steps earlier). One is intended to print the report and the second one is to
save the data without print output (FLC_ZReportPrintTender and
FLC_ZReportNoPrintTender).
Those functions are reflected on the actual report, under Save and Print and Save
buttons respectively.
There are certain rules while counting amounts on X/Z Reports:
1. The Total Slag does not include transactions like:
• Transaction Voids
• Transaction Returns
• Discounts
2. Proforma line counts only those checks that have been service totaled and
physically issued for a customer. Refer to Tender Media - Proforma.
3. Vekslekasse INN line represents all Paid In amounts registered with a specially
configured Tender Media (key type set as 4 - Loan).
4. Vekslekasse UT line represents all Paid Out amounts registered with a specially
designed Tender Media (key type set as 3- Pickup).

Figure 4-1 - Z-Report Output

4-2
 Chapter 4
Simphony EMC Configuration

Z-Report – Daily Summary Report (Close Business Day)

The Z-Report is a daily summary of the registrations at the particular cash register and
must be executed per cash register daily (not the entire system). By running the report,
you agree that the business date is almost over and the totals on the report are about to
be reset.
It is recommended to generate a Z-Report before posting the first transaction for a new
business date (by business date, we understand a time frame from the last time a Z-
Report was executed). You are prompted by the system if a Z-Report was not executed
on that workstation and reminds you to run the report!

NOTE:
It is recommended to have all checks closed before running a Z-Report. It
allows you to have similar data on the Z-Report and Simphony core reports
and ultimately helps avoid discrepancies. Otherwise, report totals do not
match.

X-Report – Daily Summary Report (Preview)

The X-Report works in a very similar way as the Z-Report. The only difference is that it
does not reset daily sales totals. It is intended to give you the ability to print/generate
unlimited copies of the report during the business date. By business date, we understand
that daily sales totals accumulate from the point that the last Z-Report was executed.
To be able to use mandatory reports you need to configure additional Payments in the
Tender Media module. Without those two payments it won’t be possible to use buttons
on the reports such as Save or Save and Print.
Add two Tender Media records to allow the X/Z Reports to work properly.

NOTE:
The Record Numbers (99998 and 99999) used on the screen captures below
are only examples. It is up to an implementation specialist to decide which
number ranges are used by these two additional Tender Media payment
records.

Follow the steps outlined below:

1. Choose the desired level in EMC (Enterprise, Property, Revenue Center, or Zone)
and navigate to Configuration | Sales | Tender/Media.
2. Click Insert and create a new record for the ZReportPrintTender.

4-3
 Chapter 4
Simphony EMC Configuration

a. From the Insert Record window, enter 99998 in the Record number or range
field and then enter ZReportPrintTender in the Record Name(s) field.

Figure 4-2 - Tender Media Insert Record Window

b. Open the Form view of the previously created record, and select the General tab
and set the Key Type as 1 – Payment.
c. Click the Options | Printing Options tab and enable these options:
• 8 – Print Customer Receipt
• 23 – Print Check on Demand
d. Select the Menu Levels tab and enable all Main Levels and all Sub Levels.
e. Select the Output tab and enable the Print on Customer Receipt, Print on
Guest Check, and Print on Journal options.
f. Click Save.
g. Click Insert to add the second payment record.
h. From the Insert Record window, enter 99999 in the Record number or range
field, and then enter ZReportNoPrintTender in the Record Name(s) field.

4-4
 Chapter 4
Simphony EMC Configuration

Figure 4-3 - Tender Media Insert Record Window

i. Open the Form view and select the General tab and set the Key Type as 1 –
Payment.
j. Select the Menu Levels tab and enable all Main Levels and Sub Levels.
k. Select the Output tab and enable the Print on Journal option.
l. Click Save.

It is not required to set the [FLC] Fiscal Payment Type fiscal enhancement row for those
two payment types. More information about Payment Fiscal Types can be found in the
next chapter.

Tender Media - Setup

The Tender Media module was enhanced with the [FLC] Fiscal Payment Type data
extension to properly define payment types such as cash or credit cards. All means of
payment types are tracked in the Journal Export file.
There is one more data extension in the Tender Media module called [NO] SAF-T
Payment Code which allows you to pair a particular payment type with the proper audit
number for SAF-T Export purpose. More information about which number should be
assigned to specific payment types can be found in the SAF-T – Payment Codes (Tender
Media) section.
1. Navigate to EMC | Configuration | Tender/Media.
2. Double-click on the tender media record and select the Data Extensions tab.
3. Set the payment type for the [FLC] Fiscal Payment Type by inserting one of the
following values:
• 0 – Cash (all payments which are considered cash)

4-5
 Chapter 4
Simphony EMC Configuration

• 1 – Credit Card (all payments which are considered credit or debit cards)
• 2 – Other (any other payment type)
• 3 – Room Charge (only for room charge payments connected to a property
management system (PMS) interface)
4. Repeat for each payment that should execute the fiscal printing when used.
5. Click Save.
Here is information about two more data extensions designed for Tender/Media:
• [FLC] Number of Receipts Count – Allows you to limit number of fiscal receipt
copies printed for one transaction
• [FLC] Change Due – Allows you to set which tender media is used to issue
change due while closing transactions with pre-defined payments like 100 Euro,
50 Euro, and so on. In such situations, the change due is displayed and
calculated on the X/Z Reports with this particular tender media. It is strongly
recommended to use this option with only one CASH Payment configured in the
system!

Tender Media - Proforma

A Proforma is a paper copy of not closed transaction and not signed yet. Mainly in the
Oracle Hospitality Simphony this is a situation where a Service Total button was used
to send an order and store the check for a later purpose.
The section below outlines how to configure to have a Proforma counted on the X/Z
Reports and also how to avoid printing and incrementing the count number.
How to make Proforma countable on the X/Z Report and printable
1. Navigate to EMC | Configuration | Tender/Media.
2. Find any Tender Media with the key type set as a Service Total.
3. Ensure that both option bits are set like:
• 13 - Print Memo Check – enabled
• 19 - Reprint Check – enabled
4. Click Save.

How to make Proforma non-countable on the X/Z Report, but printable

1. Navigate to EMC | Configuration | Tender/Media.
2. Find any Tender Media with the key type set as a Service Total.
3. Ensure that both option bits are set like:
• 13 - Print Memo Check – disabled
• 19 - Reprint Check – enabled
4. Click Save.

4-6
 Chapter 4
Simphony EMC Configuration

How to make Proforma non-countable on the X/Z Report and non-printable

1. Navigate to EMC | Configuration | Tender/Media.
2. Find any Tender Media with the key type set as a Service Total.
3. Ensure that both option bits are set like:
• 13 - Print Memo Check – disabled
• 19 - Reprint Check – disabled
4. Click Save.

Tax Rates - Setup

The Tender Media module was enhanced with data extension [FLC] Fiscal Payment
Type to properly define payment types like cash or credit cards. All means of payment
types are tracked in the Journal Export file.
1. Navigate to EMC | Setup | Taxes and Order Types | Tax Rates on the Enterprise,
Property, or Zone level.
2. In the Tax Rates module, customize one of 64 available tax rates.
3. Start entering from highest tax rate.
a. Name: VAT 25% Standard (it can be any other name, this is just an example)
b. Type: 3 – Included, Percentage
c. Percentage column: 25,00
d. Repeat steps from a through d for the following tax rates VAT 15%, VAT 12%
and VAT 11,11%
4. Click Save.
There is one additional column in Tax Rates module which needs to be customized (Tax
Codes). This column is intended to map tax rates configured in Oracle Hospitality
Simphony with SAF-T codes required by the Norwegian government to be able to
correctly report sales figures. The configuration for this column is explained later in this
document in chapter SAF-T – Standard VAT Codes (Tax Rates).

Enterprise Level Setup

There are certain enhancements that can be made at the Property level. Perform the
following steps to setup fiscal enhancements for a property.
1. Go to Enterprise | Setup | Enterprise Configuration and Properties.
2. Double-click the desired property and go to Data Extension.
3. Enter information about the property in the following rows:
a. [NO] Official Organization No. – Official registered company identification
number used in SAF-T file - mandatory field, cannot be empty.

4-7
 Chapter 4
Simphony EMC Configuration

b. [NO] Official Organization Name – Official registered company name used in

SAF-T file - mandatory field, cannot be empty.
c. [NO] Unique Passphrase – Enter a passphrase with a minimum length of 8
characters for security reasons. This will ensure that workstations within this
property are able to communicate - mandatory field, cannot be empty.
d. [FLC] X/Z Report No Print Tender – Object number of payment X/Z Report No
Printout mandatory field, cannot be empty otherwise you won’t be able to run an
X/Z Report.
e. [FLC] X/Z Report Print Tender – Object number of payment X/Z Report With
Printout mandatory field, cannot be empty otherwise you won’t be able to run an
X/Z Report.
f. [FLC] Anonymous Chk Ttl Trsh – *Optional. Allows you to set a check
threshold value.
g. [NO] Enable/Disable Backup Audit Export – *Optional. It could be enabled for
any customer who wishes to use an automatic backup of an FCR Journal table
which data is used to generate SAF-T Export. Enter 1 (one) to enable the
automatic daily backup.
h. [NO] SAF-T Audit Table Export Time – *Optional. Allows you to program a time
when a backup of an audit table should occur. More information is located in the
Backup chapter.
i. [NO] SAF-T Audit Table Export Path – *Optional. Allows you to set a
destination folder where the backup of the audit table is stored for SAF-T export
purposes. More information is located in the Backup chapter. If path is not set the
export will be saved in default folder which is located in
C:\Micros\Simphony\WebServer\DefaultBackupExportFolder.
j. [NO] SAF-T Audit Table Import Path – *Optional. Allows you to set an import
folder for a Journal on Demand operation. More information is located in the
Backup chapter.
k. Click Save.

WARNING:
As a result of not filling out mandatory fields, a message appears on the POS
client screen while logging onto the device, reminding you that the
configuration is not accurate or valid.

4-8
 Chapter 4
Simphony EMC Configuration

Page Design
This section describes the functionality provided by the Fiscal Layer Interface. Built in
functions can be accessed through a configurable button on a touchscreen.

Page Design – Button Configuration

The following steps describe how to add particular function buttons and link them to fiscal
extensibility application. A listing of all of the functions are available in the table below.
1. Navigate to the EMC | Configuration | User Interface | Page Design on the
desired configuration level.
2. Open the Page on which you want to add the touchscreen function key.
3. Click Button in upper left corner of the Page Design module and configure it as
follows:
a. Type: Function
b. Function#: Run Extensibility App
c. Arguments: listed in Table 4-1: Arguments (below)
d. Copy the entire argument for each function from Table 4-1: Arguments
below.
e. Click Save.

Table 4-1 - Arguments

# Button Name Description Arguments

1. Fiscal Version Display information about Type=DLL;AppName=Micros.FiscalLayerClient;FileName=Micros.Fi
fiscal interface version in scalLayerClient.dll;Script=version;Arg=""
use
2. Z-Report Prints Z-Report Type=DLL;AppName=Micros.FiscalLayerClient;FileName=Micros.Fi
scalLayerClient.dll;Script=z-report;Arg=""
3. X-Report Prints X-Report Type=DLL;AppName=Micros.FiscalLayerClient;FileName=Micros.Fi
scalLayerClient.dll;Script=x-report;Arg=""
4. Z-Report Reprint Allows to reprint Z-Report Type=DLL;AppName=Micros.FiscalLayerClient;FileName=Micros.Fi
by workstation, by date scalLayerClient.dll;Script=z-report-reprint;Arg=""
and by report number
5. Validate Journal Checks and validates Type=DLL;AppName=Micros.FiscalLayerClient;FileName=Micros.Fi
fiscal data scalLayerClient.dll;Script=journal-validation;Arg=""
6. Export Journal Exports journal to a file in Type=DLL;AppName=Micros.FiscalLayerClient;FileName=Micros.Fi
xml format and stores at scalLayerClient.dll;Script=journal-export;Arg=""
workstation
7. Journal Backup Allows to export fiscal data Type=DLL;AppName=Micros.FiscalLayerClient;FileName=Micros.Fi
Export from audit backup scalLayerClient.dll;script=journal-backup-export;arg=""
8. Reprint Closed Allows to reprint closed Type=DLL;AppName=Micros.FiscalLayerClient;FileName=Micros.Fi
Check check just once scalLayerClient.dll;Script=reprint-closed-check;Arg=""

4-9
 Chapter 4
Simphony EMC Configuration

Button clarifications:
• Fiscal Version – Shows the version of fiscal interface and validates if all required
Data Extensions were added to configuration.
• Z-Report – Allows you to close a business date.
• X–Report – Allows you to print / preview report. It can be run multiple times.
• Z-Report Reprint – Allows you to reprint a previously printed Z-Report by
workstation, Report Date, or Report Number
• Validate Journal – This function allows you to validate if data is correct. Once the
function is called from CAPS, it checks the data on the CAPS workstation. When the
function is called from a NON CAPS WORKSTATION, it sends a request to CAPS
and awaits the replay. When a connection cannot be established, then you receive
an error message.
• Export Journal – Exports data into the xml file format in a predefined location at the
CAPS Workstation in C:\Micros\FiscalLayer\Reports. The Export Journal
process can be started at any other workstation on the property, but connection with
CAPS is required. The SAF-T Export file is created and stored on the workstation
which called the action, and is placed in the location
C:\Micros\FiscalLayer\Reports. The SAF-T Export file is validated during
the export process.
• Reprint Closed Check – This feature was introduced to limit reprint of the copies to
only one for each closed check. All built in functions such as the Reprint Closed
Check or Reprint Previous Closed Check are disabled by the fiscal interface.
• Journal Backup Export – Allows you to export fiscal data from a previously archived
FCR Journal table. This button lets you to create the SAF-T Export file, but this time
from historical (archived) files. This button works only in a situation where the [NO]
SAF-T Audit Table Import Path is populated with backup files. More information is
located in the Backup chapter.

SAF-T (Standard Audit File – Tax)

The following chapter and further subchapters outline how to configure your system to
meet Norway fiscal regulations. Without this required configuration, the SAF-T Export
does not work. Furthermore, without this configuration, your system complains at each
step of a POS Operation while logging onto the POS client and while attempting to close
a transaction. Read carefully.
The SAF-T Export file is an electronic copy of transactions and is stored in the .xml file
format on a CAPS workstation.
It is customer’s responsibility to keep sales data safe as per fiscal requirements in
Norway. It is recommended to perform a Journal Export directly on the CAPS
workstation as it contains sales data from all workstations in the property.
The other way to export files is to set an automatic export time at the Property level (read
the previous chapter carefully) and set the following data extensions [NO] Backup Audit
Export Time, [NO] Backup Audit Export Path, [NO] Backup Audit Import Path, and
[NO] Enable/Disable Backup Audit Export. More information is located in the
Enterprise Level Setup chapter.

4-10
 Chapter 4
Simphony EMC Configuration

SAF-T – Article Group Codes (Family Groups)

In order to ensure accuracy and compliance with Norway fiscal requirements, Oracle
Hospitality Simphony is required to have all Family Groups mapped to the
PredifinedBasicIDs from Table 4-2 below.
The following article group codes were delivered by the Norwegian Government as
guidance. As you will see, not all are applicable and can be simply deleted. Later in this
document, you will be presented a default file and same after customizations.
The system does not control if your configuration is correct!
Table 4-2 - Predefined Basic ID04 - Article Group Codes
PredefinedBasicID Article Group Names
1. 4001 Withdrawal of treatment services
2. 4002 Withdrawal of goods used for treatment
services
3. 4003 Sale of goods
4. 4004 Sale of treatment services
5. 4005 Sale of haircut
6. 4006 Food
7. 4007 Beer
8. 4008 Wine
9. 4009 Liquor
10. 4010 Alcopops/Cider
11. 4011 Soft drinks/Mineral water
12. 4012 Other drinks (tea, coffee, etc.)
13. 4013 Tabaco
14. 4014 Other Goods
15. 4015 Entrance fee (cover charge)
16. 4016 Free entrance (members, etc.)
17. 4017 Cloakroom fee
18. 4018 Free cloakroom
19. 4019 Accommodation - full board
20. 4020 Accommodation - half board
21. 4021 Accommodation - with breakfast
22. 4999 Other

1. Open EMC.
2. At the main window choose your desired level (Enterprise, Property, Revenue
Center, or Zone), and navigate to Setup | Custom Content | Extension
Application.
3. In the Extension Application, double-click Micros.FiscalLayer.Client and open the
previously added Micros.FiscalClient.Mapping.xml record.
4. In each line of the Micros.FiscalClient.Mapping.xml file, change the value when:

4-11
 Chapter 4
Simphony EMC Configuration

a. following Article Group Code is to be used in the property, then make the
proper adjustment and change the wording Family Group Number to the
existing/corresponding Family Group number from Oracle Hospitality
Simphony (as shown in Figure 4-4 presented on the next page)
b. following Article Group Code is not be used in the property, then the entire line
can be deleted and the fiscal interface omits its validation.
5. Click Save.
Figure 4-4 - Template Configuration Micros.FiscalClient.Mapping.xml File
<?xml version="1.0" encoding="utf-8" ?>
<ArticleGroupCodesMapping>
<code nr="04001" dsc="Withdrawal of treatment services">Family Group Number</code>
<code nr="04002" dsc="Withdrawal of goods used for treatment services"> Family Group Number
</code>
<code nr="04003" dsc="Sale of goods">Family Group Number </code>
<code nr="04004" dsc="Sale of treatment services">Family Group Number</code>
<code nr="04005" dsc="Sale of haircut">Family Group Number</code>
<code nr="04006" dsc="Food ">Family Group Number</code>
<code nr="04007" dsc="Beer">Family Group Number</code>
<code nr="04008" dsc="Wine">Family Group Number</code>
<code nr="04009" dsc="Liquor">Family Group Number</code>
<code nr="04010" dsc="Alcopops/Cider">Family Group Number</code>
<code nr="04011" dsc="Soft drinks/Mineral water">Family Group Number</code>
<code nr="04012" dsc="Other drinks (tea, coffee etc.)">Family Group Number</code>
<code nr="04013" dsc="Tobacco">Family Group Number</code>
<code nr="04014" dsc="Other goods">Family Group Number</code>
<code nr="04015" dsc="Entrance fee (cover charge)">Family Group Number</code>
<code nr="04016" dsc="Free entrance (members etc.)">Family Group Number</code>
<code nr="04017" dsc="Cloakroom fee">Family Group Number</code>
<code nr="04018" dsc="Free cloakroom">Family Group Number</code>
<code nr="04019" dsc="Accommodation - full board">Family Group Number</code>
<code nr="04020" dsc="Accommodation - half board">Family Group Number</code>
<code nr="04021" dsc="Accommodation - with breakfast">Family Group Number</code>
<code nr="04999" dsc="Other">Family Group Number</code>
</ArticleGroupCodesMapping>

This file shows that many Article Group Codes can be mapped to different Family Group
numbers. In this example, we have mapped four Family Groups to a Food (04006) Article
Group Code. Be aware that in line <code nr="04006" dsc="Food ">ONLY THIS
NUMBER CAN BE CHANGED to the number of the Family Group</code>.
Other sections of this line should not be edited.

Figure 4-5 - Sample Configuration Micros.FiscalClient.Mapping.xml File

<?xml version="1.0" encoding="utf-8" ?>

<ArticleGroupCodesMapping>
<code nr="04006" dsc="Food ">1</code> <!-- Family Group '1' = Breakfast Food -->
<code nr="04006" dsc="Food ">2</code> <!-- Family Group '2' = Starters -->
<code nr="04006" dsc="Food ">3</code> <!-- Family Group '3' = Soups -->
<code nr="04006" dsc="Food ">4</code> <!-- Family Group '4' = Main Courses -->
<code nr="04007" dsc="Beer">12</code> <!-- Family Group '12' = Beer -->
<code nr="04008" dsc="Wine">14</code> <!-- Family Group '14' = Wine -->
<code nr="04009" dsc="Liquor">16</code> <!-- Family Group '16' = Liquors -->
<code nr="04011" dsc="Soft drinks/Mineral water">10</code> <!-- Family Group '10' = Soft
Drinks -->
<code nr="04012" dsc="Other drinks (tea, coffe etc)">11</code> <!-- Family Group '11' =
Hot Drinks -->
<code nr="04013" dsc="Tobacco">17</code> <!-- Family Group '17' = Cigarettes -->
</ArticleGroupCodesMapping>

4-12
 Chapter 4
Simphony EMC Configuration

SAF-T – Service Charge Codes (Service Charges)

All of the Service Charges must be mapped to Service Charges Predefined Basic ID.
To achieve this, a new Data Extension was added to the configuration of the [NO] SAFT
Service Charge Code, which points to one of the following Predefined Basic IDs from
the table below:

Table 4-3 - Predefined Basic ID 10 - Service Charge Codes

PredefinedBasicID Service Charge/Tip/Gratuity Name
1. 10001 Amount from gratuity/tip
2. 10099 Other

1. Open EMC.
2. At the main window choose the desired level (Enterprise, Property, Revenue Center,
or Zone) and navigate to Configuration | Sales | Service Charges.
3. In the Service Charges module double-click any listed item and navigate to the Data
Extension tab.
4. Make changes to the [NO] SAF-T Service Charge Code row.
5. Apply codes according to Table 4-3 above, and set the correct Predefined Basic
ID’s to all Service Charges in the configuration.
6. Click Save.

Figure 4-6 - Service Charge Data Extensions

SAF-T – Standard VAT Codes (Tax Rates)

All of the Tax Rates must be mapped to Predefined Basic ID’s. To achieve this the
fiscal interface use additional column available in Tax Rates module called Tax Codes.
Use Table 4-4 below and map each Tax Rate to the proper Predefined Basic ID that
best describes the tax rate used in the system.
1. Open EMC.
2. At the main window choose the desired level (Enterprise, Property, Revenue Center,
or Zone) and navigate to Setup | Taxes and Order Types | Tax Rates.

4-13
 Chapter 4
Simphony EMC Configuration

3. In the Tax Rates module navigate to Tax Codes column.

4. Apply codes accordingly to table below and set the correct Predefined Basic ID’s to
all tax rates in the configuration.
5. Click Save.

Table 4-4 - Predefined Basic ID - Standard VAT Codes

PredefinedBasicID Description Tax Rate Compensation

1. 0 No VAT treatment TRUE
2. 1 Input VAT deductible (domestic) Regular rate TRUE
Reduced
3. 11 Input VAT deductible (domestic) rate, middle TRUE
Reduced
rate, raw
4. 12 Input VAT deductible (domestic) fish
Reduced
5. 13 Input VAT deductible (domestic) rate, low TRUE
Input VAT deductible (payed on
6. 14 import) Regular rate TRUE
Input VAT deductible (payed on Reduced
7. 15 import) rate, middle TRUE
8. 20 No VAT treatment TRUE
9. 21 Basis on import of goods Regular rate TRUE
Reduced
10. 22 Basis on import of goods rate, middle TRUE
11. 3 Output VAT Regular rate
Reduced
12. 31 Output VAT rate, middle
Reduced
rate, raw
13. 32 Output VAT fish
Reduced
14. 33 Output VAT rate, low
15. 5 No output VAT Zero rate
Domestic sales of reverse charge
16. 51 /VAT obligation Zero rate
17. 52 Export of goods and services Zero rate
Not liable to VAT treatment,
turnover outside the scope of the
18. 6 VAT legislation
No VAT treatment - no turnover
19. 7 according to the VAT legislation
Importation of goods, VAT
20. 81 deductible Regular rate TRUE
Importation of goods, without
21. 82 deduction of VAT Regular rate TRUE
Importation of goods, VAT Reduced
22. 83 deductible rate, middle TRUE

4-14
 Chapter 4
Simphony EMC Configuration

PredefinedBasicID Description Tax Rate Compensation

Importation of goods, without Reduced
23. 84 deduction of VAT rate, middle TRUE
Importation of goods, not
24. 85 applicable for VAT Zero rate TRUE
Services purchased from abroad,
25. 86 VAT deductible Regular rate TRUE
Services purchased from abroad,
26. 87 without deduction of VAT Regular rate TRUE
Services purchased from abroad, Reduced
27. 88 VAT deductible rate, low TRUE
Services purchased from abroad, Reduced
28. 89 without deduction of VAT rate, low TRUE
Purchase of emissions trading or
29. 91 gold, VAT deductible Regular rate TRUE
Purchase of emissions trading or
30. 92 gold, without deduction of VAT Regular rate TRUE

The following screen explains how mapping works. Each of the Tax Rates must be
mapped only to one of the Predefined ID’s from Table 4-4 above.

Figure 4-7 - Tax Rates Module

WARNING:
This is a mandatory configuration that is required by the SAF-T Export. You
are warned by the system if some of the tax rates are not properly mapped to
the provided Predefined ID’s shown above. The fiscal interface notifies you at
any step of POS Operations until the configuration is corrected.

4-15
 Chapter 4
Simphony EMC Configuration

SAF-T – Payment Codes (Tender Media)

All of the Tender Media’s must be mapped to Predefined Basic ID’s. To achieve this,
new Data Extension was added to the configuration of the [NO] SAF-T Payment Code
which points to one of the following Predefined Basic ID’s.

Table 4-5 - Predefined Basic ID 12 – Payment Codes

ID PredefinedBasicID Payment Code Types
1. 12001 Cash
2. 12002 Debit Card
3. 12003 Credit Card
4. 12004 Bank Account
5. 12005 Gift Token
6. 12006 Customer Card
7. 12007 Loyalty, Stamps
8. 12008 Bottle Deposit
9. 12009 Check
10. 12010 Credit Note
11. 12011 Mobile Phone Apps
12. 12999 Other

1. Open EMC.
2. At the main window choose the desired level (Enterprise, Property, Revenue Center,
or Zone) and navigate to Configuration | Sales | Tender/Media.
3. In the Tender/Media module double click any listed item and navigate to Data
Extension tab.
4. Find the row [NO] SAF-T Payment Code and apply codes accordingly to table
above and set correct Predefined Basic ID’s to all tenders in the configuration.
5. Click Save.

4-16
 Chapter 5
Backup

5
Backup
From a compliance standpoint, all fiscal data must remain in the Norway territory even
when the main application server is hosted abroad. The fiscal interface was enhanced
with a backup functionality which allows you to keep its data locally and safe. From a
technical stand point, a backup prevents the local database on CAPS (checkpostingdb)
to grow until it consumes all of the disk space and POS Operations becomes frozen.
The backup file is encrypted to prevent data manipulation. If for some reason, someone
edits a backup file, then while creating a SAF-T Export, the backup file is not properly
decrypted and the operation fails.
Remember that a backup cannot be created for an already backed up period which
happens daily!

Backup Setup
The following section describes how to setup a backup and enable it. In previous
chapters we added Data Extensions to define export paths and time settings to interact
with a backup. Adding buttons in Page Design – Button Configuration to be able to
produce SAF-T Export file on demand was also reviewed.
All configuration must be performed in the Enterprise | Properties module where all of
the properties are listed, as data extensions are designed for property use. The
Enterprise Level Setup chapter already provides instructions on how to set up extensions
for backup. Below, find more detailed explanations about how backup functionality works.
1. Go to Enterprise | Setup | Enterprise Configuration and Properties.
2. Double-click the desired property and go to Data Extension.
3. Enter the information in the following rows about the property:
a. [NO] Enable/Disable Backup Audit Export – This setting allows you to enable
the backup functionality. This row accepts only two arguments. The first is zero
(0) or an empty record which means functionality is disabled. To turn it on enter
one ‘1’ which enables backups.
i. Row set to ZERO (0) or empty - backup DISABLED
ii. Row set to ONE (1) – backup ENABLED
b. [NO] SAF-T Audit Table Export Time – Allows you to set a time when the
backup process of the FCR Journal table should occur on a daily basis. The
result of a successfully executed backup is an .xml file, in a user defined location,
in next point (c). The backup file is an exact copy of an FCR Journal table and it
is encrypted to provide another layer of security. If the encrypted file is somehow
manipulated for any reason, then while executing a Journal Backup Export (via a
button in Page Design) the backup file is not properly read and the SAF-T
Export file is not created.

5-1
 Chapter 5
Backup

c. [NO] SAF-T Audit Table Export Path – This is an export path where the backup
file of the FCR Journal table resides on a CAPS workstation. If you do not
manually create a folder, then it is automatically created by the system during the
first occurrence of the backup process based on the argument provided in this
row.
Be aware that files from this location should be secured on behalf of the end user.

d. [NO] SAF-T Audit Table Import Path – The import path is not created
automatically like the export path. It is your responsibility to define the import
path in EMC and create the same folder structure at the workstation level. The
import folder is not automatically populated with backed up files which are saved
in a folder specified in a previous step. Again, it is your responsibility to copy files
to the defined location before creating a SAF-T Export with a manually run
(button) Journal Backup Export.

Export from Backup (SAF-T Export from Backup)

By the export of the backup we understand that the SAF-T Export file is created based
on the files which were backed up earlier and are in the folder defined in [NO] SAF-T
Audit Table Export Path row in the Enterprise Property module.
If you want to create a SAF-T Export file from backup files, then the backup files for a
given date range must be manually copied to the location defined in this row [NO] SAF-T
Audit Table Import Path before an export can occur. The backup files can be taken
directly from the location defined in this row [NO] Backup Audit Export.
The SAF-T Export file is stored in a predefined location at CAPS along this path:
C:\Micros\FiscalLayer\Reports.

5-2
 Chapter 6
Fiscal Service Standalone Installer

6
Fiscal Service Standalone Installer
If the CAL Package cannot be used for Oracle Fiscal Layer Service deployment, a
standalone executable installer delivered as a part of installation process should be used
on each workstation.
Perform the following steps to manually install the Fiscal Service:
1. After unzipping the Oracle Hospitality Simphony Norway Fiscal , the library
contains a Fiscal Service Standalone Install folder.
2. Copy all files to the C:\Micros\Simphony\FiscalLayer on the workstation.
3. Run a CMD prompt as an administrator.
4. Navigate to C:\Micros\Simphony\FiscalLayer
5. Type FiscalServiceInstall.exe and press the Enter key.

Figure 6-1 - Administrator Command Prompt

6. Open the Microsoft Windows Services console (services.msc) and verify the
MICROS Fiscal Service state:
- The service should be set to Automatic in the Startup Type column and
started.
Figure 6-2 - Microsoft Windows Services Console

6-1
 Chapter 7
Extended Data Posting - Reporting & Analytics

7
Extended Data Posting - Reporting & Analytics
This Fiscal solution attaches the fiscal information listed below to each transaction that is
processed by a point of sale (POS) system. To allow this additional information to be
posted to Reporting and Analytics, the configuration described in this section needs to
be completed.
Information attached to transactions:
• Cash Register ID
• Signature
• JWS representation of transaction (part of DEP Log)
• Cash Register receipt counter
• Cash Register running total at the moment of transaction closure

Application Server Settings

To enable the fiscal data transfer to Reporting and Analytics, the following changes
must be applied on the Simphony application server.

Direct Posting Service

Perform the following:
1. Change to the following directory:
[Drive]:\MICROS\Simphony2\DirectPostingService.
2. Edit the DirectPostingService.exe.config file with your favorite text editor.
3. Check if the following section needs to be added to the top of the file, just after the
<configuration> tag. If this content is already present, skip to the next step, otherwise
add these lines immediately after the <configuration> tag:
<configSections>
<section name="extensionAppSettings"
type="Micros.DPS.ConfigSectionHelper,DirectPostingService"/>
</configSections>
Do not change any part of the above lines.
The appKey value must match the previously entered extension application name
Micros.FiscalLayerClient. If these values are not equal, the data to be exported cannot
be created. Note that this string is case-sensitive.
Ensure that the Direct Posting Service is restarted if any changes are made to the
DirectPostingService.exe.config file.

7-1
 Chapter 8
Effective Reporting

8
Effective Reporting
This section of the document is meant to provide guidance on how to report problems
related to the solution described in previous chapters or operational dysfunctions from the
end user perspective.

Reporting
Use the following escalation report as a guidance while creating a BugDB ticket. This
allows the Fiscal Center of Excellence Team to act promptly and address tickets with
the appropriate severity.
1. System/environment setup (note if system is hosted)
Server: Windows version, Simphony and Fiscal Interface version in use
Workstation: Type (WS5, WS6) and operating system
Hardware: list any external printers (version and firmware optional)
2. Oracle Hospitality Simphony setup/configuration
Please provide information about any specific configuration which may have impact
on raised error and are related to configuration itself or configuration files in EMC
3. Exact scenario – Does it affect operations or not (is it possible to close transaction)?
Provide an exact situation when the error occurred using the following workflow as an
example:
• Open Transaction and add Menu Items
• Service Total Check
• Pick up check and add another Menu Item
• Close Check with fiscal Payment Type
4. Log files
All files containing information related to transaction and POS Operations are located
in %AppRoot%WebServer\wwwroot\EGateway\EGatewayLog
5. Log files from MICROS Fiscal Service
The most important log file when escalating any SR’s is usually located in
C:\Micros\Simphony\FiscalLayer\Logs and is called
Micros.FiscalClient.DataProcessor.Log.txt. With this file, the QA Team and
Sustaining Engineering Team can very quickly reproduce the reported issue.
Please zip all information into one folder, and attach it to the BugDB Ticket.

8-1
 Appendix A
Troubleshooting

Troubleshooting
The Oracle Hospitality Simphony Norway Fiscal Interface is based on Oracle
Hospitality Fiscal Layer architecture. The following chapter will help you to understand
how application layers cooperate with each other, how to effectively troubleshoot the
solution, and how to report potential issues in order to get them reproduced in separate
lab environments.

Fiscal Layer Architecture

The Fiscal Layer solution for Oracle Hospitality Simphony is built from two separate
applications:
• Fiscal Layer Client
• Fiscal Layer Service
While Oracle Hospitality Simphony is operating, the Fiscal Layer Client
communicates with the Fiscal Layer Service that is responsible for communication with
a fiscal device such as a fiscal printer, signature capturing device, or another instance of
the Fiscal Service (diagram below).
Note that it depends on country specific regulations for which the device is utilized.

Figure 7-1 - Fiscal Layer Architecture

Fiscal Layer Client – Extension Application

The Fiscal Layer Client is a standard Extension Application, configured in EMC on the
Enterprise, Zone, Property, or Revenue Center level, depending on the implementation
model.
The Fiscal Layer Client requires XML configuration files respectively for both the Client
and Service which are supplied as Extension Application content:
• Micros.FiscalClient.Properties.xml
• Micros.FiscalService.Properties.xml

A-1
 Appendix A
Troubleshooting

Figure 7-2 - Extension Application Configuration

When Simphony (ServiceHost) is starting, the Fiscal Layer Client reads both XML files
as well as additional configuration elements set in EMC such as a Data Extension on
various levels, described in the previous chapters of this manual.
If the configuration is correct, the Micros.FiscalService.Properties.xml is saved on the
workstation file system in the folder where the Fiscal Layer Service binaries are stored
(usually C:\Micros\Simphony\FiscalLayer).
After the Fiscal Layer Service is started by the Fiscal Layer Client the system becomes
ready for operations.

Fiscal Layer Service – Middleware Service

The Fiscal Layer Service is a middleware Microsoft Windows Service application. It is
responsible for all communication with fiscal devices such as physical printers, security
signature capture devices, or a simple service which signs checks with signatures. It is
similar to fiscal printers that are common and not strictly linked to a specific POS system
(Simphony). Fiscal documents are formatted by the Fiscal Service based on the check
content received from Fiscal Layer Client.
If the Fiscal Layer Service is installed properly, it should be visible in the standard
Microsoft Windows system Services console. The Startup Type should be set to
Automatic.

Figure 7-3 - Microsoft Windows Services Console

A-2
 Appendix A
Troubleshooting

NOTE:
In Oracle Hospitality Simphony On-Premise and Cloud, the Fiscal Layer
Service is automatically deployed as a CAL Package.
For Oracle Hospitality Simphony Multi-Tenant environments, a CAL Package
is not available, and the service must be installed manually on each
workstation. Refer to the Fiscal Service Standalone Installer chapter for more
information.

Logging
There are three levels of logging to help troubleshoot the solution:
1. Simphony EGateway logs
2. Fiscal Layer Client logs 1
3. Fiscal Layer Service logs 2

EGateway Log
Oracle Hospitality Simphony EGateway log files are generated by standard Simphony
logging functionality. The logged information is dependent on the Log Verbosity setting
set at the workstation level.

Figure 7-4 - Workstation Logging Settings

Log files are located in the EGatewayLog folder

(usually %AppRoot%\WebServer\wwwroot\EGateway\EGatewayLog\Log_[works
tation_name].txt).
The EGatewayLog contains entries about the Simphony ServiceHost application, not only
the Fiscal Layer Client. This log can be used to verify if the Fiscal Layer Client Extension

1 Log files are automatically overwritten after reaching maximum size.

2 Log files are automatically overwritten after reaching maximum size.

A-3
 Appendix A
Troubleshooting

Application is properly loaded by Simphony, or if there are any suspected incidents or

issues.

NOTE:
While troubleshooting performance incidents in the EGateway Log, ensure
that the verbosity setting for a specific workstation is set high enough to
provide you with enough detail.

Fiscal Layer Client Logs

There are two separate log files maintained by the Fiscal Layer Client. Both are stored
in the Fiscal Layer log folder (usually C:\Micros\Simphony\FiscalLayer\Logs)
1. Micros.FiscalClient.Log.txt
This log contains the information about the application initialization parameters that
are finally used.

Figure 7-5 - Example Logging Content

What can be verified using this log file?

• What the version is of the Fiscal Layer Client that is physically loaded by a specific
workstation
• What the data extension values are that are physically read by the application
• What the settings are that are stored in the XML file that is physically recognized by
the application
• If the Fiscal Layer Service exists and is installed
• If the XML configuration file was successfully saved in the proper location
• If the communication with the Fiscal Layer Service was established

Example Suspected Cases

The log file does not exist or there is no content in during the corresponding time after
Simphony has started.
• Reason: The Fiscal Layer Client Extension Application is not loaded
• Steps to verify:
o Check the EGatewayLog
o Check EMC | Extension Application configuration:
 If not overwritten on a lower level
 If the Micros.FiscalLayerClient is not disabled

A-4
 Appendix A
Troubleshooting

 If the Micros.FiscalLayerClient.dll is properly added as an application

content:
- The Zonable Key is correct.
- The Disk file name is correct – Micros.FiscalLayerClient.dll
- Target is enabled for Win32 devices
- The Content file was loaded as a 3-DLL

• Data Extension or XML values are different than expected

o Reason: The configuration is not applied to the workstation
o Steps to verify:
 Workstation is online
 Workstation DB is up to date – reload workstation if needed and restart
 EMC configuration is not overwritten on a lower level

• Fiscal Layer Service not found

o Reason: MICROS Fiscal Service is not installed
o Steps to verify:
 Verify if CAL Package was deployed 3
 Navigate to the Fiscal Layer Service folder and verify if files exists
 Run the Services console and check if the MICROS Fiscal Service is visible

• Configuration for Fiscal Layer Service cannot be saved

o Reason: MICROS.FiscalService.Properties.xml cannot be saved in Fiscal
Layer Service installation folder
o Steps to verify:
Check permissions for the Local Service account

• Communication with Fiscal Layer Service cannot be established

o Reason: Fiscal Layer Service is not running or is not properly started
o Steps to verify:
 Check if the Fiscal Layer Service is running after Simphony is started
 Try to start the Fiscal Layer Service manually (perform troubleshooting for
the Fiscal Layer Service)

3 For Simphony Standard Cloud (Multi-tenant) environments, a CAL Package is not available, so the service must be
installed manually.

A-5
 Appendix A
Troubleshooting

2. Micros.FiscalClient.DataProcessor.Micros.Log.txt
This log file contains all of the communication submitted by the Fiscal Layer Client to
the Fiscal Layer Service and their responses. This is the equivalent of Fiscal Layer
Service transaction log, but it is generated by the client.
The content of this file in a correctly working environment should be the same as the
Micros.FiscalLayer.DataProcessor.Micros.Log.txt generated by the Fiscal Layer Service
(except timestamps can be different by +/- 1 sec.).

What can be verified using this log file?

In comparison to the Micros.FiscalLayer.DataProcessor.Micros.Log.txt if request
submitted by a client was received by the service and if each package submitted by the
service reached the client.

Example suspected cases:

• A Request is logged that does not have a corresponding entry in the
Micros.FiscalLayer.DataProcessor.Log.txt
o Reason: There is a problem with Inter Process Communication between client
and the service
o Steps to verify:
Named Pipes are not blocked on an OS or Antivirus software level
If this problem exists, the workstation could possibly be frozen until it is restarted.

Fiscal Layer Service Logs

Most of Fiscal Layer Service log files are stored in log file folder usually
C:\Micros\Simphony\FiscalLayer\Logs, except the main log –
Micros.FiscalService.Log.txt that is stored in the Fiscal Layer Service installation folder
C:\Micros\Simphony\FiscalLayer
1. Micros.FiscalService.Log.txt
This log contains the main information about the environment where the Fiscal Layer
Service is installed as well as the service configuration read from the
Micros.FiscalService.Properties.xml file.

Figure 7-6 - Example Logging Content

A-6
 Appendix A
Troubleshooting

What can be verified using this log file?

• The version of the installed Fiscal Layer Service

• Versioning of .Net Framework that is installed
• Status of each module initialization (DataProcessor and Country Layer)
• If the configuration was correctly read and applied

Example suspected cases:

• Problem with initializing caused by missed assemblies
o Reason: Some files are missing or do not exist
o Steps to verify:
 Check if all of the CAL Package content exists in folder
 Check if the required .Net Framework versions are listed

• Problem with reading XML configuration (In-flight configuration error)

o Reason: Structure of the Micros.FiscalService.Properties.XML is incorrect
o Steps to verify:
 Check if Micros.FiscalService.Properties.XML file located in the service
folder exists
 Check if Micros.FiscalService.Properties.XML is stored as a part of
Micros.FiscalLayerClient Extension Application content exists (EMC)

2. Micros.FiscalLayer.DataProcessor.Micros.Log.txt
This is the most important file and also called the transaction log. This file contains all
communication between the Fiscal Layer Client and the Fiscal Layer Service. In correctly
working environments, with the exception of logged timestamps, this is identical with the
Micros.FiscalClient.DataProcessor.Log.txt.
This file can be used to run each operation submitted by the Client to the Service in an
isolated Product Development environment directly from the file.

What can be verified using this log file?

Communication between the Client and the Service (refer to the Fiscal Layer Client –
Extension Application section).

A-7