Order Management

Get Involved. Join the Conversation.

Topic

    Huyen Nguyen
    Sales Orders are stuck for further processing due to line...
    Topic posted August 14, 2019 by Huyen Nguyen, tagged Order Management 
    22 Views, 2 Comments
    Title:
    Sales Orders are stuck for further processing due to line status changes pending and Scheduled
    Summary:
    Sales Orders are stuck for further processing due to line status changes pending and Scheduled
    Content:

    Hi all,

    Sales Orders are stuck for further processing due to line status changes pending and Scheduled.

    1. User created SO and performed transactions.

    2. There are some splitted SO lines, some lines were partially shipped and closed and user tried to update one SO line and its status became scheduled/changing pending and could not continue processing.

    I checked and saw some errors in fulfillment line as below 

    "Service {SERVICE_NAME} request for task {TASK_INSTANCE_ID} failed due to a system error. (DOO-2685019)
    You cannot perform this action because at least one order line is fully shipped."

    Please see my attachment for details.

    If you experience this issue, please help me to fix it.

    Thanks,

    Jenny

     

    Document:

    Comment

     

    • Shyam Singh Patel

      Hi Jenny,

      Since this is custom task did you see the " Cancel Current Task" Enable at Fulfilment Line Level?
      Please try to recover the Order from Fulfilment Line or Run ESS "  Recover Errors"
      Please check the Compensation Rule for this Task if this is going through.

      After 19C upgrade, we have seen this issue in our instance too (Update the Line quantity to Zero, Order line will go into Error for our custom task) before 19C it was working perfectly.

      Severity 1   SR 3-20695535241: Compensation Rule is not working for Order revision after 19C upgrade

      Regards
      Shyam

      • Huyen Nguyen

        HI Shyam,

         

        Thanks for your sharing. Unfortunately "Cancel current task"' is disable so I could not choose it.

        Best regards,

        Jenny