1. Understanding Import and Export Management for Sales and Fusion Service
  2. Import Your Source System Reference Data

Import Your Source System Reference Data

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

To import 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 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.

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

To import data into Oracle Applications Cloud, your CSV file must include some specific attributes that enable the import process to uniquely identify the records. The file import process uses the attribute values to automatically map your source data to the target object attributes in Oracle Applications Cloud.

The preferred options for uniquely identifying an object record are as follows:

  • Internal ID: If you're identifying a record that already exists in Oracle Applications Cloud, then you can use the internal ID of the record, a system-generated unique identifier Attributes with "id" in the attribute name are typically internal IDs. Use this option only if you're updating Source System References. You can determine the internal ID of a record by exporting Oracle Applications Cloud object data, or by doing a transactional database query. Using an internal ID typically provides better performance and reduces the import duration. For the Source System Reference object, the attributes are SourceSystemReferenceId and PartyId.

  • Public unique identifiers: If you're creating new records, then you can provide a user-friendly public unique identifier (attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for which you have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can use the Number attribute to identify the record. For the Source System Reference object, the attribute is PartyNumber.

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

Attribute

Description

Data Type

Data Length

Prerequisite Setup Task/ Import Validations

Creating a Source System Reference Record

Updating an Existing Source System Reference Record

SourceSystemReferenceId

Source system reference identifier. This is a primary key.

Number

18

No validation

Not required

If you can export the existing source system reference, provide this primary key to identify the record for further updates.

SourceSystem

Original source system name

Varchar

30

This has to be in HZ_ORIG_SYSTEMS_B with status "A".

Provide a valid value.

Not required

SourceSystemReferenceValue

Identifier in the original source system.

Varchar

255

No validation

Provide a valid value.

Not required

Status

Denotes either ACTIVE or INACTIVE

Varchar

1

No validation

Not required

Not required

StartDate

Start date of the source system reference in the source system.

Date

No validation

If you don't provide a value, it defaults to the current date.

Not required

EndDate

End date of the source system reference in the source system.

Date

No validation

If you don't provide a value, it defaults to 12/31/4712.

Not required

PartyId

Party identifier to which the source system reference is associated

Number

18

No validation

Provide one of the following :

  • PartyId

  • Party Number

  • A combination of Party Source System and Party Source System Reference Value

Not required

PartyNumber

Party's PUID to which the source system reference is associated

Varchar

30

No validation

Provide one of the following :

  • PartyId

  • Party Number

  • A combination of Party Source System and Party Source System Reference Value

Not required

Party Source System

Specifies the original source system of the party

Varchar

30

No validation

Provide one of the following :

  • PartyId

  • Party Number

  • A combination of Party Source System and Party Source System Reference Value

Not required

Party Source System Reference Value

Specifies the party's source system reference in the original source system

Varchar

255

No validation

Provide one of the following :

  • PartyId

  • Party Number

  • A combination of Party Source System and Party Source System Reference Value

Not required

You can view the 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: To directly update the SourceSystemReferenceValue field, you must use the SourceSystemReferenceId as the record identifier.

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:

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

  2. Select the 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 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.

You can use the following steps to inactivate origin system and origin system reference for the source system reference object:

  1. Create a source CSV file with values for the attributes SourceSystem, SourceSystemReferenceValue, and SourceSystemReferenceId. You can find the values for these attributes by exporting the source system reference object records using Export Management.

  2. Create an import activity using the object Source System and the import mode Delete records.

  3. If required, map the attributes on the Map Fields page, and submit the import activity.

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.

Related Topics