Chat now with support
Chat with Support

Identity Manager 8.2.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
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

Linking E-Business Suite user accounts to imported employees

Employee data imported from Oracle E-Business Suite is mapped in the Employee table in the One Identity Manager database. The data source of the import is specified for every imported employee (ImportSource column). The E-Business Suite user accounts have a variety of properties with which these employees can be assigned.

To assign an imported employee to 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. Select the General tab.

  5. Select the HR person from the HR person menu.

    - OR -

    Select the customer from the Customer menu.

    - OR -

    Select the supplier from the Supplier menu.

  6. Save the changes.

If the imported employees are only connected to the user accounts through these columns, the user accounts are not managed by One Identity Manager. If an employee is deactivated or classified as a security risk, this change has no effect on the assigned user account. To utilize the possibilities available in One Identity Manager for the management of user accounts and employees for the imported employees, you can create connected user accounts. In these account, persons are connected to the user accounts by the EBSUser.UID_Person column.

HR people can also be connected to user accounts through automatic employee assignment. Standard search criteria are defined for this.

Table 19: Persons assigned to user accounts



Person (UID_Person)

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.

Every active person can be assigned.

Customer (UID_PersonCustomer)

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 person (UID_PersonEmployee)

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 (UID_PersonParty)

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 (UID_PersonSupplier)

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').

Detailed information about this topic
Related topics

Special features for the deletion of employees

If an employee is deleted in the One Identity Manager database who is connected to an E-Business Suite user account, the user account loses its reference to the employee after the deferred deletion has expired. If the user account is managed using an account definition, the behavior on deletion of the connected person is defined in the account definition. User accounts cannot be deleted in One Identity Manager. The person is physically deleted from the One Identity Manager database if all other prerequisites for deletion are in place. The user account is retained with the INACTIVE status.

For detailed information about deleting employees and user accounts, see the One Identity Manager Target System Base Module Administration Guide.

Related topics

Supported user account types

Different types of user accounts, such as default user accounts, administrative user accounts, service accounts, or privileged user accounts, can be mapped in One Identity Manager.

The following properties are used for mapping different user account types.

  • Identity

    The Identity property (IdentityType column) is used to describe the type of user account.

    Table 20: Identities of user accounts
    Identity Description Value of the IdentityType column

    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 admin identity

    User account with administrative permissions, used by one employee.


    Sponsored identity

    User account used for a specific purpose. For example, for training purposes.


    Shared identity

    User account with administrative permissions, used by several employees.


    Service identity

    Service account.


    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.

    The primary identity, the organizational identity, and the personalized admin identity are used for different user accounts, which can be used by the same actual employee to perform their different tasks within the company.

    To provide user accounts with a personalized admin identity or an organizational identity for an employee, you create subidentities for the employee. These subidentities are then linked to user accounts, enabling you to assign the required permissions to the different user accounts.

    User accounts with a sponsored identity, shared identity, or service identity are linked to pseudo employees that do not refer to a real employee. These pseudo employees are needed so that permissions can be inherited by the user accounts. When evaluating reports, attestations, or compliance checks, check whether pseudo employees need to be considered separately.

    For more information about mapping employee identities, see the One Identity Manager Identity Management Base Module Administration Guide.

  • Privileged user account

    Privileged user accounts are used to provide employees with additional privileges. This includes administrative user accounts or service accounts, for example. The user accounts are labeled with the Privileged user account property (IsPrivilegedAccount column).

Detailed information about this topic

Default user accounts

Normally, each employee obtains a default user account, which has the permissions they require for their regular work. The user accounts are linked to the employee. The effect of the link and the scope of the employee’s inherited properties on the user accounts can be configured through an account definition and its manage levels.

To create default user accounts through account definitions

  1. Create an account definition and assign the Unmanaged and Full managed manage levels.

  2. Specify the effect of temporarily or permanently disabling, deleting, or the security risk of an employee on its user accounts and group memberships for each manage level.

  3. Create a formatting rule for IT operating data.

    You use the mapping rule to define which rules are used to map IT operating data for user accounts and which default values are used if no IT operating data can be determined through a person's primary roles.

    The type of IT operating data required depends on the target system. The following setting are recommended for default user accounts:

    • In the mapping rule for the IsGroupAccount column, use the default value 1 and enable the Always use default value option.

    • In the mapping rule for the IdentityType column, use the default value Primary and enable Always use default value.

  4. Enter the effective IT operating data for the target system. Select the concrete target system under Effects on.

    Specify in the departments, cost centers, locations, or business roles that IT operating data should apply when you set up a user account.

  5. Assign the account definition to employees.

    When the account definition is assigned to an employee, a new user account is created through the inheritance mechanism and subsequent processing.

Related topics
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating