Oracle® Identity Manager Connector Guide for SAP CUA Release 9.1.0 E11209-02 |
|
Previous |
Next |
The following are known issues associated with this release of the connector:
Bug 7255088
Suppose a user is created in SAP CUA and then locked. When this user is reconciled for the first time, the user may not get locked because linking in Oracle Identity Manager takes place in an asynchronous manner. This user is successfully locked during the next reconciliation run.
Bug 7255110
Suppose a user is deleted from SAP CUA. During reconciliation, the user is deleted from Oracle Identity Manager. However, the Delete User function is also run and a message saying that the user does not exist on the target system is displayed. This message can be ignored.
Bug 7516300
On SAP CUA, you can create a lookup field entry with only the description (Decode) value and without a code (Code Key) value. After lookup field synchronization, the Code Key and Decode columns both contain the description (Decode) value.
Bug 7207232
Some Asian languages use multibyte character sets. If the character limit for fields on 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 point:
Suppose you can enter 50 characters of English in the User Last Name field of the target system. If you have configured the target system for the Japanese language, then you would not be able to enter more than 25 characters in the same field.
See Section 4.2, "Modifying Field Lengths on the Process Form" for information about working around this issue.
Bug 8470245
The connector cloning feature is not supported in this release of the connector.
Bug 8504052
The Test Connectivity option does not work for the IT resource that you create to hold information about the SoD engine.