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

FAW provides two features to customize and extend the semantic model: Semantic Model Extensions and Data Augmentation. Semantic Model Extensions allow you to modify the existing dimensions, facts, and subject areas, as well as create new ones from existing data sources. Data Augmentation allows you to create new dimensions, facts, and subject areas from custom data sources that are not part of the FAW data pipelin

The step that would be required for the data pipeline to run without any issues after your source Fusion Cloud Application instance has been refreshed with data from another environment is to update the applicable users credentials, if the passwords differ between environments. You need to ensure that the FAWService user and any other users that are used for data extraction have valid credentials in both environments8. You do not need to update the source application URL or the notification email of the FAW instance for this purpose

The option that is available in FAW for synchronizing users and job roles between FAW and Fusion Applications is to implement SSO and synchronization of users and job roles between FAW and Fusion Applications, before provisioning the FAW instance. This will allow you to avoid creating Fusion Applications users and their assigned job roles in FAW, as they will be automatically synchronized from Fusion Applications4. You cannot use the FAW console security option or the Bulk Load option in FAW to do the synchronization. 

The operations that are disabled during the scheduled incremental data refresh are ad hoc data refresh for functional areas and semantic model extensions. You cannot perform an ad hoc data refresh for a functional area while a scheduled data load is ongoing, as this may cause conflicts or errors in the data pipeline3. You also cannot perform semantic model extensions while a scheduled data load is ongoing, as this may cause inconsistencies or corruption in the semantic model1. FAW subject areas and decks are not disabled during the refresh, but they may show outdated or incomplete data until the refresh is completed. 

The DFFs and their attributes must be BI-enabled in order to be extracted by the FAW data pipeline and loaded into the data warehouse. BI-enabling a DFF means that it is exposed as a column in a view object that is part of a subject area in Oracle Transactional Business Intelligence (OTBI). This allows FAW to access the DFF data through OTBI web services.

Verified References: Use Descriptive Flexfields, section 23.1; About Flexfields, section “Use Flexfields in Your Data Model”.