Update IBAN for Infotype 0009

Hi,
I have to upload data in IT0009 including IBAN.  As per the requirement I have to update IBAN first and then upload the record in IT0009.
I have to update IBAN against Country,Bank Account, Bank Key, Control Key.
I have used the following function modules to update IBAN.
1.  HRCA_PAYMENT_CHECK (Validate the Bank Account)
2.  CONVERT_BANK_ACCOUNT_2_IBAN (Generate IBAN number)
3.  Here I have used list of function module to update IBAN in table TIBAN but didnot work.
         MAINTAIN_IBAN
     (ii)   MAINTAIN_IBAN_FROM_DATA
     (iii)  BAPI_IBAN_CREATE
Later I found that standard IT0009 update IBAN with FM HR_UPDATE_IBAN.
CALL FUNCTION HR_UPDATE_IBAN
          EXPORTING
            iban      = iban
          CHANGING
            container = act_container_if.
If I want to use this FM then i have to instantiate "act_container_if".
Can anybody help me how to use this FM HR_UPDATE_IBAN.
PS : I dont want to update IBAN through Infotype 0009 screen.  I have to update it programatically before IT0009 LSMW run.
Thanking you in advance,
Ankit Gupta

Hello Ankit,
I am not understanding the ur requirement.
If u have update IBAN in IT0009 before actually puttin in other data . Its easy to write a code.
U can use HR_INFTYPE_OPERATION with INS as parameter.
I hope it helps. Incase you are talking abt the IBAN switch u can go the su01 go to parameters  and activate the switch HR_ADMIN_IBAN parameter ID.
Thanks and Regards,
Tarun Mishra

Similar Messages

  • Recording IBAN Code - infotype 0009

    Hi all,
    I want to record on infotype 0009 the IBAN code with LSMW or Batch Input.
    The problem is that on line, to get the IBAN, we have to click on a button that shows in another screen the code, and then you can save.
    In batchInput mode, when i try to click on button, it is disabled.
    Do somebody found a way to do a massive recording of infotype 0009 with the IBAN?
    (if it's possible without change standard SAP)
    Thanks a lot.
    Massi.

    Hello Ankit,
    I am not understanding the ur requirement.
    If u have update IBAN in IT0009 before actually puttin in other data . Its easy to write a code.
    U can use HR_INFTYPE_OPERATION with INS as parameter.
    I hope it helps. Incase you are talking abt the IBAN switch u can go the su01 go to parameters  and activate the switch HR_ADMIN_IBAN parameter ID.
    Thanks and Regards,
    Tarun Mishra

  • How can I remove PERNR Check for Infotype 0009 on a new-hire create

    We have contractors working for our H.R. department setting up new-hire employees.  The workflow in PA40 includes setting up default Infotype 0009 banking information to paycheck.  The PERNR check in the workflow fails because the HR Contractor does not have an Employee Record in HCM (PERNR), therefore, it bypasses setting up the 0009 Banking Information Default.
    How can we change this work-flow so that an H.R. Contractor can setup a new hire employee with infotype 0009 banking information default?

    '''Hello peacefultrev,'''
    I believe from your question you wish to remove the window title-bar, while keeping the menu bar available.
    I have two solutions for you to try. One requires no plugin and the other requires the installation of a plugin.
    '''No plugin option:'''
    This option hides the the window title while also removing the menu bar. The menu bar can then be reactivated and viewed simply by pressing "Alt" which shows the menu bar until you click away from it. To do this:
    # Right click on the tab bar and disable "Menu Bar".
    # Whenever you which to use the menu bar, tap "Alt" on your keyboard.
    # When you click away from the menu bar the windows title will disappear until you tap "Alt" again.
    '''Plugin Option:'''
    You can download this plugin called [https://addons.mozilla.org/en-US/firefox/addon/hide-caption-titlebar-plus-sma/ Hide Caption Titlebar Plus] which can be customized to suit your needs. I cannot provide support on this plugin as I have not used it myself.
    I hope one of these solutions will suit your needs.
    Mattlem

  • 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.

  • Ess wda: updating Iban for insert/copy/modify in bank detail screen for germany

    Hi,
    We are using standard detail screen HRESS_CC_PER_DTL_BANK_DE for Germany, We have observed that even if the user changes/updates/creates the new record without filling Iban field system will not throw any error which is correct as per V_T588MFPROPC as we have not made it mandatory. but we have an option to populate Iban using specific button in PA30, can we have the same functionality in ESS? Can we implement HRPAD00INFTYDB for this purpose? Is there any other option for this functionality?
    Thank you,
    Krishna kishore T.

    I can solve this issue implementing the BAdI HRPAD00INFTYDB
    Summary of configuration options in ESS Personal Information scenario
    Regards

  • Override default values for infotype 0009 (Bank Details)

    Dear all,
    When we create a new bank details, default value will populate.
    I would like to know how to override these value, dynamic action? User exist? Feature? Or something else?
    Thanks in advance
    Regards
    Bill

    Hi Sikindar,
    Thanks for the reply, am trying to understand the options available.
    It look like the current behavior is: INITS + RUFNM
    and the user want to change it into: INITS only
    And it should only apply to country group 28
    Regards
    Bill

  • Adding field in infotype 0009

    Hi,
    I have a requirement where in i have to add a filed in the infotype 0009.
    For this i have added the field in the structure ps0009 through append structure. But i have to get the filed in the sceen. Please let me know how to do this.
    I have gone to PM01 transaction and for infotype 0009 went into module pool option button and clicked on create screen then its asking for the access key as this is the standard infotype. But i dont know how many screens are related to this infotype as the access key for all the screens is different. I took access for 2 screens but not sure how many screens are there.
    Please advice how to proceed.
    Thanks,
    Raju

    Hi raja,
    1. The screen numbers starting with 2
      are the ones which will show the data for entry purpose.
    2. So while doing pa30, check the exact screen number,
      which comes in your case (this is country dependent / customizing dependent)
    3. Then accordingly u can enhance those screen.
    regards,
    amit m.

  • Adding a field in infotype 0009

    Hi,
    I have a requirement where in i have to add a filed in the infotype 0009.
    For this i have added the field in the structure ps0009 through append structure. But i have to get the filed in the sceen. Please let me know how to do this.
    I have gone to PM01 transaction and for infotype 0009 went into module pool option button and clicked on create screen then its asking for the access key as this is the standard infotype. But i dont know how many screens are related to this infotype as the access key for all the screens is different. I took access for 2 screens but not sure how many screens are there.
    Please advice how to proceed.
    Thanks,
    Raju

    Hi raja,
    1. The screen numbers starting with 2
      are the ones which will show the data for entry purpose.
    2. So while doing pa30, check the exact screen number,
      which comes in your case (this is country dependent / customizing dependent)
    3. Then accordingly u can enhance those screen.
    regards,
    amit m.

  • New field in Infotype 0009- to update IFSC Code- SAP Note Required

    Dear consultants,
    One of my client want to maintain their employees IFSC code in the Infotype 0009, where one new field required for this to update IFSC number.
    Which SAP note can fulfill this requirement, please do needful.
    Thanks & Regards,
    Navesh

    Dear Supriya,
    Thanks for quick responce, It is helpful. pelase do needful on below issue.
    http://scn.sap.com/thread/3517340
    Regards,
    Navesh

  • Error while updating HRA in infotype 581 for the employees.

    Hi,
    System is showing an error while updating HRA in infotype 581 for the employees.
    The error is No Automatic updation for IT0008. Allowance Grouping not found.
    What is this error. Please advice what to do in this case.

    Hi Deepthi,
    Check Table V_T7INA5,V_T7INA1,V_T7INA3 and V_T7INA9 also.
    Check it,
    Regards,
    Vinod.
    Edited by: vinod rao on Jul 30, 2008 1:23 PM

  • IBAN in Infoype 0009

    Dear All,
    I have actived the IBAN in T77SO( ADMIN, IBAN) and IBAN is icon is displyaing in infotype 0009 properly.
    but its not proposing the IBAN for employees please let me know where am mising this out.
    Thanks and Regards,
    Anoop

    Hi Anoop,
    For this, refer to the sap note 1266571.
    In order to actually use the IBAN/SEPA-format in HCM please start report RPU_FILL_IBAN.
    This report converts all existing entries from table TIBAN into the corresponding database tables (infotypes, views) that make use of an IBAN. Additionally, it sets switch ADMIN/IBAN from table T77S0 value 'S'. If you did not use table TIBAN before only switch ADMIN/IBAN is set to 'S'.
    Caution: Report RPU_FILL_IBAN is a technical report only: no business-specific checks are performed and no database record gets locked against an update from any application program.
    For that reason it is recommended to run the report only in case you can ensure no user works with HR master data.
    Please read the report´s documentation before starting it in your production system.
    The following objects were adjusted to make use of an IBAN:
    International functionality and country specific functionalities of infotype 0009 (Bank Details, modulepool MP000900)
    International functionality and country specific functionalities of infotype 0011 (External Transfers, modulepool MP001100)
    International functionality and country specific functionalities of infotype 0057 (Membership Fees, modulepool MP005700)
    Class CL_HRPAD_BANK_DATA
    Class CL_HRPAD00_IBAN
    Query /SAPQUERY/H2BANK_DETAILS and infoset /SAPQUERY/HR_ADM
    Report RPLBNK00
    Fast entry screen for Hiring (report RPFEFA0000101__0001)
    The following BAPIs were adapted:
    BAPI_BANKDETAILCREATESUCCESSOR
    BAPI_BANKDETAILGETDETAILEDLIST
    BAPI_BANKDETAIL_CHANGE
    BAPI_BANKDETAIL_CREATE
    BAPI_BANKDETAIL_GETDETAIL
    BAPI_BANKDETAIL_REQUEST
    Business Object type BANKDETAIL
    Table T521B and the corresponding view V_T521B
    A new field IBAN has been inserted in infotypes 0009 ("Bank Details"), 0011 ("External Transfers") and 0057 ("Membership Fees"). In order to distribute field IBAN via ALE, please refer to attached note 105148.
    Thanks & REgards, Swapnil Mishra

  • Posting HR Text for Infotype 2004

    Hello Friends,
    I am using RP-EXP-C1-TX to write text for Infotype 2004(Availability) and then updating it using below Routine:
    IF sy-subrc = 0.
    PERFORM prepare_update(sapfp50p) USING 'V'.
    COMMIT WORK and WAIT UP TO 3 SECONDS.
    ENDIF.
    My issue is that the text is getting updated properly but it is quite intermittent, meaning it posts sometimes and sometimes not. When I run it in debugging mode and execute each statement in PREPARE_UPDATE, it updates the text properly. But when I run it all at once, it updates at its own mood. I assume there is no issue with the code as it creates text many a times.
    I have given a WAIT of 3 seconds also after the PREPARE_UPDATE call which has already made it very slow. The fact that through PA61 everything gets updated pretty quickly,  makes me worry even more.
    Please let me know what should I do or if I am missing something somewhere. Or this can be a system/Database issue? I am afraid if I move this to Production assuming that it is a system issue and it does not work there either.
    Any help would be appreciated and rewarded.
    Thanks.

    Resolved myself

  • Error : 'No object identification permitted for infotype 0582, subtype LTA'

    Hi Experts,
                   While executing the program 'HINUINFO_UPDATE'
    i am getting an error 'No object identification permitted for infotype 0582, subtype LTA'.
                   After the approval for LTA claim  is done in ESS i have executed the program 'HINUINFO_UPDATE' to update he infotypes 15 and 582. Infotype 15 is getting created but while creating the infotype 582 system gives the above error message.
                 In the detailed error log system gives the following message.
                    "You attempted to access a data record with the object identification 1. However, according to the Customizing settings, object identifications cannot be used for subtype LTA of infotype 0582".
            Can anybody please assist me how to solve this problem. Helpful answers will be rewarded.
    Thanks and Best Regards,
    Sanoj.

    Hi ,
    Did any one find solution for this ? Please reply how to fix this issue.

  • 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

  • Additional field in infotype 0009 issue ( PBO and PAI )

    Hi Guru,
    I need your help please.
    I have a additional field in IT0009 and when I want created a new infotype 0009, I fill all field but after ENTER or SAVE all field are save in the layout but not the additional field.
    To save the additional field in the layout, I must fill it again and after the ENTER or SAVE the field is save in the layout.
    I have checked in the debbugger, when I create a new infotype 0009 it goes to the PBO but after ENTER or SAVE it doesn't go to the PAI so I must do it again ( fill the additional field and ENTER or SAVE ) and then it goes to the PAI.
    Thus I would like to know how I can make so that after the ENTER or SAVE the screen goes in PAI before the PBO and at the first time.
    Thanks very much in advance.
    Regards.

    Hi Srini Vas, hi Pedro Guarita and thanks for your reply,
    After more investigation, the probleme come from a check over country bank.
    In fact, the screen of the infotype 0009 must be adpated following the country bank but to do this, the standard module pool (mp000900) check if the country bank have changed.
    call method cl_hrpad00_iban=>process_iban_pai
          changing
            cs_bankdata = ls_bank_data_current
          exceptions
            error_iban  = 1
            others      = 2.
        if sy-subrc <> 0.
          message id sy-msgid type sy-msgty number sy-msgno
                     with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        endif.
        call method cl_hrpad00_iban=>get_bank_data_old
          importing
            bank_data_old = ls_bank_data_old.
        if ls_bank_data_current-banks <> ls_bank_data_old-banks. "MELN1357200
    bank country changed -> leave screen needs to be done
          leave_screen = 'X'.
        endif.
    But when you create a new infotype 0009, the ls_bank_data_old-banks is always initial. So when module pool compared the ls_bank_data_old-banks with the ls_bank_data_current-banks, those are always different.
    In conclusion, when you create a new infotype 0009 it is always mandatory to push ENTER before to fill any additional field because at each first time that the standard module pool go in the PAI, it make a leave screen.
    Thanks in advance for all yours reply.

Maybe you are looking for