How do I import contact point data?
You can use Import Management to create, update, or delete Contact Point records. You can use contact point to import customer contact information such emails, phone numbers, instant messenger address, web URL, and so on.
To import Contact Point records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Target Object Attributes
To import your Contact Point data into Oracle Applications Cloud, you need to populate a CSV file with your source data and map that source data to target object attributes in Oracle Applications Cloud.
You need to do the following before creating the CSV file for data import:
-
Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.
-
Ensure prerequisite setups are done, if applicable.
-
Understand your options for uniquely identifying the records.
-
Ensure parent records exist before importing child records.
-
Identify the target object attributes that are required in the CSV file for a successful import.
-
Ensure that you don't insert duplicate addresses while importing, to avoid redundant data.
Before You Start
You must do some basic checks before starting your import. For example, make sure that:
-
You have completed all the prerequisites for importing each attribute in your source data.
-
You have all parent records in place before importing child records.
Select a Unique Identifier for Your Records
All records must be unique in the application. You can use one of these to identify records:
-
Public unique identifiers: If you're creating records, then you can provide an easily understandable public unique identifier. These are, usually, denoted with 'Number' and visible in the business object's UI. PUID attributes are usually named <object> Number. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.
-
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new contacts or are updating contacts that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Contact Point Object
To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Ensure that you provide valid values for the attributes. This table lists the required attributes for importing new Contact Point records, required attributes for updating Contact Point records, prerequisite setup tasks for the attributes, and specific validations, if any, for Contact Point import:
Attribute |
Description |
Prerequisite Setup Task/ Import Validations |
Creating a Contact Point Record |
Updating an Existing Contact Point Record |
---|---|---|---|---|
ContactPointType |
Type of the contact point that's imported or updated |
This has to be a lookup_code in HZ_LOOKUPS with a lookup_type as COMMUNICATION_TYPE |
Provide one of these values:
|
Not required |
PartyId |
The internal ID for the party to which the contact point belongs |
No validation |
Provide one of the following :
|
Not required |
PartyNumber |
Specifies the PUID of the party |
No validation |
Provide one of the following :
|
Not required |
PartySourceSystem |
Specifies the original source system of the party |
This has to be in HZ_ORIG_SYSTEMS_B with the status "A". |
Provide one of the following :
|
Not required |
PartySourceSystemReferenceValue |
Specifies the party's source system reference in the original source system |
No validation |
Provide one of the following :
|
Not required |
SourceSystem |
Specifies the original source system name |
This has to be in HZ_ORIG_SYSTEMS_B with the status "A". |
Provide a valid value. |
Not required |
SourceSystemReferenceValue |
Specifies the identifier in the original source system |
No validation |
Provide a valid value. |
Not required |
ContactPointId |
System generated unique identifier. This is the primary key. |
No validation |
Not required |
If you can export the existing contact point, provide this primary key to identify the record for further updates. |
Status |
The status of the contact point. |
Not required This defaults to Y during creation. |
Not required |
To inactivate the existing active contact point record, provide the value "N". |
DoContactPreferenceFlag |
Add or update a contact's preference to receive e-mail or phone calls on the contact, account or household contact points. This attribute identifies if a contact has made a choice to be contacted. |
Don't set both this attribute and DoNotContactPreferenceFlag to Y simultaneously. Set either this attribute or DoNotContactPreferenceFlag to "Y". These are non-mandatory values. However, you can set both this attribute and DoNotContactPreferenceFlag to "N". |
Not required |
Not required |
DoNotContactPreferenceFlag |
Add or update a contact's preference not to receive e-mail or phone calls on the contact, account or household contact points. This attribute identifies if a contact has made no choice to be contacted. |
Don't set both this attribute and DoContactPreferenceFlag to Y simultaneously. Set either this attribute or DoContactPreferenceFlag to "Y". These are non-mandatory values. However, you can set both this attribute and DoContactPreferenceFlag to "N". |
Not required |
Not required |
DoNotContactReason |
Add or update the reason for a contact not to receive e-mail or phone calls on the contact, account or household contact points. |
This is used for DoNotContactPreferenceFlag. It is a non-mandatory field. |
Not required |
Not required |
You can view the Contact Point object along with all its child objects and attributes in the Manage Import Objects page of the Import Management flow. You can find attribute information like type, length, description, and so on, on this page.
Create the Source CSV File
You include the data that you want to import into Sales and Fusion Service in a source CSV file.
You can use the templates available in the Import Objects UI page to create the source CSV file. To download a template:
-
Go to
. -
Select the Contact Point object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the information. To create an import activity:
-
Go to
. -
Click Create Import Activity in the Manage Imports page.
-
In the Enter Import Options page, provide a name for the import activity, and select Contact Point from the Object drop-down list.
-
Select the CSV file in the File Name field, and click Next.
-
You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.
-
Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.
-
Review the import details on the Review and Submit page, and click Submit when you're ready.
Review the Import Results
Check if your import succeeded on the Manage Imports page. This page shows the status of all active, completed, and unsuccessful imports. To check the status of the import activity:
-
Go to
. -
Click All Imports and search for the import activity that you created earlier.
-
Check the Status column for the import activity. The import is successful if the status displays as Completed. You can drill down on the import activity to go to the Import Status page which provides the status details of the import activity.