Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 479
Message text: Document conditions missing for purchasing document &, item &
A price determination process has been carried out for purchasing
document &V1&. This means that document conditions should exist which
are used as the basis for updating the cumulative business volumes.
However, although data records were found during the importing of the
document conditions, none of them were for item &V2&.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Please check the document conditions for purchasing document &V1&. In
particular, check to see whether there are any missing business volume
updates relevant to subsequent (end-of-period rebate) settlement.
Error message extract from SAP system. Copyright SAP SE.
MN479
- Document conditions missing for purchasing document &, item & ?The SAP error message MN479 indicates that there are missing document conditions for a purchasing document and a specific item. This error typically arises during the processing of purchasing documents, such as purchase orders or contracts, when the system cannot find the necessary condition records that are required for pricing or other calculations.
Cause:
- Missing Condition Records: The most common cause is that the condition records for pricing, discounts, or surcharges are not maintained in the system for the relevant purchasing document or item.
- Incorrect Condition Types: The condition types that are expected for the document may not be set up correctly in the pricing procedure.
- Document Type Issues: The document type of the purchasing document may not be configured to use the required conditions.
- Master Data Issues: The vendor master data or material master data may not have the necessary pricing information.
- Pricing Procedure Configuration: The pricing procedure assigned to the purchasing document may not include the required condition types.
Solution:
Check Condition Records:
- Go to transaction code VK11 (Create Condition) or VK12 (Change Condition) to check if the necessary condition records exist for the relevant condition types.
- Ensure that the condition records are maintained for the specific vendor and material combination.
Review Pricing Procedure:
- Use transaction code OBQ1 to check the pricing procedure assigned to the purchasing document.
- Ensure that the required condition types are included in the pricing procedure.
Verify Document Type Configuration:
- Check the configuration of the document type in transaction code OMEC to ensure it is set up to use the necessary conditions.
Check Master Data:
- Review the vendor master data (transaction code MK03) and material master data (transaction code MM03) to ensure that they are correctly set up with the necessary pricing information.
Test with Different Scenarios:
- If possible, create a test purchasing document with a different vendor or material to see if the issue persists. This can help isolate whether the problem is specific to certain data.
Consult with SAP Support:
- If the issue persists after checking the above points, consider reaching out to SAP support for further assistance, as there may be specific configurations or issues in your system that need to be addressed.
Related Information:
Transaction Codes:
Documentation: Refer to SAP Help documentation for detailed information on pricing procedures and condition records.
Community Forums: Check SAP Community forums or other SAP-related discussion boards for similar issues and solutions shared by other users.
By following these steps, you should be able to identify and resolve the cause of the MN479 error in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
MN478
Document conditions for purchasing document & missing
What causes this issue? A price determination process has been carried out for purchasing document &V1&. This means that document conditions ...
MN477
Parameters for index entry (updating of documents) not allowed
What causes this issue? The system logs all relevant documents (purchase orders, goods receipts, invoice receipts, supplier billing documents, settle...
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&-...
MN481
Current date taken as update date
What causes this issue? The current date has been chosen as the update date because neither the document date nor the posting date had been set in th...
Click on this link to search all SAP messages.