Oracle® Identity Manager Connector Guide for SAP Employee Reconciliation Release 9.0.3 Part Number B32369-02 |
|
|
View PDF |
The following are known issues associated with this release of the connector:
During SAP Employee Reconciliation configuration, you must decide which infotypes and which fields in infotypes need to be recorded. The connector tracks the following infotypes: 0000, 0001, 0002, 0006, and 0105. These infotypes must be recorded at the time of SAP HRMS configuration.
Suppose an employee account is created in SAP Employee Reconciliation and then reconciled to Oracle Identity Manager. Next, you provision a user on SAP User Management through Oracle Identity Manager. You then link the user account on SAP User Management with the SAP Employee Reconciliation employee account. During the next reconciliation run, the link between the employee account and the user account is reflected in Oracle Identity Manager.
However, if you do not reconcile the SAP Employee Reconciliation employee account to Oracle Identity Manager before you link the employee account and the user account on SAP, then the link will not be reflected in Oracle Identity Manager during the next reconciliation run.
Some Asian languages use multibyte character sets. If the character limit for the fields in the target system is specified in bytes, then the number of Asian-language characters that you can enter in a particular field may be less than the number of English-language characters that you can enter in the same field. The following example illustrates this limitation:
Suppose you can enter 50 characters of English in the User Last Name field of the target system. If you were using the Japanese language and if the character limit for the target system fields were specified in bytes, then you would not be able to enter more than 25 characters in the same field.
The connector uses the JCO API that supports JDK 1.4 to communicate with SAP Employee Reconciliation. Oracle Identity Manager supports the Oracle Containers for J2EE (OC4J) release that works on JDK 1.5. Therefore, the connector does not support OC4J.