Prompt "show value help" button for GL Account variable doesn't display all possible values

[former_member690380]

Hello,

I have a bex query that uses variable for GL Account in filters. Now when I try to use that query in AO workbook, It does prompt for value. But when click on "show value help" button, it doesnt display all possible values. how do I make it display all possible values?

Thanks

[former_member690380]

Please advise. thanks

[former_member690380]

Thanks mine is set to default(1000)but it only shows like 5 or 6.

Attached is the screenshot , top part is what shows up when I click on show value help for the variable. Bottom part

[gregor_dieckmann · Accepted solution]

Hi,

the value help in the variable context usually returns only posted values (corresponding to the so called 'read mode' of the value help). It seems that in your case the read mode 'D' (for 'dimension', i.e. posted values in the InfoProvider) is used.

To my knowledge the only way to force to use the read mode 'M' (for master data' is to implement the BADI RSR_VARIABLE_F4_RESTRICT_BADI; there you can set the read mode, cf. the documentation of the BADI.

Regards,

Gregor

[VijayetaSharma]

Number of items displayed are restricted by AO and BW admin setting you can change that count. Or you can search for patterns. By default 1000 members are displayed for performance reason.

Change

Setting For Analysis Plug-in

Change Ao_app.config paramert shown below

FetchMemberLimit= 1000 (default value) or any integer value

[former_member690380]

Thanks mine is set to default(1000)but it only shows like 5 or 6.

Attached is the screenshot , top part is what shows up when I click on show value help for the variable. Bottom part

ows what variable help in AO workbook variable pop up screen shows. Bottom part shows Infoobject data. e.g. why is 4600 not showing up?

[VijayetaSharma]

Please check infoobject and BEx query settings. Check if they are set as navigational/ master data/ infoprovider etc. I am assuming it may be set as navigational (either at info object level or BEx query level).
If that is that case, rest of F4 / LOV's are impacted by rest of of the query filters. In other words if you consider rest of the query filter then your result will end up with 5-6 GL Accounts.

Thanks