How do I import incentive transaction data?
You can use the import functionality to create or update Incentive Transaction records.
To import Incentive Transaction records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (.csv) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Target Object Attributes
To import your Incentive Transaction 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 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
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 option to uniquely identifying an object record is through the 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 Incentive Transactions. 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 Incentive Transaction object, the attributes are Transaction Number and Transaction Type.
Required Attributes and Validations for Incentive Transaction 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.
The following table lists the required attributes for importing new Incentive Transaction records, required attributes for updating Incentive Transaction records, prerequisite setup tasks for the attributes, and specific validations, if any, for Incentive Transaction import:
Attribute |
Description |
Data Type |
Data Length |
Prerequisite Setup Task/ Import Validations |
Creating a Incentive Transaction Record |
Updating an Existing Incentive Transaction Record |
---|---|---|---|---|---|---|
Business Unit |
Name of the business unit |
Varchar2 |
240 |
To find the business unit:
Note: You can export the results to a spreadsheet and use
this information to identify and assign the Business Unit values
to the data that you're preparing.
|
Required A value is required either for the Business Unit or the Business Unit Id. |
Required A value is required either for the Business Unit or the Business Unit Id. |
Business Unit ID |
Unique numeric identifier for the Oracle Fusion Incentive Compensation business unit. |
Number |
18 |
To find the business unit:
Note: You can export the results to a spreadsheet and use
this information to identify and assign the Business Unit ID values
to the data that you're preparing.
|
Required A value is required either for the Business Unit or the Business Unit Id. |
Required A value is required either for the Business Unit or the Business Unit Id. |
Event Date |
When the transaction triggers an incentive event associated with the row, for example, salespeople are compensated when an invoice is booked or an order is posted. |
Date |
The period must be open before you can collect the transaction into the application. |
Required |
Required |
|
Transaction Amount |
The transaction amount to be evaluated by the credit and earning processes. |
Number |
If providing a monetary amount, the amount should be in the currency of the source application. |
Required |
Required |
|
Transaction Number |
Unique transaction identifier used in the source application. The combination of Source Transaction Number and Transaction Type values must be unique, and is validated during the Collect Transactions process. |
Varchar2 |
30 |
Map an identifier that end users recognize and can search. For example, map your source invoice number and invoice line number to this field. |
Required |
Required |
Transaction Type |
Defines the type of the transaction. Predefined transaction types are CLAWBACK, CUSTOMER_SATISFACTION, GRP, INVOICE, ITD, MANUAL, ORDER, PAYMENT, and RAM_ADJUSTMENT. |
Varchar2 |
30 |
The value must be a valid lookup code for lookup type CN_TP_TRANSACTION_TYPE. To define your own transaction types:
|
Required |
Required |
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 Transaction 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 information. To create an import activity:
-
Go to
. -
Click Create Import Activity in the Manage Imports page.
-
In the Enter Import Options page, provide a name for the import activity, and select Incentive Transaction 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
You can review the import results by checking for the import activity in the Manage Import Activity page. A file import activity is said to be successful when its status displays as Completed. To check the status of the import activity, do as follows:
-
In the Navigator, under Tools, click Import Management.
-
On the Manage Imports page, search for the import activity that you created using one of the search criteria, such as status, name, object, and so on.
-
Check the Status column for the import activity. The import is successful if the status displays as Completed. The other valid values for the import activity status are Queued for import, Preparing data for import, Importing data, Completed with errors, and Unsuccessful.