Oracle Credit Management (OCM) Integration with Trading Community Architecture (TCA) Dun and Bradstreet (DNB) Has Multiple Issues When Searching and Purchasing
(Doc ID 1679742.1)
Last updated on AUGUST 24, 2020
Applies to:Oracle Credit Management - Version 12.1.1 and later
Oracle Trading Community - Version 12.1.1 and later
Information in this document applies to any platform.
Credit Management and Trading Community A D&B Integration.
There are three problems here:
Problem 1: Party search criteria, entered on New Application Page, is not carried forward to the Search D&B page for the first Party.
Problem 2: Searching for a second party, in the same session, and then navigating to the Search D&B page, is showing the first party searched in Problem 1. Here you have to manually clear the fields on the D&B Search page and populate the second party again.
Problem 3: When purchasing D&B data for the second party, even after populating the details manually, the system is updating first Party details with the D&B information of second Party.
Steps to Reproduce:
Search for customer ‘XXXX’ and Create Application page. Click on Go no results found
Click on button Search D&B
1. The FIRST problem is that the system did not carry over the name from ‘XXXX’ to the New Application page, to this search the D&B page.
- So you need to manually populate ‘XXXX’ here again and purchase the Party information from D&B. No problem.
Now, you click on the New Application page and search for a new Party ‘YYYYY’.
Click on go and no results are found, because this Party does not exist either.
Click on button Search D&B
2. The SECOND problem is that the system should carry over the new name from ‘YYYY’ to the New Application page to this Search D&B page. But, instead it is now showing the first party you searched for (‘XXXX’).
So you will manually clear the fields from ‘XXXX’ to ‘YYYY’.
3. Here is the BIG THIRD problem.
Even though you searched for Party ‘YYYYY’ in DNB, the system is updating the first Party ‘XXXX’ incorrectly with D&B information of ‘YYYY’ Party.
All three issues should be resolved, if search criteria from the New Application page is carried forward to the Search D&B page.
There are users who is using the OCM application globally and this issue needs to be resolved before more Party information is corrupted with the wrong Party information.
Credit Checks are performed using the OCM module and this is impacting the credit check process.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|1. Bug Summary|
|2. Fixed Files|
|3. Recommended Patches|
|4. Solution Steps|