4 Extending the Functionality of the Connector

This chapter describes procedures that you can perform to extend the functionality of the connector for addressing your specific business requirements.

This chapter discusses the following optional procedures:

See Section 4.1, "Removing or Adding Attributes for Reconciliation" if you want to modify the default field mappings between Oracle Identity Manager and the target system.
See Section 4.2, "Modifying Field Lengths on the OIM User Form" if you want to modify lengths of fields on the process form.
The Section 4.3, "Configuring the Connector for Multiple Installations of the Target System" describes the procedure to configure the connector for multiple installations of the target system.

4.1 Removing or Adding Attributes for Reconciliation

The Lookup.SAP.HRMS.AttributeMapping lookup definition holds the default attribute mappings. Table 1-5 lists the default attribute mappings stored in this lookup definition.

If required, you can modify or add to this predefined set of attribute mappings. This section discusses the following procedures:

Section 4.1.1, "Removing Attributes"
Section 4.1.2, "Adding Attributes"

4.1.1 Removing Attributes

Before you begin connector operations, you can remove any attribute that is not marked as a mandatory attribute in Table 1-5.

Note:

If required, you can also reconfigure segment filtering to exclude the segment containing the attribute that you remove. See Section 2.3.3.10, "Configuring Segment Filtering" for instructions.

To remove an attribute mapping:

Log in to the Design Console.
Expand Administration, and double-click Lookup Definition.
Search for and open the Lookup.SAP.HRMS.AttributeMapping lookup definition.
Click the row that you want to delete.
Click Delete.
Click the Save icon.

4.1.2 Adding Attributes

To add an attribute mapping:

Note:

The names of attributes are case-sensitive. The spelling and case (uppercase and lowercase) of an attribute must be the same in all the connector objects. See existing attribute mappings for examples.

Determine the Decode column entry for the attribute that you want to add.

To determine the Decode column entry:
1. Run transaction WE60.
2. Specify the basic IDoc type, for example, HRMD_A05.
3. If you have extended the basic type, then enter the name of the extension in the Enhancement field.
4. Select the Data rec.
5. The segment name, subtype, attribute name, start position, and end position are indicated in Figure 4-1.
  
  Figure 4-1 Attribute Details for Attribute Mapping
  
  Description of "Figure 4-1 Attribute Details for Attribute Mapping"
Add the attribute mapping in the Lookup.SAP.HRMS.AttributeMapping lookup definition as follows:
1. Log in to the Design Console.
2. Expand Administration, and double-click Lookup Definition.
3. Search for and open the Lookup.SAP.HRMS.AttributeMapping lookup definition.
4. Click Add.
  
  An empty row is added.
5. In the Code Key column of the new row, add the name of the OIM User attribute.
6. In the Decode column of the new row, add the entry that you determine for the target system attribute by performing Step 1.
  
  The Decode column entry for an attribute is in the following format:
```
SEGMENT_NAME;SUB_TYPE;SAP_ATTRIBUTE_NAME;START_POSITION;END_POSITION;[Text|Date]
```
  Note:
  Append Date at the end of the Decode value if the attribute holds date values. For all other data types, append Text at the end of the Decode value.
7. Click the Save icon.
Create a UDF for the field.
Add the attribute in the SAP HRMS Trusted Resource Object resource object.
In the SAP HRMS Trusted Resource Object process definition, add a reconciliation field mapping for the attribute.
On the target system, add the attribute to the segment filter that you create by performing the procedure described in Section 2.3.3.10, "Configuring Segment Filtering".

4.2 Modifying Field Lengths on the OIM User Form

You might want to modify the lengths of fields (attributes) on the OIM User form. For example, if you use the Japanese locale, then you might want to increase the lengths of OIM User form fields to accommodate multibyte data from the target system.

Note:

On mySAP ERP 2005 (ECC 6.0 running on WAS 7.0), the default length of the password field is 40 characters. The default length of the password field on the process form is 8 characters. If you are using mySAP ERP 2005, then you must increase the length of the password field on the OIM User form.

If you want to modify the length of a field on the OIM User form, then:

Log in to the Design Console.
Expand Administration, and double-click User Defined Field Definition.
Search for and open the Users form.
Modify the length of the required field.
Click the Save icon.

4.3 Configuring the Connector for Multiple Installations of the Target System

You may want to configure the connector for multiple installations of the target system. The following example illustrates this requirement:

The Tokyo, London, and New York offices of Example Multinational Inc. have their own installations of the target system. The company has recently installed Oracle Identity Manager, and they want to configure Oracle Identity Manager to link all the installations of the target system.

To meet the requirement posed by such a scenario, you must create and configure one IT resource for each installation of the target system.

The IT Resources form is in the Resource Management folder. The IT resource is created when you import the connector XML file. You can use this IT resource as the template for creating the remaining IT resources, of the same resource type.