Do you have any question about this error?
Message type: E = Error
Message class: FAA_POST - FIAA Posting Messages (Object-Oriented Kernel)
Message number: 123
Message text: Posting generates double entries for asset document &1 &2 &3 &4
The posting generates several entries for the same asset document.
The posting <ZH>cannot</> be carried out.
Check the cause of the incorrect document creation:
Splitting of a fixed asset balance sheet account with document
splitting:
Correct the setting so that asset accounts are <ZH>not</> split, but
instead are defined as natural accounts.
System error:
Create a customer message for SAP Support if an error occurs.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
FAA_POST123
- Posting generates double entries for asset document &1 &2 &3 &4 ?The SAP error message FAA_POST123 indicates that there is an issue with posting an asset document that results in double entries. This typically occurs in the Asset Accounting (FI-AA) module when the system detects that the posting would create duplicate entries for the same asset document.
Causes:
- Duplicate Posting: The most common cause is that the same asset document is being posted more than once, either due to user error or a system issue.
- Incorrect Configuration: There may be configuration issues in the asset accounting settings that allow for duplicate entries.
- Batch Input Sessions: If batch input sessions are being used, they may be attempting to post the same document multiple times.
- Custom Code: If there are custom enhancements or user exits that manipulate asset postings, they may inadvertently cause duplicate entries.
- Data Integrity Issues: There may be issues with the underlying data, such as incorrect asset master data or transaction data.
Solutions:
- Check for Duplicate Entries: Review the asset documents in the system to ensure that the document you are trying to post has not already been posted. You can use transaction codes like AW01N (Asset Explorer) to check the asset history.
- Review Configuration: Ensure that the configuration settings for asset accounting are correct and do not allow for duplicate postings. This includes checking the document types and number ranges.
- Batch Input Sessions: If using batch input sessions, check the sessions for any duplicate entries and correct them before processing.
- Custom Code Review: If there are any custom developments related to asset postings, review the code to ensure it does not create duplicate entries.
- Data Consistency Check: Run data consistency checks to identify and resolve any issues with asset master data or transaction data.
- Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional guidance.
Related Information:
If the problem persists after following these steps, it may be necessary to involve your SAP support team or consult with SAP directly for further assistance.
Get instant SAP help. Start your 7-day free trial now.
FAA_POST122
Data incomplete for company code &1 fiscal year &2
What causes this issue? Once SAP Note 2305475 has been adopted, either through advance correction or by importing the relevant Support Package, the d...
FAA_POST121
CCode &2: Balance carryforward for account &3 in ledger &1 is not correct
What causes this issue? The balance carryforward is being peformed in a way that is <ZH>not</> valid for the asset reconciliation account...
FAA_POST124
Balance carryforward is required for CoCode &1 and ledger &2 in year &3
What causes this issue? You are making a posting on a fixed asset. The system ascertains that a balance carryforward has not taken place to the curre...
FAA_POST199
Reversal legacy data transfer does not allow an alternative posting date
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.