Infotype header definition

hi all
what is infotype header definition???
what is the use of table T588J
regards

Hello,
in each infotype you can select which fields are to be diplayed, PERNR-PERSG etc.
In customizing under Customizing user interfaces-change screen header you first select Header modifier where you create or select one of the exististing if it is ok with you and you assign it to master data or applicant data.
In infotype header definition(which is the table you asked for) you define in your header modifier the fields, the infotype to which are to be displayed, the column and the field type.
You will have to do several changes until the result is satisfying!
At the end you assign to the infotype the header modifier at Header structure per infotype
ps. don't forget to generate the table T588J when you are finished.
Regards
Nadia

Similar Messages

  • T588J - Infotype Header Definition

    Greetings
    The table T588J has all relevant infotypes and fields are placed in the first three lines only.
    Questions :
    1)From where the Line 4 information is picked up . (Start Date - End Date and change info)
    2) Can we add more fields in Line 4 and move start date - end date to Line 5 - How ?
    Thanks
    AP

    Hi Avinash,
    Lines 1-3 are permitted for changes.
    Line 4 is default.
    I am not sure but I dont think that you can add a line 5 or change the contents of line 4.
    Regards,
    Divya

  • What is an Infotype header?

    please tell me that also. iam preparing for job iam a fresher i don't have any experience in sap-hr.so ,please help me in that
    <Moderator Comments: Pl do not use all caps>

    Hello,
    The headers displayed on each infotype and on the initial PA20/PA30 screen is configurable. The relevant IMG path is:
    Personnel Mgmt > Personnel Admin > Customizing User Interfaces > Define Screen Header
    The infotype header is just the 3 lines in the header part (with personnel number, name, EE group. EE subgroup, etc)
    Here are the 3 main tables : V_T588J Header Modifier Definition
    V_T588I Header Modifier to Screen Header
    V_582A_B Screen Header to Infotype
    that you will find in the IMG path above.
    Hope it helps,
    Christine

  • Referencing a substitution variable in data load rule header definition

    Hi All,
    Im trying to add a substitution variable to the header definition of a DLR.
    the sub var is &CurrMonth.
    When I execute the data load I get an "unknown member error" with a list of all members in the header definition, including Oct which is my current month.
    It looks like the DLR is resolving the sub var but for some reason it is refusing to load data.
    We are on 9.2.0.1.
    Are sub vars referenced differently for DLR?
    Thanks for your help.
    Seb

    Hi Seb!
    Hope you're well. You're doing everything right with the subvars so the issue must be elsewhere. Is the list comma separated? Sorry I can' help more :(
    Gee

  • Authorization Check Infotype Header

    Hi all,
    i posted the following threat in HCM Forum, but i think it is also a question for ABAP Forum
    Authorization Check Infotype Header
    Thanks & regards

    1. authorisations in hr cannot be controlled at infotype-header level and/or infotype field level.
    2. If only a few fields of a specific infotype are to be allowed for a user the most efective way of doing it is by way of creating a view for the infotype with only the allowed fields in it.
    3. another way of doing it is by way of a custom authorisation object (potentially) but then again your requirement is not going into explicit details,. so this option is a possibility you may want to do some due diligence on.
    cheers

  • Infotype Header

    Hi,
    I have created a custom PA infotype and as per the requirement the database table for this infotype would have dates defaulted to 01.01.1800 and 31.12.9999 since the actual data would be stored in OM tables.
    Now, the infotype header is retrieving data as of the BEGDA and hence in the header of the infotype the latest values are not getting displayed. I want the header to display the values valid as of system date.
    Please let me know where to configure that.
    Thanks,
    Harini

    Got the solution.

  • Photo upload in infotype 2, or infotype header

    Can anyone tell me in detail how to upload photo of employee in infotype header and what all needs to be done in terms of basis also , archieve link or something.  I know oAAD but how does that linkage happen.

    Solution in https://wiki.sdn.sap.com/wiki/display/ERPHCM/Add%20Employee%20Photo%20on%20Infotype%200002?showChildren=false is very good.
    Mass upload program ZHR_BDC_UPLOADPIC requires input every file path for photos in dialog window.
    I have improved this process:
    1. Made a copy of program OANEWCON (program in transaction OAOH)  ZOANEWCON (hung on new transaction ZOAOH)
    inserted two lines  allow to pass a path as a parameter to this program:
    PROGRAM ZOANEWCO MESSAGE-ID OA.
    TABLES: TOAV0, TOAOM, TWFDB, TOAPA.
    DATA: KEY LIKE OJINT-KEY.
    DATA: OBJECT LIKE OJINT-NAME.
    DATA: OBJECT_ID LIKE TOAV0-OBJECT_ID.
    DATA: ARCHIV_ID LIKE TOAV0-ARCHIV_ID.
    DATA: ARC_DOC_ID LIKE TOAV0-ARC_DOC_ID.
    DATA: ABLAGEDATUM LIKE SAPB-SAPABLDATE.
    DATA: AR_DATE LIKE TOAV0-AR_DATE.
    DATA: DEL_DATE LIKE TOAV0-DEL_DATE.
    DATA: SAP_OBJECT LIKE TOAOM-SAP_OBJECT.
    DATA: AR_OBJECT LIKE TOAOM-AR_OBJECT.
    DATA: EXPIRY_TIM LIKE TOAOM-EXPIRY_TIM.
    DATA: METHOD LIKE OJINT-METHOD.
    DATA: RETURN LIKE OJINT-RETURN.
    DATA: PARAMETER LIKE OJINT-PARAMETER.
    DATA: BEGIN OF I_TOAV0 OCCURS 1.
            INCLUDE STRUCTURE TOAV0.
    DATA: END OF I_TOAV0.
    DATA: BEGIN OF I_TOAOM OCCURS 1.
            INCLUDE STRUCTURE TOAOM.
    DATA: END OF I_TOAOM.
    DATA: BEGIN OF FIELDS OCCURS 1.
            INCLUDE STRUCTURE OJFIELDS.
    DATA: END OF FIELDS.
    DATA: OK_CODE(4)         TYPE C,
          OK_CODE_SAVE(4)    TYPE C.
    DATA: CREATE(2) VALUE '01'.
    DATA: infile(70).
          MODULE INIT0100 OUTPUT                                        *
    MODULE INIT0100 OUTPUT.
      SET TITLEBAR '000'.
      CLEAR: OBJECT, AR_OBJECT.
      SET PF-STATUS 'POPU100'.
    ENDMODULE.
          MODULE EXIT_BEARBEITEN INPUT                                  *
    MODULE EXIT_BEARBEITEN INPUT.
      OK_CODE_SAVE = OK_CODE.
      CLEAR OK_CODE.
      CASE OK_CODE_SAVE.
        WHEN 'ESC'.
          SET SCREEN 0.
          LEAVE SCREEN.
        WHEN 'BACK'.
          SET SCREEN 0.
          LEAVE SCREEN.
        WHEN 'CANC'.
          SET SCREEN 0.
          LEAVE SCREEN.
      ENDCASE.
    ENDMODULE.
          MODULE READ0100 INPUT                                         *
    MODULE READ0100 INPUT.
      OK_CODE_SAVE = OK_CODE.
      CLEAR OK_CODE.
      CLEAR KEY.
      CASE OK_CODE_SAVE.
        WHEN 'NEW'.
          OBJECT = TOAOM-SAP_OBJECT.
          AR_OBJECT = TOAOM-AR_OBJECT.
          SELECT * FROM TOAOM WHERE AR_OBJECT = AR_OBJECT
          AND SAP_OBJECT = OBJECT.
          ENDSELECT.
          IF SY-SUBRC <> 0.
            MESSAGE W251 WITH AR_OBJECT OBJECT.
            "MESSAGE: NO NCI-DOCTYPE with this Objecttyp
          ELSE.
    Corr. 3.0. Begin
    Authority check with Archive id
            ARCHIV_ID = TOAOM-ARCHIV_ID.
            PERFORM AUTHORITY_CHECK_CREATE(OAALL)
               USING ARCHIV_ID OBJECT SPACE AR_OBJECT SPACE
               CHANGING SY-SUBRC.
            IF SY-SUBRC NE 0.
              MESSAGE ID SY-MSGID TYPE 'E' NUMBER SY-MSGNO
                      WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
            ELSE.
    Corr. 3.0 End.
    Change 5.0 for BOR Objecttypes with GUID vok
             METHOD = 'EDIT'.
        Eingabe der Object_Id
             CALL FUNCTION 'OJ_KEY_FIELDS'
                  EXPORTING
                       KEY                  = KEY
                       METHOD               = METHOD
                       OBJECT               = OBJECT
                       TITLE_DIALOG         = TEXT-001
                  IMPORTING
                       KEY                  = KEY
                  TABLES
                       FIELDS               = FIELDS
                  EXCEPTIONS
                       EXC_OBJECT_NOT_FOUND = 01.
              CALL FUNCTION 'ARCHIV_POPUP_OBJECT_KEY'
                  EXPORTING
                DISPLAY               = ' '
                    OBJTYPE               = OBJECT
                    TITLE                 = TEXT-001
                OBJKEY                = ' '
                LASTTYPE              = ' '
                LASTKEY               = ' '
                    CHECKEXISTENCE        = 'X'
                GENERIC               = ' '
                EDIT                  = ' '
                 IMPORTING
                CHANGED               =
                RETURN                =
                    OBJKEY                = KEY
                USE_LAST              =
                  EXCEPTIONS
                    ERROR_PARAMETER       = 1
                    USER_CANCEL           = 2
                    OTHERS                = 3
    End of change 5.0 for BOR Objecttypes with GUID vok
              IF SY-SUBRC <> 0.
                MESSAGE ID SY-MSGID TYPE 'W'      NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
                CLEAR TOAV0.
              ELSE.
                TOAV0-OBJECT_ID = KEY.
                IF KEY EQ SPACE.
                  MESSAGE W252.
                  CLEAR TOAV0.
         'Kein SAP-Beleg vorhanden.'.
                ELSE." create archiveobject versus dialog
                  PERFORM CREATE_ARCHIVE_OBJECT.
                ENDIF.
              ENDIF.
            ENDIF.
          ENDIF.
      ENDCASE.
    ENDMODULE.
          FORM CREATE_ARCHIVE_OBJECT                                    *
    FORM CREATE_ARCHIVE_OBJECT.            "Create an archiveobject
      CALL FUNCTION 'ARCHIV_CREATE_DIALOG_META'
           EXPORTING
                AR_OBJECT                = TOAOM-AR_OBJECT
                OBJECT_ID                = TOAV0-OBJECT_ID
                SAP_OBJECT               = TOAOM-SAP_OBJECT
                FILE                     = infile
           IMPORTING
                ARCHIV                   = TOAV0-ARCHIV_ID
                ARCHIV_DOC_ID            = TOAV0-ARC_DOC_ID
                DOCUMENTCLASS            = TOAOM-DOC_TYPE
           EXCEPTIONS
                ERROR_ARCHIV             = 01
                ERROR_COMMUNICATIONTABLE = 02
                ERROR_CONNECTIONTABLE    = 03
                ERROR_KERNEL             = 04
                ERROR_PARAMETER          = 05
                ERROR_SCANQUEUE          = 06
                others                   = 7.
      IF SY-SUBRC <> 0.
        MESSAGE ID SY-MSGID TYPE 'W'      NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        CLEAR TOAV0.
      ELSE.
        MOVE TOAOM-DOC_TYPE TO TOAV0-RESERVE.
        TOAV0-SAP_OBJECT = TOAOM-SAP_OBJECT.
        TOAV0-AR_OBJECT = TOAOM-AR_OBJECT.
        COMMIT WORK.
        MESSAGE I044.
      ENDIF.
    ENDFORM.
    2. in program ZHR_BDC_UPLOADPIC calling transaction ZOAOH
    added parameters for data file, for a photo ID in archive, and add date of a photo into the data file
    e.g.: 0000000527.09.2004C:\Photos\5.jpg
    {REPORT ZHR_BDC_UPLOADPIC NO STANDARD PAGE HEADING LINE-SIZE 255.
    DATA : BEGIN OF IT_DATA OCCURS 0,
             PERNR(8), " LIKE RP50G-PERNR,
             DATUM(10), "date of the photo
             FILENAME(128),
           END OF IT_DATA.
    DATA:  T1(80),
                 file_path(132).
    SELECTION-SCREEN: BEGIN OF BLOCK sp WITH FRAME TITLE text-f01
      NO INTERVALS.
      SELECTION-SCREEN BEGIN OF LINE.
        SELECTION-SCREEN COMMENT 5(4) A1 .
      SELECTION-SCREEN   END OF LINE.
    SELECTION-SCREEN: END   OF BLOCK sp.
       INCLUDE BDCRECX1.
    SELECTION-SCREEN SKIP 2.
    SELECTION-SCREEN: BEGIN OF BLOCK vst WITH FRAME TITLE text-f02.
    SELECTION-SCREEN BEGIN OF LINE.
      SELECTION-SCREEN COMMENT 3(25) TEXT-S11 FOR FIELD IDOBJ.
      selection-screen position 45.
      PARAMETERS POPFILE(128)  VISIBLE LENGTH 50
        DEFAULT 'C:\PICTURE.TXT'.  "input data file
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
      SELECTION-SCREEN COMMENT 3(25) TEXT-S12 FOR FIELD IDOBJ.
      selection-screen position 45.
      PARAMETERS IDOBJ(2) DEFAULT '01'.  "id object
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN: END   OF BLOCK vst.
    at selection-screen on value-request for POPFILE.
      call function 'F4_FILENAME'
             exporting
                 field_name = file_path
             importing
                 file_name = POPFILE.
           exception
                others    = 1.
    START-OF-SELECTION.
      PERFORM OPEN_GROUP.
      CALL FUNCTION 'WS_UPLOAD'
        EXPORTING
          FILENAME = POPFILE
          FILETYPE = 'ASC'
        TABLES
          DATA_TAB = IT_DATA
        EXCEPTIONS
          CONVERSION_ERROR = 1
          INVALID_TABLE_WIDTH = 2
          INVALID_TYPE = 3
          NO_BATCH = 4
          UNKNOWN_ERROR = 5
          GUI_REFUSE_FILETRANSFER = 6
          OTHERS = 7.
      IF SY-SUBRC NE 0.
        WRITE : / 'No to able read input file'.
        STOP.
      ELSE.
        WRITE : / 'Data processing ...'.
        T1 = 'Data processing ...'.
        MESSAGE T1 Type 'S'.
      ENDIF.
      LOOP AT IT_DATA.
        PERFORM BDC_DYNPRO USING  'ZOANEWCON'         '0100'.
        PERFORM BDC_FIELD  USING  'BDC_CURSOR'       'TOAOM-AR_OBJECT'.
        PERFORM BDC_FIELD  USING  'BDC_OKCODE'       '=NEW'.
        PERFORM BDC_FIELD  USING  'TOAOM-SAP_OBJECT' 'PREL'.
        PERFORM BDC_FIELD  USING  'TOAOM-AR_OBJECT'  'HRICOLFOTO'.
        PERFORM BDC_FIELD  USING  'INFILE'           IT_DATA-FILENAME."JPG
        PERFORM BDC_DYNPRO USING  'SAPLOA12'         '0200'.
        PERFORM BDC_FIELD  USING  'BDC_CURSOR'       'OBJID-VALUE(03)'.
        PERFORM BDC_FIELD  USING  'BDC_OKCODE'       '=OK'.
        PERFORM BDC_FIELD  USING  'OBJID-VALUE(01)'  IT_DATA-PERNR.
        PERFORM BDC_FIELD  USING  'OBJID-VALUE(02)'  '0002'.
        PERFORM BDC_FIELD  USING  'OBJID-VALUE(04)'  IDOBJ.
        PERFORM BDC_FIELD  USING  'OBJID-VALUE(05)'  IT_DATA-DATUM.
        PERFORM BDC_TRANSACTION USING 'ZOAOH'.
        clear IT_DATA-FILENAME.
      ENDLOOP.
      PERFORM CLOSE_GROUP.}

  • Header Definition in Load Rule

    Hi,
    Is there any limitation of defining members in "Data load Settings" under the "Header Definition" while creating a load rule?
    let me explain the issue. There are say 13 dimensions in the outline and we have only 7 dimensions in the source file can we include the rest (members related to the other 6 dimensions) in the "Header definition"?
    If YES, Is there any limitation?
    Thanks,
    RNG

    I've not seen any limitation and believe I have done that many dimensions in a header. I have run into a bug (I think) in 9 and 11 that is you sue a substitution varible in the header, it can't be the last item in the header. For some reason, It does not always get recogonized

  • Infotype header the format

    hello,
    As you know in the infotype header the format name that the screen shows is diferent
    for USA:            Last Name  , Name
    for MEX version :   Name , Last Name
    I need both to have the same format (Name , Last Name)
    Is that posible?
    Best Regards.

    Hello,
    Sure it's possible.
    1º) Open an infotype in pa20/pa30
    2º) Go system -> Status
    3º) Save the value of Program(Subscreen). E.g.: /1PAPAXX/HDR_00288A
    4º) Open Se38
    5º) Open the copied header. E.g.: /1PAPAXX/HDR_00288A
    6º) Check the comments in blue. The header modifier will be the 2 number on second column. E.g.:
    T588J (Table to change the header fields)
    002  88  1  01  TXD   0000   PERNR   08   PN1
    88 = Header modifier. Save this number.
    7º) Open SM31
    8º) Table T588J
    9º) Open the corresponding header modifier. E.g.: 88
    Now you can change the header
    If you nede to change the format displayed go thru table T552N and set the value at field "Conversion".
    Example:
    Conversion = 07 , make this:
                     Before   >    After
                   - GJM      >  G.J.M.
                   - ThChr    >  Th.Chr.
    Hope that helps.
    Márcio Leoni

  • Enhancements on Infotypes header screen

    Can I insert a push button in Infotype header screen?
    How can I do it?
    Regards
    Angela

    Hi all,
    I need to know if is it possible to add a custom field in COR1 for process order. I searched forum for something about this, but cannot find anything.
    can anybody please suggest me something ?
    thanks
    Kruthik

  • Infotype Header Data - Cost center- System to read the latest data

    Dear Group Members,
    I am modifying Infotype Header data and calling Cost center (Field - KOSTL) in header data via modifying header data in   table T588J. The cost center values appears on the  header data (As stored in Infotype 0001) however it appears with the oldest data. i.e. if the employee cost center had been changed after his joining system does not picked up the Latest data/ Latest cost center value.
    Any one on how to resolve this issue with SAP Standard functionality.
    Regards
    VISHAL SAXENA
    SAP Specialist - HCM

    Hi,
    The answer to your question lies in table V_582A_B. You can either access it through SM30 or by following IMG path:
    SPRO>Personnel Management>Personnel Administration>Customizing User Interfaces>Change Screen Header>Header structure per infotype
    There is a u201Cchoose datau201D indicator for each infotype. If that is checked, the header displays data as per the start date of infotype displayed; otherwise, it shows data valid as of system date. Please bring up SAP help on the field by F1 for more information.
    Also check table T588H (data selection field) as it has some dependencies for the above mentioned settings. The table can be brought up from:
    SPRO>Personnel Management>Personnel Administration>Customizing User Interfaces>Change Screen Header> Infotype header data selection control
    Hope this helps.
    Donnie

  • Add a logo to the header definition of an Interactive Report

    Hi Folks.
    Using Apex 3.1 and BI Publisher.
    I am enabling an Interactive Report region to output to PDF & Excel.
    Has anyone managed to add a logo to the Header/footer definition in the Print Attributes section?
    Is it possible? The region definition does not understand simple HTML syntax.
    If anyone would let me know if a) They've done it or b) It ain't possible that would be great.
    Many thanks.
    Dogfighter.

    Just reading through this thread. So perhaps a few comments might be helpful:
    - Interactive report regions do currently not support Report Layouts, you're limited to the built-in generic layout and won't be able to include images
    - You can add a button to your interactive report region page which could initiate the download of a report query, when doing this, you would get the result set of your report query not the interactive report region, so even if the queries are the same, you might have different filters applied to your interactive report
    - You can in fact include static images in your RTF report layouts using the BI Publisher Desktop Word Plug-In and MS Word, so you can have logos etc in your PDF documents. But report layouts currently only work with report queries and classic report regions
    - You can also include dynamic images in your PDF, e.g. based on images stored in a BLOB column, there's currently a character escaping issue causing some trouble with this, which will be fixed in 3.1.1, more on that once 3.1.1 is out (soon)
    - the print server overwrite is designed to point to a different print server than the one configured for your APEX instance, not to point to a specific report. So if your instance has BI Publisher configured, but for a specific report you want to do some special rendering using your own code, you can write e.g. a JSP, Servlet, etc that's doing the rendering, and then point yout report to that URL
    Hope this helps, we do plan to add support for report layout to interactive report regions in the next full release of Application Express
    Regards,
    Marc

  • Infotype header - best practice

    Hi group
    Today our ifnotype headers are created in a way that makes us have to break a lot of infotypes just to refresh the header.
    There are 2 reasons in my opinion:
    - We have chosen to read header on infotype begda
    - We have eg. position information in the header
    We want to change this so we don't have to break eg. address just to read correct data.
    I don't feel reading header at sy-datum is a right choice.  This can give an incorrect picture if you read an infotype and the header is inconsistent with the actual situation in the date-range for the infotype.
    So I am leaning towards letting the header contain much less information.
    Does anyone have some "best practice" thoughts?
    Any documentation I can read up on regarding best practice on this matter?
    Thanks in advance
    Kirsten

    Hi,
    Headers, in general, are part of the whole philosophical debate. Iu2019ve seen both ways: current dated and infotype date driven. Iu2019m an advocate of them being infotype date driven for the very same reason that you mentioned: display what is on the record.
    The other school of thought is to always display current information. It also gets some leverage depending on what is being displayed. If you have OM related data like position, job, org units etc, and clients may want to always display the current information. Maybe they are trained that way to only pay attention to headers to give them ad-hoc type information. They can get historical data through other reports.
    I donu2019t think there is any u201Cbest practiceu201D with headers; itu2019s a purely philosophical choice.
    Hope this helps.
    Donnie

  • SSN value in Screen header

    Hi All,
    We have a requirement where we have to call SSN number field with *value ******** instead of orginal value* in PA30 screen header. Is it possible?
    Kind regards.
    Subhash

    Hi,
    Please check following tables  (transaction SM30):
    V_582A_B     Header Structure per Infotype
    V_T588I     Header Modifier
    T588J     Infotype Header Definition     
    T588H     Infotype Header Data Selection Control
    Cheers

  • Header Problem in PA30

    Dear Gurus
    I am facing some problem, which is related to header which comes into PA30 Screen, fieled Name EG, ESG is not shown,  Check all settings under Customizing User Interfaces, every thing is perfectly configured and matched to the QAS server.
    System also call different screens when go to infotypes.
    Regards
    waseem

    hi waseem
                    please check below table for infotype 0001
    V_582A_B Header Structure per Infotype (SM30)
    V_T588I Header Modifier
    T588J Infotype Header Definition
    T588H Infotype Header Data Selection Control
    T588L Field names for screens different from DDIC entry
    it becoz pa30 header is directly related to infotype 0000 & 0001 header
    Thanks
    Nh

Maybe you are looking for