Prev
Next
Forums IPA/ProcessFlow

inconsistent resulst running Lawson Transaction with Webrun

Sort:
You are not authorized to post a reply.
Author
Messages
donnas
New Member
Posts: 2
New Member
3/8/2016 3:38 PM

    HI,

    I have an IPA flow that runs MA126.  I have a Lawson transaction node set up to run a MA126 job I created and then I have a Webrun to execute it.  This runs sometimes.  The actual IPA runs every night and I see it in the Rich Client . I always get a success string found on the Webrun (I can see this in the log in Rich Client) and I have an on error STOP and notify set up on both the Lawson transaction node and the Webrun node.  It never stops and it never notifies me.  I run it once a day and in the last 2 days it ran on 1 day and didn't run on the other.  When it runs, I can log into Lawson app and see in the job schedule a completed job and when it doesn't run there is no entry in the job scheduler for that day.  What can I check in IPA to make sure the transaction actually runs?

    I'm running on version 10.1.1.29 rich client/IPD Designer

     

    thanks for any help with this!

    donna

     

    Tags: webrun
    Bob Canham
    Veteran Member
    Posts: 217
    Veteran Member
    3/8/2016 3:45 PM
      There are a few things to do to make it monitor for you. Make sure your webrun is set for &wait=true and &out=xml. Then in your success string, you put 
       63
      . This will have the WebRun node wait for your MA126 to complete and then check the XML output to see that it completed successfully.
      Tags: webrun
      donnas
      New Member
      Posts: 2
      New Member
      3/10/2016 3:38 PM

        Thanks Bob.  That works.  I have 1 more question though, do you know where we control the timeout of the Webrun?  the MA126 is matching invoices and it may take a while to run, I'm curious where we would adjust the timeout.

        if it does timeout, will some invoices get matched?  that would not be good.

        thanks again!

        donna

         

        Tags: webrun
        Bob Canham
        Veteran Member
        Posts: 217
        Veteran Member
        3/10/2016 3:46 PM
          I think the timeout is in the IPA Configuration record, but i'm not positive. I never updated ours.

          As for the job being incomplete, the timeout relates to the WebRun only. so it will kick off the MA126 job and wait up to timeout for the job to finish. If it doesn't finish in that time, the MA126 should (test this) continue running to completion but your WebRun would report a failure since it didn't complete before the timeout.
          Tags: webrun
          You are not authorized to post a reply.