Table TKZU3 Enhancement in SPRO

Hi,
I have a request for enhancement in SPRO:
Customizing: Controlling/Product cost controlling/Product cost planning/Basic settings for material costing/Overhead/Define costing sheets
I need to add a new column for Plant to table TKZU3. Can someone tell me how to do this?

Hi,
Yes, it is possible.  I've recently written a blog with details on how to do it;
/people/nick.young/blog/2010/01/12/getting-the-basics-right-150-creating-the-perfect-config-table-part-4-img-integration
Regards,
Nick

Similar Messages

  • Modify standard table in enhancement spot

    Hi Experts,
    I am using userexit_move_field_to_vbap enhancement spot.
    my piece of  code -
    XVBAP-ABGRU = 'ZP'.
    MODIFY XVBAP.
    I am getting dump. I want to know how to update a standard table in enhancent spots. Here i am tring to update XVBAP-ABGRU  with ZP for the corresponding sales order.
    Please help me <removed by moderator>.
    Thanks&Regards,
    sahil
    Edited by: Thomas Zloch on Jan 3, 2011 2:24 PM

    In this user exit you should change the field values of structure VBAP,not internal table XVBAP.
    VBAP-ABGRU = 'ZP'.
    See the Userexit comments
    This userexit can be used to move some fields into the sales  *
    *       dokument item workaerea VBAP

  • Planner table changes transport in SPRO

    Hi all,
    I have created a new planner in SPRO and using menu 'Table View'->Transport, I have saved the changes of the planner table under one request number, but I dont see any info under this in se10. Is this right approach or else I missed anything? Please guide.
    Thanks in advance.
    Regards,
    Guru.

    Hi Guru,
    I think you have followed the right steps...
    Please use TCode SE01 where you have options of search by User ID or TR no. etc... there you can input the transport request number (in Display Tab ) which you had created(under own requests) while saving the planner data in SPRO table-/SAPAPO/PLANNER.
    If that is not displayed under that view then please check if the entries/changes are correctly saved in table under that TR-Transport Rrequest ,if not save the changes again and create a new TR and follow the steps suggested above.
    hope this helps...
    Regards,
    Digambar

  • VA01 dump..because of include tables in enhancement in MM06E005

    Hi,
    In enhancement MM06E005, I have created a structure under 'Include tables'.
    I am facing serious consequences of this such..as not able to enter VA01 and not able to save Invoice.
    Can anyone tell me how to get rid of this problem?
    thanks,

    Hi,
    I have just  included a structure under this enhancement.
    no implementation after all.
    VA01,02,03 t-codes are getting dump.
    Thanks.

  • CRM - tables in enhancement

    Hello,
    How to see the tables and fields involved in a content extractor enhancement in CRM.
    Regards
    RT

    Hi ravi,
    one way to find the tables -->You can run the SQL trace (ST05).
    goto RSA3 -> enter data source
    activate the SQL trace
    Execute RSA3
    next deactivate the trace and click on Display trace
    from trace list ->menu --> trace list -->Combined table acesses --> it will display the list of tables used... export the tables to excell and remove the duplicate entries and check you can find the tables used in that extractor.
    Or
    you can get the tables n fields links using the help link.
    Regards
    KP

  • Deep Table - Application Enhancement Tool - SAP Library

    To add a comment, please log in or register on the top of this page and choose Reply. Please write your comment in English.
    You can also go back to the SAP help page.

    Hi Sasha,
           We have a very similar requirement to add custom fields in CRM and map it to existing fields in ECC. Can you please let me know the steps whcih you followed in ECC for this ? I have added the fields in CRM side using AET with r/3 adapter flag. But I am trying to figure out which structures need to be enhanced in ECC side.
    Any help on this is much appreciated.
    Regards,
    Manas,

  • How to Update EKPO table with enhancement at header level-customer data tab

    Experts,
    I have a requirement where I had to create a new button in the 'customer data' tab(header) in the ME21N/ME22N Transaction and once it gets clicked a table control will appear and in that all the line items with item no, material and plant and an additional check box will display, and once any one checks the check box against the item/material in the table control the item data with additional z fields (already created the zfields in EKPO Table) should get updated.
    Displaying Table control and item data on the click of button was successful, but once you check the check box against the item and save the PO it is not updating the z-fields in the EKPO table.
    I have implemented all the user exits , badis but no results. 
    Once you check the box in the table control against each item in the header part (Table control is in header part (customer tab)) the line item EKPO table with z fields should get updated.
    Any Clues/ideas will be appreciated.
    Thanks in advance,
    Kalikonda.

    Hi,
    Can you please share the remedy for above issue, recently we have same issue in our system.
    or please send me any supportive doc. for the below mail
    Looking forward for your positive response.
    Thanks
    Mohan
    ([email protected])

  • SRM 7.0 Add Fields in Account Assignment Table

    Hi SRM Gurus,
    I am working on SRM7.0.
    I want to add two fields in Account Assignment Table in Account assignment tab of Shopping cart Item.
    I can do it using WebDynpro Enhancement framework , i.e.
    1) Create an append structure for Structure INCL_EEW_PD_ACC_CSF
    2) Enhance WebDynpro Component : /SAPSRM/WDC_UI_DO_ACC - Component controller node
    3) Map this with View  V_DO_ACCOUNTING Node
    4) Create the necessary Table Columns and Column editors in Account Assignment Table
    However i think using SPRO configuration and enhancing few structures also this can be achieved.
    Can anyone guide me on how can i achieve it without creating WebDynpro ABAP Enhancement?
    Regards,
    Ashish Shah

    I've never done it with account data, but yes with header and item.
    I think in this case you need to add these fields in SPRO:
    SAP Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Extensions and Field Control (Personalization) --> Configure Field Control --> Configure Control for Fields of Substructures --> Metadata for Fields of Substructures and Table-Like Enhancements
    Adding the fields with "Set Type" = 31 Accounting...

  • Enhancement in BPSeach of winclient CIC

    hi,
    i want to add a new field(say mobile no)in BP search page of winclient CIC.now i have changed the sceen layout using smw0.But in backend in order to search based on mobile no, i have to assign some function module .But for that what i have to do exactly.
    can anybody  guide me??
    thanks in advance
    regards,
    anirban

    Hi Anirban,
    If you want to add a field which is a part of any of the table strutures  mentioned in
    spro ->icwinclient -> Customer Specific System Modifications for IC -> Define customer specific search control
    ,then all you have to do is to add an entry here
    eg. Z_ISM_BPSEARCH     CCMADDRESSFIELDS     STR_SUPPL2     X
    The corresponding entry on the html template for this would be
    eg. <TR>
              <TH align=left  width=28%>Apartment Name</TH>
              <TD width=72%><INPUT name=STR_SUPPL2 size=60 maxLength=60 type=TEXT/PLAIN>
              </TD>
            </TR>
    If you want a field which is not part of any of the structures mentioned above then you've got alot to do.
    1.Enhance one of the strutures mentioned above.
    2.Make a Z copy of CRM_CIC_BP_SUB function group and
      make few customization settings accordingly.
    3.Finally in the START_BUPA_SEARCH routine of 
      Z_CCMCS_BP_SEARCH2 function module you have to build
      in your own logic for search based on your newly added
      field.
    Regards
    Ranjit

  • VA01 - Enhancement - Taxware

    Hi Experts,
    I need to enhace order process(VA01,VA02) & Billing Process(VF01, Vf02).
    My aim is to assign the Taxcodes from custom tables before the TAXWARE System is called.
    I found FV64A500 & FV64A300 programs used in the process.
    Am I right?.
    Can someone Pls explain in detail how to go about this process step by step.
    I am working on ECC 6.0. I am not so very confortable in implicit  Enhancements.
    Expecting your answers.
    Regards,
    Kevin.

    check with following programs,
    MV45AFZ4
    MV45AFZA
    MV45AFZB
    MV45AFZB_USEREXIT_CHECK_VBAK
    MV45AFZB_USEREXIT_FILL_VBAP_FR
    MV45AFZC
    MV45AFZD
    MV45AFZF
    MV45AFZH
    MV45AFZU
    MV45AFZZ
    MV45AFZZ_FCODE_KKON_REDIRECT
    MV45AFZZ_FCODE_PKON_REDIRECT
    MV45AFZZ_USEREXIT_FIELD_MODIFI
    moreover you can find more enhancement in SPRO. Follow this path,
    SPRO --> Sales & Distribution --> System enhancements...
    here you will see user exit as well as BADI also.
    Regards,,,,
    Sunil

  • Brief about enhancements and user exits

    hai,
    can any  one tell me what are enhancements and user exits in sap sd,
    their  signifcance & configuration
    regards
    sriram

    hi,
    an example of user exit
    In case of Inbound DELINS IDOC (830 type) once there was a requirement of taking the “Target *** Qty required” and the “Target *** Date” for a specific customer who was not sending “*** Qty Received” by him.
    So for that specific customer we used the search term and added the same in the “Data 4” field of the IDOC under segment E1EDK09.
    There was one user exit available in IDOC_INPUT_DELINS_START Function module of SAP. We triggered this logic by the search term of customer and reached the user exit where we had made some code changes. (User Exits are used to make code changes when we are running standard programs or reports or function modules). With this we were able to reach the desired point of calculating “*** Issued” and then find out the difference from “Target *** Qty” and get “*** Qty Received” for the scheduling agreement. We did not copy the standard function module into Z . Instead the same was done using a user exit.
    <b>User exits in SD</b>
    Menu Path:
    SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
    • User exits for price determination
    • User exits for partner determination
    • User exits for credit check & risk management
    • User exits in sales:
    o User exits in sales doc processing
    o User exits for contract processing
    o User exits for product allocation processing
    o User exits for availability checking
    o User exits for component supply processing
    o User exits for product selection
    o User exits for billing plan
    • User exits for shipping
    • User exits for transportation
    • User exits for billing
    • User exits for general billing interface
    • User exits for sales support
    • User exits for lists.
    The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
    A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
    NEW FIELDS IN PRICING:
    To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
    The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOM”x” because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
    If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
    To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
    Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
    Write the code in the user exit to read the transaction data & transfer it to the KOM”x” structures.
    Menu Path:
    SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
    Adding the field to KOMK & KOMP:
    This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
    Let’s say you need to use the ‘base material’ to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
    • When you add a field to these tables, it must start with ‘ZZ’. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
    • After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
    Menu Path:
    SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
    • User exits for price determination
    • User exits for partner determination
    • User exits for credit check & risk management
    • User exits in sales:
    o User exits in sales doc processing
    o User exits for contract processing
    o User exits for product allocation processing
    o User exits for availability checking
    o User exits for component supply processing
    o User exits for product selection
    o User exits for billing plan
    • User exits for shipping
    • User exits for transportation
    • User exits for billing
    • User exits for general billing interface
    • User exits for sales support
    • User exits for lists.
    The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
    A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
    NEW FIELDS IN PRICING:
    To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
    The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOM”x” because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
    If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
    To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
    Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
    Write the code in the user exit to read the transaction data & transfer it to the KOM”x” structures.
    Menu Path:
    SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
    Adding the field to KOMK & KOMP:
    This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
    Let’s say you need to use the ‘base material’ to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
    • When you add a field to these tables, it must start with ‘ZZ’. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
    • After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
    Pl reward if helpful.
    Thanks
    Sadhu Kishore

  • Very urgent Enhancement category for include or subtype missing

    HI all;
    I am currently on BI 7.0 release
    I have a cube A that activated in Development. I transported cube A to Staging get the following error
    Enhancement category for include or subtype missing
    Enhancement category for include or subtype missing    
    No active nametab exists for /BIC/DZIP_INT9            
    Termination due to inconsistencies                     
    Table (Statements could not be generated)
    Flag: 'Incorrect enhancement category' could not be upda
    Enhancement category for table missing                 
    Enhancement category for include or subtype missing    
    No active nametab exists for /BIC/DZIP_INTP    
    and the cube couldn't activate in staging.
    I re-transport this cube A a few times with difference option of grouping and still no luck.
    in Development, i copied cube A to cube Aa, then transport new cube Aa to staging, then everything went ok. the new cube Aa is activated in staging area.
    I couldn't use the new name Aa since all the queries using the A name.
    Is there any possible solution that could help?
    Thanks.
    Rainnie

    jj

  • Table view in EHP1 CRM 7.0

    How to create a table view in ehp1 CRM.
    Is it the same way by creating a view and adding value node /model node then selecting view as table view with congigurable mode?

    Hi Anita,
    As per your requirement, AET table enhancement will be best suited to it.
    Use the help.sap.com link i gave in earlier reply to know more about  AET table enhancements.
    Now to get on to this task ,
    1) Use transaction AXTSYS and create an entry for Z component, give a name say ZAET_TBLEXT.
    and Save. The AET Table extension, then will use this component by default( if you select the radio button there) to create the views. Remember, just give any name you desire for the component. You dont need to create this componenet. AET extension wizard will create the component automatically.
    2) Open the overview page on which you would like to have the tableview as an assignment block. Since its a compititor info, i assume you want to place it on a BP/Account/Prospect. Competitor Overview Page or Opportunity Overview Page. Now chose the config button and once the Assignment blocks are highlighted, select the Header View( Compititor header or Opportunity header view depending on the overview page you are in) and config tool will open. Use the Display Enhancement button or create enhancement button and another popup will open which display the enhancements if any,
    3) On this Pop up you will see the AET table extensions assignment block. Use the Add table button. Follow the wizard and create the table, mention fields, translations etc. Also mention it as 1:n relation and so the table view. Chose the Standard buttons so you get all action buttons as well as inser, editlist, delete buttons etc.
    Once done, save and generate. This creates the view and also adds the component usage on overviewpage.
    Now all you need to do is just configure the overviewpag to pull the new tableview assignment block from Available to Displayed blocks.
    Note :
    1) this creates a Ztable , name same as mentioned/defaulted while AET table enahncement
    2) this create Z BOL entity with 1:n relation with Access Entity of OverviewPage , for example, BuilHeader if account overview page or BTAdminH if Opportunity overview page.
    3) creates BOL strucutre, handler class etc on its own.
    4) You do not need to do any coding,
    Thus in half an hour, you are done with Table view enhancement with Z table based entities.
    Before EhP1, we had to extend the BT/BP model with ZBOL and had to do a lot of thigs on our own. Almost 2 days job for an advance developer which is reduced to 15-20 minutes with zero coding required.
    If you have a sandbox or IDES system, i would recommand you to try it there frst, get confident and then do development on your development system.
    Remember ->
    1) AET Enhancement tool has to be started from WEB UI - which is generally runs on Customizing client, but creating AET table and enhancements is Workbench task. So if your customizing client is locked for workbench developments, then You must run the WEBUI on your workbench client ( use transaction wui ). It does not make any difference as far as development is concerned because your development its pure Workbench activity. later, you configure the Overview Page to pull the AET table view on your customizing client.
    2) Be confident and have well determined about the table design & about your table view design like the fields you need etc. because once you add the fields and mention the field type like Numeric, indicator,text etc, you can not change it later once the Tableview is generated. You can add more fields later and you can delete fields too but you can not change their type later.
    All the best.
    Thanks & Regards
    Suchiita
    Edited by: Suchita Phulkar on Jul 30, 2011 12:16 AM

  • Creation of table in ecc6

    i am creating a table in ecc 6 , while creating it is warning to create enhancement category. may i know why i need to choose enhancement category.
    Anybody let me know pls its urgent .
    rewards will be there..
    Regards,
    Madhavi

    Hi Madhavi,
    <i><b>Intro</b></i>
    Append structures permit you to append fields to a SAP standard table and structures without having to modify the table definition. An append structure is a structure which is assigned to exactly one table. There can be several append structures for a table. When a table is activated, all the active append structures for the table are found and their fields are appended to the table. If an append structure is created or changed, the table to which it is assigned is also activated and the changes also take effect there when it is activated. Like all structures, an append structure defines a type that can be used in ABAP programs.
    With Release 4.6C you can define foreign keys for fields that already exist in the table using an append structure. Search helps can also be attached to fields that already exist in the table.
    Customers create append structures in their namespace. The append structures are thus protected against overwriting during an upgrade. The new versions of the standard tables are imported during the upgrade. When the standard tables are activated, the fields contained in the active append structures are appended to the new standard tables. When append structures are added to a table, you do not have to manually adjust the customer modifications to the new SAP version of
    the table (Transaction SPDD) during the upgrade. Since the order of the fields in the ABAP Dictionary since Release 3.0 can differ from the order on the database, a conversion is not necessary when you add an append structure or insert fields in an existing append structure. The structure is adjusted when the database catalog is adjusted (ALTER TABLE). When activating in the ABAP Dictionary, the definition of the table is changed and the new field is appended to the database table.
    The new version of the SAP standard table is activated and the new field is appended to the database table.
    <i><b>Hint: Please note the following points about append structures:</b></i>
    No append structures may be created for pooled and cluster tables.
    If a long field (data type LCHR or LRAW) occurs in a table, it cannot
    be extended with appends structures. This is because such long fields
    must always be in the last position of the field list (e.g. they must be
    the last field of the table).
    *If you as a customer add an append structure to an SAP table, the fields
    in this append structure should be in the customer namespace for fields,
    that is they should begin with YY or ZZ. This prevents name collisions
    with new fields inserted in the standard table by SAP.
    *If you as a partner have your own reserved namespace for your
    developments, the fields you select in append structures should always
    lie in this namespace.
    Structures and tables that have been defined by SAP in the ABAP Dictionary can be subsequently enhanced by the customer in the following way:
    <b><i>Customizing Includes</i></b>
    With this variant, certain places within a structure or tables for enhancements
    are already reserved. However, the associated Includes are first of all created
    by the customer.
    <i><b>Appends</b></i>
    With this variant, any fields without previous reservation are appended to the
    end of structures or tables.
    <b>Caution: Problems due to structure enhancements</b>
    Not only the enhanced structures and tables are affectted by enhancements
    of this kind, but also all dependent structures that the enhancement takes
    on as Include or substructure. For example, enhancements using appends,
    which only have an effect at the end of the initial structure, can, for dependent
    structures, also lead to adjustments within these structures.
    In programs without active Unicode checking, structure enhancements
    can lead to syntax and runtime errors, especially in type checks and in
    connection with deep structures. In programs with active Unicode checking,
    assignments, operand checks and accesses with offset and length are also
    affected. Problematic here are changes if, for example, numerical or deep
    components are inserted into a purely character-like structure and this leads
    to the structure losing its character-like character. Enhancements are also
    therefore problematic, because the fragment view is changed and checks in
    assignments and comparisons which are based on this are influenced.
    So that the effects pf structure enhancements are recognizable at all, structures and tables in the ABAB dictionary are classified under Extras -> Enhancement category according to the following procedure:
    <b>Level </b>                     <b>  Category</b>                                   <b> Meaning</b>
    1                         Not classified                   The structure does not have an  
                                                                      enhancement category
    2                        Not enhanceable              The structure cannot be enhanced
    3                       Enhanceable and
                             character-like
                                                                All structure components and their
                                                                enhancements must be character-like
    4                        Enhanceable and
                            character-like or
                            numerical
                                                              The structure and its enhancement cannot
                                                              contain any deep data types
    5                     Freely enhanceable         The structure and its enhancements may
                                                                 contain components whose data type is
                                                                optional.
    Here, the elementary types C, D, N and T are describes as character-like, the
    elemenatry types F, I, P and X as numerical. The deep types STRING and XSTRING are not supported. With structures and tables with Includes or substructures, the enhancement categories of the Includes and substructures cannot be larger than those of the initial structure. For example, if the initial structure contains an Include of level 4, then levels 2 and 3 are not permitted for the initial structure. Structure enhancements in Dictionary can also have an effect on internal structures in ABAP programs if Dictionary structures in the source text are used as Include or substructure. These dependencies are considered implicitly in the ABAP program check. This does not include classified structures that contain enhanceable Includes or substructures.
    Regards,
    Balaji Reddy G
    ***Rewards if answers are useful

  • Warning messages recieved when activating z* tables after refresh.

    Hi all,
    We are having a problem in activating tables. After the system refresh, while activating z* tables warning messages are recieved. Some of the warnings recieved are as follows:
    Index LIKP-BGR is not in customer namespace.
    Enhancement category for table missing.
    Enhancement category for include or sub-type missing.
    It appears that the tables with "enhancement categories" set to "not classified" are the ones posing the problems.
    Earlier, this problem was not there. But after a technical weekend the issues are being faced.
    The details of the system are:
    Application Server beevssp1_RQ1_00
    SAP Kernel Information
    SAP Kernel :  700_REL
    Database Client Library : OCI_102 (10.2.0.2.0)
    created in  :  AIX 2 5 005DD9CD4C00
    created on  :  Oct 26 2008 20:51:39
    Support Level  :  0
    Kernel Patch number : 183
    Source ID  :  0.183
    DBSL Patch No. : 167
    ICU Version : 3.0 Unicode Version 4.0.1
    libsapu16 Version : 1.0025  Oct 24 2008 20:54:38
    Supported Environment
    SAP Database Version
    700
    Database
    ORACLE 9.2.0..
    ORACLE 10.1.0..
    ORACLE 10.2.0..
    Operating System
    aix 1 5
    aix 2 5
    aix 3 5
    aix 1 6
    Please suggest.

    Hi varsha,
    Index LIKP-BGR is not in customer namespace.
    Enhancement category for table missing.
    Enhancement category for include or sub-type missing.
    For this goto SE11
    Enter the table name .
    Click on Display               .
    Go to Extras-->Enhancement Category.
    select radio button for Can be enhanced Deep.
    Click on continue.
    This will resolve your issue.
    Let me know if you have any problem....
    Thanks & Regards,
    Sudheer.
    Edited by: sudheer chowdhary on Dec 22, 2008 8:02 PM

Maybe you are looking for

  • Regarding non-unicode to unicode conversion in mapping

    In our project we have Pi system which is installed as unicode system. But the SAP systems at the sender side is unicode and most of them are non-unicode systems. We have a doubt regarding the challenges that we need to face in PI mapping with refere

  • Hash mismatching error while downloading mountain lion

    i got a has mismatching error when downloading mountain lion in app store, any way to fix it?

  • FDQM Target Dimension - connection failed

    Hi, I am getting started to FDQM and I am trying to prepare the new environment so I started with the workbench and finished these steps:- 1) Imported the Essbase adapter (ES11XG4-J) to the application then registered it successfully. 2) Edited the t

  • Actions profile for Transaction.

    Hi Experts, Please share the best practice doc for actions determination for transaction (lead). how to create the action profle Thanks in advance Prajith P

  • C855-S5308 - SDCARD reader really slow?

    Hi, I have a C855-S5308, and I've installed Windows 7 Ultimate 64 bit on it.  I downloaded all the various drivers for this from Toshiba's website, including the one for the SDCARD reader, and everything shows up ok in Device manager. However, I've n