When working through the Model Mapping on MS OLAP cubes, it is important to understand how MDX members are represented, either through captions or keys.  If you are matching via captions, then the format is [Dimension].[Hierarchy].[Caption] or [Dimension].[Hierarchy].[Level].[Caption] depending on how unique the caption is (i.e. [Unit].[Company Code].[C46752]).   If you are matching via keys, then you will see an ampersand in the naming convention and the value may be dramatically different than the caption [Dimension].[Hierarchy].&[Key] (i.e. [Unit Source System].[Unit Source System].[Company].&[RE300]&[CL400]&[SR430]&[Swe467]&[X46752]).  It really depends on how the cube was built as to which method is easier to match.  In the example you showed, it looks like there is not a simple way to parse the captions to map them and the keys for the Sales DW model are a combination of multiple levels.  So the quickest way to solve the problem would be with a manual mapping of each value in both cubes by using a CASE statement. Obviously this would be difficult if you had a large number of values to map.

Be aware that the CASE statement in the Model Mapper is not MDX but actually PQL so the syntax is a bit different (see Help file for more detail: LINK ).  Here is an example:

Case(
criteria(SourceMember().MemberCaption()="Canada"
,SourceMember().MemberCaption()="France"
,SourceMember().MemberCaption()="Germany"
,SourceMember().MemberCaption()="Australia"
,SourceMember().MemberCaption()="United States")
,criteriaResults("[Organization].[Organization].&[8]"
,"[Organization].[Organization].&[11]"
,"[Organization].[Organization].&[12]"
,"[Organization].[Organization].&[13]"
,"[Organization].[Organization].&[7]")
,"")

In my example, I am mapping the Caption from one model to the Key of the other model. There are other ways to write this but it should give you an idea of the basic syntax.