4Implementation Users

This chapter contains the following:

Implementation Users

The initial user can perform all the necessary setup tasks. She can also perform security tasks, including resetting passwords and the granting of additional privileges to herself and to others. After you sign in the first time, you can create additional implementation users with the same broad setup privileges that Oracle provides to the initial user. If you prefer, you can restrict the privileges of these implementation users based on your own setup needs.

The setup or implementation users are typically different from the Oracle Applications Cloud application users. For example:

  • Setup users are usually not part of your Oracle Applications Cloud organization.

  • You don't assign them product-specific work or make it possible for them to view product-specific data.

You do, however, have to give them the necessary privileges they require to complete application setup. You provide these privileges through role assignment.

Your application includes several types of roles. A job role, such as the IT Security Manager role, corresponds to a specific job that a person does in the organization. An abstract role, such as the Employee role, corresponds to general categories of people in an organization. You assign both types of roles to users in the security console. For the setup users, these roles are:

  • Application Diagnostic Administrator

  • Application Implementation Consultant

  • Employee

  • IT Security Manager

Note: The Application Implementation Consultant role has unrestricted access to large amounts of data. Limit assignment of the Application Implementation Consultant abstract role to implementation users who perform a wide range of implementation tasks and move the setup data across environments. Use other administrator roles such as the Financials Applications Administrator for users required to perform specific implementation tasks.

There is nothing to stop you from providing the same setup permissions to users that are part of the organization, if you need to. Highly privileged implementation users are not the only users who can do setup. You can create administrative users who don't have such broad permissions, yet can configure product-specific structures and perform other related setup tasks.

Overview of ERP Implementation Users

As the service administrator for the Oracle ERP Cloud service, you're sent sign-in details when your environments are provisioned. This topic summarizes how to access the service for the first time and set up implementation users to perform the implementation. You must complete these steps before you release the environment to your implementation team.

Tip: Create implementation users in the test environment first. Migrate your implementation to the production environment only after you have validated it. With this approach, the implementation team can learn how to implement security before setting up application users in the production environment.

Signing In to the Oracle ERP Cloud Service

The service activation mail from Oracle provides the service URLs, user name, and temporary password for the test or production environment. Refer to the e-mail for the environment that you're setting up. The Identity Domain value is the environment name. For example, ERPA could be the production environment and ERPA-TEST could be the test environment.

Sign in to the test or production Oracle ERP Cloud service using the service home URL from the service activation mail. The URL ends with either AtkHomePageWelcome or FuseWelcome.

When you first sign in, use the password in the service activation mail. You're prompted to change the password and answer some challenge questions. Make a note of the new password. You must use it for subsequent access to the service.

Don't share your sign-in details with other users.

Creating Implementation Users

This table summarizes the process of creating implementation users and assigning roles to them.

Step Task or Activity Description

1

Create Implementation Users

The Application Implementation Consultant user may be your only implementation user. However, you can create the implementation users TechAdmin and ERPUser, and assign the required job roles to them if you need these implementation users and they don't already exist in your environment.

You don't associate named workers with these users at this time because your service isn't yet configured to onboard users in the integrated HCM core. As your implementation progresses, you may decide to replace these users or change their definitions.

2

Run User and Roles Synchronization Process

Run the process Retrieve Latest LDAP Changes to copy changes to users and their assigned roles to Oracle Fusion Human Capital Management (Oracle Fusion HCM).

3

Assign Security Profiles to Abstract Roles

Enable basic data access for the predefined Employee, Contingent Worker, and Line Manager abstract roles.

4

Create a Generic Role Mapping for the Roles

Enable the roles created in step 3 to be provisioned to implementation users.

5

Assign Abstract Role and Data Access to the Implementation User

Assign the implementation user with the roles that enable functional implementation to proceed.

6

Verify Implementation User Access

Confirm that the implementation user can access the functions enabled by the assigned roles.

Once these steps are complete, you're recommended to reset the service administrator sign-in details.

User Accounts

The User Accounts page of the Security Console provides summaries of user accounts that you select to review. For each account, it always provides:

  • The user's login, first name, and last name, in a User column.

  • Whether the account is active, whether it is locked, and the user's password-expiration date, in a Status column.

It may also provide:

  • Associated worker information, if the user account was created in conjunction with a worker record in Human Capital Management. This may include person number, manager, job title, and business unit.

  • Party information, if the user account was created in conjunction with a party record created in CRM. This may include party number and party usage.

The User Accounts page also serves as a gateway to account-management actions you can complete. These include:

  • Reviewing details of, editing, or deleting existing accounts.

  • Adding new accounts.

  • Locking accounts.

  • Resetting users' passwords.

To begin working with user accounts:

  1. Select the Users tab in the Security Console.

  2. In a Search field, select any combination of user states and enter at least three characters.

    The search returns user accounts at the states you selected, whose login, first name, or last name begins with the characters you entered.

User Account Details

To review full details for an existing account, search for it in the User Accounts page and click its user login in the User column. This opens a User Account Details page.

These details always include:

  • User information, which consists of user, first, and last name values, and an e-mail address. It also includes an external identifier if one has been created. This is an external-system identifier, such as a single sign-on account ID if single sign-on is enabled.

  • Account information, which comprises the user's password-expiration date, whether the account is active, and whether it is locked.

  • A table listing the roles assigned to the user, including whether they are autoprovisioned or assignable. A role is assignable if it can be delegated to another user.

The page may also include an Associated Worker Information region or an Associated Party Information region. The former appears only if the user account is related to a worker record in Human Capital Management, and the latter if the user account is related to a party record in CRM.

To edit these details, click Edit in the User Account Details page. Be aware, however:

  • You can edit values only in the User Information, Account Information, and Roles regions.

  • Even in those regions, you can edit some fields only if the user is not associated with a worker or a party. If not, for example, you can modify the First Name and Last Name values in the User Information region. But if the user is associated with a worker, you would manage these values in Human Capital Management. They would be grayed out in this Edit User Details page.

  • In the Roles table, Autoprovisioned check boxes are set automatically, and you cannot modify the settings. The box is checked if the user obtained the role through autoprovisioning, and cleared if the role was manually assigned. You can modify the Assignable setting for existing roles.

Click Add Autoprovisioned Roles to add any roles for which the user is eligible. Or, to add roles manually, click Add Role. Search for roles you want to add, select them, and click Add Role Membership.

You can also delete roles. Click the x icon in the row for the role, and then respond Yes to a confirmation message.

Add User Accounts

The ability to add user accounts in the Security Console is intended for the creation of implementation users. The expectation is that an implementation user would set up Oracle Human Capital Management (HCM). You would then use HCM to create accounts for application users.

To add a user account in the Security Console:

  1. Select the Users tab in the Security Console to open the User Accounts page.

  2. Click the Add User Account button.

  3. Select a value for Associated Person Type: Worker if this account is to be linked to a worker record in HCM, or None if not.

  4. By default, the account is set to be active and unlocked in the Account Information area. Typically these values are appropriate, but you may modify them.

  5. Select the User Category with which you want to associate the user.

    Note: If you are not sure which user category to select, you may leave it unchanged. All new users are automatically assigned to the Default user category.
  6. Enter name, e-mail, and password values in the User Information region as per the following guidance.

    • You need not enter a User Name value. It is generated automatically according to the user name generation rule selected on the User Categories page.

    • The First Name value is not required. However, you must enter one if the selected user name generation rule makes use of the first name or the first-name initial.

    • The Password value must conform to the password policy established on the User Categories page. The Confirm Password value must match the Password value.

    • An external identifier is the user's ID in another system, such as a single sign-on account ID if single sign-on is enabled.

  7. Click Add Autoprovisioned Roles, to assign roles for which role-provisioning rules make the user eligible.

  8. Click Add Roles to assign other roles. Search for roles you want to assign, select them, then click Add Role Membership. Select Done when you are finished.

  9. In the Roles table, select Assignable for any role that can be delegated to another user.

  10. Click Save and Close.

Reset Passwords

An administrator may use the Security Console to reset other users' passwords. That action triggers an e-mail notification to each user, informing him or her of the new password.

A new password must conform to your password policy. You establish this policy on the User Categories page. The page on which you reset the password displays the policy.

To reset a password:

  1. On the User Accounts page, search for the user whose password you want to change.

  2. For the selected user, click Action > Reset Password.

    As an alternative, open the user's account for editing: click the User Login value in the User Accounts page, then Edit in a User Account Details page. On that page, select Reset Password.

  3. On the Reset Password dialog box, select whether to generate the password automatically or change it manually. For a manual change, also enter a new password value and a confirmation value, which must match the new value.

    Note: The option to reset a password to an automatically generated value is always available. For the manual reset option to be available, you must select the Administrator can manually reset password option on the User Categories page.
  4. Click Reset Password.

Lock and Unlock User Accounts

An administrator may use the Security Console to lock users' accounts. When an account is locked, its user cannot sign in. He or she must either use the "forgot password" flow to reset the password or contact the help desk to have the account unlocked.

You can lock a user account in either of two ways. In either case, open the User Accounts page and search for the user whose account you want to lock.

To complete the first procedure:

  1. In the user's row, click the Action icon, then Lock Account.

  2. Respond Yes to a confirmation message.

To complete the second procedure:

  1. Open the user's account for editing: click the User Login value in the User Accounts page, then Edit in a User Account Details page.

  2. In the Edit User Account page, select the Locked check box in the Account Information region.

  3. Select Save and Close.

You can unlock the account only from the Edit User Account page, by clearing the Locked check box.

Delete User Accounts

An administrator may use the Security Console to delete users' accounts.

  1. Open the User Accounts page and search for the user whose account you want to delete.

  2. In the user's row, click the Action icon, then Delete.

  3. Respond Yes to a confirmation message.

Create Notification Templates

Users may receive Email notifications of user-account events, such as account creation or password expiration. These notifications are generated from a set of templates, each of which specifies an event. A template generates a message to a user when that user is involved in the event tied to the template.

You can enable or disable templates, edit templates, or create templates to replace existing ones. There are 16 events, and a predefined template exists for each event. You can enable only one template linked to a given event at a time.

Here's how you can create a template:

  1. Click the User Categories tab in the Security Console.

  2. Select a user category and on the User Category Information page, click the Notifications tab.

  3. Click the Edit button to make changes.

    Ensure that the Enable Notifications check box is selected.

  4. Click Add Template.

  5. Specify a name and description for the template.

  6. Select Enabled to use the template immediately. If selected, template that had been enabled for the event which you select, is automatically disabled.

  7. Select an Event from the corresponding drop-down list.

    The values for Message Subject and Message are copied from an already-configured template for which the same event is selected.

  8. Update the Message Subject and Message as required.

    Note: The message text includes tokens which are replaced in runtime by literal values appropriate for a given user or account.
  9. Click Save and Close.

To edit a template, select it from the templates listed in the Notification Templates table. Then follow the same process as you would to create a template. You cannot modify the event selected for a template that has been saved. You cam only enable or disable an individual template when you edit it.

Note: You can't edit or delete predefined templates that begin with the prefix name ORA. You also can't modify the message subject or the message. However, you can only enable or disable the predefined templates.

You can delete the templates you created. Select the template row in the table and click Delete.

Here's the table that lists the tokens that you can use in the message text for a template:

Token Meaning Events

${userLoginId}

The user name of the person whose account is being created or modified.

  • Forgot user name

  • Password expired

  • Password reset confirmation

${firstName}

The given name of the person whose account is being created or modified.

  • Administration activity location based access disabled confirmation

  • Administration activity requested

  • Administration activity single sign-on disabled confirmation

  • Expiring external IDP signing certificate

  • Expiring service provider encryption certificate

  • Expiring service provider signing certificate

  • Forgot user name

  • New account created - manager

  • New user created

  • Password expired

  • Password expiry warning

  • Password generated

  • Password reset

  • Password reset - manager

  • Password reset confirmation

  • Password reset confirmation - manager

${lastName}

The surname of the person whose account is being created or modified.

  • Administration activity location based access disabled confirmation

  • Administration activity requested

  • Administration activity single sign-on disabled confirmation

  • Expiring external IDP signing certificate

  • Expiring service provider encryption certificate

  • Expiring service provider signing certificate

  • Forgot user name

  • New account created - manager

  • New user created

  • Password expired

  • Password expiry warning

  • Password generated

  • Password reset

  • Password reset - manager

  • Password reset confirmation

  • Password reset confirmation - manager

${managerFirstName}

The given name of the person who manages the person whose account is being created or modified.

  • New account created - manager

  • Password reset confirmation - manager

  • Password reset - manager

${managerLastName}

The surname of the person who manages the person whose account is being created or modified.

  • New account created - manager

  • Password reset confirmation - manager

  • Password reset - manager

${loginUrl}

The web address to sign in to Oracle Cloud. The user can sign in and use the Preferences page to change a password that is about to expire. Or, without signing in, the user can engage a forgot-password procedure to change a password that has already expired.

  • Expiring external IDP signing certificate

  • Password expired

  • Password expiry warning

${resetUrl}

A one-time web address expressly for the purpose of resetting a password, used in the Password Generated, Password Reset, New Account, and New Account Manager templates.

  • New account created - manager

  • New user created

  • Password generated

  • Password reset

  • Password reset - manager

${CRLFX}

Insert line break.

All events

${SP4}

Insert four spaces.

All events

${adminActivityUrl}

A URL of the page in which an administrator initiates an administration activity.

Administration activity requested

${providerName}

The name of an external Identity Provider.

Expiring external IDP signing certificate

${signingCertDN}

The signing certificate of an external Identity Provider.

Expiring external IDP signing certificate

${signingCertExpiration}

The expiration date of the external Identity Provider signing certificate or of the service provider signing certificate.

  • Expiring external IDP signing certificate

  • Expiring service provider signing certificate

${encryptionCertExpiration}

The expiration date of the Service Provider encryption certificate.

Expiring service provider encryption certificate

${adminFirstName}

The given name of the person who has administrator rights.

  • Administration activity location based access disabled confirmation

  • Administration activity single sign-on disabled confirmation

${adminLastName}

The surname of the person who has administrator rights.

  • Administration activity location based access disabled confirmation

  • Administration activity single sign-on disabled confirmation

Synchronize User and Role Information

You run the process Retrieve Latest LDAP Changes once during implementation. This process copies data from the LDAP directory to the Oracle Fusion Applications Security tables. Thereafter, the data is synchronized automatically. To run this process, perform the task Run User and Roles Synchronization Process as described in this topic.

Run the Retrieve Latest LDAP Changes Process

Follow these steps:

  1. Sign in to your Oracle Applications Cloud service environment as the service administrator.

  2. In the Setup and Maintenance work area, go to the following for your offering:

    • Functional Area: Initial Users

    • Task: Run User and Roles Synchronization Process

  3. On the process submission page for the Retrieve Latest LDAP Changes process:

    1. Click Submit.

    2. Click OK to close the confirmation message.

Reset the Cloud Service Administrator Sign-In Details

After setting up your implementation users, you can reset the service administrator sign-in details for your Oracle Applications Cloud service. You reset these details to avoid problems later when you're loaded to the service as an employee. This topic describes how to reset the service administrator sign-in details.

Sign in to your Oracle Applications Cloud service using the TechAdmin user name and password and follow these steps:

  1. In the Setup and Maintenance work area, go to the following:

    • Functional Area: Initial Users

    • Task: Create Implementation Users

  2. On the User Accounts page of the Security Console, search for your service administrator user name, which is typically your email. Your service activation mail contains this value.

  3. In the search results, click your service administrator user name to open the User Account Details page.

  4. Click Edit.

  5. Change the User Name value to ServiceAdmin.

  6. Delete any value in the First Name field.

  7. Change the value in the Last Name field to ServiceAdmin.

  8. Delete the value in the Email field.

  9. Click Save and Close.

  10. Sign out of your Oracle Applications Cloud service.

After making these changes, you use the user name ServiceAdmin when signing in as the service administrator.

User Categories

Overview of User Categories

You can categorize and segregate users based on the various functional and operational requirements. A user category provides you with an option to group a set of users such that the specified settings apply to everyone in that group. Typical scenarios in which you may want to group users are:

  • Users have different preferences in receiving automated notifications from the Security Console. For example, employees of your organization using the organization's single sign-on don't require notifications from the Security Console about creating new users, password expiry, or password reset. However, the suppliers of your organization who aren't using the organization's single sign-on, must receive such notifications from the Security Console.

  • You have built an external application for a group of users using the REST APIs of Oracle Fusion Applications. You intend to redirect this user group to the external application when using the Security Console to reset passwords or create new users.

On the Security Console page, click the User Category tab. You can perform the following tasks:

  • Segregate users into categories

  • Specify Next URL

  • Set user preferences

  • Define password policy

  • Enable notifications

Segregate Users into Categories

Create user categories and add existing users to them. All existing users are automatically assigned to the Default user category unless otherwise specified. You may create more categories depending upon your requirement and assign users to those categories.

Note: You can assign a user to only one category.

Specify Next URL

Specify a URL to redirect your users to a website or an application instead of going back to the Sign In page, whenever they reset their password. For example, a user places a password reset request and receives an Email for resetting the password. After the new password is authenticated, the user can be directed to a website or application. If nothing is specified, the user is directed to Oracle Applications Cloud Sign In page. You can specify only one URL per user category.

Set User Preferences

Select the format of the User Name, the value that identifies a user when signed in. It is generated automatically in the format you select. Options include first and last name delimited by a period, email address, first-name initial and full last name, and person or party number. Select the check box Generate system user name when generation rule fails to enable the automatic generation of User Name values if the selected generation rule cannot be implemented.

Define Password Policy

Determine the number of days a password remains valid. Set the number of days before expiration that a user receives a warning to reset the password. You can define the period in which a user must respond to a notification to reset the password (Hours Before Password Reset Token Expiration). Select a password format and determine whether a previous password may be reused. You may decide whether to permit an administrator to manually modify passwords in the Reset Password dialog box, available from a given user's record on the Users tab. This option applies only to the manual-reset capability. An administrator can always use the Reset Password dialog box to initiate the automatic reset of a user's password.

Enable Notifications

Notifications are enabled by default, but you can disable them if required. You can also enable or disable notifications separately for each user category. If users belonging to a specific category don't want to receive any notification, you can disable notifications for all life cycle events. Alternatively, if users want to receive notifications only for some events, you can selectively enable the functionality for those events.

Notifications are sent for a set of predefined events. To trigger a notification, you must create a notification template and map it to the required event. Depending on the requirement, you can add or delete a template that is mapped to a particular event.

Note: You can't edit or delete predefined notification templates that begin with the prefix ORA. You can only enable or disable them. However, you can update or delete the user-defined templates.

User Category feature supports both SCIM protocol and HCM Data Loader for performing any bulk updates.

Add Users to a User Category

Using the Security Console, you can add existing users to an existing user category or create a new category and add them. When you create new users, they are automatically assigned to the default category. At a later point, you can edit the user account and update the user category. You can assign a user to only one category.

Note: If you are creating new users using Security Console, you can also assign a user category at the time of creation.

You can add users to a user category in three different ways:

  • Create a user category and add users to it

  • Add users to an existing user category

  • Specify the user category for an existing user

Note: You can create and delete a user category only using the Security Console. Once the required user categories are available in the application, you can use them in SCIM REST APIs and data loaders. You can't rename a user category.

Adding Users to a New User Category

To create a user category and add users:

  1. On the Security Console, click User Categories > Create.

  2. Click Edit, specify the user category details, and click Save and Close.

  3. Click the Users tab and click Edit.

  4. On the Users Category: Users page, click Add.

  5. In the Add Users dialog box, search for and select the user, and click Add.

  6. Repeat adding users until you have added the required users and click Done.

  7. Click Done on each page until you return to the User Categories page.

Adding Users to an Existing User Category

To add users to an existing user category:

  1. On the Security Console, click User Categories and click an existing user category to open it.

  2. Click the Users tab and click Edit.

  3. On the Users Category: Users page, click Add.

  4. On the Add Users dialog box, search for and select the user, and click Add.

  5. Repeat adding users until you have added the required users and click Done.

  6. Click Done on each page until you return to the User Categories page.

Specifying the User Category for an Existing User

To add an existing user to a user category:

  1. On the Security Console, click Users.

  2. Search for and select the user for whom you want to specify the user category.

  3. On the User Account Details page, click Edit.

  4. In the User Information section, select the User Category. The Default user category remains set for a user until you change it.

  5. Click Save and Close.

  6. On the User Account Details page, click Done.

You can delete user categories if you don't require them. However, you must ensure that no user is associated with that user category. Otherwise, you can't proceed with the delete task. On the User Categories page, click the X icon in the row to delete the user category.

How can I direct users to a specific application or website after password reset?

Use this task if you want to direct your users to another application or a website instead of the Oracle Applications Cloud sign in page, after they reset the password. Using the Security Console, you can specify the URL of the application or the website to which the users can be directed.

  1. On the Security Console, click User Category.

  2. Select the user category and on the User Category: Details page, click Edit.

  3. Specify the URL in the Next URL field and click Save and Close.

When users of that user category successfully reset their password, they are automatically redirected to the specified application or the web page instead of the Oracle Applications Cloud sign in page.

How can I enable or disable notifications for users?

Using the Security Console, you can determine whether to turn notifications on or off for the users.

  1. On the Security Console, click User Categories and from the list, select the specific user category.

  2. Click the Notifications tab and click Edit.

  3. Select the Enable Notifications check box to enable notifications for all users of that user category. To disable notifications, deselect the check box.

  4. Click Done.

To determine which notifications to send, you have to enable the notification template for each required event.