Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Hi Mukesh,
Unfortunately, I do not support your suggestion of creating a new release strategy or add a new code for the new approver. The reasons were simple -
1) People are always relocating themselves into different departments. Therefore, you can't simply change your release procedure to cater for this regular change.
2) Secondly, what are you going to deal with existing ones?. Are you going to delete it?. If yes, then how are you going to deal with outstanding purchasing documents?
3) Lastly, everytime, the new release strategy is changed, you will have to take care of outstanding purchasing documents to make sure no negative impact onto release strategy will take place.
Cheers,
HT
| | | ---------------Original Message---------------
From: ChunWai
Sent: Friday, October 29, 2010 6:51 AM
Subject: Change of release code in release strategy
Hi MM Experts,
Recently one of the PO approvesr went on leave. He has delegate this authority to one of his staff. Instead of using the substitution function, we just replace the original approval code with his staff approval code in the release strategy.
Now, all POs, including those approved before we change the release code, show the new approver's name. Since the workflow and business object are customized, can anyone clarify whether this is standard SAP behavior if we change a release code in the release strategy.
Thanks and regards,
Lai |
| __.____._ Copyright © 2010 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
| |  ha_tran
SAP Logistics Material Management Helper
Posted helpful replies on 50 threads in a group to earn a Silver Achievement Related Content Most Popular White Papers
In the Spotlight  _.____.__ |
Mark as helpful
