Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
I've been doing HR config for 13 years so I can nail down that side. It's the MM stuff that I'm still trying to master. The consultant that initially configured MM said that PR approval by cost center owner was not possible. This conclusion was based on the fact that when setting up the various characteristics, reference fields from CEBAN were being used, and in this structure there was no way to grab the cost center owner. At that time, we did not entertain custom workflow but are now in a position to do so.
This cost center approval strategy is all about me thinking ahead to us someday stepping away from a professional buyer model into self service purchasing. If I were an employee submitting a PR for an SAP MM for Dummies book, the approval would first get routed to my cost center owner, which would be defined as: there would be a relationship between org unit and cost center owner position. Based on the org unit that I belong to, the workflow would route the approval to the CC owner.
So if I understand you correctly, in the config for T16FW I would leave the object type and agent ID blank? Would the system then automatically search for a responsibility rule, or how do I link a responsibility rule to the release strategy? I have an experienced workflow developer here, but she's new to the area of MM and release strategies.
Second, I have been using positions as my agents. It's a pain every time there is a change to the approver. Is there no way to maintain this approver list as part of master data instead of config?
Thanks, Vlad
p.s. Mack007 -- Keeping position IDs in synch between systems/clients is not so bad. We own a tool called DataPort which allows me to port data over from Prod to Dev.
| | | ---------------Original Message---------------
From: sapnomad
Sent: Thursday, October 07, 2010 2:05 PM
Subject: Custom workflow approvals for PR
I have a few basic assumptions I'd like to get verified. Our release strategy for PR approval has become too inflexible to meet some new PR approval rules.
1) I'm assuming there is no user exit, or it makes no sense, to start building custom code on the current release strategy config?
2) With that the case, I'm assuming that we'll be able to achieve our objectives by abandoning the release strategy altogether and going with custom workflow.
3) We are running backend MM but have plans to deploy SCM in the future. When we do self-service purchasing, I'm assuming any custom workflows we build now for PR approvals can be fully leveraged within SCM?
Thanks for any input!
Vlad |
| __.____._ Copyright © 2010 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
| | Related Content Most Popular White Papers
In the Spotlight  _.____.__ |
Mark as helpful
