Mapping members allows you to translate source values to valid members in each target dimension. If you have defined target expressions to derive the target members for a given dimension, then you don’t have to define member mapping. If you use conditional target expressions, then you can define member mapping for the remaining source values not covered by the conditions. If your data transformations can be achieved using target expression, then its highly recommended to use it instead of mapping members. Transformation using target expression perform significantly better than member mapping for large data sets.
Mappings can be shared across multiple integrations using parent location. Mappings are processed for each dimension in default order of Account, Entity, ICP, UD1, UD2, etc. You can override the mapping order by changing the calculation sequence in Application definition.