Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Hi Lai,
Yes this is standards SAP behavior, release strategy is dynamic in nature. any change in the existing release strategy will reflect in all the previous already released PO .
So the right move will be to have new release strategy or add one more code for new approver without removing the earlier one. do not make any precedence relationship with old code and also put suitable release indicator against old code.
regards,
mukesh (author @ sapbymukesh . com)
http://sapbymukesh.com/
| | | ---------------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 | | Related Content Most Popular White Papers In the Spotlight _.____.__ |