Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from Waelz, Dean on Jan 10 at 5:17 PM Hi Peter,
IMO that's a management issue. Changes that made it to QAS but not all the way to PRD will be wiped out in the client refresh (as you know). The system developers should have been advised that the client refresh was coming (they were likely the originators of the request). The developers are accountable for the decision on when any particular piece of code/config is ready to move up - BASIS is simply the transport enabler. The developers have to keep track of their work in progress - I'd guess they were doing that anyway. The developers have to tell you (the BASIS/transport guy) what packages are appropriate to re-deploy into the refreshed client; that's not really your call (IMO). The process that allows the developers to efficiently communicate the exact transport list to BASIS would vary from shop to shop depending on what tools are used to track development progress/status.
Regards
| | | ---------------Original Message---------------
From: Snowy
Sent: Friday, January 10, 2014 11:29 AM
Subject: SAP Client Copy and Transport Issue
Hi,
simply export transports you are still working on BEFORE client copy. then, re-import these if needed.
thanks. |
| Reply to this email to post your response. __.____._ |   _.____.__ |
