Oracle® Identity Manager Connector Guide for SAP Employee Reconciliation Release 9.1.2 E11210-05 |
|
Previous |
Next |
This chapter provides an overview of the updates made to the software and documentation for release 9.1.2 of the SAP Employee Reconciliation connector.
See Also: The earlier release of this guide for information about updates that were new for that release |
The updates discussed in this chapter are divided into the following categories:
These include updates made to the connector software.
Documentation-Specific Updates
These include major changes made to the connector documentation. These changes are not related to software updates.
The following sections discuss software updates:
The following are software updates in release 9.1.0:
Support for All Major (Including Effective-Dated) Lifecycle Events
Support for Synchronization of Employee Type Data and Reconciliation by Employee Type
Support for the Multiple Trusted Source Reconciliation Feature of Oracle Identity Manager
In earlier releases, the connector used custom BAPIs to exchange data with the target system. From this release onward, the connector supports IDoc-based reconciliation. Both tRFC and file ports can be used as modes of communication between the target system and Oracle Identity Manager.
The connector provides all the features required for setting up SAP HRMS a trusted (authoritative) source of identity data for Oracle Identity Manager.
The connector cannot be used for setting up SAP HRMS as a target resource. In other words, the connector does not support provisioning operations and target resource reconciliation with SAP HRMS. This is because person records maintained in SAP HRMS are not accounts that users can use to log in to the system and perform business-related work.
In earlier releases, you could not modify or add to the predefined attribute mapping between the target system and Oracle Identity Manager. Support for IDoc-based messaging ensures that you can customize attribute mappings.
See Section 4.1, "Removing or Adding Attributes for Reconciliation" for more information.
The connector can recognize and respond to both current-dated and effective-dated lifecycle events.
See Section 1.4.4, "Reconciliation of Effective-Dated Lifecycle Events" for more information.
From this release onward, a lookup definition is used to specify mappings between the following items:
Employee Group and Employee Subgroup combinations on the target system
Employee types defined in Oracle Identity Manager
You can use a predefined scheduled task to synchronize this lookup definition with changes made on the target system. You can also specify the employee type (that is, employee group and subgroup combination) for which you want to fetch data during reconciliation.
See the following sections for more information:
In earlier releases, the Manager ID attribute was not included in the predefined list of attributes reconciled from the target system. Data about employees' managers is reconciled from this release onward.
See Section 1.4.6, "Reconciliation of the Manager ID Attribute" for more information.
The connector now supports the multiple trusted source reconciliation feature of Oracle Identity Manager. See Oracle Identity Manager Design Console Guide for detailed information about multiple trusted source reconciliation.
From this release onward:
The required SAP JCo version is 3.0.
The minimum certified release of Oracle Identity Manager is release 9.1.0.2.
AIX is one of the certified operating systems for the host computer on which Oracle Identity Manager is installed.
See Section 1.1, "Certified Components" for the complete listing of certified components. See the following Oracle Technology Network page for information about certified components of Oracle Identity Manager:
http://www.oracle.com/technology/software/products/ias/files/idm_certification_101401.html
Note: The title of that section has been changed from "Certified Deployment Configurations" to "Certified Components." |
The reconciliation rule for trusted source reconciliation has been modified. See Section 1.5.2, "Reconciliation Rule" for more information.
The following are software updates in release 9.1.1:
Bug Number | Issue | Resolution |
---|---|---|
8722140 | If the manager of the organization was changed, then the change was not automatically propagated to the OIM User records of individuals who belonged to that organization. These records were updated only when other changes made to the corresponding person records on the target system were reconciled into Oracle Identity Manager. | This issue has been resolved. The Org Unit attribute has been added as a UDF in the OIM User record. In addition, the "SAP HRMS Unprocessed Manager Recon" scheduled task has been updated:
See Section 3.4.2.3, "Running the SAP HRMS Update Manager Scheduled Task" for more information about this scheduled task. The attribute mappings table in "Lookup.SAP.HRMS.AttributeMapping" now includes the Org Unit UDF. |
The following is a software update in release 9.1.2:
In earlier releases, the listener was used to reconcile manager ID values. This slowed down the incremental reconciliation process because manager ID reconciliation required the use of two lookup definitions in Oracle Identity Manager. From this release onward, manager ID reconciliation is no longer performed through the listener. Section 3.5.4, "Configuring Incremental Reconciliation of Manager ID Attribute Values" instructs you to use the SAP HRMS Update Manager scheduled task to perform incremental reconciliation of manager ID values.
The following sections discuss documentation-specific updates:
See Section 1.6, "Roadmap for Deploying and Using the Connector" for detailed information about the organization of content in this guide.
The following are documentation-specific updates in release 9.1.1:
In Table 1-1, the requirement for using Sun JVM if Oracle Identity Manager is running on Oracle WebLogic Server has been added.
In Section 2.3.1, "Setting Up the Lookup.SAP.HRMS.Configuration Lookup Definition in Oracle Identity Manager", the IT Resource Mapping entry has been added.
Section 2.3.2, "Verifying Segment Details in Lookup Definitions" has been added.
In this release, minor changes and corrections have been made across the guide.