sapdev logo background
sapdev logo sapdev logo
Comments

SAP SYNTAX CONVENTIONS documentation, setup help and example usage



Return to SAP documentation index


ARTICLE

Syntax Conventions in the ABAP Keyword Documentation
The ABAP keyword documentation uses the following syntax conventions:

  • ABAP words are displayed in uppercase letters.


  • Example:

    APPEND, NON-UNIQUE, INTO

  • Operands are displayed in lowercase letters.


  • Example:

    dobj, dbtab

  • Parts of statements whose syntax diagrams are shown in another place are displayed as pseudo syntax.


  • Example:

    selscreen_options, list_options

  • Periods, commas, colons, and parentheses are displayed as normal. They are part of the ABAP syntax.


  • Example:

    . : , ()

  • Operators are displayed as normal. They are part of the ABAP syntax.


  • Example:

    +, -, *, /

  • Parts of statements that are optional are displayed in square brackets [ ] . A list of parts of statements in square brackets means that some or all of the parts can be used. If at least one part must be used, this is noted in the text. Square brackets are not a part of ABAP syntax. (Exception: table expressions ).


  • Example: :

    [NO-GROUPING] [NO-SIGN] [NO-ZERO]

  • Vertical lines | between parts of statements mean that only one of the parts listed within a statement can be used. A vertical line always joins immediate neighbors. Lines are not a part of ABAP syntax. (Exception: delimiters of string templates

  • ).

    Example:

    DDMMYY | MMDDYY | YYMMDD

  • Curly brackets { } group together related parts of statements, for example on the right or left of vertical lines. Curly brackets are not part of ABAP syntax. (Exception: embedded expressions in string templates ).


  • Example:

    {NO EDIT MASK}|{EDIT MASK mask}

  • A string of dots means that other parts of the statement can be included at this point.


  • Example:

    ... AS CHECKBOX
    Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved




    SYNTAX_CHECK_GUIDL
    SYNTAX_ERROR_GLOSRY




    comments powered by Disqus