1. Implementing Incentive Compensation
  2. Participant Import Mappings

Participant Import Mappings

Run All Participant Processes includes the Collect Participants and Participant Updates process which imports participants. It uses mappings to collect information about the participant from HCM or the trading party record.

The mapping is used when you first collect new participants and when collecting HCM updates to the person's work assignment. HCM must be on the same instance as Sales. Use the Manage Incentive Import Mappings task and choose the Participants import type.

The Participant region of the table is for the target participant and participant detail attributes. You select the source object and related attributes in the Source region. The list of source objects for participant is in the lookup type ORA_CN_PRTCPNT_MAP_SOURCE. Here's the provided list of source objects:

  • Person business unit
  • Person legal entity
  • Person position
  • Person work location
  • Person assignment
  • Person deparatment
  • Person job
  • Party

In the Verify Mapping region, you can select a person and click Run Test to view what the participant record will look like according to that person's work assignment. You can then make adjustments to the mapping if needed.

Attribute Mapping Rules

These rules apply to mapping attributes:

  • You can have only one mapping for each incentive compensation business unit.

  • A participant attribute can only be mapped to one source attribute.

  • If the source object supports flexfields defined within a context, then you can select the source flexfield attribute and context combination.

  • You can map attributes from the trading community party but keep in mind that the party record isn't date effective.

  • Person department general ledger accounts can be mapped as source attributes. However, when there is more than one set of accounts for a single department, the import process can't distinguish which information to select. In this case, the information isn't collected.

  • If the source object attribute is displayed as translated text but stored as a code, then the collection process will also collect the code.

  • If you have a participant attribute that can't be mapped, then you can populate the value using import or Web Service.

  • Mappings don't apply to the Import Participants task in the Participant Assignments work area.