Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 082
Message text: Condition record (item) period &-& does not exist
A condition record (item data) could not be read. This is probably due
to a program error.
The number of the affected condition record is &V3&, item &V4&, valid
from &V1& to &V2&.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Contact your system administrator.
Error message extract from SAP system. Copyright SAP SE.
MN082
- Condition record (item) period &-& does not exist ?The SAP error message MN082 indicates that a condition record for a specific item and period does not exist in the system. This error typically arises in the context of pricing, where the system is unable to find the necessary condition records for calculating prices, discounts, or other conditions related to a transaction.
Cause:
- Missing Condition Records: The most common cause is that the required condition records for the specified item and period have not been created in the system.
- Incorrect Validity Dates: The condition records may exist, but their validity dates do not cover the date of the transaction being processed.
- Incorrect Condition Type: The condition type being used may not be set up correctly or may not be relevant for the item in question.
- Master Data Issues: There may be issues with the master data (e.g., material master, customer master) that prevent the system from finding the correct condition records.
Solution:
Create Condition Records:
- Use transaction code VK11 to create the necessary condition records for the item and period in question.
- Ensure that you enter the correct condition type, material, customer, and other relevant details.
Check Validity Dates:
- Verify the validity dates of existing condition records using transaction code VK13. Ensure that the records are valid for the date of the transaction.
Review Condition Types:
- Check if the correct condition type is being used in the pricing procedure. You can do this by reviewing the pricing procedure configuration in transaction code V/08.
Check Master Data:
- Ensure that the relevant master data (material, customer, etc.) is correctly maintained and that there are no discrepancies that could affect pricing.
Consult with Configuration Team:
- If you are unsure about the configuration or if the issue persists, consult with your SAP configuration team to ensure that the pricing procedure and condition records are set up correctly.
Related Information:
Transaction Codes:
Pricing Procedure: Understand how pricing procedures work in SAP and how condition records are linked to them.
Documentation: Refer to SAP Help documentation for detailed information on condition records and pricing procedures.
By following these steps, you should be able to resolve the MN082 error and ensure that the necessary condition records are in place for your transactions.
Get instant SAP help. Start your 7-day free trial now.
MN081
Condition record (header) period &-& does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MN080
Rebate arrangement & extended (becomes arrangement &)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MN083
No period in new rebate arrangement corresponding to period &-&
What causes this issue? In the extension of rebate arrangement &V3& to the next overall validity period (e.g. to the following year), the ind...
MN084
Data of last period used for period &-&
In the extension of rebate arrangement &V3& to the next overall validity period (e.g. to the following year), the individual periods of the e...
Click on this link to search all SAP messages.