サポートと今すぐチャット
サポートとのチャット

Identity Manager 9.1 - 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 initial synchronization of Oracle E-Business Suite Customizing the synchronization configuration Running synchronization Tasks following synchronization Troubleshooting Ignoring data error in synchronization Pausing handling of target system specific processes (Offline mode)
Managing E-Business Suite user accounts and employees 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 Configuration parameters for managing Oracle E-Business Suite Permissions required for synchronizing with Oracle E-Business Suite Default project templates for synchronizing an Oracle E-Business Suite Editing system objects Example of a schema extension file

E-Business Suite user accounts

You use One Identity Manager to manage Oracle E-Business Suite user accounts. A user can log on to the E-Business Suite using their Oracle E-Business Suite user account. The user retains all permissions and security groups assigned to the user account. In addition, user accounts can also be linked to employees who are managed in the Oracle E-Business Suite. Employee data from the Oracle E-Business Suite can be synchronized with the One Identity Manager database and linked to the user accounts.

A user account can be linked to an employee in One Identity Manager. You can also manage user accounts separately from employees.

NOTE: It is recommended to use account definitions to set up user accounts for company employees. In this case, some of the main data described in the following is mapped through templates from employee main data.

NOTE: If employees are to obtain their user accounts through account definitions, the employees must own a central E-Business Suite user account and obtain their IT operating data through assignment to a primary department, a primary location, or a primary cost center.

Related topics

Entering main data of E-Business Suite user accounts

To create a user account

  1. In the Manager, select the Oracle E-Business Suite > User accounts category.

  2. Click in the result list.

  3. On the main data form, edit the main data of the user account.

  4. Save the changes.

To edit main data of a user account

  1. In the Manager, select the Oracle E-Business Suite > User accounts category.

  2. Select the user account in the result list.

  3. Select the Change main data task.

  4. Edit the user account's resource data.

  5. Save the changes.
Detailed information about this topic

General main data of E-Business Suite user accounts

On the General tab, you enter the following main data:

Table 34: Additional main data of a user account

Property

Description

Employee

Employee that uses this user account. An employee is already entered if the user account was generated by an account definition. If you create the user account manually, you can select an employee in the menu. If you are using automatic employee assignment, an associated employee is found and added to the user account when you save the user account.

You can create a new employee for a user account with an identity of type Organizational identity, Personalized administrator identity, Sponsored identity, Shared identity, or Service identity. To do this, click next to the input field and enter the required employee main data. Which login data is required depends on the selected identity type.

NOTE: To enable working with identities for user accounts, the employees also need identities. You can only link user accounts to which an identity is assigned with employees who have this same identity.

No link to an employee required

Specifies whether the user account is intentionally not assigned an employee. The option is automatically set if a user account is included in the exclusion list for automatic employee assignment or a corresponding attestation is carried out. You can set the option manually. Enable the option if the user account does not need to be linked with an employee (for example, if several employees use the user account).

If attestation approves these user accounts, these user accounts will not be submitted for attestation in the future. In the Web Portal, user accounts that are not linked to an employee can be filtered according to various criteria.

Not linked to an employee

Indicates why the No link to an employee required option is enabled for this user account. Possible values:

  • By administrator: The option was set manually by the administrator.

  • By attestation: The user account was attested.

  • By exclusion criterion: The user account is not associated with an employee due to an exclusion criterion. For example, the user account is included in the exclude list for automatic employee assignment (configuration parameter PersonExcludeList).

Account definition

Account definition through which the user account was created.

Use the account definition to automatically fill user account main data and to specify a manage level for the user account. One Identity Manager finds the IT operating data of the assigned employee and enters it in the corresponding fields in the user account.

NOTE: The account definition cannot be changed once the user account has been saved.

NOTE: Use the user account's Remove account definition task to reset the user account to Linked status. This removes the account definition from both the user account and the employee. The user account remains but is not managed by the account definition anymore. The task only removes account definitions that are directly assigned (XOrigin=1).

Manage level

Manage level of the user account. Select a manage level from the menu. You can only specify the manage level can if you have also entered an account definition. All manage levels of the selected account definition are available in the menu.

User name

User account identifier. If you have assigned an account definition, this input field is filled automatically depending on the manage level.

Display name

User account display name. If you have assigned an account definition, this input field is filled automatically depending on the manage level.

Distinguished name

User account's distinguished name. This is formed based on a template from the user name and the distinguished name of the E-Business Suite system.

Email address

User account email address. If you have assigned an account definition, this input field is filled automatically depending on the manage level.

Fax

Fax number for the user account. If you have assigned an account definition, this input field is filled automatically depending on the manage level.

Status

Status of the user account. The status is set using a template. The value depends on the validity period of the user account (Active from (date), Active to (date)).

Permitted values are:

  • ACTIVE: The current date is within the validity period.

  • INACTIVE: The active-from date has not yet been reached or the active-to date is in the past.

Active from (date)

First date from which the user account is valid. If you have assigned an account definition, this input field is filled automatically depending on the manage level. The template is only effective if the user account has been created as a new user account.

Active to (date)

Last date from which the user account is valid If you have assigned an account definition, this input field is filled automatically depending on the manage level.

E-Business Suite system

E-Business Suite system in which you want to create the user account.

Customer

Reference to an employee who is managed as a customer.

Only employees from the E-Business Suite AR data source can be assigned (Person.ImportSource='EBSOIM').

HR employee

Reference to an employee in the Human Resources module of Oracle E-Business Suite.

Only employees from the E-Business Suite HR data source can be assigned (Person.ImportSource='EBSHR').

Party

Reference to an employee who is managed as a party.

An employee with the E-Business Suite AR data source can be assigned (Person.ImportSource='EBSOIM'). The assignment cannot be edited in One Identity Manager.

supplier

Reference to an employee who is managed as a supplier or a contact.

Only employees from the E-Business Suite AP data source can be assigned (Person.ImportSource='EBSCRM').

Risk index (calculated)

Maximum risk index value of all assigned entitlements. The property is only visible if the QER | CalculateRiskIndex configuration parameter is set. For more information, see the One Identity Manager Risk Assessment Administration Guide.

Category

Categories for the inheritance of E-Business Suite permissions to the user account. User accounts can selectively inherit permissions. To do this, entitlements, and user accounts are divided into categories.

Select one or more categories from the menu.

Description

Text field for additional explanation.

Identity

User account's identity type Permitted values are:

  • Primary identity: Employee's default user account.

  • Organizational identity: Secondary user account used for different roles in the organization, for example for subcontracts with other functional areas.

  • Personalized administrator identity: User account with administrative permissions, used by one employee.

  • Sponsored identity: User account to use for a specific purpose. Training, for example.

  • Shared identity: User account with administrative permissions, used by several employees. Assign all employees that use this user account.

  • Service identity: Service account.

Privileged user account.

Specifies whether this is a privileged user account.

Entitlements can be inherited

Specifies whether the user account can inherit E-Business Suite permissions through the employee. If this option is set, the user account inherits permissions through hierarchical roles or IT Shop requests.

  1. Example: An employee with an E-Business Suite user account is a member of a department. This department is assigned an E-Business Suite entitlement. If this option is set, the user account inherits this entitlement.

  2. Example: An employee with an E-Business Suite user account requests an E-Business Suite entitlement in the IT Shop. The request is approved and assigned. The user account only inherits this entitlement if this option is active.

User account is disabled

Specifies whether the user account is blocked from logging in to the E-Business Suite system. The status of the user account is transferred by template. To disable the user account, edit the last validity date of the user account.

Related topics

Login data for E-Business Suite user accounts

On the Login tab, enter the password for logging in to the Oracle E-Business Suite. Once you have saved the user account password with One Identity Manager it cannot be changed.

Table 35: Login data for a user account

Property

Description

Last login

Date of last login.

Password

Password for the user account. The employee’s central password can be mapped to the user account password. For more information about an employee’s central password, see One Identity Manager Identity Management Base Module Administration Guide.

If you use a random generated initial password for the user accounts, it is automatically entered when a user account is created.

The password is deleted from the database after publishing to the target system.

NOTE: One Identity Manager password policies are taken into account when a user password is being verified. Ensure that the password policy does not violate the target system's requirements.

Confirmation

Reconfirm password.

Logins (remaining)

Number of logins remaining until the password expires.

Password last changed

Data of last password change.

Logins

Permitted number of logins.

Days

Validity period for the password.

Related topics
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択