Req Item Rec Service Definition

Service Name should be ReqItemRec (no spaces). the requester from REQ header is used to lookup email address.

Joan,

We had some similar challenges using the same document with similar results (i.e. the service that should be used was setup correctly, enabled, but nothing was being triggered). For our situation, we use the PO23 and PO100. What we ended up using was the Gen_PurchaseOrd service. Once I enabled that, I tied a process flow to the trigger to send out a short email notification to the requester letting them know the item(s) were received. Since you are using the PO30, I would take a look at the Gen_POReceive service (should be page 185 in the 10.0.5 service manual). This gets triggered anytime a PO reciept is created or updated using the PO30. Give that a try and see if it works for you.

Thanks James I'll give that a try.
I decided to test a PO that was generated through RQC and had items I could receive.  That did trigger a work unit.  So it looks like the RecReqItem only work if there is a requester and not if it's entered on the PO screen.  So I'll try the Gen_POReceive service and let you know.

thanks.

Well the Gen_PORecieve trigger does generate a work order.  However, I would like to be able to filter this and only create a work unit if... ultimately I only need a wu if the Item's Serial Tracking is R (receipts).  I've been testing to see if I can filter on Location or Bin since location is already listed as a 'Criteria'.  I have not had any luck with this approch.  Can anyone tell me if it's possible to create/set up a service to only trigger is a specific thing is true?  If so, how?  I have looked at documentation, but can't find anything.

Also, I know I've seen documentation on how to create a custom trigger, but now that I want it I can't find it.  Anyone know where that is?

Thanks!

For a delivered trigger, the only filters you can apply are on the Service in the Criteria fields. Whatever these pre-defined fields are for the Service, you enter the value you want met for the Service to trigger. Custom triggers can have any criteria you build.

Joan,

Glad to hear the service/trigger worked for you. Another approach to the custom trigger solution is to filter it after the trigger. You could create a process flow, tie it to the trigger, and then run a query against your database/record source to look up information for the req. If it didn't meet your criteria, just branch it off to the end. If it met your criteria, then you can process it (i.e. update application forms, send notifications, run another flow, etc.). Yes, it creates more workunits from the trigger, but they run really fast if they don't meet your filter criteria.

Yes that is possible, however we are talking hundreds of work units that we don't need.  So really want a different solution.

I found the infor documentation, Creating a Custom Java Trigger API for Infor Process Automation and one for LPL.  They are basic! one or two pages long, ha.  I'm going to keep trying.  Is it possible to copy and then modify an existing trigger?