Import Your Incentive Rule Assignment Data
You can use the import functionality to create, update, or delete Incentive Rule Assignment records.
You can import Incentive Rule Assignment 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 Incentive Rule Assignment 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 Incentive Rule Assignment 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 Incentive Rule Assignment 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 Incentive Rule Assignments 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 Incentive Rule Assignment attributes.
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 the public unique identifier to identify records. 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.
Required Attributes and Validations for Incentive Rule Assignment 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 Incentive Rule Assignment records, prerequisite setup tasks and specific validations, if any:
Attribute |
Description |
Prerequisite Setup Task/ Import Validations |
Creating an Incentive Rule Assignment record |
Updating an Existing Incentive Rule Assignment record |
Deleting an Existing Incentive Rule Assignment record |
---|---|---|---|---|---|
RuleNumber |
PUID of the rule |
The RuleNumber should exist. |
A value is required if the Name isn't provided. |
A value is required if the Name isn't provided. |
A value is required if the Name isn't provided. |
Name |
Name of the rule |
The Rule name should exist. |
A value is required if the RuleNumber isn't provided. |
A value is required if the RuleNumber isn't provided. |
A value is required if the RuleNumber isn't provided. |
AssignedObjectType |
The type of the object assigned to the rule. |
A value is required only when importing credit rules. Values can be INDIVIDUAL or PARTICIPANT_ON_TXN. |
Optional |
Optional |
Optional |
AssignedObjectId |
The unique internal identifier of the object being assigned to the rule.
|
This is validated against the corresponding object depending on the type of rule assignment being imported. |
Provide one of the following :
When the object is a participant, provide one among EmailAddress, HrPrimaryWorkerNumber, HrPersonNumber, or PartyNumber. |
Provide one of the following :
When the object is a participant, provide one among EmailAddress, HrPrimaryWorkerNumber, HrPersonNumber, or PartyNumber. |
Provide one of the following :
When the object is a participant, provide one among EmailAddress, HrPrimaryWorkerNumber, HrPersonNumber, or PartyNumber. |
AssignedObjectName |
The name of the object being assigned to the rule.
|
This validated against the corresponding object depending on the type of rule assignment being imported. |
Provide one of the following :
When the object is a participant, provide one among EmailAddress, HrPrimaryWorkerNumber, HrPersonNumber, or PartyNumber. |
Provide one of the following :
When the object is a participant, provide one among EmailAddress, HrPrimaryWorkerNumber, HrPersonNumber, or PartyNumber. |
Provide one of the following :
When the object is a participant, provide one among EmailAddress, HrPrimaryWorkerNumber, HrPersonNumber, or PartyNumber. |
EmailAddress |
The Email address of the participant. This is applicable only when the object is a participant. |
This is validated against the participant's email address. |
Provide one of the following :
EmailAddress, HrPrimaryWorkerNumber, HrPersonNumber, and PartyNumber are only valid for participants. |
Provide one of the following :
EmailAddress, HrPrimaryWorkerNumber, HrPersonNumber, and PartyNumber are only valid for participants. |
Provide one of the following :
EmailAddress, HrPrimaryWorkerNumber, HrPersonNumber, and PartyNumber are only valid for participants. |
HrPrimaryWorkerNumber |
The Worker Number of the participant. This is applicable only when the object is a participant. |
This is validated against the worker number of the participant. |
Provide one of the following :
EmailAddress, HrPrimaryWorkerNumber, HrPersonNumber, and PartyNumber are only valid for participants. |
Provide one of the following :
EmailAddress, HrPrimaryWorkerNumber, HrPersonNumber, and PartyNumber are only valid for participants. |
Provide one of the following :
EmailAddress, HrPrimaryWorkerNumber, HrPersonNumber, and PartyNumber are only valid for participants. |
HrPersonNumber |
The Person Number of the participant. This is applicable only when the object is a participant. |
This is validated against the person number of the participant. |
Provide one of the following :
When the object is a participant, provide one among EmailAddress, HrPrimaryWorkerNumber, HrPersonNumber, or PartyNumber. |
Provide one of the following :
When the object is a participant, provide one among EmailAddress, HrPrimaryWorkerNumber, HrPersonNumber, or PartyNumber. |
Provide one of the following :
When the object is a participant, provide one among EmailAddress, HrPrimaryWorkerNumber, HrPersonNumber, or PartyNumber. |
PartyNumber |
The Party Number of the participant. This is applicable only when the object is a participant. |
This is validated against the party number of the participant. |
Provide one of the following :
EmailAddress, HrPrimaryWorkerNumber, HrPersonNumber, and PartyNumber are only valid for participants. |
Provide one of the following :
EmailAddress, HrPrimaryWorkerNumber, HrPersonNumber, and PartyNumber are only valid for participants. |
Provide one of the following :
EmailAddress, HrPrimaryWorkerNumber, HrPersonNumber, and PartyNumber are only valid for participants. |
StartDate |
The start date of the rule assignment, if applicable to the object. |
None |
Required |
Required |
Required |
EndDate |
The end date of the rule assignment, if applicable to the object. |
None |
Optional |
Optional |
Optional |
SplitPct |
The percentage split applicable to the participant assigned to the credit rule. |
None |
Required for credit rules |
Optional |
Optional |
RevenueType |
The revenue type applicable to the participant assigned to the credit or rollup rule. |
The valid values are the lookup codes setup for lookup type CN_RS_REVENUE_TYPE. This is applicable only to credit and rollup rules. |
Required for credit and rollup rules. |
Optional |
Optional |
RollupFlag |
Option to determine if direct credit should be rolled up to every individual on parent rules. This is applicable only to credit rules. |
The valid values are Y and N. |
Required for credit rules |
Optional |
Optional |
SummaryFlag |
Option to determine if credits should be summarized. This is applicable to direct credit and rollup rules. |
The valid values are Y and N. |
Required for credit and rollup rules. |
Optional |
Optional |
GroupMemberCreditFlag |
Option to determine if the member gets credit from any direct credit receivers in group or child groups. This is applicable to rollup rules. |
The valid values are Y and N. |
Required for rollup and hierarchy analyst rules |
Optional |
Optional |
RuleAssignmentId |
The unique internal identifier of the Rule Assignment record. |
This validates against the Rule Assignment table when you update and delete incentive rule assignment records. |
Leave this blank. |
Optional |
Optional |
ActionCode |
Indicates explicitly the operation to be performed on a row:
|
The value can be blank, UPDATE, or DELETE. |
Optional Leave this blank. |
Required Enter the value as UPDATE. |
Required Enter the value as DELETE. |
Go to
, to see all the attributes of the Incentive Rule Assignment 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 Incentive Rule Assignment object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
Create the Import Activity
After you have the CSV file ready, create an import activity to import the Incentive Rule Assignment 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 Incentive Rule Assignment 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 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.