Do you have any question about this error?
Message type: E = Error
Message class: FMLGD -
Message number: 701
Message text: Customer accnt assignment: Bank credit memo is incomplete or inconsistent
If no setting exists for this event (message 701) in the Customizing for
error events and no basic setting exists either for the handling of
errors with customer bank credit memos (message 700), the system cannot
execute the posting automatically.
Otherwise the system executes the posting in accordance with the setting
for message 701 or 700.
Make sure that the account assignment for this turnover is complete.
Check for further possible error messages in the log of the clearing
control (program FM_LGD_H_RFEBKAP0).
Error message extract from SAP system. Copyright SAP SE.
FMLGD701
- Customer accnt assignment: Bank credit memo is incomplete or inconsistent ?The SAP error message FMLGD701 indicates that there is an issue with the customer account assignment related to a bank credit memo. This error typically arises when the system detects that the information required for processing the bank credit memo is either incomplete or inconsistent. Here are some common causes, potential solutions, and related information for this error:
Causes:
- Missing Data: Required fields in the bank credit memo may not be filled out completely. This could include customer account details, amounts, or other relevant information.
- Inconsistent Data: The data entered may not match the expected format or may conflict with existing records in the system (e.g., incorrect customer account number).
- Configuration Issues: There may be issues with the configuration settings in the financial module that affect how bank credit memos are processed.
- Document Type Issues: The document type used for the bank credit memo may not be set up correctly in the system.
- Authorization Issues: The user may not have the necessary permissions to process the bank credit memo.
Solutions:
- Check Data Completeness: Review the bank credit memo for any missing fields. Ensure that all required information is filled out correctly.
- Validate Data Consistency: Verify that the data entered matches the expected formats and that there are no discrepancies with existing records (e.g., customer account details).
- Review Configuration Settings: Check the configuration settings in the SAP system related to bank credit memos. Ensure that all necessary settings are correctly configured.
- Document Type Verification: Ensure that the document type used for the bank credit memo is correctly defined and configured in the system.
- User Authorization: Confirm that the user processing the bank credit memo has the necessary authorizations to perform this action.
- Consult SAP Notes: Look for any relevant SAP Notes that may address this specific error message. SAP frequently updates its knowledge base with solutions for known issues.
Related Information:
FB60
(Enter Incoming Invoices), F-28
(Post Incoming Payments), or FBL5N
(Customer Line Item Display) to help troubleshoot the issue.By following these steps, you should be able to identify and resolve the issue causing the FMLGD701 error message in SAP.
Get instant SAP help. Start your 7-day free trial now.
FMLGD700
Basic setting for error handling of customer bank credit memo
What causes this issue? An event was triggered that belongs to posting type 07 (customer bank credit memo).System Response If no special entry exist...
FMLGD614
No customer exists in estimated revenue &1/&2
What causes this issue? The clearing control always determines the customer from the item of the forecast of revenue (general request). However, no c...
FMLGD703
You are not allowed to clear open items for more than one customer
What causes this issue? You want to clear several open items with a customer bank credit memo as the open items were posted on different customers.Sy...
FMLGD711
No open items exist for payment; customer is not known
What causes this issue? The system issues an error message and will not allow you to continue with this transaction until the error is resolved. Syst...
Click on this link to search all SAP messages.