Import Your Hub Source System Reference Data

You can use Import Management to create or update Hub Source System Reference records.

To import Hub Source System Reference records, perform the following tasks:

1. Map your source data to Oracle Applications Cloud object attributes.

2. Create source Comma Separated Values (CSV) file for import.

3. Create the import activity.

4. Review the import results.

How You Map Your Source Data to Target Object Attributes

To import your Hub Source System Reference 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 hub source system reference records or are updating hub source system reference records that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Hub Source System Reference 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 Hub Source System Reference records, required attributes for updating Hub Source System Reference records, prerequisite setup tasks for the attributes, and specific validations, if any, for Hub Source System Reference import:

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Hub Source System Reference Record	Updating an Existing Hub Source System Reference Record
OwnerEntityId	Internal identifier or primary key of a record that exists in the OSC table	If provided, it has to be an active primary key value from the table name provided for the OwnerEntityObject.	If you export data from the OSC table provided for the OwnerEntityObject, provide the primary key data to this attribute. If you can't provide this data, provide valid values for the combination of ExistingSourceSystem and ExistingSourceSystemReferenceValue.	Not required
StartDateActive	The date on which the hub source system reference becomes valid.	If provided, this date should be earlier than the end date. If you don't specify a date, this defaults to the current date.	Optional	Optional
EndDateActive	The date on which the hub source system reference is no longer valid.	If provided, this date should be later than the start date. If you don't specify a date, this defaults to 12/31/4712.	Optional	Optional
SourceSystem	Specifies the original source system name	This has to be present in the HZ_ORIG_SYSTEMS_B table with the status "A".	Provide a valid value.	Conditionally required. Provide one of the following: SourceSystemReferenceId A combination of SourceSystem, SourceSystemReference and OwnerEntityObject
SourceSystemReferenceValue	Specifies the original source system reference text or number in the original source system	No validation	Provide a valid value.	Conditionally required. Provide one of the following: SourceSystemReferenceId A combination of SourceSystem, SourceSystemReference and OwnerEntityObject
OwnerEntityObject	Specifies the OSC table in which the record exists	This has to be a valid lookup code in the lookup type ORA_ZCH_OWNER_ENTITY_OBJECT.	Provide a valid value.	Conditionally required. Provide one of the following: SourceSystemReferenceId A combination of SourceSystem, SourceSystemReference and OwnerEntityObject
SourceSystemReferenceId	Specifies the source system reference identifier. This is a primary key.	If provided, this has to be an active primary key value from the table HZ_ORIG_SYS_REFERENCES.	Not required	Conditionally required. Provide one of the following: SourceSystemReferenceId A combination of SourceSystem, SourceSystemReference and OwnerEntityObject
ExistingSourceSystem	Specifies the original source system name of data that exists in Oracle Engagement Cloud	This has to be present in the HZ_ORIG_SYSTEMS_B table with status "A".	If you can't provide the OwnerEntityID, provide a combination of ExistingSourceSystem and ExistingSourceSystemReferenceValue values. Export the Source System Reference repository to obtain this value.	Not required
ExistingSourceSystemReferenceValue	Specifies the original source system reference of data that exists in Oracle Engagement Cloud	No validation	If you can't provide the OwnerEntityID, provide a combination of ExistingSourceSystem and ExistingSourceSystemReferenceValue values. Export the Source System Reference repository to obtain this value.	Not required

You can view the Hub Source System Reference 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.

Note: A lookup type ORA_ZCH_OWNER_ENTITY_OBJECT is now available. You can now use this lookup without specifying the underlying physical tables, when providing input data in the CSV import file. When you migrate from File-Based Data Import to Optimized or Import Management, the underlying physical tables are secured to external parties.

Create the Source CSV File

You include the data that you want to import into CX 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:

1. Go to Navigator > Tools > Import Management > Import Objects.

2. Select the Hub Source System Reference object in the table and click Download.

You can now edit the downloaded file and provide valid values for the required attributes.

Note: For help in populating the CSV file and to avoid any issues in entering values, see the topic Potential Issues When Opening CSV Files With Excel in Related Topics section.

Create the Import Activity

After you have the CSV file ready, create an import activity to import the information. To create an import activity:

1. Go to Navigator > Tools > Import Management > Import Queue.

2. Click Create Import Activity in the Manage Imports page.

3. In the Enter Import Options page, provide a name for the import activity, and select Hub Source System Reference from the Object drop-down list.

4. Select the CSV file in the File Name field, and click Next.

5. You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

7. 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:

1. Go to Navigator > Tools > Import Management > Import Queue.

2. Click All Imports and search for the import activity that you created earlier.

3. 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.