Table Creation:

Data Dictionary: SE11

Provide a name for table ZCUSTOMER_DEMO

 Provide description for table Delivery class A for Application Tables Maintenance is allowed

Delivery class
The delivery class controls the transport of table data when installing or upgrading, in a client copy and when transporting between customer systems. The delivery class is also used in the extended table maintenance.

There are the following delivery classes:

A: Application table (master and transaction data). C: Customer table, data is maintained by the customer only. L: Table for storing temporary data. G: Customer table, SAP may insert new data records, but may not overwrite or delete existing data records. The customer namespace must be defined in table TRESC. (Use Report RDDKOR54 here). E: System table with its own namespaces for customer entries. The customer namespace must be defined in table TRESC. (Use Report RDDKOR54 here.) S: System table, data changes have the same status as program changes. W: System table (e.g. table of the development environment) whose data is transported with its own transport objects (e.g. R3TR PROG, R3TR TABL, etc.).

Maintenance :

Display/maintenance not allowed The usage of standard table maintenance tools is not allowed.

o o

Maintenance and display of this Dictionary object is not possible in transaction SE16. Transaction SE54 does not allow the generation of a maintenance dialog, which means automatically that calling transactions SM30/SM34 for this Dictionary object is no longer possible.

Display/maintenance allowed to limited extent Usage of standard table maintenance tools is allowed to a limited extent:

o o o

Transaction SE16 allows the display function for this Dictionary object, but no maintenance. Generation of a maintenance dialog for this Dictionary object is possible using transaction SE54. Transaction SM30 does not allow maintenance and display functions for this Dictionary object Note: The generated dialog can be included in view clusters (data maintenance through transaction SM34) or called within a program through the function module View_Maintenance_Call.

Display/maintenance allowed The usage of standard table maintenance tools is allowed:

Transaction SE16 allows the maintenance and display functions for this Dictionary object. Note: If an SM30 maintenance dialog exists for this Dictionary object, it is called.

o o

Transaction SE54 allows the generation of a maintenance dialog for this Dictionary object. Transaction SM30 allows the display and maintenance functions for this Dictionary object. Note: The generated dialog can be included in view clusters (data maintenance through transaction SM34) or called through the function module View_Maintenance_Call in the same way as the transaction call SM30.

Click on technical settings in Application tool bar

 Provide Data class and size category Save and back

Data class in technical settings

The data class defines the physical area of the database (for ORACLE the TABLESPACE) in which your table is logically stored. If you choose a data class correctly, your table will automatically be assigned to the correct area when it is created on the database. The most important data classes are (other than the system data):

APPL0 APPL1 APPL2

Master data Transaction data 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. Note:The data class only has an effect on table storage for the database systems ORACLE and INFORMIX.

Enter fields with data elements, domains Creating a data element: Zcustnum

Provide description and domain name Save Now double click on domain, and go ahead creating domain.

 Provide short description Data type and size in chrecters Save and activate the domain Go back to the data element and activate the domain Go back to the main screen of table creation

As fallow create all the fields

Go to Extras menu and provide enhance ment category- Can be enhanced

Provide atleast one field as key field Save and activate ..Now table is created successfully

Establishing foreign key relation

Create a table as follows

Now go to the customer table

Select the dept number and click on foreign key relation

Provide the check table name as dept table Click on button Generate praposal Then copy button

Now foreign key relation is established between two tables. We can also identify the foreign key tables associated with the current table by checking in tab and we can find our foreign key table here

Steps to create entries to a table: Open the table

Go to the menu Utilities->Table contents-> Create entries as follows.

Provide the entries as many no.of records you want to create Note: Provide the value for deptnumber that is already existed in Depttable .

Creating a stucture :
Go to transaction se11 Select the data type: Provide a name for the structure, Here it is ZSTRUCTURE_DEMO

Select structure radio button here.

Provide description And create the structure with following fields.

Now go to extras->enhancement category and select the enhancement category . Save & activate. *-------------------*Structure created successfully*-----------------*

Including structure to the tables

Open the existing table customer

Include the structure as follows

Position the at where you want to insert this include Edit->Include->insert

Specify the name of include structure Save and activate, The included structure will look like follows

Including same structure in Manager table

After including the structure

Domain with fixed value range