Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: VSCE - Messages for SCE
Message number: 358
Message text: Dependency &1 contains unsupported syntax &2
Dependency contains syntax that is not supported in the knowledgebase.
The dependency will not be copied to the knowledgebase.
Check if the dependency can be formulated in an alternative way without
using the unsupported syntax.
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.
VSCE358
- Dependency &1 contains unsupported syntax &2 ?The SAP error message VSCE358 indicates that there is a dependency in your ABAP code that contains unsupported syntax. This typically occurs when the system encounters a syntax that it cannot process or recognize, which can happen for various reasons, such as using outdated or incorrect syntax, or trying to use features that are not supported in the current context.
Cause
- Unsupported Syntax: The dependency might be using a syntax that is not supported in the version of SAP you are using.
- Incorrect Code: There may be a typo or logical error in the code that leads to the unsupported syntax.
- Version Compatibility: The code may be written for a different version of SAP that supports certain features that are not available in your current version.
- Missing Dependencies: Sometimes, the error can arise if there are missing or incorrectly defined dependencies in your project.
Solution
- Review the Code: Check the specific line of code mentioned in the error message. Look for any syntax errors or unsupported constructs.
- Update Syntax: If you find that the syntax is outdated or incorrect, update it to conform to the current standards of the ABAP language.
- Check Documentation: Refer to the SAP documentation for the version you are using to ensure that the syntax you are using is supported.
- Use Transaction SE80: Use the Object Navigator (transaction SE80) to analyze the object and its dependencies. This can help you identify where the unsupported syntax is being used.
- Consult SAP Notes: Check the SAP Support Portal for any relevant notes or updates that might address this issue.
- Testing: After making changes, test the code to ensure that the error is resolved and that the functionality works as expected.
Related Information
By following these steps, you should be able to identify and resolve the cause of the VSCE358 error in your SAP environment.
Get instant SAP help. Sign up for our Free Essentials Plan.
VSCE357
Procedure &1 to &2 not supported
What causes this issue? The procedure is assigned to a characteristic or characteristic value.System Response The procedure is not copied to the kno...
VSCE356
Action &1 to &2 not supported
What causes this issue? The 'Incl. actions (converted to procedures)' option is not selected.System Response The action will not be copied...
VSCE359
Variant table &1 does not exist on date &2
What causes this issue? The variant table does not exist for the date on which the runtime version is generated. The variant table was possibly creat...
VSCE360
Table &1 has no entry in column &2
What causes this issue? You cannot process variant tables with empty cells in the IPC.System Response Generation of the knowledge base is terminated...
Click on this link to search all SAP messages.