Do you have any question about this error?
Message type: E = Error
Message class: GK - Messages for SAP Consolidation
Message number: 347
Message text: Equity item & already has an entry
The <DS:GLOS.financial_statement_item>equity item</> &V1& already has
an entry.
This could be due to the fact that the items:
are the same
have the same <DS:GLOS.subitem>subitem</> as a subassignment
have the same debit/credit sign
Error message
Specify a different equity item, a different subitem as the
subassignment, or a different debit/credit sign.
Error message extract from SAP system. Copyright SAP SE.
GK347
- Equity item & already has an entry ?The SAP error message GK347 typically indicates that there is an issue with equity items in the system, specifically that an equity item already has an entry. This can occur in various contexts, such as during the posting of financial transactions or when trying to make adjustments to equity accounts.
Cause:
- Duplicate Entries: The error often arises when there is an attempt to post a transaction that would create a duplicate entry for an equity item that already exists in the system.
- Incorrect Posting Period: The posting might be attempted in a period that is already closed or has restrictions.
- Configuration Issues: There may be issues with the configuration of the equity accounts or the way they are set up in the system.
- Data Integrity Issues: There could be inconsistencies in the data, such as missing or incorrect entries that lead to conflicts.
Solution:
- Check Existing Entries: Review the equity item in question to see if there are already existing entries. You can do this by using transaction codes like FBL3N (Display G/L Account Line Items) to check the G/L account for any existing postings.
- Correct Posting Period: Ensure that you are trying to post in the correct period. If the period is closed, you may need to open it or post in a different period.
- Review Configuration: Check the configuration settings for the equity accounts in the Financial Accounting (FI) module to ensure they are set up correctly.
- Data Consistency Check: Run a data consistency check to identify any discrepancies in the equity items. This can often be done through transaction codes like SE38 to run specific reports or programs that check for data integrity.
- Consult Documentation: Refer to SAP documentation or help files for specific guidance on handling equity items and related transactions.
- Contact Support: If the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert who can provide more tailored assistance.
Related Information:
By following these steps, you should be able to identify the cause of the GK347 error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
GK346
Recursive definition of the structure version
What causes this issue? Your definition of the stucture versions contains the recursion &V1&.System Response The system issues an error mess...
GK345
Structure version &1 does not exist
What causes this issue? Either the structure version &V1& has been mapped to a consolidation structure, or the default structure version &...
GK348
Item & requires a subitem
What causes this issue? You need to specify a <DS:GLOS.subitem>subitem</> for the <GL:financial_statement_item>FS item</> &am...
GK349
Reported data for changes in inv. equity comes from the totals database
What causes this issue? The global settings do not support the entry of additional financial data for investee equity, because this data is read from...
Click on this link to search all SAP messages.