1. Implementing Receivables Credit to Cash
  2. Data Import for Customers and Consumers

Data Import for Customers and Consumers

Use the File-Based Data Import process to import data from a CSV or XML file. You use the Data Import dashboard to monitor the import process and view reports and statistics.

You can choose to pause a File-Import batch, and then use the Data Import work area to configure data quality services for the batch. You can pause import activities if the HZ_IMP_PAUSE_FILE_IMPORT profile option is set to Yes. If the profile option is set to Yes, all submitted import activities are sent for administrator review and appear in the Data Import Batches Overview page.

Before importing data into the registry, you must decide if you want to use the data quality services and if so, how you want to configure the following data quality services:

  • Batch deduplication

  • Registry deduplication

  • Import to registry options

Batch Deduplication

Batch deduplication lets you identify and resolve duplicates within the imported batch.

To define batch deduplication, you must:

  • Select the match configuration rule you want to use to identify duplicates for each entity.

  • Specify the action to perform on the duplicate records within the batch. These actions are performed when the data is imported into the registry.

Registry Deduplication

Registry deduplication, similar to the batch deduplication, identifies duplicates between the data in the batch and the data in the registry before the data is imported into the registry. Similar to batch deduplication, with registry deduplication you select the match configuration and specify the action for duplication records.

Import to Registry Options

You use the Import to Registry options for these definitions:

  • Import Process mode: You can run the import process in preview mode, or load the data directly into the registry without previewing the data. In preview mode, you can review information, such as the number of duplicates, incorrect addresses in the batch data, the number of records that will be updated, and the number of records that will be created, before the data is actually imported. After reviewing the batch, you can decide to either import the batch, or amend the match configuration rules and actions and then rerun the batch to review the data again.

  • 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 incorrect.

  • Geography Validation: You can configure geography validation for data import by setting the HZ_IMP_DEFAULT_GEO_VALID_ADDRESS profile option to Yes. This validates the addresses in an import batch against geography data before importing them into the registry. Geography validation uses the geography-based address validation settings for each country, and imports only valid addresses.

    Note: Geography Name Referencing is run on all imported addresses regardless of this profile option setting.

  • Error Handling Limit: You can define how many process errors can be generated by the import batch process before the process terminates automatically.