Oracle Customer Hub (UCM) Master Data Management Reference > Configuring the List Import Function >

Scenarios for Using the List Import Function with Oracle Customer Hub (UCM)

This topic gives the following examples of how the List Import function might be used with Oracle Customer Hub (UCM). You might use Oracle Customer Hub (UCM) differently depending on your business model.

• Importing and Cleansing a Flat File
• Verifying Import and Updating Errors

Importing and Cleansing a Flat File

A branch of a national bank's account-opening system sends a flat file containing a given days' customer and account records for create and update. The originating system is a registered source system for Oracle Customer Hub.

A business user takes the flat file and imports it into Oracle Customer Hub, using the List Import function. Because this file is to be processed daily, the user automates the import process to take place at 1:00 AM every day. When defining the scheduling process, the user uploads the file (a delimited text file) and selects which type of data included in the document: data intended for the Account or Contact objects. This action displays a predefined set of Business Component fields that allows the user to map the columns of the file.

Because this file is in a standard layout, the user selects a predefined mapping and starts the import process. The import process validates the format of the data. After the import process is complete, an IT user runs a server task to run the Batch Data Management workflow in Oracle Customer Hub. All the updates are propagated on the base tables as defined by the survivorship rules predefined in Oracle Customer Hub. All imported records are also cleansed and matched.

Verifying Import and Updating Errors

Following the successful import of a flat file, a data steward at the same bank branch verifies the import process and identifies the records that were deleted because of errors during the Batch Data Management workflow. These views show all the records that have failed the import process with a status set to Incomplete. The data steward corrects the data from the UI and changes the type of the record from Incomplete to Batch. After the type of the record is changed to Batch, the Run UCM Batch button is enabled. The data steward clicks the Run UCM Batch button to rerun the UCM Batch Data Management process for the corrected records. For more information about importing flat files, see Importing and Cleansing a Flat File.