Show TOC

Syntax documentation*XDIM_GETMEMBERSET Locate this document in the navigation structure

Allowed uses: By Commit, MDX, SQL

*XDIM_GETMEMBERSET {dimension} [={member set}]

[*APP={application}] //optional

[*XDIM_MEMBERSET {dimension} [={member set}] //as many of these as needed

[*QUERY_TYPE= 0 | 1 | 2] //optional

*CRITERIA {expression} //required

*ENDXDIM

This instruction filters the members of the selected region for a given dimension according to their compliance with some user-defined criteria that must be met by the values in the application.

Example Example

*XDIM_GETMEMBERSET ENTITY=[ENTITY].[PARENT1].CHILDREN

*APP=OWNERSHIP

*XDIM_MEMBERSET INTCO=I_NONE

*CRITERIA [ACCOUNTOWN].[METHOD]>1

*ENDXDIM

End of the example.

This filters all children of entity PARENT1 to only those that in application OWNERSHIP have a value greater than 1 in account METHOD, intercompany I_NONE.

For all the dimensions not specified in the instruction, the search is performed in the corresponding members of the selected region. For example, the category and period are those for which the logic was being executed.

This instruction can be useful to restrict the scope of a logic execution where you have selected a large region of data to process. For example, a currency conversion selected for all entities could be automatically limited to only those entities that have a value in a specified account.

Another use of this feature could be to break a complex modeling logic into independent sections separated by multiple COMMIT instructions, and to only execute those for which some specific accounts have changed.

Another possibility is to trigger a different type of logic based on the value of an account. For example a FORECAST logic could only be executed for just those months where [account].[One_If_Forecast]=1.

Special case: Change of dimension name across applications

The instruction *XDIM_GETMEMBERSET can redefine the name of the dimension being filtered, if, when querying a different application, such dimension has a different name than in the source application.

The syntax supports an optional AS statement as follows:

*XDIM_ GETMEMBERSET {ThatDimension} [ AS {ThisDimension}] [={member set}]

Example Example

*XDIM_GETMEMBERSET SOMEENTITY as ENTITY=[SOMEENTITY].members

*APP OWNERSHIP

*XDIM_MEMBERSET RPTCURRENCY=GROUP1

*XDIM_MEMBERSET INTCO=Non_Interco

*CRITERIA [ACCOUNTOWN].[METHOD]<>0

*ENDXDIM

In the above example the members of the ENTITY dimension are extracted from the members of the SOMEENTITY dimension existing in the SOMEOWN application.

End of the example.