Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: FMUP - Update in Funds Management
Message number: 164
Message text: 'Standardized document' was changed by document splitting.
You post a document that is only updated in the universal journal (table
ACDOCA) and does not have an entry view of the BSEG table.
The system displays this error message because this document was changed
by document splitting in Financial Accounting (account assignments were
added, lines were split). Funds Management requires a document with an
entry view to ensure that the update is performed correctly.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
If this document was generated by a standard SAP process, check whether
this document can be posted with an entry view (see SAP Note 2670040 for
foreign currency valuation).
If this is not possible (such for depreciation postings in Asset
Accounting), assign the corresponding document type to a suitable b
usiness transaction variant, which does not change the document.
If the posting comes from a customer-specific program or is generated
using an interface, post the document with an entry view of the table
BSEG, or post it with a complete account assignment so that document
splitting is no longer required.
Error message extract from SAP system. Copyright SAP SE.
FMUP164
- 'Standardized document' was changed by document splitting. ?The SAP error message FMUP164, which states that a "Standardized document was changed by document splitting," typically occurs in the context of Financial Accounting (FI) and Controlling (CO) modules when document splitting is enabled. This error indicates that there is a conflict or inconsistency in the document due to the document splitting process.
Cause:
- Document Splitting Configuration: The error often arises when the document splitting configuration is not set up correctly. This can include missing or incorrect settings for the splitting characteristics or rules.
- Inconsistent Data: If the data in the document does not meet the requirements for document splitting, it can lead to this error. For example, if the account assignments or segment information are not properly defined.
- Manual Changes: If a user manually changes a document that has already been processed for splitting, it can trigger this error.
- Posting Logic: The posting logic may not align with the document splitting rules, leading to inconsistencies.
Solution:
- Check Document Splitting Configuration: Review the configuration settings for document splitting in the Financial Accounting module. Ensure that all necessary characteristics and rules are correctly defined.
- Transaction Code:
OBCE
(for document splitting configuration).- Review Document Data: Check the document that triggered the error for any inconsistencies in account assignments, segments, or other relevant data. Ensure that all required fields are filled out correctly.
- Reprocess the Document: If the document was changed after it was posted, consider reversing the document and reposting it with the correct data.
- Consult SAP Notes: Look for any relevant SAP Notes that may address this specific error or provide guidance on document splitting issues.
- Testing: If changes are made to the configuration, conduct thorough testing in a development or quality assurance environment before applying changes to the production system.
Related Information:
FB03
(Display Document), FB02
(Change Document), and OBCE
(Document Splitting Configuration).If the problem persists after following these steps, it may be beneficial to consult with an SAP expert or your organization's SAP support team for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
FMUP163
Program is obsolete. Please see Note 2897555.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FMUP162
Excessive document lines in FM document
What causes this issue? The posting would produce a Funds Management document with over 999 document lines.System Response The posting cannot be car...
FMUP200
FM initial archiving run is not possible as archiving has already begun
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FMUP201
RFFM_FMARC_BATCH background process &1 not yet finished -> lock entry
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.