Automate

 View Only
  • 1.  MIGO_GO Runtime error

    Posted 02-10-2020 16:47
      |   view attached
    Hello,

    When creating a script using MIGO_GO to remove stock of MRO materials, I am receiving a runtime error. The script is working in the sense that the stock is being removed or added, but the script is returning an error. My fear is that this will "block" or change a different error so the script will not be accurate. Anyone have any experience with this issue and could provide feedback? My guess is that this i due to the fact that MIGO_GO does not have the option to save the changes, only back out once the stock has been posted or removed. 

    I appreciate the help.

    Thanks,
    Matt

    ------------------------------
    Matt Dunlap | Data Steward
    Dairy Farmers of America, Inc. | 8168636217
    ------------------------------


  • 2.  RE: MIGO_GO Runtime error

    Posted 02-11-2020 02:35
    Hi Matt,
    You can run the script in DEBUG - show all screens to find screen of error.

    Still if not able to resolve.There would be an error dump in tcode ST22 for the time and sap user. 
    Open its details
    Please share the text from these sections of the dump
    1 System Environment
    2 User and Transaction
    3 Error Analysis
    Regards
    Gurpreet Singh Sidhu

    ------------------------------
    Gurpreet Sidhu | Manager Software Engineering
    Winshuttle North America
    ------------------------------



  • 3.  RE: MIGO_GO Runtime error

    Posted 02-11-2020 15:55
    Hello Gurpreet,

    Thank you for the prompt response. I have ran the debugger and still can't figure out the root cause of the issue. Here are the screenshots of the information you had requested from the ST22 run.

    Thanks,
    Matt
     



    ------------------------------
    Matt Dunlap | Data Steward
    Dairy Farmers of America, Inc. | 8168636217
    ------------------------------



  • 4.  RE: MIGO_GO Runtime error

    Employee
    Posted 02-11-2020 11:27
    Hi Matt

    For MIGO - ensure you have Launch SAP GUI checked.   I will often get that message if it's not for a tcode that needs it.  This is an SAP "enjoy" tcode, and most of the time it's needed.


    Also go to the expert tab in the mapper and enable extended logging, if it's available.  It usually provides all of the messages, including warnings and postings.

    And as Gurpreet suggested, running in debug mode may help you.

    Hope that helps,
    Sigrid

    ------------------------------
    Sigrid Kok
    PSE | Winshuttle NA
    ------------------------------