Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 320
Message text: Update date outside validity period of rebate arrangement
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
The function has been performed.
Check whether or not the associated supplier business volumes actually
belong to rebate arrangement &V3& and need to be included in the
settlement accounting process.
The condition record affected has the (internal) number &V4& and belongs
to rebate arrangement &V3&. Item &V2& of purchasing document &V1& was
processed.
&HINWEIS&
As a rule, the update date is the document date of the invoice
verification document. However, for the purposes of the retrospective
compilation of supplier business volumes, the posting date of the
invoice verification document is taken instead.
Error message extract from SAP system. Copyright SAP SE.
MN320
- Update date outside validity period of rebate arrangement ?The SAP error message MN320, which states "Update date outside validity period of rebate arrangement," typically occurs when you are trying to process a rebate arrangement that has a defined validity period, and the date you are attempting to use falls outside of that period. This can happen in various transactions related to rebates, such as creating or updating rebate agreements.
Cause: Validity Period: The rebate arrangement has a specific start and end date. If the date you are trying to use (for example, the posting date of a document) is outside this range, the system will trigger this error. Incorrect Date Entry: The date entered in the transaction may be incorrect or not aligned with the rebate arrangement's validity. Rebate Arrangement Status: The rebate arrangement may be inactive or not fully set up, which can also lead to this error.
Solution: Check Validity Dates: Review the validity period of the rebate arrangement. You can do
Get instant SAP help. Sign up for our Free Essentials Plan.
MN319
Current condition record in purchasing doc. &, item &, is inactive
What causes this issue? There is no provision for the updating of condition records from the "subsequent (end-of-period rebate) settlement"...
MN318
System error reading purchasing document &
What causes this issue? The system could not read purchasing document no. &V1& (header data) because the relevant entry does not exist in the...
MN321
Partner role & not defined
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MN322
Partner & (partner role &) not defined
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.