Oracle Financials Cloud

Latin America Cloud Local Solution

Chile – Payables XML Loader
Functional Implementation Guide

Version 2

26 Oct 2023

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.
TABLE OF CONTENTS
TABLE OF CONTENTS ..............................................................................................................................................2

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

LATIN AMERICA CLOUD LOCAL SOLUTION FOR CHILE ............................................................................................5

AUTOMATION TO CREATE PAYABLES INVOICES – OVERVIEW ............................................................................................5

AUTOMATION TO CREATE PAYABLES INVOICES - FLOW....................................................................................................7
Macro Flow .......................................................................................................................................................... 7
Detailed Flow – ERP Tasks .................................................................................................................................... 7
AUTOMATION TO CREATE PAYABLES INVOICES - VALIDATION RULES .................................................................................9
Validation “DTE” XML File .................................................................................................................................... 9
Control Data Access ............................................................................................................................................. 9
Document Type and Purchase Orders ................................................................................................................ 10
Legal Entity and Business Unit - Extractor.......................................................................................................... 10
Suppliers and Purchase Orders - Extractor ......................................................................................................... 10
Legal Entity ......................................................................................................................................................... 10
Suppliers ............................................................................................................................................................. 11
Purchase Orders ................................................................................................................................................. 11
Purchase Orders – Line Number ......................................................................................................................... 11
Purchae Orders - Items ....................................................................................................................................... 12
Purchase Orders - Schedules .............................................................................................................................. 13
Receipt Number .................................................................................................................................................. 13
Taxes – Documents based on Purchase Order ................................................................................................... 14
Taxes – Documents Without Purchase Order ..................................................................................................... 14
Payables Invoice Number ................................................................................................................................... 15
XML File Version ................................................................................................................................................. 16
Currency Code .................................................................................................................................................... 16
Control Statuses ................................................................................................................................................. 17
PRODUCT REQUIREMENTS ASSOCIATE TO LACLS SCOPE ............................................................................................... 18
INTENDED AUDIENCE............................................................................................................................................. 18
APPLICATIONS TECHNOLOGY ................................................................................................................................... 18
ASSUMPTIONS ..................................................................................................................................................... 19

PREPARING TO INSTALL/UPDATE ......................................................................................................................... 20

CONFIGURATION TASKS ....................................................................................................................................... 21

DISTRIBUTION SET ................................................................................................................................................ 21

PAYABLES SOURCE ................................................................................................................................................ 21
INVOICE HOLDS .................................................................................................................................................... 22
MANAGE TRADING PARTNER ITEMS ......................................................................................................................... 23
LOOKUP ............................................................................................................................................................. 24
Default Context: LACLS_DEFAULT_CONTEXT ..................................................................................................... 24
Setup Solution - LACLS_CL_LXML_SETUP ........................................................................................................... 25
Document Types - LACLS_CL_LXML_DOC_TYPES ............................................................................................... 26
VALUE SET .......................................................................................................................................................... 27

LACLS – CL – Payables XML Loader - Functional Implementation Guide 2

 Payables Invoice Numer ..................................................................................................................................... 27
DESCRIPTIVE FLEXFIELD .......................................................................................................................................... 29
Document Types and Invoice Number ................................................................................................................ 29
TAX REPORTING TYPE CODE.................................................................................................................................... 31
Tax Type - LACLS_CL_TAX_TYPE ......................................................................................................................... 31
ROLE FOR AUTOMATION TO CREATE PAYABLES INVOICES .............................................................................................. 32
LACLS CL Loader XML for Payables - Super User ................................................................................................ 33
LACLS CL Loader XML for Payables - User .......................................................................................................... 33
LACLS CL Loader XML for Payables - iSupplier .................................................................................................... 34
Manage Data Access for User ............................................................................................................................ 34
ENTERING INFORMATION ....................................................................................................................................... 35
Tax Type ............................................................................................................................................................. 35
Document Types and Invoice Number ................................................................................................................ 35

CREATING AUTOMATION TO CREATE PAYABLES INVOICES MENU ITEM .............................................................. 37

CREATE THE MENU ITEM (ICON) .............................................................................................................................. 37

SOLUTION USER INTERFACES ............................................................................................................................... 42

Dashboard – Panel de Controle .......................................................................................................................... 42

Management Derivation – Mantenimiento ....................................................................................................... 43

LACLS – CL – Payables XML Loader - Functional Implementation Guide 3

REVISION HISTORY

This document will continue to evolve as existing sections change and new information is added. All
updates are logged below:

Date Version Changes Description Delivery by Included

Standalone in
Patchset
03-Aug-2023 1 Document Creation 34820850 23.3.0
26-Oct-2023 2 Treating Receiving transactions 35697881 24.1.0

LACLS – CL – Payables XML Loader - Functional Implementation Guide 4

LATIN AMERICA CLOUD LOCAL SOLUTION FOR CHILE

Latin America Cloud Local Solution (LACLS) for Chile is a set of components which complements the core
functionalities providing predefined processes and reports that are used to meet legal requirements
requested by government agencies.

LACLS solution to automate Payables invoices creation – Payables XML Loader will treat XML File that
were previously approved by Chilean Government and are available to be processed at Oracle UCM
directory.

AUTOMATION TO CREATE PAYABLES INVOICES – OVERVIEW

The solution is responsible for creating Payables Invoices based on XML files known by “Documentos
Tributarios Electrónicos-DTE”, that have been approved by Chilean government agency called “Servicio de
Impuestos Internos-SII”.

This Solution considers commercial transactions accomplished between companies and their suppliers
using Oracle Purchase Orders. This is very important once internal process in the Solution uses purchase
order to find Oracle source information.

Then, in a usual commercial cycle, after supporting companies demands based on purchase order,
supplier will issue the “DTE” complying with government laws. These files must be sent to company and,
at the end, these files must be available on Oracle Universal Content Management (UCM).

LACLS solution to automate Payables invoices creation – Payables XML Loader solution will be started by
an automated flow scheduled. This flow is responsible for reading the UCM directory, which has the “DTE”
XML files to be processed. Each file retrieved from UCM directory will be checked to validate if it is a XML
file that must be processed. All files recovered will be logged by Solution. It will provide to users a view
about what is being processed and its statuses.

Solution will validate if file really is an “XML” by checking if its structure fits under “SII” definition. Files
considered as “XML” will be gotten and its information will be read and sent to PaaS database, storing,
not only information but also the file, in the solution tables.

Once information from “DTE” XML files are stored in the database layer, database process will be
responsible for filtering suppliers and legal entities in order to use them for extracting data from SaaS. It
means that each cicly of processing, Solution will find in SaaS information about company configuration
and, for suppliers, will be extracted their information and its purchase orders in status “Open”. For
supporting process that use schedules lines based on match option “Receipts”, Solution also gets
information from Receiving Transactions linked with these purchase orders.

Information extracted from SaaS will be also stored in PaaS database in order to be used in a processes
called Derivation. The Derivation process consists in find SaaS information that corresponds to “DTE” XML

LACLS – CL – Payables XML Loader - Functional Implementation Guide 5

files information. For example, while creating invoice in Payables, the supplier site name is required,
however, this information is not available in “DTE”. Then, the derivation process is responsible for getting
data from “DTE” and, based on it, find the site name corresponds to from SaaS.

While running and applying derivation over data, Solution also applies validation in order to be sure that
information on these files are eligible to be used for generating a new Payables Invoice. Validations
applied will be describe in the section “Automation to Create Payables Invoices – Validation Rules”,
however, there are important points that must be highlighted:

 Legal Entity Identifier must match with information provided in the tag “RUTRecep”;

 Supplier Registration Number must match with information provided in the tag “RUTEmisor”;

 The solution works based on the match of the XML Invoice with the Purchase Orders.

Information that does not match with validation applied by LACLS solution to automate Payables invoices
creation – Payables XML Loader will be logged, providing to user the option to analyze the messages and
then take appropriated action over the “DTE” XML files.

After Payables invoice be created, the Solution will close the status for processing the “DTE” XML file
document by updating the status as “FINISHED”.

Important:

 The Payables XML Loader reads “DTE” XML file document and, based on that, creates an invoice
in Oracle Payables. Companies that are adopting this new solution, must review its process,
avoiding invoice be created manually by the users or even by the Suppliers throght the iSupplier
Portal.

 Solution handles ONLY domestic purchases in Chilean pesos (CLP), as Chilean legislation demands
the issuance of invoice in CLP.

 LACLS solution to automate Payables invoices creation – Payables XML Loader was created based
on SII layout version “1.0”. So, only “DTE” XML files in this version will be processed. Solution
reads file based on the structure defined in this version.

 When the invoice is created in Payables the XML file will be send as Attachment at Invoice header
level.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 6

AUTOMATION TO CREATE PAYABLES INVOICES - FLOW

MACRO FLOW

FUNCIONALITY AND TECHNOLOGIES

 Payables
 BI Tools
 OIC Flows
 PaaS Oracle Database
 OIC VBCS

DETAILED FLOW – ERP Tasks

These tasks refer to a set of steps required in SaaS by LACLS solution to automate Payables invoices
creation – Payables XML Loader SaaS:
 Taxes
o Set taxes information using the LACLS Tax Reporting Code “LACLS_CL_TAX_TYPE” to
indicate type of tax and its codes.
 Lookups
o Lookups used by solution to support a more flexible approaches.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 7

1. Read UCM;
• Process scheduled to check UCM directory and get XML files;
• Process will get information from tags and send it to be stored in PaaS database;
• “DTE” XML files documents will also be sent to be stored in PaaS database;
• Files handle successfully will be moved to Success UCM directory;
• Those handle with error will be moved to Error UCM directory;
• All “DTE” XML files processed will be registered in PaaS database tables in order user
can see and analyze its status.
2. Extraction SaaS Infos
• Information have been gotten by flows and stored in PaaS database will be used as
parameters while running BI Extractors. For example Legal Entity Identifier and
Supplier Taxpayer Id;
• Process responsible for run BI Extractors and retrieve information from SaaS.
Information extracted will be sent to PaaS database. These will be used in Derivation
Process;
3. Derivation
• All information extract from XML files will be matched with information extracted
from SaaS;
• This step uses information from “DTE” XML files to find SaaS information , those
required to create invoices in Payables;
• Data such as item, purchase order number (which is demanded for Solution),
business unit, supplier site and others.
4. [Link] Invoices
• Those were possible to run the match between “DTE” XML files and SaaS
information, resulting in every data needed to create invoice in Payables, then a rest
service will be called and invoice will be created;
• For those information required have not been found yet, “DTE” XML file will be
available in Solution´s UI allowing user to access them and take appropriate action.
5. UIs
• When a file is read from UCM directory, this file is registered in PaaS database tables.
It allows user see and following flow of processing file. This functionality is available
using Dashboard UI “Panel de Control”;
• Through “Panel de Control” user also can access the UI in which matches that were
not done automatically processed by Solution. This UI is known as Manage Derivation
“Mantenimiento” UI.
• In the “Mantenimiento” UI, user can choose the Purchase linked to the “DTE” XML
file and from this maintenance solution can process and find every information
required to create invoice in Payables.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 8

AUTOMATION TO CREATE PAYABLES INVOICES -
VALIDATION RULES

The main requirement for LACLS solution to automate Payables invoices creation – Payables XML
Loader is to create a Payables Invoice based on “DTE” XML file. While solution processing information
there are some validations applied, these validations start since from reading files taken from UCM and
go until creating invoice in Payables.

VALIDATION “DTE” XML FILE

Just after file is read from UCM directory, solution validates if file is a “DTE” XML file. This validation is
done by checking if file captured fits in structure defined by “SII”. Files were not considered a valid
“DTE” XML will be moved to an “Error” folder. Those validated as a valid file, will be moved to a
“Processed” folder in UCM directory.

CONTROL DATA ACCESS

Control Data Access works based on the following type of accesses:
 User;
o Users classified by company as “User” must have assigned to their Oracle user the LACLS
role “LACLS CL Loader XML for Payables - User”;
o For those users assigned to this role, it is required that company configures the Data
Accesses control to indicate which business unit these users can access. It can be done
by standard task “Manage Data Access for Users”;
o Using this role users can access the UI Dashboard and see files just for those business
units assigned under the role “LACLS_CL_LXML_USER_JOB”.

 Super User;
o Users classified by company as “Super User” must have assigned to their Oracle user the
LACLS role “LACLS CL Loader XML for Payables - Super User”;
o Using this role users can access the UI Dashboard and see all files processed by Solution,
no matter the restriction applied over standard task Manage Data Access for Users.

 iSupplier User
o LACLS solution to automate Payables invoices creation – Payables XML Loader
considers that actions required to become an iSupplier User have been done properly.
o This type of user will access information that have been assigned previously in Oracle
Procurement, in Suppliers.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 9

DOCUMENT TYPE AND PURCHASE ORDERS
Solution treats the following “SII” document types. Documents types must be setup in the lookup
“LACLS_CL_LXML_DOC_TYPES”:
 33 - “Factura Electrónica”;
o Solution requires the Oracle Purchase Order information linked to the “DTE” XML file.
 34 - “Factura No Afecta o Exenta Electrónica” ;
o Solution requires the Oracle Purchase Order information linked to the “DTE” XML file.
 56 – “Nota de Débito Electrónica”;
o Solution will not create invoice in Oracle Payables based on Oracle Purchase Order, due
to the business flow characteristic.
 61 – “Nota de Crédito Electrónica”.
o Solution will not create invoice in Oracle Payables based on Oracle Purchase Order, due
to the business flow characteristic.

LEGAL ENTITY AND BUSINESS UNIT - EXTRACTOR

This solution requires from company a standard functionality called “Manage Associated Business
Entities” be setup in order to create an explicity relationship between Legal Entities and their Business
Units.
As known, taxpayer id is created at Legal Entity level, althought the access in Oracle SaaS is run at
business unit level, Solution will use the association functionality to filter and achive which business
units supposed to be supported by “DTE” XML file is being processed.

SUPPLIERS AND PURCHASE ORDERS - EXTRACTOR

Solution takes information were extracted from “DTE” XML file and uses it as parameters while running
BI Extractors. It means that while running BI Extractor for Supplier, Solution uses as parameters the
taxpayer id that was available in tag “RUTEmisor”. Besides Supplier information, purchase orders that
belongs to this supplier are also gotten.

Important: Only purchase orders in status “Open” will be retrieved.

LEGAL ENTITY
After Legal Entity and Business Units information extracted and stored into PaaS database tables,
Solution uses these in order to validate if the “DTE” XML file is being processed belongs to the company.
This validation is done by using information available in tag “RUTRecep” and checking if this data must
matches with information setup as Legal Entity Identifier (for more details, see standard task Manage
Legal Entity).

LACLS – CL – Payables XML Loader - Functional Implementation Guide 10

For those cases that information does not match, the “DTE”processment will be assigned with status
“Error” and a proper message will be logged in order to provide to user a view about the validation
results.

SUPPLIERS
Once Supplier information are stored into PaaS database tables, Solution takes it to validate if “DTE”
XML file is being processed was sent by a Supplier that exists in the company´s environment system. For
doing it, Solution gets the information put in tag “RUTEmisor” and match it against Supplier Registration
Number.
Company also can validate it by going to Procurement offering, navigating to Suppliers and then search
a Supplier. In this Supplier setup, access Profile folder, navigate until Transaction Tax folder, and then
access Tax Registrations. Information in field Registration Number is the data which must match with
information gotten from tag “RUTEmisor”.

PURCHASE ORDERS
It is very important due Solution works only based on purchase orders. It is the source for most of
information required by Solution while is creating invoice in Payables. Thus, Solution gets information
available on “DTE” XML file, tag “FolioRef” and uses it as Oracle purchase order number.

PURCHASE ORDERS – LINE NUMBER

In order to automate every single step of processing information, Solution allows to inform the Purchase
Order Line Number thougth “DTE” XML file standard structure defined by “SII”. For that, Solution is
using the group information from XML called “CdgItem” to get the PO Line Number. For example, to
inform the PO Line Number the “DTE” XML file must be filled as the following:
<CdgItem>
<TpoCodigo>POLINE</TpoCodigo>  This info “POLINE” is configurable in lookup LACLS_CL_LXML_SETUP
<VlrCodigo>10</VlrCodigo>  Represent the Purchase Line Number
</CdgItem>

In a structure like this, Solution will get the PO Number informed in tag “FolioRef”. After that, Solution
will look for information available on tag “TpoCodigo”. If value contented at this tag is the same
configured in lookup “LACLS_CL_LXML_SETUP”, at lookup code " TAG_PO_LINE_NUM”, then Solution
takes value available on tag “VlrCodigo”, it will be considered as the purchase order line number
informed by Supplier.

Taking example above, let´s consider that value set in the lookup code is “POLINE”. Then Solution gets
the information available on tag “VlrCodigo” to find which purchase line number is being treating.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 11

This functionality brings more precision and effectiveness while looking for SaaS information to be used
in the Derivation process.

Important: Each lines of “DTE” XML file must has only one set of information for PO Line Number.

PURCHAE ORDERS - ITEMS

For “DTE” XML detail lines which has the PO Line Number informed, Solution get the purchase order line
information directly, identifying which purchase order line is being treated in the “DTE” XML file.

In the other side, for those scenarios that there are no PO Line Number available, Item figures as an
important information when it comes to derivation process once item is used as drive to find which
purchase order line is being treated in the “DTE” XML file. Solution uses information available in tag
“NmbItem” to find in Oracle an inventory item that corresponds to this data. Then, after getting the
Oracle inventory item, Solution takes the purchase order number, which has already been gotten, and
try to find the line in this purchase order that is referencing the Oracle inventory item found.

As known, information available in “DTE ” XML file represent the supplier information, however, for
creating invoice in Payables, Solution needs the SaaS information. Looking for flexibles way to handle
with this gap, Solution provides the following option to link the Supplier Items information with
Company Items information.

MANAGE TRADING PARTNER ITEMS

This standard functionality allows company creates a relationship between their items and supplier
items. Using this approach, Solution gets information retrieved from tag “NmbItem” and try to find the
supplier items configured under this functionality, getting the Oracle inventory item.

PURCHASE SUPPLIER ITEM

When Oracle user is creating a Purchase Order, there is a field called “Supplier Item” in the purchase
order line where can be informed the Supplier Item Code. Solution takes this information and matches it
against the information retrieved from tag “NmbItem” in order to find the Oracle inventory item.

ORACLE INVENTORY ITEM

Suppliers can inform in the tag “NmbItem” the company item code. It means, in this tag will be put the
Oracle Inventory Item, the same code present in the Oracle Purchase Order Line. Thus, Solution gets the
information available in the tag and try to match it against Oracle Purchase Order Lines, directly.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 12

PURCHASE ORDERS - SCHEDULES
When an invoice based on purchase order is created in Oracle Payables, it must be created at the lowest
level of purchase order, which means this invoice will be created at Schedules level.

This way, after finding purchase order and purchase order line, Solution must find the schedule available
to be consumed by Oracle Payables while invoice is entered. This schedule information will be used by
ERP to control the actions done over Purchase Order.

When Solution does not find a schedule that corresponds to the “DTE” XML file line a message will be
logged informing user in order a proper action can be taken. Besides that, there is a status assigned to
this document, warning user that document is available to be managed in order to create the relation
between “DTE” XML line and Oracle Purchase Order and its Schedule.

RECEIPT NUMBER
Oracle Purchase Order provides to companies the standard functionality retricting how Payables Invoice
can be created. The functionality Match Option defines if Schedule Line of Purchase Order Line will be
handle by “Order” or “Receipts”. Schedules lines with match option “Order” indicate that the Payables
Invoice can be created referencing one Purchase Order. The other option, the “Receipts” match option,
restrict the Payables Invoice creation by referencing one Receipts previously done.

LACLS CL Loader XML for Payables considers both type of match option. For lines that are based on
Schedules Lines that have “Order” as match option will be created in Payables referencing the Purchase
Order Line data.

For lines based on Schedules Line that have match option “Receipt”, Supplier can provide the Receipt
Number in the “DTE” XML file standard structure defined by “SII”. Solution is using the group
information from XML called “CdgItem” to get the Receipts Number. For example, to inform the
Receipts Number the “DTE” XML file must be filled as the following:
<CdgItem>
<TpoCodigo>RCVNUM</TpoCodigo>  This info “RCVNUM” is configurable in lookup LACLS_CL_LXML_SETUP
<VlrCodigo>27,28,35</VlrCodigo>  Represent the Receipts Number
</CdgItem>

In a structure like this, Solution will get the PO Number informed in tag “FolioRef” also will take
purchase order line number and then treats the Receipts information available on XML. For that the
mechanism used by Solution is the same allowed to inform purchase order line number, it means that
Solution will check information available on tag “TpoCodigo”. If value contented at this tag is the same
configured in lookup “LACLS_CL_LXML_SETUP”, at lookup code " TAG_RCV_NUM”, then Solution takes
value available on tag “VlrCodigo”, it will be considered as the receiving number informed by Supplier.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 13

Taking example above, let´s consider that value set in the lookup code is “RCVNUM”. Then Solution gets
the information available on tag “VlrCodigo” to find which receiving number is being treating.
This functionality brings more precision and effectiveness while looking for SaaS information to be used
in the Derivation process, ending up retrieving the receipts information to be referenced while creating
the Payables Invoice.

Important: More than one Receipt Number can be set by delimiting each one of that by using coma “,”.
In the example above, Solution will look for Receipts numbers 27 or 28 or 35.

TAXES – DOCUMENTS BASED ON PURCHASE ORDER

For documents types that are working based on purchase orders, Solution will take taxes codes were
created in purchase orders.

As known, “DTE” XML file has taxes informated at header level. There is no any taxes information
provided at lines leve. However, in Oracle Payables taxes must be entered by line. To solve it, while
creating invoice in Payables, Solution does the following:
 Takes the line amount informed in the tag “MontoItem” and send it as taxable amount;
 Takes the taxes codes available in Oracle Purchase Order, in Tax Details, and send them to
Oracle Payables.

These information are processed by Oracle Payables, generating, at the end, every tax calculation,
fitting with amounts of the “DTE” XML file.

TAXES – DOCUMENTS WITHOUT PURCHASE ORDER

For those document types (document type 56 – “Nota de Débito Electrónica” and 61 – “Nota de Crédito
Electrónica”) that purchase order are not considered, Solution will take taxes information from a set of
validation. This validation starts by retrieving taxes configured in Oracle Fusion Tax and that have Tax
Reporting “LACLS_CL_TAX_TYPE” assigned, indicating which taxes must be considered in the process.

As an example, takes a “DTE” XML file with document type 56. Consider that this document has an “IVA”
tax amount calculated using a tax rate of “19%”. In this scenario, Solution will work as the following:
 Takes the taxes configured in the SaaS, that ones with the Tax Reporting “LACLS_CL_TAX_TYPE”
assigned;
 In these set of information retrieved from SaaS, Solution will search for one tax information that
has the tax rate equal “19%”;
 It is demand that only one tax information line be found, if not, then Solution will not process
transaction.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 14

PAYABLES INVOICE NUMBER
As known, Oracle Payables run a validation in order to avoid duplicity. The restriction applied in Oracle
Payables considers the key formed by Invoice Number, Supplier and Business Unit. However, in Chile a
Supplier can issue an Invoice using certain number (for instance, 123456), for a document type and also
migth use the same number (123456) in other Invoice, but this time using other document type. In this
scenario, when company enters these two invoices, Oracle Payables validates and does not allow
entering one of these document.

LACLS Solution creates a mechanism to allow companies handle with it. For it, company must do the
following:

SUFFIX OR PREFIX
Use the lookup “LACLS_CL_LXML_SETUP”, in the lookup code “SUFFIX_PREFIX_INDICATOR” company
must indicate the “SUFFIX” or “PREFIX” which will be used while generating the invoice number.

SEGMENTS FORMAT
The invoice number will be a set of segments concatened. It must be provide using descriptive flexfields
(DFFs). It is under the configuration done in the lookup “LACLS_CL_LXML_DOC_TYPES”. In these “DFFs”
will be allowed indicate:
 Concatenated Code;
o It indicates the code chosen by company to compose the new invoice number.
 Concatenated segment;
o It indicates the char will be used to separate information that composed the new
invoice number.
 Oracle Payables document type;
o It indicates the Oracle Payables document type must be used while creating invoice in
Payables.

GENERATING INVOICE NUMBER

LACLS Solution starts the mechanism to create invoice number using information available in the “DTE”
XML file. Following this path, solution gets the “SII” invoice type in the tag “TipoDTE”. Using this data,
solution goes to lookup “LACLS_CL_LXML_DOC_TYPES” and look for one line that matches with the
value gotten. After finding this results, solution gets the information setup under “DFFs”, which are
created under the lookup “LACLS_CL_LXML_DOC_TYPES”.
1. Getting an example it can be better explained. Take a “DTE” XML file which is a “SII” invoice
type “33”.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 15

 2. Solution gets values available in the lookup “LACLS_CL_LXML_DOC_TYPES”. It should has similar
configuration, in according the company rules:

3. Solution also has to get the value set in lookup “LACLS_CL_LXML_SETUP”, to discovery where
concatenated values, as a “SUFFIX” or “PREFIX”.

Using this example, the invoice number generating by LACLS Solution would be:
Source info Tag “Folio” from “DTE” “DFF” under lookup “DFF” under lookup
XML file “LACLS_CL_LXML_DOC_TYPES” “LACLS_CL_LXML_DOC_TYPES”
Value 2307041759 - FA

As the configuration points to a compose using “SUFFIX” option, the final result will be:
Invoice Number 2307041759-FA

XML FILE VERSION

LACLS solution to automate Payables invoices creation – Payables XML Loader was created based on SII
layout version “1.0”. So, only “DTE” XML files in this version will be processed. Solution reads file based
on the structure defined in this version.

CURRENCY CODE
LACLS solution to automate Payables invoices creation – Payables XML Loader only will process “DTE”
XML files in Chilean pesos (“CLP”).

LACLS – CL – Payables XML Loader - Functional Implementation Guide 16

CONTROL STATUSES
Solution works in several phases of processing information. In some of it data will be available in the User
Interfaces (UI) in the Solution allowing user interacts, indicating the right information about source
purchase order in which “DTE” XML file is based.

# Status Phase User action

1. NEW Solution takes files from UCM. System status.
It will not allow user interaction.
2. INVALID FILE For those files that are not elegible for System status.
processing. It will not allow user interaction.
3. FILE INFO Status set when Solution takes files from System status.
UCM, takes its information and sent It will not allow user interaction.
them to the database layer.
4. DERIVATION IN After takes the “DTE” XML file and its System status.
PROGRESS information, solution is ready to work in It will not allow user interaction.
derivation processes. Before starting the
process, record is updated to this status.
5. ERROR CROSS Documents will lay in this status when System status.
CURRENCY CODE an invoice processed is based on a It will not allow user interaction.
purchase order that is not in “CLP”.
6. AWAITING USER Solutions applies validation in order to It will be available in UI Management
run derivation process, however, Derivation (“Mantenimiento”) in order
information required to create invoice user can indicate the purchase
in AP were not found. information, properly.
7. DERIVATED BY After user access the UI Management System status.
USER Derivation and applied changes, the It will not allow user interaction.
“DTE” XML file will be updated to this
status.
8. DERIVATED Information required for creating System status.
invoice in Payables were derivated It will not allow user interaction.
automatically, by Solution.
9. READY Al information were processed and System status.
Solution gotten all information required It will not allow user interaction.
to create invoice in Payables. The
document is ready to be sent to
Payables.
10. SENT TO PAYABLES Document was sent to Payables in order System status.
to create invoice. It will not allow user interaction.
11. ERROR CREATING When solution gets all information Given the wide scenarios validated by
INVOICE required to create an invoice in AP, then standard procedures, this status will
these set of information is sent to allow user interactions, providing to
Payables. Neverthells, it can contain user the opportunity to check and takes
some wrong information according to action, properly.
Oracle Payables rules and validation. It

LACLS – CL – Payables XML Loader - Functional Implementation Guide 17

 ended up in error while running rest api
to create invoice.
12. FINISHED Cycle of processing is finished, creating System status.
the invoice in Payables. It will not allow user interaction.
13. ERROR Generic error while processing System status.
information. It will not allow user interaction.

PRODUCT REQUIREMENTS ASSOCIATE TO LACLS SCOPE

Please verify Latin America Cloud Local Solutions (LACLS) - Installation and Maintenance Notes (Doc ID
2568812.1), available in My Oracle Support. aqui

INTENDED AUDIENCE

Welcome to LACLS solution to automate Payables invoices creation – Payables XML Loader.

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

 The principles and customary practices of your business financial area.

 Computer desktop application usage and terminology.

If you have never used Oracle Financials Cloud, we suggest you attend one or more of the Oracle Fusion
training classes available through Oracle University.

APPLICATIONS TECHNOLOGY

BIP –BUSINESS INTELLIGENCE PUBLISHER

LACLS for Chile was developed using the more powerful and innovative Oracle technologies when it
comes to create reports.

Using the B.I.P is possible to extract, format and report information required to be used by LACLS Chile
Solutions.

OIC – ORACLE INTEGRATION CLOUD

LACLS solution to automate Payables invoices creation – Payables XML Loader uses ICS. This powerful
technology simplifies how to build integrations in the cloud, letting you connect securely to applications
and services both in the cloud and on-premises.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 18

DATA BASE

LACLS for Chile uses PaaS Database Cloud to store and process information.

ASSUMPTIONS

The solution will be seen here assume that the following functionalities have been set up:

 Data Security
 Enterprise Structure
 General Ledger
 Procurement Business Function
 Payables
 Tax Regime information
 Tax Party Profiles
 Tax Rules
 Taxes and Tax Rate

LACLS – CL – Payables XML Loader - Functional Implementation Guide 19

PREPARING TO INSTALL/UPDATE

All information related to the install and update steps are described in guide
GUIDE_LACLS_CHILE_LOADER_XML_TECHNICAL.pdf.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 20

CONFIGURATION TASKS

There are some additional information required in order to be possible to work with the solution
properly.

In the next topics will be described each additional information according their approach type.

 Distribution Set
 Payables Source
 Supplier
 Lookup
 Value Set
 Descriptive Flexfield
 Tax Reporting Type Code
 Payables Invoice Holds and Releases
 Roles

DISTRIBUTION SET

Invoices created by LACLS solution to automate Payables invoices creation – Payables XML Loader will
use the Distribution Set name according to indicated in the lookup “LACLS_CL_LXML_SETUP”. It means
that when the invoices be created it will receive the accounting information configured under the
Distribution Set setup in the lookup. This behavior is applied for the following “SII” invoice types:

 56 – “Nota de Débito Electrónica”;

 61 – “Nota de Crédito Electrónica”.

Important: It is not necessary create a new Distribution Set, specific for the LACLS solution to automate
Payables invoices creation – Payables XML Loader. Companies can use one that already
exists.

PAYABLES SOURCE

One of the information that will be sent to Payables is the Source. Using this information company can
identify who was responsible for creating the Invoice or just filter by the specific Payables Source in further
searches. So, to do that, please navigate as following.

1. Navigate until Manage Payables Lookups page.

2. In the Search area, put the data “SOURCE” in the Lookup Type field. Then, click on Search button.
3. In the Search Results area, click on New icon.
4. At lookup code are, enter information as the following:

LACLS – CL – Payables XML Loader - Functional Implementation Guide 21

 Lookup Code Reference Data Set Enabled Meaning
LACLS_CL_LXML_AP_INVOICE Choose data set  LACLS CL Loader Payables XML
according the Invoice
Company setup
CUSTOM_CL_LXML_AP_INVOICE Choose data set  Custom CL Loader Payables
according the XML Invoice
Company setup

Important: These Source must be created exactly as defined due to Solution uses the Source while
creating Invoices in Payables.

INVOICE HOLDS

While processing automatically “DTE” XML Invoices, Solution will verify if there is a potention invoice with
the similar number already created in Payables. For those cases where may present potention duplicity
Solution will apply a hold over the invoice created by LACLS Solution. This way, in this topic will be created
the Hold used by Solution.

1. Go to Manage Invoice Holds and Releases task.

2. Enter information as following:
Create Invoice Hold or Release
Type Invoice hold reason
Name LACLS_CL_LXML_INVOICE_DUP
Description Hold para las facturas que pueden tener duplicidad
Allow Accounting Y
Allow Manual Release Y

3. Click on Save and Close button

LACLS – CL – Payables XML Loader - Functional Implementation Guide 22

 4. Done

MANAGE TRADING PARTNER ITEMS

In this topic must be created the relation between the Supplier Item and Company´s Items. This is used
for providing more inputs in order to try to find the Purchase Order. Based on this configuration, Solution
uses the information available on tag “NmbItem” and try to find which Oracle item corresponds to this
value, identifying the Oracle inventory item. This information is one of drives used to get the specific
purchase order is being used in the transaction.

1. In the home page, choose Product Management;

2. Go to Product Information Management functionality;
3. In the task list, choose Manage Trading Partner Items;
4. Enter creating information as following:
Manage Trading Partner Items
Trading Partner Item Item Code from Supplier.
It correspondes to the Item Code put in the XML Invoice file,
in the tag “NmbItem”.
Description  Not Required
Type Supplier
Trading Partner Choose the Supplier
Start Date Current Date

5. Go to Relationships area;
6. Enter information as following:
Create Supplier Item Relationship
Organization Choose the Inventory Organization
Item Choose Item that corresponds to the Supplier Item chosen in
the Trading Partner Item.
Start Date Set the date

7. Click on OK button
8. Click on Save button
9. Done

LACLS – CL – Payables XML Loader - Functional Implementation Guide 23

LOOKUP

LACLS for Chile requires the following configuration for common setups:

1. Go to Setup and Maintenance

2. Search for Manage Common Lookups

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 Chilean 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: 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:
Considering a specific Descriptive Flexfield, it is possible to have as many Contexts as desired, however,
in this situation, all LACLS_CL information need to be configured to be store in the same ATTRIBUTE
column, in all different Contexts created.

1. On Search Results area, find for “LACLS_DEFAULT_CONTEXT” in Lookup Type field and insert a
new lookup code. If there is no record found, press Create icon.

Lookup Type Meaning Description

Descriptive Flexfield
LACLS_DEFAULT_CONTEXT LACLS_DEFAULT_CONTEXT
Default

Module Lookup Configuration Level REST Access Secured

Functional Setup Manager User Secure

Lookup Codes
Lookup Code Enabled Meaning Description Tag
CL Yes Chile Default Context to Chile

Our suggestion is use the Country name “Chile” as context, however it can be chosen any value
according project specification. In this case the context chosen must be entered on the fields “Meaning”
and “Description”. The fields “Lookup Code” must be entered as “CL” and the “Display Sequence” can
be null or put a unique value.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 24

SETUP SOLUTION - LACLS_CL_LXML_SETUP

In this lookup will be stored information required by LACLS solution to automate Payables invoices
creation – Payables XML Loader. Values defined here are required for the solution runs properly.

Important: In order to avoid incorrect information, it is strongly recommended to copy and paste
information. However, attention to the values that must be entered according the companies
needs.

After navigating until Manage Common Lookups page, it is time to create the lookup.

1. In the Search Results area, click on New icon.

2. Enter information as following:
Lookup
Lookup Type LACLS_CL_LXML_SETUP
Meaning LACLS_CL_LXML_SETUP
Description Configuraciones requeridas por la Solución
Module Functional Setup Manager
Lookup Configuration Level User

3. Click on Save button

4. At lookup code are, enter information as the following:
Lookup Code Enable Meaning Description
SUFFIX_PREFIX_INDICA  Very Important: It indicates how
TOR The value inputted here will define how Invoice Num will be
Solution will generate new invoice created. Indicates
number. If information will be where Doc
concatenated by suffixing Concatenated
complementary segments or by prefixing Segment will be
them. concatened.

Values allowed:
 SUFFIX
 PREFIX

DIST_SET  Very Important: Payables Distribution

Put here the Payables Distribution Set Set.
that company wants to be present in the
Payables Invoices will be created by the
solution.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 25

 LIMIT_INVOICE_DATE  Very Important: It indicates the
Put here the number of the Days allowed number of the Days
in the rage between Receiving Date and between Receiving
Issuing Date of “DTE” XML file to the XML Date and Issuing
be loaded. Date.
TAG_PO_LINE_NUM  Very Important: It indicates the name
Put here the content will be used to will be used while
fullfilled in tag “TpoCodigo” to indicate feeding tag
the Purchase Order Line Number. “TpoCodigo” to
indicate the
Example: Purchase Order Line
<TpoCodigo>POLINE</TpoCodigo> Number

Using this example, the information set in

meaning field must be POLINE.

TAG_RCV_NUM  Very Important: It indicates the name

Put here the content will be used to will be used while
fullfilled in tag “TpoCodigo” to indicate feeding tag
the Receiving Number. “TpoCodigo” to
indicate the
Example: Receiving Number
<TpoCodigo>RCVNUM</TpoCodigo>

Using this example, the information set in

meaning field must be RCVNUM.

DOCUMENT TYPES - LACLS_CL_LXML_DOC_TYPES

Lookup to store document types that will be treated by Solution.

Important: In order to avoid incorrect information, it is strongly recommended to copy and paste
information. However, attention to the values that must be entered according the companies
needs.

After navigating until Manage Common Lookups page, it is time to create the lookup.

5. In the Search Results area, click on New icon;

6. Enter information as following:

LACLS – CL – Payables XML Loader - Functional Implementation Guide 26

 Lookup
Lookup Type LACLS_CL_LXML_DOC_TYPES
Meaning LACLS_CL_LXML_DOC_TYPES
Description
Module Functional Setup Manager
Lookup Configuration Level User

7. Click on Save button;

8. At lookup code are, enter information as the following:
Lookup Code Enable Meaning Description
33  Factura Electrónica Factura Electrónica
34  Factura No Afecta o Exenta Electrónica Factura No Afecta o Exenta
Electrónica
56  Nota de Débito Electrónica Nota de Débito Electrónica
61  Nota de Crédito Electrónica Nota de Crédito Electrónica

9. Click on Save button;

10. Done.

VALUE SET

LACLS for Chile requires to setup the following value set:

1. Go to Setup and Maintenance

2. Search for Manage Value Sets
3. Click on Manage Value Sets link
4. On Search Results area press Create icon
5. Create the value set entering each information as follow:

PAYABLES INVOICE NUMER

Create a value set to list all Status allowed for LACLS solution to automate Payables invoices creation –
Payables XML Loader.
Important: In order to avoid incorrect information, it is strongly recommended to copy and paste
information.

After navigating until Manage Common Lookups page, it is time to create the Value Set.

1. In the Search Results area, click on Create icon;

2. In the Create Value Set area, enter information as the follow:

LACLS – CL – Payables XML Loader - Functional Implementation Guide 27

 Value Set

Value Set Code LACLS_CL_LXML_INVNUM_DOC_CODE

Description Codigo de Documento que va se adjuntar en la
creación del Numero de la Factura
Module Functional Setup Manager
Validation Type Independent
Definition
Value Subtype Text
Maximum Length 30
Manage Values
Value Description Enabled
NA No se aplica 
Very Important: 33: Factura Electrónica 
Put value that company wants to
be used while solution is
compounding the invoice number
Very Important: 34: Factura No Afecta o Exenta 
Put value that company wants to Electrónica
be used while solution is
compounding the invoice number
Very Important: 61: Nota de Crédito Electrónica 
Put value that company wants to
be used while solution is
compounding the invoice number
Very Important: 56: Nota de Débito Electrónica 
Put value that company wants to
be used while solution is
compounding the invoice number

Setup may result in something similar to:

LACLS – CL – Payables XML Loader - Functional Implementation Guide 28

 3. Save and Close;
4. Click on create button to create other value set, as the following:

Value Set

Value Set Code LACLS_CL_LXML_INVNUM_INVOICE_TYPE

Description Tipo de Facturas Cuenta a Pagar
Module Functional Setup Manager
Validation Type Independent
Definition
Value Subtype Text
Maximum Length 30
Manage Values
Value Description Enabled
Credit memo Tipo de documento para Nota de Crédito 
Debit memo Tipo de documento para Nota de Débito 
Standard Tipo de documento estándar para Factura 

5. Save and Close;

6. Done.

DESCRIPTIVE FLEXFIELD

LACLS for Chile requires setup the following Descriptive Flexfields.

Important:
Create Context specifics, is just an optional step and the functionality is just to keep the information
grouped by Context, however, if the preference is not using the Context there is no problem at all.

Considering a specific Descriptive Flexfield, it is possible to have as many Contexts as desired, however,
in this situation, all LACLS_CL information need to be configured to be store in the same ATTRIBUTE
column, in all different Contexts created.
1. Go to Setup and Maintenance
2. Search for Manage Descriptive flexfield
3. Click on Manage Descriptive flexfield link
4. After Descriptive Flexfield created, press button Deploy Flexfield

DOCUMENT TYPES AND INVOICE NUMBER

This flexfield will be used by the solution to get setup information in order to concatenated values and
generate new invoice number.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 29

Important: In order to avoid incorrect information, it is strongly recommended to copy and paste
information.

Setting up the Lookup DFF:

1. In the field Flexfield Code inform FND_LOOKUP_VALUES_B and press Search button;
2. In Search Results area Press the Edit icon;
3. Entering creating context for this solution, as the following:

Context
LACLS_CL_LXML_DOC_TYPES

Display Name IMPORTANT:

You must enter the name exactly as above since it is used to identify this
additional information.
Context Code LACLS_CL_LXML_DOC_TYPES
API Name This name will be generated automatically based on the Name. Keep it.
Description
Enabled Yes
4. Click on Create icon and then enter information to setup flexfields:

SEGMENT 1 SEGMENT 2
Sequence 10 20
Name LACLS_CL_LXML_INVOICE_NUM_DOC_CODE LACLS_CL_LXML_INVOICE_NUM_SEPARATOR
Code LACLS_CL_LXML_INVOICE_NUM_DOC_CODE LACLS_CL_LXML_INVOICE_NUM_SEPARATOR
Description
API Name Maintain the suggested name Maintain the suggested name
Enabled Yes Yes
Data Type Character Character
Table
Any Available Attribute column Any Available Attribute column
Column
Choose on value set according company
Value Set LACLS_CL_LXML_INVNUM_DOC_CODE
needs
Required No No
Prompt Codigo Documento para Concatenar Separador
Display
List of Values Text Box
Type
Display
5 1
Size
Read Only
BI Enabled Yes Yes

SEGMENT 3
Sequence 30
Name LACLS_CL_LXML_INVOICE_NUM_INVOICE_TYPE
Code LACLS_CL_LXML_INVOICE_NUM_INVOICE_TYPE
Description
API Name Maintain the suggested name
Enabled Yes
Data Type Character
Table
Any Available Attribute column
Column

LACLS – CL – Payables XML Loader - Functional Implementation Guide 30

 Value Set LACLS_CL_LXML_INVNUM_INVOICE_TYPE
Required No
Prompt Tipo Factura Cuentas por Pagar
Display
List of Values
Type
Display
5
Size
Read Only
BI Enabled Yes

5. Click on Save and Close until reach Deploy Flexfield page

6. Click on Deploy Flexfield button
7. Click on Ok button
8. Done

TAX REPORTING TYPE CODE

LACLS solution to automate Payables invoices creation – Payables XML Loader requires the following
Tax Reporting Type be created:

Creating the Tax Reporting Type Code:

1. Go to Setup and Maintenance

2. Search for “Manage Tax Reporting Types”
3. Click on Manage Tax Reporting Types link
4. In the Search Results area press the create icon

TAX TYPE - LACLS_CL_TAX_TYPE

This Tax Reporting Type was created to classify the transactional tax type. It is required at Tax setup
configuration, what will allow the solution identify the transactional taxes.

Important: For cases the Company has already been using other LACLS Chile Solution, this Tax Reporting
Type may be already created.

Create the Tax Reporting Type entering information as follows:

Tax Reporting Type

Tax Reporting Type Code LACLS_CL_TAX_TYPE

Tax Reporting Type Name Tipo de Impuesto

Tax Reporting Type Purpose Tax reporting type

LACLS – CL – Payables XML Loader - Functional Implementation Guide 31

 Country Chile

Data Type Text

Tax Regime Code

Tax

Minimum Length of Reporting Codes 1

Maximum Length of Reporting Codes 30

Start Date 1/1/01

End Date
Reporting Type Uses

Tax Rate Yes

All others Reporting Type Use No
Tax Reporting Codes

It is necessary create the valid values to identify the tax type. This information must be
entered for each tax rate defined to Chile.
It is necessary create the values as follow:
Tax Reporting Description Effective Start Effective
Code Date End Date

EXENTO EXENTO 01/01/01

IMP IMP 01/01/01

IVA IVA 01/01/01

OTROS OTROS 01/01/01

IVANOREC IVANOREC 01/01/01

ROLE FOR AUTOMATION TO CREATE PAYABLES INVOICES

This role is responsible for getting allow User to see information at Business Unit level. So, in order to
process information User must have the roles assigned to.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 32

  LACLS CL Loader XML for Payables - Super User:
This role allow user to access Dashboard(“Panel Controle”) UI, in which is possible to analyze
information about file processing and its status. It also enable to access Management Derivation
(“Mantenimiento”) UI.

The role LACLS CL Loader XML for Payables – Super User allows to analyze “DTE” XML file
processed by Solution. It is required due to some documents may not derivate all information
required to control access as, for example, the Business Unit.

 LACLS CL Loader XML for Payables - User:

This role allow user to access Dashboard(“Panel Controle”) UI, in which is possible to analyze
information about file processing and its status. It also enable to access Management Derivation
(“Mantenimiento”) UI.

The role LACLS CL Loader XML for Payables - User controls the access for this UI by Business
Unit level. It means that Users will have access to Business Unit information according to those
assigned under this role through standard funcionatility “Data Access for Users”.

 LACLS CL Loader XML for Payables - iSupplier:

This role allow user to access Dashboard(“Panel Controle”) UI, in which is possible to analyze
information about file processing and its status. It also enable to access Management Derivation
(“Mantenimiento”) UI.

LACLS CL LOADER XML FOR PAYABLES - SUPER USER

1. Menu --> Tools --> Click Security Console --> Click on Create Role Button.

The Basic Information to register:

Information Value
Role Name LACLS CL Loader XML for Payables - Super User
Role Code LACLS_CL_LXML_SUPERUSER_JOB
Role Category Common – Job Role

2. Click on Next Button until achieve User icon menu.

3. Go to Users. Set User that will have access to the solution.
4. Click on Next. Click on Save and Close.

LACLS CL LOADER XML FOR PAYABLES - USER

1. Menu --> Tools --> Click Security Console --> Click on Create Role Button.

The Basic Information to register:

LACLS – CL – Payables XML Loader - Functional Implementation Guide 33

 Information Value
Role Name LACLS CL Loader XML for Payables – User
Role Code LACLS_CL_LXML_USER_JOB
Role Category Common – Job Role

2. Click on Next Button until achieve User icon menu.

3. Go to Users. Set User that will have access to the solution.
4. Click on Next. Click on Save and Close.

LACLS CL LOADER XML FOR PAYABLES - ISUPPLIER

1. Menu --> Tools --> Click Security Console --> Click on Create Role Button.

The Basic Information to register:

Information Value
Role Name LACLS CL Loader XML for Payables – iSupplier
Role Code LACLS_CL_LXML_ISUPPLIER_JOB
Role Category Common – Job Role

2. Click on Next Button until achieve User icon menu.

3. Go to Users. Set User that will have access to the solution.
4. Click on Next. Click on Save and Close.

MANAGE DATA ACCESS FOR USER

After creating Role and assign it to Users, it is required to define the Business Unit that Users can access.

1. Navigate to Setup and Maintenance

2. Search for Manage Data Access for Users
3. In the Search Results area, click on Create button
4. Enter information – Role “LACLS CL Loader XML for Payables – User”

LACLS – CL – Payables XML Loader - Functional Implementation Guide 34

 Create Data Access for Users
*User Name Set the User that can run the LACLS solution to
automate Payables invoices creation – Payables
XML Loader
*Role LACLS CL Loader XML for Payables - User
(LACLS_CL_LXML_USER_JOB)
*Security Context Business unit
*Security Context Value Allow User to have access for the Business Unit

5. Click on Save and Close.

6. Done

Important:
When the role is assigned to users is necessary Access “Scheduled Process” task and submit the
processes:
 Retrieve Latest LDAP Changes.
 Import User and Role Application Security Data.

ENTERING INFORMATION
This section explain how to set some information that are required by Solution.

TAX TYPE
This information must be entered at tax rate level.

Entering the Tax Type value for the Tax Rates:

1. Go to Setup and Maintenance;
2. Search for “Manage Tax Rates and tax Recovery Rates” and then click on link;
3. Search for the Tax Rate defined to Chile;
4. Click on the Tax Rate Code link;
5. Press Edit button;
6. On Tax Reporting Codes folder press Add Row icon;
7. Set Tax Reporting Type Code “LACLS_CL_TAX_TYPE”;
8. In the Tax Reporting code field, choose value that represent the tax rate configured.

DOCUMENT TYPES AND INVOICE NUMBER

This information must be entered under lookup “LACLS_CL_LXML_DOC_TYPES” configuration.

1. Go to Setup and Maintenance;

LACLS – CL – Payables XML Loader - Functional Implementation Guide 35

2. Search for Manage Common Lookups;
3. Search for lookup type “LACLS_CL_LXML_DOC_TYPES”;
4. Goes to each lookup code value and click to expand descriptive flexfields;
5. Enter information according to company definition;
6. It will be similar to the following:

LACLS – CL – Payables XML Loader - Functional Implementation Guide 36

CREATING AUTOMATION TO CREATE PAYABLES INVOICES MENU ITEM
LACLS solution to automate Payables invoices creation – Payables XML Loader menu item is a
“shortcut” inside the ERP that allows user access Solution.

CREATE THE MENU ITEM (ICON)

To create the Automation to Create Payables Invoices menu Item follow the next steps.

1. Go to Home page
2. Navigate to Configuration menu option
3. Click on Sandboxes icon

4. Clink on the Create Sandbox button

5. Input a meaningful Name to the Sandbox
6. Active option “Structure” then click on “Create and Enter” button

LACLS – CL – Payables XML Loader - Functional Implementation Guide 37

7. Check the sandbox is active when it goes back to the home page.

8. Now, click on to expand Tools icon. The list of values will be displayed, click on Structure option

9. Click on “Create Group” (Important, skip to step 11 if you already have this group item)

10. Name it as “LACLS” and set the option “Show on Navigator” as Yes then click on “Save and close”
button.

11. Position the mouse cursor over Group “LACLS” has just been created, then click on Create list option
to expand values available, choose “Create Page Entry”.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 38

12. Add page information as indicated below following the steps:

12.1. On the “Show on Navigator”, choose “EL Expression”

This configuration controls if Solution icon will be available or not, according to role
assigned for User:

Name Value

CL XML Loader AP
 It can be a name chosen by company. Something that
Name
fits better to identify the icon and its functionality,
according to users familiarity
Group LACLS
EL Expression
Shon on Navigator Important: Edit EL Expression
Procedure required

12.1.1. While entering information to EL Expression. Click on Edit icon

12.1.2. Expression Editor will be popup. Enter the follow information:

Type a value or expression

#{[Link]['LACLS_CL_LXML_USER_JOB,LACLS_CL_LXML
_SUPERUSER_JOB,LACLS_CL_LXML_ISUPPLIER_JOB']}

12.1.3. Click on OK button

LACLS – CL – Payables XML Loader - Functional Implementation Guide 39

12.2. Show on Springboard
Click on Edit icon.
It will display icon on home menu LACLS area, according to role assigned for User:

Name Value

CL XML Loader AP
 It can be a name chosen by company. Something that
Name
fits better to identify the icon and its functionality,
according to users familiarity
Group LACLS
Shon on Navigator EL Expression
EL Expression
Show on Springboard
Important: Edit EL Expression
Procedure required

12.2.1. While entering information to EL Expression. Click on Edit icon

12.2.2. Expression Editor will be popup. Enter the follow information:

Type a value or expression

#{[Link]['LACLS_CL_LXML_USER_JOB,LACLS_CL_L
XML_SUPERUSER_JOB,LACLS_CL_LXML_ISUPPLIER_JOB']}

12.2.3. Click on OK button

12.3. To complete the configuration, User must setup the other information as the following:

Name Value

Mobile enabled No
Link Type Static URL
[Link]
Destination [Link]/ic/builder/rt/LACLS_CL_
LXML_LOADER/live/webApps/main/

LACLS – CL – Payables XML Loader - Functional Implementation Guide 40

 WARNING:
The Production to Test process (PtoT), production copy to test environment, makes the
<YourOICDomainInformation> entered on the Destination field entered above be
inherited as is. So, it is mandatory that after a PToT process, the
<YourOICDomainInformation> be updated pointing the OIC Test Domain.
Please inform your infrastructure team to consider this update step always you have a
PtoT process.

13. Click on Save and Close button

14. Click on OK button
15. To release configuration done, navigate to the sandbox and then click to expand options available.
Click on Publish
16. A confirmation message will be displayed, click on OK button:

17. Click in the Publish button:

18. Confirm:

19. Navigate back to the home page and confirm the LACLS solution to automate Payables invoices
creation – Payables XML Loader icon appears
20. Done.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 41

SOLUTION USER INTERFACES

Among several technical artefacts that are part of this Solution, there are these User Interfaces that
allows user interacts and follow the flow of processing the “DTE” XML file document.

The UI Dashboard (“Panel Controle”) provide to user a view of file processing and allow user analyze
and take the action required.

Other UI provided by Solution, the Management Derivation (“Mantenimiento”) provides more

information about “DTE” XML file is being processed. Furthermore, there are also information derivated
based on this document file.

DASHBOARD – PANEL DE CONTROLE

The main functionality of this UI is provide to user, in an easy way, the possibility to analyze files processed
and its status. Furthermore, there are some others functionalities that allow user to manage information,
upload and download files. These items will be approached in the detail in the next topics.

UPLOAD FILE – IMPORTAR DOCUMENTOS

By clicking on this button user can upload one “DTE” XML file document. To upload more than one file,
user can import a zip file in which can be stored several files. It is limited to 10 megabites.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 42

FILTER - FILTRO

Each field available allow user to filter the search and find files specifically in according to the criterias
selected.

WORKSHEET ICON

This icon allow user to download a “csv” file with information available on results search area.

MANAGE DERIVATION - MANTENIMIENTO

To enable the button, click on the line. After clicking on this button solution will launch to Manage
Derivation UI, displaying information about “DTE” XML file that corresponds to the line where cursor was
positionated.

DOWNLOAD ICON

Option will be enabled by clicking on the line. By clicking on the download icon, Solution will download
file processed.

REFRESH ICON

This button run a refresh on the results listed. It is usefull for those files are processing.

INFORMATION ICON

By clicking on this icon, User can view messages logged during the process of file. Information available
here is only for User level, there is no technical messages.

DOCUMENT HYPERLINK – DATOS DOCUMENTO, DATOS COMPAÑIA

It is a hyperlink to provide to user a fast navigation on the regions of the UI.

Clicking on “Datos documento” user can view information extracted from “DTE” XML file document. It
allows user identify main information about file is being processed.

By clicking on “Datos compañia” user can view information have already derivated while Solution
importing “DTE” XML file document.

MANAGEMENT DERIVATION – MANTENIMIENTO

Through this UI is possible view more data retrieved from “DTE” XML file document and its derivation
information. It means that user can analyze source information and data gotten by Solution in order to
generate invoice in Oracle Payables. For those scenarios in which Solution could not link “DTE” XML file

LACLS – CL – Payables XML Loader - Functional Implementation Guide 43

document lines with purchase order schedule line automatically, user can set this association using
functionalities available in the UI.

It is the while image of UI, however main areas from UI will be detailed in the following sections.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 44

HEADER – CABECERA DE DOCUMENTO

In this region are displayed most part of information available on the header of “DTE” XML file document.
Data presents at this area are showed as display only mode.

HEADER – DATOS DE LA COMPAÑIA

In this area will be displayed information gotten from derivation processes. Then, based on “DTE” XML
file document Solution found data required for creating invoice in Oracle Payables. The following table
was created to explain how information was gotten:

Prompt Source

Entidad legal Solution takes the Legal Entity Name from legal entity setup.
Legal Entity Name will be gotten from the legal entity which has the legal entity identifier
matching with tag “RUTRecep” content.
Unidad de negocios Business unit name gotten based on the purchase order.
Solution uses the purchase order referenced in tag “FolioRef” to find the purchase order
schedules lines in status “Open” that has been issued to supplier that is referenced in “DTE”
XML file document.
Nombre proveedor Solution gets the supplier name from Suppliers setup.
It is retrieved from a supplier that has the registration number corresponds to tag “RUTEmisor”.
Sítio proveedor It corresponds to Supplier Site of purchase order identified.
Origen Identifies that source in which invoice will be created in Oracle Payables.
Ordem de compra Purchase order number identified while processing the derivation.
In this field there is a list of values bringing purchase order, in open status, available for Supplier.
If user choose one of the purchase from this list of values, the following data will be updated:
 “Sítio proveedor”;
 “Ordem de compra”.
Tipo factura Using the information available on tag “TipoDTE”, Solution goes to lookup
“LACLS_CL_LXML_DOC_TYPES” and gets the data configured in DFF
“LACLS_CL_LXML_INVOICE_NUM_INVOICE_TYPE”.
Numero factura Information displayed on tag “Folio” will be concatenated in according to setup done under DFF
“LACLS_CL_LXML_INVOICE_NUM_INVOICE_TYPE”.
Fecha factura Same information available on tag “FchEmis”.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 45

LINES – LÍNEAS ARCHIVO

This area brings information available on lines of “DTE” XML file document.

MATCHING LINES – CONFRONTAR LÍNEA

In this button there is a functionality which allows user link the “DTE” XML file document line with the
purchase order schedule lines. Navigating to the line will enable the button. Then, click on it. It will open
a popup allowing user chooses the purchase order, the line and schedules available for supplier.

Important: UI lists schedules in status “Open” and that belongs to Supplier that is being processed.

After clicking on button, the following UI will be displayed:

1

2 7

3 4 5 6

8 9

LACLS – CL – Payables XML Loader - Functional Implementation Guide 46

LINKING LINES – CONCILIAR LÍNEAS DE FACTURA

In this UI user can link purchase order schedule lines with lines of “DTE” XML file document. User can
link one line of “DTE” XML file document with one or more purchase order schedule lines. Both
quantity and line amount will be validated, assuring that information provided on “DTE” XML file
document match with quantities/amount chosen by user in this UI.

The main information were mapped with number in order to detail its functionalities, as following:

Item Field Funcionality

1. Lines of file Information retrieved from lines of “DTE” XML file document. It
is displayed on the previous UI, it is also displayed in this UI once
more for providing to user a better experience while managing
lines.

2. Orden de Compra List of values bringing all purchase order and its schedules in
status “Open”. It is restricted by Supplier.

3. Combinar Icon allows user manages the quantity and amouts.

4. Cantidad de entrada Field fullfiled automatically by clicking on icon “Combinar”. This

corresponds to data available on line of “DTE” XML file
document.

While clicking on the icon, UI will automatically set field

“Cantidad de entrada” with quantity retrieved from tag
“QtyItem” of the “DTE” XML file document line. It will happen if
the purchase order schedule line has the matching basis
“QUANTITY”.

User can edit information populated automatically in order to

match quantity with the data present in the line of “DTE” XML
file document.

5. Precio Unitario This information will not be available to changes. It is retrieved

from line of “DTE” XML file document, tag “PrcItem”.

6. Monto de entrada For purchase order schedule line using matching basis
“QUANTITY” this field will be calculated automatically after

LACLS – CL – Payables XML Loader - Functional Implementation Guide 47

 clicking on “Combinar” icon. It is results of “Cantidad de entrada”
* “Precio Unitario”.

For purchase order schedule line with matching basis “AMOUNT”

this field will be set with value retrieved from line of “DTE” XML
file document, tag “MontoItem”. In this scenario field will be
enabled to user, allowing manage data to match amount inputed
with amount of line of file.

7. Purchase Order info Region with information retrieved from purchase orders issued
to Supplier. The information are detailed at schedule lines level.

8. Aceptar After managing information untill match them with data from
“DTE” XML file document, user must click on button “Aceptar” in
order to validate information entered. In this action UI will
validate quantities and amounts informed.

Quantity chosen in the UI must match with that one available on

tag “QtyItem” from line of “DTE” XML file document.

Amount choose in the UI must match with that one available on

tag “MontoItem” from line of “DTE” XML file document.

If one of these does not match, a warning message will be

displayed and changes will not be validated.

9. Cancelar Allow user cancel and exit from UI.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 48

SCHEDULES MATCHED – PROGRAMAS ASOCIADOS

This area will displayed all purchase order schedule lines linked with lines of “DTE” XML file document. It
works as a “master/detail” relationship.

1
2

3 5 7 9 11
4 6 8 10

12 13

Item Field Funcionality

Suprimir Asociación This functionality allows user delete an association done

1. between purchase order schedule lines and the lines of “DTE”
XML file document. The button will be enabled by clicking on the
line. Once button is enabled to user, click on button to delete the
link. A message will be displayed before deleting the relation.

2. Confrontar Recepción Button to list the Receipts linked to the Purchase Order
Schedules Lines (Line Locations).

3. Orden Compra Purchase Order Number.

It represent the PO found by Solution automatically or chosen by

User.

4. Línea OC Purchase Order Number Line.

It represent the PO Line found by Solution automatically or

chosen by User.

5. Línea Programa Purchase Order Schedules Lines (Line Locations).

LACLS – CL – Payables XML Loader - Functional Implementation Guide 49

 It represent the PO Schedules Lines found by Solution
automatically or chosen by User.

6. Ítem OC Item Code from PO.

Item found by Solution automatically or chosen by User.

7. Descripción Ítem OC Item Description from PO

8. Cantidad de Entrada Quantity from Purchase Order Schedule Lines.

It represents the quantity found by Solution automatically or

chosen by User.

9. Monto de Entrada Amount from Purchase Order Schedule Lines.

It represents the amount found by Solution automatically or

chosen by User.

10. Base Compra Matching Basis of Purchase Order. It is a standard concept to

indicate if Payables Invoices will be matched by checking
Quantity or Amount.

It corresponds to “QUANTITY” or “AMOUNT”.

11. Tipo Confrontación Match Option of Purchase Order. It is a standard concept to

indicate the type of entered is allowed in Payables while creating
Invoice.

It corresponds to “P” for Purchase Order or “R” for Receipts.

12. Cantidad Total It is a sum of quantities elegibled for Purchase Order Schedules.
These values aggruped must be matched with the quantity
presented in the “DTE” XML file, tag “QtyItem”.

13. Monto Entrada Total It is a sum of amounts elegibled for Purchase Order Schedules.

These amount aggruped must be matched with the line amount

presented in the “DTE” XML file, tag “MontoItem”.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 50

MATCHING LINES – CONFRONTAR RECEPCIÓN

In this button there is a functionality which allows user link the purchase schedule lines with its respective
receipts. Navigating to the schedule line have been chosen this button will be enabled. By clicking on it,
will open a popup allowing user chooses the receipts that matches with the purchase schedule line.

LINKING PURCHASE SCHEDULE LINES – CONCILIAR LÍNEAS DE ENTREGA

Using this functionality, User can link purchase order schedule lines with its respective receipts. It
means that for purchase schedule lines with match option “Receipt” Solution allows to indicate the
receipts have been done previoully. These information will be used by Solution while creating the
Payables Invoices, referencing the Purchase Order and Schedules linked with its Receipts.

After clicking on button, the following UI will be displayed:

2
3

4 5 6 7 8 9 10 11 12 13

14 15

16 17

The main information were mapped with number in order to detail its functionalities, as following:

Item Field Funcionality

1. Line of purchase It is displayed on the previous UI, it is also displayed here for
schedule line chosen in providing to user a better experience while managing
previous UI information.

2. Recepción List of values bringing all receipts linked to purchase schedule

line (Line Location).

LACLS – CL – Payables XML Loader - Functional Implementation Guide 51

3. “Check box - All” It allows User to choose one or all lines available.

4. “Check box – One-by- It allows User to choose one line available.

One”

5. Recepción Receipt Number.

6. Línea Receipt Line Number.

7. Cantidad de Entrada Quantity from Receipt.

8. Monto de Entrada It is an important point. For lines vinculated to purchase schedule

line with matching basis “QUANTITY”, then the amount
displayied in this field represents the quantity of Receipt
multiplied by Unit Selling Price of the “DTE” XML file line( linked
to this line is being managed).

For those purchase schedule line with matching basis

“AMOUNT”, then the value in this field will be recovered from
Receipt directly.

9. Organización Inventory Organization where the receipt was done.

10. Subinventario Subinventory where the receipt was done.

11. Ubicación Envio Ship to Location where receipt was done.

12. Fecha Recepción Receipt Transaction Date.

13. Recepción por User who receipts.

14. Total Total of Quantity chosen. Sum of “Cantidad de Entrada”.

15. Total Total of Amount chosen. Sum of “Monto de Entrada”.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 52

 16. Aceptar After managing information untill match them user must click on
button “Aceptar” in order to sent information to new area in the
UI called “Recepciones Asociadas”.

17. Cancelar Allow user cancel and exit from popup.

RECEIPTS MATCHED – RECEPCIONES ASOCIADAS

This area will displayed all receipts linked with purchase schedule lines. It works as a “master/detail”
relationship.

2 3 4 5 6 7 8 9 10

11 12

Item Field Funcionality

1. Suprimir Asociación This functionality allows user delete an association done

between purchase order schedule lines and its receipts. The
button will be enabled by clicking on the line. Once button is
enabled to user, click on button to delete the link. A message will
be displayed before deleting the relation.

2. Recepción Receipt Number.

Information chosen from list of values in the previous UI.

3. Línea Receipt Line Number.

Information chosen from list of values in the previous UI.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 53

4. Cantidad de Entrada Quantity from receipt.

Information chosen from list of values in the previous UI.

5. Monto de Entrada Receipt line amount.

Information chosen from list of values in the previous UI.

6. Organización Inventory Organization where the receipt was done.

Information chosen from list of values in the previous UI.

7. Subinventario Subinventory where the receipt was done.

Information chosen from list of values in the previous UI.

8. Ubicación Envio Ship to Location where receipt was done.

Information chosen from list of values in the previous UI.

9. Fecha Recepción Receipt Transaction Date.

Information chosen from list of values in the previous UI.

10. Recepción por User who receipts.

Information chosen from list of values in the previous UI.

11. Total Total of Quantity chosen. Sum of “Cantidad de Entrada”.

12. Total Total of Amount chosen. Sum of “Monto de Entrada”.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 54

TOTALS – TOTALES ARCHIVO

This area brings information available on “DTE” XML file document, it comes from group called “Totales”.

Item Field Funcionality

Suprimir Asociación This functionality allows user delete an association done

1. between purchase order schedule lines and its receipts. The
button will be enabled by clicking on the line. Once button is
enabled to user, click on button to delete the link. A message will
be displayed before deleting the relation.

BUTTONS

There actions under buttons at top of UI.

INFO

This button shows a popup listing relevant messages for users.

ACTIONS - ACIONES

In Actions button user can save information managed and also submit it. This event will save
information and change the status of processing indicating user interaction. This “DTE” XML file
document will be processed by Solution in the next cycle scheduled.

DONE - LISTO

This event exits from UI and navigate back to the previous one, the Dashboard UI.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 55

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.

LACLS – CL – Payables XML Loader - Functional Implementation Guide 56