Do you have any question about this error?
Message type: E = Error
Message class: FGL_SFIN_NGLM - SAP AC on HANA : New G/L Migration
Message number: 070
Message text: Different attributes between &1/&2 und &3/&2 (s. table &4)
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.
The SAP error message FGL_SFIN_NGLM070 indicates that there is a discrepancy in the attributes of the specified objects in the system. This error typically arises in the context of financial accounting and can occur during processes such as posting or reporting.
Cause:
The error message suggests that there are different attributes between two sets of objects (e.g., accounts, cost centers, etc.) that are being compared. The placeholders in the message represent:
This discrepancy can occur due to:
To resolve this error, you can follow these steps:
Identify the Objects: Check the specific objects mentioned in the error message. Look at the details provided in the error to understand which accounts or entities are involved.
Review Attributes: Compare the attributes of the objects in question. You can do this by checking the relevant master data in the SAP system (e.g., using transaction codes like FS00 for G/L accounts, or OX19 for cost centers).
Check Configuration: Ensure that the configuration settings for the financial accounting module are consistent. This may involve checking settings in the Financial Accounting (FI) and Controlling (CO) modules.
Synchronize Data: If there are discrepancies in the master data, you may need to update or correct the attributes to ensure consistency across the system.
Consult Documentation: Refer to SAP documentation or notes related to this error message for additional guidance and troubleshooting steps.
Testing: After making the necessary changes, perform a test transaction to ensure that the error no longer occurs.
By following these steps, you should be able to identify and resolve the cause of the FGL_SFIN_NGLM070 error message in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
FGL_SFIN_NGLM069 No object entry for table &1 was created in the customizing request
Self-Explanatory Message Since SAP believes that this specific error message is ...
FGL_SFIN_NGLM068 Object entries for table &1 have been created in the customizing request
Self-Explanatory Message Since SAP believes that this specific error message is ...
FGL_SFIN_NGLM071 Reset of allocation configuration was failed (ledger &1, table &2)
Self-Explanatory Message Since SAP believes that this specific error message is ...
FGL_SFIN_NGLM072 Object entries for table &1 have been deleted from the custom.request
Self-Explanatory Message Since SAP believes that this specific error message is ...
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.