PREFACE

Purpose Statement
This document is intended to outline our general product direction. It is intended for information purposes only, and
may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and
should not be relied upon in making purchasing decisions. The development, release, timing and pricing of any
features or functionality described for Oracle’s products remains at the sole discretion of Oracle.
This document provides a suggested approach to configure OPERA Cloud, in order to comply with Mexico’s legal
requirements. Each chain and/or property must evaluate their existing configuration and make appropriate changes
with the help of the Consulting / Implementation team. Oracle recommends that all configuration changes are tested in
the customer’s training/testing environment, prior to application in a live production environment.
Examples and screenshots contained within this document are for demonstration purposes only.

Disclaimer
This document in any form, software or printed matter, contains proprietary information that is the exclusive property
of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle
software license and service agreement, which has been executed and with which you agree to comply. This document
and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle
without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated
into any contractual agreement with Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in planning for the
implementation and upgrade of the product features described. It is not a commitment to deliver any material, code, or
functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of
any features or functionality described in this document remains at the sole discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all features described in this
document without risking significant destabilization of the code.

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
 Tenant\Organization code
 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
 Screen shots of each step you take

Documentation
Oracle Hospitality product documentation is available on the Oracle Help Center at
http://docs.oracle.com/en/industries/hospitality/
Revision History
Date Version Description of Change

February 13, 2020 1.0 Initial publication

October 15, 2021 1.1 OPERA Controls chapter updated.

May 5, 2022 1.2 Outlined topics that apply to the country and
Latin America when applicable.

February 1, 2023 1.3 Document content re-formatted.

Fiscal Revenue Bucket Codes
Fiscal Revenue Bucket Codes (Generic Partner Related)
Edit the following Revenue Bucket Codes by completing them with the corresponding Transaction Codes.

To access Revenue Bucket Codes: Administration > Financial > Transaction Management > Fiscal Folio
Bucket Codes

Note: Only the Description and Transaction Code fields can be changed according to the hotel’s needs.

Payment Methods

1) Select Revenue Bucket Type ‘FLIP_PAY_SUBTYPE’ and Search.

2) Select the first Revenue Bucket Code for ‘FLIP_PAY_SUBTYPE’ listed below with a Bucket Value.

NOTE: Anything without a Bucket Value will not be used for GENERIC installations.

3) Select the Edit button.

4) Update the Description and Bucket Value to the value shown on the list below, then search and select the
transaction codes that should be linked to this Revenue Bucket Code. Save changes after editing each
Revenue Bucket Code.

5) The bucket value must contain the government payment code and divided by pipe, the payment type

Government Payment codes should be obtain from the SAT catalog an example of those codes as follow
under the name C_FormaPago

Validate with the property because this information can be changed by the government.
Examples
CODE DESCRIPTION BUCKET
REVENUE BUCKET
TYPE VALUE

FLIP_PAY_SUBTYPE CASH 01
Cash Payments
(Efectivo)

FLIP_PAY_SUBTYPE OTHER_CASH_1 Other Cash Payment 1

FLIP_PAY_SUBTYPE OTHER_CASH_2 Other Cash Payment 2

FLIP_PAY_SUBTYPE OTHER_CASH_3 Other Cash Payment 3

FLIP_PAY_SUBTYPE OTHER_CASH_4 Other Cash Payment 4

FLIP_PAY_SUBTYPE OTHER_CASH_5 Other Cash Payment 5

FLIP_PAY_SUBTYPE CHECK 02
Check Payments
(Cheque nominative)

FLIP_PAY_SUBTYPE CREDIT 99
Direct Bill Payments
(Remisión de deuda)
FLIP_PAY_SUBTYPE CCARD_1 04
Credit Card Payments 1
(Tarjeta de crédito)

FLIP_PAY_SUBTYPE CCARD_2 Credit Card Payments 2

FLIP_PAY_SUBTYPE CCARD_3 Credit Card Payments 3

FLIP_PAY_SUBTYPE CCARD_4 Credit Card Payments 4

FLIP_PAY_SUBTYPE CCARD_5 Credit Card Payments 5

FLIP_PAY_SUBTYPE CCARD_6 Credit Card Payments 6

FLIP_PAY_SUBTYPE CCARD_7 Credit Card Payments 7

FLIP_PAY_SUBTYPE CCARD_8 Credit Card Payments 8

FLIP_PAY_SUBTYPE CCARD_9 Credit Card Payments 9

FLIP_PAY_SUBTYPE CCARD_10 Credit Card Payments 10

FLIP_PAY_SUBTYPE OTHER_1 99
Other Payments
(Por definer)
FLIP_PAY_SUBTYPE OTHER_2
Debit Card
(Tarjeta de débito)
FLIP_PAY_SUBTYPE OTHER_3 03
Bank Transfer/EFT
(Transferencia electrónica de fondos)
FLIP_PAY_SUBTYPE OTHER_4
Company Money/Points
(Monedero electrónico)

FLIP_PAY_SUBTYPE OTHER_5 Paypal (Dinero electrónico)

FLIP_PAY_SUBTYPE OTHER_6
Deposit Transfer at Check in
*Set just the code for Deposit Transfer at Check in this revenue
bucket code. Also, cannot be present on other FLIP Revenue
bucket code.

FLIP_PAY_SUBTYPE OTHER_7 Other Payments 7

FLIP_PAY_SUBTYPE OTHER_8 Other Payments 8

 FLIP_PAY_SUBTYPE OTHER_9 Other Payments 9

FLIP_PAY_SUBTYPE OTHER_10 Other Payments 10

Tax Codes
For creating tax codes using the following rev bucket.

FLIP_TAX_CODES
1) Select Revenue Bucket Type ‘FLIP_TAX_CODES’ and Search.
2) Select the first Revenue Bucket Code for ‘FLIP_TAX_CODES’ listed below
3) Select the Edit button.
4) Update the Description to the name or percentage of the Tax, then search and select the transaction codes that
should be linked to this Revenue Bucket Code. Save changes after editing each Revenue Bucket Code. Complete
this task until all Tax/VAT transaction codes are linked to Revenue Bucket Codes.
5) The bucket value must contain the government tax code and divided by pipe, the tax rate code

Government Payment codes should be obtained from the SAT catalog an example of those codes as follow under the
name C_Impuesto
Validate with the property because this information can be changed by the government.

Note: If this Revenue Bucket Type and Revenue Bucket Codes are not available in SID Data, they should be set up
manually with the same values as below. The description can then be updated and the transaction codes linked as
required.
In this case, login in OPERA and go to

Administration > Financial > Transaction Management > Fiscal Folio Bucket Types
Click on “New”
Type: FLIP_TAX_CODES
Description: FLIP Tax Codes
Click on the “Save” button

Next step is to create the Bucket Codes, for that go to

Administration > Financial > Transaction Management > Fiscal Folio Bucket Codes
Select the Revenue Bucket Type previously created, FLIP_TAX_CODES;
Click on “New” then create the Bucket Codes like below/
For each new code created to remember to Increase the number on Code field. For reference see below the default.
Please make sure to create the revenue codes necessary to accommodate the different taxes used by the property.

Examples

REVENUE BUCKET TYPE CODE DESCRIPTION BUCKET VALUE COMMENTS

FLIP_TAX_CODES TAX_1 IVA 002 Used for % taxes

FLIP_TAX_CODES TAX_2 ISH ISH Used for % taxes

Creating Transactions Revenue Buckets

FLIP_TRX_BY_GRP
1) Select Revenue Bucket Type ‘FLIP_TRX_BY_GRP’ and Search.
2) Select the first Revenue Bucket Code for ‘FLIP_TRX_BY_GRP’ listed below
3) Select the Edit button.

12) Update the Description in order to create revenue buckets to qualify/group all items, then search and select the
transaction codes that should be linked to this Revenue Bucket Code. Save changes after editing each Revenue Bucket
Code. Complete this task until all transaction codes are linked to Revenue Bucket Codes except for the transaction
codes of payments.
13)The detail section of the printed invoice will follow the order of the fiscal folio bucket created, given by the key
Group_X
14) try to create the as many fiscal revenue buckets groups as subgroup transaction codes the property have been
configured
15) wrapper trx code should be created in a separated fiscal rev. bucket.
16) Revenue bucket value must include the product code according to Mexico’s regulation and divided by pipe the
measure unit, and the objecto impuesto
Regarding the product code, the consultant should request this information to the hotel

The following codes should be configured, and the property must be agree on it.

CODES DESCRIPTION

Product code
Information should be obtained from SAT document Validate with the property and the property
under the name C_claveProdServ should give this information
 Unit of Information should be obtained from SAT document Validate with the property and the property
measure under the name C_claveUnidad should give this information

For taxable it should be 02 and for nontaxable 01

Objeto Validate with the property and the property
impuesto should give this information

Note: If this Revenue Bucket Type and Revenue Bucket Codes are not available in SID Data, they should be set up
manually with the same values as below. The description can then be updated and the transaction codes linked as
required. If needed create new Bucket Codes as demand.
REVENUE BUCKET CODE DESCRIPTION BUCKET VALUE COMMENTS
TYPE

FLIP_TRX_BY_GRP GROUP_1 e.g. Room 90111500|Os|02

Either Cabys code and measure unit should be
Revenue
requested to the property based on the trx codes
subgroup and according to the codification created
by the CR government

FLIP_TRX_BY_GRP GROUP_2 e.g. Food and e.g. Either product code and measure unit should be
Beverage 90111500|Os|02 requested to the property based on the trx codes
subgroup and according to the codification created
by the Government
FLIP_TRX_BY_GRP GROUP_3 SPA Either product code and measure unit should be
Product Code as
requested to the property based on the trx codes
needed|Unit code
subgroup and according to the codification created
e.g. by the Government
90111500|Os|02

FLIP_TRX_BY_GRP GROUP_4 As needed

Product Code as
needed|Unit
code|tax object

FLIP_TRX_BY_GRP GROUP_5 As needed

Product Code as
needed|Unit
code|tax object

FLIP_TRX_BY_GRP GROUP_6 As needed

Product Code as
needed|Unit
code|tax object

FLIP_TRX_BY_GRP GROUP_7 As needed

Product Code as
needed|Unit code

FLIP_TRX_BY_GRP GROUP_8 As needed

Product Code as
needed|Unit
code|tax object
 FLIP_TRX_BY_GRP GROUP_27 Tips
Product Code as
needed|Unit
code|tax object

FLIP_TRX_BY_GRP GROUP_28 Paid Outs

Product Code as
needed|Unit code

Important:
Starting from the GROUP_25 must be used fof grouping the different the non taxable trx codes like tips, paid outs and
so on. As standard Tips should be grouped in the GROUP_27 and Paid Outs in GROUP_28

Each fiscal folio bucket code field “Bucket Value” the must be filled with Product Code accordingly with the need.
Confirm with the property in order to have the correct Product Code.
In addition, it´s mandatory to have the “|” symbol followed by the unit Code, which can be defined by the hotel.
Note that the revenue type might be created manually.
In this case, login in OPERA and go to

Administration > Financial > Transaction Management > Fiscal Folio Bucket Types
Click on “New” then create the Bucket Type like below
Type: FLIP_TRX_BY_GRP
Description: FLIP Transaction Codes by Group
Click on the “Save” button.

Next step is to create the Bucket Codes, for that go to

Administration > Financial > Transaction Management > Fiscal Folio Bucket Codes.
Select the Fiscal Folio Bucket Type previously created, FLIP_TRX_BY_GRP;

Terceros rev bucket

In order to identify the products and services to be sold in behalf of the third party, the transaction codes should be
grouped in the same fiscal rev bucket

Go to administration/financial/fiscal folio buckets codes

Within the buket type FLIP_TRX_BY_GROUP create the new revenue bucket with the following information

Description: the name of the service o product in the way the property wants to be created in the invoice
Bucket Value: sat poduct code | sat unit of measure | terceros RFC

Fiscal Folio Bucket Codes and Fiscal Folio Bucket Types (VOXEL Partner Related)
Edit the following Fiscal Folio Codes by completing them with the corresponding Transaction Codes.
To access Fiscal Folio Codes:
Path: Administration > Financial > Fiscal Management > Fiscal Folio Buckets Codes

Note: Only the Description and Transaction Code fields can be changed according to the hotel’s needs.
1) Select Revenue Bucket Type ‘OFIS_PAY_SUBTYPE’ and Search.
2) Select the first Revenue Bucket Code for ‘OFIS_PAY_SUBTYPE’ listed below with a Bucket Value.
NOTE: Anything without a Bucket Value will not be used for Voxel installations.
3) Select the Edit button.
4) Update the Description and Bucket Value to the value shown on the list below, then search and select the transaction
codes that should be linked to this Revenue Bucket Code. Save changes after editing each Revenue Bucket Code.
REVENUE BUCKET BUCKET
CODE DESCRIPTION
TYPE VALUE
OFIS_PAY_SUBTYPE CASH 01
Cash Payments
(Efectivo)

OFIS_PAY_SUBTYPE OTHER_CASH_1 Other Cash Payment 1

OFIS_PAY_SUBTYPE OTHER_CASH_2 Other Cash Payment 2

OFIS_PAY_SUBTYPE OTHER_CASH_3 Other Cash Payment 3

OFIS_PAY_SUBTYPE OTHER_CASH_4 Other Cash Payment 4

OFIS_PAY_SUBTYPE OTHER_CASH_5 Other Cash Payment 5

OFIS_PAY_SUBTYPE CHECK 02
Check Payments
(Cheque nominative)

OFIS_PAY_SUBTYPE CREDIT 25
Direct Bill Payments
(Remisión de deuda)

OFIS_PAY_SUBTYPE CCARD_1 04
Credit Card Payments 1
(Tarjeta de crédito)

OFIS_PAY_SUBTYPE CCARD_2 Credit Card Payments 2

OFIS_PAY_SUBTYPE CCARD_3 Credit Card Payments 3

OFIS_PAY_SUBTYPE CCARD_4 Credit Card Payments 4

OFIS_PAY_SUBTYPE CCARD_5 Credit Card Payments 5

OFIS_PAY_SUBTYPE CCARD_6 Credit Card Payments 6

OFIS_PAY_SUBTYPE CCARD_7 Credit Card Payments 7

 OFIS_PAY_SUBTYPE CCARD_8 Credit Card Payments 8

OFIS_PAY_SUBTYPE CCARD_9 Credit Card Payments 9

OFIS_PAY_SUBTYPE CCARD_10 Credit Card Payments 10

OFIS_PAY_SUBTYPE OTHER_1 99
Other Payments
(Por definer)

OFIS_PAY_SUBTYPE OTHER_2 28
Debit Card
(Tarjeta de débito)

OFIS_PAY_SUBTYPE OTHER_3 03
Bank Transfer/EFT
(Transferencia electrónica de fondos)

OFIS_PAY_SUBTYPE OTHER_4 05
Company Money/Points
(Monedero electrónico)

OFIS_PAY_SUBTYPE OTHER_5 Paypal (Dinero electrónico) 06

OFIS_PAY_SUBTYPE OTHER_6
Deposit Transfer at Check in
*Set just the code for Deposit Transfer at Check in this revenue bucket
code. Also, cannot be present on other OFIS Revenue bucket code.

OFIS_PAY_SUBTYPE OTHER_7 Other Payments 7

OFIS_PAY_SUBTYPE OTHER_8 Other Payments 8

OFIS_PAY_SUBTYPE OTHER_9 Other Payments 9

OFIS_PAY_SUBTYPE OTHER_10 Other Payments 10

Payment Types SAT Codification

C_FORMAPAGO DESCRIPCIÓN

01 Efectivo

02 Cheque nominativo

03 Transferencia electrónica de fondos

04 Tarjeta de crédito

05 Monedero electrónico
06 Dinero electrónico

08 Vales de despensa

12 Dación en pago

13 Pago por subrogación

14 Pago por consignación

15 Condonación

17 Compensación

23 Novación

24 Confusión

25 Remisión de deuda

26 Prescripción o caducidad

27 A satisfacción del acreedor

28 Tarjeta de débito

29 Tarjeta de servicios

30 Aplicación de anticipos

31 Intermediario pagos

99 Por definir
OFIS_PAY_SUBTYPE > OTHER_6 must be used to qualify the transaction code set by the property for the Deposit
Transfer at Check-in. It´s mandatory to be in this revenue code as Edicom will guide their mapping based on that.

 Transaction Codes in Revenue Bucket Code CASH
 List of all Cash (Efectivo) Transaction Codes, with Default Value 01



 Revenue Bucket Code CHECK
 List of all Check (Cheque nominative) Transaction Codes, with Default Value 02



 Revenue Bucket Code CREDIT
 List of all Direct Bill (Remisión de deuda) Transaction Codes, with Default Value 25


 Revenue Bucket Code CCARD_1
 List of all Credit Card (Tarjeta de crédito) Transaction Codes, with Default Value 04



 Revenue Bucket Code OTHER_1
 List of all Other Payment (Por definer) Transaction Codes, with Default Value 99



 Revenue Bucket Code OTHER_2
 List of all Debit Card (Tarjeta de débito) Transaction Codes, with Default Value 28



 Revenue Bucket Code OTHER_3
 List of all Bank Transfer/EFT (Transferencia electrónica de fondos) Transaction Codes, with Default Value 03


 Revenue Bucket Code OTHER_4
 List of all Company Money/Points (Monedero electrónico) Transaction Codes, with Default Value 05



 Revenue Bucket Code OTHER_5
 List of all Paypal (Dinero electrónico) Transaction Codes, with Default Value 06



 Revenue Bucket Code OTHER_6
 List of all Deposit Transfer at Check-in Transaction Codes, with Default Value 99



OFIS_TAX_CODES
5) Select Revenue Bucket Type ‘OFIS_TAX_CODES’ and Search.

6) Select the first Revenue Bucket Code for ‘OFIS_TAX_CODES’ listed below
7) Select the Edit button.
8) Update the Description to the name or percentage of the Tax, then search and select the transaction codes that
should be linked to this Revenue Bucket Code. Save changes after editing each Revenue Bucket Code. Complete
this task until all Tax/VAT transaction codes are linked to Revenue Bucket Codes.
For Example Transaction Code 8000 is IVA Tax. In TAX_1 you would link Transaction code 8000, update the description
to IVA and the bucket value to IVA. The Bucket Value must receive the type of tax, like IVA in this case, as this will be
used to qualify the type of tax to partner.
Note: If this Revenue Bucket Type and Revenue Bucket Codes are not available in SID Data, they should be set up
manually with the same values as below. The description can then be updated and the transaction codes linked as
required.
In this case, login in OPERA and go to

Path: Administration > Financial > Fiscal Management > Fiscal Folio Buckets Types

Click on “New” then create the Bucket Type like below;

Type: OFIS_TAX_CODES
Description: OFIS Tax Codes

Click on the “Save” button

Next step is to create the Bucket Codes, for that go to

Path: Administration > Financial > Fiscal Management > Fiscal Folio Buckets Codes

Select the Revenue Bucket Type previously created, OFIS_TAX_CODES;

Click on “New” then create the Bucket Codes like below

For each new code created to remember to Increase the number on Code field. For reference see below the default.
Please make sure to create the revenue codes necessary to accommodate the different taxes used by the property
Example
 CODE DESCRIPTION BUCKET VALUE
REVENUE BUCKET TYPE

OFIS_TAX_CODES TAX_1 Tax 1 Codes

OFIS_TAX_CODES TAX_2 Tax 2 Codes

OFIS_TAX_CODES TAX_3 Tax 3 Codes

OFIS_TAX_CODES TAX_4 Tax 4 Codes

OFIS_TAX_CODES TAX_5 Tax 5 Codes

OFIS_TAX_CODES TAX_6 Tax 6 Codes

OFIS_TAX_CODES TAX_7 Tax 7 Codes

OFIS_TAX_CODES TAX_8 Tax 8 Codes

OFIS_TAX_CODES TAX_9 Tax 9 Codes

OFIS_TAX_CODES TAX_10 Tax 10 Codes

OFIS_TAX_CODES TAX_11 Tax 11 Codes

OFIS_TAX_CODES TAX_12 Tax 12 Codes

OFIS_TAX_CODES TAX_13 Tax 13 Codes

 OFIS_TAX_CODES TAX_14 Tax 14 Codes

OFIS_TAX_CODES TAX_15 Tax 15 Codes

OFIS_TAX_CODES TAX_16 Tax 16 Codes

OFIS_TAX_CODES TAX_17 Tax 17 Codes

OFIS_TAX_CODES TAX_18 Tax 18 Codes

OFIS_TAX_CODES TAX_19 Tax 19 Codes

OFIS_TAX_CODES TAX_20 Tax 20 Codes

OFIS_TRX_BY_GRP
9) Select Revenue Bucket Type ‘OFIS_TRX_BY_GRP’ and Search.
10) Select the first Revenue Bucket Code for ‘OFIS_TRX_BY_GRP’ listed below 11) Select the
Edit button.

12) Update the Description in order to create revenue buckets to qualify/group all items, then search and select the
transaction codes that should be linked to this Revenue Bucket Code. Save changes after editing each Revenue Bucket
Code. Complete this task until all transaction codes are linked to Revenue Bucket Codes except for the transaction
codes of payments.

Note: If this Revenue Bucket Type and Revenue Bucket Codes are not available in SID Data, they should be set up
manually with the same values as below. The description can then be updated and the transaction codes linked as
required. If needed create new Bucket Codes as demand.

REVENUE BUCKET TYPE CODE DESCRIPTION BUCKET VALUE

OFIS_TRX_BY_GRP GROUP_1
e.g. Room
Revenue
 OFIS_TRX_BY_GRP GROUP_2
e.g. Food and
Beverage

OFIS_TRX_BY_GRP GROUP_3 As needed

OFIS_TRX_BY_GRP GROUP_4 As needed

OFIS_TRX_BY_GRP GROUP_5 As needed

OFIS_TRX_BY_GRP GROUP_6 As needed

OFIS_TRX_BY_GRP GROUP_7 As needed

OFIS_TRX_BY_GRP GROUP_8 As needed

OFIS_TRX_BY_GRP GROUP_9 As needed

OFIS_TRX_BY_GRP GROUP_10 As needed

OFIS_TRX_BY_GRP GROUP_11 As needed

OFIS_TRX_BY_GRP GROUP_12 As needed

OFIS_TRX_BY_GRP GROUP_13 As needed

OFIS_TRX_BY_GRP GROUP_14 As needed

OFIS_TRX_BY_GRP GROUP_15 As needed

OFIS_TRX_BY_GRP GROUP_16 As needed

OFIS_TRX_BY_GRP GROUP_17 As needed

OFIS_TRX_BY_GRP GROUP_18 As needed

OFIS_TRX_BY_GRP GROUP_19 As needed

OFIS_TRX_BY_GRP GROUP_20 As needed

Each fiscal folio bucket code field “Bucket Value” the must be filled with SAT Product Code accordingly with the need.
Confirm with the property in order to have the correct Product Code.
In addition it´s mandatory to have the “|” symbol followed by the SAT unit Code, which can be defined by the hotel. If
it´s not can be used “H87”.
Note that the revenue type might be created manually.
In this case, login in OPERA and go to
Path: Administration > Financial > Fiscal Management > Fiscal Folio Buckets Types

Click on “New” then create the Bucket Type like below

Type: OFIS_TRX_BY_GRP

Description: OFIS Transaction Codes by Group

Click on the “Save” button.

Next step is to create the Bucket Codes, for that go to

Path: Administration > Financial > Fiscal Management > Fiscal Folio Buckets Codes

Select the Fiscal Folio Bucket Type previously created, OFIS_TRX_BY_GRP;

*** Fiscal Folio Buckets Code: Packages Configuration If the property wants the package and the respective elements in
one single line on the invoice, then the transaction codes used as wrapper and room transaction code used in rates
must be created in a separated fiscal folio bucket code in order to attend to the logic.
**If the package elements should be declared individually do not set up the wrapper transaction code in any fiscal folio
bucket code. This way it will not be considered an Item.

CONNECT WITH US
Call +1.800.ORACLE1 or visit oracle.com.
Outside North America, find your local office at oracle.com/contact.

blogs.oracle.com facebook.com/oracle twitter.com/oracle

Copyright © 2023, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without
notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties
and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed
either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without
our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

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. 0120

OPERA Cloud Mexico Primary Data Document March,

2023