cancel
Showing results for 
Search instead for 
Did you mean: 

After transport changes are not immediatly avalable

Former Member
0 Kudos

Hallo.

When I import a transport request in our TES system, the changes are not immediatly available but we have to wait some minutes.

Why this?

Could you help me?

Thanks.

Mario

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

Hello Mario,

1. If you are working with old level of kernel and transport tools (tp and R3trans). if yes update these immediately.

2.if transport tools are new and updated then the problem is due to Buffer Synchronization :

After the transport, the changes are not done in the database level and not reflecting immediatly in the TCODE. And after some you are able to see the changes.

If this true, the the problem may the sync of the buffers. Try by executing /$sync after import. Which resets the buffer and next start of tcode buffers the program again.

Please check the settings of the profile parameter rdisp/bufrefmode is as per the note 1163741.

"If the changes are there after some time, then this is most probably a buffering issue. rdisp/bufreftime and bufrefmode can be checked but also DDLOG issues might be relevant.

Check whether the following parameters are set correctly.

rdisp/bufrefmode = sendoff, exeauto

rdisp/bufreftime = 60 (or less)

Best Regards

Niraj