In a maintenance view for mappings, you can compare the source and mapping viewpoints to identify nodes that exist in the source but have not been mapped to the target. The next step to define mappings is to create a request, then drag and drop nodes from the source to the mapping viewpoint. This way, you can create new nodes in the mapping viewpoint that have properties derived or transformed from the source nodes using the node type converter and map binding.You do not need to use an Excel mapping file, run a mapping utility, or open a request and add nodes to the target viewpoint, because these are not supported methods for defining mappings in Oracle Enterprise Data Management Cloud. Reference: Working with Requests - Oracle Help Center3; Creating Mapping Viewpoints - Oracle Help Center2

The Data Manager permission is the second highest level of permission that can be assigned to an application. Users with the Data Manager permission can perform various tasks such as: import, export, and update data for all dimensions in the application, create and submit requests for dimensions in the application, manage viewpoints and viewpoint subscriptions for all dimensions in the application, run business rules on dimensions in the application, copy data across dimensions in the application, etc. Users with the Data Manager permission cannot manage the application's node sets, hierarchy sets, and node types, because these are data objects that require Owner permission to manage.Users with the Data Manager permission cannot assign permissions for the application data, because this requires Owner permission as well. Reference: Working with Permissions - Oracle Help Center1; Working with Requests - Oracle Help Center3

''Suppose you have an acquired company with a general ledger, and you want to map the general ledger accounts to planning accounts. The general ledger accounts have different prefixes than the planning accounts.'' This is an example of a scenario where mapping nodes across applications is required. Another scenario is when applications share data but have different dimensions, such as when mapping accounts from a GL application to a Planning application. The other options are not scenarios where mapping nodes across applications is required.

When a data manager submits a request in a view that has subscriptions defined, the system generates subscription requests based on the subscriptions and assignees for each viewpoint.If multiple viewpoints have the same assignee, the system bundles the request items into a single subscription request for that assignee. Reference: Creating, Editing, and Validating Subscriptions - Oracle Help Center1

According to the reference, ''A node type converter is a data object that enables you to share nodes between different node types in different applications.'' To keep account dimensions in sync between two applications, you need to create two node type converters, one for each direction of sharing. You cannot create a bi-directional node type converter, or specify a reverse conversion in requests.

To keep account dimensions in two different applications in sync and share nodes added to either application with the other, you can create two node type converters. One node type converter can have application 1 accounts as the source and application 2 accounts as the target, and the other node type converter can have application 2 accounts as the source and application 1 accounts as the target. This will ensure that nodes added to either application are shared with the other. (Reference: Oracle Enterprise Data Management Cloud 2022 Implementation Essentials, Module 3)