A mapping contains a specific set of attributes from the source file and the corresponding interface table attributes that they are to be loaded into. You can save mappings and use them for loading files from any source system.

By default, all the source attributes are displayed, in the order that they appear in the source file. You have these options for providing the target attribute mapping to use.

• Manually select the target interface table attribute for each source attribute. The available target attributes depend on the party and information type selected for the file load definition. See: Defining File Loads.

• Automatically map the attributes. If a target attribute has the same name as a source attribute, those attributes will be automatically mapped. It is possible that not all source attributes have a match. You can still manually select target attributes after the automatic map.

  Note: You can automatically map attributes only if your source file has a file header.

• Select an existing saved mapping. After you click Go, the target attributes that match your source file are displayed next to the corresponding source attribute.

  For example, the existing mapping has source attribute Name mapping to target attribute First Name, and source attribute Surname to target attribute Last Name. If your source file has attribute Surname, but not Name, then only target attribute Last Name would appear next to Surname.

  You can still modify the mapping after using the existing mapping.

You can optionally save the mapping as it is in the table, no matter which method you used to create or modify it. Enter a new mapping name or an existing one to overwrite it with the mapping that you are saving. You can manage saved mappings. See: Managing Mappings.

Whatever mapping you have when you move on to the next step is the mapping used for this file load, whether or not you saved it. If you saved a mapping, modified it, and then clicked Next, the modified mapping is used for the file load.

Mapping Rules and Validations

Each target attribute can only be used once in a mapping. Other rules and validations for the mapping that you provide include:

• Persons

  • Person records must have either a first or last name. Include the First Name or Last Name target attributes in the mapping, or both.

  • Do not include the Organization Name attribute.

• Contacts

  • You must include these target attributes:

    • Both First Name and Last Name.

    • Organization Name.

  • Optionally include the Department Code, Department, Title, or Job Title attributes.

• Contact Points

  You must include the Contact Method Type target attribute. This table describes additional mandatory target attributes, based on the contact method type.

  Contact Method Type	Mandatory Target Attribute
  Phone or Fax	Either Telephone Number or Primary Phone
  E-Mail	Email Address
  Web	URL

Managing Mappings

Saved mappings can be used for file loads from any source. See: Providing Mappings. Access mapping management from the File Loads page. See: File Loads Process.

To manage mappings, you can:

• Rename mappings. All mappings that you create and update must have unique names.

• View source-to-target attribute mappings in the details.

• Delete mappings.