Mapping keys are used to specify the source node types mapped to target node types and to define a location name to export the mapping data. The following statements are true about mapping keys: mapping keys consist of a location, source node type, and target node type; mapping keys control which dimensions are output in the source and target columns of the mapping export. The following statements are false about mapping keys: the system automatically generates mapping keys for each unique location; one mapping key is required per location. You need to manually define mapping keys for each source-to-target relationship using a unique location name. You can have multiple mapping keys for the same location if you have different source node types mapped to the same target node type. References: Defining Mapping Keys - Oracle Help Center1; Exporting Mapping Data - Oracle Help Center2

According to the Oracle Help Center, the Data Manager permission allows users to create and manage views for Planning application data and make updates to data in any dimension of an application. The Browser role allows users to view changes made to data in all applications. The Application Creator role allows users to create and manage a Planning application. The Auditor role allows users to view audit reports for all applications.

1: :

According to the Oracle Help Center, migration snapshots are used to migrate application artifacts and data between environments, such as refreshing the test environment from the production environment. Migration snapshots can also be used to restore the artifacts and data to the snapshot state in case of any issues or errors. The other reasons are not valid for creating a migration snapshot.