Do you have any question about this error?
Message type: E = Error
Message class: MDG_DT_DATA_MODEL - Messages for the Configuration Workbench Model Access API
Message number: 148
Message text: Attribute names must start with ZZ* or YY* in customer landscape.
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.
MDG_DT_DATA_MODEL148
- Attribute names must start with ZZ* or YY* in customer landscape. ?The SAP error message MDG_DT_DATA_MODEL148 indicates that in a customer landscape, attribute names for data models must start with the prefixes ZZ or YY. This is a common requirement in SAP Master Data Governance (MDG) to ensure that custom attributes are easily identifiable and do not conflict with standard SAP attributes.
Cause:
The error occurs when you attempt to create or modify a data model in SAP MDG, and one or more attribute names do not adhere to the naming convention. Specifically, the attribute names must start with either ZZ or YY to signify that they are custom fields created by the customer, as opposed to standard SAP fields.
Solution:
To resolve this error, you need to ensure that all custom attribute names in your data model start with the required prefixes. Here are the steps to follow:
Identify the Attributes: Review the attributes in your data model that are causing the error. Look for any attribute names that do not start with ZZ or YY.
Rename Attributes: Modify the names of the offending attributes to start with the appropriate prefix. For example, if you have an attribute named
CUSTOM_FIELD
, you could rename it toZZ_CUSTOM_FIELD
orYY_CUSTOM_FIELD
.Update Data Model: After renaming the attributes, update your data model accordingly. Ensure that any references to these attributes in your configuration, mappings, or other related areas are also updated to reflect the new names.
Test Changes: Once the changes are made, test the data model to ensure that it functions correctly and that the error message no longer appears.
Documentation: Document the changes made to the attribute names for future reference and to maintain clarity in your data model.
Related Information:
By following these steps, you should be able to resolve the MDG_DT_DATA_MODEL148 error and ensure compliance with SAP's naming conventions for custom attributes.
Get instant SAP help. Start your 7-day free trial now.
MDG_DT_DATA_MODEL147
Object names must not start with Z* or Y* in delivery client
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MDG_DT_DATA_MODEL146
Model Package details successfully deleted
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MDG_DT_DATA_MODEL149
Attribute names must not start with ZZ* or YY* in SAP landscape.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MDG_DT_DATA_MODEL150
Data model specific structures need to be adjusted in separate activity.
What causes this issue? No transport request found for model specific structuresSystem Response Structure Information is saved but DDIC objects are ...
Click on this link to search all SAP messages.