SAP ABAP Data Element PROP_NAME (Properties)
Hierarchy
☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-DWB-TOO-SCR (Application Component) Screen Painter
     ⤷ SCRP (Package) Screen Painter
Basic Data
Data Element PROP_NAME
Short Description Properties  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type PROP_NAME    
Data Type CHAR   Character String 
Length 30    
Decimal Places 0    
Output Length 30    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 0   
Medium 0   
Long 0   
Heading 0   
Documentation

The term "Properties" groups together a number of attributes for screen elements that

  • are designed mainly for SAP-internal use
  • are not part of the standard attributes of screen elements
  • for technical reasons, cannot be stored directly in the screen source in the element list, but in a special property bag.
    The property bag exists as of Basis Release 4.6C.

Properties are maintained in special processing screens that you can access by pressing the pushbutton "Properties". This pushbutton is located in the following places:

(a) In the attribute screen of a screen element

(b) In the element list, view "General attributes"

Which properties are allowed depends on the type of screen element and on the Basis release. Some of the properties may be allowed, but are supported only by special GUIs (usually WebGui and WinGui) or in the accessibility mode of the WinGui or not at all yet.
The accessibility mode is available in WinGui as of 6.40 as a special GUI mode, under which enriched information is provided to screen readers. It can be activated using the Windows menu
Start->Settings->ControlPanel->SAP Configuration
on the "Design Selection" tab page by setting the switch "Use Accessibility Mode".

Only screen elements that have a name can receive properties. For nameless screen elements, the Screen Painter does not provide the pushbutton "Properties".

There are the following main properties:

  • Text Field

    Assignment of a label to a screen field

    Allowed as of Basis Release 6.20; implemeted in WebGui as of 6.20 and in WinGui as of 6.40 (only in accessibility mode)

    The label can be a text field or a simple output field that can be at any place in the screen. In this sense, the property "text field" is an enhancement of the attributes "Label left" and "Label right".

    The property "TextField" supports screen operation for visually-impaired users. The Screen Reader can communicate to the visually-impaired user which purpose an input/output field serves, provided there is a label that can be interpreted (picked up and communicated) by the Screen Reader.

  • Tooltip Text

    Assignment of a tooltip (quick info) to a screen field

    Allowed as of Basis Release 6.20; implemented in WebGui as of 6.20 and in WinGui as of 6.40 (only in accessibility mode)

    The Tooltip can be either a text element that is defined in the program or a value that a program variable has at runtime. In this sense, the property "tooltip text" is an enhancement of the attribute "Quick info".

    The property "Tooltip Text" supports the operation of the screen by visually-impaired users. The Screen Reader can communicate to the visually-impaired user the meaning of an input/output field, provided it has a text that it can read, pick up, and communicate.

  • DisableImplicitLabels

    Suppressing all implicit strategies of the WinGui, assigning a label to a screen field

    Allowed as of Basis Release 7.00; implemented in the WinGui as of 6.40 (only in accessibility mode)

    The WinGui tries to assign a meaningful text -- in accessibility mode -- to an I/O field or a button. In addition to the explicit assignments (attributes "as label left" or "as label right" for text fields right beside each other; properties such as TextField and TooltipText for the I/O field or button), it also uses implicit strategies. The implicit strategies extend the search for text fields that carry the attribute "as label left" or "as label right" past the immediate neighboring fields to all text fields of the same row. For fields in a step loop, they also search for suitable heading fields.

    In some cases, the use of implicit strategies can lead to the assignment of undesired, unsuitable texts. The property DisableImplicitLabels therefore provides the option of switching of all implicit strategies for a particular field so that solely the explicit strategies are taken into consideration.

  • Keeptab

    Keeps the tab in the subscreen area

    Allowed as of Basis Release 6.10; implemented as of Release 6.10 in WebGui and WinGui

Sequentially pressing the tab key in the screen results in jumping to the next field to the right on the same row or to the first field in the next row, and so on. This flat sequence is broken only for the fields within a frame: If the tab jumps into the frame for the first time, then the next tab jumps to the next field within the frame until the frame is finished.
The KeepTab propertiy enhances this behavior to include areas of subscreens:
If a field is reached that belongs to an included subscreen, the next tab steps lead to all other fields of this subscreen.

  • BarcodeInput

    Processing of Barcodes

    Allowed as of Basis Release 6.20; implemented as of Release 6.20 in WebGui and SAPConsole

    This property allows you to scan composed barcodes of data labels with variable length. It makes sense only for character-type input/output fields such as CHAR or STRG.
    According to Standard EAN120 the barcode data elements (consisting of a data label each, followed by the data content) are separated by the function character 1 (FNC 1). This character is represented as the decimal ASCII character 29 ("GS").

    During the scan, the separator character is converted into the string "]C1". Within the application program, you can prompt for the string "]C1" in order to decode all data (data label and content).

  • KnowledgeObject

    Link to an object of the Knowledge Warehouse

    Allowed as of Basis Release 4.6C; implemented as of Basis Release 6.30

    This property is possible only for a special type of pushbutton, the pushbutton for the dialog help. Buttons for dialog help are intended to provide a help documentation for the screen field with which they are linked via the reference attribute. They are usually positioned to the right of this field. They are visualized as icon ICON_DIALGHELP.
    The property defines a link to a document in the Knowledge Warehouse.

  • Hyperlink

    Drag&Relate Hyperlink

    Allowed as of Basis Release 4.6C

    The Drag&Relate hyperlink is intended exclusively for SAP-internal use to support the Drag&Relate functions.
    This property cannot be used to define a link to other screen pages.

  • Speech

    Support for Speech Input

    Allowed as of Basis Release 6.20; implemented as of Release 6.20 in ITSmobile X+V generator.

    This property allows the operation of a screen through speech input. Through the attributes of the "Speech" property, it is possible to control the speech dialog at the front end and, for example, to achieve speech output.
    Speech output is activated by setting the "Speech" property (without specification of other attributes) for any screen you wish. It is then in effect solely for this screen and for all included subscreens.
    For those elements belonging to this screen that are of the type input/output field, pushbutton, radio button, and checkbox, other attributes of this property can be set as well.

    • General Speech Attributes
      • PromptText: Text for input requirement for a field - for example, "Enter a client".
      HelpText: Help text for speech input. The text is read out loud if a speech input has not been recognized.
      FilledText: Text is read out loud if a speech input has been recognized successfully.
      Grammar: Grammar for recognizing speech input.
      GrammarLnk: Grammar for recognizing speech input that is loaded as an external file.
      TimeOut: Time interval in seconds up to which help text is read out - if no speech input takes place.
      NextField: Specifies the next field with speech input.
    • Device-Specific Attributes
      • In addition to the general attributes, it is possible to specify also device-specific attributes. The evaluation of these attributes must be implementated at the front end itself - for example, through a separate X+V generator.
  • RFID

    Support of RFID Devices

    Allowed as of Basis Release 6.40, implemented as of Release 640 in ITSmobile, integrated ITS.

    This property enables the connection of RFID devices to the front end. The property can only be set for pushbuttons, whereby the pushbutton symbolizes the trigger for the RFID pistol.

    Clicking the pushbutton and "pulling the trigger" behave identically and trigger the function code set for the pushbutton.

    The following RFID attributes link individual screen fields to the RFID operation - for example, to the data transport.

    • Required RFID Attributes
      • Command: Specifies the RFID command to be executed - for example, ReadTag, WriteTag.
      TagData: Specifies the name of the screen field that contains the
History
Last changed by/on SAP  20100420 
SAP Release Created in