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

SAP Best Practice - working parallely on same object

birendra_chatterjee
Active Participant
0 Likes
445

Experts,

We are doing a roll-out on a SAP box for a particular geography, which is already being used/live for other markets. There are 2 teams, one supporting the existing system, and our team for roll-out.

There are common includes that can be accessed by both the teams (for e.g. MV45AFZZ, RV50AFZZ, RV60AFZZ etc.).

Could you please suggest the best practice, in which both the teams can work on the same include simultaneously (like defining Z-includes in the standard include and working on them) and avoid any conflicts/ locks.

Rgds,

Birendra

Experts,

We are doing a roll-out on a SAP box for a particular geography, which is already being used/live for other markets. There are 2 teams, one supporting the existing system, and our team for roll-out.

There are common includes that can be accessed by both the teams (for e.g. MV45AFZZ, RV50AFZZ, RV60AFZZ etc.).

Could you please suggest the best practice, in which both the teams can work on the same include simultaneously (like defining Z-includes in the standard include and working on them) and avoid any conflicts/ locks.

Rgds,

Birendra

1 REPLY 1
Read only

Former Member
0 Likes
413

> Could you please suggest the best practice, in which both the teams can work on the same include simultaneously (like defining Z-includes in the standard include and working on them) and avoid any conflicts/ locks.

Not possible within the same System (sy-sysid) and the same Client (sy-mandt) - not that it makes any sense to do it anyway!

Cheers,

Sougata.