To address your specific security business requirements within the FAW Application, you can use the security customization in FAW for both data security and object security. Data security allows you to restrict access to data based on various attributes, such as business unit, legal entity, department, or any other filter criteria7. Object security allows you to restrict access to objects, such as subject areas, facts, dimensions, KPIs, dashboards, or reports based on user roles or groups8. You do not need to address those requirements in Fusion Applications or rely on only the out-of-the-box security model.

The way that you can address your requirements in FAW when FAW does not move and replicate your entire security implementation from Fusion Applications is to evaluate your security requirements and utilize security customization features in FAW to meet your needs. FAW provides various security customization features, such as custom data roles, custom duty roles, custom security configurations, and functional groups, that allow you to define advanced data security and object security4. You do not need to set up SSO between FAW and Fusion Applications or open a support ticket for this purpose.

You can create multiple branches to customize the semantic model. You use a branch or version to publish your changes to the model. You can apply the model from the branch to a local service instance for testing. When the changes are correct, you can merge that branch with the main branch3

The Reporting Configuration parameters are used to define how the data is displayed in the FAW user interface. They include settings such as currency, date format, decimal separator, number of decimals, and default dashboard. These parameters affect the presentation layer of the FAW semantic model and can be changed at any time without affecting the data pipeline or the data warehouse.

Verified References: Oracle Fusion HCM Analytics, page 9.

The typical use case of the Promote Objects feature is to move your customization from one environment to another, such as from development to production. The Promote Objects feature allows you to export and import your customizations of the semantic model, security configurations, and KPIs between different instances of FAW4. The Promote Objects feature is not used to check the validity of your customization or to replicate one instance to another.

The prerequisite for creating a data pipeline for any functional area is setting up the pipeline parameters. The pipeline parameters define the global settings for the data pipeline, such as the source application URL, credentials, notification email, incremental refresh frequency, and retention period4. Configuring single sign-on and completing data security assignments are not prerequisites for creating a data pipeline, but they are recommended for securing access to FAW and Fusion Applications5

The purpose of the system groups (like FAW Licensed ERP Authors and FAW Functional Administrator) in the FAW Security framework is to grant a user access to FAW based on the system groups to which they are assigned. System groups are predefined groups that specify the user’s system permissions, such as whether they can consume, author, or administer content for a specific module5. System groups do not map duty and data roles or define job-specific roles for users. References: 5