How To Fix EDI_SD806 - No schedule line to be copied from the old JIT delivery schedule.


SAP Error Message - Details

  • Message type: E = Error

  • Message class: EDI_SD - Messages for EDI SD Integration

  • Message number: 806

  • Message text: No schedule line to be copied from the old JIT delivery schedule.

  • Show details Hide details
  • 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 requirement of the German
    Automobile Industry Association. According to your setting, the system
    copies schedule lines in the old delivery schedule that come before or
    after the validity period of the new delivery schedule to the new
    delivery schedule.
    There is no such schedule line.

    System Response

    The system keeps processing the EDI message.

    How to fix this error?

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

    Procedure for System Administrators


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message EDI_SD806 - No schedule line to be copied from the old JIT delivery schedule. ?

    The SAP error message EDI_SD806, which states "No schedule line to be copied from the old JIT delivery schedule," typically occurs in the context of Just-In-Time (JIT) delivery schedules in the Sales and Distribution (SD) module. This error indicates that the system is unable to find a corresponding schedule line in the old JIT delivery schedule that can be copied to the new schedule.

    Causes:

    1. Missing Schedule Line: The old JIT delivery schedule may not have any schedule lines defined, or the schedule lines may have been deleted or not created properly.
    2. Incorrect Configuration: There may be configuration issues in the JIT delivery schedule settings or in the EDI settings that prevent the proper copying of schedule lines.
    3. Data Inconsistency: There could be inconsistencies in the data between the old and new schedules, such as mismatched material numbers, plant codes, or other relevant fields.
    4. Document Status: The old JIT delivery schedule may be in a status that does not allow for copying, such as being completed or archived.

    Solutions:

    1. Check Old JIT Delivery Schedule: Verify that the old JIT delivery schedule exists and has valid schedule lines. You can do this by navigating to the relevant transaction (e.g., ME38 for JIT delivery schedules) and checking the details.
    2. Review Configuration: Ensure that the configuration for JIT delivery schedules and EDI settings is correct. This may involve checking the relevant customizing settings in SPRO.
    3. Data Consistency Check: Ensure that all relevant data (material, plant, etc.) is consistent between the old and new schedules. If there are discrepancies, correct them.
    4. Document Status Review: Check the status of the old JIT delivery schedule. If it is not in a suitable status for copying, you may need to change its status or create a new schedule.
    5. Consult SAP Notes: Look for any relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide fixes or workarounds for known issues.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as ME38 (Display JIT Delivery Schedule) and ME39 (Display JIT Delivery Schedule with History).
    • SAP Documentation: Review SAP documentation related to JIT delivery schedules and EDI processes for additional insights and best practices.
    • Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.

    By following these steps, you should be able to identify the root cause of the EDI_SD806 error and implement a suitable solution.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant