Transparent/Pool/Cluster tables

Transparent Tables:

1. Contain a single table. Used to store master data
2. It has a one-to-one relationship with a table in the database
3. For each transparent table there is one associated table in the database
4. The database table has the same name, same number of fields and the fields have the same names
5. Single table can have one or more primary key
6. Secondary indexes can be created
7. They can be accessed using open and native SQL
8. USE: They are used to hold master data e.g. Table vendors or table of customers. Example of transaction
    data is orders placed by customers


Pool Tables:

1. They are used to hold a large number of very small tables(stores customizing data or system data)
2. It has a many-to-one relationship with a table in the database
3. It is stored with other pooled tables in a single table called table pool in the database
4. The database table has different name, different number of fields and fields have different names
5. Table pools contain more tables than table clusters
6. Primary key of each table does not begin with same fields or fields
7. Secondary indexes cannot be created
8. They can be accessed using open SQL only
9. USE: They reduce the amount of database resources needed when many small tables have to be opened
    at the same time

Cluster Tables:
1. They are used to hold data from a few number of large tables.(stores system data)
2. It has a many-to-one relationship with table in the database
3. Many cluster tables are stored in a single table in the database called a table cluster
4. The database table has different name, different number of fields and fields have different names
5. Contains less tables than table pools
6. Primary key of each table begins with same fields or fields
7. Secondary indexes cannot be created
8. They can be accessed using open  SQL only
9. USE: They would be used when the tables have primary key in common and data in these tables are all
     accesses simultaneously

How to copy Idoc from one System to another system

- Below steps will be helpful to debug the production failure iodcs in your acceptance environment. Hope this may helpful for your issues with error Idocs data

Step 1: Go to transaction we19 and give the idoc number and ececute

Step 2: Click inbound file and remove the tick option from the start idoc inbound box.
provide the file name with directory ( Example, /local/data/interface/sample.txt )

Step 3: File will store in application server in AL11 transaction then download to that file using cg3y transaction code from production directory to your desktop and upload agian upload file to AL11 in acceptance environement directoty using cg3z transaction code.

Step 4: Now file placed under AL11, so just pass the file directory (/local/data/inteface/sample.txt)  in WE19 towards radio button  -- File as template. 

SteP 5 : Choose the option, file as template and execute.

Step 6:  You can see option to chose on the direction inbound or Outbound.

IDoc number will be generate ..