Update Infotype 1005 (Planned Compensation)

Hi,
Can anyone let me know...how to update infotype 1005 (Planned Compensation.
Transaction to create 1005 (Planned Compensation).
Thanks in advance....
Sandeep.

Hi,
You can goto tcode pp01 or pp02(Expert mode) to create the planned compensation for the job or position.
Rgds,
Balaji.

Similar Messages

  • Updating Infotype PA0001 PLANS

    Dear All... we have requirement to update the PLANS field in PA0001 with 9999999 when the employee is terminated. we are using HR_INFOTYPE_OPERATION. but this fails to update PA0001 as it says 9999999 does not exist in T528b. Is there a way to update PA0001 with out firing a direct update statement.
    Thanks in advance,
    Raghavendra

    Hi,
    There are two cases.
    1. If PA-OM integration is active i.e. in T77S0 the fields PLOGI PLOGI = XX, where XX is your plan version also PLOGI ORGA = X.
       In this case PLOGI PRELI should have your default position i.e. 99999999
    2. In case your PA OM is not active, which I think is the case with you.
      a) go to SM30 view T528B. Click maintain. New entry.
      b) Maintain 99999999 position
    First check if T528B has position 99999999 or not.
    Also if PA OM integration is active please check if the employee for which you are trying to enter the position is included in integration. For this you will have to check feature PLOGI through PE03. Check the decision tree if there is X then integrated or else not integrated.
    cheers
    Ajay

  • ECM Implementation: Custom Infotype instead of IT1005 Planned Compensation

    Hello,
    We are thinking about implementing SAP ECM (incl. MSS). I have seen that OM Infotype 1005 (Planned Compensation) is required to get salary ranges for example.
    In our current OM solution we already have this information stored in a custom Infotype. Does anyone have experience using custom infotypes instead of standard ones in the ECM solution?
    Many thanks
    Lucas

    Hi Lucas,
    Not sure how you are set-up if not using Pay Scale Grades and Levels.  Do you use T710 or T510 at all?  What values are in IT0008 for these fields? 
    In any other change in status other than Activation, the report only changes IT0759-Compensation Program.  So Pay Scale Grade and Level should not be a factor.  If activating the Compensation Program infotype (IT0759), the report is trying to create a new IT0008, so your settings for Features such as TARIF and LGMST and any custom BAdIs should be checked to make sure the IT0008 can be created as required by your customization.  Even so, we use transaction PECM_CHANGE_STATUS (Report RHECM_CHANGE_PROC_STATUS) to activate bonus payments which are not linked to IT0008 but to IT0015 and so they are not tied to a Pay Scale Group or Level.
    Thus, I would need more info to determine why you are experiencing the error message.
    Paul

  • Enhance Standard Infotype 1005 in HR

    Dear All,
    Please suggest how to enhance standard infotype 1005 - Planned Compensation in HR.Transcation PM01 is not allowing to do so ...as no CI include is attached for the same.
    Please guide.
    Regards,
    Subhash

    hi,
      maybe you can achieve your requirement by creating a new custom OM infotype
    ( if the custom information are linked to the OM entity :  org unit, positions.. ) or a new PA infotype ( if the custom information are linked to the employee ) .
    Regards luigi
    Edited by: luigi la motta on Sep 2, 2011 11:46 AM

  • Input fileds not appearing in IT1005 Planned Compensation in Tab for PPOME

    Hello friends,
    The business requirement is:
    - add IT 1005 Planned Compensation as a tab page in T.code PPOME/PPOCE
    - I configured the following in system:
      - IMG>Personnel Mgt>Org Mgt>Hierarchy Framework>Integrate New Infotype>  >Add Infotype as Tab Page in Detail Area>Define your onw tab page>Tab Page Definition (this is option one)>
    I added Tab page as z1005, ticked infotype specific and infotype 1005
    > Scenario Definition (Hierarchy Framework) > select OME0 >
    Tab Page in Scenario for each Object Type >
    I entered object type S (as we need it for Position), tab page: z1005, and respecitve sequence, I did not enter any report name, screen no, FM for Icons and Donot display is unchecked.
    Once I did this configuration and run PPOME tcode I got the tab page there but in the input fields it is blank and showing text like ##################### just a row like this.
    However when I do the same configuration for IT 1050 Job evaluation, it is working fine there. But 1005 is throwing the above error.
    Can anybody faced the same problem and resolve the above issue or incase some SAP Notes are available for the same.
    thanks
    Sunny

    In my opinion, that would be "Best Practice".  Although I think that term is over-used. Everything varies by each client's needs/wants and what functionality they use in the system.   That being said, even if they're not using portions of functionality today, it's better to plan for it.  That way you don't have to redefine the catalog every time you want to use something new.
    There really is no "correct" ratio of Jobs to Positions.  For a smaller company you're going to have fewer positions assigned to each job.  For a larger company, you're going to have more people doing the same work, and therefore more positions assigned to a lot of your jobs.
    I generally recommend a new job is created when there is a difference in one or more of the following.
    u2022   Tasks (Function) - Administration vs. Manufacturing vs. Engineering, etc.
    u2022   Responsibilities - Supervising other people vs. not supervising, Lead, Trainers, etc.
    u2022   Pay Range (significant differences) - Except for differences based on location (Someone in San Fran/Bay area is
        going to get more money than someone doing the same job in Iowa; different amts/currencies for different countries)
    u2022   Qualifications/Skills - requires a degree or certificate vs. job that doesn't
    With your client, I would recommend having the approximately 200 Jobs, and creating the existing Jobs as Job Families so they could still report on data as they see it today.
    ...Danialle
    Edited by: Danialle Rook on Aug 12, 2010 9:49 PM

  • Infotype 1005 update

    Hi ,
    I need to upload data into OM infotype 1005.
    for this i am using the FM  RH_insert_infty.
    the logic I am using is as follows.
    DATA:
        lt_relation TYPE TABLE OF p1001,
        ls_relation TYPE          p1001.
      ... data determination from file ...
      ls_relation-mandt = sy-mandt.
      ls_relation-plvar = your plvar from file.
      ls_relation-otype = your otype  from file.
      ls_relation-objid = your from file.
      ls_relation-infty = '1001'.
      ls_relation-istat = '1'.
      ls_relation-rsign = constant if always same objects.
      ls_relation-relat = constant if always same objects.
      ls_relation-begda = sy-datum.
      ls_relation-endda = '99991231'.
      ls_relation-sclas = your sclas from file.
      ls_relation-sobid =  your sobid from file.
      APPEND ls_relation TO lt_relation.
      CALL FUNCTION 'RH_INSERT_INFTY'
        EXPORTING
          vtask               = 'v'
        TABLES
          innnn               = lt_relation
        EXCEPTIONS
          no_authorization    = 1
          error_during_insert = 2
          repid_form_initial  = 3
          corr_exit           = 4
          begda_greater_endda = 5
          OTHERS              = 6.
        CASE sy-subrc .
      ... error handling ...
    After this when I go back and check with respective table I am able to see the records in HRP1005 table thru SE11.
    How ever when i am trying to see the records which are existing in HRP1005 thru PP02, it is displaying no object exists.
    Can any one help me.
    thanks
    Rakhnil

    Hi rakhnil21,
    I want to data upload OM infotype 1005. I used FM (RH_PNNNN_MAINTAIN) it is working fine but I checked the table HRP 1005 this are the field values not inserted in the table (MOLGA, TRFAR, TRFGB, TRFKZ, TRFG1, TRFG2, TRFS1, TRFS2, BUDG1, BUDG2, and CURCY)
    Can you please help me what are the correct values pass into the FM Or if you have sample code Please help me out.
    Thanks,
    Chandran.

  • Update Infotype 0167 - Health Plans

    Hi, All!
    I am coding a mass update of health plans.  I'm using HR_INFOTYPE_OPERATION and it seems to be working except for employees with dependents.  I get the following returned from the function when there are dependents:
    No entry for plan A313 / option 0001 / dependent coverage 0002
    Where A313 is the plan I'm trying to change to and this employee has 2 dependents. 
    Can anyone help with this?

    This is resolved.  Turns out that message is part of our configuration; the fact that I got it means my program is running as it should.

  • 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

  • Change / update Infotype u201C0000u201D during/after the 759 process

    Hi All,
    Can anybody tell me the process to
    change / update Infotype u201C0000u201D during/after the 759 process. 
    Is there any BADI or Exit or any other way to update Infotype '0000' when we make changes in infotype '0759'??
    Thanks in advance..

    Hi Friends,
    I too have a same query to update the infotype " 0000 "  Actions. During or After the changes of the compensation process infotype " 0759 " .
    Could any body can give me a suggestion of  Update FM or BADI or any Exits to update the
    infotype  " 0000 ".
    Regards,
    Vikram.C

  • Updating infotype 1007

    Hello experts,
    I need to update the IT 1007 marking a position as Vacant.
    Is this can be done using a Function Module? like the one that updates infotype in the PA30 (HR_INFOTYPE_OPERATION) ?
    Thanks in advance for your help,
    ArepaKing

    Dear King,
    Not much sure but kindly have a look at function module :-
    RH_UPDATE_INFTY
    Short Text
    Change infotype records
    Functionality
    With this function module you can change multiple infotype records for OM objects from Personnel Planning database tables (HRPnnnn). The infotype tables of the table parameter INNNN must all have the structure Pnnnn (logical structure for the infotype nnnn). The records you want to change must exist in the Personnel Planning database tables. If not, this triggers the exception ERROR_DURING_UPDATE.
    Might be other members can have some more better ideas as well.
    Hope this helps.
    Kindly reward in case useful.
    Regards & Thanks,
    Darshan Mulmule

  • Planned Compensation from Job to Position

    Hi experts
    Is there any transaction that migrates the planned compensation from the job to the position infotype?
    Thanks in advance

    No need to transfer IT1005 from a Job to a position. Based on the S-C relationship, a position inherits the planned comp from the position, unless you create an IT1005 on the position, in which case that superceded the one inherited from the job

  • Planned Compensation

    Hi All,
    Rquirement is give budget estimate for all positions.
    We are planning to use IT 1005 for storing the planned compensation. For each position we are maintaining data for IT 1005 under tab Pay Grade. As per the salary data defined in SPRO, values are getting defaulted once i select the grade and level.
    But when I am cheking the data from HRP1005 i am not able to see the data for Currency, Pay Grade Min, Max and the refernce salary.
    If i maintain the data under "Direct" tab the data for above fields are captured, but the grade is not captured.
    Any input, from where i can fetch this data? or is there any alternate approach?
    Thanks!
    Regards,
    Chetan

    Hi Chetan,
    Currently these fields are filled in via the following process:
    The Reference salary displayed in IT1005 (Planned Compensation) PayGrade tab is retrieved from table T710A (cluster V_T710CL_B (SM34)).
    Min grade level and Max grade level are from table T710.
    Hope this help
    Sarah

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

Maybe you are looking for