Distributed Development

[hardyp180]

Dear All

Does anyone work for a large company which has more than one development system e.g. one in America, one in Europe, one in China?

I would imagine most companies only have one central system for developing custom programs, otherwise you would run the risk of a situation where different countries have different versions of the same custom object. But, for the sake of argument, let's just say you did have more than one development team, does anyone have any ideas how to guard against the situation where two teams are changing the same object simultaneously?

Cheersy Cheers

Paul

[Former Member]

Hi Paul,

You can do one thing.

You can create your own transaction screen say ZSTART which will take two values :

transaction code and object name like

SE38 ZXXXXXXX

or

SE24 ZCLASSNAME

etc.

Create a RFC which will be give status of object locking.

Now the main transaction say ZSTART wiill do this.

It will make an RFC call to other sytems and check if the object is locked by someone, if yes it will not call the said transaction else it would go and call the transaction. So this will resolve your issue.

Also, for this access to all the transactions thru the commans need to removed.

Hope this gives an idea

Regards

Nishant

[Former Member]

Hello Paul

We can explore the option of using the <b>remote comparison</b> option that we have.

We have an RFC call to the target system, we replicate/or use the SAP functionality (SE38 wherein we can do a remote comparison (Utilities-> Versions -> Version management-> Remote comparison) )

If any differences are found it means the code is not in synch.

Regards,

Arun