This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Can someone explain to me how they have buyers configured and how (or if) they have workflow set up to direct desktop requisitions and/or PR routed to the appropriate buyer?
I'm working on something similar to that. . .I took three of the spare fields that cross from DR to PR to PO and assigned the same domain to all three of them. The domain is our list of departments. I added those 3 fields to the user screens and made them required. Their purpose is to help route it. The three fields are implemented as:
1) Department the person asking for the items works for (maybe you could even steal this from the person's Person record, but that wouldn't work for us)
2) Department ordered for -- could be different from #1, like if a Maintenance person is ordering something for our Food Service department, Academics, Publishing, Sales, Accounting, etc.
3) Department handling the order -- could be the same or different from both #1 or #2.
For example, I work in the Maintenance department. If I want a new computer, our procedures require I get approval from my department head AND IT's department head. So I fill out a requisition with Maintenance, Maintenance, and IT as my answers, respectively. Part of my workflow process is then to find "me" and where I fit in the Maintenance (answer #1) ordering process. It routes the PR to my boss, then his boss, and up the chain until it goes as high as it needs to. (I have these chains defined as Person Groups - just using the Person.Supervisor field wouldn't work for us in our environment).
Then it looks at answer #2, in this case again it is Maintenance. So it skips to answer #3 because it already got Maintenance approval. If answer #2 were different, it would route to the department head of that area.
Answer #3 is where it routes to the Purchaser of department #3. Actually it routes to the department head first (in my example and for our procedures, I wanted a new computer, I convinced my boss I should have one and he approved it, but I still have to get approval from IT to purchase it). If he approves, it goes to that purchaser.
And just to make sure I don't try to skirt the rules by choosing "Maintenance" on all three in order to get my computer (bypassing the approval from IT I'm supposed to get), I have measures in my Workflow that look at the classification of the item(s) being ordered and if the items are in certain "IT-approval required" classifications it will change my answers. (I modified the Classifications app, adding checkboxes to indicate that items in a category are IT-approval-required)
A second example: Maintenance man is repairing kitchen equipment and needs a part (often quite expensive, but that's beside the point). He requisitions it with Maintenance, Food Service, and Maintenance. My workflow process finds "him" and routes the PR to his boss, then his boss, etc. Once it clears through Maintenance, it goes to the department head of Food Service (so he can at least see how much of his money we're spending for him). Once he approves it, the PR goes back to Maintenance, also detecting that it has already passed through Maintenance for approval. As such it goes straight to the Maintenance Purchaser -- it does not seek approval again.
Hope that all makes sense and gives you AN idea. Maybe some others here have other/better ideas. It's pretty complex (much more than I've explained here), but I think it'll be sweet once all the quirks are worked out.
Travis Herron
--- In MAXIMO@yahoogroups.com, "cbrandon63" <cbrandon63@...> wrote:
>
> Can someone explain to me how they have buyers configured and how (or if) they have workflow set up to direct desktop requisitions and/or PR routed to the appropriate buyer?
>