Importing with External Keys

Learn how to communicate and import using external keys.

The following fields are used by Aurea CRM as unique fields for communication and importing:

  • FI_StaNo and FI_SerNo for companies
  • PE_StaNo and PE_SerNo for persons
  • OJ_StaNo and OJ_SerNo for properties (BTB only)

You can store additional "external" keys for companies, persons or properties in Aurea CRM that are used by external systems (e.g. accounting, mainframe) and use them as match-up criteria when importing data. The external key needs to be included in the import file to be able to identify the record. Any number of external keys can be assigned to each record.

You can define external key fields for other info areas in the data model (field type "ext.key"), see Aurea CRM Field Types in the CRM.core Administrator Guide.

Example: A company is maintained externally on 3 systems:

Company

System

Company number

European Inc.

AS 400

12

European Inc.

Accounting

511

European Inc.

Addresses

1100

The Ext. Company Key (XF) info area is used to match up the company imported data from the different systems with the company in Aurea CRM.

Company

FI_StaNo

FI_SerNo

Ext. System

Ext. Key

European Inc.

K

333

AS 400

12

European Inc.

K

333

Accounting

511

European Inc.

K

333

Addresses

1100

Note: External keys for persons and properties are stored in the Ext. Person Key (XP) and Ext. Property Key (XO) info areas. External keys for other info areas are stored in the Generic external key (XG) info area.

You can also enter an external key for catalog values. However, there is no info area for these external keys. You can therefore only define one external key, see Editing Variable Catalogs in the CRM.core Administrator Guide and Importing Catalog Values using External Keys.