Child pages
  • Variable screen F4 help issues in portal runtime
Skip to end of metadata
Go to start of metadata

Please check the note: 1843538 - Common issue with variable/selection/filter screen F4 value

1. After executed the query in portal, when click "f4 help" of selection screen value, it shows Maximum Records allowed "1000 ".

   This is the standard behavior. In the new Web Java Runtime, the default filtering count is 1000 and it cannot be changed. Unfortunately there is no workaround to change it as well.

2.  F4 help text not working properly

       Please check the note: 1080863  - FAQ: Input helps in Netweaver BI     

In general, the following settings are relevant and can be made for the input help for characteristics:

    o  Display: Determines the display of the characteristic values with  the following options "Key", "Text", "Key and text" and "Text and key".
    o  Text type: If there are different text types (short, medium andlong text), this determines which text type is to be used to display the text.
    o  Attributes: You can determine for the input help which attributes of the characteristic are displayed initially. 
        When you have a large number of attributes for the characteristic, it makes sense to display only a selected number of attributes.
        You can also determine the display sequence of the attributes.
    o  F4 read mode: Determines in which mode the input help obtains its characteristic values. This includes the modes "Values from themaster data table (M)",
         "Values from the InfoProvider (D)" and "Values from the Query Navigation (Q)".
        Note that you can set a read mode, on the one hand, for the input help for query execution (for example, in the BEx Analyzer or in
        the BEX Web) and, on the other hand, for the input help for the  query definition (in the BEx Query Designer).

You can make these settings in InfoObject maintenance using transaction RSD1 in the context of the characteristic itself, in the InfoProvider-specific characteristic settings using transaction RSDCUBE in the context of the characteristic within an InfoProvider or in the BEx Query Designer in the context of the characteristic within a query. Note that not all the settings can be maintained in all the contexts. The following table shows where certain settings can be made:

         Setting               RSD1    RSDCUBE    BExQueryDesigner        
         Display                X           X                    X         
        Text type              X           X                    X         
        Attributes              X          -                       -         
        Read mode          - 
        Query execution   X         X                      X          
         Query definition   X         -                        -

  Note that the respective input helps in the BEx Web as well as in the   BEx Tools enable you to make these settings again after executing the  input help.

3. Variable entry * displayed as \*

Characters such as '*', ';', '!', '>', '<', '=' etc. have a special meaning since they are used as operators, separators, wild cards etc. The escape character was introduced via note 1133107 to ensure that the parser correctly interprets special characters when these occur as part of the master data and does not consider them in the context of their special meaning.
Please check the note: 1483260 for more information.


  • No labels