Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Two developers, one program

Former Member
0 Likes
713

Subject changed by moderator. Please use a meaningful subject in future

Dear guru ,

i have encountered an issue

we hav a project pressure.

me n my friend both want to write some codes in the same user exit in the same time due to the lack of time

what will be strategy to work on same source of code in same time.

and we know if u r in the editing mode my friend won't b able 2 write in it as it ll b locked by me .

but anyhow I hav 2 do both

how could I do

pls help

Edited by: Matt on Nov 13, 2008 5:35 PM

1 ACCEPTED SOLUTION
Read only

uwe_schieferstein
Active Contributor
0 Likes
691

Hello Saifur

You may have a look at my recent blog

[Dangerous Liaisons in User-Exits and How to Avoid Them|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/11882] [original link is broken] [original link is broken] [original link is broken];

which exactly discusses this problem and shows a simple way to organize this.

Regards

Uwe

7 REPLIES 7
Read only

ThomasZloch
Active Contributor
0 Likes
691

you could sit on his lap and code four-handed.

Read only

0 Likes
691

he may encounter some more issues...

Read only

matt
Active Contributor
0 Likes
691

Now, chaps, keep it clean...

Saifur Rahaman - create two function modules. One that holds your logic, one that holds his. Call those function modules from the user exit.

matt

Read only

ThomasZloch
Active Contributor
0 Likes
691

OK OK, so Uwe's excellent blog here might come in handy:

Or if that gun is too big, just create two separate includes.

Thomas

Read only

0 Likes
691

Thomas, you were faster than me )

Regards

Uwe

Read only

ThomasZloch
Active Contributor
0 Likes
691

Yes, I really liked that one. I had a similar situation a few years back, with distributed development teams working on the same exits. My solution was not quite as elegant, so I will deploy your design next time.

Cheers

Thomas

Read only

uwe_schieferstein
Active Contributor
0 Likes
692

Hello Saifur

You may have a look at my recent blog

[Dangerous Liaisons in User-Exits and How to Avoid Them|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/11882] [original link is broken] [original link is broken] [original link is broken];

which exactly discusses this problem and shows a simple way to organize this.

Regards

Uwe