Customer Interface lets you import and validate current or historical party and customer account information from other systems into your database.
Although Customer Interface imports both party and customer account information, it does so in a row-by-row manner and is slower than Bulk Import. However, you cannot use Bulk Import to import accounts; it can be used only to import parties. Therefore, for optimal performance, you should import parties using Bulk Import and use Customer Interface to import the associated accounts.
Note: Customer Interface runs independently and does not regard party level information already loaded into your database using Bulk Import. If you plan to use Customer Interface to import accounts that are associated with parties that have already been imported using Bulk Import, you must ensure that the source ID alone is unique across all source systems in the bulk import process. While Bulk Import requires source IDs to be unique only within an identified source system, customer interface does not recognize the source system and therefore requires that the source ID is unique across all sources systems. See:
Review the validation rules for each column of the Customer Interface tables. See: Customer Interface Validation Rules.
Perform all required set up steps preceding customer entry to ensure that values exist in your system for the columns of the Customer Interface tables that require predefined values. See: Customer Interface, Oracle Trading Community Architecture Reference Guide.
Write an import program to transfer customer information from an external system.
Validate customer addresses (if you are using US Sales Tax). See: Preparing for Import.
Set these profile options:
HZ: Gather Table Stats
HZ: Import Tax Details Using Customer Interface
HZ: Number of Workers Used by Customer Interface
HZ: Character Value to Indicate NULL During Import
HZ: Date Value (DD-MM-YYYY) to Indicate NULL During Import
HZ: Numeric Value to Indicate NULL During Import
See: .