Professional Documents
Culture Documents
Version 2
MAY 2020
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
Brazilian Receivables Collection Documents
1
TABLE OF CONTENTS
TABLE OF CONTENTS ..............................................................................................................................................2
INTENDED AUDIENCE...................................................................................................................................................... 5
APPLICATIONS TECHNOLOGY............................................................................................................................................ 5
ASSUMPTIONS ............................................................................................................................................................... 5
SEQUENCES ................................................................................................................................................................ 16
VALUE SETS ................................................................................................................................................................ 19
DESCRIPTIVE FLEXFIELD................................................................................................................................................. 20
ASSOCIATING DOCUMENT TYPES TO TRANSACTION TYPES ................................................................................................... 22
CUSTOM ESS JOB ........................................................................................................................................................ 23
This document will continue to evolve as existing sections change and new information is added. All
updates are logged below, with the most recent updates at the top.
The “Brazilian Receivables Collection Documents” solution is a set of components which complements the Oracle
Fusion Cloud Receivables core functionalities providing predefined remittance and occurrence formats for Brazilian
banks. This solution is being delivered as part of Local Solution to offer this reporting capability until the moment
that the Oracle Fusion will have it inside the product.
Collection
Bank Remittance Occurrences
Document (Boleto)
If you have never used the Oracle BIP we suggest you attend one or more of the Oracle Fusion training classes
available through Oracle University.
APPLICATIONS TECHNOLOGY
LACLS for Brazil was developed using the more powerful and innovate Oracle technologies when it comes to create
data extractors.
The BIP objects will be stored in a structure that represents its country and functionality, as well.
The Receivables Collection Documents for Brazil objects will be stored in a structure that represents its country and
functionality, as well.
ASSUMPTIONS
The solution will be seen here assume that the following core functionalities have been set up:
The collection document printing (boleto) requires the font “INTERCALADO 2 DE 5 (FEBRABAN)” to print the
barcode.
The font “INTERCALADO 2 DE 5 (FEBRABAN)” is not provided by LACLS solution. You must acquire it from the
specialized supplier GBNET. For more information about to purchase the barcode supplier access the URL
http://www.gbnet.com.br/v2/codigo_de_barras_fontes_boleto_febraban_intercalado_2_de_5.html.
After the acquisition of the font “INTERCALADO 2 DE 5 (FEBRABAN)” you should download the font to your desktop
and upload it to the BIP server.
ATTENTION: The installation of barcode font should be done before the installation of the templates (xdoz) and
data models (xdmz) files.
1. Access BI Publisher Enterprise Tool (including /xmlpserver after URL used to access the Cloud environment).
The “Brazilian Receivables Collection Documents” solution provides a set of files that allow your company maintain
the process, according to the Oracle Fusion Cloud Application requirements.
There are some files that need to be uploaded at BI Publisher instance for the “Brazilian Receivables Collection
Documents” processes.
Customers that are installing the LACLS for Brazil must upload the “.xdmz” and “.xdoz” files in order to have BI
extractors available. The files are available in LACLS Brazilian Pack.
The required files are available for download on My Oracle Support. Please refer to MOS Note 2588752.1, Section
3, Table 3.1.1, to download the latest available Brazilian pack.
The following BIP artifact files from the Brazilian Pack will be used for upload according to the bank:
Bank Artifact
The files XDMZ contains the data model objects and the files XDOZ contains the layouts of reports. In the following
the steps describe in chapter “BI Publisher Repository – Install / Update Artifacts”.
The BIP artifacts developed in the solution (data model and layouts) should be deployed in BIP under the directory
structure:
It is mandatory do not create or update any other report or folder below the Shared Folders/Custom/Local
Solution/BR. Updates from LACLS Brazil could overwrite all files in this folder every time the upload process be
executed.
Considering that customer is already a user of the BIP tool, below will be described the steps required to deploy the
reports in the BIP folders.
1. Access BI Publisher Enterprise Tool (including “/xmlpserver” after URL used to access the Cloud
environment). A similar page will be displayed:
4. Expand the directory “Local Solution” and check if the directory “BR” exists. If not exists, create a new
directory called “BR”.
5. Expand the directory “BR” and check if the directory “BANK EFT AR” exists. If not exists, create a new
directory called “BANK EFT AR”.
6. Expand the directory “BANK EFT AR” and check if the directory “Data Models” exists. If not exists, create a
new directory called “Data Models”.
After you create all directories the following directory structure should be available in BIP for uploading the
objects related to the process:
1. Select the structure “Shared Folders/Custom/Local Solution/BR/BANK EFT AR/Data Models”, click on
“More” and “Upload” option.
2. Click on “Choose File” button and select to be uploaded from the folder “LACLS Brazilian
Pack/CA/BI/datamodel” of the Brazilian Pack. This step must be done for the following data model files
(XDMZ):
3. Click on “Upload” button to upload the data model files. When the upload is completed the data models
will be available in the directory “Shared Folders/Custom/Local Solution/BR/BANK EFT AR/Data Models”.
4. Select the structure “Shared Folders/Custom/Local Solution/BR/BANK EFT AR” and click on the Upload link.
5. Click on “Choose File” button and select to be uploaded from the folder “LACLS Brazilian
Pack/BR/BANK_EFT_AR/CA/BI/template/PTB” of the Brazilian Pack. This step must be done for the
following template files (XDOZ):
6. Click on “Upload” button to upload the report files. When the upload is completed the report files will be
available in the directory “Shared Folders/Custom/Local Solution/ BR/BANK EFT AR”.
Before creating Receivables collections some configuration is required in Oracle Fusion Cloud for the collection files
to be successfully generated.
SEQUENCES
Some banks require that the collection batch files have internally a serial numbering to guarantee the chronological
order of sending.
The “Brazilian Receivables Collection Documents” solution will use numbering sequences allowing:
1. Open the application and select the “Setup and Maintenance” tasks.
2. Search and select the “Manage Standard Lookups” task.
3. Click on the “Create” button.
6. Click on the “+” button and create the follow lookup codes:
LACLS_BR_REMESSA_BRADESCO LACLS_AR_BRADESCO_SEQ
LACLS_BR_REMESSA_BRASIL LACLS_AR_BRASIL_SEQ
LACLS_BR_REMESSA_CAIXA LACLS_AR_CAIXA_SEQ
7. Return to the “Setup and Maintenance” task to create a Document Sequence for each lookup code that
was created.
8. Search and select the “Manage Document Sequences” task.
9. Click on the “Create” button.
Initial number of
LACLS_AR_BRADESCO_SEQ Receivables Collections Automatic Not filled start date
sequence
Initial number of
LACLS_AR_BRASIL_SEQ Receivables Collections Automatic Not filled start date
sequence
Initial number of
LACLS_AR_CAIXA_SEQ Receivables Collections Automatic Not filled start date
sequence
11. Save
1. Open the application and select the “Setup and Maintenance” tasks.
2. Search and select the “Manage Value Sets” task.
3. Click on the “Create” button, insert a new value set fields and “Save”.
LACLS_BR_DOC_TYPE
An information that needs to be required for some banks in the remittance flat file is the Document Type.
The document type is associated to the Receivables transaction type in a Descriptive Flexfield.
Currently the document type is required only for Itaú Bank.
SEGMENT 1
Sequence 10
Name LACLS_BR_DOC_TYPE
Code LACLS_BR_DOC_TYPE
Description Tipo do Documento
API Name Maintain the suggested name
Enabled Yes
Data Type Character
Table Column ATTRIBUTE10
Value Set LACLS_BR_DOC_TYPE
Required No
Prompt Tipo do Documento
Display Type List of Values
Display Size 3
Read Only No
BI Enabled Yes
For some banks require the document type information in the remittance collection files. That information should
be registered in the Receivables transaction type using Descriptive Flexfields.
Currently the document type is required only for Itaú Bank.
To associate a document type to the Receivables transaction type execute the following steps:
The next steps show how to create a custom ESS job in Oracle Cloud to generate remittance collection files (boleto
and flat files).
1. Open the Fusion Cloud application and go to “Setup and Maintenance” task group.
2. Search and select the task “Manage Enterprise Scheduler Job Definitions and Job Sets for Financial, Supply
Chain Management, and Related Applications”.
3. Click on the “Create” button.
Banco BBM
Field Value
Display Name Boleto e Remessa Bancária Banco BBM
Name BoletoRemessaBBM
Path /financials/latinLocalizations/reports/
Description Cobrança Bancária para o Contas a Receber – Banco BBM
Job Application Name FscmEss
Job Type BIPJobType
Report ID /Custom/Local Solution/BR/BANK EFT AR/BBM Banking Collection Document.xdo
Banco do Brasil
Field Value
Display Name Boleto e Remessa Bancária Banco do Brasil
Name BoletoRemessaBBrasil
Path /financials/latinLocalizations/reports/
Description Cobrança Bancária para o Contas a Receber – Banco do Brasil
Job Application Name FscmEss
Job Type BIPJobType
/Custom/Local Solution/BR/BANK EFT AR/Banco do Brasil Banking Collection
Report ID
Document.xdo
Banco Fibra
Field Value
Display Name Boleto e Remessa Bancária Banco Fibra
Banrisul Bank
Field Value
Display Name Boleto e Remessa Bancária Banrisul
Name BoletoRemessaBanrisul
Path /financials/latinLocalizations/reports/
Description Cobrança Bancária para o Contas a Receber – Banrisul
Job Application Name FscmEss
Job Type BIPJobType
Report ID /Custom/Local Solution/BR/BANK EFT AR/Banrisul Banking Collection Document.xdo
Bradesco Bank
Field Value
Display Name Boleto e Remessa Bancária Bradesco
Name BoletoRemessaBradesco
Path /financials/latinLocalizations/reports/
Description Cobrança Bancária para o Contas a Receber – Bradesco
Job Application Name FscmEss
Job Type BIPJobType
Report ID /Custom/Local Solution/BR/BANK EFT AR/Bradesco Banking Collection Document.xdo
Citibank
Field Value
Display Name Boleto e Remessa Bancária Citibank
Name BoletoRemessaCitibank
Path /financials/latinLocalizations/reports/
Description Cobrança Bancária para o Contas a Receber – Citibank
Job Application Name FscmEss
Job Type BIPJobType
Report ID /Custom/Local Solution/BR/BANK EFT AR/Citibank Banking Collection Document.xdo
Daycoval Bank
Field Value
Display Name Boleto e Remessa Bancária Daycoval
Name BoletoRemessaDaycoval
Path /financials/latinLocalizations/reports/
Description Cobrança Bancária para o Contas a Receber – Daycoval
Job Application Name FscmEss
Job Type BIPJobType
/Custom/Local Solution/BR/BANK EFT AR/Banco Daycoval Banking Collection
Report ID
Document.xdo
Itaú Bank
Field Value
Display Name Boleto e Remessa Bancária Itaú
Name BoletoRemessaItau
Path /financials/latinLocalizations/reports/
Description Cobrança Bancária para o Contas a Receber – Banco Itaú
Job Application Name FscmEss
Job Type BIPJobType
JP Morgan Bank
Field Value
Display Name Boleto e Remessa Bancária JP Morgan
Name BoletoRemessaJPMorgan
Path /financials/latinLocalizations/reports/
Description Cobrança Bancária para o Contas a Receber – JP Morgan
Job Application Name FscmEss
Job Type BIPJobType
Report ID /Custom/Local Solution/BR/BANK EFT AR/JP Morgan Banking Collection Document.xdo
Pine Bank
Field Value
Display Name Boleto e Remessa Bancária Pine
Name BoletoRemessaPine
Path /financials/latinLocalizations/reports/
Description Cobrança Bancária para o Contas a Receber – Pine
Job Application Name FscmEss
Job Type BIPJobType
Report ID /Custom/Local Solution/BR/BANK EFT AR/Pine Banking Collection Document.xdo
Safra Bank
Field Value
Display Name Boleto e Remessa Bancária Safra
Name BoletoRemessaSafra
Path /financials/latinLocalizations/reports/
Description Cobrança Bancária para o Contas a Receber – Safra
Job Application Name FscmEss
Job Type BIPJobType
Report ID /Custom/Local Solution/BR/BANK EFT AR/Safra Banking Collection Document.xdo
Santander Bank
Field Value
Display Name Boleto e Remessa Bancária Santander
Name BoletoRemessaSantander
Path /financials/latinLocalizations/reports/
Description Cobrança Bancária para o Contas a Receber – Santander
Sofisa Bank
Field Value
Display Name Boleto e Remessa Bancária Sofisa
Name BoletoRemessaSofisa
Path /financials/latinLocalizations/reports/
Description Cobrança Bancária para o Contas a Receber – Sofisa
Job Application Name FscmEss
Job Type BIPJobType
/Custom/Local Solution/BR/BANK EFT AR/Banco Sofisa Banking Collection
Report ID
Document.xdo
6. Fill the following fields as suggested bellow and click on the “Save and Close” button to save the parameter.
8. Edit the Custom ESS Job created to check the “User Properties”. Case the user properties were not
inserted automatically you must to insert them manually.
To generate Receivables Collection Documents reports, a remittance batch should be created and formatted.
The next steps will guide you to create and format a remittance collection batch.
5. Fill all the required fields. If you are creating a manual batch is necessary to select the installments that will
be included in the remittance batch.
8. Click on the “Format Batch” button. The process “Prepare Collection Document Updates Remittance
Batches” will be submitted to format the remittance batch.
9. When the process “Prepare Collection Document Updates Remittance Batches” finishes successfully you
can search remittance batch again. The batch status was changed to “Formatted”.
To generate the receivables collection documents reports is necessary to inform the parameter “Remittance Batch
Number”. The “Remittance Batch Number” can be retrieved from the page “Manage Collections Remittance
Batches”.
The next steps will guide you to generate collection documents reports.
1. In the Fusion Cloud application open the “Tools” module.
2. Navigate to “Schedule Processes” page and open the task bar.
3. Click on the “Schedule New Process” button
4. Search for the ESS Job of the bank that will receive the collection. Example: “Boleto e Remessa Bancária
Itaú” and click “OK”.
6. At “Parameters” folder, inform the remittance batch number in the field “Número da Remessa”.
7. At “Output” folder, click on the “+” button and select the layout name and output format. You can select
mare then one layouts for the same process.
8. Click on the Submit button to generate the report. The report can be shown and downloaded through the
“output” link.
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.