This chapter provides an overview of the updates made to the software and documentation for the Oracle E-Business Employee Reconciliation connector in release 9.1.0.7.14.
The updates discussed in this chapter are divided into the following categories:
This section describes updates made to the connector software.
Documentation-Specific Updates
This section describes major changes made to this guide. These changes are not related to software updates.
The following sections discuss software updates:
The following are software updates in release 9.1.0.7.14:
The following are issues resolved in release 9.1.0.7.14:
| Bug Number | Issue | Resolution |
|---|---|---|
| 14097548 | Clearing the person ID field was not propagated to the target system. | This has been resolved as the employee id field has been cleared from EBS User properly. Additionally, other user fields like end_date etc have been cleared. |
| 14757090 | If EBS employee reconciliation found any data with an invalid PersonType, then reconciliation stopped and the scheduled task terminated. | This issue has been resolved. During reconciliation, when a record with an invalid person type is found, the scheduled job skips this record and continues with reconciling the next record.
The scheduled job skips the record with an invalid |
| 16169075 | User records were disabled based on the date stored in the EFFECTIVE_END_DATE target system column rather than the ACTUAL_TERMINATION_DATE target system column. | This issue has been resolved. The connector disables a user record based on the value in the ACTUAL_TERMINATION_DATE column of the target system. |
| 16933356 | Date comparisons done to set the status of a user record were in the dd-Mon-yy format instead of the dd-Mon-yyyy format. | This issue has been resolved. Date comparisons are done using the dd-Mon-yyyy format. |
The following are software updates in release 9.1.0.7:
From this release onward, support for validation and transformation are added for employee reconciliation.
The following are issues resolved in release 9.1.0.7:
| Bug Number | Issue | Resolution |
|---|---|---|
| 9707201 | Schedule task stops because the user data has got a special character | Reconciliation scheduled task will not stop now even if user fields contains special characters. It will log the warning message with exception stack trace details of that user record and continue the reconciliation for next user records. |
The following are software updates in release 9.1.0.5:
The following are issues resolved in release 9.1.0.5:
| Bug Number | Issue | Resolution |
|---|---|---|
| 9851274 | If an employee was marked as Terminated on the target system with a date less than or equal to SYSDATE and if SYSDATE was greater than the twentieth day of the month, then the corresponding account created in Oracle Identity Manager through reconciliation was not in the Disabled state. | This issue has been resolved. An account in the Disabled state on the target system is now created in the Disabled state on Oracle Identity Manager through reconciliation. |
The following is a software update in release 9.1.0.4:
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 are issues resolved in release 9.1.0.1:
| Bug Number | Issue | Resolution |
|---|---|---|
| 8969251 | The connector created reconciliation events even for records that had not changed since the last reconciliation run. | This issue has been resolved. The connector now creates reconciliation events only for records that are added or modified after the last reconciliation run. |
| 8919839 | An unhandled exception in the scheduled task kept the scheduled task running. | This issue has been resolved. The connector now handles all exceptions encountered during a reconciliation run. |
| 8916172 | In earlier releases, the connector required the ojdbc14.jar during reconciliation and provisioning. You had to copy this file from an external source. | This issue has been resolved. The connector can now work with the ojdbc6.jar file. This file is present in the application server installation directory.
As part of the fix implemented for this bug, the RECON_DATE_FORMAT and TO_CHAR_DATE_FORMAT entries have been introduced in the Lookup.EBS.ER.Configurations lookup definition. See the following sections for more information about the these entries: |
The following are software updates in release 9.1.0:
Support for Configurable Reconciliation Queries (Configurable Attribute Mappings)
Support for Target System Account with Minimum Permissions for Connector Operations
Support for the Multiple Trusted Source Reconciliation Feature of Oracle Identity Manager
Support for SSL Communication Between the Target System and Oracle Identity Manager
The connector provides all the features required to integrate Oracle E-Business HRMS as a trusted source of identity data. The connector can also be configured for use in scenarios in which Oracle E-Business HRMS is one of the trusted sources in the operating environment of the organization.
Note:
If you want to manage Oracle E-Business Suite as a target resource of Oracle Identity Manager, then use the Oracle E-Business User Management connector.From this release onward, the connector supports the following new target system versions and configurations:
Oracle E-Business Suite 11.5.10, 12.0.1 through 12.0.6 running on Oracle Real Application Clusters 10g and 11g
Oracle E-Business Suite 12.1.1 running on Oracle Database 10g or Oracle Database 11g, as either single database or Oracle RAC implementation
The Section 1.1, "Certified Components" section provides information about these and other certified software components that you can use with the connector.
Reconciliation involves running a SQL query on the target system database to fetch the required person records to Oracle Identity Manager. From this release onward, you can modify the predefined SQL queries that are shipped in the connector deployment package. You can also create and use your own SQL queries for reconciliation. This feature can also be used to extend the default set of attribute mappings for reconciliation.
See the following sections for more information:
Oracle E-Business HRMS allows effective-dating of lifecycle events. For example, a change in an employee's designation can be scheduled for the end of the current quarter. The connector can detect and respond to such effective-dated lifecycle events.
See Section 1.3, "Connector Architecture" for more information.
An organization can use Oracle E-Business HRMS to store different types of person records. Examples of person types include employees, part-time workers, contingent workers, and contractors. The connector can distinguish between records of different person types. In addition, you can add to or modify the predefined set of supported person types.
See the following sections for more information:
To meet the requirements of specific use cases, you might need to create multiple copies of the Oracle Identity Manager objects that constitute the connector. The connector can work with multiple instances of these objects.
See Section 4.8, "Configuring the Connector for Multiple Installations of the Target System" sections for more information.
You can create and use an Oracle E-Business HRMS user account with the minimum permissions required for connector operations.
See Section 2.1.2.1, "Creating a Target System User Account for Connector Operations" for more information.
The connector supports the connection pooling feature introduced in Oracle Identity Manager release 9.1.0.2. In earlier releases, a connection with the target system was established at the start of a reconciliation run and closed at the end of the reconciliation run. This approach was resource-intensive. With the introduction of connection pooling, multiple connections are established by Oracle Identity Manager and held in reserve for use by the connector.
See Section 1.4.9, "Connection Pooling" 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, you can configure SSL to secure communication between Oracle Identity Manager and the target system.
See Section 2.3.4, "Configuring Secure Communication Between the Target System and Oracle Identity Manager" for more information.
The following sections discuss documentation-specific updates:
The following documentation-specific updates have been made in revision "14" of release 9.1.0.7.14:
The "Oracle Identity Manager" and "Target system" rows of Table 1-1, "Certified Components" have been updated.
Section 2.3.7, "Displaying UDFs in Oracle Identity Manager 11.1.2 or Later" has been added.
A "Note" has been added to Step 2 of Section 4.1, "Adding New Attributes for Reconciliation".
The "java.sql.SQLException: Attempt to set a parameter name" row of Table 5-1, "Troubleshooting Errors Encountered During Connector Operations" has been updated.
An issue regarding task job for employee reconciliation from Oracle EBS has been added to Chapter 6, "Known Issues."
Screenshots pertaining to Oracle Identity Manager release 9.1.0.x have been removed from the document as they are no longer applicable.
The following documentation-specific update has been made in revision "13" of release 9.1.0.7.14:
The "Target system" row of Table 1-1, "Certified Components" has been updated.
The following documentation-specific updates have been made in revision "12" of release 9.1.0.7.14:
Section 3.3, "Uninstalling the Connector" has been added.
The "Oracle Identity Manager" and "Target system" rows of Table 1-1, "Certified Components" have been modified.
The following documentation-specific update has been made in revision "11" of release 9.1.0.7.14:
An issue related to eBusiness HRMS Delete Reconciliation has been added to Chapter 6, "Known Issues."
The following are documentation-specific updates in revision "10" of release 9.1.0.7:
The "Oracle Identity Manager" and "JDK" rows in Table 1-1, "Certified Components" have been modified.
Instructions specific to Oracle Identity Manager release 11.1.2.x have been added in the following sections:
There are no documentation-specific updates in this release.
The following is a documentation-specific update in release 9.1.0.4:
Section 2.1.1.3, "Creating a Backup of the Existing Common.jar File" has been added.
There are no documentation-specific updates in release 9.1.0.3.
The following are documentation-specific updates in release 9.1.0.1:
The "Copying Files to the Oracle Identity Manager Host Computer" section has been removed from Chapter 2, "Deploying the Connector."
The issue tracked by bug 8535215 was fixed in an earlier release. Therefore, the following item has been removed from Chapter 6, "Known Issues":
The "ORA-00904 OBJ_UDF_KEYFIELD is invalid" error is thrown during reconciliation. To resolve this problem, deselect the Sequence Recon check box on the Resource Objects form of the Design Console. See Oracle Identity Manager Design Console Guide for more information about this flag.
In Section 2.1.2.1, "Creating a Target System User Account for Connector Operations":
The information that you must enter while running the scripts to create a target system user account for connector operations has been updated.
The list of privileges granted to the target system user account for connector operations has been modified.
The following are documentation-specific updates in release 9.1.0:
Major changes have been made in the structure of guide for this release. The objective of these changes is to synchronize the guide with the software updates and to improve the usability of information provided by the guide.
See Section 1.6, "Roadmap for Deploying and Using the Connector" for detailed information about the organization of content in this guide.
In Section 1.1, "Certified Components," changes have been made to the "Target system" row.