05-20-2008 2:01 PM
Hi Guys,
take the following szenario:
We have Development system A and a copy of this system Development system B. Where B is the project system. In the time the systems A and B will be enhanced using different development. At one point in time the developments from system B should be merged with system A. Could this merge be done using some similar functionality like the SPAU after SAP-Upgrade to ensure the developments with origin in A and developments with origin in B are compared and amended in the right way ?
Thanks for any idea in managing this.
Best regards,
André
05-20-2008 2:04 PM
ähm well, the idea is nice, but you will have such an extra heapload of work developing in two systems that it should be avoided unless its REALLY REALLY needed that way.
tho i cant help you in finding out if your idea was just nice and not practicable.
05-20-2008 2:12 PM
Hi,
i agree with you that this will absolutely cause extra effort. The issue is that for some reasons two project phases need to be developed for some time in parallel. That's not my idea - I'm just asking if there is a tool or something else like SPAU is available to support the different developers taking there developments from B to A without doing all manuelly with copy and paste as there can be objects forgotten and if just transported all transport requests from B to A all changes within A gets lost.
As far as I understand the SPAU the system compares the active versions of the dev system with the once of the productive system and display's them. Is it possible to use this mechanism - if my assumption is correct - for custom development as well ?
Regards,
André
05-20-2008 2:20 PM
ok a small excourse on SPAU.
When transporting a transport request into the system (same for hot-packages or release-change), a new version is beeing put into the version managment of the referred object.
SPAU compares the active versions with the ones which got transported.
Problem at this edge is that SPAU just scans for modifications.
Modifications are changes to SAP-Standard objects. SPAU just checks for differences in SAP object.
Objects in customer name room, x or y will be ignored.
Thats why i dont think you can use SPAU.
BUT well you could copy the SPAU, and then reprogramm it a way it will not ignore x and y objects.
When SPAU is done and all is fine, THEN you transport the things to test and productive Server.
Edited by: Florian Kemmer on May 20, 2008 3:20 PM
05-20-2008 2:29 PM
Hi Florian,
thanks for that excourse. Your solution looks feasable - if there are resources to amend a SPAU to ZSPAU. Thanks for that.
@All: Any other ideas ?
05-20-2008 2:33 PM
We have a similiar kind of environment and we are forced to do manual sync for each object modified in either developement boxes to the other box. It is extra work but still works.
05-21-2008 8:46 AM
Hi all, the big risk in doing completely manuell merge and nearly the end of some developments in the additional dev box is that the developer miss an object. An other idea comes in my mind is using something similar as a SAP note.
Idea: All developments which will be carried out in devbox B must be bundled into a "custom note" and implemented into Devbox A using SNOTE. Is that possible to bundle your own note and import/implement it like SNOTE will do ?
Do any one knows how an note is structured in this matter?
Thanks.
Best regards
André
05-21-2008 2:16 PM
An automated approach will definately be a perfect solution. But will it take care of dependecies. Say for example in one of the environments for a production issues you had to change some logic in one part of code. the same part of code was modified in the other environment for a different reason. Will the automated approach take care of this scenario?
05-21-2008 3:01 PM
Hi,
this exactly the case where the automated approach has at least to indicate with a red light or something like that (as in SPAU or SNOTE) the user has to do the merge manually. But the most of the different developments in the system should be merged automatically (if possible) so the developer can focus on the once they realy need to have attention for.
Regards,
André