PR160 Web run node

Hi,

I have web run Node to submit the job PR530 ,PR137,PR140 ,PR160 and PR197 . We are facing issue when the job submit for PR160. Only the error occurs for PR160.

Job moves to recovery state with the below error . Any clue on this please.

Code is below

Find more posts tagged with

Process Automation (IPA) - General Discussions

Accepted answers

Legacy Contributor

Hi lavanya, when I execute your string without the receipt number, I also receive an error. Try adding START-RECEIPT-NBR. Also keep in mind that when you update PR160 using a transaction node, any static parameters you have set up in your job will get blanked out or defaulted, if you do not specify them when you do the change transaction. We do an inquire on the job in a txn node before we update it. The inquire node will have a value for every parameter, and you can use them to populate your change transaction.

All comments

adam-sturtevant

I have not seen that error. We trigger the PR jobs a bit differently using the WebRun node. Can you trigger the PR160 from lawson with that username?

kyle-tucker

I would just double check the job parameters as there are quite a few on the PR160 and if one is amiss (or empty) it could be causing this. The payment numbers have to be correct and not already used.

Legacy Contributor

that is a good point Kyle, we submit our PR160s from a flow, but we have another job that updates all the parameters first, and one of the things it does is set the payment numbers.

Legacy Contributor

This is not a Program error or IPA error. It looks like... in PR160 Message Maintenance section, message is missing for code 153.

Legacy Contributor

The message not found error is often a red herring. I would confirm that you have a PR160 executable out there, and then try to run the job from portal with the parameters as is, under the ID that is submitting the job in the flow, as Adam and Kyle suggest, and then go from there.

Legacy Contributor

it would be really helpful if you culd send the code to lavanya@greenotech.co..It would create clue.

Legacy Contributor

Hi lavanya, we use a webrun method similar to what you use. Here is our string:

/lawson-ios/action/SubmitJob?jobName=<!strJob>&jobOwner=<!strJobOwner>&startDate=&startTime=&displayOldFormat=true&OUT=TXT&wait=true

Populate the <!strJob> and <StrJobOwner> with the job name and username (just like what you already do). We set the method to POST, rather than GET. Maybe that will make a difference?

If this does not work, I would open a case with support. They can help you quicker than we can!

Copyright © 2025 Infor. All rights reserved.