Import Your Deal Registration Data

You can use import management to create or update Deal Registration records.

To import Deal Registration 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 Deal Registration 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 to uniquely identify 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 Deal Registrations. 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 Deal Registration object, the attribute is DealID.

  • 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 Deal Registration object, the attributes are:

    • AccountPartyNumber

    • ContactPartyNumber

    • OwnerPartyNumber

    • MatchedAccountPartyNumber

    • MatchedContactPartyNumber

    • OptyNumber

    • LeadNumber

    • PartnerCompanyNumber

    • ProgramEnrollmentNumber

    • DealNumber

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

Attribute

Description

Prerequisite Setup Task/ Import Validations

Creating a Deal Registration Record

Updating an Existing Deal Registration Record

AccountPartyNumber

The public unique identifier of account party on the deal registration

None

Required

Not required

ContactPartyNumber

The public unique identifier of contact party on the deal registration

None

Required

Not required

OwnerPartyNumber

The public unique identifier of owner party on the deal registration

None

Required

Not required

MatchedAccountPartyNumber

The public unique identifier of the matched account party on the deal registration

The deal registration should have the status "Approved".

Not required

Not required

MatchedContactPartyNumber

The public unique identifier of the matched contact party on the deal registration

The deal registration should have the status "Approved".

Not required

Not required

OptyNumber

The public unique identifier of the opportunity associated with the deal registration

The deal registration should have the status "Approved".

Not required

Not required

LeadNumber

The public unique identifier of the lead associated with the deal registration.

The deal registration should have an associated lead.

Not required

Not required

PartnerCompanyNumber

The unique identifier of the partner associated with the deal registration

None

Required

Not required

ProgramEnrollmentNumber

The unique identifier of the partner program enrollment in the context of the deal registration

The partner associated with the deal registration should be enrolled in a program.

Not required

Not required

DealID

The unique identifier of the deal registration.

None

Required

Required

DealNumber

The alternate identifier of the deal registration.

None

Required

Not required

You can view the Deal Registration 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:

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

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