Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: V4 - Nachrichten Verkauf (Variable Meldungen und EDI-Meldungen)
Message number: 058
Message text: The old dlv. sched no. &1 in IDoc &2 <> than current delivery sched.no.&3
It is possible that a previous release order number of the customer was
not scheduled, which means there was a gap in the release order
numbers.
Current release number in delivery schedule &V4&: &V3&
Old release number in IDoc &V2&: &V1&
The system terminates processing.
Check the release order numbers in the
<DS:GLOS.scheduling_agreement>scheduling agreement</>. If you want to
copy the <DS:GLOS.IDoc>IDoc</>, restart scheduling from the mailing.
Error message extract from SAP system. Copyright SAP SE.
V4058
- The old dlv. sched no. &1 in IDoc &2 <> than current delivery sched.no.&3 ?The SAP error message V4058 indicates a mismatch between the delivery schedule number in the IDoc and the current delivery schedule number in the system. This error typically occurs during the processing of IDocs related to delivery schedules, such as when updating or processing delivery information.
Cause:
The error arises when the delivery schedule number specified in the IDoc does not match the delivery schedule number that is currently active or expected in the SAP system. This can happen due to several reasons, including:
- Data Inconsistency: The IDoc may contain outdated or incorrect information that does not align with the current state of the delivery schedule in the system.
- Manual Changes: If there were manual changes made to the delivery schedule after the IDoc was generated, it could lead to this mismatch.
- IDoc Generation Issues: The IDoc may have been generated incorrectly, leading to discrepancies in the delivery schedule numbers.
- System Configuration: There may be configuration issues in the system that affect how delivery schedules are processed.
Solution:
To resolve the V4058 error, you can take the following steps:
- Check IDoc Data: Review the IDoc data to ensure that the delivery schedule number is correct. You can use transaction WE02 or WE19 to analyze the IDoc.
- Verify Current Delivery Schedule: Check the current delivery schedule in the SAP system to confirm the correct delivery schedule number. You can do this using transaction ME33L (for scheduling agreements) or other relevant transactions based on your context.
- Update IDoc: If the IDoc contains incorrect information, you may need to correct the IDoc data and reprocess it. This can involve creating a new IDoc with the correct delivery schedule number.
- Reprocess IDoc: If the IDoc is correct but the system is not recognizing it, you may need to reprocess the IDoc. This can be done using transaction BD87.
- Consult Documentation: Review any relevant documentation or notes from SAP that may provide additional insights into this error.
- Contact SAP Support: If the issue persists and you cannot identify the cause, consider reaching out to SAP support for further assistance.
Related Information:
By following these steps, you should be able to identify and resolve the cause of the V4058 error in your SAP system.
Get instant SAP help. Sign up for our Free Essentials Plan.
V4057
IDoc &2 was already planned in scheduling agreement &1
What causes this issue? The <DS:GLOS.IDoc>IDoc</> was already scheduled for this <DS:GLOS.scheduling agreement>scheduling agreement...
V4056
Delivery schedule &2 already exists in sales scheduling agreement &1.
What causes this issue? The delivery schedule entered has already been allowed for, that is, it corresponds to the delivery schedule for the precedin...
V4059
An error occurred during CALL TRANSACTION processing
What causes this issue? An error occured during processing using CALL TRANSACTION.System Response The system terminates processing.How to fix this e...
V4060
IDoc & could not be opened
What causes this issue? It was not possible to open the <DS:GLOS.IDOC>IDOC</>, because it is blocked or does not exist.System Response T...
Click on this link to search all SAP messages.