Show TOC

Syntax documentation*XDIM_GETINPUTSET Locate this document in the navigation structure

Allowed uses: By Commit, MDX, SQL

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

[*APP={application}] //optional

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

[*CRITERIA {expression}] //optional

*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 database.

XDIM_GETINPUTSET serves the same purpose of XDIM_GETMEMBERSET, but it generates an SQL query instead of an MDX query behind the scenes. This implies that, while it can only be used to check for the value of input cells (that is, having entries in the fact table), it will, in most cases, deliver much better performance and scalability.

Example Example

*XDIM_GETINPUTSET ENTITY

*APP OWNERSHIP

*XDIM_MEMBERSET ACCOUNTOWN=METHOD

*XDIM_MEMBERSET CURRENCYPARENT=C_GR_FIN

*XDIM_MEMBERSET INTCO=TPNONE *CRITERIA SIGNEDDATA>71

*ENDXDIM

End of the example.

This filters all entities that in application OWNERSHIP have a value greater than 71 in account METHOD, for currencyparent=C_GR_FIN, and so on.

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.

Warning: the criteria instruction can be used to filter the members against an acceptable value range. However, currently the instruction is not able to take into account the stored sign of the selected account, and this has to be figured out manually.

Example Example

For example, if the instruction is supposed to filter a REVENUE account with a value greater than 100, the instruction should say:

*CRITERIA SIGNEDDATA<-100 // this means >100 for income accounts

because REVENUE is stored with a negative sign.

End of the example.

Similarly to XDIM_GETMEMBERSET, the XDIM_GETINPUTSET instruction is specific to the COMMIT section it is written in.

Special case: Change of dimension name across applications

The instruction *XDIM_GETINPUTSET 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_ GETINPUTSET {ThatDimension} [ AS {ThisDimension}] [={member set}]

Example Example

*XDIM_GETINPUTSET SOMEENTITY as ENTITY=[SOMEENTITY].members

*APP SOMEOWN

*XDIM_MEMBERSET ACCOUNTOWN=METHOD

*XDIM_MEMBERSET RPTCURRENCY=GROUP1

*XDIM_MEMBERSET INTCO=Non_Interco

*CRITERIA SIGNEDDATA<>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.