C.2 Customizing the Subscriber Channel

The following sections provide information about customizing the Subscriber channel to synchronize additional attributes from the different Oracle modules with which the drivers synchronize attributes.

C.2.1 Modifying the IDM_DRIVER_S PL/SQL Script

The Oracle EBS system provides many built-in APIs for making certain changes to the user or employee data. You can use the IDM_DRIVER_S PL/SQL package to make these changes on the Subscriber channel. This package uses some of the Oracle EBS built-in APIs.

Table C-1 lists the APIs used for each module.

Table C-1 Oracle Module and EBS System APIs

Oracle Modules	Oracle EBS System APIs
User Management	fnd_user_pkg.createuser fnd_user_pkg.updateuser
HR Implementation	r_employee_api.create_employee hr_person_api.update_person hr_person_api.delete_person
TCA	hz_party_v2pub.create_person hz_party_v2pub.update_person hz_contact_point_v2pub.create_email_contact_point

To understand which attributes are supported by these APIs, use the SQL Developer tool and connect to the database where Oracle EBS system is installed. The API information is stored under the Packages panel on the left side of the screen. To view the APIs, expand the Packages panel.

NOTE:Currently, the query operations are supported on the FND_USER, PER_ALL_PEOPLE_F, and HZ_PARTIES tables.

Table C-2 lists the Identity Manager Schema attributes.

Table C-2 Schema Attributes

Condition	Action
Condition 1:The attribute is supported by one of the Oracle EBS system APIs and belongs to one of the FND_USER, PER_ALL_PEOPLE_F, or HZ_PARTIES tables.	There is no change required in the PL/SQL script. You can directly add the attribute to the driver schema and filter for extending it.
Condition 2:The attribute is supported by one of the Oracle EBS system APIs but does not belong to any of the FND_USER, PER_ALL_PEOPLE_F, or HZ_PARTIES tables.	Modify the query in the IDM_DRIVER_S package to specify the appropriate table name in the IF condition that starts with IF EVENT_NAME = TO_CHAR('oracle.apps.fnd.user.search') THEN statement.
Condition 3:The attribute is not supported by any of the Oracle EBS system APIs but belongs to one of the FND_USER, PER_ALL_PEOPLE_F, or HZ_PARTIES tables.	Determine which Oracle EBS system API is required to find the attribute, then add that API to the IDM_DRIVER_S PL/SQL package. You can use the EMPLOYEE_OPERATION and EXECUTE_EMPLOYEE_API functions as examples in the IDM_DRIVER_S package.
Condition 4:The attribute is neither supported by the Oracle EBS system APIs nor belongs to the FND_USER, PER_ALL_PEOPLE_F, or HZ_PARTIES tables.	Make changes as instructed for condition 2 and 3. A new Oracle EBS system API is needed to find the attribute and then modify the query to include it in the new table.

IMPORTANT:Restart the driver after making the required changes.

C.2.2 Verifying the Changes

Create a user in the Identity Vault with the recently added attributes and verify that the newly added attributes are synchronized to the EBS.
Perform a query operation for the recently added attributes and verify the response.

Example C-3 XML Code for the Subscriber Changes

<EBS_EVENT> 
               <EVENT_NAME>oracle.apps.fnd.user.insert</EVENT_NAME> 
               <DRIVER_TYPE>UM</DRIVER_TYPE> 
               <OBJECT TYPE="USER"> 
                  <x_user_name>IDM_TEST_SUB_996111</x_user_name> 
                  <x_description>IDM_TEST_SUB_998</x_description> 
                  <x_email_address>IDM_TEST_SUB_998@test.com</x_email_address> 
                  <x_fax>19999989</x_fax> 
               </OBJECT> 
            </EBS_EVENT>