Do you have any question about this error?
Message type: E = Error
Message class: UGMD - FIN Master Data: Messages
Message number: 124
Message text: Database conversion may cause loss of data
New database tables have been generated for characteristic &V1&. This
regeneration substitutes table &V2& with table &V3&. However, there may
be circumstances in which the data of table <DS:TRAS.SE11>&V2&</> cannot
be copied to table <DS:TRAS.SE11>&V3&</> without losses.
For example, this may be the case when you shorten the length of
existing fields or when you change a field type from C (characters) to
NUMC (numeric). Deleting an existing compound of characteristics can
also cause such a situation.
Processing has been interrupted. The generation of the new table
structure has not yet begun.
Decide whether you really want to keep the changes. This is normally
only advisable if (1) no data has been posted yet, or (2) only test data
has been posted.
If you want to undo the changes that have been triggered by this
message, you can do this in the definitions of the affected InfoObjects.
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.
UGMD124
- Database conversion may cause loss of data ?Get instant SAP help. Start your 7-day free trial now.
UGMD123
An error occurred during the generation; see the log
What causes this issue? An error occurred while generating the Data Dictionary. For more detail, see the <DS:TRAN.UG_MD_GEN_LOG>Generation Log....
UGMD122
The background job must finish first
What causes this issue? A background job for changing the Data Dictionary structures has been scheduled. This job must be completed successfully befo...
UGMD125
The area must contain the required characteristic &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
UGMD126
The area uses an unknown characteristic &1
What causes this issue? The application area uses the unknown characteristic &v1&. This can occur, for example, if the application area was i...
Click on this link to search all SAP messages.