Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

object was repaired in this system error while importing

Former Member
0 Likes
32,917

Hi,

  I am getting error as "R3TRPROG<XXXX> was repaired in this system with return code 8"  while importing the object from development system to Integration testing system.

I got many clue from NET but not helped me much

steps mentioned to rectify this error as below

          goto transaction SE03

  1. Object in Requests
  2. Search for Objects in Requests/Tasks
  3. click the 'Execute' icon (F8)
  4. in the 'Selection of objects' part of the window choose <PGMID> <OBJECT> <OBJ_NAME> and also select the options 'Also search for sub-objects (not for generic entry)' and 'Modifiable'
  5. click the 'Execute' icon (F8)
  6. a list of transport request will be shown. Look for the request with status 'Modifiable' and release it.

Alternatively you can check directly in table TLOCK using SE16. If there is an entry in table TLOCK then the field TKORR will contain the transport request number which contains the unconfirmed repair. Release the transport request and confirm the repair

i am not getting my objects neither in the repaired list nor in locked list. So i can say it didn't helped me

Please let me know what are the other reasons for this error.

Thanks,

Ajit

7 REPLIES 7
Read only

Former Member
0 Likes
15,215

Have your tried transporting with overwrite checked?

Neal

Read only

kiran_k8
Active Contributor
0 Likes
15,215

Could you please let us know what are the objects in the TR and their changes.

K.Kiran.

Read only

Former Member
0 Likes
15,215

Hi Ajit,

This error comes when the objects you want to transport is having some other system mentioned as ORiGINAL system in their attributes. Generally in support systems we have this error.  You can solve this problem by 2 ways.

1. Lock your objects in a REPAIR transport and then will not give error.

2. Reset the original system in SE03 for these objects. and then lock them in Correction/modification request and it will work. Go to SE03 =>Objects=>Display repaired objects=>select the particular objecct that you are working on and click on "Reset flag". It will make it original to the current system.

Thanks

Rakesh

Read only

0 Likes
15,215

Ajit,

I don't know if ORIGINAL system is cause for this error.But,if that is the cause then better change it in

DEV and then transport by following the below steps.

Go to SE03.

Select Change Object Directory Entries.

In the next screen select the desired object ID ( ie R3TR PROG etc) and feed the Object Name and execute.

In the next screen place the cursor on the object name and click on OBJECT DIRECTORY (change).

This will let you change the ORIGINAL SYSTEM details.

K.Kiran.


Read only

RaymondGiuseppi
Active Contributor
15,215

In the TARGET system, call transaction SE03 and select option "Object", "Display Repaired Objects"

Alternative, during import, transaction STMS, in option tag, check box "Overwrite Objects in Unconfirmed Repairs"

Regards,

Raymond

Read only

Former Member
0 Likes
15,215

Hi experts,

    Thanks to all. I got the solution with the same apporach se03 only. Only thing i was checking at source system end. We should look at the destination end.

Thanks

Ajit

Read only

Former Member
15,215

HI Ajit,

Please use the option 'Overwrite Objects in Unconfirmed Repairs' while importing the TR, it resolves the issue.

Note: the TR can be imported with warning but it will not impact in reflecting the changes to destination.

Regards,

Rukmini