Skip to Content
author's profile photo
Former Member

Table creation warning

Hello, I created a table and I got a warning message as follows :

" Enhancement category for table missing". I verified all the fields and

I didn't find anything wrong. Can someone give me some hints?

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • author's profile photo
    Former Member
    Posted on Sep 27, 2007 at 07:51 PM

    You can find the enhancement category on the Menu in Extras --> Enhancement Category.

    If you feel that there is no need to enhance your table then choose cannot be enhanced, else choose a valid category.

    If you choose any of the other options, in every program that you will use this table, you will a syntax warning indicating that this table can be enhanced.

    No matter what the category you choose, you will be able to come back and change it later.

    Hope it helped.

    Regards,

    Srihari

    Add comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 28, 2007 at 03:33 AM

    hi ,

    This problem occurs because the Enhancement type is not provided properly .

    To solve this proces like :

    on the table screen go to Menu options Extras -> Enhancement catagory -> select the radio button 'Can be Enhanced ( Deep ) .

    Thats all, you will not find anymore errors .

    Regards,

    Ranjita

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Posted on Sep 28, 2007 at 05:22 AM

    Hi

    after creating the table

    you ned to specify the technical settings

    that will be shown on the application tool bar , by clicking this button you will get one screen enter the values

    <b>Technical Settings in Dictionary</b>

    <b>The data class logically</b> defines the physical area of the database (for ORACLE the table space) in which your table should be created. If you choose the data class correctly, the table will automatically be created in the appropriate area on the database when it is activated in the ABAP Dictionary.

    The most important data classes are master data, transaction data, organizational data and system data.

    Master data is data that is rarely modified. An example of master data is the data of an address file, for example the name, address and telephone number.

    Transaction data is data that is frequently modified. An example is the material stock of a warehouse, which can change after each purchase order.

    Organizational data is data that is defined during customizing when the system is installed and that is rarely modified thereafter. The country keys are an example.

    System data is data that the R/3 System itself needs. The program sources are an example.

    Further data classes, called customer data classes (USER, USER1), are provided for customers. These should be used for customer developments. Special storage areas must be allocated in the database.

    <b>The size category</b> describes the expected storage requirements for the table on the database.

    An initial extent is reserved when a table is created on the database. The size of the initial extent is identical for all size categories. If the table needs more space for data at a later time, extents are added. These additional extents have a fixed size that is determined by the size category specified in the ABAP Dictionary.

    You can choose a size category from 0 to 4. A fixed extent size, which depends on the database system used, is assigned to each category.

    Correctly assigning a size category therefore ensures that you do not create a large number of small extents. It also prevents storage space from being wasted when creating extents that are too large.

    Modifications to the entries of a table can be recorded and stored using logging.

    To activate logging, the corresponding field must be selected in the technical settings. Logging, however, only will take place if the R/3 System was started with a profile containing parameter 'rec/client'. Only selecting the flag in the ABAP Dictionary is not sufficient to trigger logging.

    Parameter 'rec/client' can have the following settings:

    rec/client = ALL All clients should be logged.

    rec/client = 000[...] Only the specified clients should be logged.

    rec/client = OFF Logging is not enabled on this system.

    The data modifications are logged independently of the update. The logs can be displayed with the Transaction Table History (SCU3).

    Logging creates a 'bottleneck' in the system:

    Additional write access for each modification to tables being logged.

    This can result in lock situations although the users are accessing different application tables!

    after this step now check for the errors you won't get any errors

    <b>Reward if usefull</b>

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Posted on Sep 29, 2007 at 06:00 AM

    Hi

    For this warining you have to do like this

    after creating of table before activation it

    follow this path <b>Extras -> Enhance Catagory</b>

    by clicking on enhancement catagory it will ask for some options like

    1) can be enhanced Deep

    2) can be enhanced character type or numeric

    3) can be enhanced character type

    4) can't be enhanced

    5) not clasified

    if you don't find any thing regarding this then click the radiobutton not clasified

    then next activate it it won't show any warning

    <b>the datiled description of the enhancement catagory</b>

    <b>Enhancement Category Selection</b>

    Structures and tables that were defined by SAP in the ABAP Dictionary can be enhanced subsequently by customers using Customizing includes or append structures. The enhancements do not only refer to structures/ tables themselves, but also to dependent structures that adopt the enhancement as an include or referenced structure. Append structures that only take effect at the end of the original structure can also cause shifts - in the case of dependent structures - even within these structures.

    You must select an enhancement category for the following reason: In programs where there is no active Unicode check, enhancements to tables and structures can cause syntax and runtime errors during type checks and particularly in combination with deep structures.

    In programs where there is an active Unicode check, statements, operand checks, and accesses with an offset and length are problematic - for example, if numeric or deep components are inserted into a purely character-type structure and the structure thus loses its character- type nature.

    Depending on the structure definition, the radio buttons allowed in the dialog box are ready for input. Choose one of the possible enhancement categories:

    <b>Cannot be enhanced</b>

    The structure must not be enhanced.

    Can be enhanced or character type

    All structure components and their enhancements must be character-type (C, N, D, or T). The original structure and all enhancements through Customizing includes or through append structures are subject to this limitation.

    Can be enhanced or character-type or numeric

    The structure and its enhancement must not contain any deep data types (tables, references, strings).

    Can be enhanced in any way

    The structure and its enhancement may contain components whose data type can be of any type.

    Not classified

    This category can be chosen, for example, for a transition status; however, it must not be chosen for creating structures.

    The rules for defining the enhancement category result implicitly from the structure setup and the classification of the types used. These rules are as follows:

    If the object contains at least one numeric type or a substructure or component (field has a structure/table/view as its type) that can be enhanced numerically, the object can no longer be enhanced character-type, but is itself, at most, enhanceable character-type or numeric.

    If the object contains a deep component (string, reference, or table type), or it contains a substructure or component that is marked as enhanceable in any way, then the object itself is enhanceable in any way.

    If the object does not contain any substructure or component that is marked as enhanceable, you can select cannot be enhanced. If the structure has not yet been enhanced, you can choose the categorycannot be enhanced in any case.

    If you are creating new tables and structures in the ABAP Dictionary, the system proposes the category can be enhanced in any way as standard value for the classification of the enhancement options. If the developer chooses a more restrictive classification than can be enhanced in any way for a particular structure, then only the classification levels that adhere to the rules above are allowed. It is not possible to choose an enhancement option of a structure that is more restrictive than the classification resulting immplicitly from the structure setup and from the classification of the types used. Therefore, only the allowed categories are proposed for selection in the maintenance user interface.

    If a structure depends on one or several other structures, the smallest category is chosen as implicit classification (in the order cannot be enhanced < can be enhanced and character-type < can be enhanced and character-type or numeric < can be enhanced in any way). This classification is greater than or less than the category in the other structures and also greater than or the same as the category that results from the actual setup in the original structure itself.

    <b>Enhancement Category Selection</b>

    <b>Definition</b>

    Structures and tables that were defined by SAP in the ABAP Dictionary can be enhanced subsequently by customers using Customizing includes or append structures. The enhancements do not only refer to structures/ tables themselves, but also to dependent structures that adopt the enhancement as an include or referenced structure. Append structures that only take effect at the end of the original structure can also cause shifts - in the case of dependent structures - even within these structures.

    You must select an enhancement category for the following reason: In programs where there is no active Unicode check, enhancements to tables and structures can cause syntax and runtime errors during type checks and particularly in combination with deep structures.

    In programs where there is an active Unicode check, statements, operand checks, and accesses with an offset and length are problematic - for example, if numeric or deep components are inserted into a purely character-type structure and the structure thus loses its character- type nature.

    Depending on the structure definition, the radio buttons allowed in the dialog box are ready for input. Choose one of the possible enhancement categories:

    Cannot be enhanced

    The structure must not be enhanced.

    Can be enhanced or character type

    All structure components and their enhancements must be character-type (C, N, D, or T). The original structure and all enhancements through Customizing includes or through append structures are subject to this limitation.

    Can be enhanced or character-type or numeric

    The structure and its enhancement must not contain any deep data types (tables, references, strings).

    Can be enhanced in any way

    The structure and its enhancement may contain components whose data type can be of any type.

    Not classified

    This category can be chosen, for example, for a transition status; however, it must not be chosen for creating structures.

    The rules for defining the enhancement category result implicitly from the structure setup and the classification of the types used. These rules are as follows:

    If the object contains at least one numeric type or a substructure or component (field has a structure/table/view as its type) that can be enhanced numerically, the object can no longer be enhanced character-type, but is itself, at most, enhanceable character-type or numeric.

    If the object contains a deep component (string, reference, or table type), or it contains a substructure or component that is marked as enhanceable in any way, then the object itself is enhanceable in any way.

    If the object does not contain any substructure or component that is marked as enhanceable, you can select cannot be enhanced. If the structure has not yet been enhanced, you can choose the categorycannot be enhanced in any case.

    If you are creating new tables and structures in the ABAP Dictionary, the system proposes the category can be enhanced in any way as standard value for the classification of the enhancement options. If the developer chooses a more restrictive classification than can be enhanced in any way for a particular structure, then only the classification levels that adhere to the rules above are allowed. It is not possible to choose an enhancement option of a structure that is more restrictive than the classification resulting immplicitly from the structure setup and from the classification of the types used. Therefore, only the allowed categories are proposed for selection in the maintenance user interface.

    If a structure depends on one or several other structures, the smallest category is chosen as implicit classification (in the order cannot be enhanced < can be enhanced and character-type < can be enhanced and character-type or numeric < can be enhanced in any way). This classification is greater than or less than the category in the other structures and also greater than or the same as the category that results from the actual setup in the original structure itself.

    <b>

    Reward if usefull</b>

    Add comment
    10|10000 characters needed characters exceeded