Import Your Address Data
You can use the import functionality to create, update, or delete address records.
You can import address records using these steps:
-
Map your source data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
-
Create the source CSV file with the address data you want to import.
-
Kick off an import activity.
-
Check the import results to know if the import went well.
How You Map Your Source Data to Target Object Attributes
You import address data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.
Before you create the source data file, you should:
-
Know how your source data attributes map to the target object attributes in Oracle Applications Cloud. Match each column from the source file to an attribute in the address import object.
-
Finish all prerequisite steps, such as understanding what attributes are required for importing your objects.
-
Know how you can uniquely identify the records.
-
Check the target object attributes required in the CSV file for a successful import.
-
Ensure that you don't insert duplicate addresses while importing, to avoid redundant data.
If you want to import only a few records, then you can create a single CSV file for all address attributes. However if you want to import a large number of records, then you may decide to create multiple CSV files, one for each of the address child objects. Note that you must have imported the CSV file for address object successfully before trying to import the CSV files for the child objects. There are separate help topics describing how to import each of these child objects.
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 address or are updating address that have source system reference data, then provide the source system and source system reference values.
Required Attributes and Validations for Address 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 address records, prerequisite setup tasks and specific validations, if any:
Attribute |
Description |
Prerequisite Setup Task/ Import Validations |
Creating an Address record |
Updating an Existing Address record |
---|---|---|---|---|
PartyId |
The internal ID for the party (account, contact, household, or legal entity) to which the address belongs |
Identify the party ID value by exporting the relevant Party object such as Account, Contact, and so on. |
Conditionally Required Provide reference information to identify the existing party. The reference information can be:
|
Conditionally Required Provide reference information to identify the existing party. The reference information can be:
|
PartyNumber |
The code representing the source system for the party (account, contact, household, or legal entity) to which the address belongs. |
Identify the party ID value by exporting the relevant Party object such as Account, Contact, and so on. |
Conditionally Required Provide reference information to identify the existing party. The reference information can be:
|
Conditionally Required Provide reference information to identify the existing party. The reference information can be:
|
PartySourceSystem |
The code representing the source system for the party (account, contact, household, or legal entity) to which the address belongs. |
Identify the source system code that was used when you imported the party in a prior batch, or identify the source system code that you will use when importing the party in the same batch as this address |
Conditionally Required Provide reference information to identify the existing party. The reference information can be:
|
Conditionally Required Provide reference information to identify the existing party. The reference information can be:
|
PartySourceSystemReferenceValue |
The reference number or text representing the source system unique ID for the party (account, contact, household, or legal entity) to which the address belongs. |
Identify the reference value from your source system that was used when you imported the party in a prior batch, or identify the source system reference that you will use when importing the party in the same batch as this address. |
Conditionally Required Provide reference information to identify the existing party. The reference information can be:
|
Conditionally Required Provide reference information to identify the existing party. The reference information can be:
|
PrimaryFlag |
Identifies the primary address for the parent party record. |
Only one of the child records can be Primary. |
Optional |
Optional Pass Y to set Primary and N to reset an existing primary record. |
Status |
Indicates the current status of the address record. |
Not required Defaults to A (Active) |
Not required Defaults to A (Active) |
Optional Pass A to set the status to Active and I to set the status to Inactive. |
AddressId |
Unique identifier of the address record as primary key. |
No validation |
Not required |
Optional Either the AddressId or the AddressNumber can be passed. |
Country |
The country code component of the postal address. |
Identify valid country codes. |
Required |
Not required. |
LocationId |
The unique ID for the existing location record in the destination table. |
Identify the LOCATION_ID for an existing location by exporting the Location object. |
Optional |
Optional |
StartDateActive |
The date on which the address becomes valid. |
No validation |
This is a PUID for Address. If a value is passed, it will be imported. Otherwise, it will be auto-generated. |
The Address record can be updated by passing the Address Number. |
AddressNumber |
The address internal unique identifier that's internally generated when creating an address |
None |
This is a PUID for Address. If a value is passed, it will be imported. Otherwise, it will be auto-generated. |
The Address record can be updated by passing the Address Number. |
SourceSystem |
Name of external source system of the account, contact or household with which the address is associated. |
The source system should exist. You can manage source systems from the Manage Source Systems task. |
Optional If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values. |
Not required |
SourceSystemReferenceValue |
Specifies the identifier in the original source system |
Combination of Source System and Source System Reference Value should be unique. |
Optional If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values. |
Not required |
DoNotValidateFlag |
Option to indicate that a specific location isn't eligible for address validation |
No validation The values can be Y, N, or blank. |
Optional If you don't pass a value, set to No. |
Optional |
DunsNumberC |
A unique nine-digit identification number assigned to business entities by Dun and Bradstreet |
No validation |
Not required |
Not required |
PartySiteName |
User defined name for the site |
No validation |
Not required |
Not required |
Go to
, to see all the attributes of the address object. The page also lists attribute information like type, length, description, and so on.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 Address object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Providing the ZIP and Country Code values in the import CSV file will not automatically populate the State/County/City fields. Values for these fields should be separately provided in the import file.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the address information. To create an import activity:
-
Go to
. -
On the Manage Imports page, click Create Import Activity.
-
In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Address 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.