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.

 

oracle skip lot functionality

Quality Skipping Inspection Control :

QIt is normally assumed that the SKIP Lot Functionality applies to items which are only Lot Controlled items. But its not the case. Skip lot functionality applies to all the items being received in Oracle Purchasing.

Lots in "Skip Lot Inspection" means receipt.

Some Pointers to make sure that the Skip lot functionality works as intended.

(1) For "Skip Lot Inspection" in the Collection Plan the Transaction description is not mandatory to use Inspection Transaction. Whenever a collection plan is associated to a Skip Lot Setup, it needn't necessarily have an Inspection / Receiving Transaction associated to it. For items having skiplot assigned, the skiplot is triggering the Inspection when required. For items without skiplot, the transactions and the triggers are checked and the plan will come based on that.



The Skip Lot triggering is set up at the Skip Lot/Sampling Criteria screen and it does not make use of the setup in Collection Plans Setup (Transaction Window).


 (2) Receipts have to be created only after setting up the skip lot inspection. For receipts created before the setup , the skip lot will not hold good.

(3) For Skip Lot Inspection the Receipts should be created one after the other and not in BULK.
 The receipt created should be processed completely before proceeding to create another receipt.

(4) In the Inventory Organization parameters "Quality Skipping Inspection Control" Check box should be checked for the Skip Lot Inspection to come into effect in that organization.

(5) We have to make sure that the Profile Option RCV: Processing Mode to On-line at site level and user level in System Administrator Profile options so that the transactions get completed before proceeding to do another transaction..
If the Receiving transactions for a particular receipt is not completed and we go ahead and raise a new Receipt then routing will be Inspection Required because the skip lot will not skip unless the receipt which you inspected is Accepted.
 So we need to make sure that the Receiving transaction is complete before we go to make a New receipt.
 The best way to ensure is to Change the profile option as given below.

(6) If we make a receipt which has to be inspected and we do not inspect the same and the next receipt we are about to make should get skipped according to skip plan, it will not get skipped as the skip plan will not get validated as the earlier receipt has not been inspected and accepted. This receipt also will have to be inspected.

(7) Number of Consecutive Lots accepted for Qualification mentioned in the Skip Lot Process Setup is the number of accepted lots to be accepted for the Skip lot process to become active. So for example if the Number of Consecutive lots accepted for Qualification is 2 then we have to receive 2 accepted lots and then only the Skip lot Process will become active.

(8) The sequence in the Skipping Parameters is to indicate the sequence in which the frequencies mentioned will come into effect. Suppose we have given a sequence of 10 with frequency of 1 out of 2 and no of rounds as 2 and in the second line we have given a sequence of 20 with frequency of 1 out of 5  and no of rounds as 5 then after the lots have been skipped 2 times as per sequence 10 it will move on to sequence 20 to skip lots as per the condition mentioned i.e. 1 out of 5. If we do not have any sequence mentioned after that then this particular condition (1 out of 5) will be active till a lot does not get rejected.

(9) We can see the status of the Skip lot code by going to Quality -> Inquiries -> Skip Lot Inquiry.
 It will open in a self service page.
(10) When doing the receipt we can see the Routing in the same form. If Routing is Inspection required after saving then we will have to do Inspection. If Routing is Standard Receipt then we need not do Inspection and it will be accepted in the Inventory i.e it will skipped. We need to make sure to see the Routing after we have saved the Receipt and not when we are viewing it.

(11) We have to make sure that we Associate the Skip Lot Process Code to the Item which has to be skipped in the Skip Lot/ Sampling Criteria Set up.
(12) If a Lot gets Rejected then the Skip Lot Process will Get halted and the Inspection Stage will return to Qualification from Skipping. We will have to get the qualification lots as per the condition mentioned in the Skipping parameters and then only the Skip lot Process will come into Effect again.

(13) The Profile Option QA:PO Inspection should be set to Oracle Quality.

DEMO TEST CASE
=================

Step 1 . Create a Purchased Goods Item X in the Master Items form by choosing the Purchased Item template.
Assign it to the required inventory Organization.
Navigation : Inventory -> Items -> Master Items

Step 2. Create a Collection Plan "CP"
 Navigation : Quality -> Setup -> Collection Plan
 Associate the required Collection Elements to the Plan
 Leave the Transaction Description in the Transaction Tab blank.

Step 3. Create a Skip lot process setup "SL"
 Navigation : Quality -> Set up -> Skip Lot Process Setup.
 Give the Number of Consecutive lots accepted for qualification as 1

Step 4. In skipping Parameters Associate the Collection Plan "CP" created above.
Give Frequency as 1 out of 2  Rounds 2
 (This means one out of every two lots submitted will get inspected )

Step 5. Associate the Skip Lot Process Code "SL" to the Item Created X above in the Skip Lot / Sampling Criteria Set up.
 Mention the Item name and click on Skip Lot Association and give the Skip Lot Process Code.

Step 6. Create a Purchase Order and approve it. Make sure that the Receiving Controls in Purchase Order is Inspection Required.

Step 7. If we see in Quality Inquiries -> Skip lot Inquiries and query for the organization and item we
 will get the skip lot code associated. Click on the Skip Lot Code and we will get to see the Inspection stage.
 The Inspection stage at this point will be Qualification.

Step 8. Create the first Receipt.
Routing will be Inspection Required.
 Go to Receiving Transaction and the destination type will be Receiving & status "Not Inspected"
 Do Inspection by clicking on the Inspect button.
 After Inspection the Destination type will change to Inspect.
 Re query the receipt in the Receiving Transaction and the destination type would have become Inventory.
 Move the items into sub inventory.

This completes the requirement of consecutive lots accepted for qualification. Now the Skip lot
 comes into effect.

Step 9.Create the second receipt
 Routing will be Inspection Required.
 Go to Receiving Transaction and the destination type will be Receiving & status "Not Inspected"
 Do Inspection by clicking on the Inspect button.
 After Inspection the Destination type will change to Inspect.
 Re query the receipt in the Receiving Transaction and the destination type would have become Inventory.
 Move the items into sub inventory.

Now if we check in Quality Inquiries -> Skip lot Inquiries and query for the organization and item
 The Inspection stage will have changed from Qualification to Skipping

Step 10. Create the third Receipt
 Routing will be Standard Receipt
 Go into Receiving Transaction and the destination type will be Inventory & status Not Inspected - Standard Receipt
 Move the items into sub inventory.

Step 11. Create the Fourth Receipt
 Routing will be Inspection Required.
 Go to Receiving Transaction and the destination type will be Receiving & status "Not Inspected"
 Do Inspection by clicking on the Inspect button.
 After Inspection the Destination type will change to Inspect.
 Re query the receipt in the Receiving Transaction and the destination type would have become Inventory.
 Move the items into sub inventory.

Step 12. Create the Fifth Receipt
 Routing will be Standard Receipt
 Go into Receiving Transaction and the destination type will be Inventory & status Not Inspected -  Standard Receipt
 Move the items into sub inventory.

Thus one out of 2 lots got skipped.

If the Rounds is given as 2 and no other sequence is mentioned then the system will continue to
 skip based on Skipping parameters