1z0-1086-22 - Oracle Enterprise Data Management Cloud 2022 Implementation Professional

When you create a map binding in a dimension, you are creating a mapping relationship between a source node type and a target node type within that dimension. This enables you to transform properties or derive values from source nodes to target nodes when sharing data across applications. When you create a map binding called Account Mapping in the Planning Account dimension, three objects are created in the Planning application: an Account Mapping hierarchy set that contains hierarchies for mapping accounts from GL to Planning; an Account Mapping node set that contains nodes for mapping accounts from GL to Planning; and a node type converter with the Account (GL) node type as source and Account Mapping (Planning) node type as target that defines how properties are transformed or derived from source nodes to target nodes. A map binding does not create a new dimension or a viewpoint in a view. References: Working with Map Bindings - Oracle Help Center; Working with Node Type Converters - Oracle Help Center

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)

A custom validation is a validation that checks whether nodes meet certain criteria based on their actions or properties using an expression that returns a Boolean value. To enable a custom validation, you need to meet the following conditions: define a valid expression and a failure message for the custom validation; configure at least one trigger action and/or a trigger property for a node set or hierarchy set that uses the custom validation. You do not need to define a derived property of the Custom Validation node type or an expression that returns a Boolean value and a failure message, because these are not supported by Oracle Enterprise Data Management Cloud. References: Working with Custom Validations - Oracle Help Center