Regarding transport requests, sequences

[Former Member]

Hi All,

For the issue below i would need peoples suggestion as to how should we avoid it in the future.

We got 2 grp of development team in our office.

the fist grp worked on the smart form form1 and got it transported till qa.

the second grp again worked and got it transproted till qa after the first grp for the form 1.

Now when in qa the 2nd grp got the permission first to transport the smafrtform form1 till production. and the firat group's request got delayed because of the permission delay.

so what happened is the first request in the development finally reached production later than the second grp all all the efforts\ chages done by the first group got over written.

Need everybodys comment on the issue above as in how to stop it in the future.

IS there any way so that only the active version in the development should be transported to the qa and then prd. and also because of the whole confusion finally the active version of the smartfroms in development and production is different.

Summimg up the issue: Beacuse of the delays in the permissions finally the active version in the development and production differs......

[Former Member]

Hi All,

For the issue below i would need peoples suggestion as to how should we avoid it in the future.

We got 2 grp of development team in our office.

the fist grp worked on the smart form form1 and got it transported till qa.

the second grp again worked and got it transproted till qa after the first grp for the form 1.

Now when in qa the 2nd grp got the permission first to transport the smafrtform form1 till production. and the firat group's request got delayed because of the permission delay.

so what happened is the first request in the development finally reached production later than the second grp all all the efforts\ chages done by the first group got over written.

Need everybodys comment on the issue above as in how to stop it in the future.

IS there any way so that only the active version in the development should be transported to the qa and then prd. and also because of the whole confusion finally the active version of the smartfroms in development and production is different.

Summimg up the issue: Beacuse of the delays in the permissions finally the active version in the development and production differs......

[Former Member]

Hi Anu,

I would suggest you the following suggestion.:

1) Write modlog clearly while modifying any object. Now if person A changes the form he puts his modlog with details like what is the request number, transport number.

When person B got the request to change the same form, he should first check the modlog and then compare version in production and development. If any descripancy found, he should not start working on the requrest. The next changes should be done when the changes related to person A has been moved to production.

2) Incase changes for the person B are very urgent, then get the changes done by A backed out even from test systems and let the changes for B go to production first and then A can start working on it.

3) For changing SAP scripts and forms need to manually check with PD2 version. For program and other ABAP code, version check should be done mandatory.

4) You can create a tool which can detect the conflict when two people are changing the same object.

5) You can develope a good transport management system to handle this.

I think this approach will resolve your issue.

Reward if helpful.

Regards,

Shahu

[Former Member]

Hi,

I think the Technical/Development Team Leader actually should be aware of the work what each team member is doing what and when. It is Team Leader's responsiblity to guide/advise the team.Accordingly the request for approvals etc need to be planned and implemented.

Hope this helps.

Thanks,

Srinivas

[Former Member]

The most Important thing is to follow the sequence for a particular development. Always follow the same sequence to move to PRD the way it was moved to QA.

Shreekant