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: SRF_AUTHORING - Message class for SRF Authoring
Message number: 143
Message text: Invalid XSD built-in type name &1. Use a valid built-in type.
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
SRF_AUTHORING143
- Invalid XSD built-in type name &1. Use a valid built-in type. ?The SAP error message SRF_AUTHORING143 indicates that there is an issue with the XML Schema Definition (XSD) being used in your SAP application. Specifically, it suggests that an invalid built-in type name has been referenced in the XSD. This can occur when the XSD is trying to use a type that is not recognized or is incorrectly specified.
Cause:
- Invalid Type Name: The type name specified in the XSD does not match any of the built-in types defined in the XML Schema specification.
- Typographical Error: There may be a typo in the type name, leading to the error.
- Namespace Issues: The type may be defined in a different namespace that is not properly referenced in the XSD.
- Version Compatibility: The XSD may be using types that are not supported in the version of SAP you are using.
Solution:
- Check Type Names: Review the XSD file and ensure that all type names are valid and correctly spelled. Refer to the XML Schema specification for a list of built-in types.
- Namespace Declaration: Ensure that the correct namespaces are declared in the XSD. If the type is defined in a different namespace, make sure to include the appropriate namespace prefix.
- Use Valid Built-in Types: Replace any invalid type names with valid built-in types. Common built-in types include
string
,int
,boolean
, etc.- Validate the XSD: Use an XML/XSD validation tool to check the XSD for errors. This can help identify any issues with the schema.
- Consult Documentation: Refer to SAP documentation or community forums for guidance on the specific types supported in your version of SAP.
Related Information:
By following these steps, you should be able to resolve the SRF_AUTHORING143 error and ensure that your XSD is correctly defined.
Get instant SAP help. Sign up for our Free Essentials Plan.
SRF_AUTHORING142
Type ID is mandatory.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SRF_AUTHORING141
Query ID &1 in query parameter &2 of report definition &3 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...
SRF_AUTHORING144
You cannot use XSD built-in type for type ID &1 for complex element &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SRF_AUTHORING145
No built-in data type assigned. Data type defaulted to '&1'.
What causes this issue? Elements with simple content (that is without child elements) and attributes must have a data type assigned. No data type was...
Click on this link to search all SAP messages.