transport error

[Nawanandana]

Hi All

i created z-table in the development and while i was transporting it to the production client, the following log error is occured,

R3TRTABLZLAB_DIP was repaired in this system

(ZLAB_DIP is the table name.)

regard

nawanandana

[Former Member]

I think you might have done some changes in the data element or domains used for the fields in that table. If there are any such changes done then those requests should be transported first before transporting the request for the table.

Best Regards,

Vibha Deshmukh

*Please mark all the helpful answers

[FredericGirod]

Hi,

for SAP a repair is a modification of an object that was not create in his own system.

For example, when you would like to modify a standard table (that was not create in your development system), SAP set a repair request order.

Are you sure that nobody has already create this table in your production client ??

Rgd

Frédéric

[Nawanandana]

at the moment anybody dont create that table in the production one.. but in the early i transport that ..after that i add another feild and i transport it agin in to production.. at that time gv me that log error.....

[Former Member]

after adding the field fields to the table u have to adjust the table by using the tcode SE11-->utilities->database utility--->activate and Adjsut DB table.

regards

Prabhu

[stefanh_lima]

hello nawanandana,

go to ta se11 and view the table. Select goto and display

object directory entry and then press lock overview. Now

you can see an Transport that locks the table. a second

step is to get an overview avout mofified object in the

ta se03 - display repaired objects.

hope it helps

regards

stefan

[Former Member]

Hi ,

Goto transactions se14 enter u r table and doActivate and adjust data base table u r problem will be solved.

[Former Member]

Hi nawanandana,

The problem is that the table ZLAB_DIP was modified in the production client. Transport the request in "<b>Overwrite Originals</b>" mode once again into production client and the error should be solved.

Regards,

Manoj