Import Contacts, Accounts and Leads
The next step is to import data from Fusion Sales into Eloqua. By running the import, the identifiers (email, party ID, party number) for the accounts and contacts are updated in Eloqua.
The initial import ensures that the identifiers are shared between the two systems, and then later imports maintain the sync. You import accounts, contacts, and leads. Once you've set them up, for a given record type, a new import job starts, 15 minutes after the previous one has completed. This ensures that there are no multiple import jobs running in parallel for the same record.
If you include PrimaryAddress fields in your sync configurations you must include the Fusion Sales PrimaryAddress.AddressNumber field in your mappings. The address number field is required when you want to update contacts from Eloqua into Fusion Sales using an action and when you're mapping any address field. If you don't include the address number in the action mapping, the call will fail. To have the address number information in Eloqua you must store it in a custom field. You then take the value from Fusion Sales imports. In the case of mapping contacts, you map the address number along with the registry number that you take from Fusion Sales after the contact gets created in Fusion Sales.
See the Related Topics section for information on creating imports, and for creating default assets which will enable you to more quickly create your imports. Both topics are in the Oracle CX Sales Integration App User Guide.