FGL_SFIN_NGLM073 - Object entries for table &1 have not 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: 073

  • Message text: Object entries for table &1 have not 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_NGLM073 - Object entries for table &1 have not been deleted from the custom.request ?

    The SAP error message FGL_SFIN_NGLM073 indicates that there are object entries for a specific table that have not been deleted from the custom request. This typically occurs during transport or when trying to manage changes in the system landscape.

    Cause:

    1. Transport Request Issues: The error usually arises when there are inconsistencies in the transport request. This can happen if the objects were modified in the development environment but not properly included in the transport request.
    2. Missing Authorizations: Sometimes, the user may not have the necessary authorizations to delete or modify the entries in the transport request.
    3. System Configuration: There may be issues with the system configuration or the transport directory that prevent the deletion of entries.
    4. Incomplete Object Deletion: If an object was deleted in the development system but the corresponding entries in the transport request were not updated, this error can occur.

    Solution:

    1. Check Transport Request:

      • Go to the transaction code SE09 or SE10 to check the transport request. Ensure that all necessary objects are included in the request.
      • If you find that the objects are not included, you may need to add them manually or create a new transport request.
    2. Delete Unused Entries:

      • If you have identified that certain entries are no longer needed, you can manually delete them from the transport request. This can be done in SE09/SE10 by selecting the request and using the delete option.
    3. Check Authorizations:

      • Ensure that you have the necessary authorizations to modify the transport request. If not, contact your system administrator to grant the required permissions.
    4. Transport Directory Check:

      • Verify the transport directory settings and ensure that there are no issues with the transport paths. This can be checked in transaction code STMS.
    5. Recreate the Transport Request:

      • If the transport request is corrupted or has too many inconsistencies, consider recreating it. This involves creating a new transport request and re-adding the necessary objects.
    6. Consult SAP Notes:

      • Check for any relevant SAP Notes that may address this specific error. SAP frequently updates its knowledge base with solutions for known issues.

    Related Information:

    • Transaction Codes: SE09 (Transport Organizer), SE10 (Transport Organizer - Workbench Requests), STMS (Transport Management System).
    • SAP Notes: Search for specific SAP Notes related to transport issues or the error message FGL_SFIN_NGLM073 in the SAP Support Portal.
    • Documentation: Review SAP documentation on transport management and object handling to understand best practices and troubleshooting steps.

    If the issue persists after trying the above solutions, it may be beneficial to 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