• Author / Uploaded
• Add Venture

• Categories
• Factura
• Licencia
• Impuesto al valor agregado
• Oracle Corporation
• Programa de computadora

Citation preview

Oracle® Hospitality OPERA PMS Opera Fiscal Solution Install / Configuration Guide – eFactu for Peru (Electronic Invoice) Release 10.4.0.0

July 2019

Copyright ©, 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 Installation of eFactu Solution (1st time installation) ....................................................................................... 4 Pre-requisites ............................................................................................................................................ 4 Installation ................................................................................................................................................ 4 Opera Configuration ................................................................................................................................. 9 eFactu Scripts for Peru .......................................................................................................................... 9 Transaction Codes Grouping ..................................................................................................................... 9 Configurable Variables ............................................................................................................................ 10 Multi-property generation ...................................................................................................................... 13 UDF's in profiles ...................................................................................................................................... 13 Transaction code identifier ..................................................................................................................... 14 Folder permissions (non-administrator users) ....................................................................................... 14 Opera Configuration ................................................................................................................................... 15 Opera Parameters ................................................................................................................................... 15 FISCAL FOLIO PRINTING ...................................................................................................................... 15 FISCAL PROGRAM NAME .................................................................................................................... 15 FISCAL XML RETRIEVAL VIA SERVLET .................................................................................................. 16 OPERA Tax Types..................................................................................................................................... 17 Fiscal Print Tasks ..................................................................................................................................... 18 Terminal Configuration (Workstations) .................................................................................................. 18 Explanation of fields in FISCAL_FOLIO_TAX ............................................................................................ 19 Peru New Enhancement Requirements (1st time Installation and Upgrade) ................................................ 20 Opera Configuration Steps...................................................................................................................... 20 Update XML Folio Layout .................................................................................................................... 20 Opera Profile and Reservation Screen .................................................................................................... 23 Opera Profile Fields – Individual ......................................................................................................... 23 Opera Reservation Fields .................................................................................................................... 26 eFactu Configuration File Parameters .................................................................................................... 30 Upgrading eFactu.ini on Workstations ............................................................................................... 30 eFactu.ini Example .............................................................................................................................. 32 eFactu Output ..................................................................................................................................... 32 Appendix 1 .............................................................................................................................................. 33

Installation of eFactu Solution (1st time installation) Pre-requisites -

eFactu.msi – latest version could be downloaded from MOS Privileges of Administrator to install the .msi file. Hotel data to fill eFactu configuration file.

Installation For each terminal that will be used for electronic invoices, is suggested to create a directory, like C:\eFactu where the installation files must be copied. Put the eFactu.msi file on it. Run the eFactu.msi as an administrator user in each terminal that generates electronic invoices. The steps indicated by the successive windows must be followed.

On the “Carpeta” field always keep the value C:\windows\SysWOW64\ otherwise the solution won´t work properly. Choose to install for all users by the radio button “Para todos los usuarios”;

Click on “Siguiente” to continue;

Wait for the installation then select “Cerrar” to close.

In each terminal that generates electronic invoices, the SOAP Toolkit V3.0 of Microsoft that is located in C:\Windows\SysWOW64\eFactuSoapToolkit3 must be installed. This component is deployed under eFactu.msi install.

Right click on it and select “Run as Administrator” if it´s available

Then click on “Yes”

Wait for a moment to load, then Hit “Next”, choose “I Accept….” and “Next” again;

Hit “Next”

Assure that all items are selected and click on “Install”

Wait for the install then click on “Finish”

Opera Configuration eFactu Scripts for Peru In a terminal with connection to the base, the file eFactuScript .sql must be run ONLY ONCE as follows: - Connect to the base by sqlplus from a command window (cmd): sqlplus / @ ; - Run the .sql as follows: @ \ system32 \ eFactuScripts \ eFactuScript .sql; - Then load the requested info: App_server_name: name of the application server. Property_code: name of the resort.

Transaction Codes Grouping It is convenient to have all the transaction codes with an associated arrangement. Otherwise, those codes that do not have an associated arrangement will be accumulated in generic groupings according to their VAT. All department codes corresponding to an arrangement must have the same VAT rate. The code of the arrangement must be numeric from 01 to 99. The exempt and paid out codes must NOT have grouping since they appear in the footer of the electronic invoice. In Mexico there are two ways to group transaction codes when you have packages: - All grouped in a single concept (charges within the same arrangement). - Room charges and package items (two arrangements). NOTE: It is extremely important that the trx codes associated with the individual packages are unique at the time of application, otherwise the charges will be duplicated.

Configurable Variables The file eFactu.ini located on C:\Windows\SysWOW64\eFactu.ini has a series of variables that can be configured to adapt to the operation of each establishment. Below are the variables currently available, with their possible values: VARIABLE

VALUE

DESCRIPTION

version

Current version of Opera (5.0.04.01). As of V5.0.04.01, an empty field is sent in the eFactu error responses.

VATNB

VAT rate used for net and gross codes (19%, 21%, 16%).

VATU

VAT rate used for codes with different VAT (10.5%, 2.5%).

VATZ

VAT rate used for codes with different VAT (27%).

VATY

VAT rate used for codes with different VAT (IAEMS 35% on ISH).

basecurrency

[PEN | USD]

The base currency of the property (Nuevos Soles or Dollars).

detailed

T F

associatedDocument

T F

exemptIncluded

T

(AR)

F

log

T F

pkgArrangements

[1 | 2]

If the printer prints the tax documents in detail. If the printer prints the fiscal documents by groupings (recommended value). It presents an editing window for the manual entry of the associated document (series and invoice number) in the case that Opera could not obtain it. It does not present any window. The exempt amount is included in the subtotal. The exempt amount in the subtotal is excluded. The log file is generated: OperaFactu .log in the : \ \ system32 \ eFactuLogs directory. No log file is generated. The charges corresponding to packages will be defined by

this amount and descriptions of roomDescription and othersDescription. roomDescription

All package charges will go under this grouping if pkgArrangement is set to 1 (ex: Package). If only the room rental is loaded, pkgArrangements is set to 2 with the corresponding description (eg: Room Package, Room Rental) and the othersDescription variable is configured.

othersDescription

Charges corresponding to the package elements. He configure this variable in case pkgArrangements is set to 2 (ex: Package Elements).

loCaseParameters

T

F

IRSResponse

T F

Connection parameters in lowercase letters (for Peru you must go in T - area, password, documentType, documentContent). Connection parameters in uppercase-lowercase (Area, Password, DocumentType, DocumentContent). Obtain the response of the document processing directly from the SUNAT consuming a second web service (ReceiveMessage). It does not take any action.

area

A string that contains the name of the area created by Sign @ ture xDoc.

password

A string that contains the password associated with the area.

URL

String that contains the URL referred to the web service of Sign @ ture (ex: http: //mdq1/Signature.xDoc.Services/Core.asmx).

country

Country code where eFactu applies (AR: Argentina, CL: Chile, MX: Mexico, PE: Peru, UY: Uruguay).

mode

Available mode [SIGNATURE].

The functionality of c- in / c-out according to new fields PMCIDATE and PMCODATE for PMs according to the client. The functionality of obtaining the currency of the document to be generated from a variable:

customer

USDPaymentTrxCodes. Available customer [LIBERTADOR].

exchangeOperation

T F

Activates the division as an operation in the calculation of the exchange rate. Default value assumed by multiplication as an operation.

serieFactura

Series of invoices for numbering.

serieBoleta

Series of ballots for numbering.

facturaNumero

Current invoice number for the local billing point (MUST NOT BE MODIFIED).

boletaNumero

Current ticket number for the local billing point (MUST NOT BE MODIFIED).

notaNumero

Current credit note number for the local billing point (MUST NOT BE MODIFIED).

debitoNumero

Current debit note number for the local billing point (MUST NOT BE MODIFIED).

RUC

RUC of the issuer (hotel).

razonSocial

Social reason of the issuer.

nombreComercial

Commercial name of the issuer.

codigoPostal

Geographical Location Code (UBIGEO) of the INEI.

calle

Complete and detailed address of the issuer.

ExcludedTrxCodes

List of trx codes separated by ',' that define those trx codes that are exempt from 18%. It should start and end with ','.

List of trx codes separated by ',' that define those trx codes that activate the calculation of deductions from the amount defined in DetractionTriggerAmount and the percentage expressed in DetractionPercentage is applied to them. It should start and end with ','.

DetractionTrxCodes

DetractionTrxCodes2

List of trx codes separated by ',' that define those trx codes that activate the calculation of deductions from the amount defined in DetractionTriggerAmount and the percentage expressed in DetractionPercentage2 is applied to them. It should start and end with ','.

DetractionPercentage

Percentage that indicates the deduction rate 1 to calculate on the list DetractionTrxCodes (ex: 10.00).

DetractionPercentage2

Percentage that indicates the deduction rate 2 to calculate on the list DetractionTrxCodes2 (ex: 12.00).

DetractionTriggerAmount

Amount from which the detraction calculation is activated (ex: 700.00).

List of trx codes separated by ',' that define those trx codes of payments in dollars that cause documents to be generated in that currency automatically. It should start and end with ','.

DepositTransferTrxCode

Trx code used for the transfer of deposits at check-in. It must be indicated for the correct use of the parameter USDPaymentTrxCodes since it is a payment and can be used both for a generation in dollars and soles.

serial

The serial code used by eFactu (MUST ALWAYS be at the end of eFactu.ini with a carriage return at the end).

USDPaymentTrxCodes

Multi-property generation In the case where you want to invoice from a terminal to more than one property, you must create an eFactu .ini by the property. In this way, eFactu will take the corresponding ini file and update the sequences correctly.

UDF's in profiles The following fields, if configured in Screen Painter and folio layout config, will be printed in the fiscal documents. UDFC33 Fiscal email address (may contain more than one address separated by ';'). You can vary its number according to the chain. UDFC40 Corporate Name. You can vary its number according to the chain.

Transaction code identifier All transaction codes in Opera must have a transaction code identifier (Fiscal Trn. Code Type). The identifiers are defined by the type of transaction: Code P X V O N B U Z Y D A

Description Process: payments such as Cash, Checks, Credit Cards, (Deposits in MX). Exempt: exempt charges such as tips, etc. Exempt1: other exempt charges such as paidouts (MX) defined by the user. No process: Internal Taxes, VAT rates, internal codes (except D in AR). Net: charges without tax included as room charges. Gross NB: charges with tax defined in the variable VATNB. Gross U: charges with tax defined in the VATU variable. Gross Z: charges with tax defined in variable VATZ. Gross Y: charges with tax defined in the variable VATY. Deposit: applies only to the internal code Deposit Transfer at check-in. Identifier of payment form of accounts receivable.

***It is extremely important that all transaction codes have an associated value. Otherwise, the generation of documents will not be correct. *** Zero rate package charges should not be mixed with others that do have tax. For packet transaction codes with allowance, the fiscal trx code type must also be configured in the profit and loss codes.

Folder permissions (non-administrator users) Read and write permissions must be given to the eFactu.exe executable and to eFactu.ini, along with the eFactuLogs folder. They are all located in c:\ windows \ Syswow64.

Opera Configuration Opera Parameters After installation is completed, the first step in Opera is review some parameters.

FISCAL FOLIO PRINTING Opera´s functionality Fiscal XML Configuration is used to generate the folio XML. In order to have the menu and functions available, the parameter FISCAL FOLIO PRINTING must be active. Opera->Configuration->Setup->Applications Settings->Cashiering->Parameters->Fiscal Folio Printing

FISCAL PROGRAM NAME In order to indicate to Opera the path where is located the Fiscal Folio Program (installed as procedure mentioned above), it´s necessary to fill the setting FISCAL PROGRAM NAME, accordingly with the path or name of the executable file informed during installation process. (e.g.: efactu)

Opera->Configuration->Setup->Applications Settings->Cashiering->Settings->Fiscal Program Name

FISCAL XML RETRIEVAL VIA SERVLET Opera->Configuration->Setup->Applications Settings->Cashiering->Parameters-> FISCAL XML RETRIEVAL VIA SERVLET. This parameter should only be set like YES if necessary. This will prevent to PII data keeps masked on Opera XML file and eFactu output. **Remember: with this parameter active Opera will delete the webtemp payload (D:\MICROS\OPERA\operaias\webtemp\). You can access the data on this file using eFactu log located on C:\Windows\SysWOW64\eFactuLogs. Note that the name of the log file will be changed too.

Example: 

Parameter set like N: o Log file name: eFactuFP_5850BOLETA287_19_02_2019_7_18_39.log o PII Data masked in Opera XML Payload:

xxxxxxxx xxxxxxxx

xxxxxxxx o PII Data masked in eFactu output: E3|XXXXXX22|7| Test, Guest |Rua Oracle- Lima|[email protected]||||52|AMA||PE| P3|XXXXXX22||998|1||TRAVELSCAPE LLC / EXPEDIA(COMISIONABLE)|FacturaCompany||| 

Parameter set like Y: o Log file name: eFactu_19_02_2019_7_45_59.log o PII Data masked in Opera XML Payload:

xxxxxxxx xxxxxxxx

xxxxxxxx o PII Data unmasked in eFactu output: E3|fb001122|7|Test, Guest|Rua Oracle- Lima|[email protected]||||52|AMA||PE| P3|fb001122||998|1||TRAVELSCAPE LLC / EXPEDIA(COMISIONABLE)|FacturaCompany|||

OPERA Tax Types The script for will create it, just make sure they are ok. If not create accordingly by clicking on new and fill tax type field and the description CONFIGURATION->CASHIERING->TAX TYPES

Fiscal Print Tasks The script for will create it, just make sure they are ok.

Terminal Configuration (Workstations) The print tasks must be created by the terminal and on each workstation that generates electronic invoices. By terminal, you will have 'FACTURA','FAEXON','BOLETA','FACNC','FAENC','BOLNC','FAEND','FACND','BOLND'. Printing tasks and printers are associated with each terminal.

To establish that a terminal generates electronic invoices, you must mark the checkbox Fiscal Printer Attached.

NOTE: It is extremely important that the date and time of the terminals from which the electronic invoices are generated are correct.

Explanation of fields in FISCAL_FOLIO_TAX Tax1, 2, 3, 4 Tax totals. Tax5 Total exempt1. Tax6 Associated invoice number. Tax7 CAI. Tax8 Payment AR [Y | N]. Tax9 Total exempt.

Peru New Enhancement Requirements (1st time Installation and Upgrade) In order to be compliant with the new requirements for Peru, we have to deliver some new information made obligatory in March 2019. For that, is necessary additional configuration in Opera and in the eFactu configuration file. These steps must be followed after confirmed that eFactu is installed by checking if c:\windows\syswow64\efactu logs has recent generated files. Assure that the installation is in accordance with default documentation and scripts delivered on install package.

Opera Configuration Steps Some configuration need to be done in Opera as following. Please pay attention on Opera Parameters configuration section of this document, once it was included a note regarding FISCAL XML RETRIEVAL VIA SERVLET.

Update XML Folio Layout Go to CONFIGURATION->CASHIERING->FOLIO PRINT TASKS

Select the FOLIO TYPE, click on Edit and click on Layout;

-

Assure the fields below are created for each Folio Print Task created. o Guest_info->ID Country IDCOUNTRY o Guest_info->ID Number IDNUMBER o Guest_info->ID Type IDTYPE

o

General-> A UDFD available. Suggestion UDFD05

o

Folio detail-> Transaction Code Type

Opera Profile and Reservation Screen Validate that exists and if not, create it.

Opera Profile Fields – Individual o o o

ID_country ID_type ID_number

Go to CONFIGURATION->SETUP->SCREEN DESIGN->SCREEN PAINTER

Once in OPERA Screen Painter screen select the radio button for Profile and choose INDIVIDUAL;

Right click on the green area and select “Add Fields”;

On the search field look or ID and one by one add the fields below;

If there is no space on the main tab, place it on MORE FIELDS tab.

Once completed, right click on a green area and choose “Save Changes”

If these screens appear, click on “Close” then “Yes”. If not wait for the saving process.

Note: This message appears when there are overlapping fields. If it is one of the new fields added above, certify that everything is functional by saving and looking at a profile screen in OPERA PMS. If it´s not please go back and redesign it. After saving, right click on a green area and “Close Designer”

The OPERA Screen Painter screen will come up do not close it.

Opera Reservation Fields Validate that exists a UDFD for ARRIVAL DATE IN COUNTRY and if not, create it. On the OPERA Screen Painter screen, select the radio button for RESERVATION then “Reserved More Fields”

Right click on the green area then select “Add Fields” then search for UDFD.

Choose the most suitable available (remember this must be included in OPERA XML Folio Configuration and on the next steps for eFactu configuration file). On the example, the reservation UDFD01 and the respective button was used.

After adding the field, right click on it and edit the prompt field accordingly; In the example is showed “Ingreso al Pais”. Once completed, right click on a green area and choose “Save Changes”

If these screens appear, click on “Close” then “Yes”. If not wait for the saving process.

The screen for replicate the changes to the reservation more fields screens will be shown, select “ALL” and click “OK”.

After saving, right click on a green area and “Close Designer”

Close Screen Painter menu. Next step is to include on eFactu configuration file new parameters in order to deliver the new data according to conditions.

eFactu Configuration File Parameters On a new install, be sure to fill these parameters as demand, but in an eFactu upgrade the first step suggested is to create a backup (copy and paste) of the current eFactu.ini. File. Consider doing that on each workstation where it will be upgraded.

Upgrading eFactu.ini on Workstations Once eFactu.ini file backup done, open the current version of the file and add under the SUNAT group the following parameters: o o

CodeTypeLodging= complete with Trn. Type that corresponds to accommodation (Alojamiento). Remember to start and finish with a comma. Example CodeTypeLodging=,L,

The CodeTypeLodging parameter will be used to inform to eFatu which transaction code will represent Accommodation (Alojamiento) charges. Mainly used as a condition to define the Operation type field (Section E1 Pos. 10) vide Appendix 1. o

codigoAnexoSUNAT= complete with the correspondent code according to customer data.

The codigoAnexoSUNAT parameter will be used to inform the annex code SUNAT of the hotel. It will be on the Section E2 Pos. 09 and if it is blank eFactu will fill it with “0000”. o

productCodeSUNAT= complete with a key|value structure considering the code type|product code by SUNAT. Example: L|90111500,O|90111600,

It will represent the product code according to SUNAT. The logic is based on Opera transaction code field “Trn Type” which will be the tag in OPERA XML Folio Configuration.

Possible OPERA CODETYPE values to be set and SUNAT Product Codes suggestions based on the catalog 53. The catalog is attached bellow in order to confirm with the property. Note the suggestion here is to use the SUNAT Product Codes up to third level (each couple of characters mean a level) leaving the fourth level generic (00).

SUNAT Product code Spreadsheet.

UNSPSC_Spanish_v 14.xlsx

o

DateArrivalCountryUDF= complete with the UDFD created on the reservation screen and set on XML Folio Layout. Example RESVUDFD01

This parameter represents the User Defined Field created on the Reservation screen to accommodate the Date of Arrival in Country information. Remembering, it must be the same as created on the reservation screen and the same set on OPERA XML Folio Configuration. o

DetractionBankAccount= complete with the hotel´s account for Banco de la Nación.

This parameter is used to indicate the banking account of the property where the detraction amounts will be made available.

eFactu.ini Example Below you will find an eFactu configuration file as example.

efactu.ini

eFactu Output Follow the same eFactu routine of tests and validate all the fields are ok on log file (\windows\SysWow64\efactulogs)

Example: E1|01|F411-00000101|2019-02-14||CONTADO|||||1001|| E2|20114803228|6|INVERSIONES NACIONALES DE TURISMO S.A.|THE WESTIN LIMA HOTEL & CONVENTION CENTER|150131|Calle Las Begonias 1450, San Isidro|PE|003286|1234| E3|20603547692|6|00677954|10190 Covington Cross Drive Suite 300- Las Vegas|[email protected]|||||CUS||PE| E5|1000|600.00|9998|-0.00|9997|-0.00||0.00||752.40|68.40|10.00|0123456789|PEN|Cash | E6|54.00|30.00|0.00|0.00|-0.00|684.00|PEN|0.00|0.00|SON: SEISCIENTOS OCHENTA Y CUATRO Y 00/100 SOLES|TIPO DE CAMBIO:|PEN|1.00||1000| D|NIU|1|Food&Beverages/Almentos y Bebidas ( 1)|300.00|354.00|01|10|54.00|01|0.00|0.00|2|0.00|0.00|18.00|0.00|90101500|||||||||||||| D|NIU|1|Accommodation/Alojamiento ( 1)|300.00|354.00|01|10|54.00|01|0.00|0.00|1|0.00|0.00|18.00|0.00|90111500||||||||||||||

R||||| P1|00|00|01 P2|0206|3|02-08-18|05-08-18|3.400|Raphael|Barbosa|13151|252|| P3|||998|1||TRAVELSCAPE LLC / EXPEDIA(COMISIONABLE)|FacturaCompany||| P4|Cash 684,00||0,00||0,00||0,00|

Appendix 1