How To Fix SDDL_PARSER_MSG106 - : was expected instead of "&1"

SAP Error Message - Details

• Message type: E = Error

• Message class: SDDL_PARSER_MSG - Message Class for DDL Parser

• Message number: 106

• Message text: : was expected instead of "&1"

What causes this issue?

A list of input parameters has the following form:
[<(><<)>Annotation_1>] <(><<)>r_par_1>:<(><<)>Namespace_1>.<(><<)>Typ_1>
[<(><<)>Post_Annotation_1>],
...

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

[<(><<)>Annotation_n>] <(><<)>r_par_n>:<(><<)>Namespace_n>.<(><<)>Typ_n>
[<(><<)>Post_Annotation_n>]
The individual parameters are separated by commas; no comma must appear
after the last parameter. (<DS:ABEN.CDS_F1_DEFINE_TABLE_FUNCTION>CDS
Table Functions</>)

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SDDL_PARSER_MSG106 - : was expected instead of "&1" ?

  The SAP error message SDDL_PARSER_MSG106 typically indicates a problem with the syntax or structure of a Security Descriptor Definition Language (SDDL) string. This error occurs when the parser encounters an unexpected token or type in the SDDL string, which does not conform to the expected format.
  
  Cause:
  The error message <type name> was expected instead of "&1" suggests that the parser was expecting a specific type (like a SID, ACL, or other SDDL component) but found something else (represented by "&1"). This could be due to:
  
  Syntax Errors: There may be a typo or incorrect formatting in the SDDL string.
  Invalid Characters: The presence of invalid characters or symbols that are not recognized by the SDDL parser.
  Incorrect Structure: The overall structure of the SDDL string may not follow the required conventions, such as missing components or incorrect ordering.
  Unsupported Types: The SDDL string may reference types or components that are not supported in the current