data base tables

[Former Member]

hi experts

unfortunately in my 800 client mara table contents got deleted ?

how can i restore those data into (800) client my mara table from master clien (000).

please somebody can help

thanks&regards

satish

[Former Member]

Hi

If you are looking at moving configuration (SPRO) entries from one client to another, you can save the configuration table entries under a transport request and then import the transport entries into the target client by running the transaction SCC1 in the target client.

For copying transactional data, you can contact the BASIS team.

Authorizations for Creating and Copying Clients

Normally, you use the superuser (SAP* or equivalent) to create or copy a client. The superuser has all of the authorizations necessary for these operations.

Should you want to use another user, the user must have authorizations for three objects:

System Authorizations (S_ADMI_FCD): Define a new client in table T000 with the SAP Customizing system. Defining a client is the necessary first step in copying a client.

Maintenance of Client-Independent Tables (S_TABU_CLI): Authorization to copy table contents from the source client to the target client.

Table Maintenance (Using Standard Tools) (S_TABU_DIS): Authorization to maintain table CCCFLOW, the log table for the client-copy report.

If you want to copy user master records from the source client to the target client, you must also have a global authorization for this object:

User Master Maintenance: User Groups (S_USER_GRP)

You must copy user master records and authorizations to the target client if you want to execute the copy with a user other than the superuser. The target client must contain a user master record and the required authorization for the user with which you perform the client copy.

one more way to copy.

See Note 0001942 . You can do it at OS Level.

1) Generate a control file:

clientcopy

source client ...

target client ...

select * from yyy # for individual tables

2) R3trans -w <Log file> -u 1 <control file>

After verifying the client copy log, due to some storage probslems in table MOFF, this table could not be completely copied. To avoid having to perform the whole client copy process, just hte entries on table MOFF from the source client will be copied to the table MOFF on the target client 010 in thte target system T12.

1. In the source system (C12), create a control file, for example, expmoff.ctrl with the following contents:

export client

select * from moff where mandt = '002".

2. Run the R3trans utility with the previous control file:

R3trans -w expmoff.log -u 18 expmoff.ctrl

The -w flag indicates the log file, the -u flag sets unconditional modes for the transport. In the export phonase, unconditional mode 1 indicates the system to ignore the wrong status of transport requests.

Mode 8 allows direct selection of tables when the default modes are not allowed. By default, the previous command generates the data file trans.dat in the directory where the export has been executed. If both source and target systems share the transport directory, it wont be necessary to copy the trans.dat file. Otherwise you must use ftp.

3. Check the export log file, expmoff.log and verify it did not contain any errors.

4. Once in the target system, create the import control file, for example impmoff.ctrl with the following content: import client

5. Then execute it with the R3trans tool: R3trans -w impmoff.log -u 248 impmoff.ctrl

By default it uses the data file trans.dat generated by the previous commnad file. The unconditional modes used in the import phase are :

2 for enabling the overwriting of the original, 4 which ignores that the transport request was intended for a different target system, and

8 which allows for importing tables which are restricted by their table types. If you use the default options for the import, you do not need a control file.

The import can be performed directly with R3trans -i <file>.

6. Check the import log file, impmoff.log to check that the import runs fine without errors. You can also log on to the target client, 010, in the target system and look up the table contents with se16.

NOTE

You can also achieve this with a transport request, Object T3TR.TABU.<Table Name> and then double click and add the Key <Table name>.

Reward points if helpful.

Thanks and Regards.

Edited by: Ammavajjala Narayana on Mar 28, 2008 2:08 AM

Edited by: Ammavajjala Narayana on Mar 28, 2008 2:09 AM