ABAP reports not modifiable in the DEV system

[Former Member]

Hi Experts,

We have done the copy client from PRD to new DEV server as we our discontinuing our old DEV server.

But the problem is ABAPers can not able to modify their own created custom reports in new DEV server though we have given same role as they were having previously. However, they can able to create new programs without any problem but the existing one they can't modify.

Also, they are not getting any kind of errors while going into change mode of any existing report but just getting one information message and then its coming in Display like mode. Please refer attached screens.

Any help or suggestion would be highly appreciated.

Thanks.

[former_member586730 · Accepted solution]

Hi Alis,

The report is going to editable mode with Modification Assistance Parameter Turned On. They can still edit it using Modification Assistant or can turn off the  Modification Assistant and continue to edit as normal report.(See Edit --> Modification operation in SE38 editor.)

The Modification Assistant is the tool that offers you support when making modifications to the standard but in your case its turned on for custom reports as well. It seems all you SAP objects are being treated as repaired as they have been moved from production to development.

Thanks,

R

[Former Member · Accepted solution]

Thanks a lot Ritesh...it solved the issue

[matt · Accepted solution]

It may not have solved the issue in the best way. What objects that you should use the modification assistant? If you switch off the modification assistant globally, you'll have a world of pain come upgrade.

Go to SE03

Choose "Change Object Directory Entries"

Enter the system number of your production system (e.g. P10) in "original system".

Put the cursor on the Pxx node.

Click on "select" (F6)

Enter mass in the OK CODE field.

Check the "Original System" check box and enter your Dev system id, Dxx

Press Enter

[SimoneMilesi · Accepted solution]

Matthew Billingham wrote:


Or you could let each developer do this on an object by object basis.

That's the safest way in my experience.

A couple of click the first time you change a custom object are not a big delay or issue but it prevents you, for example, to change external packages from consultants or headquarters developers

[vwegert · Accepted solution]

Nice one - didn't know about that MASS trick. Thanks for sharing.

[matt · Accepted solution]

Found it on SCN once!