Chat now with support
Chat with Support

Identity Manager 8.1.5 - Administration Guide for Connecting to Oracle E-Business Suite

Mapping an Oracle E-Business Suite in One Identity Manager Synchronizing Oracle E-Business Suite
Setting up the initial synchronization Customizing the synchronization configuration Executing synchronization Tasks after a synchronization Troubleshooting
Managing E-Business Suite user accounts and employees Provision of login information Managing entitlement assignments Mapping of E-Business Suite objects in One Identity Manager Handling of E-Business Suite objects in the Web Portal Basic configuration data Users and permissions for synchronizing with Oracle E-Business Suite Default project templates for synchronizing an Oracle E-Business Suite Editing system objects Configuration parameters for managing Oracle E-Business Suite Example of a schema extension file About us

Project template for OIM data

For the synchronization of party person data of an Oracle E-Business Suite, you use the project template Oracle E-Business Suite OIM data. The template uses mappings for the following schema types.

Table 53: Mapping E-Business Suite schema types to tables in the One Identity Manager schema.
Schema type in the target system Table in the One Identity Manager Schema
HZParty Employee

Editing system objects

The following table describes permitted processing methods for Oracle E-Business Suite schema types.

Table 54: Methods available for editing schema types

Schema type

Read

Paste

Delete

Refresh

Application (ORA-Application)

 Yes No No No
Attribute (ORA-Attribute) Yes No No No
Language (ORA-Language) Yes No No No
Menu (ORA-Menu) Yes No No No

User accounts (ORA-Account)

 Yes Yes No Yes
Data group (ORA-Datagroup) Yes No No No
Data group unit (ORA-Datagroupunit) Yes No No No
Request group (ORA-Requestgroup) Yes No No No
Security group (ORA-SecurityGroup) Yes No No No

User account: assignment to security attribute (ORA-UserHasAttribute)

 Yes No No No
Responsibility/security combi (ORA-RESP) Yes No No No
Responsibility (ORA-Responsibility) Yes No No No
Responsibility: exclusion attribute (ORA-ResponsiExcludesAttribute) Yes No No No
Responsibility: excluded menu (ORA-ResponsiExcludesMenu) Yes No No No
Responsibility: assigned security attribute (ORA-ResponsiHasAttribute) Yes No No No

User account: assignment to responsibility(ORA-UserInRESPDirect)

 Yes

Yes

No

Yes

User account: assignment to responsibility(ORA-UserInRESPIndirect)

 Yes No No No

Person (APSupplierContacts)

 Yes No No No

Person (HZParty)

 Yes No No No

Person (HRPerson)

 Yes No No No

Person (HRPersonManager)

 Yes No No No

Location (HRLocations)

 Yes No No No

Secondary assignment: location (HRPersonSecondaryLocation)

 Yes No No No

Department (HROrganization)

Yes

No

No

No

Secondary assignment: department (HRPersonInOrganization)

Yes

No

No

No

Configuration parameters for managing Oracle E-Business Suite

The following configuration parameters are additionally available in One Identity Manager after the module has been installed.

Table 55: Configuration parameter

Configuration parameter

 Meaning

TargetSystem | EBS

Preprocessor relevant configuration parameter for controlling the database model components for the administration of the target system Oracle E-Business Suite. If the parameter is set, the target system components are available. Changes to this parameter require the database to be recompiled.

TargetSystem | EBS | Accounts

Parameter for configuring E-Business Suite user account data.

TargetSystem | EBS | Accounts |
InitialRandomPassword

This configuration parameter specifies whether a random generated password is issued when a new user account is added. The password must contain at least those character sets that are defined in the password policy.

TargetSystem | EBS | Accounts |
InitialRandomPassword | SendTo

Specifies to which employee the email with the random generated password should be sent (manager cost center/department/location/role, employee’s manager or XUserInserted). If no recipient can be found, the email is sent to the address stored in the configuration parameter TargetSystem | EBS | DefaultAddress.

TargetSystem | EBS | Accounts |
InitialRandomPassword | SendTo |
MailTemplateAccountName

This configuration parameter contains the name of the mail template sent to provide users with the login data for their user accounts. The Employee - new user account created mail template is used.

TargetSystem | EBS | Accounts |
InitialRandomPassword | SendTo |
MailTemplatePassword

This configuration parameter contains the name of the mail template sent to provide users with information about their initial password. The Employee - initial password for new user account mail template is used.

TargetSystem | EBS | Accounts |
MailTemplateDefaultValues

This configuration parameter contains the mail template used to send notifications if default IT operating data mapping values are used for automatically creating a user account. The Employee - new user account with default properties created mail template is used.

TargetSystem | EBS | Accounts |
PrivilegedAccount

This configuration parameter allows configuration of settings for privileged user accounts.

TargetSystem | EBS | Accounts |
PrivilegedAccount |
AccountName_Postfix

This configuration parameter contains the postfix for formatting login names for privileged user accounts.

TargetSystem | EBS | Accounts |
PrivilegedAccount |
AccountName_Prefix

This configuration parameter contains the prefix for formatting login names for privileged user accounts.

TargetSystem | EBS |
DBDeleteOnError

If this configuration parameter is set and a user account cannot be added to the target system, the object is deleted from the database afterward.

TargetSystem | EBS |
DefaultAddress

 The configuration parameter contains the recipient's default email address for sending notifications about actions in the target system.

TargetSystem | EBS |
MaxFullsyncDuration

This configuration parameter contains the maximum runtime for synchronization. No recalculation of group memberships by the DBQueue Processor can take place during this time. If the maximum runtime is exceeded, group membership are recalculated.

TargetSystem | EBS |
PersonAutoDefault

This configuration parameter specifies the mode for automatic employee assignment for user accounts added to the database outside synchronization.

TargetSystem | EBS |
PersonAutoDisabledAccounts

This configuration parameter specifies whether employees are automatically assigned to disabled user accounts. User accounts do not obtain an account definition.

TargetSystem | EBS |
PersonAutoFullsync

This configuration parameter specifies the mode for automatic employee assignment for user accounts added to or updated in the database through synchronization.

TargetSystem | EBS |
PersonExcludeList

List of all user accounts for which automatic employee assignment should not take place. Names are listed in a pipe (|) delimited list that is handled as a regular search pattern.

The following configuration parameters are also required.

Table 56: Additional configuration parameters

Configuration parameter

 Meaning

Common | Journal | Delete | BulkCount

Number of entries to be deleted in any operation.

Common | Journal | Delete | TotalCount

Total number of entries to be deleted in any processing run.

Common | Journal | LifeTime

Use this configuration parameter to specify the maximum amount of time (in days) that a system journal entry can be stored in the database. Older entries are deleted from the database.

Common | MailNotification | DefaultSender

Default email address (sender) for sending notifications.

DPR | Journal | LifeTime

This configuration parameter specifies the synchronization log's retention period (in days). Older logs are deleted from the database.

QER | CalculateRiskIndex

Preprocessor relevant configuration parameter controlling system components for calculating an employee's risk index. Changes to the parameter require recompiling the database.

If the parameter is enabled, values for the risk index can be entered and calculated.

QER | Person | TemporaryDeactivation

This configuration parameter specifies whether user accounts for an employee are locked if the employee is temporarily or permanently disabled.

QER | Person | UseCentralPassword

This configuration parameter specifies whether the employee's central password is used in the user accounts. The employee’s central password is automatically mapped to the employee’s user account in all permitted target systems. This excludes privileged user accounts, which are not updated.

QER | Person | UseCentralPassword |
PermanentStore

This configuration parameter controls the storage period for central passwords. If the configuration parameter is enabled, the central password is stored in the One Identity Manager database and is used for new users. If the configuration parameter is disabled, the central password is deleted from the One Identity Manager database following publishing to the existing user accounts. The central password is not available for new user accounts.

QER | Structures | Inherite |
GroupExclusion

Preprocessor-relevant configuration parameter for controlling the effectiveness of permissions. If this parameter is set, the assigned permissions can be reduced based on exclusion definitions. Changes to this parameter require the database to be recompiled.

Example of a schema extension file

<?xml version="1.0" encoding="utf-8" ?>

<EBSF12>

<ObjectNames>

<Object SchemaName="UserInRESPDirect" ParentSchemaName="ORA-RESPDirect" DisplayPattern="%vrtDistinguishedName%" IsReadOnly="false" UseDistinct="false">

<ObjectKey>

<Key Column="APPS.FND_USER_RESP_GROUPS_DIRECT.USER_ID" IsDNColumn="true" X500Abbreviation="UR" />

<Key Column="APPS.FND_USER_RESP_GROUPS_DIRECT.RESPONSIBILITY_ID" />

<Key Column="APPS.FND_USER_RESP_GROUPS_DIRECT.RESPONSIBILITY_APPLICATION_ID" />

<Key Column="APPS.FND_USER_RESP_GROUPS_DIRECT.SECURITY_GROUP_ID" />

<Key Column="APPLSYS.FND_APPLICATION.APPLICATION_ID" />

</ObjectKey>

<Tables>

<Table Name="FND_USER_RESP_GROUPS_DIRECT" Schema="APPS" APK="" USN="" WhereClause="" >

<PK Column="SECURITY_GROUP_ID" />

<PK Column="RESPONSIBILITY_ID" />

<PK Column="RESPONSIBILITY_APPLICATION_ID" />

<PK Column="USER_ID" />

</Table>

<Table Name="FND_APPLICATION" Schema="APPLSYS" APK="" USN="" WhereClause="" JoinParentColumn="APPS.FND_USER_RESP_GROUPS_DIRECT.RESPONSIBILITY_APPLICATION_ID" JoinChildColumn="APPLSYS.FND_APPLICATION.APPLICATION_ID" >

<PK Column="APPLSYS.FND_APPLICATION.APPLICATION_ID" />

</Table>

<Table Name="FND_USER" Schema="APPLSYS" APK="USER_ID" USN="LAST_UPDATE_DATE" WhereClause="" JoinParentColumn="APPS.FND_USER_RESP_GROUPS_DIRECT.USER_ID" JoinChildColumn="APPLSYS.FND_USER.USER_ID" >

<PK Column="USER_NAME" />

</Table>

<Table Name="FND_SECURITY_GROUPS" Schema="APPLSYS" APK="SECURITY_GROUP_ID" USN="LAST_UPDATE_DATE" WhereClause="" JoinParentColumn="APPS.FND_USER_RESP_GROUPS_DIRECT.SECURITY_GROUP_ID" JoinChildColumn="APPLSYS.FND_SECURITY_GROUPS.SECURITY_GROUP_ID" >

<PK Column="SECURITY_GROUP_ID" />

</Table>

<Table Name="FND_RESPONSIBILITY" Schema="APPLSYS" APK="" USN="" WhereClause="" JoinParentColumn="APPS.FND_USER_RESP_GROUPS_DIRECT.RESPONSIBILITY_ID, APPS.FND_USER_RESP_GROUPS_DIRECT.RESPONSIBILITY_APPLICATION_ID" JoinChildColumn="APPLSYS.FND_RESPONSIBILITY.RESPONSIBILITY_ID, APPLSYS.FND_RESPONSIBILITY.APPLICATION_ID" >

<PK Column="APPLSYS.FND_RESPONSIBILITY.RESPONSIBILITY_ID" />

<ParentTableFK Column="APPLSYS.FND_RESPONSIBILITY.APPLICATION_ID" ParentColumn="APPLSYS.FND_APPLICATION.APPLICATION_ID" />

</Table>

</Tables>

<Functions>

<Insert>

<Function Name="$ebsUserPackageName$.AddResp">

<Parameter Name="username" PropertyName="APPLSYS.FND_USER.USER_NAME" PropertyType="CHAR" Mandatory="TRUE" />

<Parameter Name="resp_app" PropertyName="APPLSYS.FND_APPLICATION.APPLICATION_SHORT_NAME" PropertyType="CHAR" Mandatory="TRUE" />

<Parameter Name="resp_key" PropertyName="APPLSYS.FND_RESPONSIBILITY.RESPONSIBILITY_KEY" PropertyType="CHAR" Mandatory="TRUE" />

<Parameter Name="security_group" PropertyName="APPLSYS.FND_SECURITY_GROUPS.SECURITY_GROUP_KEY" PropertyType="CHAR" Mandatory="TRUE" />

<Parameter Name="description" PropertyName="APPS.FND_USER_RESP_GROUPS_DIRECT.DESCRIPTION" PropertyType="CHAR" Mandatory="TRUE" NullValue ="null" />

<Parameter Name="start_date" PropertyName="APPS.FND_USER_RESP_GROUPS_DIRECT.START_DATE" PropertyType="DATE" Mandatory="TRUE" NullValue ="sysdate" />

<Parameter Name="end_date" PropertyName="APPS.FND_USER_RESP_GROUPS_DIRECT.END_DATE" PropertyType="DATE" Mandatory="TRUE" NullValue ="null" />

</Function>

</Insert>

<Update>

<Function Name="$ebsUserPackageName$.AddResp">

<Parameter Name="username" PropertyName="APPLSYS.FND_USER.USER_NAME" PropertyType="CHAR" Mandatory="TRUE" />

<Parameter Name="resp_app" PropertyName="APPLSYS.FND_APPLICATION.APPLICATION_SHORT_NAME" PropertyType="CHAR" Mandatory="TRUE" />

<Parameter Name="resp_key" PropertyName="APPLSYS.FND_RESPONSIBILITY.RESPONSIBILITY_KEY" PropertyType="CHAR" Mandatory="TRUE" />

<Parameter Name="security_group" PropertyName="APPLSYS.FND_SECURITY_GROUPS.SECURITY_GROUP_KEY" PropertyType="CHAR" Mandatory="TRUE" />

<Parameter Name="description" PropertyName="APPS.FND_USER_RESP_GROUPS_DIRECT.DESCRIPTION" PropertyType="CHAR" Mandatory="TRUE" NullValue ="null" />

<Parameter Name="start_date" PropertyName="APPS.FND_USER_RESP_GROUPS_DIRECT.START_DATE" PropertyType="DATE" Mandatory="TRUE" NullValue ="sysdate" />

<Parameter Name="end_date" PropertyName="APPS.FND_USER_RESP_GROUPS_DIRECT.END_DATE" PropertyType="DATE" Mandatory="TRUE" NullValue ="null" />

</Function>

</Update>

<Delete>

<Function Name="$ebsUserPackageName$.DelResp">

<Parameter Name="username" PropertyName="APPLSYS.FND_USER.USER_NAME" PropertyType="CHAR" Mandatory="TRUE" />

<Parameter Name="resp_app" PropertyName="APPLSYS.FND_APPLICATION.APPLICATION_SHORT_NAME" PropertyType="CHAR" Mandatory="TRUE" />

<Parameter Name="resp_key" PropertyName="APPLSYS.FND_RESPONSIBILITY.RESPONSIBILITY_KEY" PropertyType="CHAR" Mandatory="TRUE" />

<Parameter Name="security_group" PropertyName="APPLSYS.FND_SECURITY_GROUPS.SECURITY_GROUP_KEY" PropertyType="CHAR" Mandatory="TRUE" />

</Function>

</Delete>

</Functions>

</Object>

<\ObjectNames>

</EBSF12>

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating