Do you have any question about this error?
Message type: E = Error
Message class: SABAP_DOC - ABAP Doc messages
Message number: 105
Message text: Wrong position for ABAP Doc comment in a chained statement
The ABAP-Doc-comment is located at the wrong position in the source
code.
An ABAP-Doc-comment-block is introduced by the character combination "!.
It has to be located directly in front of a declarative statement (e.g.,
data declaration, method definition, class definition).
Example
<EX>"! This is a documentation for the following constant</>
<EX>constants co_initial_value type i value 0.</>
You can use multiple lines for your documentation to document your
source code elements. In this case you have to add the character
combination "! in front of each line.
Example
<EX>"! This documentation for the following constant is documented</>
<EX>"! in multiple lines.</>
<EX>constants co_initial_value type i value 0.</>
If you want to document a block of statements by using the ABAP
colon-comma-semantic the ABAP Doc comment block must be located in front
of the identifier and must be after the colon.
Example
<EX>constants:</>
<EX> "! Initial value</>
<EX> co_initial_value type i value 0<(>,<)></>
<EX> "! Invalid value</>
<EX> co_invalid_value type i value -1.</>
Syntax check returns a warning.
Put the ABAP-Doc comment at the right position in the source code.
If the comment is not an ABAP-Doc-comment, but a standard comment and
starts with the character combination "!, you can add a space between
the characters " and ! to declare this comment as standard comment.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
SABAP_DOC105
- Wrong position for ABAP Doc comment in a chained statement ?The SAP error message SABAP_DOC105 indicates that there is an issue with the placement of an ABAP documentation comment in a chained statement. This error typically arises when the documentation comment (which starts with
*
or"
for single-line comments) is not positioned correctly in relation to the code it is meant to document.Cause:
The error occurs when:
IF
, CASE
, or method calls).To resolve the SABAP_DOC105 error, you should:
Check the Position of the Comment: Ensure that the comment is placed on a separate line before the statement it is documenting or at the end of the line, but not in the middle of a chained statement.
For example, instead of:
IF condition. " This is a comment
" Do something
ENDIF.
You should write:
" This is a comment
IF condition.
" Do something
ENDIF.
Avoid Inline Comments in Chained Statements: If you are using chained statements, avoid placing comments inline. Instead, place comments on separate lines.
Review the Code Structure: Ensure that your code structure adheres to ABAP syntax rules. If you are using multiple statements in a single line, consider breaking them into separate lines.
IF
, CASE
, and other control structures.By following these guidelines, you should be able to resolve the SABAP_DOC105 error and improve the quality of your ABAP code documentation.
Get instant SAP help. Start your 7-day free trial now.
SABAP_DOC104
ABAP Doc comments must contain documentation
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SABAP_DOC103
ABAP Doc comment is in an incorrect position
What causes this issue? The ABAP-Doc-comment is located at the wrong position in the source code. An ABAP-Doc-comment-block is introduced by the char...
SABAP_DOC106
ABAP Doc comments behind statements are not allowed
What causes this issue? The ABAP-Doc-comment is located at the wrong position in the source code. An ABAP-Doc-comment-block is introduced by the char...
SABAP_DOC107
'{@' is a reserved string in ABAP Doc
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.