You can import supplier and buyer data (master data) in several formats via a maintenance plan.
The SupplierNumber, CorporateGroupId, and Location fields are currently used as the identifiers needed to qualify a unique match with a supplier in master data. Consequently, these fields must be included in the master data, and the master data must be imported before importing EHIX files with invoice definitions that include these fields (in order to be able to map them).
Importing master data updates existing master data, if any.
Invoice profiles must be closed before you import master data.
The master data file that you import can be in ANSI or Unicode format.
Unicode: if you want to import master data using a text file, for example, two prerequisites must be met:
The text file used to import the data must be in unicode format (in Notepad, for example, you would need to use the Save as function making sure the Encoding setting is set to Unicode and not ANSI).
The Oracle database must use a Unicode character set such as UTF8 or UTF16.
Use this query to see what character set is used in the database:
"Select value from SYS.NLS_DATABASE_PARAMETERS where PARAMETER = 'NLS_CHARACTERSET'"
If an ANSI character set is used, the database needs to be recreated using a unicode character set.
Click Finish to save the maintenance plan.
Import the master data at any time by running the maintenance plan (select the plan and click Start in the Maintenance dialog).
Running a maintenance plan creates two log files in the location specified in the maintenance plan:
Maintenance log file – Summarizes maintenance results.
Detailed log file – Contains database details intended for ReadSoft personnel. This file uses the same location and name, except the file name is appended with _detailed.
Any errors during the import are saved in the log files. Validation errors show the location of the error in the XML file. For example, ----- Validation error: (4,297) means that the error is on line 4, position 297.