Pool Table Creation in ABAP Dictionary

Please Help
How to create Pool table in ABAP DDIC ? I Tried with the Existing Transparent Table
Changing Its Category to Pool Table by going through EXTRA menu and then Change Table Category Option but After this
it is asking for Table Pool name in Delivery and Maintaince Tab what should be the name of table pool ?
How to assign pool table in Table Pool?

hi,
u will have to create your own ztable pool/cluster anad assign your table to that .
eg.
refer to table A005 its a pool table ...

Similar Messages

  • Customise table inconsistency between ABAP Dictionary and the databas

    Hi all,
    I have encountered a problem where by, I was not able to activate a table due to inconsistency between ABAP Dictionary and the database.
    After I run the SE14--> Check Database object. It has show that there is a missing Unique Index(Primary Index) at the Database Level, but at ABAP Dictionary it is there.
    I have try to recreate the primary index at the Database level, but failed. Because one of the primary key field is been dropped from this table.
    So now, may I know how can I still make this table Active again?
    Is it save to folllow the following solution that I found on internet?
    Syntax error in SDCC, table inconsistency between ABAP Dictionary and the database, transport error 8 during the generation of ABAP Dictionary. When you call Transaction SDCC, a termination occurs due to a putative syntax error because a table is not known or active. When you check this with the ABAP dictionary (SE11), you notice, that the table is active or inactive, however it is not possible to activate it. The activation might terminate with the error message 'Inconsistency between ABAP Dictionary and database'. A check of the affected object also delivers this error.
    Solution
    Proceed as follows:
    Log on as user DDIC
    Call Transaction SE14
    Enter the affected table name and
    select EDIT
    In the following screen, choose Table -> Reconstruct
    Confirm the execution
    Call Transaction SE11
    Enter the affected table name
    Display
    Activate
    Thanks.
    CK

    I managed to solved this by
    Solution
    Proceed as follows:
    Log on as user DDIC
    Call Transaction SE14
    Enter the affected table name and
    select EDIT
    In the following screen, choose Table -> Reconstruct
    Confirm the execution
    Call Transaction SE11
    Enter the affected table name
    Display
    Activate
    Thanks.
    CK

  • Pooled table supported by ABAP Query .................

    Hi,
    I have an requirment to create a abap query report .For that one i have to use a pooled table as join with another table?
    Is that possible or not?
    Reagrd
    Ricky

    Hi,
    You can use the tables in ABAP query but not in the direct join format.
    For e.g.
    Select "data" from BSEG into correspoding fields of table itab.
    select "data" from <tablename>
    into correspoding fields of table itab1
    for all entries of itab
    where <conditions>.
    Thanks & Regards

  • Number of lines in ABAP Dictionary table

    Hi to all!
    I've got a table in the ABAP Dictionary. Is there any function in any function module that lets know how many lines this table contains?
    I don't wanna use the way to read data to the internal table and describe it using
    DESCRIBE TABLE <itab> LINES <num_of_lines>.
    Thanks!!!

    REPORT ychatest.
    TABLES mara.
    SELECT COUNT(*) FROM mara.
    WRITE : sy-dbcnt.

  • ZSD_TABLE is not defined in the ABAP dictionary as a table"

    Hello,
    I created zsd_table and inserted few records
    When i use this table in program system is giving error message "ZSD_TABLE is not defined in the ABAP dictionary as a table"
    How can we define this table in ABAP dictionary?
    Thanks

    Hi,
    Go to Transaction SE11
    Give the table name 'ZSD_TABLE'
    and click on create and enter the fileds
    after entering fields give 'techinical setting' for a table by clicking on technical setting button on tool bar
    save check and activate
    Regards
    Krishna

  • DB02 = Missing Tables and Indexes = Unknown objects in ABAP Dictionary = DB views

    Hi SAP Gurus,
    on our SAP NetWeaver 7.x BW (based on AIX/Oracle) I find via transaction DB02 (path = Diagnostics => Missing Tables and Indexes) under "Unknown objects in ABAP Dictionary" under DB views a BW object /BI0/.....
    When I make a double click on the object, I am getting the popup window "Display not possible for this object":
    How can I identify the object and clarify with the BW application expert, if needed, how to resolve this object?
    I searched already via RSA1 for the object, but I wasn't able to find anything so far ...
    Thanks for your help and ideas.
    Best regards
    Carlos

    Hello Carlos
    The database view in question is a temporary database object created during a query execution.
    Please read this SAP note 449891 - Temporary database objects in BW 3.x to understand what that view is all about and impact if those views are removed.
    The SAP notes 449891 and 1139396 suggests to run the report SAP_DROP_TMPTABLES to drop these temporary objects. Whether the objects are still required or not is a question to be put across to the BW team. If the temporary objects are removed when they are used by a query, then the query will fail.
    Have a nice day
    RB

  • BW - Unknown objects in ABAP Dictionary - DB Tables

    Hello gurus,
    As a result of the consistency check in DB02 transaction, our BW System is showing a high number of "DB Tables" and "DB Tables withouth unique index" as unknown objects in the ABAP dictionary.
    Is there any way to solve these consistency issues detected in DB02?
    Thanks
    Regards

    Hi Dibya,
    I checked the SAP note 33814 and it tooke me to the SAP note 449891 - Temporary database objects in BW 3.X
    According to the recommendations, I executed the report SAP_UPDATE_DBDIFF, and I got as result 579 secondary indexes missing in the DB from the and still the 5 DB Tables unknown in the ABAP dictionary and 2 DB Tables withouth unique index,
    I executed the report SAP_INFOCUBE_INDEXES_REPAIR in order to try to repair the secondary missing indexes that were shwon but withouth getting any results.
    Do you have any recommendation to solve this situation?  In the original scenario the DB02 transaction wasn't reporting any missing index.
    Thanks and regards,

  • Delete restrict for ABAP Dictionary database table

    Hi,
    I defined two database tables in ABAP dictionary, one with master data, and one with records referencing the master data.
    I also defined a foreign key relationship in the second table, so that new entries in the second table are checked against the master data table.
    In addition to this behaviour, I also want the Dicitionary to perform a check the other way round. In other words, if I try to delete a record in the master data table, this should not be possible if there are records in the second table referencing this record. Thats how foreign key relationships work in Oracle databases.
    Is there a way to force this behaviour for ABAP Dictionary tables, too? Or is it possible to make the table maintenance view perform this check?
    Thanks for your help!
    Kind regards,
    Tobias

    Hello Tobias,
    I can delete records in the master table which have dependent entries in the second table without an error or a warning.
    How are you deleting the entries, via SM30?
    If yes, you can use the [Event 03: Before Deleting the Display Data|http://help.sap.com/saphelp_nw04s/helpdata/en/91/ca9f14a9d111d1a5690000e82deaaa/content.htm]. In this TMG event you can check if the entry can be deleted at all!
    If you're using Open SQL statements to delete the records, i don't think DB layer implicitly checks the dependency. You can always put an explicit check though
    Btw, out-of-curiosity, is this a custom or standard table?
    BR,
    Suhas

  • Register Table in ABAP Dictionary

    One of our SAP RWD standard table got deleted during the upgrade. I have a backup of that table & created it using Create Table SQL commands directly at the database level.
    I did exp & imp of various tables too however in SE11 the tables created directly in database no matter Z tables or SAP Standard tables does not show up.
    My question is that how to register that table in ABAP dictionary?

    Table is a part of PSAPCRMUSR & does exists in schema SAPCRM.
    Let me give another example:
    One of SAP Table STERM_LINK got corrrupted and we did'nt knew about it for almost a month. OSS replied back saying that its a 3rd party table and we are not using any modules that would have updated/read that table. Also that table did'nt had any data.
    OSS suggested that either we exp/imp that table from QA to PRD or they can send us a script which is a normal create table....... script and we can drop can corrupted table.
    Now in this example if we drop that table and recreate it using script at database level, it will be unknown in dictionary.
    How to solve this kind of issue?

  • How to update whole external table(in ABAP dictionary) from internal table at once

    Hi,
    How can I update the content of the external table (in ABAP dictionary) from the content of internal table data at once. I created the internal tables with out the header line, with the work area. I tried UPDATE TARGET_EXTERNAL_TABLE FROM TABLE INTERNAL_TABLE. But it returns 4 for sy-subrc and did not work.
    Thank you
    Regards.
    CHINTHAKA

    Hi Feiyun Wu,
    Thank you very much. Your code worked. Is there any way to replace the whole content of the external table from internal table data ?
    Regards,
    Chinthaka

  • A standard table is missing in ABAP dictionary

    We wane to use a standard program which uses a standard table(CCEE/FISISTGRD) .
    but when trying to execute this pgm , itrs going into dump..
    The error is CCEE/FISISTGRD doesnot exist in ABAP dictionary
    Edited by: deepti Gandham on Apr 24, 2009 9:58 AM

    Hi,
    deepti Gandham,
    I check with ECC 6.0  ,but your standard Table not there
    List of the table,
    /CCEE/FISI_DDVN    Slovenia VAT open period
    /CCEE/FISI_SET       Seting for print programs
    /CCEE/FISIFP_A       Forign Payments - account connection
    /CCEE/FISIFP_B       Forign Payments in/out
    /CCEE/FISIFP_C       Bank list
    /CCEE/FISIFP_HAL   Podatki za HALCOM
    /CCEE/FISIKOEF1    Coefficients for revaluation
    /CCEE/FISIMT940     Bank statement - MT 940 - convert referenc
    /CCEE/FISIOBR1      Povezava kupca z letno obr. mero za izraèu
    /CCEE/FISISTGRD   Reasons for Reversal enabling to change ta
    /CCEE/FISITAX        Convert Tax on sales
    /CCEE/FISIZDV       
    Regards,
    Ansari.

  • 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

  • Dynamic Internal Table creation and population

    Hi gurus !
    my issue refers to the slide 10 provided in this slideshow : https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b332e090-0201-0010-bdbd-b735e96fe0ae
    My example is gonna sound dumb, but anyway: I want to dynamically select from a table into a dynamically created itab.
    Letu2019s use only EKPO, and only field MENGE.
    For this, I use Classes cl_abap_elemdescr, cl_sql_result_set and the Data Ref for table creation. But while fetching the resultset, program dumps when fields like MENGE, WRBTR are accessed. Obviously their type are not correctly taken into account by my program.
    Here it comes:
    DATA: element_ref             TYPE REF TO cl_abap_elemdescr,
          vl_fieldname               TYPE string,
                 tl_components         TYPE abap_component_tab,
                 sl_components         LIKE LINE OF tl_components_alv,
    linetype_lcl               TYPE REF TO cl_abap_structdescr,
    ty_table_type            TYPE REF TO cl_abap_tabledescr,
    g_resultset             TYPE REF TO cl_sql_result_set
    u2026
    CONCATENATE sg_columns-table_name '-' sg_columns-column_name INTO vl_fieldname.
    * sg_columns-table_name contains 'EKPO'
    * sg_columns-column_name contains 'MENGE'
    * getting the element as a component
    element_ref ?= cl_abap_elemdescr=>describe_by_name( vl_fieldname ).
    sl_components-name  = sg_columns-column_name.
    sl_components-type ?= element_ref.
    APPEND sl_components TO tl_components.
    * dynamic creation of internal table
    linetype_lcl = cl_abap_structdescr=>create( tl_components ).
    ty_table_type = cl_abap_tabledescr=>create(
                      p_line_type = linetype_lcl ).
    u2026
    * Then I will create my field symbol table and line. Code has been cut here.
    CREATE DATA dy_line LIKE LINE OF <dyn_table>.
    u2026
    * Then I will execute my query. Here itu2019s: Select MENGE From EKPO Where Rownum = 1.
      g_resultset = g_stmt_ref->execute_query( stmt_str ).
    * Then structure for the Resultset is set
      CALL METHOD g_resultset->set_param_struct
        EXPORTING
          struct_ref = dy_line.
    * Fetching the lines of the resultset  => Dumpu2026
      WHILE g_resultset->next( ) > 0.
        ASSIGN dy_line->* TO <dyn_wa>.
        APPEND <dyn_wa> TO <dyn_table>.
      ENDWHILE.
    Anyone has any clue to how prevent my Dump ??
    The component for MENGE seems to be described as a P7 with 2 decimals. And the resultset wanna use a QUAN type... or something like that !

    Hello
    I have expanded your sample coding for selecting three fields out of EKPO:
    *& Report  ZUS_SDN_SQL_RESULT_SET
    *& Thread: Dynamic Internal Table creation and population
    *& <a class="jive_macro jive_macro_thread" href="" __jive_macro_name="thread" modifiedtitle="true" __default_attr="1375510"></a>
    *& NOTE: Coding for dynamic structure / itab creation taken from:
    *& Creating Flat and Complex Internal Tables Dynamically using RTTI
    *& https://wiki.sdn.sap.com/wiki/display/Snippets/Creating+Flat+and+
    *& Complex+Internal+Tables+Dynamically+using+RTTI
    REPORT  zus_sdn_sql_result_set.
    TYPE-POOLS: abap.
    DATA:
    go_sql_stmt       TYPE REF TO cl_sql_statement,
    go_resultset      TYPE REF TO cl_sql_result_set,
    gd_sql_clause     TYPE string.
    DATA:
      gd_tabfield      TYPE string,
      go_table         TYPE REF TO cl_salv_table,
      go_sdescr_new    TYPE REF TO cl_abap_structdescr,
      go_tdescr        TYPE REF TO cl_abap_tabledescr,
      gdo_handle       TYPE REF TO data,
      gdo_record       TYPE REF TO data,
      gs_comp          TYPE abap_componentdescr,
      gt_components    TYPE abap_component_tab.
    FIELD-SYMBOLS:
      <gs_record>   TYPE ANY,
      <gt_itab>     TYPE STANDARD TABLE.
    START-OF-SELECTION.
    continued.

  • Cluster and pooled tables

    when we will use cluster table , pooled table and transparent tables...

    FOr Tables
    http://www.erpgenie.com/abap/tables.htm
    For Tables
    <b>Pooled Tables, Table Pools, Cluster Tables, and Table Clusters</b>
    These types of tables are not transparent in the sense that they are not legible or manageable directly using the underlying database system tools. They are managed from within the R/3 environment from the ABAP dictionary and also at runtime when they are loaded into application memory.Pool and cluster tables are logical tables. Physically, these logical tables are arranged as records of transparent tables. The pool and cluster tables are grouped together in other tables, which are of the transparent type. The tables that group together pool tables are known as table pools, or just pools; similarly, table clusters, or just
    clusters, are the tables which group cluster tables.Not all operations that can be performed over transparent tables can be executed over pool or cluster tables.
    For instance, you can manage these tables using Open SQL calls from ABAP, but not Native SQL.These tables are meant to be buffered and loaded in memory, because they are commonly used for storing internal control information and other types of data with no external (business) relevance. SAP recommends that tables of pool or cluster type be used exclusively for control information such as
    program parameters, documentation, and so on. Transaction and application data should be stored in transparent tables.
    <b>Table Pools</b>
    From the point of view of the underlying DBMS as from the point of view of the ABAP dictionary, a table pool is a transparent table containing a group of pooled tables which, when created, were  assigned to this table pool.
    Field              Type                Description
    TABNAME CHAR(10)   Table                 name
    VARKEY CHAR(n)    Maximum key length n =< 110
    DATALN INT2(5) Length of the VARDATA record returned
    VARDATA RAW(m) Maximum length of the data varies according to DBMS
    <b>Table Clusters</b>
    Similarly to pooled tables, cluster tables are logical tables which, when created, are assigned to a table cluster. Therefore, a table cluster, or just cluster, groups together several tables of type clusters.Several logical rows from different cluster tables are brought together in a single physical record. The records
    from the cluster tables assigned to a cluster are thus stored in a single common table in the database.A cluster contains a transparent cluster key which must be located at the start of the key of all logical cluster tables to be included in the cluster. As well, a cluster contains a long field (VARDATA), which contains the
    data of the cluster tables for this key. If the data does not fit into a field, continuation records are created.
    Field Type Description
    CLKEY1 CHAR(*) First key fields
    CLKEY2 CHAR(*) Second key field
    CLKEYN CHAR(*) nth key field
    PAGENO INT2(5) Number of the next page
    TIMESTMP CHAR(14) Time stamp
    PAGELG INT2(5) Length of the VARDATA record returned
    VARDATA RAW(*) Maximum length of the data section; varies according to database system
    <b>Working with Tables</b>
    The dictionary includes many functions for working with tables. There are five basic operations you can perform on tables: display, create, delete, modify, copy. Please do not confuse displaying a  table with displaying the table entries (table contents). In order to display a table, it must previously exist; otherwise the system will display an  error message in the status bar. For the following example, the table TABNA is used. To display this table, from the main dictionary screen, enter the table name in the Object name
    input field with the radio button selected next to Tables. Then, click on the Display button at the bottom of the screen, or press the F7 function key,  or, alternatively,
    select Dictionary object Display from the menu.
    In this screen, you can see table information such as
    ¨ Table type, shown next to the name of the object. In the example, it is a transparent table.
    ¨ Short text description.
    ¨ Name of the user who made the last change, and the date of the change.
    ¨ Master language.
    ¨ Table status. On the screen, you can see this table is saved and active.
    ¨ Development class. For information on development classes, refer to Chap. 6.
    Delivery class, which sets the maintenance group for the table. It controls how tables will behave during client copy procedures, upgrades, and so forth.¨
    Tab. Maint. Allowed flag, which indicates whether you can generate a screen for maintaining table entries.
    ¨Then, on the lower part of the screen, you can see the table fields with all associated characteristics such as:
    ¨ Field name.
    ¨ Key indicator. When set, this field is the primary key, or part of it.
    ¨ Data element.
    ¨ Basic data type.
    ¨ Length.
    ¨ Check table.
    ¨ Short text, describing the field.
    Additional information about the table can be displayed by selecting the corresponding functions from the menu or directly from the application toolbar, such as keys, indexes, or technical settings.
    Regards,
    Balaji
    **Rewards for helpful answers

  • Inconsistencies on pool tables when import patches

    Hello Experts.
    I installed the enhacements packages of EA-PS and SAP_APPL (version 603) on my system SAP ECC 6.0 Unicode 64 bits. This process terminated correctly.
    Then, when i'm importing another patch of SAP_BASIS or another component with the spam, the system return me the following error in the check_requirements phase:
    " Some open conversion requests still exist in the ABAP Data Dictionary
    for the following ABAP Dictionary objects. To avoid inconsistencies and
    loss of data, you must process these conversions first.
    Proceed as follows:
    - Open a new session.
    - Start the Database Utility (transaction SE14).
    - Correct the inconsistencies for the specified objects.
    - Repeat the import phase. If no more inconsistencies are found, the
      import continues.
    Phase CHECK_REQUIREMENTS: Open ABAP Dictionary Conversions
    Object Type       Object Name
    Pools/Clusters    GLSP
                             GLTP"
    In the se14, for both, there is not inconsistencies on the database objects but on the runtime objects, the
    length of the vardata field is a half of the value of this field of the runtime object.
    For correct this inconsistencies, i execute the reports RADPOCNV (ABAP Dictionary: Table Pool Conversion) and RATPONTC (Adaption of VARDATA field for table pools).
    Now this tables are totally consistent but when i import again the SAP_BASIS patch or another patch, the inconsistence error still appears.
    ¿How could i resolve this inconsistencies?
    Thanks in advance.

    http://ora-24006.ora-code.com/

Maybe you are looking for