SAP Transaction Table

TSTC - SAP Transaction Codes

Used SE12 to display the tables.

Copying table entries from client 000

I need to copy table entries from client 000.
I have identified which entries I need to copy through running RPULCP00 but I don't know how to move the entries.

The simplest way is to go into the table through SM31
Then in your top row of buttons there should be one called 'utilities' from here select 'adjust',
Then select the client that you want to compare/copy from (you need to have an RFC destination set up).
This will then show you the contents of the table in both clients and identify the status of each record, they will fall into the following categories:
ML Differences, logon client entry
MR Differences, comparison client entry
L Entry only exists in logon client
R Entry only exists in comparison client
Identical entries
(M) Differences only in hidden fields

You should be able to scroll down the table, select the entries that you want to import, then hit the 'adjust' button, then hit the 'copy all' button, then back out with the green arrow, and save your table.

That should do the job.

Transport Tables between Clients

Use report RSCLCCOP to transport user master records, profiles and authorizatons between clients in an R/3 system.

Start RSCLCCOP from the target client which the users and authorizations should be copied.

Do not use this report if the target client contains some users and authorizations you want to preserve.

Finding any of the SAP tables that have been changed

During the production run of the SAP system, additional fields might have been added and you might have lost tracks of the SAP tables changes.

Transaction code SPDD have been created to help you to find all the SAP tables that have been modified.

Other ABAP Dictionary objects such as lock objects, matchcodes, and views, for which modification would not result in data loss, are not processed during the upgrade with transaction SPDD, but only after the upgrade is complete with transaction SPAU.

Basis - Edit, create, delete or adjust your database table

Edit, create, delete or adjust your database table

The database utility is the interface between the ABAP Dictionary and the relational database underlying the R/3 System.

This tools allows you to delete all the data in the tables.

You can call the database utility from the initial screen of the ABAP Dictionary with

Utilities -> Database utility (Transaction SE14).

You can use the database utility to edit all the database objects that are generated from objects of the ABAP Dictionary.

These are database tables that are generated from transparent tables or physical table pools or table clusters, indexes, database views and matchcode pooled tables or matchcode views.

If you want to use the database utility, you need authorization for authorization object

S_DDIC_OBJ, e. g. S_DDIC_ALL.

How to activate the IMG Change Log?

SCU3 transaction is used to see the IMG change logs for modified objects. 
If your table change log is not active, it will gives you a message that :-
...table logging is switched off...  
This particular setting can be changed in the following path :-
IMG--> Basis Components --> System Administration--> Tables changes recording 
You can log changes made to the following tables: 
- Control tables (system logic control) 
- Customizing tables 
What is recorded is always in the form of complete "before" images, that is, all entries as they appear before the changes.
The recorded data is compressed without buffering, and this is not an appropriate method for recording and managing large amounts of data. Activating logging impacts on performance as it entails twice as many database updates as would otherwise be the case, and the database storage load is also increased substantially. 
It is recommend that you use logging for your production clients and Customizing clients so that you can see exactly where Customizing tables have been changed. Other than the reasons above, it is not recommended that you use this tool for application tables. 
Two conditions have to be met for a table to be logged: 
1. The table has to be selected for logging in the Dictionary (see Dictionary -> Table maintenance -> Technical configuration). 
2. Logging also has to be set in the system profile
Set the rec/client (note the use of lowercase characters) profile parameter to one of the following values :-
- OFF: no logging at all (effectively a central system switch) 
- nnn: logs client-specific tables in client nnn only 
- mmm,nnn,ppp,...: logs client-specific tables in the named clients 
- ALL: logs all client-specific tables in all clients.  
Caution: Only in exceptional circumstances is it appropriate to use the 'ALL' setting. If, for example, the profile parameter is set to 'ALL' when you upgrade all test clients (including 000, the SAP client), these changes are recorded in the system log file. This reduces performance and requires a lot of database space. 
The default setting is OFF (no changes are logged). 
If logging is set in the ABAP Dictionary, changes to client-indepedent tables are always logged unless rec/client is set to 'OFF' 
Use the ABAP programs RSTBHIST or RSVTPROT to analyze table changes. RSVTPROT allows you to analyze change logs both at table level and with reference to Customizing objects. To access the program, select an executable Customizing activity in IMG and choose Goto -> Change log.  
 

Reorganization of Single Object

You have ARCHIVED the BSIS table (because of old data etc) and now this BSIS table has "holes" in physical structure and it's quite a large table.

Here are the steps to reorg. a single object:

1. Take a backup of your Oracle database.
2. Shutdown SAP
3. Start Oracle Database with Rollback Segment PSAPROLLBIG (all other smaller segments not started). Remember, the size of PSAPROLLBIG should be equal or larger than your BSIS table.
4. Ensure sapreorg directory has enough space for taking BSIS Oracle Export dump. The Oracle Export utility compresses the file to some extent.
5. Fire your SAPDBA from Unix level.
6. Go into SAPDBA "reorganisation" menu.
7. Select "Reorganize Single Table / Index"
8. Give BSIS as table name.
9. Start.
10. Don't Forget, first upgrade your SAPDBA tools first from OSS/SAPNet.
These include: 1. sapdba 2. brtools 3. brarchive 4. brbackup 5. brrestore 6. brconnect.