Axioms of FIC

1. Only one credit category can be attached to classification rules.
2. We cannot attach classification rule to category.
3. Since the payment module does not include nonmonetary earnings, you can
export those earnings and set their statuses to Posted to ensure that the same
nonmonetary earnings are not included the next time that you export them.
4.

The sum of the target incentive weights does not have to equal 100. 5. You can specify multiple rate tables for an  incentive formula, provided that the • Effective dates of the rate table associations do not overlap

• Number of dimensions for the rate tables are the same

6. Typically, set up the formula to access quantifiable attributes through the

performance measure attainment, and non-quantifiable attributes directly from

the transaction or credit.

-------------------
7. Mappings can be shared across BUs.
8. Participants and Analysts cannot be imported together in same batch.
-------------------------------

9. We can same calender for different BUs but periods need to be opened for each BU.
--------
10. Lightweight Directory Access
Protocol (LDAP) user accounts for users of Oracle Fusion applications. OIM also
stores the definitions of abstract, job, and data roles and holds information about
roles provisioned to users.
=---
11
You must add the following Oracle Identity Management (OIM) roles to the IT
Security Manager job role's role hierarchy to enable the super user to create one
or more initial implementation users.
• Identity User Administrators
• Role Administrators
Additionally, you must assign the Xellerate Users organization to the IT Security
Manager role.
============

Tip
If you have multiple incentive compensation business units and want to
segregate all transactional data, include Business Unit as one of your qualifiers.
Do not include it as a qualifier if you plan to use cross business unit Crediting
and Rollup processes.

====================

12 .
You can only create a payment batch for a paygroup when there are no payment batches in unpaid status fro that particular paygroup.  Any unpaid paymentt batch either has to be paid or deleted before a new payment batch can be created for that paygroup.
===============================

13.

Note that instead of note :
How To Change Participant Type From Participant To Analyst (Doc ID 1586644.1)
There are no pre-requisites checking to run before doing this update (as soon script pass participant_type from ANALYST to PARTICIPANT

 ========================