Guide Lacls Costa Rica Ufig XML Canonical Efactura

Oracle Financials Cloud
Latin America Cloud Local Solution

Costa Rica
XML Canonical for Electronic

Invoice
User and Functional Implementation Guide
Version 15
01 Dec 2022
DISCLAIMER:
This guide may contain screen shots and output reports to facilitate the user comprehension about the
topic. The content represents a fictitious sample. Any similarity to actual persons, living or dead, or
company names, active or inactive, is purely coincidental and not intended in any manner.
LACLS Costa Rica – XM Canonical for Electronic Invoice – User and Functional Implementation Guide
1
TABLE OF CONTENTS
TABLE OF CONTENTS ..............................................................................................................................................2
REVISION HISTORY ......................................................................................................................................................... 4
INTRODUCTION TO XML CANONICAL FOR ELECTRONIC INVOICE FOR COSTA RICA ................................................5
INTENDED AUDIENCE...................................................................................................................................................... 5
ASSUMPTIONS .............................................................................................................................................................. 5
MACRO FLOW .............................................................................................................................................................. 6
CONCATENATE SPECIAL INFORMATION .............................................................................................................................. 7
PREPARING TO INSTALL/UPDATE ...........................................................................................................................8
GETING THE LATEST VERSION ........................................................................................................................................... 8

CREATING PACK STAGE AREA ........................................................................................................................................... 8
INSTALLATION/UPDATE TASKS ..............................................................................................................................9
CREATE BI FOLDERS STRUCTURE – INSTALL / UPDATE........................................................................................................... 9

BI Folders Structure Required ............................................................................................................................... 9
Create BI Folders Structure ................................................................................................................................. 10
BI PUBLISHER FILES...................................................................................................................................................... 11
BI Files Upload to Cloud...................................................................................................................................... 12
CONFIGURATION TASK ........................................................................................................................................ 15
TAX REPORTING TYPES ................................................................................................................................................. 15

MH Vat Codes: LACLS_CR_VAT_CODE ............................................................................................................... 15
MH Rate Codes: LACLS_CR_RATE_CODE ............................................................................................................ 16
Product Type: LACLS_CR_PRODUCT_TYPE ......................................................................................................... 16
MH Environment: LACLS_CR_EFD_ENVIRONMENT............................................................................................ 17
COMMON LOOKUPS..................................................................................................................................................... 17
Document Type: LACLS_CR_DOCUMENT_TYPE ................................................................................................. 17
Reference Document Code: LACLS_CR_EFD_REF_CODE .................................................................................... 18
Payment Condition: LACLS_CR_PAYMENT_CONDITION .................................................................................... 18
Reference Doc Type: LACLS_CR_REF_DOC_TYPE ............................................................................................... 18
Establishment Number: LACLS_CR_ESTABLISH_NUMBER ................................................................................. 19
Billing Point: LACLS_CR_BILLING_POINT ............................................................................................................ 19
Inconterm Codes: LACLS_CR_INCONTERMS ....................................................................................................... 20
Invoice Status: LACLS_CR_EFD_STATUS ............................................................................................................. 20
Payment Term: LACLS_CR_PAYMENT_TERMS ................................................................................................... 21
Payment Term FROM / TO: LACLS_CR_MH_PAYMENT_TERM .......................................................................... 22
E-invoice Condiction: LACLS_CR_EINVOICE_CONDITION ................................................................................... 23
Unit of Mesure: LACLS_CR_UOM_CODES .......................................................................................................... 23
Product Code: LACLS_CR_PRODUCT_CODE_MH ................................................................................................ 23
Default Context: LACLS_DEFAULT_CONTEXT ..................................................................................................... 24
STANDARD LOOKUPS .................................................................................................................................................... 25
Customer Doc Type: ZX_REGISTRATIONS_TYPE ................................................................................................. 25
LACLS Costa Rica – XML Canonical for Electronic Invoice – User and Functional Implementation Guide
2
VALUE SETS ................................................................................................................................................................ 26
Document Type: LACLS_CR_DOCUMENT_TYPE ................................................................................................. 26
Reference Document Code: LACLS_CR_REF_CODE ............................................................................................ 26
Payment Condition: LACLS_CR_PAYMENT_CONDITION .................................................................................... 27
Reference Doc Type: LACLS_CR_REF_DOC_TYPE ............................................................................................... 27
Establishment Number: LACLS_CR_ESTABLISH_NUMBER ................................................................................. 27
Billing Point: LACLS_CR_BILLING_POINT ............................................................................................................ 28
Incoterm Codes: LACLS_CR_INCONTERMS ......................................................................................................... 28
Invoice Status: LACLS_CR_EFD_STATUS ............................................................................................................. 29
Payment Term: LACLS_CR_PAYMENT_TERMS ................................................................................................... 29
CABYS Code: LACLS_CR_CABYS_CODE ............................................................................................................... 29
Duty Item: LACLS_CR_DUTY_ITEM ..................................................................................................................... 30
Einvoice Condition: LACLS_CR_EINVOICE_CONDITION ...................................................................................... 30
DESCRIPTIVE FLEXFIELDS ............................................................................................................................................... 31
Receivables Transaction Header ........................................................................................................................ 31
Receivables Transaction Type ............................................................................................................................ 32
Party Sites........................................................................................................................................................... 34
Locations ............................................................................................................................................................ 35
Memo Line.......................................................................................................................................................... 35
Invoice Line ......................................................................................................................................................... 36
FND Lookups – Payment Term ........................................................................................................................... 37
ITEM TYPE – INVENTORY CATALOG ................................................................................................................................. 38
GEOGRAPHY LOOKUP ................................................................................................................................................... 39
Geography Code: LACLS_CR_GEOGRAPHY_CODES ............................................................................................ 39
ENTERING LACLS ADDITIONAL INFORMATION ..................................................................................................... 41
DESCRIPTIVE FLEXFIELDS ............................................................................................................................................... 41

Receivables Transaction ..................................................................................................................................... 41
Receivables Transaction Type ............................................................................................................................ 42
Locations ............................................................................................................................................................ 43
Party Sites........................................................................................................................................................... 43
Memo Lines ........................................................................................................................................................ 44
Receivables Transaction Lines ............................................................................................................................ 44
TAX REPORTING TYPES ................................................................................................................................................. 45
Vat Codes: LACLS_CR_VAT_CODE ...................................................................................................................... 45
Rate Code: LACLS_CR_RATE_CODE .................................................................................................................... 45
PRODUCT TYPE: LACLS_CR_PRODUCT_TYPE ...................................................................................................... 45
Environment Type: LACLS_CR_EFD_ENVIRONMENT .......................................................................................... 46
ITEM INFORMATION – INVENTORY CATALOG..................................................................................................................... 46
MONITORING PROCESS ....................................................................................................................................... 48
THIRD PARTY INTEGRATION USER AND ROLES ..................................................................................................... 49
3
REVISION HISTORY
This document will continue to evolve as existing sections change and new information is added. All updates are
logged below:
Data Version Description Delivery by Included in

Standalone Patchset
19-Nov-2020 1 Document creation

07-Dec-2020 2 Type fix
08-Dec-2020 3 Type fix
15-Dec-200 4 Add LACLS_CR_EFD_ENVIRONMENT tax reporting type
14-Jan-2021 5 Add CONCATENATESPECIAL INFORMATION gap
- LACLS_CR_EINVOICE_CONDITION lookup
- LACLS_CR_EINVOICE_CONDITION Value Set
‘Situación del comprobante electrónico’ attribute in
header invoice DD
04-Fev-2021 6 Create lookup LACLS_CR_UOM_CODES
23-Feb-2021 7 Remove:
- Payment Terms DFF -
LACLS_CR_PAYMENT_TERMS
- Receivables Lines and Memo Line DFF -
LACLS_CR_ITEM_CODE
- Item Catalog -
LACLS_CR_EFD_PRODUCT_CODE
- Item Catalog – LACLS_CR_PRODUCT_CODE
Create:
- Lookup LACLS_CR_MH_PAYMENT_TERM
- Lookup LACLS_CR_PRODUCT_CODE_MH
- Receivables Lines DFF -
LACLS_CR_DISCOUNT_LINE_REF
Tax Reporting Type LACLS_CR_PRODUCT_TYPE
03-Mar-2021 8 Update LACLS_CR_MH_PAYMENT_TERM lookup 32624881 21B
definition
23-Mar-2021 9 Add instructions related to Maintenance
Assistant (MNT)
13-May-2021 10 Typo fixes
08-Jun-2021 11 Change guide name
10-Aug-2021 12 Remove value set ‘LACLS_CR_ECONOMIC_ACTIVITY’
Update DFF ‘HZ_PARTY_SITES’ attribute
‘LACLS_CR_ECONOMIC_ACTIVITY’ to text
Add note for load Economic activities
11-Nov-2021 13 Note about data transformation
03-Oct-2022 14 Remove attribute LACLS_CR_DISCOUNT_LINE_REF for 34609721 22D
DFF invoice line
Update definition for References Line Discount in
ENTERING LACLS ADDITIONAL INFORMATION
RECEIVABLES TRANSACTION LINES
29-Nov-2022 15 Update ZX_REGISTRATIONS_TYPE lookup code
4
INTRODUCTION TO XML CANONICAL FOR ELECTRONIC INVOICE FOR COSTA
RICA
Latin America Cloud Local Solution (LACLS) for Costa Rica is a set of components that complements the core
functionalities providing new features used to meet legal requirements requested by government agencies.
For Costa Rica, the government agency responsible to establish the legal requirements is named MH (Ministerio de
Hacienda).
LACLS released “XML Canonical for Electronic Invoice” solution for Costa Rica providing BI Publisher extractor to
generate canonical XML file containing information about Oracle Receivables (AR) transactions eligible to generate
electronic fiscal document (EFD). The XML file can be consumed by the third party software providers to create
electronic fiscal document files to be sent to the government agency (MH).
Important: The information contained into the canonical XML file is extracted from the Oracle ERP Cloud tables
considering the database model. The extractor does not perform calculation, sum or any other data manipulation
over the extracted information. If a data transformation be required, it must be done by the Third Party or custom.
In this manual you will find:
 Macro Flow;
 The Additional Information required in order to issue Electronic Invoice;
 The steps describing how to setup and enter these Additional Information;
 The steps to upload the BI Publisher artifacts in the Cloud instance;
 How to monitor the process.
INTENDED AUDIENCE
Welcome to LACLS XML Canonical for Electronic Invoice solution for Costa Rica. This guide is intended to be used
by the Oracle ERP Cloud functional implementers and key users.
This guide assumes you have a working knowledge of the following:
• The principles and practices of your business area;

• Computer desktop application usage and terminology;
 BIP architecture
 Web Services concepts
ASSUMPTIONS
The solution will be seen here assume that the following functionalities have been set up in Oracle ERP:
 Data Security
 Geographies
 Enterprise Structure
 Tax Regime information
 Tax Party Profiles
LACLS Costa Rica – XM Canonical for Electronic Invoice – User and Functional Implementation Guide
5
 Tax Rules
 Customers
 Reference Data Sets
 Common Options for Receivables
MACRO FLOW
The solution is based on transactions created under Oracle Receivables (AR) in the ERP Cloud.
The solution is composed by BI Publishers that expose the AR information in a canonical XML and two Web Services
(WS):
 one to execute the BI extractors and
 other to update information in AR
o Status
o Message
o UUID Number
o UUID Date
The third party is responsible for the governance of the integration process: requesting the transactions file,
consuming the file, controlling which transaction was already captured and sent to MHI, validating, transforming
and formatting the information according government layout, and returning the set of information to Oracle ERP
Cloud. In general the print process for ‘factura’ is also part of the third party scope, or an ERP custom report, since
the standard report in Oracle ERP is for global purpose and might not present specific information required by the
country.
The flow starts by the third party calling a WS to run the BI Publisher Extractor (1). This BI will return select all
Receivables transactions eligible to generate an electronic voucher (2). A transaction is eligible to generate an
electronic voucher when:
 The transaction status in Oracle ERP is completed. That means the information cannot be changed.
 The type of transaction is flagged as "electronic invoice". All transactions are associated to a
transaction type, the transaction type has a flag to identify if the transactions generated under
that type must be issued electronically.
 The transaction E-Invoice Status is NULL or “3-ERROR”. E-Invoice Status as NULL means this is a
new transaction, and E-Invoice Status as 3-ERROR means this transaction once was rejected by
MH and now might be fixed and needs to be processed by MH again, since for Costa Rica the
Electronic Invoice is not gapless.
6
Once third party has the xml file in its possession, he is responsible to decompose the file into individual transaction
(3) in order call the WS to update the CFE Status as “SENT” (captured by third party) (4). This field should be updated
with “SENT”, preventing that the transaction be retrieved again in the next execution of the extractor;
After the update at MH status, the third party must process each transaction: validating, transforming and
formatting (5) the new pay load to send to MH (7). Including digital signature (6), when required, according to MH
specifications. The control regarding which transaction has already been processed and communicated with MH is
under third party responsibility as well.
Once MH has answered, the third party needs to return these information to Oracle ERP Cloud (9).
The return information required are:
 KEY Status:
 1-FINISHED – Indicates the electronic voucher was processed and approved by MH;
 2-WARNING – Indicates the electronic voucher was processed and approved with warnings
by MH;
 3-ERROR – Indicates the electronic voucher was processed and rejected by MH.
 KEY Number – Number of Key assigned by MH;
 KEY Date – Date of Key generation.
 KEY Message – Relevant messages (optional).
CONCATENATE SPECIAL INFORMATION
The solution will be show concatenate special information:
 Key Number
- The first three digits correspond to the country code (506).
- From the fourth to the fifth digit, it corresponds to the day the electronic invoice is generated.
- From the sixth to the seventh digit, it corresponds to the month in which the electronic invoice is
generated.
- From the eighth to the ninth digit, it corresponds to the year in which the electronic invoice is
generated.
- From the tenth to the twenty-first digit, it corresponds to the issuer's identification number. NIT
legal entity
- From the twenty-second to the forty-first digit, it corresponds to the consecutive numbering of the
electronic invoice. trx number with leading zeros
- The forty-second corresponds to the situation of the electronic invoice.
- From the forty-third to the fiftieth digit, it corresponds to the security code generated by the
taxpayer's system. Last 8 digits of the invoice id
 Sequence Number
- Establishment Number
- Billing Point
- Transaction Type
- Invoice Number
7
PREPARING TO INSTALL/UPDATE
This chapter provides instructions for obtaining the latest version of Costa Rica solution and assists in
creating a stage area for installation.
GETING THE LATEST VERSION
To download the latest Costa Rica Update Pack available, please refer to the Note Latin America Cloud
Local Solutions (LACLS) - How to get the latest Pack (Doc ID 2588752.1) and search for Costa Rica
component in Table 3.1.1. "Latest quarterly cumulative pack" column contains the link to download the
latest Pack released. Example:
CREATING PACK STAGE AREA

1. Before starting, create a new folder to be used as a stage area during the installation process.
Example for Windows user: c:\temp\LACLS_PACKS
Transfer the Costa Rica Update Pack to stage area folder and unzip it.
Important:
2. Go to Pack folder and review the README.html for Installation Instructions. In README is also
detailed the Bugs fixed and Source Files.
8
INSTALLATION/UPDATE TASKS
This chapter provides a guide for Installing/Updating Costa Rica XML Canonical for Electronic Invoice
solutions artifacts. Mandatory for all customers who are installing/upgrading Costa Rica solution.
For customers using Maintenance Assistant (MNT), please skip this chapter since all manual procedures
will be replaced by MNT processing.
After apply the Pack manually or using MNT please follow to "Configuration Tasks" chapter.
Important:
It is mandatory do not create or update any report or folder below the Shared Folders  Custom 
Local Solution  CR since updates from Latin America Cloud Local Solution for Costa Rica will overwrite
the files in this folder, every time the upload process be executed.
CREATE BI FOLDERS ST RUCTURE – INSTALL / UPDATE
Verify if BI folders structure required for Costa Rica is already available. In this case, the steps describe in
this section can be skipped and you can follow to the “BI Files Upload to Cloud” steps.
1. Access BI Publisher Enterprise Tool (including /xmlpserver after URL used to access the Cloud
environment). Example: https://XXXX.XX.XXX>.oraclecloud.com/xmlpserver
2. Click on Catalog option
3. Click on Expand Shared Folders option
4. Click on Expand Custom option
5. Under the Custom folder, verify if there is a folder called Local Solution
6. Under the Local Solution folder, verify if there is a folder called CR
BI FOLDERS STRUCTURE REQUIRED
 CR folders structure required for LACLS Reports:
/Custom/Local Solution/CR/E-INVOICE
/Custom/Local Solution/CR/E-INVOICE/Data Models
/Custom/Local Solution/CR/E-INVOICE/Process
/Custom/Local Solution/CR/E-INVOICE/Process/Data Models
9
CREATE BI FOLDERS STRUCTURE
If the structure required for Costa Rica is not available, create it. The steps below assumes the Local
Solution folder is not available but you must follow the steps according the structure available in your
environment.
5. Under the folder Custom, create a new folder called Local Solution. To do that, click on Create
icon.
6. Choose the Folder option
Enter the name exactly as bellow and press Create button.
Create Local Folder Solution
*Folder Name Local Solution
7. Under the structure /Shared Folders/Custom/Local Solution, create the folder CR

*Folder Name CR
9. Under CR folder, create new folder called E-INVOICE

*Folder Name E-INVOICE
11. Under the structure /Shared Folders/Custom/Local Solution/CR/E-INVOICE, create a new

folder called Data Models
*Folder Name Data Models
13. Under the structure /Shared Folders/Custom/Local Solution/CR/E-INVOICE, create a new
folder called Process
10
*Folder Name Process
15. Under the structure /Shared Folders/Custom/Local Solution/CR/E-INVOICE/Process, create a

new folder called Data Models
*Folder Name Data Models
BI PUBLISHER FILES
This step requires you have downloaded the pack, has created the Pack stage area and had the BI Folders
Structure created.
Who are installing or updating LACLS for Costa Rica must upload files with the extension “xdoz” and
“xdmz” files in order to have BI Reports running successfully.
XML Canonical for Electronic Invoice – Control Panel Layout Template “xdoz”:
1. Pack source files: <PACK_PATH>\CR\E-INVOICE\CA\BI\template\ESA
2. BI destination Folder: /Shared Folders/Custom/Local Solution/CR/E-INVOICE
XML Canonical for Electronic Invoice – Control Panel Data Model “xdmz”:
1. Pack source files: <PACK_PATH>\CR\E-INVOICE\CA\BI\datamodel
2. BI Destination Folder: /Shared Folders/Custom/Local Solution/CR/E-INVOICE/Data Models
XML Canonical for Electronic Invoice – XML Extractor Layout Template “xdoz”:
3. Pack source files: <PACK_PATH>\CR\E-INVOICE\CA\BI\Process\template
4. BI destination Folder: /Shared Folders/Custom/Local Solution/CR/E-INVOICE/Process
XML Canonical for Electronic Invoice – XML Extractor Data Model “xdmz”:
3. Pack source files: <PACK_PATH>\CR\E-INVOICE\CA\BI\Process\datamodel
4. BI Destination Folder: /Shared Folders/Custom/Local Solution/CR/E-INVOICE/Process/Data
Models
11
BI FILES UPLOAD TO CLOUD
1. Access BI Publisher Enterprise Tool (including /xmlpserver after URL used to access the Cloud
environment). Example: https://XXXX.XX.XXX>.oraclecloud.com/xmlpserver
2. Go to /Shared Folders/Custom/Local Solution/CR/E-INVOICE folder and click on Upload
Resource icon
The following page will be displayed:
3. Press “Choose File” button and select the file to be uploaded in the following path:
<PACK_PATH>\CR\E-INVOICE\CA\BI\template\ESA\<File Name>.xdoz
Check the “Overwrite existing file” and then Click on the Upload button
IMPORTANT:
In case of a New Installation repeat the previous step for all .xdoz files available in the folder
<PACK_PATH>\CR\E-INVOICE\CA\BI\template\ESA;
In case of Pack Update you may apply only the modified files since your last installation or
update. Make sure to read carefully the Packs’s readme to identify the list of files to be uploaded.
If you don’t have all the packs applied so far then you may need to evaluate the delivered packs
since your last install or update to build a list of files to be updated. In case of doubts upload all
the files available in the folder <PACK_PATH>\CR\E-INVOICE\CA\BI\template\ESA.
4. Click on Expand the folder E-INVOICE to confirm the files were successfully uploaded.
12
5. Go to /Shared Folders/Custom/Local Solution/CR/E-INVOICE/Data Models folder and click on
Upload Resource icon
<PACK_PATH>\CR\E-INVOICE\CA\BI\datamodel\<File Name>.xdmz
IMPORTANT:
<PACK_PATH>\CR\E-INVOICE\CA\BI\datamodel;
the files available in the folder <PACK_PATH>\CR\E-INVOICE\CA\BI\datamodel.
7. Click on Expand the folder Data Models to confirm the files were successfully uploaded.
8. Go to /Shared Folders/Custom/Local Solution/CR/E-INVOICE/Process folder and click on

Upload Resource icon
<PACK_PATH>\CR\E-INVOICE\CA\BI\Process\template <File Name>.xdoz
IMPORTANT:
<PACK_PATH>\CR\E-INVOICE\CA\BI\Process\template;
the files available in the folder <PACK_PATH>\CR\E-INVOICE\CA\BI\Process\template.
10. Click on Expand the folder Process to confirm the files were successfully uploaded.
11. Go to /Shared Folders/Custom/Local Solution/CR/E-INVOICE/Process/Data Models folder and

click on Upload Resource icon
<PACK_PATH>\CR\E-INVOICE\CA\BI\Process\datamodel\<File Name>.xdmz
13
IMPORTANT:
<PACK_PATH>\CR\E-INVOICE\CA\BI\Process\datamodel;
the files available in the folder <PACK_PATH>\CR\E-INVOICE\CA\BI\Process\datamodel.
13. Click on Expand the folder Data Models to confirm the files were successfully uploaded.
14
CONFIGURATION TASK
In order to provide some specific country legal requirement, some additional information, not available originally
on Oracle ERP Cloud are required. Follow setup details describing how to define each information.
TAX REPORTING TYPES
Attention: Some of those Tax Reporting Types may be being shared by other Costa Rica solutions. So, before you
create them check if it already exists.
To create Tax Reporting Types follow the next steps:
1. Go to “Setup and Maintenance” tasks.

2. Search and select the task “Manage Tax Reporting Types”.
3. On “Search Results” area press “Create” icon.
4. Create the “Tax Reporting Type” entering each information as follow in the next topics.
MH VAT CODES: LACLS_CR_VAT_CODE
This tax reporting type will identify the VAT type applied on the Receivables transactions. For MH this information
will identify the Billing Indicator.
Tax
Tax Reporting Type Reporting Data Minimum Maximum Reporting
Tax Reporting Type Code Country
Name Type Type Length Length Type Uses
Purpose
Tax
Costa
LACLS_CR_VAT_CODE LACLS_CR_VAT_CODE reporting Text 1 30 Tax Rate
Rica
type
Tax Reporting Code Description

01 Impuesto al Valor Agregado
02 Impuesto Selectivo de Consumo
03 Impuesto unico a los combustivos
04 Impuesto especifico de bebidas alcohólicas
05 impuesto especifico sobre las bebidas envasadas sin contenido alcoholico y jabones de tocador
06 impuesto a los productos de tabaco
07 IVA (cálculo especial)
20 IVA Régimen de Bienes Usados (Factor)
21 Impuesto Especifico al Cemento
99 Otros
15
MH RATE CODES: LACLS_CR_RATE_CODE
This tax reporting type will classify the tax rate applied on the Receivables transaction.
Tax
Reporting Data Minimum Maximum Reporting
Tax Reporting Type Code Tax Reporting Type Name Country
Type Type Length Length Type Uses
Purpose
Tax
Costa
LACLS_CR_RATE_CODE LACLS_CR_RATE_CODE reporting Text 1 30 Tax Rate
Rica
type

01 Tarifa 0% (Exento)
02 Tarifa Reducida 1%
03 Tarifa reducida 2%
04 Tarifa reducida 4%
05 Transitorio 0%
06 Transitorio 4%
07 Transitorio 8%
09 Tarifa General 13%
PRODUCT TYPE: LACLS_CR_PRODUCT_TYPE
This additional information identify the tax type and must be entered for each tax rate defined to Costa Rica.
Tax
Reporting Data Minimum Maximum Reporting
Tax Reporting Type Code Tax Reporting Type Name Country
Type Type Length Length Type Uses
Purpose
Tax
Costa
LACLS_CR_PRODUCT_TYPE LACLS_CR_PRODUCT_TYPE reporting Text 1 30 Tax Rate
Rica
type

BIENES Bienes
SERVICIOS Servicios
16
MH ENVIRONMENT: LACLS_CR_EFD_ENVIRONMENT
This tax reporting type will identify the environment.
Tax Dat
Reportin
Reporting Countr a Minimu Maximu
Tax Reporting Type Code Tax Reporting Type Name g Type
Type y Typ m Length m Length
Uses
Purpose e
Tax Party
LACLS_CR_EFD_ENVIRONMEN LACLS_CR_EFD_ENVIRONMEN Costa Tex
reportin 1 30 tax
T T Rica t
g type profile

PRUEBAS Pruebas
PRODUCTIVO Productivo
COMMON LOOKUPS
The “XML Canonical for Electronic Invoice” solution requires new lookup types to setup and control the process.
To create new common lookup types execute the following steps:

1) Open the application and select the “Setup and Maintenance” task group.
2) Search and select the task “Manage Common Lookups”.
3) Click on the “Create” button and fill the fields and Save.
Attention: Some of these Lookup Types may be being shared by other Costa Rica solutions. So before you create
them check if it already exists.
The following new lookup types are required in E-Invoice process:
DOCUMENT TYPE: LACLS_CR_DOCUMENT_TYPE

Used to inform the E-Invoice type code to be used for the Receivables transaction types according to MH rules.
Lookup Type Meaning Description Module
LACLS_CR_DOCUMENT_TYPE LACLS_CR_DOCUMENT_TYPE E-Invoice Type Functional Setup Manager
Lookup Codes
Lookup Code Enabled Meaning Description Tag
01 Yes Factura Electronica Factura Electronica
04 Yes Tiquete Electronico Tiquete Electronico
03 Yes Nota Credito Electronica Nota Credito Electronica
02 Yes Nota Debito Electronica Nota Debito Electronica
05 Yes Nota de despacho Nota de despacho
06 Yes Contrato Contrato
07 Yes Procedimiento Procedimiento
Yes Comprobante emitido en Comprobante emitido en
08 contigencia contigencia
Yes Factura electrónica de Factura electrónica de
09 exportación exportación
17
REFERENCE DOCUMENT CODE: LACLS_CR_EFD_REF_CODE
Determine the reference code for credit memo’s transaction.
Functional
LACLS_CR_EFD_REF_CODE LACLS_CR_EFD_REF_CODE LACLS_CR_EFD_REF_CODE Setup
Manager
Lookup Codes
Anula Documento de
Yes
1 Referencia. Anula Documento de Referencia.
Corrige texto documento
Yes
2 de referencia. Corrige texto documento de referencia.
3 Yes Corrige monto. Corrige monto.
Referencia a otro
Yes
4 documento. Referencia a otro documento.
Sustituye comprobante
Yes provisional por Sustituye comprobante provisional por
5 contingencia. contingencia.
99 Yes Otro Otro
PAYMENT CONDITION: LACLS_CR_PAYMENT_CONDITION

Determine the payment conditions types according to MH rules.
Functiona
LACLS_CR_PAYMENT_CONDITION LACLS_CR_PAYMENT_CONDITION LACLS_CR_PAYMENT_CONDITION l Setup
Manager
Lookup Codes
01 Yes Efectivo. Efectivo.
02 Yes Tarjeta. Tarjeta.
03 Yes Cheque. Cheque.
Transferencia – depósito
Yes
04 bancario. Transferencia – depósito bancario.
05 Yes Recaudado por terceros. Recaudado por terceros.
Otros (se debe indicar el
Yes
99 medio de pago). Otros (se debe indicar el medio de pago).
REFERENCE DOC TYPE: LACLS_CR_REF_DOC_TYPE

Determine the reference doc type for the transaction.
Functional
LACLS_CR_REF_DOC_TYPE LACLS_CR_REF_DOC_TYPE LACLS_CR_REF_DOC_TYPE Setup
Manager
Lookup Codes
18
01 Yes Factura electrónica Factura electrónica
02 Yes Nota de débito electrónica Nota de débito electrónica
03 Yes Nota de crédito electrónica Nota de crédito electrónica
04 Yes Tiquete electrónico Tiquete electrónico
05 Yes Nota de despacho Nota de despacho
06 Yes Contrato Contrato
07 Yes Procedimiento Procedimiento
Yes Comprobante emitido en
08 contingencia Comprobante emitido en contingencia
09 Yes Devolución mercadería Devolución mercadería
Yes Sustituye factura rechazada Sustituye factura rechazada por el Ministerio
10 por el Ministerio de Hacienda de Hacienda
Yes Sustituye factura rechazada
por el Receptor del Sustituye factura rechazada por el Receptor
11 comprobante del comprobante
Yes Sustituye Factura de
12 exportación Sustituye Factura de exportación
13 Yes *Facturación mes vencido *Facturación mes vencido
Yes Comprobante aportado por
contribuyente del Régimen Comprobante aportado por contribuyente del
14 de Tributación Simplificado Régimen de Tributación Simplificado
Yes Sustituye una Factura
15 electrónica de Compra Sustituye una Factura electrónica de Compra
99 Yes Otro Otro
ESTABLISHMENT NUMBER: LACLS_CR_ESTABLISH_NUMBER

Determine the establishment number.
Functional
LACLS_CR_ESTABLISH_NUMBER LACLS_CR_ESTABLISH_NUMBER LACLS_CR_ESTABLISH_NUMBER Setup
Manager
Lookup Codes
001 Yes Establecimiento 001 Establecimiento 001
BILLING POINT: LACLS_CR_BILLING_POINT

Determine the billing point number.
Functional
LACLS_CR_BILLING_POINT LACLS_CR_BILLING_POINT LACLS_CR_BILLING_POINT Setup
Manager
Lookup Codes
19
00001 Yes Punto 00001 Punto 00001
00002 Yes Punto 00002 Punto 00002
00003 Yes Punto 00003 Punto 00003
00004 Yes Punto 00004 Punto 00004
00005 Yes Punto 00005 Punto 00005
INCONTERM CODES: LACLS_CR_INCONTERMS

Determine the Incoterm codes.
Functional
LACLS_CR_INCONTERMS LACLS_CR_INCONTERMS LACLS_CR_INCONTERMS Setup
Manager
Lookup Codes
EXW Yes EXW Ex Works (insert place of delivery)
FCA Yes FCA Free Carrier (Insert named place of delivery)
FAS Yes FAS Free Alongside Ship (insert name of port of
loading)
FOB Yes FOB Free on Board (insert named port of loading)
CFR Yes CFR Cost and Freight (insert named port of
destination)
CIF Yes CIF Cost Insurance and Freight (insert named port
of destination)
CPT Yes CPT Carriage Paid to (insert place of destination)
CIP Yes CIP Carriage and Insurance Paid To (insert place of
destination)
DDP Yes DDP Delivered Duty Paid (Insert place of
destination)
DAP Yes DAP Delivered at Place (insert named place of
destination)
DAT Yes DAT
ZZZ Yes ZZZ
INVOICE STATUS: LACLS_CR_EFD_STATUS

Determine the possible status for a Receivables transaction, when that transaction flows through “XML Canonical
for Electronic Invoice” solution. The Status must represent the Electronic Fiscal Document flow, providing to User a
view about the Electronic Invoice processing. The status listed below is just a recommendation. If Customer has more
status, this can be setup in this lookup.
Attention about information set in Tag field. It will define which Electronic Invoice status must be considered in BI
Extractor selection. By default the BI Extractor will retrieve transaction that is in NULL value in EFD Status, which
means that this transaction has not been processed yet, and also the transactions having STATUS configured as Y in
the Tag field.
Important: The status listed below is just a recommendation.
These statuses will be used by third party while processing Electronic Invoice.
20
Functional
LACLS_CR_EFD_STATUS LACLS_CR_EFD_STATUS LACLS_CR_EFD_STATUS Setup
Manager
Lookup Codes
SENT Yes Enviado Enviado
APPROVED WITH Aceptación parcial Aceptación parcial
Yes
WARNING
APPROVED Yes Aceptado Aceptado
ERROR Yes Rechazado Rechazado
REJECTED Yes Rechazado Rechazado
FIXED Yes Solucionado Solucionado
PROCESSING Yes Procesando Procesando
Example:
Functional
LACLS_CR_EFD_STATUS LACLS_CR_EFD_STATUS LACLS_CR_EFD_STATUS Setup
Manager
Lookup Codes
SENT Yes Enviado Enviado
APPROVED WITH Aceptación parcial Aceptación parcial
Yes
WARNING
ERROR Yes Rechazado Rechazado Y
In the example above, the transactions with status ERROR will be captured by the BI Extractor along with the
new transactions.
PAYMENT TERM: LACLS_CR_PAYMENT_TERMS

Determine the payment term.
Functional
LACLS_CR_PAYMENT_TERMS LACLS_CR_PAYMENT_TERMS LACLS_CR_PAYMENT_TERMS Setup
Manager
Lookup Codes
01 Yes Contado Contado
02 Yes Credito Credito
03 Yes Consignacion Consignacion
04 Yes Apartado Apartado
Arrendamiento con opción
Yes
05 de compra. Arrendamiento con opción de compra.
Yes Arrendamiento en función
06 financiera. Arrendamiento en función financiera.
21
Yes Otros (se debe indicar la Otros (se debe indicar la condición de la
99 condición de la venta). venta).
PAYMENT TERM FROM / TO: LACLS_CR_MH_PAYMENT_TERM

Lookup used as FROM/TO to identify the valid payment term according Ministerio de Hacienda (MH).
In the lookup code must be entered a valid Payment Term or a valid Transaction class.
- For Credit Memo add the TRX class in lookup code ('CM','ONACC')
- For invoices and debit memo add the payment term name
- TAG add a value available for MH

01 Contado
02 Credito
03 Consignacion
04 Apartado
05 Arrendamiento con opción de compra.
06 Arrendamiento en función financiera.
99 Otros (se debe indicar la condición de la venta).
*this value will be transfer to MH
Functional
LACLS_CR_MH_PAYMENT_TERM LACLS_CR_MH_PAYMENT_TERM LACLS_CR_MH_PAYMENT_TERM Setup
Manager
Lookup Codes
<Value
<Enter a Payment Valid for
Term Name or a Yes MH>
Transaction Class <Meaning for the information Exemplo:
Name> entered in the lookup code> 01, 02
22
E-INVOICE CONDICTION: LACLS_CR_EINVOICE_CONDITION
Determine the condition accord MH list.
Functional
LACLS_CR_EINVOICE_CONDITION LACLS_CR_EINVOICE_CONDITION LACLS_CR_EINVOICE_CONDITION Setup
Manager
Lookup Codes
1 Yes Normal Normal
2 Yes Contingencia Contingencia
3 Yes Sin internet Sin internet
UNIT OF MESURE: LACLS_CR_UOM_CODES

This lookup is used for conversion of UOM code registered in the ERP versus UOM code required by Ministerio de
Hacienda.
Functional Setup
LACLS_CR_UOM_CODES LACLS_CR_UOM_CODES LACLS_CR_UOM_CODES
Manager
Lookup Codes
<ERP UOM Code> Yes <ERP UOM Code> <MH Description> <MH UOM Code>
PRODUCT CODE: LACLS_CR_PRODUCT_CODE_MH

Determine possible product code sources accord MH.
In the XML it is possible send until 5 values to Product Code, but not all of them are mandatory. The lookup
LACLS_CR_PRODUCT_CODE_MH has all valid values and the source to get the information in the ERP. The valid
sources are: Inventory Item Code (in this case the Meaning must be filled with value “INV Item Code” or an Item
Cross Reference (in this case the Meaning must be filled with the Cross Reference Lookup Code).
Functional
LACLS_CR_PRODUCT_CODE_MH LACLS_CR_PRODUCT_CODE_MH LACLS_CR_PRODUCT_CODE_MH Setup
Manager
Lookup Codes
<Código de la Lookup Code
Yes del Cross Reference del
01 Item> Codigo del Producto del Vendedor
02 Item> Codigo del Producto del Comprador
03 Item> Codigo de Producto Asignado por la Industria
23
04 Yes INV Item Code Codigo de Uso Interno
99 Item> Otros
Example:
In the example below the Inventory Item Code will be identified in the XML by the code “04” value
“100SMCH1JET2ML” and the Cross Reference BARCODE value will be identified in the XML by the code “03” value
“123456789”.
DEFAULT CONTEXT: LACLS_DEFAULT_CONTEXT
This Lookup information is necessary to identify the Descriptive FlexField (DFF) context chosen by the
implementation project to segregate the Costa Rica information that need be store in DFFs.
It will be the context entered on this lookup that will be used to write DFFs for the solutions that
generate DFF automatically. For example: XML Canonical for Electronic Invoice.
For the DFFs already created using a different context value from the one entered on this lookup, the
solution will keep the original context during the process that update the DFFs.
Important:
24
Considering a specific Descriptive Flexfield, it is possible to have as many Contexts as desired, however,
in this situation, all LACLS_CR information need to be configured to be store in the same ATTRIBUTE
column, in all different Contexts created.
Descriptive Flexfield
LACLS_DEFAULT_CONTEXT LACLS_DEFAULT_CONTEXT Default
Functional Setup Manager
Lookup Codes
CR Yes Costa Rica Costa Rica
Our suggestion is use the Country name “Costa Rica” as context; however, it can be chosen any value
according project specification. In this case, the context chose must be entered on the fields “Meaning”
and “Description”. The fields “Lookup Code” must be entered as “CR” and the “Display Sequence” a
unique value.
STANDARD LOOKUPS
The information will be used to identify the customer and Supplier registration type.
Attention: Some of these Lookup Types may be being shared by other Costa Rica solutions. So before you create
them check if it already exists.
Warning:
If accessing ERP using English language use “Manage Standard Lookups” task to create/update
ZX_REGISTRATIONS_TYPE Lookup Type.
If accessing ERP using any other language different from English, use “Manage Tax Lookup Codes” task to
create/update ZX_REGISTRATIONS_TYPE Lookup Type.
The following new lookup types are required in E-Invoice process:
CUSTOMER DOC TYPE: ZX_REGISTRATIONS_TYPE

New lookup codes should be added to identify the Costa Rica customer registration types.
Common
Type to indicate if the party is
ZX_REGISTRATIONS_TYPE Party Registration Type
registered with the tax authority
Tax
Components
Lookup Codes
CR_CEDULA_FISICA Yes CR - Cedula Fisica CR - Cedula Fisica 01

CR_CEDULA_JURIDICA Yes CR - Cedula Juridica CR - Cedula Juridica 02
CR_DIMEX Yes CR - DIMEX CR - DIMEX 03
CR_NITE Yes CR - NITE CR - NITE 04
Note: The “Tag” field should be filled with the document code considered by the MH.
25
VALUE SETS
Some value sets will be required for the Descriptive Flexfield creation.
Attention: Some of these Value Sets may be being shared by other Costa Rica solutions. So before you create check
if it already exists.
To create a new value set execute the following steps:
1) Open the application and select the “Setup and Maintenance” task group.
2) Search and select the task “Manage Value Sets”.
3) Click on the “Create” button, insert a new value set fields and “Save”.
The following Value Sets are required:
DOCUMENT TYPE: LACLS_CR_DOCUMENT_TYPE
Value Set Code LACLS_CR_DOCUMENT_TYPE

Description LACLS_CR_DOCUMENT_TYPE
Module Functional Setup Manager
Validation Type Table
Value Data Type Character
FROM Clause FND_LOOKUP_VALUES_VL
Value Column Name LOOKUP_CODE

Description Column Name MEANING
ID Column Named LOOKUP_CODE
WHERE Clause LOOKUP_TYPE = 'LACLS_CR_DOCUMENT_TYPE'
AND TRUNC(SYSDATE) BETWEEN
TRUNC(NVL(START_DATE_ACTIVE,SYSDATE)) AND
TRUNC(NVL(END_DATE_ACTIVE,SYSDATE)) AND ENABLED_FLAG = 'Y'
Order By LOOKUP_CODE
REFERENCE DOCUMENT CODE: LACLS_CR_REF_CODE
Value Set Code LACLS_CR_REF_CODE

Description LACLS_CR_REF_CODE
WHERE Clause LOOKUP_TYPE = 'LACLS_CR_EFD_REF_CODE'
26
PAYMENT CONDITION: LACLS_CR_PAYMENT_CONDITION
Value Set Code LACLS_CR_PAYMENT_CONDITION

Description LACLS_CR_PAYMENT_CONDITION
WHERE Clause LOOKUP_TYPE = 'LACLS_CR_PAYMENT_CONDITION'
REFERENCE DOC TYPE: LACLS_CR_REF_DOC_TYPE
Value Set Code LACLS_CR_REF_DOC_TYPE

Description LACLS_CR_REF_DOC_TYPE


WHERE Clause LOOKUP_TYPE = 'LACLS_CR_REF_DOC_TYPE'
ESTABLISHMENT NUMBER: LACLS_CR_ESTABLISH_NUMBER
Value Set Code LACLS_CR_ESTABLISH_NUMBER

Description LACLS_CR_ESTABLISH_NUMBER


27
WHERE Clause LOOKUP_TYPE = 'LACLS_CR_ESTABLISH_NUMBER'
BILLING POINT: LACLS_CR_BILLING_POINT
Value Set Code LACLS_CR_BILLING_POINT

Description LACLS_CR_BILLING_POINT
WHERE Clause LOOKUP_TYPE = 'LACLS_CR_BILLING_POINT'
INCOTERM CODES: LACLS_CR_INCONTERMS
Value Set Code LACLS_CR_INCONTERMS

Description LACLS_CR_INCONTERMS
WHERE Clause LOOKUP_TYPE = 'LACLS_CR_INCONTERMS'
28
INVOICE STATUS: LACLS_CR_EFD_STATUS
Value Set Code LACLS_CR_EFD_STATUS

Description LACLS_CR_EFD_STATUS
WHERE Clause LOOKUP_TYPE = 'LACLS_CR_EFD_STATUS'
PAYMENT TERM: LACLS_CR_PAYMENT_TERMS
Value Set Code LACLS_CR_PAYMENT_TERMS

Description LACLS_CR_PAYMENT_TERMS


WHERE Clause LOOKUP_TYPE = 'LACLS_CR_PAYMENT_TERMS'
CABYS CODE: LACLS_CR_CABYS_CODE
Value Set Code LACLS_CR_CABYS_CODE

Description LACLS_CR_CABYS_CODE
FROM Clause egp_category_sets_vl ecs, egp_category_set_valid_cats ecsv ,
egp_categories_vl ecv
Value Column Name substr(ecv.CATEGORY_CODE,1,20)
Description Column Name ecv.CATEGORY_NAME
29
ID Column Named substr(ecv.CATEGORY_CODE,1,20)
WHERE Clause ecs.category_set_name like 'LACLS_CR_CABYS_CODE'

and ecsv.CATEGORY_SET_ID = ecs.CATEGORY_SET_ID
and ecv.CATEGORY_ID = ecsv.CATEGORY_ID
Order By ecv.CATEGORY_CODE
DUTY ITEM: LACLS_CR_DUTY_ITEM
Value Set Code LACLS_CR_DUTY_ITEM

Description LACLS_CR_DUTY_ITEM
FROM Clause egp_category_sets_vl ecs, egp_category_set_valid_cats ecsv ,
egp_categories_vl ecv
Value Column Name substr(ecv.CATEGORY_CODE,1,20)
Description Column Name ecv.CATEGORY_NAME
ID Column Named substr(ecv.CATEGORY_CODE,1,20)
WHERE Clause ecs.category_set_name like 'LACLS_CR_DUTY_ITEM'
and ecsv.CATEGORY_SET_ID = ecs.CATEGORY_SET_ID
and ecv.CATEGORY_ID = ecsv.CATEGORY_ID
Order By ecv.CATEGORY_CODE
EINVOICE CONDITION: LACLS_CR_EINVOICE_CONDITION
Value Set Code LACLS_CR_EINVOICE_CONDITION

Description LACLS_CR_EINVOICE_CONDITION


WHERE Clause LOOKUP_TYPE = ' LACLS_CR_EINVOICE_CONDITION'
30
DESCRIPTIVE FLEXFIELDS
Given the dynamic characteristic of some legal information the LACLS use the Descriptive Flexfield (DFF)
concepts to configure the tax authority requirements. One highlight point that needs to keep in mind is
that the flexfield name must define according to the LACLS guidelines.
IMPORTANT:
1) You must enter the Descriptive Flexfield Name exactly as requested since it is used to identify the
additional information.
2) Considering a specific Descriptive Flexfield, it is possible to have as many Contexts as desired,

however, in this situation, all LACLS_CR information need to be configured to be store in the
same ATTRIBUTE column, in all different Contexts created.
After Descriptive Flexfield has been created, save it and press button Deploy Flexfield.
RECEIVABLES TRANSACTION HEADER
Setting up the Receivables transaction Header DFF:
1. Go to “Setup and Maintenance” task.

2. Search and select the task “Manage Descriptive Flexfields”.
3. On the field “Flexfield Code” inform “RA_CUSTOMER_TRX” and press search button.
4. On Search Results area press “Edit” link.
5. Check if the context “Costa Rica” already exists in the “Context Sensitive Segments” area. If the context
“Costa Rica” does not exists yet, create a new context clicking on the “Manage Contexts” and “Create”
buttons. If the context “Costa Rica” already exists go to the next step. To create a new context fill the fields
as follow:
Display Name Costa Rica
Description Costa Rica
Context Code Costa Rica
API Name Maintain the name create by the application
Enabled Yes
6. Select the context “Costa Rica” in the “Context Sensitive Segments” area click on the “Create” button to
add new segments:
Flexfield Name Flexfield Code Description

Transactions RA_CUSTOMER_TRX Fields for additional information on the transaction page.
Context Code Costa Rica or use some According Project Team definition
SEGMENT 1 SEGMENT 2 SEGMENT 3

Sequence 10 20 30
Name LACLS_CR_EFD_DATE LACLS_CR_EFD_NUMBER LACLS_CR_EFD_STATUS
Code LACLS_CR_EFD_DATE LACLS_CR_EFD_NUMBER LACLS_CR_EFD_STATUS
Description Fecha de Recibo Clave Estado Electronic Invoice
API Name Maintain the suggested name Maintain the suggested name Maintain the suggested name
Enabled Yes Yes Yes
31
Data Type Character Character Character
Table Column Any Available Attribute column Any Available Attribute column Any Available Attribute column
Value Set GL_20_CHARACTERS GL_150_CHARACTERS LACLS_CR_EFD_STATUS
Required No No No
Prompt Fecha de Recibo Clave Estado Electronic Invoice
Display Type Text Box Text Box List of Values
Display Size 12 20 10
Read Only Yes Yes Yes
BI Enabled Yes Yes Yes

Sequence 40 50 60
Name LACLS_CR_EFD_MESSAGE LACLS_CR_PAYMENT_CONDITION LACLS_CR_REF_CODE
Code LACLS_CR_EFD_MESSAGE LACLS_CR_PAYMENT_CONDITION LACLS_CR_REF_CODE
Description Mensaje Condicion de pago Codigo Documento Referencia
Enabled Yes Yes Yes
Value Set GL_150_CHARACTERS LACLS_CR_PAYMENT_CONDITION LACLS_CR_REF_CODE
Required No No No
Prompt Mensaje Condicion de pago Codigo Documento Referencia
Display Type List of Values List of Values List of Values
Read Only No Yes Yes

Sequence 70 80 90
Name LACLS_CR_REF_DOC_TYPE LACLS_CR_INCONTERMS LACLS_CR_EINVOICE_CONDITION
Code LACLS_CR_REF_DOC_TYPE LACLS_CR_INCONTERMS LACLS_CR_EINVOICE_CONDITION
Description Tipo de Documento Referencia LACLS_CR_INCONTERMS LACLS_CR_EINVOICE_CONDITION
Enabled Yes Yes Yes
Value Set LACLS_CR_REF_DOC_TYPE LACLS_CR_INCONTERMS LACLS_CR_EINVOICE_CONDITION
Required No No No
Situación del comprobante
Prompt Tipo de Documento Referencia LACLS_CR_INCONTERMS
electrónico
Read Only No Yes Yes
RECEIVABLES TRANSACTION TYPE
Setting up the Receivables transaction type DFF:

32
3. On the field “Flexfield Code” inform “RA_CUST_TRX_TYPES” and press search button.
4. On Search Results area Press Edit icon.
as follow:
Enabled Yes
add new segments:

Transaction Types RA_CUST_TRX_TYPES Fields for additional information on the transaction type page.
Sequence 10 20 30
Name LACLS_CR_DOCUMENT_TYPE LACLS_CR_ELECTRONIC_INVOICE LACLS_CR_EFD_MAIL
Code LACLS_CR_DOCUMENT_TYPE LACLS_CR_ELECTRONIC_INVOICE LACLS_CR_EFD_MAIL
Description Tipo de Documento Electronic Invoice Correo Notificacion Errores
Enabled Yes Yes Yes
Value Set LACLS_CR_DOCUMENT_TYPE JE_YES_NO GL_100_CHARACTERS
Required No No No
Prompt Tipo de Documento Electronic Invoice Correo Notificacion Errores
Display Type List of Values List of Values Text Box
Read Only Yes Yes Yes

Sequence 40 50 60
Name LACLS_CR_REF_CODE LACLS_CR_PAYMENT_CONDITION LACLS_CR_REF_DOC_TYPE
Code LACLS_CR_REF_CODE LACLS_CR_PAYMENT_CONDITION LACLS_CR_REF_DOC_TYPE
Description Codigo Documento Referencia Condicion de pago Tipo de Documento Referencia
Enabled Yes Yes Yes
Value Set LACLS_CR_REF_CODE LACLS_CR_PAYMENT_CONDITION LACLS_CR_REF_DOC_TYPE
Required No No No
Prompt Codigo Documento Referencia Condicion de pago Tipo de Documento Referencia
Read Only Yes Yes No
SEGMENT 7 SEGMENT 8
33
Sequence 70 80
Name LACLS_CR_ESTABLISH_NUMBER LACLS_CR_BILLING_POINT
Code LACLS_CR_ESTABLISH_NUMBER LACLS_CR_BILLING_POINT
Description Numero Establecimiento Terminal o Punto de Emisión
API Name Maintain the suggested name Maintain the suggested name
Enabled Yes Yes
Data Type Character Character
Table Column Any Available Attribute column Any Available Attribute column
Value Set LACLS_CR_ESTABLISH_NUMBER LACLS_CR_BILLING_POINT
Required No No
Prompt Numero Establecimiento Terminal o Punto de Emisión
Display Type List of Values List of Values
Display Size 20 20
Read Only Yes Yes
BI Enabled Yes Yes
PARTY SITES
Setting up the Party Sites DFF:

3. On the field “Flexfield Code” inform “HZ_PARTY_SITES” and press search button.
5. Context Code
If a Party Site can be used in different Countries, it is not possible create the DFFs under a “Costa Rica”
Context since one country can subscribe the DFFs from other country.
Please verify the best approach according customer characteristics to decide if the DFF Context DFF can be
used or not.
6. After have decided for create Context or not, create the segments as follow:
HZ_PARTY_SITES HZ_PARTY_SITES Fields for party site details
Context Code Use or Not According Project Team definition
SEGMENT 1 SEGMENT 2
Sequence 10 20
Name LACLS_CR_ECONOMIC_ACTIVITY LACLS_CR_INCONTERMS
Code LACLS_CR_ECONOMIC_ACTIVITY LACLS_CR_INCONTERMS
Description Actividad Economica Codigo Incoterm
Enabled Yes Yes
Value Set GL_20_CHARACTERS LACLS_CR_INCONTERMS
Required No No
Prompt Actividad Economica Codigo Incoterm
Display Type Text List of Values
Display Size 10 20
Read Only Yes Yes
BI Enabled Yes Yes
34
NOTE: The economic activities must loaded writing the activity code delivery by INEC.
Example: 4721
For review all economic activities please go to INEC ‘INSTITUTO NACIONAL DE ESTADÍSTICA Y CENSOS’ web site
https://www.inec.cr/documento/inec-2011-clasificacion-de-actividades-economicas-de-costa-rica-manual-de-
rama-de
*always confirm review the website because INEC can be updated the list or update the link
LOCATIONS
Setting up Locations DFF:
1. Go to Setup and Maintenance

2. Search and select the task Manage Descriptive Flexfields
3. On the field Flexfield Code inform HZ_LOCATIONS and press search button
4. On Search Results area Press Edit icon
5. Context Code
If a Location can be used in different Countries, it is not possible create the DFFs under a “Costa Rica”
used or not.

Location HZ_LOCATIONS Fields for party site details
SEGMENT 1 SEGMENT 2
Sequence 10 20
Name LACLS_CR_PHONE_NUMBER LACLS_CR_ISSUER_EXP_CODE
Code LACLS_CR_PHONE_NUMBER LACLS_CR_ISSUER_EXP_CODE
Description Número Teléfono Codigo Exportador
Enabled Yes Yes
Value Set GL_20_CHARACTERS GL_20_CHARACTERS
Required No No
Prompt Número Teléfono Codigo Exportador
Display Type Text Box Text Box
Display Size 20 20
Read Only Yes Yes
BI Enabled Yes Yes
MEMO LINE
Setting up the Memo Lines DFF:
35
3. On the field “Flexfield Code” inform “c” and press search button.
5. Context Code
If a Memo Line can be used in different Countries, it is not possible create the DFFs under a “Costa Rica”
used or not.
Memo Lines AR_MEMO_LINES Fields for memo line details on the memo line age.
SEGMENT 1 SEGMENT 2
Sequence 10 20
Name LACLS_CR_CABYS_CODE LACLS_CR_DUTY_ITEM
Code LACLS_CR_CABYS_CODE LACLS_CR_DUTY_ITEM
Description Categoria Cabys Partida Arancelaria
Enabled Yes Yes
Value Set LACLS_CR_CABYS_CODE LACLS_CR_DUTY_ITEM
Required No No
Prompt Categoria Cabys Partida Arancelaria
Display Size 20 20
Read Only Yes Yes
BI Enabled Yes Yes
INVOICE LINE
Setting up the Invoice Lines DFF:

3. On the field “Flexfield Code” inform “RA_CUSTOMER_TRX_LINES” and press search button.
as follow:
36
Enabled Yes
add new segments:
Invoice Lines RA_CUSTOMER_TRX_LINES

Fields for invoice line details on the invoice line page.
SEGMENT 1 SEGMENT 2
Sequence 10 20
Name LACLS_CR_CABYS_CODE LACLS_CR_DUTY_ITEM
Code LACLS_CR_CABYS_CODE LACLS_CR_DUTY_ITEM
Description Categoria Cabys Partida Arancelaria
Enabled Yes Yes
Value Set LACLS_CR_CABYS_CODE LACLS_CR_DUTY_ITEM
Required No No
Prompt Categoria Cabys Partida Arancelaria
Display Size
Read Only No No
BI Enabled No No
FND LOOKUPS – PAYMENT TERM
In this topic will be treated a flexfield define at FND Lookups level. Information setup in this flexfield will
be used to store the Payment Term valid according MH values.
Setting up the FND Lookup DFF:

3. On the field “Flexfield Code” inform “FND_LOOKUP_VALUES_B” and press search button.
5. Click on Manage Contexts button

7. Create the Context as follow::
Display Name LACLS_CR_MH_PAYMENT_TERM
Description LACLS_CR_MH_PAYMENT_TERM
Context Code LACLS_CR_MH_PAYMENT_TERM
Enabled Yes
8. Save
37
9. After Context Code has been created, start creating the flexfields under FND_LOOKUPS_VALUES_B.
10. Select the context “LACLS_CR_MH_PAYMENT_TERM” in the “Context Sensitive Segments” area click on the
“Create” button to add new segments:
Lookup values
descriptive FND_LOOKUP_VALUES_B Fields for lookup information.
flexfield
Context LACLS_CR_MH_PAYMENT_TERM
SEGMENT 1
Sequence 10
Name LACLS_CR_MH_PAYMENT_TERM
Code LACLS_CR_MH_PAYMENT_TERM
Description Termino de Pago MH
API Name Maintain the suggested name
Enabled Yes
Data Type Character
Table Column ATTRIBUTE1
Value Set LACLS_CR_PAYMENT_TERMS
Required No
Prompt Termino de Pago MH
Display Type List of Values
Display Size
Read Only No
BI Enabled No
ITEM TYPE – INVENTORY CATALOG
In order to identify the Inventory Item Type, Cabys and duty is necessary indicating item type catalogs. LACLS for
Costa Rica will use the Catalog functionality.

1. Navigate to home page
2. Click on Product Management
3. Choose Product Information Management
4. On the right side, in the Task list, choose the option Manage Catalogs
5. The Manage Catalogs page will be displayed. Click on Create button
6. Create the Catalog according to the company´s standard definition. We suggest a name that represents
clearly what the Catalog intends. However, the Category Code must be LACLS_CR_CABYS_CODE and
LACLS_CR_DUTY_ITEM.
Creating Catalog:
Catalog Name LACLS_CR_CABYS_CODE LACLS_CR_DUTY_ITEM

Catalog Code LACLS_CR_CABYS_CODE LACLS_CR_DUTY_ITEM
Description LACLS_CR_CABYS_CODE LACLS_CR_DUTY_ITEM
Controlled At Master Level Master Level
Default Caetegoty
38
Start Date 1/1/01 1/1/01
End Date
Assign items to leaf level
Y Y
categories only
Allow multiple item category
Y Y
assignments
Public Y Y
7. After Catalog has been created, click on Create Category
8. Create Categories as the follow:
Example:
Catalog Name LACLS_CR_CABYS_CODE LACLS_CR_DUTY_ITEM

Barquillos y obleas, incluso Barquillos y obleas,
Category Name rellenos incluso rellenos
Category Code 2342000000300 2342000000300

Barquillos y obleas, incluso Barquillos y obleas,
Description rellenos incluso rellenos
Start Date 1/1/01 1/1/01

End Date
Restrict Category to Item
Y Y
Assignment Only
GEOGRAPHY LOOKUP
Costa Rica requirements may require some kind of information not available in the ERP UIs. Thinking of
it, Oracle created the Manage Geography Lookups solution, which allows to treat specifics requirements
and use them to control anything you need.
GEOGRAPHY CODE: LACLS_CR_GEOGRAPHY_CODES
This additional information identify according MH list.
Creating the Geographical Lookup Code:
1. Go to Setup and Maintenance.

2. Go to Compensation Management Offering.
3. Select Enterprise profile functional area.
4. Click on the Manage Geography Lookups link.
5. Click on the HZ_GEO_IDENTIFIER_SUBTYPE link.
6. In the search results area press create icon.
7. Create the Lookup Code entering each bit of information as follow:
Lookup Code
Lookup Code LACLS_CR_GEOGRAPHY_CODES
Enabled Yes
Meaning Costa Rica Codigo MH
39
Description Costa Rica Codigo MH
Tag C
Important: Check MH list to create the Lookup Codes and Meaning.
Assign the information to Province, Canton, District and Neighborhood:

2. Search for Manage Geographies
3. Click on Manage Geographies link
4. Search country name Costa Rica
5. Click on Hierarchy Defined
6. Select the Province, Canton, District and Neighborhood and edit
7. Go to Primary and Alternative Codes and add the code type
Repeat these actions for all Province, Canton, District and Neighborhood required.
Example:
40
ENTERING LACLS ADDITIONAL INFORMATION
After create the application components required by the “XML Canonical for Electronic Invoice” solution (DFFs,
value sets, lookup types and tax reporting types) is necessary to assign those components to the taxes, transactions,
invoices, customers and suppliers, at the end, assign value to each level where additional information will be stored.
This activities should be performed by the Oracle ERP users.
DESCRIPTIVE FLEXFIELDS
RECEIVABLES TRANSACTION
Descriptive flexfields were created on the header of the Receivables Transaction to be used to generate and control
Electronic Invoice process.
 Clave Autorización
This DFF will be filled automatically when the transaction is retrieved by third party.
 Fecha Autorización
This DFF will be filled automatically when the transaction is retrieved by third party. The format
accepted is something like this: 2020-10-16 15:05:34.
 Status
This DFF storages the process status having the following valid values:
 Null – Indicates that it is a new transaction; that has not been captured by the EFD
Electronic Invoice process yet.
 SENT - Indicates that the transaction has been sent to third party.
 PROCESSING – Indicates that the transaction is under processing by third party.
 ERROR - Indicates that the transaction has been rejected by MH. In this case the “EFD
Message” will be filled with the error explanation (just the first 150 characters).
 FIXED – Status created just to indicate that the transaction has already been setup with
ERROR status, however was changed and may be sent once again.
 APPROVED WITH WARNING - Indicates that the electronic fiscal document has been
approved by MH with warnings.
 APPROVED - Indicates that the electronic fiscal document has been approved by MH. In
this case the Clave Autorización has been filled with a valid UUID.
 REJECTED - Indicates that the transaction was cancelled and should be discarded by the
EFD Electronic Invoice process.
This DFF will be filled auto automatically when the electronic fiscal document be approved by MH.
 Mensaje CFE
This DFF must be filled with the error message, in cases the EFD be rejected by MH, or with other
relevant message. This DFF will be filled automatically when the transaction is retrieved by third party.
 Condicion de Pago
This descriptive flexfield must be informed for Transactions and indicate the payment condition.
41
 Codigo Documento Referencia
This descriptive flexfield must be informed for Credit Memo Transactions.
 Tipo Documento Referencia
 Incoterms
Enter the Incoterms code according to defined in Exportation transaction.

 Situación del comprobante electrónico
Enter the Einvoice condition code.
RECEIVABLES TRANSAC TION TYPE
Each Receivables Transaction Type should have registered in the additional information fields if it will be considered
or not as an electronic invoice to be sent to MH.
To register the additional information:

2. Select the Setup: Financials group and Customer Billing functional area
3. Select the task Manage Transaction Types task. The Scope must be assigned to the task previously
4. Search and edit the desired Transaction Type
5. Select the context desired, according to Project Team definition and fill the fields:
 Tipo de Documento
Indicates the Transaction Type according to MH definition.
 Electronic Invoice
Indicates transaction that must be considered an electronic fiscal document. It means that
transaction assigned with Yes in this flexfields will be eligible to be retrieved in the BI
Extractor.
 Condicion de Pago
This descriptive flexfield must be informed for Transactions and indicate the payment condition.
 Codigo Documento Referencia
 Tipo Documento Referencia
42
 Correo Notificacion Errores
This descriptive flexfield must be informed for send an email with MH errors. This must delivered by
third party.
 Numero Establecimiento
This descriptive flexfield must be informed for indicate the invoice establishment number.
 Punto de Emision
This descriptive flexfield must be informed for indicate the invoice billing point.
LOCATIONS
This flexfield must be configured to provide Legal Entity information related to Exportation transactions.

2. Select the Setup: Financials group and Legal Structures functional area
3. In the Legal Structures area, choose task Manage Legal Entity. The Scope must be assigned to Legal Entity
desired.
4. In Legal Entity Addresses area, click on Edit icon and choose “Edit address” option
5. In Edit Address page, enter with Costa Rica flexfields information:
 Numero de Telefono
It indicates the legal entity phone number.
 Codigo Exportador
It indicates the Code assigned by MH to Legal Entity, allowing the company acts as a Exporter.
PARTY SITES
Descriptive Flexfields defined at Customer Sites level.

2. Search for Manage Customers
3. Search for a Customer and go to Customer Site area
4. Access the Site desired and enter the flexfields information:
 Incoterms
It allows company to indicate the Incoterms Code linked to the Customer.
 Codigo Actividad Economica
43
This information will be used for indicate the economic activity.
MEMO LINES
It allows indicate the Item Type at Memo Line level.

2. Search for Manage Standard Memo Lines
3. Search for a Memo Line desired
4. Enter with value:
 Categoria CABYS
It indicates if the Memo Line represents a specific CABYS.

 Partidad Arancelaria
It indicates if the Memo Line represents a specify duty, use only for export.
RECEIVABLES TRANSACTION LINES
It allows indicate the Item Type at Receivables Transaction Lines level.

1. Go to Home page
2. Navigate to Receivables option
3. In the Transaction created, at Lines level, click on Details icon
4. In the Additional Information area, enter with flexfield data:
 Categoria CABYS
It indicates if the Line represents a specific CABYS.

 Partidad Arancelaria
It indicates if the Line represents a specify duty, use only for export.
NOTE: The References Line Discount ‘Linea Referencia del Descuento’ will selected accord lines with same
description, same inventory item and different sign amount:
Invoice STANDAR/ DEBIT line with negative amount and CREDIT lines with positive amount.
44
TAX REPORTING TYPES
VAT CODES: LACLS_CR_VAT_CODE
This tax reporting type will identify the tax code, please follow the steps:
1. Go to Setup and Maintenance task group

2. Search for task Manage Tax Rates
3. Choose the Rate desired
4. In the Tax Rate page, click on Edit button
5. Navigate to Tax Reporting Type Code folder
6. Click on Add Row icon. Then, enter with Tax Reporting information
Tax Reporting Types Required:
LACLS_CR_VAT_CODE – It identifies the vat code.
RATE CODE: LACLS_CR_RATE_CODE
This tax reporting type must be assigned to Tax Rate in order to classified the Rate Code is being setup:

3. Choose the Tax Rate desired
4. In the Tax page, click on Edit button
LACLS_CR_RATE_CODE – It identifies the Tax Rate Code.
PRODUCT TYPE: LACLS_CR_PRODUCT_TYPE
This tax reporting type must be assigned to Tax Rate in order to identify the Product Type.

3. Choose the Tax Rate desired
45
LACLS_CR_PRODUCT_TYPE – It identifies the Product Type.
ENVIRONMENT TYPE: LACLS_CR_EFD_ENVIRONMENT
This tax reporting type must be assigned to legal entity in order to classify the environment:

2. Search for task Legal Structures Manage Tax Rates
3. Task Manage Legal Entity Tax Profiles
4. Choose the legal entity desired
LACLS_CR_EFD_ENVIRONMENT – It identifies the environment.
ITEM INFORMATION – INVENTORY CATALOG
In order to identify the Inventory CABYS and Duty codes, will be necessary to link Catalogs LACLS_CR_CABYS_CODE
and LACLS_CR_DUTY_ITEM with Inventory Items Catalog setup.
1. So, please navigate to Manage Items task

2. Choose Item desired and then navigate to Categories folder
3. Enter Catalog information:
46
47
MONITORING PROCESS
It is possible monitoring the Receivables transactions handled by the “XML Canonical for Electronic Invoice”
solution. The monitoring can be done individually through transaction descriptive flexfields or through the Panel
tool.
To monitoring the Receivables transactions individually:
1. Go to Receivables > Billing.
2. Search and edit the desired transaction.
3. The EFD descriptive flexfields can be viewed under Miscellaneous area
The monitoring of the cycle of creation, sending and return of electronic vouchers can be done through report Panel
E-INVOICE.
1. Open the Oracle ERP Cloud application and select the Reports and Analytics task of Tools group
2. Expand the directory where the panel is available (All Folders/Shared Folders/Custom/Local Solution/CR/E-
INVOICE)
3. Click on the object “Panel E-INVOICE.xdoz”
4. Inform the parameters and click on the “Apply” button:
PARAMETERS
Entidad Legal: Legal Entity name

Dias: Quantity of days to be considered in the query
OUTPUT
When the process finishes successfully an output file is generated containing information about the
Receivables transactions involved in the XML Canonical for Electronic Invoice process.
The first part of the output file shows a chart with the total of the Receivables transactions retrieved
grouped by the electronic voucher status.
The second part of the output file shows a table containing details of the Receivables transactions.
This output can be exported to the formats PDF, HTML, RTF, Excel or PowerPoint.
48
THIRD PARTY INTEGRATION USER AND ROLES
It is mandatory to have a user in Oracle ERP Cloud to allow third party execute:
 WS responsible to execute the BI Publisher;

 WS responsible to update the DFFs.
We recommend be created a specific user to be used as “ERP Third Party Integration User” instead of use
a regular natural person user.
Following the recommendation for Roles:
Job Roles
 Financial Integration Specialist

 Integration Specialist
 BI Consumer Role
 Rest API Extract Privilege
After assign the roles to the third party Integration User, execute the following processes:
 Import User and Role Application Security Data

 Retrieve Latest LDAP Changes
49
Copyright © 2022, 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.
50

Guide Lacls Costa Rica Ufig XML Canonical Efactura

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Guide Lacls Costa Rica Ufig XML Canonical Efactura

Uploaded by

Copyright:

Available Formats

Oracle Financials Cloud

Latin America Cloud Local Solution

XML Canonical for Electronic

REVISION HISTORY ......................................................................................................................................................... 4

PREPARING TO INSTALL/UPDATE ...........................................................................................................................8

GETING THE LATEST VERSION ........................................................................................................................................... 8

INSTALLATION/UPDATE TASKS ..............................................................................................................................9

CREATE BI FOLDERS STRUCTURE – INSTALL / UPDATE........................................................................................................... 9

CONFIGURATION TASK ........................................................................................................................................ 15

TAX REPORTING TYPES ................................................................................................................................................. 15

ENTERING LACLS ADDITIONAL INFORMATION ..................................................................................................... 41

DESCRIPTIVE FLEXFIELDS ............................................................................................................................................... 41

MONITORING PROCESS ....................................................................................................................................... 48

THIRD PARTY INTEGRATION USER AND ROLES ..................................................................................................... 49

Data Version Description Delivery by Included in

19-Nov-2020 1 Document creation

In this manual you will find:

This guide assumes you have a working knowledge of the following:

• The principles and practices of your business area;

CONCATENATE SPECIAL INFORMATION

The solution will be show concatenate special information:

GETING THE LATEST VERSION

CREATING PACK STAGE AREA

CREATE BI FOLDERS ST RUCTURE – INSTALL / UPDATE

BI FOLDERS STRUCTURE REQUIRED

 CR folders structure required for LACLS Reports:

/Custom/Local Solution/CR/E-INVOICE/Data Models

/Custom/Local Solution/CR/E-INVOICE/Process/Data Models

7. Under the structure /Shared Folders/Custom/Local Solution, create the folder CR

9. Under CR folder, create new folder called E-INVOICE

11. Under the structure /Shared Folders/Custom/Local Solution/CR/E-INVOICE, create a new

15. Under the structure /Shared Folders/Custom/Local Solution/CR/E-INVOICE/Process, create a

The following page will be displayed:

8. Go to /Shared Folders/Custom/Local Solution/CR/E-INVOICE/Process folder and click on

11. Go to /Shared Folders/Custom/Local Solution/CR/E-INVOICE/Process/Data Models folder and

TAX REPORTING TYPES

To create Tax Reporting Types follow the next steps:

1. Go to “Setup and Maintenance” tasks.

MH VAT CODES: LACLS_CR_VAT_CODE

Tax Reporting Code Description

Tax Reporting Code Description

PRODUCT TYPE: LACLS_CR_PRODUCT_TYPE

Tax Reporting Code Description

This tax reporting type will identify the environment.

Tax Reporting Code Description

To create new common lookup types execute the following steps:

DOCUMENT TYPE: LACLS_CR_DOCUMENT_TYPE

Lookup Type Meaning Description Module

LACLS_CR_DOCUMENT_TYPE LACLS_CR_DOCUMENT_TYPE E-Invoice Type Functional Setup Manager

Lookup Type Meaning Description Module

PAYMENT CONDITION: LACLS_CR_PAYMENT_CONDITION

Lookup Type Meaning Description Module

REFERENCE DOC TYPE: LACLS_CR_REF_DOC_TYPE

Lookup Type Meaning Description Module

ESTABLISHMENT NUMBER: LACLS_CR_ESTABLISH_NUMBER

Lookup Type Meaning Description Module

BILLING POINT: LACLS_CR_BILLING_POINT

Lookup Type Meaning Description Module

INCONTERM CODES: LACLS_CR_INCONTERMS

Lookup Type Meaning Description Module

INVOICE STATUS: LACLS_CR_EFD_STATUS

Lookup Type Meaning Description Module

PAYMENT TERM: LACLS_CR_PAYMENT_TERMS