Oracle TCA Parent Party concept (D&B)

D&B	Duns and Bradstreet
ERAM	Enterprise Risk Assessment Manager
DUNS	Data  Universal Numbering System Application integrated with D&B for customer rescore and refresh data for dell
OCM	Oracle Credit management
GDP	Global Data product
ADP	Additional Data points

TCA Architecture:

TCA or the Trading Community Architecture is an Oracle framework which allows the creation and maintenance of customer database. It is the global repository for all customer related information like the name and address information, customer relationships etc. All these information is stored in the TCA registry which is the single source of truth for all customer related data. Users with specific assigned role could view, create, and update the Registry information. The structure is flexible; therefore the information can be modeled to best fit a company’s business. Benefits of a single global customer master include single point of data entry, efficient analysis and reporting capabilities.

One important feature of TCA is the maintenance of complex relationships in the system. Parties in the system including organizations and person can be connected through hierarchical and circular relationships. These relationships help in building up a reporting structure as well as allow better control over various entities in the organization.

This document would emphasis on party relationships which is an important aspect of the TCA structure

 

Introduction to the ERAM and DNB:

 

Dun & Bradstreet (D&B) maintains a growing global database of more than 70 million businesses worldwide. This database provides key information such as D&B's unique identifier, the D-U-N-S Number, and executive contacts, as well as demographic, financial, and credit risk data. D&B provides information in the form of data products and Business Information Reports that contain a variety of data elements.

Third Party Data Integration to obtain any of these data products:

·         Business Verification provides the information necessary to verify a company's existence and validate its location with background information such as primary name, address, phone, SIC codes, branch indicator, and D&B D-U-N-S Number

·         Quick Check use to perform low-risk credit assessments with D&B's core credit evaluation information

·         Delinquency Score - D&B score that indicates the risk of a company to make delinquent payments, based on payment history information

·         Global Failure Risk Score derived predictive score that helps you assess the risk of business failure

·         Financial Standing key financial information such as sales volume, net worth, assets, and liabilities to help you assess a party's financial condition

·         Decision Support provides information that you use with a decision support system or manual credit evaluation processes

·         Enterprise Management provides detailed demographic, corporate structure, risk, and financial information

·         Commercial Credit Score includes the Commercial Credit Score and other data elements that you can use to predict the likelihood that a company would pay invoices in a severely delinquent manner within the next 12 months

• D&B rating that indicates a company's creditworthiness. The rating usually consists of a financial strength code and a risk indicator
• General information such as number of employees, business history, and so on
• Financial statements
• Payment performance information, such as the D&B PAYDEX score

 

ERAM

ERAM is an application which is built on DNB  data base which is communicated with Dell data base for the all the customer of dell for credit and financial analysis. Dell can communicate with ERAM for Real time information using API request and API response for an customer Credit request from the OCM module in oracle.

DNB offers advanced rules-based capabilities to support more complex credit risk management needs. DNBi’s five powerful add-on modules provide end-to-end risk management coverage that combine your own company data with Dun & Bradstreet’s critical information on more than 250 million company records worldwide—letting you make decisions on new credit applications instantly, standardize your credit review processes, conduct advanced portfolio and account analysis and manage your account portfolio more effectively

Parent party Setup in Oracle TCA:

Party Relationship Management Process

D&B hierarchy contains hierarchical corporate relationships that D&B provides through the Enterprise Management global data product (GDP). To access this hierarchy, you select the D&B Hierarchy relationship type, which includes the following relationship phrase pairs:

• Parent Of and Subsidiary Of
• Headquarters Of and Division Of
• Domestic Ultimate Of and Domestic Subsidiary Of
• Global Ultimate Of and Global Subsidiary Of

 

 

Defining Credit Hierarchies                                          

To provide global credit limits that are shared by some or all entities within a complex, multinational organization, you can define credit relationships between parties using Oracle Trading Community Architecture Relationship Manager.
Relationship Manager lets you easily build, view, and edit relationships between entities. Using Relationship Manager, you can:

·         View a single party and all its relationships

·         Create new relationships and edit existing relationships

·         Focus on a particular portion of a hierarchy and edit the hierarchical structure

Using Relationship Manager, you assign to your entities an existing relationship type, such as Global Ultimate, or your own user-defined Credit Management relationship type. You then link the relationships to Credit Management by assigning the relationship type to the AR: Credit Hierarchy Type profile option.

The following profile options need to be set

 

• AR:Credit Hierarchy Type is set to D&B Hierarchy at responsibility and site level
• AR: Credit Limit Selection is set to Multi at the site level
• AR: Allow summary table refresh to Yes at the application (Receivables) level

 

Party level credit checking broadly involves the following, among others

                       

1)    Setting credit limits (transaction and overall) at the party level (setups in Credit Management, OM, AR). Oracle Credit Management will be used for this purpose.

2)    Creating parent-child (party) relationships in TCA (setups in TCA)

 

Assumptions

 

1)    It is assumed that the basic setups for credit checking are complete (e.g. credit check rule, attaching the credit check rule to OM transaction types, enabling credit check in the payment terms and profile class setups

 

First, we will discuss setting of credit limits at the party level. Credit limits at the customer site and customer account level can be set from the front end – in the customer standard form. Party level limits cannot be set using this procedure. They need to be set using the credit application-case folder-recommendations route in Credit Management.