LSMW - PA30 for infotype 851

Hi Everyone,
I am loading some files for IT851 and I am having some problems with the metro field. I can see that for metro the value should be passed is 1 and 0 for non-metro. When I am running the batch in foreground I could see that the recording is setting this field to 1 - Metro. The batch was saved successfuly but this field is always set to non-metro. I tried to change it manually and it is working. I am not sure if the LSMW cannot set this properly. Is there anyway to fix this problem? thanks in advance!
Regards,
Mike Nacionales

HI,
After you do the recording,delete the recorded values in the pararmeter or else the system may  take the defualt values from the recording. After this try to upload it ,it may solve your problem.
Thanks

Similar Messages

  • How to validate the Male or Female in for infotype 002 in LSMW at FieldMapp

    Dear freinds,
               Small problem in LSMW for infotype 0002.
    Whiel recording for infotype 002  ihae done for an employee based on FeMale(GESC2) , no when i uploading data i am having for male (GESC1) ...how can i toggle in my
    Field mapping please can any body tell me
    My field mapping presenlty have is :
    __BEGIN_OF_RECORD__ Before Using Conversion Rules
                        Rule :   Default Settings
                        Code:    ZPA30_002 = INIT_ZPA30_002.
    TABNAME                      Table Name
                        Rule :   Default Settings
                        Code:    ZPA30_002-TABNAME = 'ZPA30_002'.
    TCODE                        Transaction Code
                        Rule :   Default Settings
                        Code:    ZPA30_002-TCODE = 'PA30'.
    PERNR                        Personnel Number
                        Source:  ZP0002_STRUC-PERNR (Personnel number)
                        Rule :   Transfer (MOVE)
                        Code:    ZPA30_002-PERNR = ZP0002_STRUC-PERNR.
    TIMR6                        Time period indicator: Period
                        Rule :   Constant
                        Code:    ZPA30_002-TIMR6 = 'X'.
    CHOIC                        Infotype selection for HR master data maintenance
                        Rule :   Constant
                        Code:    ZPA30_002-CHOIC = '0002'.
    BEGDA                        Start Date
                        Source:  ZP0002_STRUC-BEGDA (Start Date)
                        Rule :   Transfer (MOVE)
                        Code:    * Date Value as DDMMYYYY
                                 ZPA30_002-BEGDA0(2) = ZP0002_STRUC-BEGDA6.
                                 ZPA30_002-BEGDA2(2) = ZP0002_STRUC-BEGDA4.
    ENDDA                        End Date
                        Source:  ZP0002_STRUC-ENDDA (End Date)
                        Rule :   Transfer (MOVE)
                        Code:    * Date Value as DDMMYYYY
                                 ZPA30_002-ENDDA0(2) = ZP0002_STRUC-ENDDA6.
                                 ZPA30_002-ENDDA2(2) = ZP0002_STRUC-ENDDA4.
                                 ZPA30_002-ENDDA+4(4) = ZP0002_STRUC-ENDDA.
    ANREX                        Form of address text
                        Source:  ZP0002_STRUC-ANREX (Title)
                        Rule :   Transfer (MOVE)
                        Code:    ZPA30_002-ANREX = ZP0002_STRUC-ANREX.
    NACHN                        Last Name
                        Source:  ZP0002_STRUC-NACHN (Last Name)
                        Rule :   Transfer (MOVE)
                        Code:    ZPA30_002-NACHN = ZP0002_STRUC-NACHN.
    VORNA                        First Name
                        Source:  ZP0002_STRUC-VORNA (First Name)
                        Rule :   Transfer (MOVE)
                        Code:    ZPA30_002-VORNA = ZP0002_STRUC-VORNA.
    GESC2                        Gender key  -
    > how can i put MAle condition
                        Source:  ZP0002_STRUC-GESC2 (Female)
                        Rule :   Transfer (MOVE)
                        Code:    ZPA30_002-GESC2 = ZP0002_STRUC-GESC2.
    GBDAT                        Date of Birth
                        Source:  ZP0002_STRUC-GBDAT (Date of birth)
                        Rule :   Transfer (MOVE)
                        Code:    * Date Value as DDMMYYYY
                                 ZPA30_002-GBDAT0(2) = ZP0002_STRUC-GBDAT6.
                                 ZPA30_002-GBDAT2(2) = ZP0002_STRUC-GBDAT4.
                                 ZPA30_002-GBDAT+4(4) = ZP0002_STRUC-GBDAT.
    GBLND                        Country of Birth
                        Source:  ZP0002_STRUC-GBLND (Country of Birth)
                        Rule :   Transfer (MOVE)
                        Code:    * Leave date value in internal format (YYYYMMDD)
                                 ZPA30_002-GBLND = ZP0002_STRUC-GBLND.
    Caution: Source field is longer than target field
                         Code:    ZPA30_002-NATI2 = ZP0002_STRUC-NATI2.
    FATXT                        Marital Status
                         Source:  ZP0002_STRUC-FATXT (Marital Status)
                         Rule :   Transfer (MOVE)
                         Code:    ZPA30_002-FATXT = ZP0002_STRUC-FATXT.
    Note : however my SourceField if i click i can see both GESC1 & GESC2.
    Please help me in this regard
    Regards
    Syamla

    Hello,
    Male or female in 0002 is determined the field ANRED. (Mr. Ms.) based on this only the GESCH(Gender key is determined).
    So if a employee is a male fill ANRED with 1 else with 2.
    Thanks.
    Krishna

  • How to validate the Male or Female for infotype 002 in LSMW at FieldMapping

    Dear freinds,
               Small problem in LSMW for infotype 0002.
    Whiel recording for infotype 002  ihae done for an employee based on FeMale(GESC2) , no when i uploading data i am having for male (GESC1) ...how can i toggle in my
    Field mapping please can any body tell me
    My field mapping presenlty have is :
    __BEGIN_OF_RECORD__ Before Using Conversion Rules
                        Rule :   Default Settings
                        Code:    ZPA30_002 = INIT_ZPA30_002.
    TABNAME                      Table Name
                        Rule :   Default Settings
                        Code:    ZPA30_002-TABNAME = 'ZPA30_002'.
    TCODE                        Transaction Code
                        Rule :   Default Settings
                        Code:    ZPA30_002-TCODE = 'PA30'.
    PERNR                        Personnel Number
                        Source:  ZP0002_STRUC-PERNR (Personnel number)
                        Rule :   Transfer (MOVE)
                        Code:    ZPA30_002-PERNR = ZP0002_STRUC-PERNR.
    TIMR6                        Time period indicator: Period
                        Rule :   Constant
                        Code:    ZPA30_002-TIMR6 = 'X'.
    CHOIC                        Infotype selection for HR master data maintenance
                        Rule :   Constant
                        Code:    ZPA30_002-CHOIC = '0002'.
    BEGDA                        Start Date
                        Source:  ZP0002_STRUC-BEGDA (Start Date)
                        Rule :   Transfer (MOVE)
                        Code:    * Date Value as DDMMYYYY
                                 ZPA30_002-BEGDA0(2) = ZP0002_STRUC-BEGDA6.
                                 ZPA30_002-BEGDA2(2) = ZP0002_STRUC-BEGDA4.
    ENDDA                        End Date
                        Source:  ZP0002_STRUC-ENDDA (End Date)
                        Rule :   Transfer (MOVE)
                        Code:    * Date Value as DDMMYYYY
                                 ZPA30_002-ENDDA0(2) = ZP0002_STRUC-ENDDA6.
                                 ZPA30_002-ENDDA2(2) = ZP0002_STRUC-ENDDA4.
                                 ZPA30_002-ENDDA+4(4) = ZP0002_STRUC-ENDDA.
    ANREX                        Form of address text
                        Source:  ZP0002_STRUC-ANREX (Title)
                        Rule :   Transfer (MOVE)
                        Code:    ZPA30_002-ANREX = ZP0002_STRUC-ANREX.
    NACHN                        Last Name
                        Source:  ZP0002_STRUC-NACHN (Last Name)
                        Rule :   Transfer (MOVE)
                        Code:    ZPA30_002-NACHN = ZP0002_STRUC-NACHN.
    VORNA                        First Name
                        Source:  ZP0002_STRUC-VORNA (First Name)
                        Rule :   Transfer (MOVE)
                        Code:    ZPA30_002-VORNA = ZP0002_STRUC-VORNA.
    GESC2                        Gender key  -
    > how can i put MAle condition
                        Source:  ZP0002_STRUC-GESC2 (Female)
                        Rule :   Transfer (MOVE)
                        Code:    ZPA30_002-GESC2 = ZP0002_STRUC-GESC2.
    GBDAT                        Date of Birth
                        Source:  ZP0002_STRUC-GBDAT (Date of birth)
                        Rule :   Transfer (MOVE)
                        Code:    * Date Value as DDMMYYYY
                                 ZPA30_002-GBDAT0(2) = ZP0002_STRUC-GBDAT6.
                                 ZPA30_002-GBDAT2(2) = ZP0002_STRUC-GBDAT4.
                                 ZPA30_002-GBDAT+4(4) = ZP0002_STRUC-GBDAT.
    GBLND                        Country of Birth
                        Source:  ZP0002_STRUC-GBLND (Country of Birth)
                        Rule :   Transfer (MOVE)
                        Code:    * Leave date value in internal format (YYYYMMDD)
                                 ZPA30_002-GBLND = ZP0002_STRUC-GBLND.
    Caution: Source field is longer than target field
                         Code:    ZPA30_002-NATI2 = ZP0002_STRUC-NATI2.
    FATXT                        Marital Status
                         Source:  ZP0002_STRUC-FATXT (Marital Status)
                         Rule :   Transfer (MOVE)
                         Code:    ZPA30_002-FATXT = ZP0002_STRUC-FATXT.
    Note : however my SourceField if i click i can see both GESC1 & GESC2.
    Please can any one let me know .
    Regards
    Syamla

    Hello,
    Male or female in 0002 is determined the field ANRED. (Mr. Ms.) based on this only the GESCH(Gender key is determined).
    So if a employee is a male fill ANRED with 1 else with 2.
    Thanks.
    Krishna

  • HR-ABAP-want user exit for pa30  for creation 2001 infotype for sick leave

    Hi ALL,
             My requirement like, whenever I try to create a sick leave through PA30 Tcode for infotype 2001 then the has to be trigger like, if the personnel joing date will be from Feb-Dec any date of the year then, the SL will be valid for next year Jan.
    Ex; Todya I am creating SL on 2001 infotype. then the condition will
            If joining date not Jan 2007 then,
             Leave will be valid for next year Jan 2008.
    So, let me know is there any user exit for  this.
    Thanks In advance.
    J.P

    Find myself

  • Adding a custom field in a sap standard screen in pa30 for an infotype.

    Hi to all..
    i'm in a requirement to add a custom field in a standard screen of pa30. for the infotype 0442.
    I googled up.. but i was not getting proper solution for it.. can any one provide a solution for it..
    With regards.
    Aahbha.

    Hello Sirs,
    Step by step instructions on:
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/4f/d52552575e11d189270000e8322f96/frameset.htm
    The below thread provide more info on how to create an infotype from scratch, but this is just for the reference:
    add custom fields to standard infotype
    Regards,
    Bentow.

  • Fields missing in Screen 2000 for Infotype 580

    Hi,
    In PA30, when I go to create or change or display mode for an employee in infotype 580, there are only 4 fields shown. There should actually be over 10 fields in the screen. I checked the layout for the screen 2000 of program MP058000 in SE51 and it had all the fields there. In table T588M there was no entry with the module program name MP058000. I created an entry with this program for screen 2000, and chose the radio button Standard ( The first one) for all the fields that were there and still the screen in PA30 has only 4 fields.
    Can anyone please help with this issue?
    Additional Info: When i chose create or change for IT0580 in PA30 for an employee, there was a status message saying screen was modified, and that were i got the table name that i've mentioned above.
    Thanks & Regards,
    Pratheek Bhonsley

    Hi Pratheek,
    Please check the hiring date of employee to whom you are trying to enter and check the employee who joined before this financial year. If i am right, this info type screens are depends on hiring date of employee, if i am right..
    At the same time, Please check the control record period also.
    MVR
    Edited by: MVRmvr on Jul 19, 2010 7:43 AM

  • Disable Delete Button for infotype 2001 subtype 0025

    I want to Disable Delete Button for infotype 2001 subtype 0025 only in PA30/61.
    Is there any EXIT available

    Hi
    Try it .
    Somebody already given this type of answers.
    Pls first use Search then post.
    Well FYI,
    <b>There is a standard User Exit for PA30 / 40 for PBO and PAI events.
    ZXPADU01 for PBO and
    ZXPADU02 for PAI events.
    By writing proper code in here for the IT2001, you can write your rules.
    PBAS0001 ( PA: Pers.Admin./Recruitment: Default values and checks ),</b>
    Manoj Shakya.

  • Error in BDC for Infotype 0589

    Hi friends,
                     I have developed a BDC program for Infotype 0589.  After executing the program to upload data from file, I am getting error message: Field Q0589-ANZHL(7) input value is longer than screen field
    Here I am adding my  Sample code also.
    REPORT  ZTEST_0589.
    PARAMETERS :
      p_file TYPE rlgrap-filename.         " Accepts File Name
    *" Type declarations...................................................
    TYPES :
      BEGIN OF type_s_it0589,
        pernr   TYPE rp50g-pernr,          " Personnel Number
        inftyp  TYPE rp50g-choic,          " Infotype
        begda   TYPE p0589-begda,          " Begin Date
        endda   TYPE p0589-endda,          " End Date                                   
        lga01   TYPE q0589-lgart,           
        betrg01 TYPE q0589-betrg,         
        anzhl01 TYPE q0589-anzhl,         
        lga02   TYPE q0589-lgart,           
        betrg02 TYPE q0589-betrg,         
        anzhl02 TYPE q0589-anzhl,         
        lga03   TYPE q0589-lgart,           
        betrg03 TYPE q0589-betrg,         
        anzhl03 TYPE q0589-anzhl,         
        lga04   TYPE q0589-lgart,           
        betrg04 TYPE q0589-betrg,         
        anzhl04 TYPE q0589-anzhl,         
        lga05   TYPE q0589-lgart,           
        betrg05 TYPE q0589-betrg,         
        anzhl05 TYPE q0589-anzhl,        
        lga06   TYPE q0589-lgart,           
        betrg06 TYPE q0589-betrg,         
        anzhl06 TYPE q0589-anzhl,         
        lga07   TYPE q0589-lgart,           
        betrg07 TYPE q0589-betrg,         
        anzhl07 TYPE q0589-anzhl,         
        lga08   TYPE q0589-lgart,           
        betrg08 TYPE q0589-betrg,         
        anzhl08 TYPE q0589-anzhl,          
      END OF type_s_it0589.
    Work variables                                                   
    DATA:
      w_file      TYPE string,             " File Name
      w_betrg(50) TYPE c,                  " Proposed Contribution
      w_anzhl(50) TYPE c,                  " Actual Contribution
      w_count(2)  TYPE n,                  " Counter
      w_year(4)   TYPE n,                  " Year
      w_month(2)  TYPE n,                  " Month
      w_day(2)    TYPE n,                  " Day
      w_date(10)  TYPE c,                  " Date
      w_wage(50)   TYPE c,                  " wage
      w_waget(50)   TYPE c,                 " wage type
      w_curr(12)  TYPE c,                  " Currency
      w_tabrows LIKE sy-srows VALUE 7,     " Table Control rows
      w_update TYPE i,                     " Number of Updated Records
      w_failed TYPE i,                     " Number of Failed Records
      w_0589_lines TYPE i,                 " Number of Records in File
      w_text TYPE string.                  " CheckBox for considering
    " Actual Contributions
    Structure to hold File Data                                         *
    DATA :
      fs_it0589 TYPE type_s_it0589.
    Structure to hold Batch input: New table field structure            *
    DATA :
    fs_bdcdata TYPE bdcdata.
    Structure to hold Messages in the SAP System                        *
    DATA :
      fs_messages TYPE bdcmsgcoll.
    Structure to hold Personnel Number, Message Type & Message Text     *
    DATA:
      BEGIN OF fs_log,
        pernr   TYPE rp50g-pernr,
        msgtxt(200) TYPE c,
        msgtyp TYPE c,
      END OF fs_log.
    Structure to hold Parameter string for runtime of CALL TRANSACTION  *
    DATA :
      fs_opt TYPE ctu_params.
    Internal Table to hold File Data                                    *
    DATA :
      t_it0589 LIKE
      STANDARD TABLE
            OF fs_it0589.
    Internal Table to hold Batch input: New table field structure       *
    DATA :
      t_bdcdata TYPE
       STANDARD TABLE
             OF bdcdata.
    Internal Table to hold Messages in the SAP System                   *
    DATA:
      t_messages TYPE TABLE OF bdcmsgcoll.
    Internal Table to hold Personnel Number, Message Type & Message Text*
    DATA:
       t_log LIKE
    STANDARD TABLE
          OF fs_log.
    FORM validate .
      IF p_file IS INITIAL.
        MESSAGE e005(zvalid).
      ENDIF.                               " IF P_FILE IS INITIAL.
      MOVE p_file TO w_file.
      CALL FUNCTION 'GUI_UPLOAD'
        EXPORTING
          filename                = w_file
          filetype                = 'ASC'
          has_field_separator     = 'X'
          dat_mode                = 'X'
        TABLES
          data_tab                = t_it0589
        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 NE 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
           WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
      IF t_it0589 IS INITIAL.
        MESSAGE e006(zvalid).
      ENDIF.                               " IF T_IT0589 IS INITIAL
    ENDFORM.                               " FORM VALIDATE
    FORM f4_help .
      CALL FUNCTION 'F4_FILENAME'
        IMPORTING
          file_name = p_file.
    ENDFORM.                               " FORM F4_HELP
    *&      Form  FILL_BDCDATA
    FORM fill_bdcdata .
      DESCRIBE TABLE t_it0589 LINES w_0589_lines.
      LOOP AT t_it0589 INTO fs_it0589.
        REFRESH t_bdcdata.
        REFRESH t_messages.
        PERFORM bdc_dynpro USING 'SAPMP50A' '1000'.
        PERFORM bdc_field USING 'RP50G-PERNR'
                                fs_it0589-pernr.
        w_year = fs_it0589-begda+0(4).
        w_month = fs_it0589-begda+4(2).
        w_day = fs_it0589-begda+6(2).
        CONCATENATE w_day w_month w_year INTO w_date
                                 SEPARATED BY '.'.
        PERFORM bdc_field USING 'RP50G-BEGDA'
                                w_date.
        w_year = fs_it0589-endda+0(4).
        w_month = fs_it0589-endda+4(2).
        w_day = fs_it0589-endda+6(2).
        CONCATENATE w_day w_month w_year INTO w_date
                                 SEPARATED BY '.'.
        PERFORM bdc_field USING 'RP50G-ENDDA'
                                w_date.
        PERFORM bdc_field USING 'RP50G-CHOIC'
                                fs_it0589-inftyp.
        PERFORM bdc_field USING 'BDC_OKCODE'
                                '/00'.
        PERFORM bdc_dynpro USING 'SAPMP50A' '1000'.
        PERFORM bdc_field USING 'BDC_OKCODE'
                                '=INS'.
        PERFORM bdc_dynpro USING 'MP058900' '2000'.
    1st Row...............................................................
        ADD 1 TO w_count.
        MOVE fs_it0589-lga01 TO w_wage.
        PERFORM bdc_field USING 'Q0589-LGART(01)'
                                w_wage.
        MOVE fs_it0589-betrg01 TO w_curr.
        PERFORM bdc_field USING 'Q0589-BETRG(01)'
                                w_curr.
        MOVE fs_it0589-anzhl01 TO w_curr.
        PERFORM bdc_field USING 'Q0589-ANZHL(01)'
                                w_curr.
    2nd Row...............................................................
    3rd Row...............................................................
    4th Row...............................................................
    5th Row...............................................................
    6th Row...............................................................
        ADD 1 TO w_count.
        IF w_count > w_tabrows .
          w_count = 1.
          PERFORM bdc_field USING 'BDC_OKCODE'
                                  'P+' .
          PERFORM bdc_dynpro USING 'MP058900' '2000'.
        ENDIF.                             " IF W_COUNT > W_TABROWS
        MOVE fs_it0589-lga06 TO w_curr.
        CONCATENATE 'Q0589-LGART(' w_count ')' INTO w_wage.
        PERFORM bdc_field USING w_wage
                                w_curr.
        MOVE fs_it0589-betrg06 TO w_curr.
        CONCATENATE 'Q0589-BETRG(' w_count ')' INTO w_betrg.
        PERFORM bdc_field USING w_betrg
                                w_curr.
        MOVE fs_it0589-anzhl06 TO w_curr.
        CONCATENATE 'Q0589-ANZHL(' w_count ')' INTO w_anzhl.
        PERFORM bdc_field USING w_anzhl
                                w_curr.
    7th Row...............................................................
        ADD 1 TO w_count.
        IF w_count > w_tabrows .
          w_count = 1.
          PERFORM bdc_field USING 'BDC_OKCODE'
                                  'P+' .
          PERFORM bdc_dynpro USING 'MP058900' '2000'.
        ENDIF.                             " IF W_COUNT > W_TABROWS
        MOVE fs_it0589-lga07 TO w_curr.
        CONCATENATE 'Q0589-LGART(' w_count ')' INTO w_wage.
        PERFORM bdc_field USING w_wage
                                w_curr.
        MOVE fs_it0589-betrg07 TO w_curr.
        CONCATENATE 'Q0589-BETRG(' w_count ')' INTO w_betrg.
        PERFORM bdc_field USING w_betrg
                                w_curr.
        MOVE fs_it0589-anzhl07 TO w_curr.
        CONCATENATE 'Q0589-ANZHL(' w_count ')' INTO w_anzhl.
        PERFORM bdc_field USING w_anzhl
                                w_curr.
    *- -- Same upto 15 rows.......
    Save..................................................................
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                       '=UPD'.
    Back..................................................................
        PERFORM bdc_dynpro USING 'MP058900' '2000'.
        PERFORM bdc_field  USING 'BDC_OKCODE'
                                 '/EBCK'.
        w_count = 0.
        CALL TRANSACTION 'PA30'  USING t_bdcdata
                               OPTIONS FROM fs_opt
                              MESSAGES INTO t_messages.
        LOOP AT t_messages INTO fs_messages.
          CALL FUNCTION 'FORMAT_MESSAGE'
            EXPORTING
              id        = fs_messages-msgid
              lang      = sy-langu
              no        = fs_messages-msgnr
              v1        = fs_messages-msgv1
              v2        = fs_messages-msgv2
              v3        = fs_messages-msgv3
              v4        = fs_messages-msgv4
            IMPORTING
              msg       = fs_log-msgtxt
            EXCEPTIONS
              not_found = 1
              OTHERS    = 2.
          IF sy-subrc NE 0.
            MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                  WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
          ENDIF.                           " IF SY-SUBRC NE 0
          MOVE fs_it0589-pernr TO fs_log-pernr.
          MOVE fs_messages-msgtyp TO fs_log-msgtyp.
          APPEND fs_log TO t_log.
          CLEAR fs_log.
          IF fs_messages-msgtyp EQ 'S'
         AND fs_messages-msgnr  EQ '102'.
            ADD 1 TO w_update.
          ELSEIF fs_messages-msgtyp EQ 'S'
             AND fs_messages-msgnr  EQ '015'
              OR fs_messages-msgtyp EQ 'E'.
            ADD 1 TO w_failed.
          ENDIF.                           " IF FS_MESSAGES-MSGTYP EQ 'S'
        ENDLOOP.                           " LOOP AT T_MESSAGES
      ENDLOOP.                             " LOOP AT T_IT0585
      WRITE :/ 'Number of Records Fetched from file'(001),
             50   w_0589_lines COLOR 1,
             / 'Number of Records Updated into the database'(002),
             50    w_update COLOR 1,
             / 'Number of Records Failed to update into database'(003),
             50   w_failed COLOR 6 .
      SKIP 3.
      WRITE :/ 'Detailed Log.....'(004).
      SKIP 1.
      LOOP AT t_log INTO fs_log.
        AT NEW pernr.
          WRITE :/  fs_log-pernr COLOR 1.
        ENDAT.                             " AT NEW PERNR
        IF fs_log-msgtyp = 'E'.
          WRITE :15  fs_log-msgtxt COLOR 6 INVERSE ON.
        ELSE.
          WRITE :15  fs_log-msgtxt.
        ENDIF.                             " IF FS_LOG-MSGTYP = 'E'
      ENDLOOP.                             " LOOP AT T_LOG INTO FS_LOG
    ENDFORM.                               " FORM FILL_BDCDATA
    *&      Form  BDC_DYNPRO
    This subroutine starts new screen                                    *
    There are no interface parameters to be passed to this subroutine.  *
    FORM bdc_dynpro USING program dynpro.
      CLEAR fs_bdcdata.
      fs_bdcdata-program  = program.
      fs_bdcdata-dynpro   = dynpro.
      fs_bdcdata-dynbegin = 'X'.
      APPEND fs_bdcdata TO t_bdcdata.
    ENDFORM.                               " FORM BDC_DYNPRO
    *&      Form  BDC_FIELD
    This subroutine inserts field                                        *
    There are no interface parameters to be passed to this subroutine.  *
    FORM bdc_field USING fnam fval.
      CLEAR fs_bdcdata.
      fs_bdcdata-fnam = fnam.
      fs_bdcdata-fval = fval.
      APPEND fs_bdcdata TO t_bdcdata.
    ENDFORM.                               " FORM BDC_FIELD
    Thanks,
    Ziad khan

    Hi Amit,
               Thaks for reply. Amit, I am new to ABAP-HR so i dont know how to use FM "HR_MAINTAIN_MASTERDATA".
    Can u please explain in detail.
    Thanks
    Ziad

  • IDOC HRMD_A for Infotype 0002 (Personal Data)

    Hello,
    I'm trying to send the modifications that I make in a person in the transaction PA30 in the table PA0002 automaticly. But when I go to thew program "RBDMIDOC" and select the message type "HRMD_A" (HR: Plan data and HR master data) it says that it doesn't have anything to send. But when I modify a Object (o, c, s), and I execute the program it send information. The object(o,c,s) has sent correctly. But when I want to send the Personal Data (P), it doesn't send anything. I have the trigger activated.
    Have I selected the message type correctly?
    PM

    updating id for malasian employee is not working.
    Q0002-perid. it come only for malasian employee.
    screen no 2044
    Use transaction PA30,
    Enter infotype number 2 or select Personal Data (0002) on the Personal Data tab
    You can use any Malaysian employee #
    Click on change button
    Enter in an ID number.  (There is no validation on ID number field.)
    Click either the enter or save button.  The ID number disappears and a message says ‘No change found’.

  • Authorization for Infotype 0008

    Dear Experts,
    I am new for SAP HR module, and I am facing one authorization issue.
    It is about the PA30 authorization for Infotype 0008, I want to restrict user ( ext_test) who can change Infotype 0008 for person ID 44000156, Employee group 1, Employee subgroup EP(ETXAT).
    And I create the role for T-code PA30.
    In the P_ORGINCON object, I configure the activity as following :
    Authorization level            E, R, S                                                                      AUTHC
    Infotype                           0008                                                                          INFTY
    Personnel Area                *                                                                               PERSA
    Employee Group              1                                                                               PERSG
    Employee Subgroup         EP                                                                            PERSK
    Authorization Profile         *                                                                               PROFL
    Subtype                          ' ', 0                                                                          SUBTY
    Organizational Key          *                                                                               VDSK1
    But when I execute PA30 with person ID 44000156, and want to change Infotype 0008, It shows that I miss the authorization.
    The result of SU53 are
    Authorization level            E
    Infotype                           0008   
    Personnel Area                *
    Employee Group              *
    Employee Subgroup         *
    Authorization Profile         *
    Subtype                          0
    Organizational Key          *
    I don't know why it asks the * authorization for Employee group and subgroup even I want to chagne the data which are fit my created authorizations.
    Could anyone give me some advice?

    Dear Amamath,
    Employee group is 1 (Direct), and subgroup is EP ( Expat).
    I don't know if it is possible if I want to restrict the authority as following:
    I have two person ID, one is 44000156, the other is 44000246.
    44000156 has Employee group 1(Direct) and subgroup EP(Expat)
    44000246 has Employee group 2(Indirect) and subgroup 3(Management)
    I want to restrict the authority that end user can only change Infotype 0008 for the person which subgroup is EP ( No matter the Employee group is 1,2, or 3).That is , in this case, I can only change 44000156 basic pay but not 44000246.
    So in the P_ORGINCON object, I restrict the Authorization level as "E,M,and R); Infotype as "0008"; and subgroup as "EP".
    After that , I did the test with end user's accout. then SU53 shows that it need to have Employee subgroup = "*".
    I don't know why it need the * authority for Employee subgroup. I should be able to change 44000156 since I granted the subgroup "EP" to end user account.

  • Adding fields in pa30 for IT 170

    hi
    i have added some custom  fields for infotype 170 in se11.now i want to see those fields in pa30 for that infotype 170(when i use it for a pernr in the display screen). how can i do that.
    any help in this regard wud be appreciated.
    thanks

    Hello Alan,
    Following are the steps from this Enhancement in infotype 0006
    Go to Tcode PM01, select the third tab frm left ie. enhance infotypes. Select CI include and press Create.
    Enter all the fields you want over here and then activate . Then come out and then select the module pool option there u get a bunch of includes
    INCLUDE ZP000610.(Global Data)
    INCLUDE MPPDAT00.
    INCLUDE FP50PPSB.
    INCLUDE MPPERS00.
    INCLUDE ZP000620.(PBO module)
    INCLUDE ZP000630.(PAI module)
    INCLUDE ZP000640.(form routines)
    You put in the code in the zp includes, activate come out and then select the third option in the check box ie.include screen.Customize the screen then after u come out there is a assign enhancement button on top, there u need to assign the program name like zp000600 and screen 0200 to the standard one.
    Regards,
    Ahmad

  • Problem in updating Data for infotype P0009 through BADI

    Hi,
    we are facing a problem while trying to update value of Date field for infotype P0009 through PA30.
    we have tried to update by using BADI hrpad00infty, we are providing value in new_innnn structure of method
    AFTER_INPUT, but the value is not getting updated for that PARNR.
    Can anyone help me regarding the same?

    Hi
    HRPAD00INFTY BADI methods don't allow to modify any values of the current record being processed, but there's a possible wworkaround accessing memory fields using field-symbols:
    method IF_EX_HRPAD00INFTY~AFTER_INPUT.
      FIELD-SYMBOLS: <fs> type p0009.
      assign ('(MP000900)P0009') TO <FS>.
    if sy-subrc eq 0. 
      <FS>-YOURFIELD = YOUR_VALUE.
    endif.
    endmethod.

  • Regarding lsmw and spefic infotype fields

    hi , experts
    i want to upload reimbursement amount in sap through lsmw so for this first we should prepare format in excel right
    so in excel which fields we will maintain and how we will prepare
    suppose this amount upload in 0015 info type so give me advice and once u can test in ides then tell me the process
    as same in implementation stage master data should be upload in sap so for this now i want to give the formats for all info types to users then only they will prepare the master data in excel
    after completion of the configuration we will upload the employee master data into sap
    thanks in advance..

    Hi Nethi,
    For uploading 0015 infotype, generally we give Wagetype, Amount/Number, Date of Origin.
    It purely depends on your requirement again.
    Once your upload is successful in IDES, then export LSMW to local system. And import the same in Production.
    Pradeep.

  • Maintaining / Displaying Text for Infotype record

    Hi,
    How do we maintain infotype text for the record. Or how to display the text maintained for infotype record (I used PA20/PA30 for IT0001 record but could not locate infotype text).
    Regards,
    Avinash Josalkar.

    Hi,
    If you want to know the text of a infotype then goto the table
    V_T582A.
    eg:0000  actions
    0001 organisation assignment.
    But if you want to change the standard text of a infotype then you need to have access key to change.
    But if you are asking the text table for the fields in 0001.
    then goto se11
    enter Pa0001--dislay
    click the tab entry help/check then you can see the table names in the column check table for each field.

  • Any BAPI for Infotype 0015(Additional Data)

    Hi,
    Can anyone provide information on BAPI for Infotypes 0015(Additional Data).
    Your help will be appreciated !!!
    Vijayanand.

    To upload data into infotype 0015
    Use HR_INFOTYPE_OPERATION to create your a wrapper BAPI. You would also have to use BAPI_EMPLOYEE_ENQUEUE and BAPI_EMPLOYEE_DEQUEUE for locking and unlocking of the record in your BAPI or program.
    Enqueue personnel number
    call function 'BAPI_EMPLOYEE_ENQUEUE'
    create 0015
    call function 'HR_INFOTYPE_OPERATION'
    Use FM :  HR_MAINTAIN_MASTERDATA to update IT 0015
    check bapi : BAPI_HRMASTER_SAVE_REPL_MULT
    Dequeue personnel number
    call function 'BAPI_EMPLOYEE_DEQUEUE'
    You could also use LSMW Tool to upload the data.
    Regards
    Vasu

Maybe you are looking for