Table analysis between two systems

The contents of a table between two systems can be checked through the transaction OY19

Table contents transport

Q – How do I delete table values from a client. For example I have 969 values in client 2 and 966 values in client 1. I want to move all 966 values to client 2, and therefore delete the surplus values in client 2.

Answer – This is easily done by using a asterix in the key in the transport. Create a transport for the table, eg: R3TR TABU and the key of the from client with a * in the next field of the key. The result will be the target client will have the values of the table deleted and all the values of the source client copied into the target client.

Dont forget to test you can use SCC1, between your development client and a sandbox/test client.

Can I compare the values inside a table across clients?

Hi There, I have a table with many entries in it. Is there a way to compare the data values across clients without having to export both tables and do a Vlookup / Hlookup in excel?

Yes, there is You can compare the values of records in tables across clients by using transaction SCMP.

SAP Change Logs

Use

To view the changes made to a table or a configuration node in the IMG, you can use transaction SCU3.

To view the changes, you must first have activated the change log for the required tables.

The system will read each change to an existing data record for example (Update/delete) and record it is table log.

Pre-requisite

In order to use table logging you need to do 2 steps:

Step 1:

Activate the system/client parameter. Check your systems value with RZ11 with the value: rec/client

Some options:

• rec/client = ALL - Log all clients.
• rec/client = 001,002,003 - Log the specified clients. (Note you can specify up to 10 clients.)
• rec/client = OFF - Do not log.
• TIP – make sure this parameter is the same for all servers of a system.

Step 2:

The Table then needs to be active for logging – you can do this in transaction SE13.

Additional Info

The data is stored in tables DBTABPRT and DBTABLOG.

If you have too much data in these tables:

• As of Release 4.5A you can use Transaction SCU3 to start a deletion program (Menu “Edit –>Change Docs –>Delete”).
• Or you can drop the table on database level and recreate it with transaction SE14.

History of table logging

• Report RSTBSERV was used prior to 3.0
• Report RSTBHIST was used between 3.0 and 4.5
• Report RSVTPROT is used after 4.5

Parameter Transactions (TCode for a Table)

Where are Parameter Transactions Stored?

Ans: In Table TSTCP.