Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 591
Message text: No updating of provisions for accrued rebate income (account key missing)
Provisions for accrued rebate income have been determined in the course
of the price determination process (condition type is relevant to
provisions for rebate income).
These were not posted at the time of goods receipt because the account
key is missing from the calculation schema for the supplier.
Since no provisions for income were posted, no business volume update
has been carried out either.
Please maintain the account key for provisions in the calculation schema
for the supplier. If necessary, contact the person responsible for this
in your enterprise.
You may have to cancel already posted material documents in order to be
able to post and update the provisions for rebate income ("Detailed
statement" function for the rebate arrangement).
The relevant document from the fiscal year &V2& has the document number
&V1& (item &V3&). The rebate arrangement is &V4&.
Please note:
Provisions for accrued rebate income are posted at the time of goods
receipt. However, in the case of rebate arrangements entered prior to
Release 4.0, updating of such provisions does not take place until the
time of invoice receipt. If necessary, please also cancel the relevant
invoices.
Error message extract from SAP system. Copyright SAP SE.
MN591
- No updating of provisions for accrued rebate income (account key missing) ?The SAP error message MN591 ("No updating of provisions for accrued rebate income (account key missing)") typically occurs in the context of rebate processing in SAP. This error indicates that the system is unable to update the provisions for accrued rebate income because a necessary account key is missing in the configuration.
Cause:
- Missing Account Key: The most common cause of this error is that the account key for the rebate provisions is not defined in the system. This can happen if the configuration for rebate processing is incomplete or incorrect.
- Incorrect Configuration: The account determination settings for rebates may not be properly set up in the system.
- Master Data Issues: The customer or material master data may not have the necessary settings for rebates, leading to the absence of the required account key.
Solution:
To resolve the MN591 error, you can follow these steps:
Check Account Key Configuration:
- Go to the transaction code OB40 (or navigate through the menu: SPRO > Financial Accounting > General Ledger > Account Determination > Account Determination for Rebate Processing).
- Ensure that the account key for rebate provisions is defined and correctly assigned to the relevant condition types.
Review Condition Types:
- Check the condition types used for rebates in the pricing procedure. Ensure that they are correctly configured to post to the appropriate accounts.
- Use transaction code V/06 to review and adjust the condition types.
Verify Master Data:
- Check the customer master data (transaction code XD02) and ensure that the necessary settings for rebates are in place.
- Similarly, check the material master data (transaction code MM02) for any relevant settings.
Test the Configuration:
- After making the necessary changes, perform a test transaction to ensure that the error no longer occurs.
Consult Documentation:
- If you are unsure about the configuration, refer to SAP documentation or consult with your SAP functional consultant for guidance.
Related Information:
Transaction Codes:
SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on rebate processing.
Rebate Processing: Understanding the overall rebate processing in SAP can help in troubleshooting related issues. Familiarize yourself with the concepts of condition types, account keys, and pricing procedures.
By following these steps, you should be able to identify and resolve the cause of the MN591 error in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
MN590
Settlement Management documents/items no longer exist in the system
What causes this issue? The system could not find a Settlement Management document (supplier billing document, settlement document) or Settlement Man...
MN589
Index entry missing for document &, item &
What causes this issue? Document &V1&, item &V2&, is relevant to subsequent (end-of-period rebate) settlement with respect to a condi...
MN592
Items of documents belonging to category & cannot be processed
What causes this issue? This function is only defined for documents belonging to the categories The system issues an error message and will not allow...
MN593
Purchasing document & belongs to category & (not allowed)
What causes this issue? There is no provision for the updating of supplier business volumes within the framework of <GL> <GL:subsequent_sett...
Click on this link to search all SAP messages.