Overwrite objects

[Former Member]

Hi there,

I'm with a big doubt!!!

What happens when i transport a change request with many objects to a environment in production, but a object that is being transported, in the moment of the transport, it's being used in target environment.

How the objects are overwritten, if is it being used?

Thanks,

[Former Member · Accepted solution]

Thanks for your fast answers.

But this dump will happens with the transport or for the user that will be using the object?!

Is there a SAP recommendation for this process?!

Thanks again,

Dany Anderson

[Former Member · Accepted solution]

Hi Dany,

If at all dump happens it will happen for the users.

Regards.

Ruchit.

[Former Member · Accepted solution]

>

> If at all dump happens it will happen for the users. 
> Ruchit.

And this is why the "SAP recommendation" is to perform production transports during non-produciton hours.

Best Regards,

Matt

[Former Member · Accepted solution]

Hi Matt,

Seems like you are monitoring my posts

Regards.

Ruchit.

[Former Member · Accepted solution]

Hi Ruchit,

As a moderator, I monitor the Forums, not just your posts!

And...we like to post clarifying information whenever possible...it helps people learn and when searching in the future...

Best Regards,

Matt

[Former Member · Accepted solution]

The overall requirement for this from SAP is that you attempt to not transport objects into production while users are using the processes that you are effecting. Simple to say but in all actuality - not likely. What actually happens in the guts of the system is that all your programs that you write in ABAP are compiled and additionally are running a cached, compiled version in memory. When you make a transport of an object - if there are related objects with a dependency, upon the next request to access the effected code, it will re-compile on-the-fly and your user will take a few moments to get the transaction that they were looking for (the transport is not the trigger to re-compile).

So those users that are unlucky that are in the middle of using something that is effected will get a short-dump called 'Load Program Lost' or something to that effect (this is one of many dumps that could occur) that states that the program you are using was changed while it was running. Although the code should roll-back properly in the Db, you don't want to do this if you can avoid it. You can get some problems with updates and some objects have such a breadth of effected objects that the re-compilation may effect the entire system and force a shut-down due to a locking issue on re-compiling code. You need to check the transport logs to see the activation report to determine the impact - your QA box should provide enough details to identify how many objects are effected - sometimes changing one include may cause thousands of programs to need a re-compile.

If you want to check this out - you can do a small demo run with SE16 since it is a program that is created on the fly. Access SE16 - do a long query that will take a few minutes to get back - while it is running, open another session and access SE16 for the same table and update the fields for selection and when you do this - it will recreate the SE16 program for the table and short-dump the other one with a 'Load Program Lost'.

There are a number of other issues that have nothing to do with the time the transport was done but when the first next time the program is run to re-compile.

If this answers your questions, please set this thread to answered, if not, please provide your additional requirements so we can address your issues promptly.

[Former Member]

Hi Danny,

For starters you might get an ABAP dump stating that the object was changed while running. However as Juan pointed out this will happen in rare cases. But still to be on safer side production imports are normally done in non working hours.

We faced this issue once and switched over to non-working hours strategy in production immediately.

Also how are objects overwritten when used well the thing is simple. SAP locks tables and not reports and programs. Well a transport with code change can come while you are executing the program and bang there you go. Not only will it change the code of the program but it will also try to generate it.

Regards.

Ruchit.

[JPReyes]

This situation is unlikely..

As far as i know the enque will prevent the data from been overwitten if its in use... I presume transport will queue until the specific table/object is free or will simply fail.

Anyhow... if you have an important transport that will modify load of tables/objects you're better off to do it during a quiet time, meaning lunch or afterhours...

Regards

Juan