Professional Documents
Culture Documents
Version 3
12-May-2022
DISCLAIMER:
This guide may contain screen shots and output reports to facilitate the user comprehension about
the topic. The content represents a fictitious sample. Any similarity to actual persons, living or
dead, orAutomatic
Brazilian companyReceivables
names, active or inactive,
Collection is purely
Return Import - OICcoincidental and not intended in any manner
1
TABLE OF CONTENTS
TABLE OF CONTENTS ................................................................................................................................................2
This document will continue to evolve as existing sections change and new information is added. All updates are
logged below:
This document help you to define OIC/ICS artifacts and use the “Brazilian Automatic Receivables Collection Return
Import” process for Fusion Cloud application.
The “Brazilian Automatic Receivables Collection Return Import” solution is responsible to import the receivable
collection return files sent by the banks and import them to the Oracle Fusion Cloud Receivables providing insight
into the processing of collections by the bank.
• Banpará (CNAB240)
• Bradesco (CNAB400)
• CEF (CNAB400)
• Citibank (CNAB400)
• Daycoval (CNAB400)
• JP Morgan (CNAB400)
• SICOOB (CNAB240)
• SICREDI (CNAB240)
• Uniprime (CNAB400)
• Votorantim (CNAB400)
Welcome to Oracle Integration Cloud - OIC of the Latin America Cloud Local Solution for Brazil.
If you have never used the Oracle Integration Cloud - OIC, we suggest you attend one or more of the Oracle Fusion
training classes available through Oracle University.
LACLS for Brazil created connectors for the “Brazilian Automatic Receivables Collection Return Import” solution
using the ICS component of OIC/AIC.
The ICS simplifies how you build integrations in the Cloud, letting you connect securely to applications and services
both in the cloud and on-premises.
Currently, the solution OIC using FTP is available for the following banks:
Currently, the solution OIC using FTP and UCM is available for the following banks:
• Banpará (CNAB240)
• Bradesco (CNAB400)
• CEF (CNAB400)
• Citibank (CNAB400)
• Daycoval (CNAB400)
• JP Morgan (CNAB400)
• SICOOB (CNAB240)
• SICREDI (CNAB240)
• Uniprime (CNAB400)
• Votorantim (CNAB400)
During the process of installing and deploying LACLS solutions, you will be asked to provide a variety of application
and database users who will be responsible for interconnecting OIC, DBCS, Cloud Applications and the partner cloud.
In some cases user-specific privileges will be required to meet the minimum requirements necessary for solutions
to work well. Please, see below what are the most important credentials recommended to be used by LACLS.
DBCS lacls Review the “LACLS Infrastructure Database user and owner of the LACLS schema. This
Installation Guide” to full privileges list user is requested during the infrastructure
installation process.
OIC lacls_oic_user ServiceAdministrator (Service instance This user is used by processes originated of Cloud
administrator role.) Application and that need to connect to OIC. The
creation of this user is requested during the process
of implementing LACLS solutions.
OIC OICAgent ServiceAdministrator (Service instance Used by OIC Agent. This user is required to connect
administrator role.) the OIC to the Agent installed on DBCS during the
Infrastructure Installation process.
Cloud lacls_erp_user IT Security Manager This user is used by processes originated of OIC and
Application that need to connect to Cloud Application and/or
Application Diagnostics Administrator Cloud Application BIP. The creation of this user is
Application Implementation Consultant requested during the process of implementing
LACLS solutions.
Cash Management
Note:
✓ In addition to the users listed above. Other credentials will be required to complete solution configuration
from point to point when you need to establish connections with partner solutions. Information such as
credentials, ftp/sftp service access data and WebServices endpoints must be provided by the partner.
✓ If you want to connect more than one instance of Cloud Application, be sure to create the user
"lacls_erp_user" on all of them.
The “Brazilian Automatic Receivables Collection Return Import” 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 and OIC instances for the “Brazilian Automatic
Receivables Collection Return Import” process.
Customers that are installing the LACLS for Brazil must upload the “.par”, ”.xdmz” and “.xdoz” files in order to have
BIP extractors and OIC components 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 and OIC artifact files from the Brazilian Pack will be used for upload according to the bank and
CNAB:
Bank Artifact
LACLS_BR_AR_ABC_240_RET.par
LACLS_BR_AR_RETURN_ABC.par
LACLS_BR_AR_BPA_RET240.par
LACLS_BR_AR_BRR_240_RET.par
LACLS_BR_AR_RETURN_BRA.par
LACLS_BR_AR_RETURN_BB.par
LACLS_BR_AR_BB_240_RET.par
LACLS_BR_AR_ORI_240_RET.par
LACLS_BR_AR_RETURN_CEF.par
LACLS_BR_AR_RETURN_CITI.par
LACLS_BR_AR_DAY_400_RET.par
LACLS_BR_AR_RETURN_ITA.par
LACLS_BR_AR_ITA_240_RET.par
LACLS_BR_AR_RETURN_JPM.par
LACLS_BR_AR_SAFRA_RETURN.par
LACLS_BR_AR_SAN_240_RET.par
LACLS_BR_AR_SCB_240_RET.par
LACLS_BR_AR_SIC_240_RET.par
LACLS_BR_AR_VOT_400_RET.par
The files XDMZ contains the data model objects and the files XDOZ contains the layouts of reports and the file PAR
contains the OIC artifacts.
The BIP artifacts developed in the “Brazilian Automatic Receivables Collection Return Import” solution (data model
and layouts) will 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:
3. Under the directory “Custom”, check if the directory “Local Solution” exists. If not exists yet, create a new
directory called “Local Solution”. To do that, click on Create icon.
4. Expand the directory “Local Solution” and check if the directory “BR” exists. If not exists yet, create a new
directory called “BR”.
5. Expand the directory “BR” and check if the directory “BANK EFT AR” exists. If not exists yet, create a new
directory called “BANK EFT AR”.
6. Expand the directory “BANK EFT AR” and check if the directory “Process” exists. If not exists yet, create a
new directory called “Process”.
7. Expand the directory “Process” and check if the directory “Data Models” exists. If not exists yet, 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:
9. Click on “Choose File” button and select to be uploaded from the folder “LACLS Brazilian
Pack/BR/CA/BI/Process/datamodel” of the Brazilian Pack. This step must be done for the following data
model files (XDMZ):
10. 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 AP/Process/Data
Models”.
Bank Templates
13. Click on “Upload” button to upload the data model files. When the upload is completed the report files will
be available in the directory “Shared Folders/Custom/Local Solution/ BR/BANK EFT AR/Process”.
The following steps guide you to how import OIC components for the “Brazilian Automatic Receivables Collection
Return Import” process.
The par extension corresponds to a kind of the “zip” file where will be contained a set of flow files.
In the OIC terminology it corresponds to a package. When the file will be uploaded, the upload must be done under
the Packages option, in the Integration Designer menu.
The file is available in LACLS Brazilian Pack.
LACLS_BR_AR_ABC_240_RET.par (CNAB240)
ABC do Brasil
LACLS_BR_AR_RETURN_ABC.par (CNAB400)
LACLS_BR_AR_RETURN_BRR.par (CNAB400)
Barinsul
LACLS_BR_AR_BRR_240_RET.par (CNAB240)
LACLS_BR_AR_RETURN_BB.par (CNAB400)
Banco do Brasil
LACLS_BR_AR_BB_240_RET.par (CNAB240)
LACLS_BR_AR_CEF_400_RET.par (CNAB400)
CEF
LACLS_BR_AR_RETURN_CEF.par (CNAB240)
LACLS_BR_AR_RETURN_ITA.par (CNAB400)
Itaú
LACLS_BR_AR_ITA_240_RET.par (CNAB240)
LACLS_BR_AR_SAF_240_RET.par (CNAB240)
Safra
LACLS_BR_AR_SAFRA_RETURN.par (CNAB400)
LACLS_BR_AR_RETURN_SAN.par (CNAB400)
Santander
LACLS_BR_AR_SAN_240_RET.par (CNAB240)
5. In the Browse button, select the desired package file from the folder “LACLS Brazilian
Pack/BR/OIC/integration” of the Brazilian Pack and then click on the “Import” button.
LACLS_BR_AR_ABC_240_RET.par (CNAB240)
ABC do Brasil
LACLS_BR_AR_RETURN_ABC.par (CNAB400)
LACLS_BR_AR_RETURN_BRR.par (CNAB400)
Barinsul
LACLS_BR_AR_BRR_240_RET.par (CNAB240)
LACLS_BR_AR_RETURN_BB.par (CNAB400)
Banco do Brasil
LACLS_BR_AR_BB_240_RET.par (CNAB240)
LACLS_BR_AR_RETURN_ITA.par (CNAB400)
Itaú
LACLS_BR_AR_ITA_240_RET.par (CNAB240)
LACLS_BR_AR_SAF_240_RET.par (CNAB240)
Safra
LACLS_BR_AR_SAFRA_RETURN.par (CNAB400)
LACLS_BR_AR_RETURN_SAN.par (CNAB400)
Santander
LACLS_BR_AR_SAN_240_RET.par (CNAB240)
7. Viewing in detail, be sure that after import the package file the following files are available.
After import the package file the artifacts will be available in OIC. However, some configuration must be done in
order the Integration can run successfully.
LACLS_BR_AR_ABC_240_RET_BIP SOAP
LACLS_BR_AR_ABC_240_RET_UCM SOAP
LACLS_BR_AR_ABC_240_RET_REST REST
LACLS_BR_AR_ABC_240_RET_FTP FTP
LACLS_BR_AR_ABC_FTP FTP
LACLS_BR_AR_ABC_REST REST
ABC do Brasil (CNAB400)
LACLS_BR_AR_ABC_BIP SOAP
LACLS_BR_AR_BPA_RET_BIP SOAP
LACLS_BR_AR_BPA_UCM SOAP
LACLS_BR_AR_BPA_RET_REST REST
LACLS_BR_AR_BPA_RET_FTP FTP
LACLS_BR_AR_BRR_RET_BIP SOAP
LACLS_BR_AR_BRR_400_RET_UCM SOAP
LACLS_BR_AR_BRR_RET_REST REST
LACLS_BR_AR_BRR_RET_FTP FTP
LACLS_BR_AR_BRR_240_RET_REST REST
LACLS_BR_AR_BRR_240_RET_FTP FTP
LACLS_BR_AR_BRA_BIP SOAP
LACLS_BR_AR_BRA_UCM SOAP
LACLS_BR_AR_BRA_REST REST
LACLS_BR_AR_BRA_FTP FTP
LACLS_BR_AR_BB_BIP SOAP
LACLS_BR_AR_BB_REST REST
LACLS_BR_AR_BB_FTP FTP
LACLS_BR_AR_BB_240_RET_BIP SOAP
LACLS_BR_AR_BB_240_RET_UCM SOAP
LACLS_BR_AR_BB_240_RET_REST REST
LACLS_BR_AR_BB_240_RET_FTP FTP
LACLS_BR_AR_ORI_240_RET_BIP SOAP
LACLS_BR_AR_ORI_240_RET_UCM SOAP
LACLS_BR_AR_ORI_240_RET_REST REST
LACLS_BR_AR_ORI_240_RET_FTP FTP
LACLS_BR_AR_CEF_400_RET_BIP SOAP
LACLS_BR_AR_CEF_400_RET_UCM SOAP
LACLS_BR_AR_CEF_400_RET_REST REST
LACLS_BR_AR_CEF_400_RET_FTP FTP
LACLS_BR_AR_CEF_BIP SOAP
CEF (CNAB240)
LACLS_BR_AR_CEF_UCM SOAP
LACLS_BR_AR_CEF_REST REST
LACLS_BR_AR_CEF_FTP FTP
LACLS_BR_AR_CITI_BIP SOAP
LACLS_BR_AR_CITI_UCM SOAP
LACLS_BR_AR_CITI_REST REST
LACLS_BR_AR_CITI_FTP FTP
LACLS_BR_AR_DAY_400_RET_BIP SOAP
LACLS_BR_AR_DAY_400_RET_UCM SOAP
LACLS_BR_AR_DAY_400_RET_REST REST
LACLS_BR_AR_DAY_400_RET_FTP FTP
LACLS_BR_AR_ITA_BIP SOAP
LACLS_BR_AR_ITA_FTP FTP
LACLS_BR_AR_ITA_UCM SOAP
LACLS_BR_AR_ITA_240_RET_BIP SOAP
LACLS_BR_AR_ITA_240_RET_UCM SOAP
LACLS_BR_AR_ITA_240_RET_REST REST
LACLS_BR_AR_ITA_240_RET_FTP FTP
LACLS_BR_AR_JPM_BIP SOAP
LACLS_BR_AR_JPM_FTP FTP
LACLS_BR_AR_JPM_UCM SOAP
LACLS_BR_AR_SAFRA_RET_BIP SOAP
LACLS_BR_AR_SAFRA_RET_REST REST
LACLS_BR_AR_SAFRA_UCM SOAP
LACLS_BR_AR_SAF_240_RET_BIP SOAP
LACLS_BR_AR_SAF_240_RET_UCM SOAP
LACLS_BR_AR_SAF_240_RET_REST REST
LACLS_BR_AR_SAF_240_RET_FTP FTP
LACLS_BR_AR_SAN_BIP SOAP
LACLS_BR_AR_SAN_FTP FTP
LACLS_BR_AR_SAN_UCM SOAP
LACLS_BR_AR_SAN_240_RET_BIP SOAP
LACLS_BR_AR_SAN_240_RET_UCM SOAP
LACLS_BR_AR_SAN_240_RET_REST REST
LACLS_BR_AR_SAN_240_RET_FTP FTP
LACLS_BR_AR_SCB_240_RET_BIP SOAP
LACLS_BR_AR_SCB_240_RET_UCM SOAP
LACLS_BR_AR_SCB_240_RET_REST REST
LACLS_BR_AR_SCB_240_RET_FTP FTP
LACLS_BR_AR_SIC_240_RET_BIP SOAP
LACLS_BR_AR_SIC_240_RET_UCM SOAP
LACLS_BR_AR_SIC_240_RET_REST REST
LACLS_BR_AR_SIC_240_RET_FTP FTP
LACLS_BR_AR_UNP_400_RET_BIP SOAP
LACLS_BR_AR_UNP_400_RET_UCM SOAP
Uniprime (CNAB400)
LACLS_BR_AR_UNP_400_RET_ERP ORACLE ERP CLOUD
LACLS_BR_AR_UNP_400_RET_REST REST
LACLS_BR_AR_VOT_400_RET_BIP SOAP
LACLS_BR_AR_VOT_400_RET_UCM SOAP
LACLS_BR_AR_VOT_400_RET_REST REST
LACLS_BR_AR_VOT_400_RET_FTP FTP
SOAP CONNECTION
The connection SOAP is responsible for communication between OIC Solution and the Oracle Fusion Cloud.
1. Choose the desired SOAP connection according to the bank and CNAB.
LACLS_BR_AR_ABC_240_RET_BIP
LACLS_BR_AR_ABC_BIP
LACLS_BR_AR_BPA_RET_BIP
Banpará
LACLS_BR_AR_BPA_UCM
LACLS_BR_AR_BRR_RET_BIP
LACLS_BR_AR_BRR_400_RET_UCM
Banrisul
LACLS_BR_AR_BRR_240_RET_BIP
LACLS_BR_AR_BRR_240_RET_UCM
LACLS_BR_AR_BRA_BIP
Bradesco
LACLS_BR_AR_BRA_UCM
LACLS_BR_AR_BB_BIP
LACLS_BR_AR_BB_RET_UCM
Banco do Brasil
LACLS_BR_AR_BB_240_RET_BIP
LACLS_BR_AR_BB_240_RET_UCM
LACLS_BR_AR_ORI_240_RET_BIP
Banco Original
LACLS_BR_AR_ORI_240_RET_UCM
LACLS_BR_AR_CEF_400_RET_UCM
CEF
LACLS_BR_AR_CEF_BIP
LACLS_BR_AR_CEF_UCM
LACLS_BR_AR_CITI_BIP
Citibank
LACLS_BR_AR_CITI_UCM
LACLS_BR_AR_DAY_400_RET_BIP
Daycoval
LACLS_BR_AR_DAY_400_RET_UCM
LACLS_BR_AR_ITA_BIP
LACLS_BR_AR_ITA_UCM
Itaú
LACLS_BR_AR_ITA_240_RET_BIP
LACLS_BR_AR_ITA_240_RET_UCM
LACLS_BR_AR_JPM_BIP
JP Morgan
LACLS_BR_AR_JPM_UCM
LACLS_BR_AR_SAFRA_RET_BIP
LACLS_BR_AR_SAFRA_UCM
Safra
LACLS_BR_AR_SAF_240_RET_BIP
LACLS_BR_AR_SAF_240_RET_UCM
LACLS_BR_AR_SAN_BIP
LACLS_BR_AR_SAN_UCM
Santander
LACLS_BR_AR_SAN_240_RET_BIP
LACLS_BR_AR_SAN_240_RET_UCM
LACLS_BR_AR_SCB_240_RET_BIP
SICOOB
LACLS_BR_AR_SCB_240_RET_UCM
LACLS_BR_AR_SIC_240_RET_BIP
SICREDI
LACLS_BR_AR_SIC_240_RET_UCM
LACLS_BR_AR_UNP_400_RET_BIP
Uniprime
LACLS_BR_AR_UNP_400_RET_UCM
LACLS_BR_AR_VOT_400_RET_BIP
Votorantim
LACLS_BR_AR_VOT_400_RET_UCM
3. Fill the Email Address with the OIC administrator email account (optional).
4. Click on Configure Connectivity.
5. In the Connection Properties enter the values required:
https://<Cloud application domain name>/xmlpserver/services/PublicReportService?wsdl
The domain name is according with Oracle ERP Cloud – SaaS DFF Flexfield Web Service.
6. Click on OK button
7. Scroll down to Security option. Click on the Configure Security button
8. On the Credentials page, choose the Security Policy called No Security Police
9. Scroll to the top and then click on Test option, at the up right corner.
10. A Confirmation message will be displayed. Click on Validate and Test button
11. The successfully message will be shown at the top of the page.
12. Click on Save. There will be displayed a message indicating every Integration that use this Connection.
Choose Save.
13. The successfully message will be shown.
14. Click on Close button. It returns to the Connections page.
Brazilian Automatic Receivables Collection Return Import - OIC
37
ORACLE ERP CONNECTION
The Oracle ERP connection is responsible for communication between OIC solution and Oracle Fusion Cloud
application.
1. Choose the desired Oracle ERP connection according to the bank and CNAB.
LACLS_BR_AR_ABC_240_RET_ERP
ABC do Brasil
LACLS_BR_AR_ABC_CON
Banpará LACLS_BR_AR_BPA_RET_CN
LACLS_BR_AR_BRR_RET_CON
Banrisul
LACLS_BR_AR_BRR_240_RET_ERP
Bradesco LACLS_BR_AR_BRA_CN
LACLS_BR_AR_BB_CN
Banco do Brasil
LACLS_BR_AR_BB_240_RET_ERP
LACLS_BR_AR_CEF_400_RET_CON
CEF
LACLS_BR_AR_CEF_CN
Citibank LACLS_BR_AR_CITI_CN
Daycoval LACLS_BR_AR_DAY_400_RET_CON
LACLS_BR_AR_ITA_CN
Itaú
LACLS_BR_AR_ITA_240_RET_CON
JP Morgan LACLS_BR_AR_JPM_CN
LACLS_BR_AR_SAFRA_RET_CN
Safra
LACLS_BR_AR_SAF_240_RET_ERP
LACLS_BR_AR_SAN_CN
Santander
LACLS_BR_AR_SAN_240_RET_CN
SICOOB LACLS_BR_AR_SCB_240_RET_ERP
SICREDI LACLS_BR_AR_SIC_240_RET_CON
Uniprime LACLS_BR_AR_UNP_400_RET_ERP
Votorantim LACLS_BR_AR_VOT_400_RET_CON
3. Fill the Email Address with the OIC administrator email account
4. Click on the Configure Connectivity button
5. In the Connection Properties enter the values required:
https://<Cloud application domain name>:<port>/fndAppCoreServices/ServiceCatalogService?wsdl
REST CONNECTION
The REST connection will be used internally when a service needs to call other service, calling the flows from the
solution.
1. Search for the desired REST connection according to the bank and CNAB.
LACLS_BR_AR_ABC_240_RET_REST
ABC do Brasil
LACLS_BR_AR_ABC_REST
Banpará LACLS_BR_AR_BPA_RET_REST
LACLS_BR_AR_BRR_REST
Banrisul
LACLS_BR_AR_BRR_240_RET_REST
Bradesco LACLS_BR_AR_BRA_REST
LACLS_BR_AR_CEF_400_RET_REST
CEF
LACLS_BR_AR_CEF_REST
Citibank LACLS_BR_AR_CITI_REST
Daycoval LACLS_BR_AR_DAY_400_RET_REST
LACLS_BR_AR_ITA_REST
Itaú
LACLS_BR_AR_ITA_240_RET_REST
JP Morgan LACLS_BR_AR_JPM_REST
LACLS_BR_AR_SAFRA_RET_REST
Safra
LACLS_BR_AR_SAF_240_RET_REST
LACLS_BR_AR_SAN_REST
Santander
LACLS_BR_AR_SAN_240_RET_REST
SICOOB LACLS_BR_AR_SCB_240_RET_REST
SICREDI LACLS_BR_AR_SIC_240_REST
Uniprime LACLS_BR_AR_UNP_400_RET_REST
Votorantim LACLS_BR_AR_VOT_400_RET_REST
2. Click on the Actions icon. It will show the list, click on the Edit option.
3. Fill the Email Address with the OIC administrator email account.
4. Click on the Configure Connectivity button.
5. In the Connection Properties page enter the values required.
Enter the value on the flowapi/rest URL:
FTP CONNECTION
Now go to put credentials data about FTP adapter, these configurations will be use by our OIC Flows.
1. Search for the desired FTP connection according to the bank and CNAB.
LACLS_BR_AR_ABC_240_RET_FTP
ABC do Brasil
LACLS_BR_AR_ABC_FTP
Banpará LACLS_BR_AR_BPA_RET_FTP
LACLS_BR_AR_BRR_FTP
Banrisul
LACLS_BR_AR_BRR_240_RET_FTP
Bradesco LACLS_BR_AR_BRA_FTP
LACLS_BR_AR_BB_FTP
Banco do Brasil
LACLS_BR_AR_BB_240_RET_FTP
LACLS_BR_AR_CEF_400_RET_FTP
CEF
LACLS_BR_AR_CEF_FTP
Citibank LACLS_BR_AR_CITI_FTP
Daycoval LACLS_BR_AR_DAY_400_RET_FTP
LACLS_BR_AR_ITA_FTP
Itaú
LACLS_BR_AR_ITA_240_RET_FTP
JP Morgan LACLS_BR_AR_JPM_FTP
LACLS_BR_AR_SAFRA_RET_FTP
Safra
LACLS_BR_AR_SAF_240_RET_FTP
LACLS_BR_AR_SAN_FTP
Santander
LACLS_BR_AR_SAN_240_RET_FTP
SICOOB LACLS_BR_AR_SCB_240_RET_FTP
SICREDI LACLS_BR_AR_SIC_240_FTP
Uniprime LACLS_BR_AR_UNP_400_RET_FTP
2. Click on the hamburger menu and then choice the Edit option:
3. In the next screen, go to put the configuration credentials of the OIC FTP connection
9. Click on the OK and then Test de connection. If return Success, click on Save and then Close.
10. Done.
There are some values and information that must be used in the Integration process. These are, in most of cases,
constants or credentials to access some services. The OIC provide the Lookup functionality which is a flexible way to
setup this type of information.
1. Navigate to Lookups
3. A similar page to the follow will be displayed. To change the values, click on the Value area and then put
the required information.
ParameterName Value
ftpDirectory Inform the FTP directory where the bank return files to be
import are located. The integration will take the bank return
files from this directory and submit them to the import
process. This directory should be created in the FTP server
according to the company definition.
ftpDirectoryProcessed Inform the FTP directory where the bank return files
processed successfully will be transferred by the integration.
This directory should be created in the FTP server according
to the company definition.
ftpDirectoryError Inform the FTP directory where the bank return files
processed with errors will be transferred by the integration.
This directory should be created in the FTP server according
to the company definition.
ucmDirectory Inform the UCM directory where the bank return files to be
import are located. The integration will take the bank return
files from this directory and submit them to the import
process.
ucmDirectoryProcessed Inform the UCM directory where the bank return files
processed successfully will be transferred by the integration.
ucmDirectoryError Inform the UCM directory where the bank return files
processed with errors will be transferred by the integration.
ParameterName Value
ftpDirectory Inform the FTP directory where the bank return files to be
import are located. The integration will take the bank return
files from this directory and submit them to the import
process. This directory should be created in the FTP server
according to the company definition.
ftpDirectoryError Inform the FTP directory where the bank return files
processed with errors will be transferred by the integration.
This directory should be created in the FTP server according
to the company definition.
ucmDirectory Inform the UCM directory where the bank return files to be
import are located. The integration will take the bank return
files from this directory and submit them to the import
process.
ucmDirectoryProcessed Inform the UCM directory where the bank return files
processed successfully will be transferred by the integration.
ParameterName Value
Parameter_DirectoryRoot_Citibank Inform the FTP directory where the bank return files to be
import are located. The integration will take the bank return
files from this directory and submit them to the import
process. This directory should be created in the FTP server
according to the company definition.
Parameter_DirectorySuccess_Citibank Inform the FTP directory where the bank return files
processed successfully will be transferred by the integration.
This directory should be created in the FTP server according
to the company definition.
Parameter_DirectoryError_Citibank Inform the FTP directory where the bank return files
processed with errors will be transferred by the integration.
This directory should be created in the FTP server according
to the company definition.
ucmDirectoryProcessed Inform the UCM directory where the bank return files
processed successfully will be transferred by the integration.
ucmDirectoryError Inform the UCM directory where the bank return files
processed with errors will be transferred by the integration.
1. Check if the statement file to be imported should be available at directory configured at integration lookup.
For FTP files: “Parameter_DirectoryRoot_Citibank” or “ftpDirectory”.
For UCM files: “ucmDirectory”
2. After logged into Oracle Integration Cloud, click on the Integrations icon.
LACLS_BR_AR_ABC_240_RET (CNAB240)
ABC do Brasil
LACLS_BR_AR_BANK_RET_ABC (CNAB400)
LACLS_BR_AR_BRR_RET (CNAB400)
Banrisul
LACLS_BR_AR_BRR_240_RET (CNAB240)
LACLS_BR_AR_BANK_RET_BB (CNAB400)
Banco do Brasil
LACLS_BR_AR_BB_240_RET (CNAB240)
LACLS_BR_AR_CEF_400_RET (CNAB400)
CEF
LACLS_BR_AR_BANK_RET_CEF (CNAB240)
LACLS_BR_AR_BANK_RET_ITA (CNAB400)
Itaú
LACLS_BR_AR_ITA_240_RET (CNAB240)
LACLS_BR_AR_SAFRA_RETURN (CNAB400)
Safra
LACLS_BR_AR_SAF_240_RET (CNAB240)
LACLS_BR_AR_BANK_RET_SAN (CNAB400)
Santander
LACLS_BR_AR_SAN_240_RET (CNAB240)
LACLS_BR_AR_BRR_400_RET_UCM (CNAB400)
Banrisul
LACLS_BR_AR_BRR_240_RET_UCM (CNAB240)
LACLS_BR_AR_BANK_RET_BB_UCM (CNAB400)
Banco do Brasil
LACLS_BR_AR_BB_240_RET_UCM (CNAB240)
LACLS_BR_AR_CEF_400_RET_UCM (CNAB400)
CEF
LACLS_BR_AR_BANK_RET_CEF_UCM (CNAB240)
LACLS_BR_AR_BANK_RET_ITA_UCM (CNAB400)
Itaú
LACLS_BR_AR_ITA_240_RET_UCM (CNAB240)
LACLS_BR_AR_SAFRA_RETURN_UCM (CNAB400)
Safra
LACLS_BR_AR_SAF_240_RET_UCM (CNAB240)
LACLS_BR_AR_BANK_RET_SAN_UCM (CNAB400)
Santander
LACLS_BR_AR_SAN_240_RET_UCM (CNAB240)
4. Click on the hamburger menu and then click on the “Submit Now” option.
When the process “Import Bank Returns for Customer Payments” is submitted successfully new entries are created
for the collection document and the status is updated.
To check the return sent by the bank follow the next steps:
3. Open the task “Collections Remittance Batches for Brazil” > “Manage Collection Documents”
4. Search for de collection document and check the status and updates of the collection document.
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.