Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 274
Message text: Update date differs from validity date of period condition record
The update date is incompatible with the validity period of the period
period condition record for which the updating took place.
The function has been performed even though the update date is
incompatible with the validity period of the period condition record.
Usually, the update lies outside the rebate arrangement validity period.
This message is simply to inform you about this situation and has no
further significance.
It may be, however, that the incoming invoice was assigned to the wrong
period. Please look into the matter (the assignment of business volume
data may not make sense).
The update date determines the period condition record for which the
business volume data is updated. This may be a different period record
to the one used during price determination in the purchase order, for
example purchase order in August (period conditions for August used),
invoice receipt in September (update for September). In the case of
Settlement Management documents (settlement documents, supplier billing
documents), these can be released to Accounting in a different period.
The affected condition record has the (internal) number &V4& and belongs
to rebate arrangement &V3&. Item &V2& of purchasing document &V1& was
processed.
&HINWEIS&
In the case of updates from purchase orders/scheduling agreement, the
delivery date of the schedule line is used as the update date. In the
case of updates from goods receipt or invoice verification, the document
date is used. In the case of Settlement Management documents (settlement
documents, supplier billing documents), the posting date is used.
Error message extract from SAP system. Copyright SAP SE.
MN274
- Update date differs from validity date of period condition record ?The SAP error message MN274 ("Update date differs from validity date of period condition record") typically occurs when there is a mismatch between the update date of a condition record and its validity date. This can happen in various scenarios, particularly when dealing with pricing conditions in sales and distribution (SD) or materials management (MM).
Cause:
- Validity Date Mismatch: The update date of the condition record does not fall within the validity period defined for that condition record. Each condition record has a validity period, and if the update date is outside this range, the error will occur.
- Incorrect Date Settings: The system date or the date settings in the user profile may not align with the expected validity dates.
- Data Entry Errors: Manual entry errors when creating or updating condition records can lead to incorrect dates being set.
Solution:
Check Validity Dates: Review the validity dates of the condition record in question. Ensure that the update date falls within the defined validity period.
- You can do this by navigating to the condition record in the relevant transaction (e.g., VK11 for pricing conditions) and checking the validity dates.
Update the Condition Record: If the update date is indeed outside the validity period, you may need to either:
- Change the update date to a valid date that falls within the condition record's validity period.
- Adjust the validity dates of the condition record to include the update date.
Review System Date: Ensure that the system date is set correctly. If the system date is incorrect, it may lead to such errors.
Consult Documentation: If you are unsure about the validity periods or how to adjust them, refer to SAP documentation or consult with your SAP administrator or support team.
Transaction Logs: Check transaction logs for any recent changes that might have affected the condition records.
Related Information:
By following these steps, you should be able to resolve the MN274 error and ensure that your condition records are correctly maintained. If the issue persists, consider reaching out to your SAP support team for further assistance.
Get instant SAP help. Start your 7-day free trial now.
MN273
Function & canceled for condition record
What causes this issue? During execution of function &V1&, more than &V2& messages were issued.System Response Since too many error ...
MN272
Busn. vol. update for reb. arrang. &1 not possible (final sett. effected)
What causes this issue? Translation: in part identical to NAA040/NAA401 Settlement accounting has already been effected for rebate arrangement &V...
MN275
*** SETTLEMENT REPORT RWMBON01 ***
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MN276
No output of totals values in accordance with scope of statement
What causes this issue? Outputting of the totals values in accordance with the scope of statement in the list report "Display statements" h...
Click on this link to search all SAP messages.