Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 319
Message text: Current condition record in purchasing doc. &, item &, is inactive
There is no provision for the updating of condition records from the
"subsequent (end-of-period rebate) settlement" area which are subject
to condition exclusion.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
You can correct the faulty update by carrying out a recompilation of
the statistics or by carrying out a business volume comparison and
agreement process.
Please check whether a new price determination process was carried out
after the updating of the LIS statistics relating to "subsequent
settlement" with respect to purchase order no. &V1&, item &V2&. As a
result, the pricing types may have been changed or the exclusion of
conditions relating to "subsequent settlement" activated.
Error message extract from SAP system. Copyright SAP SE.
MN319
- Current condition record in purchasing doc. &, item &, is inactive ?The SAP error message MN319 indicates that the current condition record in the purchasing document (PO) and item specified is inactive. This typically occurs when the pricing conditions for a specific purchasing document are not valid or have been deactivated in the system.
Cause:
- Inactive Condition Record: The condition record for pricing (like discounts, surcharges, etc.) has been marked as inactive in the system.
- Validity Period: The condition record may have a validity period that has expired.
- Condition Type: The condition type may not be applicable for the specific purchasing document or item.
- Master Data Issues: There may be issues with the vendor master data or material master data that affect the condition records.
- Configuration Issues: The pricing procedure may not be correctly configured to include the condition type in question.
Solution:
Check Condition Records:
- Go to transaction code MEK1 (Create Condition) or MEK2 (Change Condition) to check the condition records for the relevant condition type.
- Ensure that the condition record is active and has the correct validity dates.
Review Validity Period:
- Verify that the validity period of the condition record covers the date of the purchasing document. If it has expired, you may need to create a new condition record.
Check Configuration:
- Ensure that the pricing procedure assigned to the purchasing document includes the relevant condition type. You can check this in the configuration settings under SPRO > Materials Management > Purchasing > Conditions > Define Price Determination Process.
Vendor and Material Master Data:
- Check the vendor master data and material master data to ensure that they are correctly set up and that there are no issues that could affect pricing.
Recreate Condition Record:
- If necessary, recreate the condition record with the correct details and ensure it is marked as active.
Consult Documentation:
- Refer to SAP documentation or consult with your SAP support team for specific details related to your configuration and setup.
Related Information:
Transaction Codes:
SAP Notes: Check for any relevant SAP Notes that may address specific issues related to condition records and pricing.
User Roles: Ensure that the user has the necessary authorizations to view and modify condition records.
By following these steps, you should be able to identify the cause of the MN319 error and implement the appropriate solution.
Get instant SAP help. Start your 7-day free trial now.
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...
MN317
System error reading item & of purchasing document &
What causes this issue? The system could not read item &V1& of purchasing document no. &V2& because the relevant entry does not exist...
MN320
Update date outside validity period of rebate arrangement
What causes this issue? The system issues an error message and will not allow you to continue with this transaction until the error is resolved. Syst...
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...
Click on this link to search all SAP messages.