Migrating Data Using Import Management

Use Import Management to migrate your legacy data to Oracle Permitting and Licensing.

Using Import Management, you can migrate data for planning applications, permits, and code enforcement.

Note: To specifically migrate only your parcel details, such as address, parcel and owner (APO) data, see the topic Migrating APO Data.

To import your data:

Map your source data to Oracle Applications Cloud object attributes. This tells the import process where to insert the information.
Create the source CSV file with the data you want to import.
Kick off an import activity.
Review and verify the imported data.

Map Your Source Data to Target Object Attributes

You import data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.

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 steps are complete, such as understanding what attributes are required for importing your objects.
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

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.
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 accounts or are updating accounts that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Activity Assignee Object

To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Make sure that you provide valid values for these attributes so that they pass import validations inbuilt into the application.

For a complete list of required attributes and validations for Oracle Permitting and Licensing objects, see Migrating Data to Oracle Permitting and Licensing Using Import Management.

Create Source CSV File

You include the data that you want to import into Oracle Permitting and Licensing 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 Navigator > Tools > Import Management > Import Objects.
Select the Activity Assignee object in the table and click Download.

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

Create Import Activity

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

Go to Navigator > Tools > Import Management > Import Queue.
Click Create Import Activity in the Manage Imports page.
In the Enter Import Options page, provide a name for the import activity, and select Activity Assignee from the Object drop-down list.
Select the CSV file in the File Name field, and click Next.
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 Import Results

Confirm that 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 Navigator > Tools > Import Management > Import Queue.
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 displayed is 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.

Delete Migrated Transactions

You can delete migrated transaction data for permits, planning applications and related objects. This allows a hard delete of imported transactions for each test run before converting to a production environment.

Note: To delete migrated transactions, ensure that you have a role with the assigned privilege Delete Public Sector Migrated Data (PSC_DELETE_MIGRATED_DATA_PRIV).

Access the process by selecting Common > Delete Migrated Transactions.
You can also access this process from the Process Monitor. See Using the Process Monitor.
On the Schedule tab, select the As soon as possible option to immediately add the process to the queue.
Select the Using a schedule option to schedule when you want the process to run.
(Optional) Turn on the Notify Me When This Process Ends switch to send yourself a notification when the process finishes.
Click Add on the Notification tab, and enter the recipient and conditions of the notification.
Click Submit.