Skip to Content

Within this post I want to introduce few interesting facts about this table. A first fact (and very obvious one) is that table is dedicated to frontend requirements of particular BW system. The minimum frontend requirements for any backend Support Pack are stored here. Below see description of parameters stored in the table. Most of them are not documented at all. The case might be that are supposed to be used only internally by SAP. We all know that sometimes even internal settings may help in specific situations. That was also my motivation to write this blog post.

I used to analyze SAP BW standard code in order to explore parameters meaning. Might be that I’m not always right about their meaning. Therefore I would encourage you to share your experience with the parameters. On other hand there is at least one SAP note discussing some of parameters – 1510916 – Collective Note: RS_FRONTEND_INIT parameters. Notice that in the most cases listed below parameters set to X means it is switch ON – enabled.

 

1.    Values in this table are being customized by calling transaction RS_FRONTEND_INIT.

 

2.    Table validation from Solution Manager (SolMan) – content of this table can be validated from SolMan by Configuration Validation functionality. By this values are compared and validated between one reference system and several target systems.

 

3.    Meaning of parameters: VER_MIN_ANA*:

 

a.    VER_MIN_ANA:        minimum revision of BExAddin.dll, e.g. 140

b.    VER_MIN_ANA_3X:   minimum revision of sapbex.xla

c.    VER_MIN_ANA_7X:   minimum revision of BExAnalyzer.xla

d.    VER_MIN_ANA_SAPBEX0: minimum revision of RRMX launcher (sapbex0.xla)

 

4.    Meaning of parameter ANA_CTX_SENS_DBL_CLK: activation of context sensitive double click functionality within navigation over hierarchy nodes in BW report’s output. 1345468 – BExAnalyzer: context sensitive double click on hier. nodes

 

5.   ANA_FLAG_EXAMPLE – setting of BEx Query Analyzer? , e.g. Y

6.   ANA_SINGLEDPREFRESH – If you have a workbook with several queries and you aim to refresh single query set this to X. , e.g. X

7.   ANA_USE_INPUT_TABLE – setting of BEx Query Analyzer, e.g. X

8.   ANA_USE_SIDGRID – setting of BEx Query Analyzer, e.g. X

9.   ANA_USE_TABLE – setting of BEx Query Analyzer, Performance improvement for frontend/backend communication, 1179647 – Performance: Network load in BEx Analyzer, e.g. X

10. BUFFER_CONTAINS_DATA – Special usage of note 1094799 – Corrections in the BEx Analyzer server runtime, e.g. X

11. OS_FLAG_EXAMPLE – ? , e.g. Z

12. QD_EXCLUSIVE_USER – setting of BEx Query Designer, used to restrict access to Query Designer 7.x. By this you can protect your BW 3.x based queries from accidental and unwanted migration to 7.x version. 962530 – NW04s: How to restrict access to Query Designer 2004s

13. QD_FLAG_EXAMPLE – setting of BEx Query Designer, ? , e.g. X

14. SERVER_VERSION – version of SAP BW backend, format: XXXYY, XXX – BW version, YY – Support Pack level, e.g. 70019

15. TEXT_VERSION – allows to force text cache update on all frontends, e.g. 0002

16. VER_ACT_ANA – actual version of BEx Query Analyzer, e.g. 140

17. VER_ACT_OS – actual version of BEx Query Analyzer, e.g. 0

18. VER_ACT_QD – actual version of BEx Query Designer, e.g. 229

19. VER_ACT_RD – actual version of BEx Query Report Designer, e.g. 132

20. VER_ACT_SEL – actual version of BEx Query Analyzer, e.g. 0

21. VER_ACT_WAD – actual version of BEx Web Application Designer, e.g. 154

22.VER_MIN_OS – minimum version Operation System, e.g. 0

23. VER_MIN_QD – minimum version of BEx Query Designer, e.g. 229

24. VER_MIN_RD – minimum version of BEx Report Designer, e.g. 132

25.VER_MIN_SEL – ? , e.g. 0

26. VER_MIN_WAD – setting of BEx Web Application Designer, e.g. 143

27. WAD_OBJ_VERSION – setting of BEx Web Application Designer, e.g. 3

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply