In the Event Details page, from the Actions list, select Ad Hoc Link. The Ad Hoc

1-14 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager

1.2.6.3.1 For an Event With Multiple Matches When several users are matched to the event

data by the reconciliation engine, you must select the right user by using ad hoc or manual linking. For information about ad hoc linking, see Ad Hoc Linking on page 1-13. For information about manual linking, see Manual Linking on page 1-13.

1.2.6.3.2 For an Event With No Matches When no matches are found for an event, you

can either trigger an entity creation, or select an Oracle Identity Manager entity to link to the event. For information about how to select and Oracle Identity Manager entity to link to an event, see Ad Hoc Linking on page 1-13.

1.3 Updating Reconciliation Profiles Manually

This section describes creating and updating reconciliation profiles manually in the following sections: ■ Creating New Reconciliation Profiles ■ Updating Reconciliation Profiles ■ Changing the Profile Mode

1.3.1 Creating New Reconciliation Profiles

You might want to create reconciliation profiles in the following scenarios: ■ Creating Additional Nondefault Profiles for Reconciliation Based on Resource Objects ■ Creating New Profiles for Trusted Source Reconciliation

1.3.1.1 Creating Additional Nondefault Profiles for Reconciliation Based on Resource Objects

For reconciliation based on resource objects, the default profile name is the same as that of the resource object. For example, if resource object name is testresource, then the default profile name is also testresource. The corresponding reconciliation horizontal table name is RA_TESTRESOURCEobj_key. If the resource has Multi-Language Support MLS data, then the MLS table name is RA_MLS_TESTRESOURCEobj_key. If the resource object has child tables, then for each child form name, which is UD_xxx, there is a corresponding RA_UD_xx. Each of the tables has a corresponding entity definition XML file, which is stored as per platform documentation on MDS storage. Therefore, RA_MLS_TESTRESOURCEobj_key has an entity definition MDS document called dbRA_TESTRESOURCEobj_key.xml, which is stored as per platform documentation on MDS storage. To create nondefault profiles for reconciliation based on resource objects: Note: If you change the name of a resource object, the reconciliation profile needs to be regenerated by clicking the Create Reconciliation Profile button in the Object Reconciliation tab in Oracle Identity Manager Design Console.