Importing Tables from PROD to DEV system.

[Former Member]

Hello Friends,

I need your help regarding importing a few tables from PROD system to DEV system.

The following are the tables that I need to put in a Transport Request without making any changes to the table.

Tables are :

BKPF-for header information

BSEG- for the line items(two lines are currently present)

Indexes - as in BSIK/BSAK/BSID/BSAD/BSIS/BSAS

Is there any possibility as in how to put them into a TR without making any changes to the table ?

Thanks.

Danish.

[Sandeep_Kumar]

Yes , you can create a piece list and add these tables to it and transport.

[Former Member]

Thanks Sandeep. I got it.

But i have only got the structure and not the data. Is there any way in which i can even add the data in a TR and transport the same from PROD to DEV system.

Thanks.

Danish.

[Sandeep_Kumar]

Well that is also possible ... You can add all the entries to a TR manually or via SE16N .

But first you need to check whether your organisation allows such stuff.. i mean imkporting data from PRD to DEV system.

[vinod_vemuru2]

Hi,

Can you let us know why you want to import data of only these two tables? There are many tables linked to these like BAID, BSAD, BSIK, BSAK etc. These index tables will have part of the BSEG data. If you import only BKPF and BSEG, your system will have inconsistent data. Ideally production data is brought to Dev system via System refresh. But not by individual TRs for particular tables.

If you still want to transport the data from production to dev, below are the steps.

1. There should be transport route enabled from production to Dev.

2. Create TR in production, Include entries via the keys R3TR, TABU, <table name>, * (All entries).

3. Transport the TR from production to Dev.

My sugestion is not to do this and go by standard way of system refresh.

Thanks,

Vinod.

[Former Member]

Hi ,

Capturing the data of production in a TR and moving it to Dev is a matter of debate between you and your basis team. We cannot comment on that . But in my Opinion thats purely Basis work and never transporting from P-> D for sake of two tables is done, For sure this will hit data inconsistency as dependency is not set.

Alternate approach.

FM RFC_READ_TABLE check this option.

You can access the table data from Production into development environment

using a RFC function module to read table data.

Now the constraint is there should be a RFC set up between Development and Production => SM59 should work between these two.

You can load the production content of these tables into Development using the FM .

Br,

Vijay

[ThomasZloch]

Vinod and sniper already mentioned it. Don't transport application data like this, you will never have a consistent database in the target.

Also look at SAP's product "Test Data Migration Server" for moving selected data from production to other systems, if a full system refresh is not an option.

Thomas