Problem in Infotype 0057

Dear Guru's
In my client few employees are having more than one lic policy. I have created 3 wage types and assigned it to 0057 infotype. When i am creating two records using two different wage types on the same date or by giving some other date for maintaining different LIC policy numbers, either its delimiting or deleting the previous record. If wage type time constraint is a problem kindly let me know that in which table i have to change the time constraint.
Thanks in advance
Thanks and Regards
Suresh.V

Dear Guru's
Thanks a lot and my problem is sloved. I rewarded the points also.
Thanks and Regards
Suresh.V

Similar Messages

  • Problem with Infotype 0319

    Dear Expert,
    I have a problem with infotype 0319 (private insurance indonesia).
    When I create the infotype and run payroll, it will show error message "Enter rate / IDR rate type M for 01.01.2012 in the system settings".
    I already asked my FI consultant and he said that nothing was wrong with his configuration.
    I try to change the infotype WITHOUT CHANGING ANYTHING and the payroll works. Can anyone give me any idea why it can happened? Is it bugs or i miss something in my configuration?
    Thanks & Regards,
    nessiaka

    Hi Salil,
    Thanks for your prompt reply.
    In the link that you gave me, there is IDR and USD rate. "Enter rate IDR / USD rate type M for 03.01.2011 in the system settings". while in my case, the error message doesn't give any rate  "Enter rate / IDR rate type M for 01.01.2012 in the system settings".
    But My FI consultant already maintain all the rate. Either from USD / IDR and IDR / USD.
    Also in that link, there is some master data that haven't properly. But in my case, there isn't any problem with my master data. This is proved by clicking the "change icon" and save it, without changing a single thing.
    Any other idea and solution?
    Thanks & Regards,
    nessiaka

  • Problem with infotype 16

    Hello.
    I expose my problem.
    We Need The InfoType 16 'for each person With The fieldname LFZFR. In This feld we include the days to pay the Illness. For ex. we pay 42 Days. You Will include 15 days.
    This is the field we need for reporting. That's because this report does not want to have access to the payroll, only the master of time and personnel, so it is only informative. My question is whether the field can turn affect payroll or have no consequences.
    I changed the property from the PE03 CONTR, adding to the property MOLG my country grouping 04 Spain. In Spain I've added the subfeature ANSVH, so depending on the type of employment relationship show me a specific number of days.
    But when I add the ANSVH, I can not display the menu of possible values ​​contained in this sub-feature.
    http://i294.photobucket.com/albums/mm90/Ivaneee/ansvh.png
    I need to add it somewhere else?
    This post can be of help or not has nothing to do?
    PROBLEM with feature CONTR and the field ANSVH
    And how can I activate the field LFZFR  in infotype 16?
    thanks
    Edited by: Ivaneee on Sep 16, 2011 12:21 PM
    Edited by: Ivaneee on Sep 16, 2011 12:22 PM

    uuuuuuuup

  • Problem updating Infotype 1208 subtype ALUM

    Hi,
    My requirement is to update the infotype 1208 subtype ALUM with the Value "YES" when I terminate a employee in PA40.   ( immediately).
    I am using the FM - HR_INFOTYPE_OPERATION which doesn't seem to work.
    I tried running a BDC for PA30 , but it is not allowing me to edit the employee and says that i am processing him.
    I feel this is an issue with locks. But not sure about how to go with.
    Are there any standard classes available or any other method to use to update this infotype while terminating.
    Regards,
    Karan.

    1) as suggested by Suresh first check the return table to know exaclty the error mesage.
    2) u can update a IT with same values i don think it wil have a problem
    3) to me it looks that it is due to PERNR locked ,as when u r updating it first time the pernr is locked and when u r trying to update it again in the same session it must be failing due to pernr looked..
    so before using FM to update IT ,use Fm -
    CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
      EXPORTING
        NUMBER        = number .
    IMPORTING
      RETURN        =          .
    and after tht call FM to update IT and then call below FM to unlock employee-
    CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
      EXPORTING
        NUMBER        = number.
    IMPORTING
      RETURN        =          .
    this will solve ur probelm .
    amit

  • Problem with infotype 0002

    Hi i'm enhanced infotype 0002, but i had to change the length of a field, and i'm having problems with activation.
    I tried to delete ci_p0002, but after that, i can`'t activate pa0002.
    the table still have that include. How can i delete it??
    Should i do anything else?

    You should not delete ci_p0002.. instead in SE11 double click on ci_p0002 & then delete the custom fields.. you can then activate the table.. be sure to run the database utility via Tcode SE14..
    Whenever you have to add/delete/change fields on an infotype go via PM01.
    ~Suresh

  • Problem in infotype 586

    Hi All.
    I am facing problem while creting the record in infotype 586.
    System is giving an information error, that record for current FY already exist, where as there is record for the last FY. not the current FY.
    Please suggest.
    Regards,
    Aman

    Hi,
    The IT 586 has connection with the payroll period of the control record (TCode - PA03)....
    You can maintain only one record per financial year...
    So until and unless the control record is in the first period of financial year you can't create the new record for for the coming financial year.
    So pls change the control record to the 1st period of the financial year (say 01 2009), and set the status as "Released Mode for Correction".
    regards
    kiran

  • I have a problem with Infotype 0021.

    Hello my name is Uilian(ABAP), helpme!!!
    In SAP(DEV 100) development.
    I create a new field(Nome da Mãe) for infotype 0021 in transaction(PM01), when I go to transaction PA30 the field is deisplayed with success.
    My problem is...
    In SAP(DEV 110) TEST
    The field (Nome da Mãe) does not displayed, I tried to transport the changes of the infotype using transaction scc1 but it doesn't work. I don't have any idea of the problem, helpme.

    Hi silva,
    When enhanching standard infotype or creating new infotypes, two transport requests are created, one is workbench request and other is customize request. Both requests should be transported to ur quality client.
    Regards,
    Thilotham

  • Problem in infotype

    I am creating a custom infotype,for which i created my own package.By using this package i created infotype PSnnnn structure,but when im creating infotype characteristics and then saving it,it asks for a package request.On filling the package request number which i created it gives an error "you cannot use this request".The package which i created and used in creating PSnnnn structure is also not in the list of available packages.
    Please help.

    Go to SE80>Click on the Edit Object pushbutton the menu>select the tab Development Coordination in the Object Selection pop-up> enter you package> click on the change icon-->maintain the Transport Attributes
    seek help from your BASIS resource if you do not know which Transport layer to use.
    ~Suresh

  • Infotype 0057 - Invisible fields - Check on amount/number

    Hi guys,
    I am using the infotype 57 to use the field P0057-MGART only. So in the table V_T588M I have put all the other fields in invisible mode. Anyway, a check is still activated: when I try to save a new record, I have the error message "Enter amount or number" - Message no. PG062, even if the fields amount/number are invisible in the table V_T588M, they should be also inactive.
    Thanks in advance for your answers.
    Olivier Gaign

    Hi Olivier,
    This infotype is to maintain the membership fees and will require the amount/number. Also, the amount field BETRG is not part of the P0057 structure but is computed ie Q0057-BETRG. Pl see if you can use the User exit ZXPADU02 to get rid of this error.
    Regards,
    Suresh Datti

  • Length problem  OM infotype creation

    Hi all,
    I have a requirement for creating an Organizational Management infotype(OM).In that total legth of structure will be around 1500.
    But in PPCI transaction it is not allowing me to create infotype telling "Total length of infotype fields must not exceed 900".
    Any body is having any solution for this?
    Thanks in advance
    Ambili B

    you can create a button in infotype and call a subscreen.code to write this data in cluster table PCL3, simultaneously creating a unique 40 character key to identify record.

  • Problem with infotype enhancement deletion...

    Hi,
    I have deleted infotype enhancement for adding a extra screen field in PM01. But even after that deletion I see that in table PA0001 the CI include is there along with the additional field.
    Please help or let me know the proper method of deleting enhancment.
    Regards,
    Rajesh.

    Hi ..
    Deleting the custome fields in the Infotype 0001 will not solve the issue. There will be some custom screens developed to include the custom fields.
    You can find the customs screens in T582C table. Once it is deleted then the deletion can be told as 100%
    Hope this helps
    Good Luck.
    Shyam

  • Problem in Infotype Creation.

    Hi Experts,
    I have created a Infotype 9051.
    When i try to open it via PA30 it says that No read authorization for Travel and Trip Infotype
    Any pointers will be a great deal of help.
    TIA.
    Edited by: Matt on Nov 13, 2008 12:03 PM - asap text removed

    Hello,
    Configuration values needs to be transported to the client which you are testing for performing any action on that particular infotype. Please check whether you have created Info type the right way.
    [http://www.sap-img.com/human/how-to-create-a-hr-infotype.htm]
    If you have followed all the steps then please ask a SCC1 of the Transport request to Basis so that you can test it there.
    Also, please ask basis team to check your ROLE so that you can maintain Info type entries thru PA30 transaction. May be you are missing some authorizations.
    Hope it helps.
    Thanks,
    Jayant

  • Problem in infotype 0591?

    can any one done uploading data into the table control of infotype 0591?
    To update nominations of employes n to SAP
    kindly send the with code?
    solution rewarded.

    Hi salman ,
    Find the code attached . The functionality of HR_INFOTYPE_OPERATION is ysed here .
    Hope this helps .
    REPORT Zb0591 MESSAGE-ID zhr.
                  TABLES                                   *
    TABLES  :pa0000,p0591.
                  TYPES                                    *
    TYPES : BEGIN OF t_upload,
            pernr_old TYPE string,
            pernr_new TYPE string,
            subty     TYPE string,
            begda     TYPE string,
            endda     TYPE string,
            nam01     TYPE string,
            ADD01     type string,
            REL01     type string,
            DAT01     type string,
            SHP01     type string,
            GRA01     type string,
            nam02     TYPE string,
            ADD02     type string,
            REL02    type string,
            DAT02     type string,
            SHP02     type string,
            GRA02     type string,
            nam03     TYPE string,
            ADD03     type string,
            REL03     type string,
            DAT03     type string,
            SHP03     type string,
            GRA03     type string,
            nam04     TYPE string,
            ADD04     type string,
            REL04     type string,
            DAT04     type string,
            SHP04     type string,
            GRA04     type string,
            nam05     TYPE string,
            ADD05     type string,
            REL05     type string,
            DAT05     type string,
            SHP05     type string,
            GRA05     type string,
            END OF t_upload.
    TYPES : BEGIN OF t_pa0591,
            pernr     TYPE pa0014-pernr,
            subty(4)  TYPE c,
            begda     TYPE char10,
            endda     TYPE char10,
            nam01     TYPE pa0591-nam01,
            add01     TYPE pa0591-add01,
            REL01     type pa0591-REL01,
            DAT01     type char10,
            SHP01(7)  type c,
            GRA01     type pa0591-gra01,
            nam02     TYPE pa0591-nam02,
            add02     TYPE pa0591-add02,
            REL02     type pa0591-REL02,
            DAT02     type char10,
            SHP02(7)  type c,
            GRA02     type pa0591-gra02,
            nam03     TYPE pa0591-nam03,
            add03     TYPE pa0591-add03,
            REL03     type pa0591-REL03,
            DAT03     type char10,
            SHP03(7)  type c,
            GRA03     type pa0591-gra03,
            nam04     TYPE pa0591-nam04,
            add04     TYPE pa0591-add04,
            REL04     type pa0591-REL04,
            DAT04     type char10,
            SHP04(7)  type c,
            GRA04     type pa0591-gra04,
            nam05     TYPE pa0591-nam05,
            add05     TYPE pa0591-add05,
            REL05     type pa0591-REL05,
            DAT05     type char10,
            SHP05(7)  type c,
            GRA05     type pa0591-gra05,
            END OF t_pa0591.
    TYPES : BEGIN OF t_pa0001,
            pernr TYPE pa0001-pernr,
            abkrs TYPE pa0001-abkrs,
            bukrs TYPE pa0001-bukrs,
            END OF t_pa0001.
    Internal table to store hiring action data.
    TYPES : BEGIN OF t_pa0000 ,
            pernr LIKE pa0000-pernr,
            massn LIKE pa0000-massn,
            stat2 LIKE pa0000-stat2,
            END OF t_pa0000.
    TYPES:  BEGIN OF t_error,
            pernr_old TYPE string,
            pernr_new TYPE string,
            begda     TYPE string,
            endda     TYPE string,
            lgart     TYPE string,
            betrg     TYPE string,
            zuord     TYPE string,
            END OF t_error.
                INTERNAL TABLES                            *
    DATA : gt_pa0591 TYPE STANDARD TABLE OF t_pa0591,
           gt_pa0001 TYPE STANDARD TABLE OF t_pa0001,
           gt_pa0000 TYPE STANDARD TABLE OF t_pa0000,
           gt_upload TYPE STANDARD TABLE OF t_upload,
           gt_error  TYPE STANDARD TABLE OF t_error..
    DATA: BEGIN OF bdcdata OCCURS 0.
            INCLUDE STRUCTURE bdcdata.
    DATA: END OF bdcdata.
                WORK AREA                                  *
    DATA : gw_pa0591 TYPE t_pa0591,
           gw_pa0001 TYPE t_pa0001,
           gw_pa0000 TYPE t_pa0000,
           gw_upload TYPE t_upload,
           gw_error  TYPE t_error.
    data : gw_return like BAPIRETURN1 .
    data :gw_p0591 like p0591.
                GLOBAL VARIABLES                           *
    DATA : gv_fname   TYPE string,
           gv_ftype   TYPE char10,
           gv_pernr   LIKE pa0000-pernr,
           gv_name    TYPE string,
           gv_ext     TYPE string,
           gv_error   TYPE string,
           gv_day(2)  TYPE c,
           gv_year(4) TYPE c,
           gv_mon(2)  TYPE c,
           gv_date    TYPE p0028-exdat,
           gv_wtfld   TYPE string,
           gv_wtfld1  TYPE string,
           gv_success(10) type c,
           gv_failure(10) type c.
    data:  l_bapireturn like bapireturn1.
                CONSTANTS
    DATA :  gc_session TYPE d0100-mapn VALUE 'ZHRPYB0591',
            gc_tcode TYPE tstc-tcode VALUE 'PA30',
            gc_err(4) TYPE c VALUE '_err',
            gc_txt(4) TYPE c VALUE '.txt'.
                SELECTION SCREEN                           *
    SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME TITLE text-001.
    SELECTION-SCREEN SKIP.
    PARAMETERS: p_fname LIKE rlgrap-filename OBLIGATORY,
                p_ftype LIKE rlgrap-filetype OBLIGATORY DEFAULT 'ASC'.
    SELECTION-SCREEN END OF BLOCK blk1.
                AT SELECTION SCREEN                        *
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_fname.
      CALL FUNCTION 'F4_FILENAME'
       EXPORTING
         program_name        = syst-cprog
         dynpro_number       = syst-dynnr
      FIELD_NAME          =
       IMPORTING
         file_name           = p_fname.
                START OF SELECTION                         *
    START-OF-SELECTION.
      MOVE : p_fname TO gv_fname,
             p_ftype TO gv_ftype.
      CALL FUNCTION 'GUI_UPLOAD'
        EXPORTING
          filename                = gv_fname
          filetype                = gv_ftype
          has_field_separator     = 'X'
        TABLES
          data_tab                = gt_upload
        EXCEPTIONS
          file_open_error         = 1
          file_read_error         = 2
          no_batch                = 3
          gui_refuse_filetransfer = 4
          invalid_type            = 5
          no_authority            = 6
          unknown_error           = 7
          bad_data_format         = 8
          header_not_allowed      = 9
          separator_not_allowed   = 10
          header_too_long         = 11
          unknown_dp_error        = 12
          access_denied           = 13
          dp_out_of_memory        = 14
          disk_full               = 15
          dp_timeout              = 16
          OTHERS                  = 17.
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      LOOP AT gt_upload INTO gw_upload.
        MOVE :gw_upload-pernr_new to  gw_pa0591-pernr,
              gw_upload-subty     to  gw_pa0591-subty,
              gw_upload-begda     to  gw_pa0591-begda,
              gw_upload-endda     to  gw_pa0591-endda,
              gw_upload-nam01     to  gw_pa0591-nam01,
              gw_upload-ADD01     to  gw_pa0591-ADD01,
              gw_upload-REL01     to  gw_pa0591-REL01,
              gw_upload-DAT01     to  gw_pa0591-DAT01,
              gw_upload-SHP01     to  gw_pa0591-SHP01,
              gw_upload-GRA01     to  gw_pa0591-GRA01,
              gw_upload-nam02     to  gw_pa0591-nam02,
              gw_upload-ADD02     to  gw_pa0591-ADD02,
              gw_upload-REL02     to  gw_pa0591-REL02,
              gw_upload-DAT02     to  gw_pa0591-DAT02,
              gw_upload-SHP02     to  gw_pa0591-SHP02,
              gw_upload-GRA02     to  gw_pa0591-GRA02,
              gw_upload-nam03     to  gw_pa0591-nam03,
              gw_upload-ADD03     to  gw_pa0591-ADD03,
              gw_upload-REL03     to  gw_pa0591-REL03,
              gw_upload-DAT03     to  gw_pa0591-DAT03,
              gw_upload-SHP03     to  gw_pa0591-SHP03,
              gw_upload-GRA03     to  gw_pa0591-GRA03,
              gw_upload-nam04     to  gw_pa0591-nam04,
              gw_upload-ADD04     to  gw_pa0591-ADD04,
              gw_upload-REL04     to  gw_pa0591-REL04,
              gw_upload-DAT04     to  gw_pa0591-DAT04,
              gw_upload-SHP04     to  gw_pa0591-SHP04,
              gw_upload-GRA04     to  gw_pa0591-GRA04,
              gw_upload-nam05     to  gw_pa0591-nam05,
              gw_upload-ADD05     to  gw_pa0591-ADD05,
              gw_upload-REL05     to  gw_pa0591-REL05,
              gw_upload-DAT05     to  gw_pa0591-DAT05,
              gw_upload-SHP05     to  gw_pa0591-SHP05,
              gw_upload-GRA05     to  gw_pa0591-GRA05.
        APPEND gw_pa0591 TO gt_pa0591.
        CLEAR :gw_pa0591,
               gw_upload.
      ENDLOOP.
    *For all the records read from the application server file, get their hiring information
      SELECT pernr massn stat2 INTO TABLE gt_pa0000
      FROM pa0000
      FOR ALL ENTRIES IN gt_pa0591
      WHERE pernr = gt_pa0591-pernr
      AND stat2 = '3'
      AND massn = '01'.
      IF sy-subrc = 0.
        SORT gt_pa0000 BY pernr.
      ENDIF.
         ENDIF.
    PERFORM open_group.
      LOOP AT gt_pa0591 INTO gw_pa0591.
    split gw_pa0591-dat01 at '.' into gv_day gv_mon gv_year.
    concatenate gv_year gv_mon gv_day into gw_p0591-dat01.
    clear : gv_day,
    gv_mon,
    gv_year.
    split gw_pa0591-dat02 at '.' into gv_day gv_mon gv_year.
    concatenate gv_year gv_mon gv_day into gw_p0591-dat02.
    clear : gv_day,
    gv_mon,
    gv_year.
    split gw_pa0591-dat03 at '.' into gv_day gv_mon gv_year.
    concatenate gv_year gv_mon gv_day into gw_p0591-dat03.
    clear : gv_day,
    gv_mon,
    gv_year.
    split gw_pa0591-dat04 at '.' into gv_day gv_mon gv_year.
    concatenate gv_year gv_mon gv_day into gw_p0591-dat04.
    clear : gv_day,
    gv_mon,
    gv_year.
    split gw_pa0591-dat05 at '.' into gv_day gv_mon gv_year.
    concatenate gv_year gv_mon gv_day into gw_p0591-dat05.
    clear : gv_day,
    gv_mon,
    gv_year.
    move:       gw_pa0591-pernr to gw_p0591-pernr,
                gw_pa0591-subty to gw_p0591-subty ,
               gw_pa0591-begda to gw_p0591-begda ,
               gw_pa0591-endda to gw_p0591-endda,
                gw_pa0591-nam01 to gw_p0591-nam01,
                gw_pa0591-ADD01 to gw_p0591-add01,
                gw_pa0591-REL01 to gw_p0591-rel01,
               gw_pa0591-DAT01 to gw_p0591-dat01,
                gw_pa0591-SHP01 to gw_p0591-shp01,
                gw_pa0591-GRA01 to gw_p0591-gra01,
                gw_pa0591-nam02 to gw_p0591-nam02,
                gw_pa0591-ADD02 to gw_p0591-add02,
                gw_pa0591-REL02 to gw_p0591-rel02,
               gw_pa0591-DAT02 to gw_p0591-dat02,
                gw_pa0591-SHP02 to gw_p0591-shp02,
                gw_pa0591-GRA02 to gw_p0591-gra02,
               gw_pa0591-nam03 to gw_p0591-nam03,
                gw_pa0591-ADD03 to gw_p0591-add03,
                gw_pa0591-REL03 to gw_p0591-rel03,
               gw_pa0591-DAT03 to gw_p0591-dat03,
                gw_pa0591-SHP03 to gw_p0591-shp03,
                gw_pa0591-GRA03 to gw_p0591-gra03,
               gw_pa0591-nam04 to gw_p0591-nam04,
                gw_pa0591-ADD04 to gw_p0591-add04,
                gw_pa0591-REL04 to gw_p0591-rel04,
               gw_pa0591-DAT04 to gw_p0591-dat04,
                gw_pa0591-SHP04 to gw_p0591-shp04,
                gw_pa0591-GRA04 to gw_p0591-gra04,
              gw_pa0591-nam05 to gw_p0591-nam05,
                gw_pa0591-ADD05 to gw_p0591-add05,
                gw_pa0591-REL05 to gw_p0591-rel05,
               gw_pa0591-DAT05 to gw_p0591-dat05,
                gw_pa0591-SHP05 to gw_p0591-shp05,
                gw_pa0591-GRA05 to gw_p0591-gra05.
                gw_p0591-infty = '0591'.
    split gw_pa0591-begda at '.' into gv_day gv_mon gv_year.
    concatenate gv_year gv_mon gv_day into gw_p0591-begda.
    clear : gv_day,
    gv_mon,
    gv_year.
    split gw_pa0591-endda at '.' into gv_day gv_mon gv_year.
    concatenate gv_year gv_mon gv_day into gw_p0591-endda.
    clear : gv_day,
    gv_mon,
    gv_year.
    call function 'BAPI_EMPLOYEE_ENQUEUE'
          exporting
            number = gw_p0591-pernr
          importing
            return = l_bapireturn.
      if l_bapireturn is initial.
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'
        EXPORTING
          infty                  = gw_p0591-infty
          number                 = gw_p0591-pernr
          SUBTYPE                = gw_p0591-subty
        OBJECTID               =
        LOCKINDICATOR          =
          VALIDITYEND            = gw_p0591-endda"'20070401'
          VALIDITYBEGIN          = gw_p0591-begda"'20070101'
         RECORDNUMBER           =
          record                 = gw_p0591
          operation              = 'INS'
        TCLAS                  = 'A'
          DIALOG_MODE            = '0'
        NOCOMMIT               =
        VIEW_IDENTIFIER        =
        SECONDARY_RECORD       =
       IMPORTING
         RETURN                  = gw_return
        KEY                    =
      call function 'BAPI_EMPLOYEE_DEQUEUE'
            exporting
              number = gw_pa0591-pernr
            importing
              return = l_bapireturn.
    endif.
    ENDLOOP.
    Rewards if usefule.
    Regards,
    SureshP

  • Problem with Infotype 194

    Hi All,
    When I am trying to create Infotype 194(Garnishments document type) I am getting the following error.
    *"for object RPGARNSUB, number range interval 01 doesn;t exist PA08"*_
    I have created  number range interval anyways, still I get the same error.
    Any solutions?
    Thanks.
    Vivek.

    There're actually two number ranges used in garnishment, one for garnishment transfer (PA07), and the other is for vendor subgroup (PA08).  Looks like what's missing is number range for vendor subgroup.
    Check tcode 'PA08' to see if you've set up number ranges with interval '01' yet.
    Rgds.

  • Problem with Infotype 0061

    I'm trying to enhance dynpro 2910 of infotype 0061, via pm01
    I've created entrance in t582c, modulpool and Dynpro.
    But when i access that dynpro via pa30 i can't see my new fields
    Any ideas???

    cross check with this
    http://www.sapdevelopment.co.uk/hr/hr_infotypes2.htm
    Regards
    Prabhu

Maybe you are looking for