Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 481
Message text: Current date taken as update date
The current date has been chosen as the update date because neither the
document date nor the posting date had been set in the purchase order
history record.
This should not be the case.
The update will take place as per the current date (today's date).
Please check the updating of the business volumes for purchasing
document &V1&, item &V2&. The PO history has the document number &V3&,
item &V4&. For more information on the document, refer to the error
log.
The document date of the material document or invoice verification
document is used as the update date (updating at the time of goods
receipt or invoice verification).
In some cases, the update date is changed to the start or end date of
the arrangement validity period if the original date is not within the
arrangement validity period (e.g. as a result of a data input error).
In the case of arrangements settled periodically, if the update date
falls in a period for which settlement accounting has already been
performed, business volumes are assigned to the next period for which
settlement accounting is due. The update date is changed accordingly.
This procedure ensures realtime inclusion of business volumes during
subsequent settlement.
In the case of invoice verification documents entered in Release 3.0,
the posting date of the invoice verification document is used for the
subsequent update of business volume data. The "Document date" field in
the PO history is empty in the case of these documents.
Error message extract from SAP system. Copyright SAP SE.
MN481
- Current date taken as update date ?The SAP error message MN481 ("Current date taken as update date") typically occurs in the context of inventory management or material movements. This message indicates that the system is using the current date as the update date for a transaction, which may not be the intended behavior. Here are some potential causes, solutions, and related information for this error: Causes: Date Configuration: The system may be configured to use the current date for certain transactions, especially if the update date is not specified. User Input: The user may not have entered a specific date for the transaction, leading the system to default to the current date. System Settings: There may be settings in the configuration of the material management module that dictate how dates are handled during transactions. Transaction Type: Certain transaction types may inherently use the current date if no other date is provided. Solutions: Specify Update Date: When performing the transaction, ensure that you explicitly
Get instant SAP help. Sign up for our Free Essentials Plan.
MN480
Subsequent settlement: Please check tax code
What causes this issue? An update of the supplier business volume expressed as value for item &V3& performed at the time(s) of -&V1&-...
MN479
Document conditions missing for purchasing document &, item &
What causes this issue? A price determination process has been carried out for purchasing document &V1&. This means that document conditions ...
MN482
Missing index entry has been created retrospectively
What causes this issue? During the price determination process for a purchase order, a scheduling agreement, a payment document, or a supplier billin...
MN483
Header data missing for purchasing document & (internal program error)
What causes this issue? The supplier business volume update should have been carried out for purchasing document &V1&. However, the document ...
Click on this link to search all SAP messages.