Bex F4 help not working correctly

[Former Member]

When running a Bex query on a DSO, and a variable prompt appears, and the user clicks on the F4 help to display values, it is getting Values in InfoProvider, even though the InfoObject is set for “Values in Master Data Table”.  This causes the F4 to run a long time, because the DSO is large.  In some cases, it times out after 20 minutes.

Details:

0FISCPER:  “Values in Master Data Table” for Query Def. Filter Value Selection and for Query Execution Filter Val. Selection.

DSO:  there is no override for these properties on 0FISCPER.

BW 7.3  SP7

The problem occurs in all versions of Bex – 3.x, 7.x, rsrt, run on web from Query Designer, run in Bex Analyzer.

This might have started with the 7.3 upgrade, I’m not sure, but I can’t find any notes to fix it.

[Former Member · Accepted solution]

Im on BW 7.3 SP4 and setting the InfoObject property "Query Execution Filter Val. Selectn" to master data, correctly retrieves master data independently if the query is run on a MultiProvider (with 2 cubes) or DSO.

Anyway, the setting on the DSO overrides the setting on the InfoObect-> Did you already try this?

Best regards,

Victor

[Former Member · Accepted solution]

I did try changing the DSO override setting to Values in Master Data (mode M), and then it works.  It comes back fast.  Then I changed the DSO override setting back to blank (no override), and it reverted back to mode D, even though the InfoObject is mode M.

I am logging it with SAP.

[Former Member · Accepted solution]

Hi Kurt,

Did you get anything on this from SAP or anyone? I am facing similar issue -  while trying to have only values from infoprovider in one of the infoObject for variable selection few random values are populating when executing query.

Please let me know if you have got some solution or any lead on this.

Regards,

Neha

[Former Member · Accepted solution]

SAP provided the solution.  The RSDCHABAS table did not match our settings in rsa1.  I went into 0FISCPER, changed to mode D, activated, then changed to mode M, activated.  Then transport 0FISCPER to QA and Prd systems.

[Former Member · Accepted solution]

Hi Kurt -

Thanks for sharing the solution with us. But I did not understand what you mean by "I went into 0FISCPER, changed to mode D, activated, then changed to mode M, activated" Can you please explain in detail what exactly you did.

[Former Member · Accepted solution]

The RSDCHABAS table did not match our settings in rsa1. 

RSDCHABAS showed: 

CHABASNM   OBJVERS   F4DEFAULT   F4QUERYEXEC

0FISCPER       A                 M                  Q

In RSA1, 0FISCPER showed "Values in Master Data Table" for Query Execution Filter Val. Selection, which is mode M, even though the table showed mode Q.  That was the problem.

I went into 0FISCPER, changed to mode D (only values in InfoProvider), activated, then changed back to mode M (Values in Master Data Table), activated.  That fixed the table entry so it now looks like this:

CHABASNM   OBJVERS   F4DEFAULT   F4QUERYEXEC

0FISCPER       A                 M                   M

[ravi_chandra3]

Hi

You can restrict the F4 values with some logic with the help of BADI, so that performance will be improved. This BADI is present in the 7.3 only.

regards,

RaviChandra.

[Former Member]

Hi,

Please check the below doc to improve performance of F4 help.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20ecb78c-374a-2d10-c6af-f024f19b7...

Thanks,

Reshma M.

[Former Member]

Thanks for the document.  The problem is our system isn't behaving the way the document says it should.  The characteristic is set to M mode, but it's behaving like D mode.  I can see the SQL statement in SM51, and it is joining to the DSO table when getting the fiscal period values.