Oracle® Fusion Applications Customer Data Management Implementation Guide 11g Release 1 (11.1.1.5.0) Part Number E20433-01

Contents

Previous

Next

19 Common Customer Data Management Configuration: Define Trading Community Import

This chapter contains the following:

Data Import Objects: Explained

Defining the Import Process for Customers and Consumers: Points to Consider

Defining the Import Process for Customers and Consumers: Worked Example

Performing What-If Analysis on Data Import Batches: Worked Example

FAQs for Define Trading Community Import

Data Import Objects: Explained

Import objects are business entities that can be imported into the trading community model registry, for example, competitors, partners or resource teams. When you create a data import batch you should choose which business entity, or object, you are importing from the batch into the trading community model registry. For example, if you are responsible for resource management, you might want to import objects such as employee resource and resource team.

The import process flow will change according to which object you have selected. There are two import process flows for the following sets of objects:

1. Customer, reference, competitor, and custom party.

2. Employee resource, resource team, partner, and partner contact.

Customer, Reference, Competitor, and Custom Party

When you select these objects you will receive the option to check for duplicates within the import batch before the import, and the option to check for duplicates between the import batch and the trading community model registry before import. You will also be able to choose to preview data before it is imported, specify if addresses will be cleansed before import, and set the how many errors you will allow before the import is terminated.

Employee Resource, Resource Team, Partner, and Partner Contact

If you choose to import these objects you will not be able to deduplicate the batch or registry data. However, you will be able to choose to preview data before it is imported, specify if addresses will be cleansed before import, and set the how many errors you will allow before the import is terminated.

Defining the Import Process for Customers and Consumers: Points to Consider

You can use the import process to import a batch from the interface tables into the Trading Community Model registry. Before the data is imported into the registry you need to decide if you want to use the data quality services and if so, how you want to configure the data quality services. The data quality services are:

• Batch deduplication

• Registry deduplication

• Import to registry options

Batch Deduplication

Within the batch deduplication page you can decide if you want to identify and resolve duplicates within the batch that you are importing from the interface tables. If you want to check for duplicates you need to choose what match configuration rule you want to use to identify duplicates for each entity. Then you need to specify what action will be taken on the persons, organizations, and address duplicates found within the batch. Your specified actions will be performed on the batch before the data is imported into the registry.

Registry Deduplication

Similar to batch deduplication, registry deduplication identifies duplicates between the data in the batch and the data in the registry before the data is imported into the registry. If you want to check for duplicates you need to choose what match configuration rule you want to use to identify duplicates for each entity. Then you need to specify what action will be taken on the persons, organizations, and address duplicates found in the registry deduplication check. Your specified actions will be performed when you import the batch into the registry.

Import to Registry Options

When defining an import process you can decide whether to run the import process in preview mode, or you can choose to load the data directly into the registry without previewing the data. You can also choose to cleanse addresses prior to import, and you can define an error limit for the batch.

Import Process Mode

You can choose to run the import batch in preview mode, or you can skip the preview and load the data directly into the registry.

If you select to run the batch in preview mode you will be able to review information about the level of duplicates or incorrect addresses in the batch data before the data is actually imported. You will also be able to preview how many records will be created and how many records will be updated for each entity. You can then continue to import the batch, or you can amend the match configuration rules and actions to be taken on the identified duplicates and then rerun the batch to review the data again.

If you do not want to review the batch data before it is imported into the registry, then you can choose to skip the preview and allow the data to be loaded into the registry as soon as preprocessing is complete. You may prefer not to preview the batch data if the data source is frequently used.

Cleanse Addresses

You can choose to validate the addresses in the interface tables before importing them into the registry. The addresses are validated using an integrated third party service that verifies addresses and corrects them if they are incorrect.

Error Handling Limit

You can define how many process errors can be generated by the import batch process before the process terminates automatically. Error reports are generated by the application for you to review.

Defining the Import Process for Customers and Consumers: Worked Example

This example demonstrates how to create an import batch, and how to define the import process data quality services you want to use on the data prior to completing the import.

Create an import batch containing customer and consumer objects, load the import data into the interface tables, and configure the data import process so that you can view the batch in preview mode to check that all duplicate data are removed.

Creating an import batch

1. On the Data Import Batches Overview page, click on the Create Data Import Batch task located in the task pane.
2. On the Create Data Import Batch page, complete the fields as shown in this table:

   Field	Value
   Batch Name	Customer Import Batch
   Source System	Comma separated values
   Object	Customer and Consumer
   Estimated Number of Records	300
   Batch Description	Import of customer data

   
   
3. Click Save and Close
4. After creating the import batch, load your data into the interface tables using a standard ETL tool.

Defining the Data Import Process: Batch Deduplication

You want to check the batch for address, organization, and person duplicates; you also want to remove all of these duplicates from the batch.

1. On the Data Import Batches Overview page, highlight the Batch Name, but do not click on the Batch ID URL.
2. Click Actions and then click Import.
3. On the Define Import: Batch Deduplication page, select the Check for duplicates within the batch before import.
4. Complete the fields in the Select match configuration to determine duplicates within the import batch section, as shown in this table:

   Field	Value
   Addresses	Batch Location Basic Duplicate Identification
   Organizations	Batch Organization Basic Duplicate Identification
   Persons	Batch Person Basic Duplicate Identification

   
   
5. Complete the fields in the Override Default Actions section, as shown in this table:

   Field	Value
   Select Action for Persons and Organizations	Remove all duplicates
   Select Action for Addresses	Remove all duplicates

   
   
6. Click Next.

Defining the Data Import Process: Registry Deduplication

You want to check for address, organization, and person duplicates between the import batch and the Trading Community Model registry; you also do not want to import duplicate records.

1. On the Define Import: Registry Deduplication page, select the Check for duplicates between the import batch and the registry before import.
2. Complete the fields in the Select match configuration to determine duplicates within the import batch section, as shown in this table:

   Field	Value
   Addresses	Batch Location Basic Duplicate Identification
   Organizations	Batch Organization Basic Duplicate Identification
   Persons	Batch Person Basic Duplicate Identification

   
   
3. Complete the fields in the Override Default Actions section, as shown in this table:

   Field	Value
   Select Action for Persons and Organizations	Do not import duplicate records
   Select Action for Addresses	Do not import duplicate records

   
   
4. Click Next.

Defining the Data Import Process: Import to Registry

You want to configure the data import process so that you can view the batch in preview mode, enabling you to review the data after preprocessing. You also want to cleanse addresses before they are imported, and specify an error limit for the batch.

1. On the Define Import: Import to Registry page, select Run the batch in preview mode.
2. Select the Cleanse addresses before import.
3. In the Error Limit field, enter 200.
4. Click Submit.

Performing What-If Analysis on Data Import Batches: Worked Example

This example demonstrates how to perform What-If analysis on a data import batch that has been processed and has completed with a status of pre-import completed. The match configuration is redefined and the import process is resubmitted. The batch deduplication actions are then amended, and the batch import is completed.

The following table summarizes key decisions for this scenario.

Prerequisites

1. The data import batch has been created.
2. The data is uploaded into the interface tables.
3. The batch is imported and has completed with a status of pre-import completed.

Viewing the What-If Analysis

1. On the Data Import Batches Overview page, click on the batch ID URL.
2. On the Edit Data Import Batch page, review the summary and import process performance information. Click Import Details to open the What-If analysis page.
3. On the Import Process Details page, click the Batch Deduplication tab. Check that you are satisfied with the batch deduplication results.
4. On the Import Process Details page, click the Registry Deduplication tab. Check that you are satisfied with the registry deduplication results.
5. On the Import Process Details page, click the Address Cleansing tab. Check that you are satisfied with the address cleansing results.

Redefining the Match Configuration and Resubmitting the Import Process

The results of the batch and registry deduplication are not as expected and so the match configurations need to be redefined.

1. On the Import Process Details page, click Cancel.
2. On the Data Import Batches Overview page, click on the batch name. Click Actions and then click Import.
3. On the Define Import: Batch Deduplication page, choose a different match configuration for the organizations entity. Click Next.
4. On the Define Import: Registry Deduplication page, choose a different match configuration for the persons entity. Click Next.
5. On the Define Import: Import Registry page, click Submit

Changing the Action for Duplicates within the What-If Analysis

You want to view the What-If analysis for the new match configurations that you selected for the batch.

1. On the Data Import Batches Overview page, click on the batch ID URL.
2. On the Edit Data Import Batch page, review the summary and import process performance information. Click Import Details to open the What-If analysis page.
3. The new match configurations have produced satisfactory results, but you would like to change the actions that will be carried out on the duplicates. On the Import Process Details page, click the Registry Deduplication tab.
4. For the Persons and Organizations duplicates, choose Do not import duplicate records from the choice list.
5. For the possible duplicates for Addresses, choose Import duplicate records from the choice list.
6. Click Complete Import.

FAQs for Define Trading Community Import

Can I redefine the data import process for an already imported batch and reimport it?

Yes. If the data is still available in the interface tables and the batch status is Preimport Completed, Completed with Errors, Error, or Terminated when Error Limit Reached, then you can redefine the data import process and reimport the batch. However, once a batch has been successfully imported then you will not able to reimport the batch, even if the data is present in the interface tables.

How can I view the errors that occurred during preimport processing?

You can view any errors that occurred after submitting the batch for import by selecting the batch in the data import batches Overview page, and then click Report.

What happens if I purge a data import batch?

You permanently remove all records in the batch from the import interface tables. You should purge batches after the batch has been imported successfully and you are sure that the data in the interface tables is no longer required.

Purging the interface tables improves import performance. To archive imported data, you should copy the data to a set of custom tables.

Why can't I purge a data import batch?

Data import batches cannot be purged when they have a status of Processing. Purging a batch purges the batch data in the interface tables and so cannot be carried out while the batch is importing the data from the interface tables into the registry.

Why did I receive a message that the data enrichment process was declined?

The Oracle Fusion Trading Community Data Quality service may be unavailable, or you may not have the necessary licenses for the Data Quality service.

Can I try and import a batch again?

Yes. You can reimport a batch to correct validation errors if the import process status is either Preimport Completed, Completed With Errors, Error, or Terminated When Error Limit Reached.

Previous Next

Copyright ©  2011, Oracle and/or its affiliates. All rights reserved. Legal Notices

Contents Contact Us