REQ SELF SERVICE

What do you mean by "your Custom Process Flow" ??

Rather than approve buy Just dollar amount we wanted to add Acccount number
to the criteria. We have some current process flow's developed for REQS. 08.0.03
I was trying to find out How to incorporate these into our new RSS (XML).

Norm.

Yes. You would need to use approval type "line using process flow". That way the variables for account-unit, account are sent whenever a workunit is created. Then you can use the variables to your liking in your flow..

Alex-

Ok, this my first post...I'm new to the requisition side of Lawson (we are 8.0.3 apps, LSF9 Technology, windows). Where do you set approval type? I see approval code, but not approval type...Thanks!

-Shari

Shari Trantas - The Approval type setting is found in versions 8.1 and higher.

Thanks, Bill!

So, if we wanted to send a req through approval (via ProcessFlow) according to account (ie. If it's coded to one account, we want to send through an expense approval flow vs another account we want to send through a capital approval flow) - how would you set up that criteria? Is it possible (via Service Criteria Level)? Thanks.


-Shari

Account isn't one of the standard criteria, so you'd have to define it as a criteria. But I've been able to do it right in the designer by adding a variable (called account) then bringing the value from MMDIST over in an ags call, assigning the variable to the MMDISTvalue, and then using the Branch to sort and route it. For example, I could send any request that hit the capital account to a different route.

Ok - that's a thought - can we then kick off another flow based off the account? For example, we would have a really simple flow that evalutes account. Then, basked off the account it would branch off to kick off a separate flow...(in LSF9).

Just because you can do something technically doesn't mean that you should. I wouldn't want a new workunit embedded in another workunit because if one fails, so would the other. Then I'd have two logs to go to to troubleshoot! Generally, lauch a second flow from the first when the second is an entirely different process. For example, after the req goes thru final approval, you set off another to run the PO100.

Shari, generally what clients do is use a single flow for the approval process. Within that single flow, it has many branches based on what type of requisition it is (i.e. CapEx, Asset, Expense, etc. ) and what level of approval is currently needed.

Thanks, John...

I think what we are trying to accomplish is trying to make it more simplified. Our approval process is so different between CapEx, Asset, Expense, etc. that the flow was huge and web-like! If we needed to change something in the flow it was so difficult to try to find where it needed to be changed (We never put the flow into production as the project was originally put on hold a while ago).

-Shari

I like to say that within a single flow, you can route anywhere as long as the level limits do not change (i.e. level 1 is always $1000). However, if level 1 is $1000 for expense, and $2500 for CapEx, but all computers need to go to entirely different approver...then that is best handled by 3 different flows and driven from the criteria.