Import Your Assignment Rule Condition Data

You can use Import Management to create, update, or delete your assignment rule condition data.

You can import assignment rule condition records using these steps:

  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

You import assignment rule condition 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. 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 action plans or are updating action plans that have source system reference data, then provide the source system and source system reference values.

Review Required Attributes and Validations for Assignment Rule Condition 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.

This table lists the required attributes for assignment rule condition records, prerequisite setup tasks and specific validations, if any:

Review Required Attributes and Validations for Assignment Rule Condition Object

Attribute Description Prerequisite Setup Tasks or Import Validations Creating an Assignment Rule Condition Record Updating an Existing Assignment Rule Condition Record Deleting an Existing Assignment Rule Condition Record
RuleNumber The alternate identifier of the rule. None Required Not Required Not Required
RuleConditionNumber The alternate identifier of the rule condition. None Required Required Required
Object The object on which the condition rule will apply, such as Accounts, Opportunities, Lead, Deals, and Partner Account. The object must correspond to the given rule. Conditionally Required. Provide value if ObjectCode isn’t provided. Not Required Not Required
ObjectCode The code of the object. The object must correspond to the given rule. Conditionally Required. Provide value if ObjectCode isn’t provided. Not Required Not Required
ObjectAttributeName The attributes of the object. The attribute must correspond to the given object and registered in assignment metadata. Conditionally Required. Provide value if ObjectAttributeCode isn’t provided. Not Required Not Required
ObjectAttributeCode The code of the attributes of the objects. The attribute must correspond to the given object and registered in assignment metadata. Conditionally Required. Provide value if ObjectAttributeName isn’t provided. Not Required Not Required
Operator The operation values according to which the rules would apply such as Equals, Start with, and so on. The right operator must be passed on the attribute type. Validate the operator if matching object is passed. Required Not Required Not Required
Value The value to which the operation would match. None Conditionally Required. Not Mandatory in case the operator value is Is not blank or you're using Matching Object. Not Required Not Required

You can view the Assignment Rule Condition 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 Assignment Rule condition object in the table and click Download.

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 assignment rule condition 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 Assignment Rule Condition 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.