This chapter provides an overview of the updates made to the software and documentation for release 18.104.22.168 of the SAP Employee Reconciliation connector.
The updates discussed in this chapter are divided into the following categories:
These include updates made to the connector software.
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 issues resolved in release 22.214.171.124:
|16941269||Wrong Manager Id was updated to the user||This issue has been resolved.|
|17047491||Update Manager Scheduled Task is not working||This issue has been resolved.|
|16989933||Update Manager Scheduled Task is throwinginvalidDataFormatException||This issue has been resolved.|
|16772203||Error loggers should be changed to Info logger for HRMS Listener||This issue has been resolved.|
|16793231||Install SAP ER 126.96.36.199 Connector Unable to edit GTC Connector||This issue has been resolved.|
|17211711||Update Manager scheduled task not working properly when the "update users with empty manger id only" parameter is set to YES||This issue has been resolved.|
|17796698||SAP ER connector creates multiple events for same change||This issue has been resolved.|
|19319985||SAPER connector 188.8.131.52.5 is not able to create deferred events for changes on identites which are not classified as HIRE, REHIRE or TERMINATE||This issue has been resolved.|
|23482998||SAPER connector fail to read it, when "Middle Name" field value is only 1 character long in the IDOC||This issue has been resolved.|
|23344445||SAP ER connector support for IDOC in XML format||This issue has been resolved.|
|23320012||SAP ER connector fails to connect to SAP Gateway and Message Server||This issue has been resolved.|
The following are issues resolved in release 184.108.40.206:
|13506280||When processing an IDoc file containing an empty date with "SAP HRMS User Recon", the date value is parsed as
||This issue has been resolved. The value of date field will be blank.|
|13538856||If you process an IDoc stream that contains more than one user and generates more than one reconciliation event of type Create, then the connector generates three new reconciliation events (Create User event).
The first reconciliation event successfully creates the OIM User. The other two reconciliation events fail with the following error message:
|This issue has been resolved.|
|13682760||If SAP reconciliation is processing an IDoc file containing two entries of InfoType E2P0016001, then the first entry contains the old value of an attribute. The second entry contains the new or updated value of the same attribute.
The connector parses only the first occurrence and consequently misses the attribute update.
|This issue has been resolved.|
|13716729||In the case of a future-dated hire, among the terminate and rehire events, the rehire event is ignored.||This issue has been resolved.|
|13803977||For future-dated reconciliation events (that is, deferred events) the data transformation feature is correctly triggered and run. However, the transformed values are not stored into the reconciliation event (reconciliation data).||This issue has been resolved.|
|14075167||Two SAP resources and therefore two SAP HRMS listener jobs are needed to connect Oracle Identity Manager.
The first job is labelled as SAP HRMS HRX listener and the second job as SAP HRMS ISX listener. When the jobs run, they are both tagged to same resource.
|This issue has been resolved.|
|14067912||A transformer in the connector transforms a field coming from SAP (SAPBUILDINGATTRIBUTE) into three attributes in Oracle Identity Manager. On the file delivery of all SAP entries, the transformer works correctly.
Using the SAP Listener job, events are received from the SAP system without the SAPBUILDINGATTRIBUTE field. In this case, the transformer delivers empty attributes that overwrite the three Oracle Identity Manager attributes.
|This issue has been resolved. The transformer job is skipped if the SAPBUILDINGATTRIBUTE field is not delivered.|
|14384664||In the case of re-hire events, the user is not enabled.||This issue has been resolved.|
|15934207||In Oracle Identity Manager 11g release, the SAP HRMS listener cannot be stopped or restarted.||This issue has been resolved.|
|15947444||Creation or updation of employee with Start Date in the future correctly generates a reconciliation event with Event Deferred status.
Information sent from the HR trusted source is visible, except the details related to Manager ID. The IDoc file generated and sent to Oracle Identity Manager contains the above field.
|This issue has been resolved.|
The following are issues resolved in release 220.127.116.11:
|12409614||User records were reconciled without populating the manager ID attribute values. However, the manager ID attribute values were reconciled after running the SAP HRMS Update Manager scheduled task.||This issue has been resolved. The manager ID attribute values are reconciled along with other user records. There is no need to run a separate scheduled task to reconcile manager ID attribute values.|
|12320106||When the SAP HRMS Listener scheduled task was run, the connector created a reference to the Oracle Identity Manager APIs. However, after the scheduled task run was completed, the reference to the Oracle Identity Manager APIs was neither closed nor refreshed automatically. Therefore, after the maximum timeout period was reached, the IBM Web Sphere Application server timed out this API reference.||This issue has been resolved. The Oracle Identity Manager APIs are re-initialized when running a scheduled task.|
|9407605||Trusted source reconciliation failed if a user is the manager of a parent organization.||This issue has been resolved. If the manager is not assigned to a user or if the user is a manager, then the connector checks for the manager of the parent organization and assigns the parent organization to the user.
If the parent organization does not have a manager or if the manager for the parent organization is same as the user ID, then the connector checks for the next organization hierarchy. This procedure continues till the manager is different from the user ID.
The following are software updates in release 18.104.22.168:
In earlier releases, if the hire event was future dated, then an OIM User was created and the Start Provisioning date was set to the future date in the Action infotype in the target system record. The manner in which future-dated hire events were processed could not be modified.
From this release onward, you can configure the manner in which the connector processes a future-dated hire event during reconciliation. To support this feature, the Create deferred event for future dated hire entry has been added to the Lookup.SAP.HRMS.Configuration lookup definition.
See the following sections in the connector guide for more information:
Depending on whether you want to reconcile values for the Start date and End date process form fields on Oracle Identity Manager, you set values for the OIM start date field and OIM end date field entries in the Lookup.SAP.HRMS.Configuration lookup definition.
See Section 1.5.5, "Setting the Start Date and End Date Values Based on the Life Cycle Events of the Target System User Record" of the connector guide for more information.
From this release onward, you can configure the connector to validate or transform user data that is brought into Oracle Identity Manager during reconciliation. To implement this feature, the Transform Lookup For Recon, Use Validation For Recon, Use Transformation For Recon, and Validation Lookup For Recon entries have been added to the Lookup.SAP.HRMS.Configuration lookup definition.
See the following sections in the connector guide for more information:
The following entries have been added to the Lookup.SAP.HRMS.Configuration lookup definition:
Create deferred event for future dated hire
Create deferred event for terminate event
Event End Date
OIM end date field
OIM start date field
Rehire Events Lookup
Transform Lookup For Recon
Use Transformation For Recon
Use Validation For Recon
Validation Lookup For Recon
See Section 2.3.1, "Setting Up the Lookup.SAP.HRMS.Configuration Lookup Definition in Oracle Identity Manager" in the connector guide for more information about each of these entries.
The following table lists issues resolved in release 22.214.171.124:
|9539918||During reconciliation, the value retrieved from the Org. Unit attribute of the target system was displayed in the Organization ID and Manager ID fields of the OIM User form.||This issue has been resolved. The value of the Organization ID field is retrieved from the Org. Unit target system attribute.
The value of the Manager ID field is determined and populated from the Lookup.SAP.HRMS.OrgManager lookup definition.
|10134695||A parsing error was encountered and reconciliation failed if IDoc contained the end-of-line (\n) character.||This issue has been resolved. If the connector encounters an end-of-line character in IDoc, then it trims this character and retrieves the necessary information from the target system.|
|10332786||Suppose a custom attribute is created on the target system and it has been made mandatory.
Reconciliation of a target system user record (containing a custom attribute that is mandatory) that was created as a future-dated event failed. In addition, several events for the infotype corresponding to the user record were created in Oracle Identity Manager.
|This issue has been resolved. However, reconciliation of a future-dated hire event still fails if the start date of the infotype containing the custom mandatory attribute is different than the start date of an infotype containing a standard mandatory attribute.|
The following is a software update in release 126.96.36.199:
From this release onward, the connector can be installed and used on Oracle Identity Manager 11g release 1 (11.1.1). Where applicable, instructions specific to this Oracle Identity Manager release have been added in the guide.
See Section 1.1, "Certified Components" for the full list of certified Oracle Identity Manager releases.
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.2, "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 are software updates in release 9.1.1:
|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 188.8.131.52, "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.
This is the first release of the Oracle Identity Manager Connector for SAP Employee Reconciliation. The following are software updates in release 9.1.0:
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.5.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.5.7, "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 184.108.40.206.
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:
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.6.2, "Reconciliation Rule" for more information.
The following sections discuss documentation-specific updates:
The following documentation-specific updates have been made for revision "18" of this guide:
Oracle Identity Manager 9.x content has been removed throughout the document.
The following rows in Table 1-1, "Certified Components" have been updated:
Section 1.2, "Usage Recommendation" has been modified to remove support to 9.0.4.x version of the connector with OIM 11g.
Information pertaining to procedures performed on the target system has been replaced with a high-level summary in the following sections:
Section "Determining the Release Number of the Connector" has been removed as it is related to OIM 9.x.
Section 220.127.116.11, "Creating a Backup of the Existing Common.jar File" has been modified.
The following rows have been added to Table 2-2, "Entries in the Lookup.SAP.HRMS.Configuration Lookup Definition":
Is Future Dated Event Handling Enabled
Is IDOC File Format in XML
Recon Rule Attribute Lookup
The description for the parameter "Gateway host" of Table 2-6, "IT Resource Parameters" has been updated.
Section 5.2.2, "Common SNC Errors" has been updated to include SNC issues.
Section 6, "Known Issues" has been updated to include bug 18668482.
The following documentation-specific updates have been made in revision "17" of release 18.104.22.168:
The "Oracle Identity Manager" row of Table 1-1, "Certified Components" has been updated.
Information specific to the Oracle Application Server has been removed from Section 22.214.171.124, "Installing the Security Package."
The following documentation-specific updates have been made in revision "16" of release 126.96.36.199:
The "Target system" row of Table 1-1, "Certified Components" has been updated.
Information specific to Oracle Application Server has been removed from Section 188.8.131.52, "Enabling Logging on Oracle Identity Manager Release 11.1.x."
Information specific to 184.108.40.206.x or later has been added to Step 2 of the procedure mentioned in Section 220.127.116.11, "Configuring the IT Resource."
The following documentation-specific updates have been made in revision "15" of release 18.104.22.168:
The "Oracle Identity Manager" row of Table 1-1, "Certified Components" has been modified.
Section 1.2, "Usage Recommendation" has been added.
The hyperlink for Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Manager in Section 2.3.13, "Creating an Authorization Policy" has been fixed.
The following are documentation-specific updates in release 22.214.171.124:
The "Oracle Identity Manager" row in Table 1-1, "Certified Components" has been modified.
Instructions specific to Oracle Identity Manager release 11.1.2.x have been added in the following sections:
A note has been added to Section 2.3.13, "Creating an Authorization Policy."
Steps 6.a and 6.b have been added to Section 126.96.36.199, "Downloading and Installing the SAP JCo."
The following are documentation-specific update in release 188.8.131.52:
In Chapter 4, "Extending the Functionality of the Connector," Table 4-1 the comments on creating a copy for the Resource Object and Process Definition connector objects have been updated.
In Chapter 6, "Known Issues," bug 13429841 has been added.
The following are documentation-specific updates in release 184.108.40.206:
In Section 3.5.1, "Configuring the Listener on Oracle Identity Manager," the name of the scheduled task that is used to transfer IDocs data from the Java object the parser was incorrectly documented. This has been corrected.
Information in Section 220.127.116.11, "Creating a Target System User Account for Connector Operations" has been modified.
There are no documentation-specific updates in this release.
In this release, minor changes and corrections have been made across the 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.