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 FAW 4 .  The Promote Objects feature is not used to check the validity of your customization or to replicate one instance to another.

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 module 5 .  System groups do not map duty and data roles or define job-specific roles for users. References:  5

To perform data validation from the FAW console, you need to ensure that you have the same data security privileges in the FAW instance and the Oracle Transactional Business Intelligence (OTBI) instance.  This will allow you to compare the metrics between the two instances and verify their accuracy 2 .  You do not need to have access to all data in the FAW instance or have the administrator privilege in the OTBI instance to perform data validation.

The FAW system role/group that is required to grant a user the privilege to manage data augmentation is Modeler.  The Modeler role allows the user to create and manage data augmentations, as well as semantic model extensions, snapshots, and bundles 1 .  The Functional Administrator role allows the user to manage functional areas, data pipelines, and data refreshes 2 .  The Security Administrator role allows the user to manage users, groups, roles, and access 3

The type of Application Role that is used to secure access to the Subject Area is the Data Role.  The Data Role defines the data security context for a user, such as which business units, legal entities, or departments they can access 2 .  The Duty Role defines the functional security for a user, such as which tasks they can perform or which objects they can view 3 .  Any of the Application Role types cannot be used to secure access to the Subject Area, as they have different purposes. 

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 period 4 .  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 Applications 5