Maintaince view creation for a cluster table

Hi friends,
I have created a maintaince view for a cluster table bseg and i have activated it its working fine..
now my problem is i can create maintaince view for mutiple tables if other tables are linked with primary table using foriegn key relationship..
Now can any one tell me is it possible to create maintance view for cluster table with multiple tables as i need a linked table with bseg which iam not able to get... ie : when i click on the relationship tab iam not getting the linked tables for bseg...
now can i create a maintaince view with 2 linked cluster tables..
if so can any one tell me how to create it.
As sap says we can create projection view for cluster and pooled table and we cannot create database view for cluster and pooled tables , but it does not mentioned like that for maintaince view....
I assume we can do it.... as iam trying to create a maintaince view with single cluster table then it shoudl allow me to create for multiple linked cluster tables.... and is it mandatory to maintain TMG for this maintaince view....?
Regards
KUMAR

yes.. ur right inserting values into a cluster table other than standard sap tarnactions is dangerious....
But sap didnot mentioned any where that we cannot maintain data for cluster tables using maintaince view... which it said for database view..that pooled and cluster table cannot be used for database view..
Regards
Kumar

Similar Messages

  • Can we create secondary index for a cluster table

    hi
    can we create secondary index for a cluster table

    Jyothsna,
    There seems to be some kind of misunderstanding here. You <i>cannot</i> create a secondary index on a cluster table. A cluster table does not exist as a separate physical table in the database; it is part of a "physical cluster". In the case of BSEG for instance, the physical cluster is RFBLG. The only fields of the cluster table that also exist as fields of the physical cluster are the leading fields of the primary key. Taking again BSEG as the example, the primary key includes the fields MANDT, BUKRS, BELNR, GJAHR, BUZEI. If you look at the structure of the RFBLG table, you will see that it has primary key fields MANDT, BUKRS, BELNR, GJAHR, PAGENO. The first four fields are those that all cluster tables inside BSEG have in common. The fifth field, PAGENO, is a "technical" field giving the sequence number of the current record in the series of cluster records sharing the same primary key.
    All the "functional" fields of the cluster table (for BSEG this is field BUZEI and everything beyond that) exist only inside a raw binary object. The database does not know about these fields, it only sees the raw object (the field VARDATA of the physical cluster). Since the field does not exist in the database, it is impossible to create a secondary index on it. If you try to create a secondary index on a cluster table in transaction SE11, you will therefore rightly get the error "Index maintenance only possible for transparent tables".
    Theoretically you could get around this by converting the cluster table to a transparent table. You can do this in the SAP dictionary. However, in practice this is almost never a good solution. The table becomes much larger (clusters are compressed) and you lose the advantage that related records are stored close to each other (the main reason for having cluster tables in the first place). Apart from the performance and disk space hit, converting a big cluster table like BSEG to transparent would take extremely long.
    In cases where "indexing" of fields of a cluster table is worthwhile, SAP has constructed "indexing tables" around the cluster. For example, around BSEG there are transparent tables like BSIS, BSAS, etc. Other clusters normally do not have this, but that simply means there is no reason for having it. I have worked with the SAP dictionary for over 12 years and I have never met a single case where it was necessary to convert a cluster to transparent.
    If you try to select on specific values of a non-transparent field in a cluster without also specifying selections for the primary key, then the database will have to do a serial read of the whole physical cluster (and the ABAP DB interface will have to decompress every single record to extract the fields). The performance of that is monstrous -- maybe that was the reason of your question. However, the solution then is (in the case of BSEG) to query via one of the index tables (where you are free to create secondary indexes since those tables are transparent).
    Hope this clarifies things,
    Mark

  • ITAB_NON_NUMERIC_COMPONENT" in the "generation of scrambling programs for non-cluster tables

    Dear Experts,
    We have are experiencing issues in standalone scrambling,
    we are getting error" ITAB_NON_NUMERIC_COMPONENT" in the "generation of
    scrambling programs for non-cluster tables"
    Please help with the needful
    urgently.
    Thanks

    Hello,
    Implement the following SAP note in the execution system and re-execute the     
    activity 'Generation of scrambling programs for non-cluster tables' to solve this issue.
    SAP NOTE : '1915906 - SAP LT V2 SP06: Dump during program generation'
    Regards,
    Jerrin Francis

  • Special authorization need for read cluster table??

    In one report, I use following coding to read information from RFDT table:
    form get_f110_parm .
      f110id-laufd   = p_laufd.
      f110id-laufi   = p_laufi.
      f110versionpar = space.
      clear:   buktab, fkttab, slktab, sldtab, trctab, usrtab,
               faetab, jobtab, f110v, f110c,  trcopt, f110versionpar.
      import buktab fkttab slktab sldtab trctab usrtab
             faetab jobtab f110c trcopt f110versionpar
             from database rfdt(fb) id f110id
             accepting padding.
    endform.                    " GET_F110_PARM
    I can fill F110c, trcopt and f110versionpar by this program. But there is no entry in table like fkttab, usrtab.
    Is there any authorization need for read cluster table??
    Thanks in advance.
    Edited by: Amy Xie on Dec 21, 2010 10:41 AM

    Hello,
    After you run your code, check transaction SU53 to see if any authorization check failed.

  • Performance Tuning for A016 (cluster table) Query

    Dear SDNers,
    Issue:
    The report runs  successfully sometimes and sometimes the report gets timed out.
    My findings
    Query which is taking a  long time to execute is the query on A016(cluster Table) to fetch the condition details
    SELECT kschl
             evrtn
             evrtp
             knumh
             FROM a016 INTO TABLE t_a016
             FOR ALL ENTRIES IN t_ekpo
             WHERE
             kappl EQ c_m (Application)
             AND kschl IN s_kschl
             AND evrtn = t_ekpo-ebeln
             AND evrtp = t_ekpo-ebelp.
    where t_ekpo contains entries (4354)from ekko and ekpo based on the selection screen entries.
    I see that a016 is a cluster table that is being used here and t_a016 contains (390*) records after the above fetch.
    Dear readers,Please help me as to what has to be taken care of inorder to fine tune this select query?
    what are the things that i need to make corrections in.
    How can i make this fetch effective and faster?
    Please help me with your inputs.
    Regards,
    SuryaD.
    Edited by: SuryaD on Oct 26, 2009 6:29 PM

    Hi,
    1) Try to hit the table A016 with only unique entries of t_ekpo for EBELN and EBELP...
    Use some temp table lt_ekpo = t_ekpo
    i.e. sort lt_ekpo by ebeln ebelp
    delete adjacent duplicates from lt_ekpo comparing ebeln ebelp.
    Now write you select query as below...So that the table might be hit with less number of entries...
    SELECT kschl
    evrtn
    evrtp
    knumh
    FROM a016 INTO TABLE t_a016
    FOR ALL ENTRIES IN lt_ekpo
    WHERE
    kappl EQ c_m (Application)
    AND kschl IN s_kschl
    AND evrtn = lt_ekpo-ebeln
    AND evrtp = lt_ekpo-ebelp.
    Please note that there will be no change in the output data if you hit with duplicate entries/unique as FOR ALL ENTRIES will fetch only unique entries matching the where condition.
    2) Order of where conditon fields should be same as the order in table for better performance...
    3) If you find any index on the table, try to include the fields in where condition(if possible) for better performance
    Hope this helps
    Regards
    Shiva

  • Techniques for accessing CLUSTER tables

    Can some 1 plz tell me , How many standard methods are there to access a cluster table. I want to know each and every method with example.1 method is Logical databases , 2nd is thrugh se16. But I want to know each and every.
    My cluster tables are
    1) ZNO_CT1 having fields (mandt , roll_no , Name)
    2) ZNO_CT2 having fields (mandt , roll_no , Age)
    AND these are  assigned to the table cluster  'ZNO_CLUST'.
    ZNO_CLUST has (mandt , roll_no , pageno , timestamp , VARDATA)

    Hi,
    You can find the methods below.
    Just go thru this link-
    http://dev.mysql.com/doc/ndbapi/en/class-table.html
    Thanks
    Do reward points if useful

  • JMS filestores creation for multi cluster through config wizard

    Hi,
    We are using multiple clusters in a domain through the config wizard. It looks like the config wizard as an limitation - It creates only jms stores for the managed servers in the first cluster but I dont see it. Is any other way to do this? I dont see any other information about this
    Please help!
    Thanks,

    Matt,
    I'd say your suggestion to use the 1GB team as another cluster network is a good idea. No harm in adding additional communication paths to your cluster.
    David A. Bermingham, MVP, Senior Technical Evangelist, SIOS Technology Corp

  • How many SECONDARY INDEXES are created for CLUSTER TABLES?

    how many SECONDARY INDEXES are created for CLUSTER TABLES?
    please explain.

    There seems to be some kind of misunderstanding here. You cannot create a secondary index on a cluster table. A cluster table does not exist as a separate physical table in the database; it is part of a "physical cluster". In the case of BSEG for instance, the physical cluster is RFBLG. The only fields of the cluster table that also exist as fields of the physical cluster are the leading fields of the primary key. Taking again BSEG as the example, the primary key includes the fields MANDT, BUKRS, BELNR, GJAHR, BUZEI. If you look at the structure of the RFBLG table, you will see that it has primary key fields MANDT, BUKRS, BELNR, GJAHR, PAGENO. The first four fields are those that all cluster tables inside BSEG have in common. The fifth field, PAGENO, is a "technical" field giving the sequence number of the current record in the series of cluster records sharing the same primary key.
    All the "functional" fields of the cluster table (for BSEG this is field BUZEI and everything beyond that) exist only inside a raw binary object. The database does not know about these fields, it only sees the raw object (the field VARDATA of the physical cluster). Since the field does not exist in the database, it is impossible to create a secondary index on it. If you try to create a secondary index on a cluster table in transaction SE11, you will therefore rightly get the error "Index maintenance only possible for transparent tables".
    Theoretically you could get around this by converting the cluster table to a transparent table. You can do this in the SAP dictionary. However, in practice this is almost never a good solution. The table becomes much larger (clusters are compressed) and you lose the advantage that related records are stored close to each other (the main reason for having cluster tables in the first place). Apart from the performance and disk space hit, converting a big cluster table like BSEG to transparent would take extremely long.
    In cases where "indexing" of fields of a cluster table is worthwhile, SAP has constructed "indexing tables" around the cluster. For example, around BSEG there are transparent tables like BSIS, BSAS, etc. Other clusters normally do not have this, but that simply means there is no reason for having it. I have worked with the SAP dictionary for over 12 years and I have never met a single case where it was necessary to convert a cluster to transparent.
    If you try to select on specific values of a non-transparent field in a cluster without also specifying selections for the primary key, then the database will have to do a serial read of the whole physical cluster (and the ABAP DB interface will have to decompress every single record to extract the fields). The performance of that is monstrous -- maybe that was the reason of your question. However, the solution then is (in the case of BSEG) to query via one of the index tables (where you are free to create secondary indexes since those tables are transparent).

  • View creation authority for a user

    How can I assign MIP views or another view creation for a user ?

    Hi
    Yes you are right you can control the status based on the authorisation Object
    M_MATE_STA.
    Award points if useful
    Thanks & Regards
    Kishore

  • Inforation on Pool tables and cluster tables required.

    I want to know about the pool tables and cluster tables like how to create them and how to look the tables associated with the given tables. Like for the table BSEG we have other tables linked BSID etc. I'm new to this concept please guide me.

    <b>Pooled Table:</b>
    A pooled table in R/3 has a many-to-one relationship with a table in the database (see Figures 3.1 and 3.2). For one table in the database, there are many tables in the R/3 Data Dictionary. The table in the database has a different name than the tables in the DDIC, it has a different number of fields, and the fields have different names as well. Pooled tables are an SAP proprietary construct.
    When you look at a pooled table in R/3, you see a description of a table. However, in the database, it is stored along with other pooled tables in a single table called a table pool. A table pool is a database table with a special structure that enables the data of many R/3 tables to be stored within it. It can only hold pooled tables.
    R/3 uses table pools to hold a large number (tens to thousands) of very small tables (about 10 to 100 rows each). Table pools reduce the amount of database resources needed when many small tables have to be open at the same time. SAP uses them for system data. You might create a table pool if you need to create hundreds of small tables that each hold only a few rows of data. To implement these small tables as pooled tables, you first create the definition of a table pool in R/3 to hold them all. When activated, an associated single table (the table pool) will be created in the database. You can then define pooled tables within R/3 and assign them all to your table pool.
    Pooled tables are primarily used by SAP to hold customizing data.
    <b>Cluster Table:</b>
    A cluster table is similar to a pooled table. It has a many-to-one relationship with a table in the database. Many cluster tables are stored in a single table in the database called a table cluster.
    A table cluster is similar to a table pool. It holds many tables within it. The tables it holds are all cluster tables.
    Like pooled tables, cluster tables are another proprietary SAP construct. They are used to hold data from a few (approximately 2 to 10) very large tables. They would be used when these tables have a part of their primary keys in common, and if the data in these tables are all accessed simultaneously.
    Table clusters contain fewer tables than table pools and, unlike table pools, the primary key of each table within the table cluster begins with the same field or fields. Rows from the cluster tables are combined into a single row in the table cluster. The rows are combined based on the part of the primary key they have in common. Thus, when a row is read from any one of the tables in the cluster, all related rows in all cluster tables are also retrieved, but only a single I/O is needed.
    A cluster is advantageous in the case where data is accessed from multiple tables simultaneously and those tables have at least one of their primary key fields in common. Cluster tables reduce the number of database reads and thereby improve performance.
    Restrictions on Pooled and Cluster Tables
    1. Pooled and cluster tables are usually used only by SAP and not used by customers, probably because of the proprietary format of these tables within the database and because of technical restrictions placed upon their use within ABAP/4 programs. On a pooled or cluster table:
    2. Secondary indexes cannot be created.
    3. You cannot use the ABAP/4 constructs select distinct or group by.
    4.You cannot use native SQL.
    5.You cannot specify field names after the order by clause. order by primary key is the only permitted variation.
    For creation of pooled /cluster table, have  a look at below link.
    http://help.sap.com/saphelp_erp2004/helpdata/en/81/415d363640933fe10000009b38f839/frameset.htm
    For creation of table pool /cluster, have  a look at below link.
    http://help.sap.com/saphelp_erp2004/helpdata/en/81/415d363640933fe10000009b38f839/frameset.htm
    Have a look at below link.
    http://www.sap-img.com/abap/the-different-types-of-sap-tables.htm
    Best Regards,
    Vibha
    *Please mark all the helpful answers

  • Why do I get a "ORA-01031: insufficient privileges" in my view creation?

    Why do I get a "ORA-01031: insufficient privileges" in my view creation for the table which exists in the same schema?
    Oracle version is 10g R2.
    connect cim/lion;
    create table cim.table1 (a number, b varchar2(10));
    create view cim.view1 as select * from cim.table1;
    create view cim.view1 as select * from cim.table1
    ERROR at line 1:
    ORA-01031: insufficient privileges

    Thanks it works now after giving CREATE VIEW permission to user CIM.
    This script was working fine in Oracle 10g R1.
    Looks like i need to execute the following GRANT permission explicitly
    grant create view to cim;

  • Edit next extent size of the Cluster table

    Hi Guys
    I need to change the next extent size of the a table.
    I ran se14 but i am not able to get into edit mode, because there is no button for edit mode.
    Reason: Cluster table
    Two questions:
    1. Why there is no Edit button? Is it because this table doesnot exixt at DB level.
    2. How can i change the next extent size for a Cluster table from sql prompt or from brtools if possible.
    Information:
    I am facing this issue only in DEV, QAS boxes, where as in Production its fine.
    Regards
    Ricky
    Edited by: Ricky kayshap on Dec 9, 2008 3:52 PM

    Hi,
    Cluster Tables doesn't exist in DB, Because of that you can't make changes to extents at DB level.
    if you experiencing some space issue. I woud suggest to check the underline Transparent tables and make changes to those.
    hope this helps.
    Kalyan.

  • Automatic storage location view creation in maintenace order (IW31)

    Hello,
    Seems like I need some help.
    Have configured automatic storage location view creation for GR and reservation. Configured movement types are 101, 201, 261. While creating reservations (201, 261 mvmnt. types) with mb21 the sloc view is automatically created in material master, and everything seems fine.
    But in iw31 when I specify material number and sloc in a Components tab, I get an error message CO312: "The storage location data is not created". Automatic reservation is not created, and maintenance order can not be saved. Movement type 261 is used for automatic reservations for the maintenance order.
    If I configure message CO312 as a (W)arning  message, then it allows me to save the order and reservation, but sloc view in material master still is not created. Think that's not good and may lead to MRP issues.
    How can I configure automatic sloc view creation in iw31? Is that possible?
    Edited by: Konstantin Dudura on Nov 17, 2009 8:11 PM

    Hi,
    The customization required for Automatic Storage location creation at reservation are:
    Goto : SPRO -> MM -> inventory Management and physical inventory -> Goods issue/ Transfer posting -> Create storage location automatically
    first of all go to Plant and tick the automatic Storage location creation for the Plant. After that goto Movement type and tick the automatic Storage location for movement type 261.
    Regards

  • How to read cluster tables

    Hi ,
    I have a requirement  to read cluster tables data using import statement . I have to access cluster tables data based on selection criteria . Any body help me regarding this isuue .
    Regards
    Uday

    Hi Uday,
    Check this one:
    [Extraction from cluster tables through function module|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33]
    Re: BW extractor for ERP cluster tables
    Regards,
    Chandra Sekhar

  • How to select data from cluster table

    hi experts,
                   I have a report which picks data from bseg (cluster table ) for a month report it is taking around 4 minutes to process.I feel it is not good when take the report after some months.
    how to select data from these table???how to declare itab for these cluster tables????can we include any search condition or any other kind of internal table???
    please advice.
    mani

    Hi Manikandan,
    The following code may be helpful to understand how to select the data from cluster table.
    Types: Begin of ty_kna1,
    Kunnr type kna1-kunnr,
    adrnr type kna1-adrnr,
    end of ty_kna1,
    begin of ty_bseg,
    belnr type bseg-belnr,
    kunnr type bseg-kunnr,
    end of ty_bseg,
    begin of ty_final,
    belnr type bseg-belnr,
    kunnr type kna1-kunnr,
    adrnr type kna1-adrnr,
    end of ty_final.
    Data: it_kna1 type table of ty_kna1,
    wa_kna1 type ty_kna1,
    it_bseg type table of ty_bseg,
    wa_bseg type ty_bseg,
    it_final type table of ty_final,
    wa_final type ty_final.
    Select kunnr adrnr from kna1 into table it_kna1 where....
    if sy-subrc = 0.
    select belnr kunnr into table it_bseg for all entries in it_kna1 where kunnr = it_kna1-kunnr.
    endif.
    sort it_kna1 by kunnr.
    Loop at it_bseg into wa_bseg.
    move wa_bseg-belnr to wa_final-belnr.
    read table it_kna1 into wa_kna1 with kunnr = wa_bseg-kunnr binary search.
    if sy-subrc = 0.
    move: wa_kna1-kunnr to wa_final-kunnr,
    wa_kna1-belnr to wa_final-belnr.
    endif.
    append wa_final to it_final.
    clear wa_final.
    endloop.
    Loop at it_final into wa_final.
    write: / wa_final-belnr, wa_final-kunnr, wa_final-adrnr.
    endloop.
    Reward if useful.
    Thankyou,
    Regards.

Maybe you are looking for