Skip to Content
author's profile photo Former Member
Former Member


What are table-infotypes?

I am not sure about this term and how it is different from infotypes as such.

Please suggest.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

6 Answers

  • Best Answer
    Posted on Jan 28, 2008 at 05:28 AM


    Hi table infotypes are the ones which lets you store data in a tabular structure in one infotype record.

    these infotype are normally used in OM, for e.g (1002, 1016, 1017 etc).

    All the OM infotype which have HRT table (search in se11 with HRT*), all these are table infotypes.



    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 28, 2008 at 05:20 AM


    I think it is infotype tables like for IT0001-- PA0001

    & for IT0002 -

    PA0002 & IT1001--HRP1001 like.



    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 28, 2008 at 05:27 AM

    HR Personnel Administration

    Infotypes are usually numeric.


    Infotype 0001 is for Org Assignment,

    corresponding table where the data is Stored is always PA (followed by infotype number).

    so for Infotype 0001 the corresponding table would be PA0001. The Screen Structure is more or like P (Infotype Number) - P0001.

    HR Org Management Infotypes


    Infotype 1000 is for Org Management Objects,

    Corresponding table where the data is Stored is always HRP (followed by infotype number).

    So for Infotype 1000 the corresponding table would be HRP1000.

    To Read the table there are standard MACROS provided by SAP. which are stored in the tabe TRMAC.

    Reward if useful.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 28, 2008 at 07:07 AM

    First of all lets keep in mind that: in order to pass data to and from screen fields, they must have the same name as a global variable. Having said that we must define a global array containing our data and a global table view control that will be used to program the data transfers.

    Let us start with the data. Assuming that the table you wish to work with corrsponds to an ABAP dictionary structure named ZMY_STRUCT, then the table definition might look something like the following:

    • Basic ITAB

    DATA BEGIN OF tbl_mydata OCCURS 0.

    DATA: sel TYPE c.

    INCLUDE STRUCTURE zmy_struct.

    DATA: END OF tbl_mydata.

    One can reasonably ask why a table with a header line and again why an ABAP dictionary structure. The answer to both questions will be given shortly afterwards but for now let's just say that things work much easier this way, or otherwise they don't work at all :-). The table control definition should be something like



    Make sure that the screen number corresponds to the actual screen number of your program. Next move to the screen and press the layout button to invoke the screen painter. Inside the screen drop a table control item and name it TC_MYDATA. Size it so that it fits your screen according to your needs. Double click on the table control to bring up the properties dialog box.

    The sel field of the tbl_mydata table will mark the user selected lines. Getting a field symbol to point at the selected line is as easy as writing something like :


    <fs> LIKE LINE OF tbl_mydata.

    READ TABLE tbl_mydata ASSIGNING <fs> WITH KEY sel = 'X' .


    MESSAGE s888(sabapdocu) WITH text-e01. " No Selection


    • Do what ever you want with -...


    Now press F6 to invoke the screen painter Dict.Program Fields window. In the field named Table field Name enter a search patter like like TBL_MYDATA-* and press the button labeled Get from program to display the matching table entries. Select the ones you wish to add to you screen and press the green ok button at the bottom. Then click inside the table view control to create the appropriate columns. Had the tbl_mydata table been declared any other way -- i.e. using a TYPES section or without the header line, then the process or field selection through F6 would not work.

    Note: At this point just save the screen and exit screen painter without performing any kind of syntax check or activation.

    Moving back to the screen properties, the basic flow logic should at least contain the following


    MODULE status_0200.

    LOOP AT tbl_mydata WITH CONTROL tc_mydata

    CURSOR tc_mydata-current_line.

    MODULE read_tbl_line.



    MODULE exit_screen_0200 AT EXIT-COMMAND.

    LOOP AT tbl_mydata.

    MODULE write_tbl_line.


    MODULE user_command_0200.

    The basic idea is that during PBO the contents of the entire table are copied from the table to the table control. Then during PAI the contemns of the table control will be copied from the control back to the table.

    Before copying any data though, we must first set the size of the table control. The best place to do this is probably at the status module. Now, although my mother told me never to use global variables, the usual approach to setting the table size during PBO, starts by declaring a global field named somthing liketotal_entries or table_size being of type i. Having done that your status_XXX module should at least contain the following.

    MODULE status_0200 OUTPUT.

    SET TITLEBAR 'TB_200'.


    DESCRIBE TABLE tbl_istat LINES total_entries.

    tc_mydata-lines = total_entries.

    ENDMODULE. " status_0200 OUTPUT

    To create the read_tbl_line module, double click on the read_tbl_line inside the screen flow editor. A message will pop up asking if the a module named read_tbl_line should be created. Answer yes and depending on the type of program you are creating select the appropriate file. After you press ok, change the text in the editor so it looks like this.

    MODULE read_tbl_line OUTPUT.

    MOVE-CORRESPONDING tbl_mydata TO tc_mydata.

    ENDMODULE. " read_tbl_line OUTPUT

    Finally the write_tbl_line PAI module does the exact opposite. It moves the data from the table control back to the internal table.

    MODULE write_tbl_line INPUT.

    MODIFY tbl_mydata INDEX tc_mydata-current_line.

    IF sy-subrc <> 0.

    APPEND tbl_mydata.


    ENDMODULE. " write_tbl_line INPUT

    From now on any code executing during the user_command_XXX module will get a consistent copy of the data.

    Screen programming in ABAP is a complex subject. This post provides only the basic template for minimal operations. More post will follow explaining how to respond to data changes, sort tables based on selected columns and dynamically changing your screen.



    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 28, 2008 at 12:34 PM

    Thanks Anil, Sravan,Shrinivas and Muneesh.. I will try all of them and let you know.. Please update me if you come across anything more regarding this.

    Thanks a lot..



    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 01, 2008 at 04:11 PM


    I'm not sure if you are trying to create a table infotype but if it is an OM/PD infotype, you can create it using the transaction PPCI and lets you choose whether the infotype is a field infotype or a Table infotype.

    I'm haven't seen the same functionality in PA infotypes. Usually you will have to code it your slef and call the editor function modules. Just out of curosity, is there a similar way to create a PA infotype as such? An infotype with a text editor?


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.