Using Attributes in Maps for Leaf Data Transfer

You can use Maps with Attributes to copy leaf-level data from one analytic model to another, from a master model to an analytic model, or from an analytic model to a master model. This feature is not designed to transfer data from HACPM_Financial to analytic models.

Attributes provide a way to group a set of leaf dimension members. The group can be composed of leaf members at different levels or in different parent structures within a dimension. Thus, it may be more efficient for you to copy leaf data between models using attributes to describe the set of members, instead of specifying each member you want to copy.

Attributes do not have data associated with them directly. Attributes point to base dimension leaf members which have data associated with them. When you transfer data to or from an attribute, you are copying data to or from the associated base dimension leaf members.

The Map must be of Type Data and must Transfer only Leaf data.

There are three methods to choose from:

• Attribute in Source to Attribute in Target (one to one)
• Attribute in Source to Dimension in Target (one to one)
• Dimension in Source to Attribute in Target (one to many)

Attribute in Source to Attribute in Target (One-to-One)

This method copies the data for source base leaf members to corresponding target base leaf members.

• Specify Filter Type LeafMembers in Source to LeafMembers in Target, or MemberAndBelow in Source to MemberAndBelow in Target.
• Specify Match Criteria Common if the base leaf members associated with the source and target are not identical.
• The attribute member names can be the same or different between source and target. For example, the attribute name in the Source could be USA/Can and the attribute name in the Target could be US and Canada.
• You can use variables and variable expressions with attribute and dimension member names.

Example 1

The following example copies leaf-level data from Everest Cycles to My Cycles, and both models have a Region attribute. Leaf data associated with the Region attribute USA/Can is copied to My Cycles.

A scope defines which data in My Cycles will be used in the calculation. In this case, no variables are in use, but you can use them if you wish.

Here is a look at the Target data before the calculation is run.

A calculation clears data in the Target, runs the map, and aggregates data.

Here is a look at the Target data after the calculation is run.

Attribute in Source to Dimension in Target (One-to-One)

This method copies the data for source base leaf members to corresponding target dimension leaf members.

• Specify Filter Type LeafMembers in Source to LeafMembers in Target, or MemberAndBelow in Source to MemberAndBelow in Target.
• Specify Match Criteria Common if the base leaf members associated with the source and target are not identical.
• The source attribute member names can be the same or different than the target dimension member names. For example, the attribute name in the Source could be USA/Can and the dimension member name in the Target could be North America.
• You can use variables and variable expressions with attribute and dimension member names.

Example 2

The following example copies leaf-level data associated with the Region, USA/Can attribute from Everest Cycles to the America's hierarchy in the Company dimension in My Cycles.

A scope defines which data in My Cycles will be used in the calculation. In this case, no variables are in use, but you can use them if you wish.

A calculation clears Target data, runs the map, and aggregates data.

Here is a look at the Target data after the calculation is run.

Dimension in Source to Attribute in Target (One-to-Many)

This method copies the data from a source dimension member to all corresponding target base leaf members associated with the attribute.

• Specify Filter Type FixedMember in Source to LeafMembers in Target.
• Match Criteria is ignored on the row that refers to the attribute.
• The source dimension member names can be the same or different than the target attribute names. For example, the dimension member name in the Source could be Europe and the attribute name in the Target could be EMEA.
• The source dimension member can be a roll-up member or a leaf member. Its data will be copied to each of the leaf base dimension members associated with the Target attribute. You copy data for only one source dimension member at a time.
• You can use variables and variable expressions with attribute and dimension member names.

Example 3

The following example copies the data for the fixed member Europe in the Company dimension from Everest Cycles to all base dimension leaf members associated with the EMEA hierarchy in the Region attribute in My Cycles. This is a one-to-many operation.

Note that Europe is a parent-level member. You can use any level of member as the Source.

A scope defines which data in My Cycles will be used in the calculation. This example uses variables. 

Here is a look at the Source data in Everest Cycles for Europe.

A calculation clears Target data, runs the map, and aggregates data.

Here is a look at the Target data in My Cycles after the calculation is run. Notice that the same data was copied to each base leaf dimension member that is associated with the EMEA attribute. This is a one-to-many operation.