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

Tables cross client copy

Former Member
0 Likes
2,664

Hello ,

I have data in tabl1 and tab2 (both datbase tables) on client 001

Can i moved selected data of these tables to another client say 002.

Rgds,

Manohar

Hello ,

I have data in tabl1 and tab2 (both datbase tables) on client 001

Can i moved selected data of these tables to another client say 002.

Rgds,

Manohar

15 REPLIES 15
Read only

Former Member
0 Likes
2,271

Manohar,

To my knowledge Client copying of data from database tables is the job of a basis buy. I dont think we can do that on our own. Take the help of basis.

Regards

Read only

Former Member
0 Likes
2,271

Hi,

I suppose that you can try with <i>CLIENT SPECIFIED</i> addition for open sql stmts.

Svetlin

Read only

Former Member
0 Likes
2,271

Try the following:

1. read whole table TABL1 (SELECT * FROM ...)

2. loop through the according internal table and switch client from 001 to 002

3. Insert whole internal table into DB-Table with 'CLIENT SPECIFIED' Option.

Read only

Former Member
0 Likes
2,271

Hi Mani Sri ,

With ABAP you can do it using client specified option in open SQL statement . You can also do it using transports ( R3TR TABU <TABNAME> , additionally specify the key . With basis support move this transport to another client ) . But be careful if you are copying data in SAP Standard tables as this may lead to inconsistencies. Why dont you repeat the transactions on client 002 to populate the data which is in client 001.

Cheers.

Read only

0 Likes
2,271

Hi,

as Sanjay said you can create a transport.

If you have the authority you can do also the transport by our own. Just log on in the client 002, call the transaction <b>SCC1</b> and fill the fields <i>Source Client</i> (001 in your case) and <i>Transport Request</i>.

Please be carefully with generic specify keys in the transport -> Entries that are in the target client and not in the source client but match the generic key will be deleted in the target client.

Good luck...

Stefan

Read only

0 Likes
2,271

Hello Sanjay,

I thought about this but it does not allow me to select and proceed for the table, it stops saying LOCKABLE objects, i read the content but i am nto sucessful to put content.

<i>Why dont you repeat the transactions on client 002 to populate the data which is in client 001.</i>

I have 10 K records of Inspection plans created manully on quality client i need to move them to Production client.

I dont have Direct input or Bapi nor i can do BDC due to complex nature of dynamic screens.

Rgds,

Manohar

Read only

0 Likes
2,271

So you are moving data from one system to another system, not just between clients of the same system?

What table is it, SAP's or yours, transparent or config?

Srinivas

Read only

0 Likes
2,271

<i>So you are moving data from one system to another system, not just between clients of the same system?</i>

YES from QA to Prod.

What table is it, SAP's or yours, transparent or config?

Transparent tables

APPLICATION and MASTER data tables

Message was edited by: Mano Sri

Read only

0 Likes
2,271

Hi Mano,

Is it a custom table?

If yes, can you create table maintanance for this table? In SM30 you can select the table entries and create a transport request. This then can be transported to Prod.

Cheers

Vinod

Read only

0 Likes
2,271

1. Call SE16, mark all entries of the table, [Table Entry] -> [Transport entries] (change request is generated)

2. import the request into your QA

3. write a program to switch client


UPDATE table WHERE client = <old client> SET client = <new client> CLIENT SPECIFIED.

Read only

0 Likes
2,271

Hi Mano!

Just be careful: in case you have objects with internal number assignment, you might run into problems with transport (or insert) in other clients / systems.

There might be already an entry with same key value, which you could overwrite. And any later manual creation might lead to dumps, when internal number already exists by insert without number range adjustment.

Regards,

Christian

Read only

0 Likes
2,271

<i>1. Call SE16, mark all entries of the table, [Table Entry] -> [Transport entries] (change request is generated)</i>

<b>I am not if this is possible thsi option is greyed out for teh tables i use say QMEL.</b>

Christian Wohlfahrt

<i>And any later manual creation might lead to dumps, when internal number already exists by insert without number range adjustment.</i>

Yes, i do have inter number for characteristics we create

But i thought i will set the next number in the Number range object.

Read only

0 Likes
2,271

Hi Mano,

If you want to transport the content of table QMEL, I think it is not a good idea. Because this is an application table and there must be many tables related to this. Why you want to transport the table content to Production?

Cheers

Vinod

Read only

0 Likes
2,271

OK, then create the request manually:

SE01

- create new change request (let´s say 'transport of copies')

- jump into the object list of this request

- add entry 'R3TR' 'TABU'

- double klick on table name in object list

- enter key '*' (all entries will be exported)

- the occuring error message can be ignored

Read only

0 Likes
2,271

Hi Mano!

If you already plan to adjust current number in number range, then you are carefully.

If you have to copy configuration, there is a standard way: have a look at SAP-help http://help.sap.com/saphelp_erp2004/helpdata/en/24/903b39878f4205e10000000a114084/frameset.htm

Also Logistic data can be distributed, see corresponding link some lines below (or your other question).

Regards,

Christian