User Rating: 0 / 5
ABC Corporation has completed Oracle Fusion installation. The next step is to select the offerings, options, and features to implement. As the Implementation Consultant for the Workforce Deployment implementation project, you must configure the Workforce Deployment offering. This article will cover the following activities:
Selecting Feature Choices
Features are associated to some offerings or options. Each feature provides two or more choices. The valid selection types for choices are:
User Rating: 5 / 5
Oracle Fusion Functional Setup Manager is the application used to perform the setup tasks required to complete the implementation of Oracle Fusion Applications. The application implementation process includes both manual activities and activities executed within the Setup and Maintenance work area within Oracle Fusion Applications.
Roles required to access FSM are:
• Application Implementation Manager
• Application Implementation Consultant
It utilizes some specific terminology to refer to its own functionality:
User Rating: 5 / 5
Here are top 10 reasons business users & accountants would love Fusion financials, presented in a quick on-the-go readable format for quick review & later in the series we will take deeper dive in these & related topics.
Oracle Fusion Financials offers an integrated financial management suite that is really designed to automate, streamline, and control an organization’s financial management processes end-to-end. It includes a broad suite of applications that are completely integrated. It has your traditional GL, Payables, Receivables, Assets, Expenses, Collections and Cash Management as well as the common module architecture from EBS that includes the centralized Subledger Accounting, centralized customer and supplier data (TCA :Trading Community Architecture), Tax, Payments, and Intercompany.
User Rating: 5 / 5
This training article will helps to understand basic concepts of different roles and their brief definition and we will also try to understand relationship between them. Let us first understand Role Based Access Control in Fusion applications-
Role Based Access Control (RBAC)
An organisation needs to control who can do what on which functions or sets of data under what conditions. The who is a user here. A user's access is based on the definition of the roles provisioned (assigned) to the user. Access is defined as entitlement, which consists of privileges. The what are the abstract operations or entitlement. The which represents the resources being accessed.
RBAC normalizes access to functions and data through user roles rather than only users. User access is based on the definition of the roles provisioned to the user. The roles are defined at functional and technical levels. The functional level is the business definition that is used by business users and the technical level is the implementation of roles using Oracle Technology.
RBAC is based on the following concepts:
Role assignment - A subject can exercise permission only if the subject has selected or been assigned a role.
Role authorization - A subject’s active role must be authorized for the subject. With rule mentioned above, this rule ensures that users can take on only roles for which they are authorized.
Permission authorization - A subject can exercise a permission only if the permission is authorized for the subject’s active role. With rules 1 and 2, this rule ensures that users can exercise only permissions for which they are authorized.
Basically security in Fusion Application is based on Role Based Access Control (RBAC) In Fusion Applications, the RBAC implementation is based on abstract, job, duty, and data roles that work together to control access to functions and data. The definitions of these functional roles are as follows:
This role categorizes the roles for reference implementation. It inherits duty role but does not contain security policies. For example: Employee, Manager, etc.
This role defines a specific job an employee is responsible for. An employee may have many job roles. It may require the data role to control the actions of the respective objects. For example: Benefits Manager, Accounts Receivable Specialist, etc.
This role defines access to the data within a specific duty. Who can do what on which set of data? The possible actions are read, update, delete, and manage. Only duty roles hold explicit entitlement to the data. These entitlements control the privileges such as in a user interface that can see specific screens, buttons, data columns, and other artifacts.
This role defines a set of tasks. It is the most granular form of a role. The job and abstract roles inherit duty roles. The data security policies are specified to duty roles to control actions on all respective objects. Duty Role is the most granular form of role where mainly security policies are attached and they are implemented as application role in Authorization Policy Manager (APM)
Below diagram from the “Oracle Fusion Applications Security Guide” shows relationships between these roles: