Do you have any question about this error?
Message type: E = Error
Message class: MC - Aggregate: views, matchcodes, lock objects
Message number: 349
Message text: Matchcodes no longer supported (-> Long text)
SAP matchcodes are no longer supported as of Basis release 6.10.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Instead of a matchcode, use a database view and, if necessary, a search
help function. The technical details are explained in CSN Note 24860.
If you have a matchcode ID of the update type "K" (implementation of F4
help through function module), make sure that the corresponding searc h
help with the same name meets the condition named in the T100 message
DH899. Afterwards, you can delete the matchcode ID without any problems
since it has become superfluous.
Error message extract from SAP system. Copyright SAP SE.
MC349
- Matchcodes no longer supported (-> Long text) ?The SAP error message MC349 "Matchcodes no longer supported" typically indicates that the system is trying to use a matchcode that is no longer available or supported in the current version of SAP. Matchcodes were used in older versions of SAP for searching and retrieving data, but they have been largely replaced by more modern search functionalities.
Cause:
- Deprecated Functionality: Matchcodes have been deprecated in favor of more efficient search methods, such as the use of indexes and full-text search capabilities.
- Configuration Issues: The system may be configured to use matchcodes that are not defined or have been removed.
- Custom Code: Custom programs or reports may still be referencing matchcodes that are no longer supported.
Solution:
- Update Custom Code: If you have custom programs or reports that are using matchcodes, you will need to update them to use the new search functionalities provided by SAP. This may involve replacing matchcode calls with appropriate database queries or using the new search tools.
- Check Configuration: Review the configuration settings in your SAP system to ensure that no obsolete matchcodes are being referenced. You may need to remove or update these settings.
- Use Alternative Search Methods: Familiarize yourself with the new search functionalities available in your version of SAP, such as the use of indexes or the SAP Fiori search capabilities.
- Consult Documentation: Refer to the SAP documentation for your specific version to understand the recommended practices for searching and retrieving data without matchcodes.
Related Information:
By addressing the underlying causes and updating your system's configuration and custom code, you should be able to resolve the MC349 error and improve your data retrieval processes in SAP.
Get instant SAP help. Start your 7-day free trial now.
MC348
Matchcodes are not supported in Unicode systems (see long text)
What causes this issue? In Unicode systems, matchcodes are not supported.System Response The system issues an error message and will not allow you t...
MC345
Error occurred when running sapmaco in the background for & -> long text
What causes this issue? An error occurred during the execution of SAPMACO in the background. The cause of the error can be found in the SAPMACO log.S...
MC350
Lock object & created
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MC351
Table & not found
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.