FGL_SFIN_NGLM072 - Object entries for table &1 have been deleted from the custom.request


SAP Error Message - Details

  • Message type: E = Error

  • Message class: FGL_SFIN_NGLM - SAP AC on HANA : New G/L Migration

  • Message number: 072

  • Message text: Object entries for table &1 have been deleted from the custom.request

  • Show details Hide details


  • Self-Explanatory Message

    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.



    What else can you do?

    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.


Smart SAP Assistant

  • What is the cause and solution for SAP error message FGL_SFIN_NGLM072 - Object entries for table &1 have been deleted from the custom.request ?

    The SAP error message FGL_SFIN_NGLM072 indicates that object entries for a specific table have been deleted from the custom request. This typically occurs during transport or when changes are made to the system that affect the data in the specified table.

    Cause:

    1. Transport Issues: The error often arises when there are inconsistencies in the transport requests. If an object was deleted or modified in a way that is not properly reflected in the transport request, it can lead to this error.
    2. Manual Deletion: If someone manually deleted entries from the table in the development environment without properly managing the transport request, it can cause this error when trying to transport changes to another environment.
    3. Custom Development: Custom developments or modifications that are not properly documented or managed can lead to this error, especially if they involve database tables.

    Solution:

    1. Check Transport Request: Review the transport request associated with the changes. Ensure that all necessary objects are included and that there are no inconsistencies.
    2. Recreate the Request: If the transport request is corrupted or incomplete, consider recreating it. This may involve re-adding the necessary objects and ensuring that they are properly configured.
    3. Restore Deleted Entries: If entries were deleted manually, you may need to restore them from a backup or recreate them as needed.
    4. Check for Dependencies: Ensure that all dependent objects are included in the transport request. Sometimes, missing dependencies can lead to this error.
    5. Consult SAP Notes: Check the SAP Support Portal for any relevant notes or updates regarding this error message. There may be specific patches or updates that address this issue.

    Related Information:

    • Transaction Codes: You may want to use transaction codes like SE09 (Transport Organizer) or SE10 (Transport Organizer for Workbench Requests) to manage and review transport requests.
    • SAP Notes: Look for SAP Notes related to transport issues or the specific error message for additional guidance.
    • System Logs: Check system logs (transaction SLG1) for more detailed error messages that may provide additional context for the issue.

    If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.

    Artificial intelligence solution provided by tomco.ai.
    Disclaimer
    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Feature Free Access Free Trial
Basic SAP error explanation T-Code Explanation T-Code Explanation 2
Step-by-Step Usage Guide Step-by-Step Step-by-Step 2
Interactive SAP Coach Assistance Interactive SAP Interactive SAP 2
AI Troubleshooting for T-Code Errors AI Troubleshooting AI Troubleshooting 2

Related SAP Error Messages

Click the links below to see the following related messages:


SAP messages fall into 3 different categories: Error messages (message type = E), Warnings (W) or Informational (I) messages.

An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant