Show TOC

Syntax documentation*XDIM_MEMBER Locate this document in the navigation structure

Allowed uses: By Commit (Global in the Formula script of a DTS task), MDX, SQL

*XDIM_MEMBER {dimension}={member} [TO {member}]

This instruction is similar to the *XDIM_MEMBERSET instruction. However, although it only supports one member to be passed for the specified dimension, it permits you to specify a different destination member into which the results of the rules execution must be written.

Example Example

*XDIM_MEMBER CATEGORY=ACTUAL TO BUDGET

The above statement forces the logic to be executed reading the desired values from the ACTUAL category, but writes the results into the BUDGET category.

Multiple DIM_MEMBER instructions can be entered in the same rule, like in this example:

*DIM_MEMBER DATASRC=INPUT TO ELIM

*DIM_MEMBER PARENTDIM=NONE TO GROUP1

This feature can be used to simplify some rules expressions. For example:

#ACC1 = ([ACCOUNT].[X],[CATEGORY].[BUDGET])

#ACC2 = ([ACCOUNT].[Y],[CATEGORY].[BUDGET])

#ACC3 = ([ACCOUNT].[Z],[CATEGORY].[BUDGET])

…could become:

*DIM_MEMBER CATEGORY=ACTUAL TO BUDGET

#ACC1 = [ACCOUNT].[X]

#ACC2 = [ACCOUNT].[Y]

#ACC3 = [ACCOUNT].[Z]

End of the example.

This instruction can also be useful when the QUERY_TYPE=2 is used. In this case, if multiple dimensions must be nested on rows, a NonEmptyCrossJoin query could result. Then it might be important to run the query directly from the data region containing the source values, in order not to miss some of them in the calculation (see the MDX language documentation for an explanation of the NonEmptyCrossJoin function).

Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or by its gross negligence.