on 08-17-2012 6:24 PM
Does these Z tables exist in the target system of the client copy?
If not , I suggest you put on hold the client copy .
Log in to the source system of client copy , create a workbench type transport request , add the objects as below
R3TR TABL ZCOMM
Add all the affected tables into the transport .
Then release the transport and import into target system. Then in target system , in SE11 check if the tables exist and is active . In SE14 , check the consistency of the runtime object and database object.
Once everything looks fine , resume the client copy again .
Regards
Ratnajit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you please execute transaction code se14 in the target system , enter the table name ZCOMM, Then adjust and activate the table. Then check the consistency of the runtime object and database object with the dictionary object. If everything looks fine , check in the database level if the entry for table ZCOMM exist in table DDNTT.
Then you can continue with client import.
Regards
Ratnajit
Can you export the table structure using the transport request I asked you to create on the source system. Create a workbench request and add the objects to the request as follows
R3TR TABL ZCOMM
Do it for all the tables . Then release the transport and import the request into target.
Then import the client request.
Regards
Ratnajit
Hi
I have created the workbench request for those tables and imported the same in target system. But it shows same error. But the thing is i have put TABU instead of TABL.
Now i have created a new request and try to import the same. But while adding teh request itself it is giving error 'addtobuffer'
Pl help to resolve the issue
Regards
Sugantha
The workbench requests are client independent , moreover the TABL ZCOMM is a repository object, so the import of the transport request containing the table structure can be done in any client. If you have imported the client with a warning , that should be fine . Just check ZCOMM has same number of entries in source and target client.
You are then good to go .
Regards
Ratnajit
Also the data elements and domains are custom objects (Z objects) which are used in the ZCOMM table. These also need to be imported , else the table cannot be activated.
I suggest check the package in which table ZCOMM is assigned by using SE11(Attributes tab) in source system. Then go to se80 , enter the package name . Then right click the package Select "Write transport entry" . Select all objects of the package . Transport this package to the target system.
Check if you can do that.
Regards
Ratnajit
Please ask the ABAP team to activate these objects in the source system , else inactive objects cannot be released within a transport request.
Let me tell you that this has been a long tedious work and generally whenever you export/import clients between systems , it is expected that the systems both the source and target should have the same contents in the ABAP repository . It seems your source and target systems do not have same repository content . By repository , I mean the ABAP source codes and ABAP dictionary contents. The permanent solution to such a problem would be to refresh the source system data with the target system using a backup/restore method if your RDBMS is same with same version. The client export/import only copies table contents for certain client specific tables and in some cases cross-client table contents depending on the copy profile , but never copies repository content.
This is the reason you are facing issues with every step you are performing.
Regards
Ratnajit
I suggest you use the following document to carry out the system copy .
Regards
Ratnajit
Please take a look at the following SAP Notes and the Link.
http://scn.sap.com/thread/1394038
70290
627454
Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.