Add User Account
To add a user account in Oracle Fusion Applications, you will need to have administrative privileges. If you do not have administrative privileges, you will need to ask someone with administrative privileges to add the user account for you.
To add a user account, follow these steps:
Log in to Oracle Fusion Applications as an administrator.
Navigate to the "Security Console" from the main menu.
Click on the "Users" tab.
Click on the "Create" button.
Enter the user's first and last name, as well as their email address and other relevant information.
Choose a username and password for the user.
Select the appropriate security roles for the user, based on their job function and responsibilities within the organization.
Click on the "Create User" button to create the user account.
After creating the user account, you may also want to assign the user to a specific business unit or department within the organization, if applicable. This can be done by navigating to the "Organization Structures" tab in the Security Console and adding the user to the appropriate organizational unit.
It's important to keep in mind that creating a user account in Oracle Fusion Applications does not automatically grant the user access to all features and functions within the system. You will need to assign the appropriate security roles to the user in order to control their access to specific features and functions.
_________________________________________________________________________________________
Create your user and access
Security Console
Continue to the next step to create your user and assign roles.
Access Navigator / Hamburguer icon
Scroll down until you reach "Tools" group
Inside of "Tools", click on "Security Console"
_________________________________________________________________________________________
Users
Continue to the next step to create your user and assign roles.
Click on "OK" button
Click on "Users" option on the left column
3. Click on "Add User Account"
4. This option allows you to search for users who have already been created. You can search for your user after you create and save it.
5. Enter the user information here.
ii. Your First Name
iii. Your Last Name
iv. Your Email
v. Like a user name suggestion, the system will concatenate your "FirstName.LastName."
vi. Your password
vii. Your password confirmation
Scroll down to block 6 to add the roles that you want or will use in your project implementation.
7.Click on Add Role Button
i. Keep searching for "Role"
ii. Enter your Role Name here
iii. Select the search icon
iv. Use roles that begin with ORA whenever possible
v. Never use roles that end with the words "COPY"
We will use the first line in this example.
vii. Select the corresponding line
viii. Click the "Add Role Membership" button to assign this role to your user
ix. Repeat the procedure for the remaining roles, entering the next role name
x. Search the next role name
Each new role you assign to your user will be added to your list - yellow block
xi. When you've finished adding roles, click the "Done" button
xii. Then click the "Save and Close" button
Assignable: "Assignable" check box is a feature that is used when creating or modifying security roles. When the "Assignable" check box is selected, it indicates that the security role is an "assignable" role, which means that it can be customized and modified by administrators to fit the specific needs of an organization. By contrast, when the "Assignable" check box is not selected, it indicates that the security role is an "abstract" role, which means that it is predefined by Oracle and cannot be modified or deleted by administrators.
The "Assignable" check box is typically used in conjunction with the "Application" and "Function" security roles in Oracle Fusion Applications. These types of security roles are used to control access to specific features and functions within the system, and they can be customized by administrators to fit the specific needs of an organization.
Auto-Provisioned: "Auto-Provisioned" check box is a feature that is used when creating or modifying security roles. When the "Auto-Provisioned" check box is selected, it indicates that the security role will be automatically provisioned to users based on their job function and responsibilities within the organization.
By contrast, when the "Auto-Provisioned" check box is not selected, it indicates that the security role must be manually provisioned to users by an administrator.
_______________________________________________________________________________________
Jobs for synchronizing roles and users
Don't forget to run these jobs after you've finished registering these roles to synchronize your access:
Retrieve Latest LDAP Changes
Import User and Role Application Security Data
Send Pending LDAP Requests
Send Personal Data for Multiple Users to LDAP
Retrieve Latest LDAP Changes
It is critical that all User Account information be synced with the Cloud application from the LDAP directory; otherwise, you will encounter the issue of not seeing Roles and user accounts in the application.
Import User and Role Application Security Data
The "Import User and Role Application Security Data" is a crucial process in Oracle Fusion ERP that initializes and maintains the Oracle Fusion Applications Security tables12. This job performs the following key functions:
Copies users, roles, privileges, and data security policies from the LDAP directory, policy store, and Applications Core Grants schema to Oracle Fusion Applications Security tables2.
Ensures that the Security Console has up-to-date information, making its assisted search feature fast and reliable2.
Synchronizes changes made since the last run, keeping the security data current2.
Send Pending LDAP Requests
Help with many important functions in the Cloud Application, such as creating, suspending, and reactivating user accounts.
Send Personal Data for Multiple Users to LDAP
All Users: The process sends personal information for all users to the Identity Store, regardless of whether the information has changed since the last time it was sent.
Changed users only: The process only sends personal information that has changed since the last time the information was sent to the Identity Store (regardless of how they were sent). This is the standard-setting.
Last updated