Which two statements are true about importing Planning dimensions?
A request was submitted that triggered an approval policy. However, there are not enough approvers available to satisfy the terms of the policy.
What are two resolutions?
You have mapped accounts from two different general ledger applications to your Planning application. What do you do when it's time to synchronize the changes by exporting the mappings?
When you have mapped accounts from two different general ledger applications to your Planning application, you need to run two separate exports, one for each source-to-target location, when it’s time to synchronize the changes by exporting the mappings. This way, you can export the mapping data from each source node type to the corresponding target node type using the appropriate node type converter and map binding. You do not need to run three exports, one for each source and one for the target, because this would not export the mapping data correctly. You do not need to run a single export for the target that contains all mappings for both sources, because this would not use the correct node type converters and map bindings for each source-to-target pair. You do not need to run four exports, one for each viewpoint involved in the mapping, because this would be redundant and inefficient. References: Working with Requests - Oracle Help Center3; Creating Mapping Viewpoints - Oracle Help Center2
You need nodes added to your General Ledger application's account dimension to be shared to your Planning application's account dimension.
Which two steps can you take to facilitate this?
These are two steps that can facilitate sharing nodes between applications. The other options are not valid. You do not need to create node type converters for this scenario, because both applications use the same node type for accounts.