Professional Documents
Culture Documents
LAD Consulting Localizations CLL-F509 Brazilian Credit Bureau Integration
LAD Consulting Localizations CLL-F509 Brazilian Credit Bureau Integration
LAD Consulting Localizations CLL-F509 Brazilian Credit Bureau Integration
Implementation Guide
RELEASE 12
April 2015
Version 3
DISCLAIMER :
Change Record
Data Autor Versão Referência da Alteração
Reviewers
Nome Função
Intended Audience
Welcome to Release 12 of the CLL-F509 Brazilian Credit Bureau Integration Implementation Guide.
This guide assumes you have a working knowledge of the following:
The principles and customary practices of your business area.
Computer desktop application usage and terminology
If you have never used Oracle Applications, we suggest you attend one or more of the Oracle Applications
training classes available through Oracle University.
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United
States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation accessible, with good
usability, to the disabled community. To that end, our documentation includes features that make
information available to users of assistive technology. This documentation is available in HTML format,
and contains markup to facilitate access by the disabled community. Accessibility standards will
continue to evolve over time, and Oracle is actively engaged with other market-leading technology
vendors to address technical obstacles so that our documentation can be accessible to all of our
customers. For more information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/ .
This documentation may contain links to Web sites of other companies or organizations that Oracle does not
own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these
Web sites.
1. Overview
2. Planning Your Implementation
3. Configuring Oracle CLL-F509 Brazilian Credit Bureau Integration
a. Profile Options Setup
b. Add CLL Extension Function to Menus
c. Personalize Forms
d. Proxy Setup and Business Event about CONFIE (R12.1.3+ only)
Related Guides
You should have the following related books on hand. Depending on the requirements of your particular
installation, you may also need additional manuals or guides.
Oracle Applications Installation Guide: Using Rapid Install:
This book is intended for use by anyone who is responsible for installing or upgrading Oracle Applications.
It provides instructions for running Rapid Install either to carry out a fresh installation of Oracle
Applications Release 12, or as part of an upgrade from Release 11i to Release 12. The book also describes
the steps needed to install the technology stack components only, for the special situations where this is
applicable.
Oracle Applications System Administrator's Guide Documentation Set
This documentation set provides planning and reference information for the Oracle Applications System
Administrator. Oracle Applications System Administrator's Guide - Configuration contains information on
system configuration steps, including defining concurrent programs and managers, enabling Oracle
Applications Manager features, and setting up printers and online help. Oracle Applications System
Administrator's Guide - Maintenance provides information for frequent tasks such as monitoring your
Integration Repository
The Oracle Integration Repository is a compilation of information about the service endpoints exposed by
the Oracle E-Business Suite of applications. It provides a complete catalog of Oracle E-Business Suite's
business service interfaces. The tool lets users easily discover and deploy the appropriate business service
interface for integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of the E-Business Suite. As your instance is patched,
the repository is automatically updated with content appropriate
for the precise revisions of interfaces in your environment.
Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data Browser, database
triggers, or any other tool to modify Oracle Applications data unless otherwise instructed.
Oracle provides powerful tools you can use to create, store, change, retrieve, and maintain information in
an Oracle database. But if you use Oracle tools such as SQL*Plus to modify Oracle Applications data,
you risk destroying the integrity of your data and you lose the ability to audit changes to your data.
Because Oracle Applications tables are interrelated, any change you make using an Oracle Applications
form can update many tables at once. But when you modify Oracle Applications data using anything other
than Oracle Applications, you may change a row in one table without making corresponding changes in
related tables. If your tables get out of synchronization with each other, you risk retrieving erroneous
information and you risk unpredictable results throughout Oracle Applications.
When you use Oracle Applications to modify your data, Oracle Applications automatically checks
that your changes are valid. Oracle Applications also keeps track of who changes information. If
you enter information into database tables using database tools, you may store invalid information.
You also lose the ability to track who has changed your information because SQL*Plus and other
database tools do not keep a record of changes.
Document Control...................................................................................................................... ii
Preface ...................................................................................................................................... iv
Intended Audience ............................................................................................................ iv
TTY Access to Oracle Support Services ......................................................................... iv
Documentation Accessibility .......................................................................................... iv
Accessibility of Code Examples in Documentation ...................................................... iv
Accessibility of Links to External Web Sites in Documentation ................................. iv
Structure ............................................................................................................................. v
Related Information Sources............................................................................................... v
Integration Repository .................................................................................................... vii
Do Not Use Database Tools to Modify Oracle Applications Data ................................ vii
1 Overview
2 Planning your
Implementation
Shared Planning
Latin America Consulting Localizations provides solutions for several countries. It is not
necessary to follow the steps from this manual if it is not planned to make use of the Brazilian
portion of the Latin America Consulting Localizations patch.
If you do not plan to implement Oracle Application for Brazil then it is not necessary to follow
this manual instructions.
The table below shows the Oracle Latin America Consulting Localizations implementation
checklist. All required setup steps in this checklist must be completed.
To have access to Brazilian Credit Bureau Integration Extensions it is necessary to enable some
profile options.
These profiles can be defined at several levels including at Operating Unit level.
Possible values are “Yes” or “No”. If no value is defined then it means “No”
Brazilian Credit Bureau Integration Profiles are:
CLL F509: Enable Extension This profile gives to the user the ability to
for Brazilian Serasa Solution use extension on AR Customer Standard
page and Transaction Types forms
The Latin America Consulting Localization Extension Page is a new function that has to be added
to the Menus linked to the responsibility that will be used.
To add this feature please follow these steps for each AP, GL and AR Responsibilities that will be
used by Brazilian Users:
1) Go to Responsibility Definition Form and get the Menu Name attached to the responsibility
Path: System Administrator -> Security -> Responsibility -> Define
3) Include a new line with the Latin America Consulting Extension page
Function Name: CLL LXM: Localization Extensions Manager
Each Latin America Localization Extension has to be defined as a personalization in the original Form
(or page) in R12. Personalization is a new feature and it is the best place to add extension functionality.
It is not possible currently to deliver this personalization as a patch since the customers personalizations
would be erased and replaced by localized personalizations. At this moment this has to be done
manually.
It is possible to carry all personalizations from one environment to another without the need of
reentering them manually. Please, look for Metalink notes regarding “Import/Export Personalizations”.
NOTE: After the configuration the Latin America Extension page will be avaliable as:
Forms: In the Form menu go to “Tools -> CLL Extension”
Java page: A new button will appear in the upper right corner with the name “CLL Additional Info”
for the Quick and for the Update page
b. Actions Tab
4. Set the sequence 20 (Go to SERASA Transaction Type Extension) in the same form:
a. Condition Tab
b. Actions Tab
5. Click in “Apply Now” button, save your job and close the form.
For more details about this fields, please verify User Guide Documentation.
5. Look for “Advanced Table: Account Sites” and press the “Create Item” button
Level: Site
Item Style: Column
ID: CLL_ADDITIONAL_INFO
7. Go back to the Personalization Page and look for “CLL_ADDITIONAL_INFO” and press the
Level: Site
Item Style: Image
ID: CLL_F509_HZ_CUST_ACC_SITES_EXT
Admin Personalization: true
Data Type: VARCHAR2
Disable Server Side Validation: false
Destination URI:
OA.jsp?page=/oracle/apps/cll/lxm/webui/ExtensionUsagesPG&pExtendedPage
=/oracle/apps/ar/cusstd/acctoview/webui/AcctOviewPG&retainAM=Y&pExtend
edTable=HZ_CUST_ACCT_SITES_ALL&pConnectString=CUST_ACCT_SITE_ID={@Cust
AcctSiteId}
Image URI: /OA_MEDIA/updateicon_enabled.gif
Initial Sort Sequence: none
No Wrap: false
For more details about this fields, please verify User Guide Documentation.
If the servers use proxy configuration, you must follow some steps to allow web service connections.
/vol02/oracle/<instance>/inst/apps/<instance>_<host>/ora/10.1.3/j2ee/forms/config/oc4j.properties
/vol02/oracle/<instance>/inst/apps/<instance>_<host>/ora/10.1.3/j2ee/oafm/config/oc4j.properties
/vol02/oracle/<instance>/inst/apps/<instance>_<host>/ora/10.1.3/j2ee/forms-
c4ws/config/oc4j.properties
/vol02/oracle/<instance>/inst/apps/<instance>_<host>/ora/10.1.3/j2ee/oacore/config/oc4j.properties
#
# Proxy Configuration for OC4J
#
http.proxyHost=<proxy host>
http.proxyPort=<proxy port>
http.nonProxyHosts=<proxy host name> – Ex: *.br.oracle.com
#
# Proxy Configuration for OC4J
#
https.proxyHost=<proxy host>
https.proxyPort=<proxy port>
Important:
Invoke Type: Responsible for do initial validations and call the WebService Serasa-
Confie
1) In “Workflow Administrator Web (New)” responsibility, access the Business Event setup:
1.1) Put the string “%.cll.se.%” in “Name” field and click on button “Go”.
- oracle.apps.cll.se.serasa.confieGeral.invoke
- oracle.apps.cll.se.serasa.confieGeral.response
If this option not appears in your environment, it’s necessary update in Workflow
table, as below:
UPDATE wf_resources
SET text='*'
WHERE name='WF_ADMIN_ROLE';
COMMIT;
Please, close your browser and try again, following steps above
1.3) After to click on link “Update”, a similar screen below, must be shown.
Name oracle.apps.cll.se.serasa.confieGeral.invoke
Description oracle.apps.cll.se.serasa.confieGeral.invoke
Status Enabled
Generate Function
Souce Local
Source Agent
Phase 10
Status Enable
1.7) Click on “Next” button. In this screen is informed the WebService endpoint. The patch
put the Homologation link. After tests, it’s necessary modify manually this information for
Production link:
In conformity with “Manual de Especificação Técnica de Integração com o Confie v5.6”, the
information valid is:
https://gw-homologa.serasa.com.br/SolucaoSintegra/SS20ws.asmx?wsdl
Homologation
https://sitenet05.serasa.com.br/SolucaoSintegra/SS20ws.asmx?wsdl
Production
1.10) The option already appears selected. Only click on “Next” button again. The another
screen will be showed:
oracle.apps.fnd.wf.bes.WebServiceInvokerSubscription
Java Rule Function
Subscription Parameters
Name Value
WFBES_CALLBACK_EVENT oracle.apps.cll.se.serasa.confieGeral.response
WFBES_CALLBACK_AGENT CLL_F509_SERASA_QAGENT
Description oracle.apps.cll.se.serasa.confieGeral.invoke
1) In “Workflow Administrator Web (New)” responsibility, access the Business Event setup:
1.1) Put the string “%.cll.se.%” in “Name” field and click on button “Go”.
- oracle.apps.cll.se.serasa.confieGeral.invoke
- oracle.apps.cll.se.serasa.confieGeral.response
Important:
If this option not appears in your environment, it’s necessary update in Workflow
table, as below:
UPDATE wf_resources
SET text='*'
WHERE name='WF_ADMIN_ROLE';
COMMIT;
Please, close your browser and try again, following steps above
1.3) After to click on link “Update”, a similar screen below, must be shown.
Name oracle.apps.cll.se.serasa.confieGeral.response
Description oracle.apps.cll.se.serasa.confieGeral.response
Status Enabled
Generate Function
Souce Local
Source Agent
Phase 10
Status Enable
1.7) Click in “Next” button. A new screen is open with the filled values:
To Agent
Priority Normal
Additional Options
Description oracle.apps.cll.se.serasa.confieGeral.response
For testing in Business Event setup, it’s necessary verify the follow steps:
2) Put an aleatory number in “Event Key” field (in this example was informed 10) and paste the
content below in “XML Content” field:
<?xml version="1.0"?>
<ConsultaConfieGeral xmlns="http://tempuri.org/SolucaoSintegra/SS20WS">
<XML>
<CONFIE><CONSULTA DOCUMENTO="00000125000111" UF="" LOGIN="68410265" SENHA="10203040"
TIPOCONSULTA="2" TIPORELATORIO="3" TIPORETORNO="1" TIPODOCUMENTO="1" TIMEOUT="100" DIAS="060" HTML="N">
</CONSULTA>
<MONITORE PERIODOMONIT="" EMAILMONIT="" REFERENCIAMONIT=""></MONITORE>
</CONFIE>
</XML>
</ConsultaConfieGeral>
If the return not appears, a problem is occurring and need to be analysis. Look for
this Step 4 again.
This topic showed how verify the possible errors that can occurs in the Public API's call. The
selects below must be executed:
select * from wf_notifications
where trunc(begin_date) = trunc(sysdate);