Do you have any question about this error?
Message type: E = Error
Message class: EDI_SD - Messages for EDI SD Integration
Message number: 804
Message text: The old delivery schedule &1 is not identical with delivery schedule &2.
The old delivery schedule &V1& in the purchase scheduling agreement is
not identical with the
<DS:DE.LABNK>delivery schedule</> &V2& in the sales scheduling
agreement.
In the electronic data interchange (EDI) message, the customer sends the
new and the old (previous) delivery schedule keys. The system compares
the old one with the current delivery schedule in the sales scheduling
agreement. If they are identical, the system updates the current
delivery schedule according to the new one.
The system stops processing the EDI message.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
EDI_SD804
- The old delivery schedule &1 is not identical with delivery schedule &2. ?The SAP error message EDI_SD804 indicates that there is a discrepancy between two delivery schedules in the system. Specifically, it means that the old delivery schedule (identified by &1) does not match the new delivery schedule (identified by &2). This error typically occurs in the context of Electronic Data Interchange (EDI) processes, particularly when dealing with delivery schedules in sales and distribution.
Cause:
- Data Mismatch: The old delivery schedule may have been modified or updated, and the new delivery schedule does not reflect those changes.
- Incorrect EDI Message: The EDI message being processed may contain incorrect or incomplete data, leading to inconsistencies between the old and new schedules.
- Manual Changes: If manual changes were made to the delivery schedule in the SAP system, it could lead to a mismatch with the EDI data being processed.
- Timing Issues: If the old delivery schedule was updated after the EDI message was generated, this could lead to discrepancies.
Solution:
- Verify Delivery Schedules: Check both the old and new delivery schedules in the SAP system to identify the differences. You can do this by comparing the relevant fields in the delivery schedule documents.
- Correct EDI Data: If the EDI message is incorrect, you may need to correct the data being sent from the external system or correct the mapping in the EDI interface.
- Reprocess EDI Message: After ensuring that the delivery schedules are consistent, you may need to reprocess the EDI message to ensure it is accepted by the system.
- Consult Logs: Check the EDI logs for any additional error messages or warnings that could provide more context about the issue.
- Update Delivery Schedule: If necessary, update the delivery schedule in the SAP system to ensure it matches the expected data from the EDI message.
Related Information:
VL03N
(Display Outbound Delivery) or ME33K
(Display Contract) to view and analyze delivery schedules.By following these steps, you should be able to identify the cause of the EDI_SD804 error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
EDI_SD803
No sales scheduling agreement found.
What causes this issue? The system uses the following search criteria to search for a sales scheduling agreement: The sold-to party that either comes...
EDI_SD802
Multiple sales scheduling agreements found for sold-to party &1.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EDI_SD805
In delivery schedule &1, delivery schedule key must be 1, 2, or blank.
What causes this issue? The delivery schedule key is not set to 1, 2, or blank. The system processes the delivery schedule when the delivery schedule...
EDI_SD806
No schedule line to be copied from the old JIT delivery schedule.
What causes this issue? You have set the requirement status key to B for JIT delivery schedules that meet standards defined in VDA 4915, a requiremen...
Click on this link to search all SAP messages.