TECHNICAL SETING

[Former Member]

HI,

WHAT IS THE USE OF TECHNICAL SETTING IN TABLE CREATION AND

EXPLAIN MAINTENANCE VIEW

THANK YOU

ASHOK KUMAR

[Former Member]

Hi Asohk,

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):

o APPL0 Master data

o APPL1 Transaction data

o 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.

Note:The data class only has an effect on table storage for the database

systems ORACLE and INFORMIX.

Size category

The size category determines the probable space requirement for a table

in the database.

You can select the categories 0 to 4 for your table. Each category is

assigned a specific fixed storage area value in the database. When you

create a table, initial space is saved for it in the database. If more

space is required later as a result of data that has been entered, the

storage space is increased in accordance with the category selected.

Press F4 on the field Size category to see the number of data records

that can be maintained for the individual categories of your table

without complications ensuing. These complications could be for example

a reorganization becoming necessary because the maximum space to be

reserved for the table was exceeded due to the maintained size category.

Thanks,

Reward If Helpful.

[Former Member]

Hi

technical settings are required in table creation for the following reason

To identify the Size of the Table Created and to Set whether buffering needs to be done for the table or not.

Maintenance View ( SE54 )

Maintenance views enable a business-oriented approach to looking at data, while at the same time, making it possible to maintain the data involved. Data from several tables can be summarized in a maintenance view and maintained collectively via this view. That is, the data is entered via the view and then distributed to the underlying tables by the system.

for maintenance view please check out the following link it might help you

http://help.sap.com/saphelp_40b/helpdata/en/cf/21ed2d446011d189700000e8322d00/content.htm

*****please reward points if the information is helpful to you********

[Former Member]

Ashok,

The required fiedls are the dataclass and size catagory:

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):

o APPL0 Master data

o APPL1 Transaction data

o 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.

Note:The data class only has an effect on table storage for the database

systems ORACLE and INFORMIX.

Size category

The size category determines the probable space requirement for a table

in the database.

You can select the categories 0 to 4 for your table. Each category is

assigned a specific fixed storage area value in the database. When you

create a table, initial space is saved for it in the database. If more

space is required later as a result of data that has been entered, the

storage space is increased in accordance with the category selected.

Press F4 on the field Size category to see the number of data records

that can be maintained for the individual categories of your table

without complications ensuing. These complications could be for example

a reorganization becoming necessary because the maximum space to be

reserved for the table was exceeded due to the maintained size category.

Don't forget to reward if useful....

[Former Member]

Hi,

In technical setting only we can specify the table size and Usage of the table .

Maintenance view is a view that user can edit the table entries directly in SM30.

Regards,

Nandha

Reward if it helps

[Former Member]

Hi Ashok,

Here you normally specify details that are required for buffering of data.

Thanks...

Preetham S

[Former Member]

Hi,

Technical Setting:

By specifying technical settings we can control how database tables are created in the database. The technical settings allows us to

· Optimize storage space requirements.

· Table access behavior.

· Buffering required.

· Changes to entries logged.

Maintainence View: (The symbol r inside a circle stands for '-->' )

Creating a Maintenance View

Enter the name of the view in the initial screen of the ABAP Dictionary, select object class Views and choose Create. A dialog box appears, in which you must choose the type of the view. Select the type Maintenance view.

The maintenance screen for maintenance views appears. You will see three input areas for tables, join conditions and view fields. Carry out the following actions in this screen:

Enter a short explanatory text in the field Short text.

In Tables, enter the primary tables of the view.

If required, include more tables in the view. In a help view you can only include tables which are linked to one another with foreign keys.

Position the cursor on the primary table and choose Relationships. All existing foreign key relationships of the primary table are displayed. Check the foreign keys you require and choose Copy. The secondary tables involved in such a foreign key are included in the view. The join conditions derived from the foreign keys ( Foreign Key Relationship and Join Condition) are displayed.

You can also include tables which are linked to one of the previously included secondary tables with a foreign key. To do this, position the cursor on the secondary table and choose Relationships. Then proceed as described above.

You can only select foreign keys in which the secondary table for the primary table or for the secondary table which transitively preceded it is in an n:1 relationship. This is the case if the secondary table is the check table of the base table and the foreign key was not defined generically. If the base table is the check table, the foreign key fields must be key fields of a text table or the foreign key must have cardinality of n:1 or n:C.

The foreign keys violating these conditions are displayed at the end of the list under the header Relationships with unsuitable cardinality.

Select the fields which you want to include in the view.

You can enter the field names directly. If you do not know the field names, you can copy them from the tables. To do this, position the cursor on a table and choose TabFields. The fields of the table are now displayed in a dialog box. You can copy fields from here by marking the first column and choosing on Copy.

Formulate the selection conditions. To do this choose Goto ® Selection condition. The input area for the selection conditions appears in place of the input areas for the fields. Maintain the selection condition as described in Maintaining the Selection Condition for a View. You can then switch back to the fields display with Goto ® View fields.

Activate the view with View ® Activate. A log is written during activation. You can display it with Utilities ® Activation log. If errors or warnings occurred during the activation of the view, you branch directly to the activation log.

Create the documentation for the view with Goto ® Documentation. This documentation is output for example when you print the view with View ® Print.

Branch to transaction SE54 with Environment ® Tab.maint.generator. From the view definition you can generate maintenance modules and maintenance interfaces there which distribute the data entered with the view to the base tables. You can find more information about using this transaction in the documentation Generating the Table Maintenance Dialog.

Optional Settings

You can make the following optional settings:

Change data element of a view field:

Select the Mod column (modify) for the view field and choose Enter. The Data element field is now ready for input. Enter the new data element there. This data element must refer to the same domain as the original data element. With the F4 help key for the Data element field, you can display all the data elements which refer to the domain of the field. If you want to assign the original data element again, you only have to reset the Mod flag and choose Enter.

Change maintenance status:

The Maintenance Status defines how you can access the view data with the standard maintenance transaction (SM30). Choose Extras ® Maintenance status. A dialog box appears in which you can select the maintenance status of the view.

Define the delivery class of the view:

Choose Extras ® Delivery class. A dialog box appears in which you can enter the delivery class of the maintenance view.

Define the maintenance attribute of a view field

The maintenance attribute defines special access modes for the fields of the view. You can make the following entries in field F in the input area for the view fields:

R : Only purely read accesses are permitted for fields with this flag. Maintenance with transaction SM30 is not possible for such fields.

S : Fields with this flag are used to create subsets when maintaining view data. Only a subset of the data is displayed. This subset is defined by entering the corresponding value in this field.

H : Fields with this flag are hidden from the user during online maintenance. They do not appear on the maintenance screen. You have to ensure in a separate procedure that each such field has the correct contents. Otherwise, they are left empty.

: There are no restrictions on field maintenance.

Check functions:

With Extras ® Runtime object ® Check you can determine whether the definition of the view in the ABAP Dictionary maintenance is identical to the specifications in the runtime object of the view. With Extras ® Runtime object ® Display you can display the runtime object of the view.

Display foreign key of a view field:

If a foreign key which was automatically included in the view definition is defined for the field of the base table, you can display it. To do so, position the cursor on the view field and choose Extras ® Foreign keys.

Display foreign key on which a join condition is based:

If a join condition was derived from a foreign key, you can display its definition. To do so, position the cursor on the join condition and choose Extras ® Foreign keys.

*****Reward points if helpful.

All the best