topic Re: data dictionary in Application Development and Automation Discussions

data dictionary

Former Member — Wed, 01 Aug 2007 05:50:59 GMT

hi experts,i'm murali plz solve my doubts

1. can we create a z table with out a 'data emement'is it possible then how plz explain me with the steps plz?

2.in a 'DATA CLASS' we have appl0, appl1, appl2, how can we confirm that whether we have to give appl0, appl1, appl2? plz any one explain me on this?

3. wat's a client dependent table, and client independent tables can any one plz explain me with some examples?

Re: data dictionary

Former Member — Thu, 02 Aug 2007 04:58:59 GMT

1. yes

2. goto se11 and give ur table name goto tech.. settings there u can check the data class in storage location parameters.

3.all Z tables are client dependent and std tables are client independent

Re: data dictionary

Former Member — Thu, 02 Aug 2007 05:02:23 GMT

Hi Murali,

Objects used in several clients are called client independent while objects used in a specific client is called client dependent.

CLIENT DEPENDENT tables contain the column mandt as the first column wheras

CLIENT INDEPENDENT TABLES don't have this column.

Re: data dictionary

Former Member — Thu, 02 Aug 2007 05:04:44 GMT

Steps to Creating domains, Data Elements, Tables

To give you the steps for creating table:.

There are two approach in creating a table.

1. Bottom-up approach

2. Top-down approach.

Both are valid and you can choose which approach is suitable for you. I always use the bottom-up approach. Here are the steps to create the tables with this approach.

1. SE11 will take you to the DDIC and enter the name of the new table to be created. Let us say Zname. Click create.

2. Enter the short discription of the table and enter the field of the table. If it is primary key and you have to check the box.

3. Enter the data element and double click it, you will be asked to save and will take you to data element discription page. Enter the short discription of the data element and enter the information of domain like the length of field and type of field.

4. If you wanted to use the existing domain then its fine, or else, you have to create one. Enter the domain name in the data element page and double click it. Page will ask to save and jump to domain creation page.

5. In the domain page, you have to save the information which you have already given in the data elements page and check it. Before going to data element page, you have to activate the domain.

6. Go to data element page and save, check and activate.

7. Go to main table page and save, check, and activate.

8. Also, you have to save the technical settings of the table.

The table is now ready for operation. You can use it in your program or you can use it to enter information.

Check table: It is the table which will have all the information about the Foreign keys which are the primary keys in the check table.

It can be created by creating the foreign key from the main table. Click foreign key in the main table and it will take you to a page which will ask for table name and field to which foreign key relation has to be associated. Enter the information and you can create the check table automatically.

SM30 is used for maintenance of the table, that is to realease the errors occured during the creation of the table.

*reward for useful answers*

First up all, do you have DEVELOPER access key to create a Table? have you previously created any object in the system?

Take the developer access key and create the table

Goto SE11 Tcode

enter table name

press create

enter description

enter delivery class as 'A'.

press fields

enter some 3 fields with their data elements or press predefined type

enter the data type as CHAR and length some 10 like that enter some fields and save

press technical settings button on application toolbar

enter data class and size category and save and activate

Database table

Tables can be defined independently of the database in the ABAP Dictionary. The fields of the table are defined together with their (database-independent) data types and lengths.

A table definition in the ABAP Dictionary has the following components:

Table fields: The field names and the data types of the fields contained in the table are defined here.

Foreign keys: The foreign keys define the relationships between this table and other tables.

Technical settings: The technical settings define how the table is created on the database.

Indexes: Indexes can be defined for the table to speed up data selection from the table.

There are three categories of database tables in the ABAP Dictionary.

A physical table definition is created in the database for the table definition stored in the ABAP Dictionary for transparent tables when the table is activated. The table definition is translated from the ABAP Dictionary to a definition of the particular database.

On the other hand, pooled tables and cluster tables are not created in the database. The data of these tables is stored in the corresponding table pool or table cluster. It is not necessary to create indexes and technical settings for pooled and cluster tables

step 1. Go to transaction se11.

step 2. write a table name prefix with z.

step 3. Give description.

step 4. It comes to delivery and maintainance, In delivery class u have 3 types u can select any of those 3. I have selected as A(master and transaction data).

Along with this u have to mention ur data browser as Display/ maintainance allowed only.

step 5. Go to technical settings, specify ur data class (APPL0) and size.

step 6. Create your fields with data element and domain.

step 7. While u enter ur data element ( the name u give should prefix with z) double click on that.

step 8. Now u have two options either to create domain or data type. After creating this, it will ask for field label, mention the field label.

step 9. Now activate at the same screen and come back u'll come to data element screen then again activate. Finally u'll come to first screen.

step 10. Follow steps 6 to 9 for more fields.

step 11. then activate.

step 12. To create entries in the table. On menu bar u have utilities, in that u have table contents, in that u have create entries.

step 13. After every entry save the data. That will be saved in the databaase.

chk ths

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eb6e446011d189700000e8322d00/content.htm

Re: data dictionary

Former Member — Thu, 02 Aug 2007 05:05:01 GMT

The data class determines in which table space the table is stored when it is created in the database.

The size category describes the probable space requirement of the table in the database.

There are 5 data classes and 11 size categories. The data classes are:

APPL0- Master data (data frequently accessed but rarely updated).

APPL1- Transaction data (data that is changed frequently).

APPL2- Organizational data (customizing data that is entered when system is configured and then rarely changed).

The other two types are: USR and USR1.

hope it helps..

regards

dinesh

Re: data dictionary

seshatalpasai_madala — Thu, 02 Aug 2007 05:05:39 GMT

Hi,

1. can we create a z table with out a 'data emement'is it possible then how plz explain me with the steps plz?

Yes in SE11 when you create a table and its fields for each field click on the button "Predefined type" then you can give the type and the length of the field there.

2.in a 'DATA CLASS' we have appl0, appl1, appl2, how can we confirm that whether we have to give appl0, appl1, appl2? plz any one explain me on this?

This depends on what is the use of this table.

APPL0 Master data

APPL1 Transaction data

APPL2 Organizational and customizing data

Master data is data which is frequently read, but rarely updated. Transaction data is data which is frequently updated. Organizational und customizing data is data which is defined when the system is initialized and then rarely changed.

There are two more data classes available, USR and USR1. These are reserved for user developments. The tables assigned to these data classes are stored in a tablespace for user developments.

3. wat's a client dependent table, and client independent tables can any one plz explain me with some examples?

If you table has a field of type MANDT then that table is client dependant else it is not.

Regards,

Sesh

Re: data dictionary

Former Member — Thu, 02 Aug 2007 05:08:02 GMT

HI Murali,

Ans2:

If you choose the data class correctly, your table is automatically assigned to the correct area (tablespace or DBspace) of the database when it is created. Each data class corresponds to a physical area in which all the tables assigned to this data class are stored. There are the following data classes:

APPL0 (master data): Data which is seldomly changed. An example of master data is the data contained in an address file, such as the name, address and telephone number.

APPL1 (transaction data): Data that is frequently changed. An example of transaction data is the goods in a warehouse, which change after each purchase order.

APPL2 (organizational data): Customizing data that is defined when the system is installed and seldomly changed. An example is the table with country codes.

Ans 3:

There are two types of tables in an R/3 database: client-dependent and client-independent. A table is client-dependent if the first field is of type CLNT. The length will always be 3, and by convention, this field is always named mandt. If the first field is not of type CLNT, the table is client-independent.

This program selects rows from table lfa1 and writes out lfa1-lifnr. When this program is run, only two rows are selected: only those where mandt equals 800. This happens automatically because the first field in the table is of type CLNT. There are five rows in the table, but the program writes out only those rows where mandt equals 800. If the user were to log on to client 700 and run the same program, three rows of data would be found and written out. If the user were to log on to client 900, only one row of data would be found.

The logon client mechanism divides the rows within a client-dependant table into distinct groups. To access a different set of data, the user logs on and specifies a different client number.

NOTE

The user master records (containing R/3 user IDs) are client-dependent. Therefore, to gain access to a client, the security administrator must create a new user ID for you within that client.

Developers and testers use the logon client mechanism to create and access multiple, independent sets of data within a single table.

For example, assume two typical, asocial programmers are working on an enhancement to the billing system. Jim is modifying the update transaction and Jane is creating a new report to go with Jim's modifications.

Jane sets up data for her test run, executes her report and obtains output. Jim works in the next cubicle, but due to his antisocial tendencies is blissfully unaware that his transaction uses the same tables as Jane's report. He runs his transaction and updates the data. Jim got what he wanted, but Jane then modifies her code and runs her program again. Her output differs from the last run, and the differences many not result from her changes, but rather they may result from Jim's changes. What we have here is a failure to communicate.

If the tables used by Jim and Jane's programs were client-dependent, they could each log in to separate clients, set up independent sets of data, and test their programs without ever talking to each other. They could perform all of their testing in the comfort of their cubicles and in isolation from their coworkers.

To make their tables client-dependant, they only need mandt as the first field and the R/3 system will take care of the rest. When records are added to the table, the system automatically moves the current logon client into the mandt field when the record is send to the database. Their Open SQL select statements will only return rows where the client number in the table is equal to the their current logon client number. The Open SQL database statements insert, update, modify, and delete also provide automatic client handling.

If the tables involved are all client-dependent, there can be more than one group of testers working at a time in one test system. Two teams of testers can test divergent functionality in the same set of programs at the same time provided they log on to different logon clients. The updates done by one team will not change the data belonging to the other team.

A training client could also exist on the test system. The students could log on to one client and the testers could log on to another. Both would run the same set of programs, but the programs would access independent sets of data.

reward points if useful:)

Regards

Twinkle

Re: data dictionary

Former Member — Thu, 02 Aug 2007 05:19:15 GMT

Hi Murli,

Ya u can create your z table without create any data element.

Here the simple steps of created tabe without data element.

1. Go to se11 then give data class and allowing options.

2. Then give the fields name and press predefined type button.

3. So that your type field is now enabled.so u can give appropriate type.

4. Then go to techinical settings gives delivery class and size of table.

5. Delivery class means who will be maintain your table in future so select appropriate.

6. Save it and activate your table.

If helpful gives rewards.

Regards,

Gurprit Bhatia

Re: data dictionary

Former Member — Thu, 02 Aug 2007 05:22:54 GMT

Hi Murli,

Any table which contain mandt key is client dependent and rest of then client independent.

MARA,EKKO,EKPO,VBAK all are client dependent.

MODSAP,Modact is client independent tables.

Any configaration table is client independent.

Award points if it useful.