Hi IPA Community,
Presently working on how to build a efficient Requisition Line approval... Any ideas or views on the same is most welcome
Thanks and Best Wishes,
Naresh.
I've entertained this idea as well. I believe the Infor provided service would create a Workunit for every line in the Requisition which would not work for our organization, we'd want to be able to create an approval for each unique cost center on the Req.
Joy:
If this is a Cloudsuite FSM flow, I believe there are at least 2 RequisitionLine BusinessClass location attributes that are not derived: RequestingLocation and PurchaseFromLocation, these should be unique for each line.Location based filtering should route the approval to the user with the key an filter that match the line location, but you will need to modify the
If this is Lawson LSF, I believe the REQLINE RLN-REQ-LOCATION is what you are after, then configure filtering and the flow accordingly.
This is for Lawson LSF - we would want to use the Company and Account for the Reqlines to base the filtering on. I had not tried to build anything but had asked the question in an Incident and was told each line would create a unique WU. Your thoughts are that it is possible to write the flow so that it would split on unique Company and Account for approval? If yes, then I will definitely put some time into that. It would be beneficial for our invoice approval flow as well.
I am not sure what you mean by "split"; using Criteria or Filtering you can control routing to the approvers. The LSF flows are delivered with the IPA install. You will find it in your IPA install; samplesIPASolutions. I combine the header and lines flows all the time, opting to let the header flow create one workunit, join with the REQLINE and iterate. I create routes to UserActions based on the unique requirements of the customer. You are not required to use the "line" or "grant management" only flows, they are starting points.
