Updating infotype 1018 automatically

Is it possible to update automatically infotype 1018 for position after creating a record on employee's infotype 0027?

it will not update IT1018 but if you maintain IT 27 then while posting to FI system will take the cost element from IT27.
the value of IT27 will overwrite the value of IT1018 while posting to FI.
It is bettter to maintain either one place.

Similar Messages

  • Class to update infotype

    Hi friends,
    Can you please give the details of class(not HR_INFOTYPE_OPERATION) for updating infotypes?
    Thanks in advance,
    Anu

    Hi Anu,
    If "Class " mentioned by you related to time constrins,
    A time constraint indicates whether more than one infotype record may be available at one time. The following time constraint indicators are permissible:
    1: An infotype record must be available at all times. This record may have no time gaps. You may not delete the record last stored on the database because all records of this infotype would otherwise be deleted.
    2: Only one record may be available at one time, but time gaps are permitted.
    3: Any number of records may be valid at one time, and time gaps are permitted.
    Other possible time constraint indicators are as follows:
    A: Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible.
    View V_T582B Infotypes Which are Created Automically controls whether the system automatically creates the infotype record for an employee hiring or an applicant data entry action.
    Infotypes with time constraint A may not be deleted.
    B: Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible.
    Infotypes with time constraint B may be deleted.
    T: The time constraint varies depending on the subtype.
    Z: Refers to time management infotypes. The time constraint for these infotypes depends on the time constraint class defined in view V_T554S_I Absence: General Control. Collision checks are defined in view V_T554Y Time Constraint Reaction.

  • Hi, I'd like to set alarms or reminders on my I phone or I pad so that it can update or sync automatically with each other. I don't know if this is possible or how to do it. I hope you can help..

    Hi, I'd like to set alarms or reminders on my I phone or I pad so that it can update or sync automatically with each other. I don't know if this is possible or how to do it. I hope you can help.

    HI, if I did this, then I believe that I cloud would then hold my info which I don't want. Is that the case? The reason is that I'm an old git, therefore used to not giving out info. Would I be right?
    Thank-You so much for taking the time to answer.
    John.

  • Why can I not disable the guest user in the 10.8.2 update? I have never enabled the guest user, but after the update, it was automatically enabled with a "managed" tag. It is not selectable even after entering my admin password to unlock the options.

    Why can I not disable the guest user in the 10.8.2 update? I have never enabled the guest user, but after the update, it was automatically enabled with a "managed" tag. It is not selectable even after entering my admin password to unlock the options. I was able to select the account under "parental controls", but again, could not delete it. Why Apple? Why?!!????

    SOLVED Ok. I actually was able to disable it. I had to actually log in as the guest user to make it accessible in the preference window. Then I disabled it and logged out. Apologies if this was obvious for some people, but I have had some sort of issue with something every update since Snow Leopard.

  • How to update transaction data automatically into MySQL database using PI

    Dear All,
    With reference to subject matter I want a sincere advice regarding how to update transaction data automatically into MySQL database using PI. Is there any link available where I can get step-by-step process.
    Ex: I have a MYSQL database in my organization. Whenever a delivery created in SAP some fields like DO Number, DO quantity, SO/STO number should get updated in MYSQL database automatically.
    This scenario is related to updation of transactional data into MYSQL DB and I want your suggestions pertaining to same issue.
    Thanks and Regards,
    Chandra Sekhar

    Hi .
    Develop a sceanrio between SAP to Database system,When the data updates in SAP Tables read the data and update it in DATA Base using JDBC adapter,but there will be some delay in updating data in MySQL.
    serach in sdn for IDOC-TOJDBC sceannario,many documents available for the same.
    Regards,
    Raja Sekhar

  • HR-ABAP Any BAPI or Function module to update infotypes 167 & 170

    Hi,
        Can anyone let me know is there any BAPI or Function module to update infotypes 167(Health Plans) & 170(Flexible Spending Accounts).
    Thanks,
    Sandeep

    Hi,
       U can use HR_BEN_CREATE_PLANS internally it calls HR infotype operation as specified by suresh.
    Suresh  : If there are approximately 3000 records to be updated on regular basis do u think is it better to use BAPI's or BDC
    regards
    Vick

  • Need a help to Update Infotype.....

    Hi Experts,
    *am developing HR-ABAP Report inthat, i have data in 2 internal tables, through these (itabs) i want to*
    *insert the data into 2 Ztables(Respective tables) and then i want to Update one Custom Infotype.*
    how can i procedure for this? is there any FM to update Infotype....
    Thanks in Advance,
    sudeer.

    The best way is to use HR_INFOTYPE_OPERATION function module in your program.
    Sample code:
          call function 'HR_INFOTYPE_OPERATION'
            exporting
              infty         = p0082-infty
              number        = p0082-pernr
              subtype       = p0082-subty
              validityend   = p0082-endda
              validitybegin = p0082-begda
              record        = p0082
              operation     = 'INS'
              tclas         = 'A'
              dialog_mode   = '0'
            importing
              return        = return
              key           = key.
         capture error messages
          if return-type = 'E'.
            concatenate 'Sub Type:' p0082-infty into messtab-tcode.
            move return-message to messtab-param.
            append messtab. clear messtab.
          endif.
    You can use it for modifying the record also.

  • HRMD_A07 Idoc to update InfoType 0014 does not delimit existing PA0014 rec

    In ECC 6.0, we are using HRMD_A07 Idoc to update infotype 0014 using update data received from a third party application. In XI, I am creating the Idoc with Update Code "U" with E1PLOGI, E1PITYP and E1P0014 segments. E1P0014 holds the data for the latest record.
    If I directly pass the Idoc thru ALE layer, It creates records for the new date range on E1P0014 segment, but does not delimit the previous record by changing its end date. This results in two records in PA0014 with end date of 12/31/9999 - which is wrong.
    I also tried using a wrapper FM to create additional segments in the Idoc representing the existing record in PA0014, with the end date being delimited to incoming record's beg. date minus 1.
    This also results in just creating two additional records in PA0014 corresponding to the two segments in Idoc while existing record in PA0014 stays intact resulting in two records with end date 12/31/9999.
    I also experimented with setting the lock indicator (PA0014-SPRPS) but that also does not result in delimiting the existing record.
    Am I missing something? Is there a piece of config that controls this?
    Regards,
    The time constraint on 0014 is "2"

    Hi Jon and Ashish,
    I too am facing the same issue that the new IDOC is not delimiting the previous record.
    Can you explain how did u get over you issue.
    I'm maintaining the same dates in E1PITYP and in E1P0014.
    Thanks,
    Jilly

  • Problem in updating infotype 2001

    Hi Experts,
                     While i am  updating infotype 2001 , using HR_INFOTYPE_operation FM it giving a error , because it calling a wrong sceen 2000 , instead of 2001 . can anybody can help on this ?
    thanks and regards
    Renjith MP

    Hi Dude,
    Go through the below code for 2002 infotype :
    TYPES BEGIN OF text_version.
    TYPES   nummer TYPE x.
    TYPES END OF text_version.
    DATA: PERSONALDATAKEY    LIKE BAPIPAKEY.
    DATA: RETURN       LIKE BAPIRETURN1.
    DATA: P2002       LIKE P2002.
    DATA: PSKEY       TYPE PSKEY.
    DATA: IT_TEXT       TYPE HRPAD_TEXT_TAB .
    DATA: LINE       TYPE HRPAD_TEXT.
    DATA: version       TYPE text_version.
    DATA: pcl1       TYPE pcl1.Input Parameters:
    PARAMETERS:  PERNR  LIKE PA2002-PERNR  DEFAULT '1004511',
                 AWART  LIKE PA2002-AWART  DEFAULT 'LW',
                 BEGDA  LIKE PA2002-BEGDA  DEFAULT SY-DATUM,
                 ENDDA  LIKE PA2002-ENDDA  DEFAULT SY-DATUM,
                 BEGUZ  LIKE PA2002-BEGUZ,
                 ENDUZ  LIKE PA2002-ENDUZ.
    START-OF-SELECTION.
      CALL FUNCTION 'HR_EMPLOYEE_ENQUEUE'
            EXPORTING
              number = PERNR
            IMPORTING
              RETURN = RETURN.
      IF RETURN-NUMBER IS NOT INITIAL.
        EXIT.
      ENDIF.
    * ADD DATA
      CLEAR: P2002.
      P2002-PERNR = PERNR.
      P2002-SUBTY = AWART.
      P2002-ENDDA = BEGDA.
      P2002-BEGDA = BEGDA.
      P2002-BEGUZ = BEGUZ.
      P2002-ENDUZ = ENDUZ.
      P2002-AWART = AWART.
      P2002-ITXEX = 'X'.
    * WRITE DATA
      CLEAR: RETURN, PERSONALDATAKEY.
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'
             EXPORTING
                  INFTY          = '2002'
                  NUMBER         = PERNR
                  SUBTYPE        = AWART
                  VALIDITYEND    = BEGDA
                  VALIDITYBEGIN  = BEGDA
                  RECORD         = P2002
                  OPERATION      = 'INS'
                  NOCOMMIT       = ''
                  TCLAS          = 'A'
             IMPORTING
                  RETURN         = RETURN
                  KEY            = PERSONALDATAKEY
             EXCEPTIONS
                  OTHERS         = 0.
      IF RETURN-NUMBER IS INITIAL.
        COMMIT WORK AND WAIT.
      ELSE.
        ROLLBACK WORK.
        EXIT.
      ENDIF.

  • Update infotype 0032 in user exit ZXPADU02

    Hi All,
    I have the following requirement.
    Telephone extension number is stored in IT0105 and IT0032. When the extension number is updated through ESS, this is stored in IT0105 but it does not update IT0032 which is displayed in MSS.
    I need to update infotype 0032 based on the data in 0105.
    I thought I could update infotype 0032 in userexit ZXPADU02 whenever infotype 0105 was saved using the function module HR_INFOTYPE_OPERATION but it is not working for me.
    Any help would be appreciated.
    Elaine

    You have to make the function call a separate unit of work.One other option is to put the function call in a report & SUBMIT it from the User exit.
    ~Suresh

  • Update Infotype 24 with Qualification

    Hi Friends,
    I have to update infotype 24(qualifications).  I am using function module Rh_insert_infty_1001_ext to update but this function only creates a record in hrp1001(i.e. OM side) but does not create any record in PA side i.e.  infotype 24.
    Is there a different way to update infotype 24?
    Thanks
    Nazish

    Hello Nazish,
    check this  HR_INFOTYPE_OPERATION with operation = 'COP'
    For PD tables,FM - BAPI_HRMASTER-SAVE_REPL_MULT is used and after PD tables are updated , for PA Tables use
    FM - HR_INFOTYPE_OPERATION
    Check FM - RH_INSERT_INFTY_1001_EXT  and also FM - BAPI_HRMASTER-SAVE_REPL_MULT
    regards

  • Update infotype

    I need to update infotype 22, 31 , 68. I am using function module "HR_INFOTYPE_OPERATION". But using this FM i can only upate the fields of infotype which are reflected in the infotype screen. I need to update other fields which are there in the PA table but not reflected in the screen.
    Is there any other function module available?

    Hi,
    You can use the Function Module <b>HR_MAINTAIN_MASTERDATA</b>.
    This function module enables you to maintain master data for employees and applicants. You can enter field names and contents in the 'proposed values' table. This will then be transferred to the corresponding infotypes. The same validation checks take place as would in the individual maintenance screens for the infotypes. You can enter as much data as you like. You can enter several records or infotypes at once. You are responsible for making sure that the data is consistent. If necessary, the module returns an error message. The error messages are the same as the those which appear in the dialog, in other words, the individual maintenance screen error messages are transferred rather than interpreted by this module.
    <u>Exanple</u>
    CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
    EXPORTING
    pernr = p_0735-pernr
    MASSN =
    actio = 'MOD'
    tclas = 'A'
    begda = p_0735-begda
    endda = p_0735-endda
    objps = p_0735-objps
    seqnr = p_0735-seqnr
    sprps = p_0735-sprps
    subty = p_0735-subty
    *Put 0 here when everything is ok. 1 shows dialog on error.
    dialog_mode = dialog_mode
    luw_mode = luw_mode
    NO_EXISTENCE_CHECK = ' '
    NO_ENQUEUE = ' '
    IMPORTING
    return = l_return
    RETURN1 =
    HR_RETURN =
    TABLES
    proposed_values = l_value_tab
    modified_keys = l_pskey.

  • Update Infotype 2051

    Hi all,
    Is there any Function module to update infotype 2051. The FM HR_Maintain_masterdate is not working for this infotype.

    I've done some more research, basically IT2051 data is calculated when you go into the screen and sickness/subsitutions etc feed into this screen. It may be easier to look at loading data into the Time infotypes that get displayed in this Infotype rather than trying to load data directly into it.
    Regards
    J

  • Updating InfoType 0001 in ABAP

    Our parent company is passing different begin and end dates from Infotype 0001 to our HR system. In our system an employee would have a start date of 3/1/2005 but our parent company has the same employee in there system as a start date of 1/1/2008. I was looking at using user exit EXIT_SAPLRHA0_003 to capture these and add the parent companies dates into our Infotype 0001 so that there feed doesnt overwrite our original dates. I have attempted to use HR_INFOTYPE_OPERATION with no luck. Any one have a possible way to update InfoType 0001 without using a BDC?

    What exactly is the issue? In any case HR_INFOTYPE_OPERATION in turn calls HR_MAINTAIN_MASTERDATA so you might end up with the same issue with either function call.
    ~Suresh

  • Standard programs to update infotypes

    Please provide updates for this question:
    What are the standard SAP programs to update infotypes ( Ex: 001 / 002 / 003 ) .
    I will be uploading data from legacy system ( Excel / Text file ) and would like to use standard programs
    before going ahead with BDC .
    Thanks
    Rohan

    Hi,
    I checked out the program you stating.......
    In that program itself if you check the documentation its given how to add in fields.......
    You can use report RPUSTD00 to transfer master data from your old HR system.
    The dataset to be transferred must be stored in a sequential file. The file is stored under the name specified in the "logical file name" field (for more information on logical file names, read the IMG section entitled Additional client-dependent file name maintenance).
    The report reads this dataset and creates a batch input session for transaction PA30.
    The data description of your old record is defined according to the structure HRDATASET. If this structure does not meet your requirements, create the structure CI_HRDATAS in the ABAP Dictionary. In this structure, you can store the infotype fields to which data should be transferred. Make the necessary changes in RPUSTD00.
    Example
    If the include CI_HRADATAS contains the field F1 which is to be assigned to the infotype nnnn, add the following ABAP statements to FORM Dnnnn:
      CLEAR BDCDATA.
      BDCDATA-FNAM = 'Pnnnn-F1'.
      BDCDATA-FVAL =   SATZ-F1.
      APPEND BDCDATA.
    If the FORM Dnnnn does not exist for your infotype nnnn, copy FORM D0008 to FORM Dnnnn. Replace the 0008 by your infotype number:
    FORM Dnnnn.
      CLEAR BDCDATA.
      BDCDATA-PROGRAM  = 'MPnnnn00'.
      BDCDATA-DYNPRO   = '2000'.
      BDCDATA-DYNBEGIN = 'X'.
      APPEND BDCDATA.
      CLEAR BDCDATA.
      BDCDATA-FNAM = 'Pnnnn-F1'
      BDCDATA-FVAL = SATZ-F1
      APPEND BDCDATA.
      CLEAR BDCDATA.
      BDCDATA-FNAM = 'BDC_OKCODE'.
      BDCDATA-FVAL = '=UPD'.
      APPEND BDCDATA.
    ENDFORM.
    The FORM Dnnnn is called directly after FORM D0008; see the ABAP statement indicated as "<------ INSERT in the following (starting at line 1730 in the standard system):
      LOOP AT INFTAB.
        CASE INFTAB.
    Include all infotypes in your action *
         WHEN '0002'. PERFORM D0002.
         WHEN '0001'. PERFORM D0001.
         WHEN '0006'. PERFORM D0006.
         WHEN '0007'. PERFORM D0007.
         WHEN '0008'. PERFORM D0008.
         WHEN 'nnnn'. PERFORM Dnnnn.         "<------ INSERT
         WHEN OTHERS. WRITE: / 'Infotype not included:' (008), INFTAB.
                       STOP.
       ENDCASE.
    ENDLOOP.
    Parameter DSLOGNAM
    Logical file name
    Parameter MAPNAME
    Session name
    Definition
    Enter any name for the session to be created.

Maybe you are looking for