2010 Sep 20 9:11 AM
Hello Friends,
In our current project, two teams are working on the developments. One team is for LES related developements and another team is for billing related developments. As part of developments, same programs are sharing by two teams, example -
Include - MV45AFZZ, the userexits in include are using by both the teams for their developments
Now the issue was, since the same program is using by both the teams, and during program activation , system automatically includes the code in both the team TRs. This was causing issue while testing and transport to other testing systems, since billing project is going live in next year and LES in coming november
Hence, we need to understand how we can differentiate the code which should not impact with other TRs.
Many thanks for your inputs
Best Regards,
Goutham
Moderator message: please do not start duplicate threads.
locked by: Thomas Zloch on Sep 20, 2010 5:30 PM
Hello Friends,
In our current project, two teams are working on the developments. One team is for LES related developements and another team is for billing related developments. As part of developments, same programs are sharing by two teams, example -
Include - MV45AFZZ, the userexits in include are using by both the teams for their developments
Now the issue was, since the same program is using by both the teams, and during program activation , system automatically includes the code in both the team TRs. This was causing issue while testing and transport to other testing systems, since billing project is going live in next year and LES in coming november
Hence, we need to understand how we can differentiate the code which should not impact with other TRs.
Many thanks for your inputs
Best Regards,
Goutham
Moderator message: please do not start duplicate threads.
locked by: Thomas Zloch on Sep 20, 2010 5:30 PM
2010 Sep 20 9:38 AM
As far as I know when you do a change to an object (here include) which is already maintained by someone else, the system will yell and will try to add new task to original developer's request. You can also change the task owner by reasigning this to other developer (the option is available from the context menu).
As for the changes which should not be applied pararelly, I think of two possibilites:
- switch off the code which is not to be applied in production system yet, by i.e. commenting it out, then (when next needed) send to production just the change for uncommenting this code
- create a separate DB table which will hold some flag, saying which part is to be executed. If flag is set then run the respective part, otherwise skip it. This way you can have sort of a switch in the live environment.
Regards
Marcin
2010 Sep 20 4:08 PM
Hi Goutham,
I would simply say to create 2 includes in your exit include one for the LES team and the other for the Billing team...This way ur code would also be neat and not messed up...
Hope this helps...
Regards,
Sitakant
Edited by: Sitakant Tripathy on Sep 20, 2010 5:12 PM
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |