Message type: E = Error
Message class: COM_PME_PARSER - Configuration
Message number: 110
Message text: Keyword RESTRICTION: expected
The syntax check could not identify the mandatory restriction part of a
constraint. This may be because the keyword <ZH>RESTRICTIONS:</> was
not found, or was not recognized because it was in the wrong place.
In a constraint, the sections OBJECTS: and RESTRICTIONS: are mandatory.
As soon as you enter a keyword that cannot be interpreted or an
incorrect punctuation mark ('.', ';', ',', ':', and so on) after an
object, the system tells you that it expects the RESTRICTIONS: section.
The cursor shows where the error in your entry occurs.
Check your entries:
You may have entered an incorrect keyword under OBJECTS: or CONDITION:
that leads the system to assume that you want to make entries for
RESTRICTIONS:. Check the syntax and spelling of the keywords in these
sections.
If the keyword RESTRICTIONS: is missing or written incorrectly, correct
the error.
If the keyword is there, perhaps it could not be interpreted correctly.
This could be, for example, because the preceding expression was not
closed correctly. A section is closed either with or without a period.
Several object declarations are separated by commas. Several
characteristic declarations are separated by semicolons.
If you enter several expressions under CONDITION: or RESTRICTIONS:,
separate them with commas.
Error message extract from SAP system. Copyright SAP SE.
COM_PME_PARSER110
- Keyword RESTRICTION: expected ?The SAP error message COM_PME_PARSER110 with the keyword RESTRICTION: expected typically occurs in the context of the SAP Product Master or similar areas where product data is being processed. This error indicates that the system is expecting a restriction keyword or value that is not present in the input data or configuration.
Cause: Missing Restriction Definition: The error may arise if there is a missing definition for a restriction that is required for the product or material being processed. Incorrect Syntax: If the syntax used in the configuration or data entry does not conform to the expected format, the parser may throw this error. Incomplete Data: The data being processed may be incomplete or incorrectly formatted, leading to the parser not being able to find the expected restriction.
Configuration Issues: There may be issues in the configuration settings related to product restrictions in the SAP system.
Solution: Check Data Input: Review the data being inputted for any
Get instant SAP help. Sign up for our Free Essentials Plan.
COM_PME_PARSER109
Error in predefined function &1
What causes this issue? An error occurred when you entered predefined expression &V1&.System Response The cursor shows where the error occur...
COM_PME_PARSER107
Invalid value &1 for parameter &2
What causes this issue? In constraints that add instances (objects) to a configuration (HAS_PART, or FIND_OR_CREATE), you can transfer defining attri...
COM_PME_PARSER111
'PART_OF'/'SUBPART_OF' dependency incorrect
What causes this issue? The syntax check found an error in the entry for predefined standard dependency <ZH>PART_OF</> or <ZH>SUBPA...
COM_PME_PARSER112
Table/function argument incorrect &1
What causes this issue? The syntax check found an error in table or function parameters.System Response The cursor shows where in your entry the err...
Click on this link to search all SAP messages.