multiple developers in the same project

[Former Member]

We are implementing MII in globally in our company and have enlisted the help of a consulting compnay to help with developement.  The problem is that we have a couple internal developers and the couple consultants and are running into problems of multiple people working in the same queries, transactions, web cade at the same time and when saving loses the changes from the other users.  We designed our system according to SAP best practices with a central developement server and each site with its own developemtn and live environment.  As changes are made in the central dev system, we move them to the site dev systems for user testing and once approved to the live system.

I'm looking for advice on how to manage multiple developers in our environment so as to limit "crossfire".  We try to communicate but this can be difficult with the team working in multiple geographies.

[Former Member]

Hi Michael,

NWDI is certainly the tool that will help achieve some of the functionality you require, the DTR provides the basic check in / check out functionality common to most CVS systems.

The only downside is I believe right now you need to use NWDS to download the MII projects and compile them and manually deploy them onto your next environment (ie. DEV -> CONS -> QA -> PRD).

Otherwise you will need some careful planning of your project structures and have someone co-ordinating re-usable projects amongst your developer team else you will get everyone stepping over each other's toes...

Regards,

Danny

[former_member193328]

Hi

Just to add to what Danny said. Manual deployment is not necessary with NWDI as this can be done automated with NWDI. It can be manual as well if that is what you wish.

Check the attached document for more help and information

http://scn.sap.com/docs/DOC-1839

Regards

Partha

[Former Member]

We have the same problem.

I have looked into NWDI which will act as a source control, the users will need to 'check out' files which should lock the file from being edited by other users. I haven't tried this functionality but that is how most source control systems work.