Common errors for the Import and Update Participant Details process. (Doc ID 1940499.1)

Last updated on JUNE 13, 2024

Applies to:

Symptoms

This document lists some common errors with updating the participant detail using the import process.

See documentation Importing and Updating Participant Details into Incentive Compensation: Procedure

To download the latest Excel ICParticipantDetailsImportTemplate.xlsm, go to Doc ID 2785163.1 File-Based Data Import (FBDI) for Incentive Compensation

STEPS
1. Populate ICParticipantDetailsImportTemplate.xlsm template and generate the csv and zip file
2. Run Navigator > Participant Assignments > Import and Update Participant Details

Following are some common error messages with the Import and Update Participant Details process :

1.  There is not a valid BUSINESS UNIT on the file. Please verify.

2.  Participant was not found.
     OR
     Participant was not found.No Existing Currency Code value found for this Participant.

3.  Hold Payment Reason must match the lookup defined values.

4.  Country Code is not valid. 

5. The valid value for Import Mode is DELETE_PARTICIPANT. (on 18B and above Release)

6. The participant detail start and end dates must fall within the participant's active start date and active end date or compensation end date range.

Changes

The template has the following column descriptions :

Spreadsheet Column : Business Unit  ( Required )
Staging Column Name: BUSINESS_UNIT_ID  NUMBER ( 18,0)
The Oracle Incentive Compensation business unit name.
The name is used by the import process to derive the unique identifier ( BUSINESS_UNIT_ID) for the business unit.

Spreadsheet Column : Participant ( Required )
Staging Column Name: PARTICIPANT_ID   NUMBER (18,0)
The participant's name.
It is recommended that you provide one or more of the following attributes to uniquely identify the participant: E-Mail Address, Party ID, Party Number, Person Number
The participant name is used by the import process to derive the unique identifier for the Oracle Fusion Incentive Compensation participant ( PARTICIPANT_ID)

Spreadsheet Column: Hold Payment Reason
Staging Column Name: HOLD_REASON   VARCHAR2 (30 CHAR)
The lookup value meaning that represents the reason for the payment hold, such as leave, Dispute, and terminated.
If providing a value, the value must be a valid lookup meaning for lookup type, CN_HOLD_REASON_CODE.
The CN_HOLD_REASON_CODE lookup is available from the Setup and Maintenance, Manage Incentive Compensation Lookups task.

Spreadsheet Column: Start Date ( Required )
Staging Column Name: START_DATE   DATE
The date that the detail attribute record starts.
The date format must be : YYYY/MM/DD

Spreadsheet Column: End Date ( Required )
Staging Column Name: END_DATE DATE
The date that the detail attribute record end.
The date format must be : YYYY/MM/DD

Spreadsheet Column : Country Code
Staging Column Name: COUNTRY_CODE   VARCHAR2 (30 CHAR)
The ISO code ( 3 digit) or the Territory Code ( 2 digit)  that represents the participant's country.
You can view available ISO Country codes (ISO Territory Codes) and the Territory Codes using the Setup and Maintenance, Manage Territories task.

Spreadsheet Column : Participant Type
Staging Column Name : PARTICIPANT_TYPE
The lookup code which represents the new participant type value.
Use this column only when you are correcting the participant type.
This column is not meant to update a participant who later switches to an analyst, plan administrator, or compensation manager.
Value values are: ANALYST or PARTICIPANT ( value all in upper case )

Spreadsheet Column : Worker Number
Staging Column Name : HR_PRIMARY_WORKER_NUMBER
The employee identifier from the source application, such as Employee Number
Type is VARCHAR2 , 30 character field.

 

NOTE: See the template for other columns not listed here by clicking on the upper red triangle on top of each column name.

Spreadsheet Column : Delete Participant  (This has been added in 18B)

The import mode to delete participants created by mistake. Only provide the value DELETE_PARTICIPANT if you are sure you want to delete the participant.

A source file must be either for deleting participants or for updating participants. Do not mix both updates and deletes in the same source file.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.