To adjust/change any keyword or DDIC field name, navigate to CMOD and browse to the option Goto->Text Enhacements->Keywords->Change.

It will ask you for the field name you want to modify/enhance. Here specify the Field Name and the language in which you want to change to be made.

It will take you the screen where you can specify various type of  texts for the field name enhacement. Change the text as desired and save. It will impact the keyword throughout SAP.

You might also be interested in these posts:

1. Dynamically read fields, field names and field contents using field symbols
2. Field Exit in SAP
3. Add Search Help to Screen Field in SAP

Since it is not possible to create the secondary INDEX for cluster tables, SAP came up with new concept called INDEX tables.

All the accounting documents (Open and closed) are stored in BKPF and BSEG tables and querying these tables takes lot of time. So SAP has created INDEX tables for BSEG which are updated with specific data based on classification and are much faster than BSEG.
 
EG: Customer documents, Vendor documents etc.
 
INDEX TABLES:
 
BSID- Accounting: Secondary Index for Customers (Open Items)
BSAD- Accounting: Secondary Index for Customers (Cleared Items)
BSIK- Accounting: Secondary Index for Vendors (Open Items)
BSAK- Accounting: Secondary Index for Vendors (Cleared Items)
BSIS- Accounting: Secondary Index for G/L Accounts (Open Items)
BSAS- Accounting: Secondary Index for G/L Accounts (Cleared Item)
 
How to remember these tables???
Remember BS*  *
 
3^rd letter indicates whether item is open or closed.
I - For open items.
A-    For closed items.
 
4^th letter indicates classification. 
     D- For customers
     K- For vendors
     S- For G/L accounts.
 
These tables are some examples which is mostly required in real time scenarios. There are few more INDEX tables like this.

You might also be interested in these posts:

1. SAP Tables Part I
2. Improving Workflow Performance
3. Transport SAP Table contents

Example Scenario

Now?  There was a business change and company code IN01 would no longer be used and will be replaced with IN02. The ABAP and BASIS teams are entrusted with the responsibility of creating new variants/change the existing variants.

How?  Automation can be achieved by the following piece of code:

Source code: Z_VARIANT_CHANGE

You might also be interested in these posts:

1. Transport Variants of an ABAP Program
2. ABAP Program for Table Maintenance in SAP
3. Debugging Background Scheduled Jobs in SAP

There have been some codes available on net where data is backed-up but not restored back to SAP.

It is basically Dynamic table export / import facility.

There are some restrictions for using the code:

* – Table definition MUST exist on target system for import.

* – Entire table is exported / imported.

* – Must be WIN95/98 WIN-NT long filenames.

Download code : Upload/Download Program

You might also be interested in these posts:

1. Upload File from Application Server into ABAP Internal Table in SAP
2. Downloading PF-Status(GUI Status) in SAP
3. ABAP HR program to download Employee data

For the same purpose, we can use SCC1 Tcode.  SCC1 T-Code u can do the transport in same R/3 System but different client like

Source : 100(DEV)
Target-1 : 200 (QAS)
Target-2: 300 (PRD)

SCC1 Just specify Source Client and the Request number and import the request.
In this process u don’t have to release the transport request.

You might also be interested in these posts:

1. Transport SAP Table contents
2. Downloading PF-Status(GUI Status) in SAP
3. Tcodes in SAP – Part 1