Do you have any question about this error?
Message type: E = Error
Message class: FG - Program Error Messages
Message number: 758
Message text: Administration entry was changed manually
The administration entry was changed manually. The previous status
is thus no longer saved. The user is responsible for his own
administration through a description of the external archive or some
other comment.
If an archive is in this status, basically all operators can be
used, that is, reloading and transporting in both directions. Errors
that might occur are displayed.
Error message extract from SAP system. Copyright SAP SE.
FG758
- Administration entry was changed manually ?The SAP error message FG758, which states "Administration entry was changed manually," typically occurs in the context of managing master data or configuration settings within the SAP system. This error indicates that a manual change has been made to an entry that is usually managed by the system, leading to inconsistencies or conflicts.
Cause:
- Manual Changes: The most common cause is that a user has manually changed an entry in the administration settings or master data that is usually controlled by the system or through specific transactions.
- Data Inconsistency: The manual change may have led to a situation where the data is inconsistent with other related entries or settings.
- Authorization Issues: Sometimes, the error can arise due to insufficient authorization to make changes to certain entries, leading to a conflict when the system tries to validate the changes.
Solution:
- Review Changes: Check the change logs to identify what manual changes were made. This can help in understanding the context of the error.
- Revert Changes: If possible, revert the manual changes to restore the original settings that the system expects.
- Consistency Check: Run consistency checks on the affected data to ensure that all related entries are aligned and there are no conflicts.
- Authorization Review: Ensure that the user making the changes has the appropriate authorizations to modify the entries in question.
- Consult Documentation: Refer to SAP documentation or help resources for specific guidance related to the module or transaction where the error occurred.
- Contact Support: If the issue persists, consider reaching out to SAP support or your internal IT team for further assistance.
Related Information:
By following these steps, you should be able to diagnose and resolve the issue related to the FG758 error message in SAP.
Get instant SAP help. Start your 7-day free trial now.
FG757
Error when transporting to optical archive
What causes this issue? When trying to transport a file to the optical archive, the underlying optical archive reported an error to the archive admin...
FG756
File is in optical archive
What causes this issue? Following a successful transport, the file is in the optical archive. They can be reloaded again with F040.Error message extr...
FG759
File is being made available by optical archive
What causes this issue? The archive file is currently being transported from the optical archive back to the file system. During this time, of course...
FG760
File is being read for deletion from database
What causes this issue? For document archiving, an archiving concept in two steps is used. In a first step, archive files are written. These files ar...
Click on this link to search all SAP messages.