Custom HRP Infotype

I am trying to create a custom HRP infotype to be used in our e-Recruiting system. I want to be able to update the infotype using the SAP standard RH_INSERT_INFTY and like function calls. However my entry in table t777d won't let me change the Update type to anything other than blank (No update via personnel planning update task). I also am having issues which I am not sure if this stems from that problem or not but when I try to use the RH_INSERT_INFTY I get a short dump when it tries to do an insert with a vtask of D because the data doesn't appear to be mapped to the correct fields. My input table type is of type p9xxx and it seems to be mapped correctly until the last stage when it actually tries to insert the line into the table. Any suggestions for what might be wrong? I have checked to make sure that the p9xxx and hrp9xxx have the same structure and they appear to match correctly.
Thanks,
Stephanie

You could search/post this question in the HR forum...

Similar Messages

  • Custom HRP Infotype for e-Recruiting

    I am trying to create a custom HRP infotype to be used in our e-Recruiting system. I want to be able to update the infotype using the SAP standard RH_INSERT_INFTY and like function calls. However my entry in table t777d won't let me change the Update type to anything other than blank (No update via personnel planning update task). I also am having issues which I am not sure if this stems from that problem or not but when I try to use the RH_INSERT_INFTY I get a short dump when it tries to do an insert with a vtask of D because the data doesn't appear to be mapped to the correct fields. My input table type is of type p9xxx and it seems to be mapped correctly until the last stage when it actually tries to insert the line into the table. Any suggestions for what might be wrong? I have checked to make sure that the p9xxx and hrp9xxx have the same structure and they appear to match correctly

    You could search/post this question in the HR forum...

  • Error in creation of custom PD infotype

    Hi,
    I have a task of creating a custom PD infotype(p9xxx). I created HRI9xxx structure with all the custom fields and when I try to create the infotype using tcode PPCI(selected 'field infotype' option and create button in the 'infotype' block was pressed), it gives an error message that p9xxx-begda is not in ABAP dictionary and then it gives me list of screens, module pools and tables created. This custom infotype entry does not exist in T777I. I have tried regenerating it and same problem persists. If anyone knows the solution, please do let me know.
    Thanks in advance

    Solved.

  • Adding Custom OM infotype in Adhoc Query

    Hi All,
    I have created a custom OM  infotype . This infotype contains  only the description of job, i.e job notes . Below  is questions on this:
    1) When I am trying to add this infotype in infoset,then I am able to see this infotype in "related to object type" folder under TWO different relationship .Why its coming under relationship part. There is no relationship for this infotype .'
    To include this in infoset do I have to select this infotype under both the relationship.?
    Please find the screenshot of the relationships under which this infotype is coming:
    Thanks,
    Vaibhav

    Hi Vaibhav,
    First, your question is not so clear:
    You write that you are trying to add a custom infotype, which manages the job's description. Do you mean Infotype 1002? If so - this is not a custom Infotype - it's a standard one.
    Second,if you want to enhance the infoset, this is done by SQ01:
    Choose the relevant infoset by SQ01 and press the Change button
    Choose "Edit" menu --> choose the "Change Info-Type Selection" entry
    In the Popup window which appears, mark the checkbox for the relevant infotype
    Regards,
    Liran

  • Creation of subtypes for a custom PD Infotype.

    HI Experts,
    We are in the process of creating a custom PD infotype (say 9003 and hrp9003 is the table).
    We want the infotype to have 2 subtypes (say 01 and 02).
    We followed the steps and created the infotypes and also made sure that we create 2 subtypes and we were successful till here.
    However, when we try to maintain data in IT9003(pp01), we never get an option to specify the subtype and hence whatever data we save doesnu2019t have any value in subtype field.
    Please help up out to save data with subtypes.
    We want something similar to infotype 1001, where we can select the relationship(subtype) and save accordingly.
    How to make the subtype appear in the data creation screen? Do we have to do some changes in the module pool program?
    Regards,
    Ravikeerthi.

    Check the tables V_778U.....assign your subtypes to custom PD Infotype.
    Check the table for Your PD infotype and subtype assigned to Object Type..
    SPRO --> OM --> Basic Settings -->Data Model Enhancement -->Infotype Maintenance
    Mohan

  • Custom OM Infotypes

    I am having issues creating a custom OM Infotype. I created my HRI9000 structure in SE11 and then went to transaction ppci to create the infotype when I follow the steps to do this the screens and table entries are not getting populated automatically. I couldn't find any documentation on how to get it to do it automatically so I decided to create the screens and table entries myself. Now however, if I go to po13 to add this infotype to a position when I hit the save button nothing is happening. Any help on fixing this issue or the original issue of why the entries are not creating by themselves would be greatly appreciated.
    PS I saw a previous article from a few years ago on this same issue of the screens not getting created but it was never answered.
    Stephanie

    Hi,
    First delete the infotype from PPCI. Then click on Check and see if ALL the entries are deleted. You can delete the Table entries manually. If you are having trouble deleting the TADIR entries, follow these steps:
    To delete the TADIR entries, Go to SE03 --> object Directory --> Change Object Directory Entries. Here Check all options and put the name of the corresponding TADIR entries that you want to delete in the right hand side boxes. Then execute.
    After they are deleted one more time delete Infotype from PPCI. then when you check, all the TADIR entries should be non-existing.
    Lastly delete the HRI9000 structure. Once all is deleted, create the Infotype from scratch.

  • Updating a table using a custom OM infotype

    Hey gurus,
    I have created a custom OM infotype HRP9608. I wish to use this infotype to update a table.
    I marked it as an external, country specific infotype and blanked out the Database table from SM30 (table T777D)
    I have also blanked out the FM. for tab name using SM30 (table T77ID) and added in Read Function and Primary Table.
    The infotype gets created correctly, but when i add it as an external infotype the screen changes. Can someone please provide me with a solution.
    Thanks.

    Hi,
    See the given link, It may help you.
    https://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=64259392
    Regards,
    Shamma

  • Transfer Custom OM Infotype data through ALE for HRMD_ABA Message type

    Hello Folks,
    I have created a Custom OM Infotype.When i run the PFAL transaction. All the standard infotype data is getting filled, but i dont see custom infotype data getting filled.
    Example: HRP9001 is the custom infotype.
    Please let me know the step by step process to populate the Custom infotype data in ALE Transfer.
    Thanks & Regards,
    Nishanth Kumar

    I think function module RH_MASTER_IDOC_DISTRIBUTE_HRMD shows some odd behaviour. It calls EDI_DOCTYPS_OF_MESTYP, which returns the name of the extension in an internal table named "doctyps". But later on, function module MASTER_IDOC_DISTRIBUTE is called with a structure "f_idoc_control". In this structure, the field "cimtyp" should hold the name of the extension, but it NEVER gets filled, although the value is present in doctyps-cimtyp.
    So what I have done, is to activate userexit #004, which is called just before MASTER_IDOC_DISTRIBUTE and modifies structure f_idoc_control, if desired.
    Call transaction CMOD and create a project in a non-SAP namespace: Zxxxx. The enhancement we need is "RHALE001" (HR-CA: Enhancement for ALE functionality in HR). One of its components is EXIT_SAPLRHA0_004, which consists of include ZXHALU08. In this include I called EDI_DOCTYPS_OF_MESTYP again to fill f_idoc_control-cimtyp.
    Here is my code for include ZXHALU08
    DATA: z_doctyps TYPE STANDARD TABLE OF edidocs WITH HEADER LINE.
    CALL FUNCTION 'EDI_DOCTYPS_OF_MESTYP'
      EXPORTING
        mestyp         = f_idoc_control-mestyp
      TABLES
        doctyps        = z_doctyps
      EXCEPTIONS
        invalid_mestyp = 1
        OTHERS         = 2.
    IF sy-subrc = 0.
      LOOP AT z_doctyps.
        f_idoc_control-cimtyp = z_doctyps-cimtyp.
      ENDLOOP.
    ENDIF.
    Hope this helps

  • How to add an customized HR infotype in personnel information on ESS

    Dear Experts,
    I am trying to add a customized HR infotype in personnel information on ESS.  Could you pls provide me some solution or references document. Thanks
    Daniel

    Daniel,
    check this(may give some hint)
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/profile/essPersonalInformationUIenhancementwithoutmodification
    Changing an input field's appearance to Optional in an ESS WD Java scenario
    you need to modify the HomePage framework to include link in ESS for custom infotype.search for chris solomon's blogs in sdn
    Thanks
    Bala Duvvuri

  • Cant  we create a custom PA infotype whose size is more than 1000 chars?

    can we create a custom PA infotype whose size is more than 1000 characters
    i have tried this way i have given 4 fields in PM01 transaction with the data element 255 so the total size is 1020 it is throwing an error. pls help......

    Hi,
    as described in the following documentaion the length of the data could be 1500 bytes.
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/4f/d526be575e11d189270000e8322f96/content.htm
    Regards
    Bernd

  • Custom table infotype

    Hi Experts,
    Can you please provide me with the steps to create a custom table infotype.
    Thanks
    Sri

    hi sri,
       the steps to follow to create the custom infotype are
    Steps to create a HR Infotype:
    1) Go to Transaction PM01.
    2) Enter the custom Infotype number which you want to create
    (Should be a 4 digit number, start with 9).
    3) Select the 'Employee Infotype' radio button.
    4) Select the 'PS Structure Infotype'.
    5) Click on Create... A separate table maintenance window appears...
    6) Create a PS structure with all the fields you want on the Infotype
    7) Save and Activate the PS structure
    8) Go back to the initial screen of PM01.
    9) Click on 'All' push button. It takes a few moments.
    10) Click on 'Technical Characteristics'. Infotype list screen appears
    11) Click on 'Change'(pencil) button
    12) Select your Infotype and click on 'Detail' (magnifying glass) button
    13) Give 'T591A' as subtype table
    14) Give 'T591S' as subtype txt tab
    15) Give your subtype field as subtype field
    16) Save and come back to PM01 initial screen
    17) Click on 'Infotype Characteristics' ... Infotype list screen appears
    18) Click on 'Change' (pencil) button
    19) Click on 'New Entries'
    20) Enter your Infotype number and short text
    21) Here we have to set different Infotype Characteristics as per the requirement.
    (Better open another session with some standard Infotype's
    infotype characteristics screen and use as the reference to fill yours)
    22) Save your entries.
    23) Now the Infotype is created and ready to use.
    24) If you want to change the layout of the Infotype as per your requirement...
    25) In the PM01 initial screen...Select 'Screen' radio button and give 2000
    as the screen name, then click on edit.
    26) In the next screen.. Select 'Layout Editor' and click 'Change'.
    27) Screen default layout appears...here you can design/modify
    the screen..change the attributes of the fields..etc.
    28) Save and activate. (Don't forget to 'Activate at every level)
    regards,
    sreelatha gullapalli

  • Populating custom om infotype

    hi all,
    i have made a custom <b>org management</b> infotype (name starting with 9).
    Can i use any standard function module to read it.Like we have
    HR_read_infotype to read pa infotype ..do we have any srandard function module to read custom om infotype...

    If you have created the infotype using the standard SAP tools ( Transaction PPCI for OM infotypes) you should be able to use all standard function modules/class methods etc.

  • Audit Log for HRP Infotypes

    Hi,
    Just like PCL4 for PA Infotypes, do we have a mechanism to check the changes done to HRP Infotypes?
    Thanks,
    Suryakiran

    Pl check this <a href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/db/7a2a40ce93185de10000000a1550b0/frameset.htm">SAP Help</a> on maintaining log for PD infotypes..
    ~Suresh

  • How to delete buffer for HRP infotypes

    Hi all,
    I am using DFPS workbench and currently it stored buffer of hrp infotype when more than 1 record is being save . i am able to get the buffer using FM : RHOM_GET_BUFFER_FOR_INFTY. However when i try with 'RH_CLEAR_BUFFER' the buffer is still there when i try.
    Any solution to this?
    Thanks and Regards,
    LH

    Hi
    Try using this FM:HR_PSBUFFER_INITIALIZE.
    For more info about this function module, click on this [link|http://shafiq.us/sap/index.php?option=com_content&view=article&id=59:hrmaintainmasterdata-and-hrinfotypeoperation-update-performance&catid=45:hr-abap-tips-and-differences&Itemid=64 ].
    Hope this helps.
    Harsh

  • Uploading HRP infotypes

    HI Experts,
    I have to upload data in HRP infotypes which must reflect through transaction PO13.
    The Inofytpes are HRP1005, HRP1008, HRP1013
    I am using the FM
    HR_INFOTYPE_OPERATION
    Is their any other better way.
    Thanks in Advance.
    Regards,
    IFF

    Hi,
    There are two options...
    1.BDC
    2. FM 'RH_PNNNN_MAINTAIN'... the below example to update the single record...but you can use these FM to update the Multiple entries also...in the Tables options of this FM you can pass the multiple entries for the single infotype which you are updating,,
    FORM rh_pnnnn_maintain  TABLES   p_return TYPE table
                            USING    p_fcode
                                     p_plvar
                                     p_otype
                                     p_objid
                                     p_infty
                                     p_subty
                                     p_pnnnn
                                     p_test
                                     p_subrc.
      DATA: l_commit_flg TYPE hrrhap-commit_flg.
      DATA: l_hrrhad_msg TYPE hrrhad_msg.
      DATA: l_msg LIKE sy-msgv1.
      DATA: l_type TYPE bapireturn-type.
      DATA: l_cl TYPE sy-msgid.
      DATA  l_no TYPE sy-msgno.
      DATA  l_m1 TYPE sy-msgv1.
      DATA  l_m2 TYPE sy-msgv2.
      DATA  l_m3 TYPE sy-msgv3.
      DATA  l_m4 TYPE sy-msgv4.
      DATA: l_return LIKE bapiret1.
      IF p_test NE space.
        l_commit_flg = ''.
      ELSE.
        l_commit_flg = 'X'.
      ENDIF.
      CALL FUNCTION 'RH_STORE_BUFFER_PLOG_TAB'.
      CALL FUNCTION 'RH_CLEAR_BUFFER'.
      CALL FUNCTION 'RH_CLEAR_PLOG_TAB'.
      CALL FUNCTION 'RH_PNNNN_MAINTAIN'
        EXPORTING
          act_fcode           = 'INSE'
          act_plvar           = p_plvar
          act_otype           = p_otype
          act_objid           = p_objid
          act_infty           = p_infty
          act_subty           = p_subty
          act_pnnnn           = p_pnnnn
          suppress_dialog     = '2'
          act_commit_flg      = l_commit_flg
        IMPORTING
          act_mess_info       = l_hrrhad_msg
        EXCEPTIONS
          infty_not_valid     = 1
          no_plvar            = 2
          object_not_defined  = 3
          otype_not_valid     = 4
          no_authority        = 5
          action_rejected     = 6
          no_gdate            = 7
          fcode_not_supported = 8
          OTHERS              = 9.
      IF sy-subrc NE 0.
        CASE sy-subrc.
          WHEN '1'.
            CONCATENATE p_objid p_infty p_subty 'Infotype Not valid'
                                        INTO l_msg SEPARATED BY space.
            PERFORM bapi_return_get TABLES p_return
                                           USING 'W' 'PN' '016' l_msg.
          WHEN '2'.
            CONCATENATE p_objid p_infty p_subty 'No Plan version'
                                        INTO l_msg SEPARATED BY space.
            PERFORM bapi_return_get TABLES p_return
                                           USING 'W' 'PN' '016' l_msg.
          WHEN '3'.
            CONCATENATE p_objid p_infty p_subty 'Object Not defined'
                                        INTO l_msg SEPARATED BY space.
            PERFORM bapi_return_get TABLES p_return
                                           USING 'W' 'PN' '016' l_msg.
          WHEN '4'.
            CONCATENATE p_objid p_infty p_subty 'Object type not valid'
                                        INTO l_msg SEPARATED BY space.
            PERFORM bapi_return_get TABLES p_return
                                           USING 'W' 'PN' '016' l_msg.
          WHEN '5'.
            CONCATENATE p_objid p_infty p_subty 'No Authority'
                                        INTO l_msg SEPARATED BY space.
            PERFORM bapi_return_get TABLES p_return
                                           USING 'W' 'PN' '016' l_msg.
          WHEN OTHERS.
            CONCATENATE p_objid p_infty p_subty 'Update Error'
                                        INTO l_msg SEPARATED BY space.
            PERFORM bapi_return_get TABLES p_return
                                           USING 'W' 'PN' '016' l_msg.
        ENDCASE.
      ELSE.
        p_subrc = 0.
      ENDIF.
      IF l_hrrhad_msg-msgty = 'E' OR
         l_hrrhad_msg-msgty = 'A'.
        l_hrrhad_msg-msgty = 'W'.
      ENDIF.
      l_type = l_hrrhad_msg-msgty.
      l_cl = l_hrrhad_msg-msgid.
      l_no = l_hrrhad_msg-msgno.
      l_m1 = l_hrrhad_msg-msgv1.
      l_m2 = l_hrrhad_msg-msgv2.
      l_m3 = l_hrrhad_msg-msgv3.
      l_m4 = l_hrrhad_msg-msgv4.
      CALL FUNCTION 'BALW_BAPIRETURN_GET1'
        EXPORTING
          type       = l_type
          cl         = l_cl
          number     = l_no
          par1       = l_m1
          par2       = l_m2
          par3       = l_m3
          par4       = l_m4
        IMPORTING
          bapireturn = l_return.
      APPEND l_return TO p_return.
      IF sy-subrc = 0 AND p_test = ''.
        COMMIT WORK.
      ENDIF.
      IF p_test = 'X'.
        ROLLBACK WORK.
      ENDIF.
      CALL FUNCTION 'RH_RESTORE_BUFFER_PLOG_TAB'.
    ENDFORM.                    " RH_PNNNN_MAINTAIN
    Edited by: avinash kodarapu on Dec 14, 2008 2:39 PM

Maybe you are looking for