System setting does not allow changes to be made to object
To trouble shoot some Agentry issues, you may need to use TCode SE37 to debug the BAPI. It is recommneded that you can copy the module and debug with the created one.
But when you try to copy the module, it may show the error below:
The error is because the /SMERP is set to “Not Modifiable” and you need to use TCode SE03 to set it to “Modifiable”.
(Note: To do the operation, you need to be an administrator of the system.)
You can follow the steps shown in the screen shots below to configure it.
- Using TCode SE03 and choose “Set System Change Option” under “Administration”.
2. Choose the one you need and change it to “Modifiable” and save.
Then try again with SE37 and you can get what you want.
thanks! it helps me a lot!!
thanks for sharing.
However in real case scenario, I never copy the function module before debugging and I never see it necessary. Any reason for the recommendation?
When our developers check the function from the customer, it will help avoid changing the code during debugging. We may try to change some parts of the code to make sure whether it is a code issue or not.
So usually we have two ways to do the trouble shooting of back end issue:
I'm sorry but this doesn't make much sense, specially for Agentry function modules like the one from the screenshot that does not have any code, only one line with an include.
And if what you want is to modify the include, just copying it and reusing in a new Z function module can raise a lot of unexpected issues given the complex dependences between some core Agentry Framework ABAP objects.
Actually we will only use this method to do the test and after the test we will delete the Z function. If the method works well, then we will consider to change the original file.
The only purpose of doing this is to avoid changing the code of the customer and also the standard one.