Guidelines for Loading User-Update Requests

You use the User object to create requests to update existing Oracle HCM Cloud user accounts. This topic describes when to use each component of the User object. It also describes any restrictions on its use.

The User Component

You can use the User component to create requests to:

• Update a user name.

• Suspend or activate a user.

• Add a single role to or remove a single role from a user.

• Create a user account, in specific circumstances.

• Delete a user account.

You also use this component to update the CredentialsEmailSent value in the PER_USERS table. This value records whether the account and password details have been sent to the user. Valid values are Y and N. After the email has been sent, it can't be sent again unless you reset this value. For example, to reset user passwords, you can run the Send User Name and Password Email Notifications process. Before doing so, you can set CredentialsEmailSent to N to ensure that users are notified of new passwords. Otherwise, they aren't notified.

The User Role Component

The User Role component is a child of the User object. You use the User Role component to add or remove multiple roles for a user. To add or remove a single role, use the User component.

Creating User Accounts

Depending on the setting of the User Account Creation enterprise option, user accounts can be created automatically for workers loaded in bulk. However, you may have prevented the user account from being created for an individual worker. Alternatively, it may have failed to be created for some reason. In these cases, you can use the User object to request a user account.

Note: Use the User object to request a user account only as an exception. The standard method is to request the user account when you create the worker.

A user account can be created by means of the User object only if the User Account Creation enterprise option enables automatic creation of user accounts.

Deleting User Accounts

On occasion, you may want to delete a user account. For example, you may have created the user name in the wrong format. You can delete user accounts in both test and production environments, and the accounts can be in any status. The User and Role Provisioning options have no effect on user-account deletion. For example, deletion requests can't be suppressed.

Tip: The user is deleted from both the LDAP directory and the PER_USERS, PER_USER_ROLES, and PER_USER_HISTORY records. Therefore, you can reuse the user name. You can recreate the user account on the Security Console, using the Manage Users task, or by loading the User object.

Running Send Pending LDAP Requests

After loading user-update requests, you run the Send Pending LDAP Requests process to deliver them to your LDAP directory server. The recommendation is to schedule this process to run daily. You don't have to run this process after updating the CredentialsEmailSent indicator.