Oracle Fusion Data Intelligence

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Fusion Data Intelligence› Oracle Fusion Data Intelligence

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

FDI access for Non-ERP user & support for Essbase cubes in Semantic model

Accepted answer
74
Views
3
Comments
FDI_USER
FDI_USER Rank 4 - Community Specialist
in Oracle Fusion Data Intelligence

Hello Team,

I'm reaching out to inquire about the recommended approach for granting system access to individuals who are not ERP users. Should we utilize IDCS for this purpose, or is it preferable to define a custom role within the ERP system and then associate that role with a predefined application role (such as author or consumer) within FDI?

Additionally, I'm interested in learning if there is any information available regarding the timeline for Essbase cube integration with the Semantic Model in FDI, considering its current availability in the standalone OAC application.

I've also observed that reports generated via a live connection to EPM are slow to load, often taking at least 30-40 seconds, and that hierarchies are not currently supported as selection steps in Data Visualization (DV).

Thank you for your assistance.

Tagged:

Best Answer

  • Sumanth V -Oracle
    Sumanth V -Oracle Rank 8 - Analytics Strategist
    Answer ✓

    @FDI_USER - Granting system access to individuals who are not Oracle Fusion Cloud Applications (ERP) users can be effectively managed through Oracle Identity Cloud Service (IDCS). By creating and assigning appropriate groups and roles within IDCS, you can control access to Oracle Fusion Data Intelligence (FDI) without relying on ERP-specific roles.​

    Recommended Approach:

    1. Utilize IDCS for User Management:
      • Create Custom Groups: In IDCS, establish custom groups tailored to the access requirements of non-ERP users.​
      • Assign System Roles: Map these custom groups to the relevant system roles in FDI, such as Functional Administrator, Security Administrator, Modeler, or Service Administrator. This mapping grants users the necessary privileges within FDI.​
    2. Assign Licensed Application Roles:
      • Determine Appropriate Roles: Based on the user's intended functions within FDI, assign licensed application roles like Author or Consumer. These roles define the level of access and capabilities the user will have.​
      • Map Roles to IDCS Groups: Associate the licensed application roles with the corresponding IDCS groups to ensure proper access control.​

    Considerations:

    • Job-Specific Groups: If the non-ERP users have roles analogous to job-specific groups (e.g., Vice President of Sales, Human Resources Analyst), you can create similar groups in IDCS and map them accordingly.
    • Data Access Policies: Ensure that data access policies are defined and applied to these groups to control the data visibility and actions permitted within FDI.​

    By leveraging IDCS for user and role management, you maintain a centralized and streamlined approach to access control, independent of ERP user definitions. This method aligns with Oracle's best practices for managing access to Oracle Fusion Data Intelligence.​

    For detailed guidance on managing users, groups, application roles, and data access in Oracle Fusion Data Intelligence, refer to the official documentation:

    https://docs.oracle.com/en/cloud/saas/analytics/25r1/fawag/managing-users-groups-application-roles-and-data-access.html

Answers