Customising new hire HCM process

Hi,
My requirement is to build a new hire process for us empoyees, I was able to create the process well, but when i execute the process in hrasr_test_process i found, when I supply the pernr then the value help for the Emp grp, empSubgrp and other fields are coming, but same value helps does not come when I dont give any pernr .
I have gone throught many threads, and std process hire_10/hire_01 they are using a back end service s_HIRE_ADD_FUNCTIONS/S_HIRE_ADD_US_FUNCTION, i did the smae way but no use.
Please help in as this is very imp critical issues.
Thanks in advance
Pooja

Passing help values do it in GET_HELP_VALUES method.
Thanks,
Aravind

Similar Messages

  • HCM Process and Forms Position Change Workflow Rejection

    Hi Experts,
    I am new to HCM Process and Forms workflows and have a simple query here.
    With the conventional workflows (PR/PO) when Approver Rejects a workitem we send a notifcation to the INITIATOR and when he changes the PO/PR the workflow gets triggered via CHANGED EVENT.
    However, here in POSITION CHANGE workflow when an approver REJECTS it at any level HOW WILL I SEND BACK THE FORM TO INITIATOR SO THAT he does the suggested changes and submits for RE-APPROVAL.
    Idea is to avoid the burden of filling all the fields everytime
    Please guide me on this.
    Thanks a lot
    Rgds,
    Lakshmi

    Hi,
    If a change method doesn't exist you can create a new one where you can use a Call Transaction sentence that redirects to a tcode where you can modify the form.
    Regards,

  • Unable to test a FPM form based process in HCM Process & Forms ?

    Hi Experts,
    Am new to HCM Process & Forms, I created my first form on FPM and am trying to test it but am not able to do so.. can you all please help me figure out where I am going wrong.
    Here is what I am doing ...
    I have a build a FPM Form Scenario and Process. Now when I clicking on the Execute button in HRASR_DT and go the test screen I dont get the option for selecting the Web Dynpro Screen as Application Start Option.
    I also tried testing it through
    http://OURSERVER/sap/bc/webdynpro/sap/asr_process_execute_fpm?sap-language=EN&sap-wd-configId=ASR_EXECUTE_5_STEP_PA
    and
    http://OURSERVER/sap/bc/webdynpro/sap/asr_process_execute
    when I do this then I am getting an error message "No Internal Service Request scenario was specified".
    Please Advice.
    Thanks

    Hi Sahir,
    Yes, I had to Activate the business function HCM_ASR_CI_5 to get the "Option for Application Start" section in HRASR_DT.
    Thanks for the launchpad configuration link.
    The one think that I am still having issues is that if I goto se80 and selected the WD Application ASR_PROCESS_EXECUTE_OVP and using the Application configuration ASR_PROCESS_EXECUTE_OVP_CFG I execute it by clicking on Test....I get an error message saying
    "Process does not exist"
    Does this mean I can't test my process through se80 I will always have to go through portal and configure the launchpad to test my process ?
    Or am I missing some config or doing something wrong ?
    Regards
    Chayan

  • HCM & Process forms

    Hi Experts,
    I am new to HCM & Process forms could you please provide the information about HCM & Process forms, and how they are useful.
    In which requirements we have to use these HCM & Process forms.(Send me some important links regarding the HCM & Process forms).
    Thank you,
    B. Raghu Prasad.
    Moderator Message: Please search before posting.
    Edited by: Suhas Saha on Oct 5, 2011 3:52 PM

    Hi Aakash,
    Yes, in my case it was an authorization issue. Try assigning the role SAP_ASR_MANAGER to the manager in the ECC.
    Regards,
    Manish

  • Creating a new position and updating IT 1028 using HCM processes and forms

    I have to create a new position and update the related infotypes using the design time framework of HCM processes and forms. The problem I am facing is the info type 1028 is not a part of the de coupled infotype framework and does not appear in the service fields list. How can I update the infotype 1028? I was thinking of updating it using the FLUSH method of the class implementing the ADV services interface IF_HRASR00GEN_SERVICE_ADVANCED by calling the function module RH_INSERT_INFTY. But, how do I get the position ID created? Is there any other way of achieving this? Please help as soon as possible.

    HI
    Create one Function Module to return all the vacant positions and load that in a drop down.
    For IT1028 you have to update via the RH_INSERT_INFTY.
    Kind Regards,
    Mukesh

  • Short Dump while executing New Hire (action type) in PA40

    Hi All,
    i am getting short dump while executing PA40 for new hire action type can anyone look into this and guide as i am new to HCM.
    Category               ABAP Programming Error                                                      
    Runtime Errors         SYNTAX_ERROR                                                                
    ABAP Program           /1PAPAXX/HDR_21000A                                                         
    Application Component  Not Assigned                                                                
    Date and Time          21.08.2014 14:07:03                                                         
    Short text                                                                                       
        Syntax error in program "/1PAPAXX/HDR_21000A ".                                              
    What happened?                                                                                   
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPFP50M" had to be terminated because it has                      
        come across a statement that unfortunately cannot be executed.                               
        The following syntax error occurred in program "/1PAPAXX/HDR_21000A " in                     
        include "/1PAPAXX/HDR_21000AO01 " in                                                        
        line 52:                                                                                     
        ""LV_LENGTH" has already been declared"                                                      
        The include has been created and last changed by:                                            
        Created by: "HCM04 "                                                                         
        Last changed by: "HCM03 "                                                                    
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPFP50M" had to be terminated because it has                      
        come across a statement that unfortunately cannot be executed.                               
    What can you do?                                                                                 
        Please eliminate the error by performing a syntax check                                      
        (or an extended program check) on the program "/1PAPAXX/HDR_21000A ".                        
        You can also perform the syntax check from the ABAP Editor.                                  
        If the problem persists, proceed as follows:                                                 
        Note down which actions and inputs caused the error.                                         
        To process the problem further, contact you SAP system                                       
        administrator.                                                                               
        Using Transaction ST22 for ABAP Dump Analysis, you can look                                  
        at and manage termination messages, and you can also                                         
        keep them for a long time.                                                                   
    Error analysis                                                                                   
        The following syntax error was found in the program /1PAPAXX/HDR_21000A :                    
        ""LV_LENGTH" has already been declared"                                                      
    How to correct the error                                                                         
        Probably the only way to eliminate the error is to correct the program.                      
        If you cannot solve the problem yourself and want to send an error                           
        notification to SAP, include the following information:                                      
        1. The description of the current problem (short dump)                                       
           To save the description, choose "System->List->Save->Local File                           
        (Unconverted)".                                                                              
        2. Corresponding system log                                                                  
           Display the system log by calling transaction SM21.                                       
           Restrict the time interval to 10 minutes before and five minutes                          
        after the short dump. Then choose "System->List->Save->Local File                            
        (Unconverted)".                                                                              
        3. If the problem occurs in a problem of your own or a modified SAP                          
        program: The source code of the program                                                      
           In the editor, choose "Utilities->More                                                    
        Utilities->Upload/Download->Download".                                                       
        4. Details about the conditions under which the error occurred or which                      
        actions and input led to the error.                                                          
    System environment                                                                               
        SAP Release..... 731                                                                         
        SAP Basis Level. 0007                                                                        
        Application server... "dc-ds-erp"                                                            
        Network address...... "172.16.23.111"                                                        
        Operating system..... "Linux"                                                                
        Release.............. "3.0.13-0.27-default"                                                  
        Hardware type........ "x86_64"                                                               
        Character length.... 16 Bits                                                                 
        Pointer length....... 64 Bits                                                                
        Work process number.. 1                                                                      
        Shortdump setting.... "full"                                                                 
        Database server... "dc-ds-erp"                                                               
        Database type..... "ORACLE"                                                                  
        Database name..... "ECD"                                                                     
        Database user ID.. "SAPSR3"                                                                  
        Terminal.......... "NLC-HP"                                                                  
        Char.set.... "C"                                                                             
        SAP kernel....... 720                                                                        
        created (date)... "Sep 14 2013 06:16:24"                                                     
        create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr130820"                            
        Database version. "OCI_112, 11.2.0.3.0, V1, default"                                         
        Patch level. 500                                                                             
        Patch text.. " "                                                                             
        Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"              
        SAP database version. 720                                                                    
        Operating system..... "Linux 2.6, Linux 3"                                                   
        Memory consumption                                                                           
        Roll.... 0                                                                                   
        EM...... 37708200                                                                            
        Heap.... 0                                                                                   
        Page.... 106496                                                                              
        MM Used. 4666776                                                                             
        MM Free. 3709976                                                                             
    User and Transaction                                                                             
        Client.............. 210                                                                     
        User................ "HCM03"                                                                 
        Language key........ "E"                                                                     
        Transaction......... "PA40 "                                                                 
        Transaction ID...... "53EF470299AB5D67E1000000AC10176F"                                      
        EPP Whole Context ID.... "005056A301D11EE48A9D08B337F884E3"                                  
        EPP Connection ID....... 00000000000000000000000000000000                                    
        EPP Caller Counter...... 0                                                                   
        Program............. "SAPFP50M"                                                              
        Screen.............. "MP000000 1000"                                                         
        Screen Line......... 3                                                                       
        Debugger Active..... "none"                                                                  
    Information on where terminated                                                                  
        Termination occurred in the ABAP program "SAPFP50M" - in                                     
        "GET_HEADER_WITH_TCLAS".                                                                    
        The main program was "MP000000 ".                                                            
        In the source code you have the termination point in line 146                                
        of the (Include) program "FP50MDHD".                                                         
    Source Code Extract                                                                              
    Line
    SourceCde                                                                                  
      116
      CALL FUNCTION 'HR_HEADER_GET'                                                            
      117
          EXPORTING                                                                            
      118
               DHDID                    = FHD_HID                                              
      119
               BEGDA                    = BEGDA                                                
      120
               TCLAS                    = TCLAS                                                
      121
    * Es wird nur einer der folgenden 3 Parameter benutzt.                                     
      122
    * Ausgewertet wird zunaechst MOLGA, dann P0001 dann PERNR.                                 
      123
    * Der erste der nicht initial ist wird ausgewertet.                                        
      124
    *           MOLGA                   =                                                      
      125
               P0001                    = P0001                                                
      126
               PERNR                    = PSPAR-PERNR                                          
      127
          IMPORTING                                                                            
      128
               PROG                     = HEADER_PROG                                          
      129
               DNUM                     = HEADER_DYNNR                                         
      130
           EXCEPTIONS                                                                          
      131
                HEADER_DEACTIVATED          = 1                                                
      132
                HEADER_UNKNOWN              = 2                                                
      133
                HEADER_GENERATE_DEACTIVATED = 3                                                
      134
                HEADER_GENERATE_FAILED      = 4                                                
      135
                INTERNAL_ERROR              = 5                                                
      136
                OTHERS                      = 6.                                               
      137
      138
      IF NOT SY-SUBRC IS INITIAL.                                                              
      139
    * Bei Problemen gibt's eben ein leeres Dynpro.                                             
      140
        HEADER_PROG = 'SAPMP50A'.                                                              
      141
        HEADER_DYNNR = '0090'.                                                                 
      142
      ELSE.  " NOT sy-subrc IS INITIAL.                                   "                    
      143
    * Dann setzen wir jetzt auch noch das Datum fest.                                          
      144
        PERFORM HEADER_BEGDA_SET IN PROGRAM (HEADER_PROG) USING BEGDA.                         
      145
    * Und schalten auf Uebergabe der PERNR mit globalen Variablen.                             
    >>>>>
        PERFORM HEADER_LAZY_ON IN PROGRAM (HEADER_PROG).                                       
      147
      ENDIF.  " (ELSE) NOT sy-subrc IS INITIAL.                           "                    
      148
    * Merken wie der Header heisst. Damit MPPERS00 sich erinnern kann.                         

    Hi,
    Error Log: Syntax error
    ""LV_LENGTH" has already been declared"
    please check LV_LENGTH variable declaration.
    It may be declared more once!

  • Runtime error while executing New Hire action in PA40

    Hi All,i am getting short dump while executing PA40 for new hire action typecan anyone look into this and guide as i am new to HCMNote: getting dump only for one user id for rest all other user id i am not getting dump.
    Category               ABAP Programming Error                                                      
    Runtime Errors         SYNTAX_ERROR                                                                
    ABAP Program           /1PAPAXX/HDR_21000A                                                         
    Application Component  Not Assigned                                                                
    Date and Time          21.08.2014 14:07:03                                                         
    Short text                                                                                       
        Syntax error in program "/1PAPAXX/HDR_21000A ".                                              
    What happened?                                                                                   
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPFP50M" had to be terminated because it has                      
        come across a statement that unfortunately cannot be executed.                               
        The following syntax error occurred in program "/1PAPAXX/HDR_21000A " in                     
        include "/1PAPAXX/HDR_21000AO01 " in                                                        
        line 52:                                                                                     
        ""LV_LENGTH" has already been declared"                                                      
        The include has been created and last changed by:                                            
        Created by: "HCM04 "                                                                         
        Last changed by: "HCM03 "                                                                    
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPFP50M" had to be terminated because it has                      
        come across a statement that unfortunately cannot be executed.                               
    What can you do?                                                                                 
        Please eliminate the error by performing a syntax check                                      
        (or an extended program check) on the program "/1PAPAXX/HDR_21000A ".                        
        You can also perform the syntax check from the ABAP Editor.                                  
        If the problem persists, proceed as follows:                                                 
        Note down which actions and inputs caused the error.                                         
        To process the problem further, contact you SAP system                                       
        administrator.                                                                               
        Using Transaction ST22 for ABAP Dump Analysis, you can look                                  
        at and manage termination messages, and you can also                                         
        keep them for a long time.                                                                   
    Error analysis                                                                                   
        The following syntax error was found in the program /1PAPAXX/HDR_21000A :                    
        ""LV_LENGTH" has already been declared"                                                      
    How to correct the error                                                                         
        Probably the only way to eliminate the error is to correct the program.                      
        If you cannot solve the problem yourself and want to send an error                           
        notification to SAP, include the following information:                                      
        1. The description of the current problem (short dump)                                       
           To save the description, choose "System->List->Save->Local File                           
        (Unconverted)".                                                                              
        2. Corresponding system log                                                                  
           Display the system log by calling transaction SM21.                                       
           Restrict the time interval to 10 minutes before and five minutes                          
        after the short dump. Then choose "System->List->Save->Local File                            
        (Unconverted)".                                                                              
        3. If the problem occurs in a problem of your own or a modified SAP                          
        program: The source code of the program                                                      
           In the editor, choose "Utilities->More                                                    
        Utilities->Upload/Download->Download".                                                       
        4. Details about the conditions under which the error occurred or which                      
        actions and input led to the error.                                                          
    System environment                                                                               
        SAP Release..... 731                                                                         
        SAP Basis Level. 0007                                                                        
        Application server... "dc-ds-erp"                                                            
        Network address...... "172.16.23.111"                                                        
        Operating system..... "Linux"                                                                
        Release.............. "3.0.13-0.27-default"                                                  
        Hardware type........ "x86_64"                                                               
        Character length.... 16 Bits                                                                 
        Pointer length....... 64 Bits                                                                
        Work process number.. 1                                                                      
        Shortdump setting.... "full"                                                                 
        Database server... "dc-ds-erp"                                                               
        Database type..... "ORACLE"                                                                  
        Database name..... "ECD"                                                                     
        Database user ID.. "SAPSR3"                                                                  
        Terminal.......... "NLC-HP"                                                                  
        Char.set.... "C"                                                                             
        SAP kernel....... 720                                                                        
        created (date)... "Sep 14 2013 06:16:24"                                                     
        create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr130820"                            
        Database version. "OCI_112, 11.2.0.3.0, V1, default"                                         
        Patch level. 500                                                                             
        Patch text.. " "                                                                             
        Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"              
        SAP database version. 720                                                                    
        Operating system..... "Linux 2.6, Linux 3"                                                   
        Memory consumption                                                                           
        Roll.... 0                                                                                   
        EM...... 37708200                                                                            
        Heap.... 0                                                                                   
        Page.... 106496                                                                              
        MM Used. 4666776                                                                             
        MM Free. 3709976                                                                             
    User and Transaction                                                                             
        Client.............. 210                                                                     
        User................ "HCM03"                                                                 
        Language key........ "E"                                                                     
        Transaction......... "PA40 "                                                                 
        Transaction ID...... "53EF470299AB5D67E1000000AC10176F"                                      
        EPP Whole Context ID.... "005056A301D11EE48A9D08B337F884E3"                                  
        EPP Connection ID....... 00000000000000000000000000000000                                    
        EPP Caller Counter...... 0                                                                   
        Program............. "SAPFP50M"                                                              
        Screen.............. "MP000000 1000"                                                         
        Screen Line......... 3                                                                       
        Debugger Active..... "none"                                                                  
    Information on where terminated                                                                  
        Termination occurred in the ABAP program "SAPFP50M" - in                                     
        "GET_HEADER_WITH_TCLAS".                                                                    
        The main program was "MP000000 ".                                                            
        In the source code you have the termination point in line 146                                
        of the (Include) program "FP50MDHD".                                                         
    Source Code Extract                                                                              
    Line
    SourceCde                                                                                  
      116
      CALL FUNCTION 'HR_HEADER_GET'                                                            
      117
          EXPORTING                                                                            
      118
               DHDID                    = FHD_HID                                              
      119
               BEGDA                    = BEGDA                                                
      120
               TCLAS                    = TCLAS                                                
      121
    * Es wird nur einer der folgenden 3 Parameter benutzt.                                     
      122
    * Ausgewertet wird zunaechst MOLGA, dann P0001 dann PERNR.                                 
      123
    * Der erste der nicht initial ist wird ausgewertet.                                        
      124
    *           MOLGA                   =                                                      
      125
               P0001                    = P0001                                                
      126
               PERNR                    = PSPAR-PERNR                                          
      127
          IMPORTING                                                                            
      128
               PROG                     = HEADER_PROG                                          
      129
               DNUM                     = HEADER_DYNNR                                         
      130
           EXCEPTIONS                                                                          
      131
                HEADER_DEACTIVATED          = 1                                                
      132
                HEADER_UNKNOWN              = 2                                                
      133
                HEADER_GENERATE_DEACTIVATED = 3                                                
      134
                HEADER_GENERATE_FAILED      = 4                                                
      135
                INTERNAL_ERROR              = 5                                                
      136
                OTHERS                      = 6.                                               
      137
      138
      IF NOT SY-SUBRC IS INITIAL.                                                              
      139
    * Bei Problemen gibt's eben ein leeres Dynpro.                                             
      140
        HEADER_PROG = 'SAPMP50A'.                                                              
      141
        HEADER_DYNNR = '0090'.                                                                 
      142
      ELSE.  " NOT sy-subrc IS INITIAL.                                   "                    
      143
    * Dann setzen wir jetzt auch noch das Datum fest.                                          
      144
        PERFORM HEADER_BEGDA_SET IN PROGRAM (HEADER_PROG) USING BEGDA.                         
      145
    * Und schalten auf Uebergabe der PERNR mit globalen Variablen.                             
    >>>>>
        PERFORM HEADER_LAZY_ON IN PROGRAM (HEADER_PROG).                                       
      147
      ENDIF.  " (ELSE) NOT sy-subrc IS INITIAL.                           "                    
      148
    * Merken wie der Header heisst. Damit MPPERS00 sich erinnern kann.                         
      149
    * Wird mit Einfuehrung des Headerobjekts obsolet.                                          
      150
      PERFORM REMEMBER_HEADER  "                             "XYVPH4K015649                    
      151
        USING HEADER_PROG HEADER_DYNNR 'S'.  "               "XYVPH4K015649                    
      152
    ENDFORM.                                                                                   
      153
      154
    *       FORM RE588I                                                   *                    
      155
      156
      157
      158
    *  -->  T588I_DHDID                                                   *                    
      159
    *  -->  T588I_MOLGA                                                   *                    
      160
    *  -->  T588I_TCLAS                         

    Implement SAP Note 1004280.. your issue if fixed
    If your issue is resolved request you to close the thread or else free feel to touch base
    BR
    Anil

  • Error while editing standard HCM Processes & Forms

    Hi experts,
    I would Iike to test the standard HCM processes & Forms & for which I have imported the standard forms from Client 000. I have also configured the ADS & have tested the credentials as well. Everything is fine & new custom ADOBE interactive forms (Not HCM Forms) are working fine through WDA. When I test any of the standard processes using HR Administrator role in Portal, I am able to select the relevant standard process (e.g. TERMINATION) for a given employee, but when I click on the  Edi Process button, the system generates an error (short dump): "'WebDynpro Exception: ADS call failed ". I have checked OSS, but did not find any suitable note for it. I have the HR administrator role assigned in the back end & have confirmed that the ADS configuration as well as credential are working fine using the recommended reports. We are on EhP4 SP06.
    Appreciate if anyone has already experienced these probelms & can suggest any solutions. Thanks in advance.
    Best regards,
    Sameer

    Sameer,
    To me it appears that ADS is conencted to only backend ECC not to the portal system.
    Please try below:
    1. Launch WDA for HCMPF in SE80 with appropriate parameters and see if this displays interactive adobe form when you click in edit button.
    2. May be test the ADS connectivity to portal system.
    regards
    Sridhar Kandisetty

  • Adding Fields to New Hire SAP Script, Text ID PAMA

    Hi there,
    I have successfully created a sapscript email to be sent via Dynamic Actions for the notification of New Hires and Terminations.  This has been accomplished via feature M0001 (we have created two new features u2013 M00NH & M00TM), dynamic action (T588z), Business Workplace, distribution lists, etc.  All are working correctly, and an email is being generated and forwarded to appropriate parties.
    Now we have been asked to add extra fields to the SAP Script text for New Hire and Termination.  These are text fields for Employee Group, Employee Subgroup, among others.
    Our syntax has been set up as follows:
    &'Employee Group:             'P0001-PERSG(02)&
    &'Employee Group Text:        'T501T-PTEXT(20)&
    &'Employee Subgroup:          'P0001-PERSG(02)&
    &'Employee Subgroup Text:     'T503T-PTEXT(20)&
    For the New Hire action, we are getting the Employee group and Employee subgroup codes to display but we are NOT getting the Employee Group or Employee Subgroup texts to display.  To confuse the issue, we ARE getting these text fields to display for the Termination script.  Our ABAP'er is also having difficulty determining how to bring in these fields to the New Hire script.
    We have researched this website have tried the instructions given by one user..... which states that we needed to go to our SAPscript text and make the following changes:
    " To get other HR data into your standard text (from SO10):
    Insert > Symbols > Program symbols (now you'll see a list of print programs, and i guess this is where the ABAP grabs the data).
    Highlight the one for HR Master data, and click the DDIC button.
    Double click the table you need data from (e.g P0000, P0001 or P0002).
    Finally select the field you want."
    I have done this, but when I get to the Program symbols, I do not see a print program for HR Master Data.  I only see RPUCOB02 - Processing of Qualifying COBRA Events and Letters & SAPMSSCE - SAPscript Standard Text Maintenance. 
    I tried to use the RPUCOB02 and inserted the text for Employee Subgroup as a test.  But it did not work as the text still did not display.
    The other oddity is that for the Termination sapscript text, the Employee Group and Employee Subgroup text displays correctly.  To test our syntax, we then connect the Termination sapscript text to the 'New Hire' action and reran the New Hire action.  The Employee Group and Employee Subgroup text fields then disappeared.  So it worked when the action was a termination, but did not work when the action was New Hire.
    The difference between these two actions is that the feature for the sapscript generation for New Hires is being generated upon saving of I0002 (which is created AFTER I0001) - we needed the Employee's name in the text.  For the Termination action, the feature is set to generate the mail upon saving of I0001.  This is the only difference between the two.  But as I need the employee name to display, it seemed the best approach.  I did try to generate the New Hire sapscript after saving of I0008, but had the same problem. 
    Does anyone know how we can add text fields to our New Hire sapscript text and actually get them to display?  We would also like to display the Org Unit text (&'ORGEH_2nd_TEXT(40)&) or even  the Supervisor (from the OM relationship).  But they do not display for the New Hire sapscript either. And our ABAP'er is able to insert the Supervisor logic, but the field still does not display.
    Thanks very much for any help.
    Edited by: Cathryn Westgarth on Nov 17, 2009 6:23 PM
    Edited by: Cathryn Westgarth on Nov 17, 2009 6:24 PM

    I am going to repost this question to the HR forum as it may be more appropriately an HR forum questions.
    Thanks
    Cathryn

  • Customizing Requisition request in HCM Processes & Forms

    Hi HCMers,
    We have just upgraded our development system to EhP4 in ECC and E-Recruiting systems, and SP5 in E-recruiting. We want to use the simple requisition request process in HCM Processes and Forms but have several customizations to apply. For example, changes to the form and the workflow.  As a developer I am able to create the custom Adobe form, the custom workflow, and apply any necessary enhancements to ABAP code. However I am unclear how to link these in via the HCM Processes and Forms framework so that they will be called from the standard screen in MSS (Manager Services > My Requisitions > Create New Requisition Request). I did find the tutorial for building a process scenario from scratch, but I can't find the "simple requisition" form in HRASR_DT, but I find the simple form in SFP as ISR_FORM_SRQ1.
    So, my question - what is the best way to implement these customizations? Should I copy the existing process scenario for exstended requisition (HR_MSSRCF_REQUISITION) into a Z_HR_MSSRCF_REQUISITION and make all my changes; or create my form scenario and process scenario from scratch?  Do we need to change the webdynpro for the Create New Requisition Request to call the new form and scenario, or is there a place that is configured? Do I really even need to use the HCM processes and form framework?
    If I sound clueless it's because I am Anyone wanna give me a clue?
    Thanks for any help you can give!
    Margaret

    Cpoy HR_MSSRCF_REQUISITION to your Z one by using the transaction SPRO-> personnel management and then HR Administrative Services and then Configuration of Forms/Processes and then execute the Design Time for process and forms.
    select your Process that is HR_MSSRCF_REQUISITION  and copied to your Z one. once you copied then you can given there your own workflow template  and in the form Secnerio you can also given your own customize adobe form.
    In the process start you can assign the role assignemnt to manager then this process would be visible in MSS under manager.
    Hope this would help you.
    thanks,
    Amar

  • How can I have SAP to identify third party new hires as a new employee?

    Hello,
    Situation:
    Our company has changed our vacation quota policy for new hires.  In 2011, new hires did not receive any vacation their first year.  In 2012, that policy has changed to give them vacation based on how many months are left in the year.  Example:
    If hired Jan 1 - June 30 = 80 hrs, July 1 - Oct 31 = 40 hrs, Nov = 24 hrs, Dec = 0 hrs.  I have configured the Rules for Generating Absence Quotas to make this happen, however we've discovered a slight problem.
    If a new hire has never been in our system, the logic works perfectly, however, in the case of third party employees, they are already in the system, thus have a Actions infotype with their third party onboarding hire date. At this point they are defined as employee group = 3.  After 90 days, we hire them as a production employee, employee group = P, so now they are now a company employee.  When they process through the generation rules, the system does not recognize they are a new hire employee because it uses their Actions entry date based on their third party onboarding entry.
    Question:
    When determining seniority, I'd like the system to use their third pary new hire action and not the third party onboarding action. Does anyone have a solution or suggestion?

    I did create a rule to determine if anyone coming through time eval is a new hire based on vacation elig. date in IT0041.  It compares Today to the vacation elig. date and if they match, set a time type indicator to 1.  I also added another decision to determine if they were a part time employee and pro-rate their quota entitlement based on what's in their IT0007 weekly working hours.  Instead of setting the time type indicator to 1, I recalculated based on a percentage of 40 hrs/wk and then updated the time type to that percentage.  In my quota generation rule I use that time type as a multiplication factor to recalculate their new pro-rated amount rounded up to the nearest whole number.

  • HCM Process & Forms: Date & Time Stamp issue in Prev Comments Box

    Hi
    We implemented HCM Process and Forms and we are in EHP4.  We need user name, date and time stamp in each step for audit purpose.
    Form Process Example:
    Step1: Manager -> Initiates a Form for employee pay/position changes  (REQUEST)
    Step2: 1-Up Manager -> Approves a Form for employee pay/position changes (APPROVE)
    Step3: HR Admin -> Process a Form for employee pay/position changes (PROCESS)
    Process Overview: HR Admin can open a form once all steps are completed and they want to see all 3 steps date & stamp here.
    New Comments -> To enter user comments in each step. Used data type HRASR_CURRENT_NOTE
    Previous Comments-> To display prev. step / user's comments including user name, date & time. Used data type HRASR_PREVIOUS_NOTES.
    I tried all different property settings in the form. May be I am still missing some property settings here.
    Issue:  If user enters any comments in "New Comments" box then only date & time stamp is coming along with their comments in "Previous Comments" otherwise not showing anything, just blank in the Prev. Comments.  I added some code in form script in case no data in "New Comments" then default a value ":" . It is working fine for first step but not working the same for other 2 steps.
    Trying in different way:
    Creating 3 text fields in a form just for display purpose and modifying each field (data set) with some text (combination of user name, system date and time) at each stage/step in a BADI.
    Method: IF_HRASR00GEN_SERVICE~DO_OPERATIONS
    Here it is updating correctly for first step/stage (REQUEST) and other 2 fields are not updating accordingly. I did debug for each step and updating the data set correctly but finally not dispalying the valuse in a form except first field.
    Can someone please share your ideas or inputs.
    Appreciate your time & help!
    Thanks
    Hari

    Hi Sahir
    Thank you for your reply.
    As I explained in my post, user details with date & stamp are coming when user enters some comments otherwise it is blank., All users may not enter comments because it is not a "required".
    HR is needed this for audit purpose, just at end of the process they need to see all user names, date & stamp in the form. Forget about comment boxes, Can't we make just simple text fields with user details for each step (all 3 stages)?
    FYI:
    Issue:  If user enters any comments in "New Comments" box then only date & time stamp is coming along with their comments in "Previous Comments" otherwise not showing anything, just blank in the Prev. Comments.  I added some code in form script in case no data in "New Comments" then default a value ":" . It is working fine for first step but not working the same for other 2 steps.
    Appreciate your inputs !
    Thanks
    Hari

  • 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

  • New Hire Data Transfer from E-Rec to ECC via PA48

    Hi,
    We have requirement where we need to use the basic new hire data transfer from erec to ecc using PA48.
    Could someone help me by listing the step by step process that is required to configure in both EREC & ECC?
    I know there is pdf document available online but that refers mostly to XI which we are not planning to use.
    Please help.
    Regards,
    Vikram

    Hi,
    For integration between E-Rec and ECC, check [Link|http://help.sap.com/saphelp_erp2005/helpdata/en/45/8150635e9c40c1e10000000a1553f7/frameset.htm]
    This gives detailed information on synchronous and asynchronous data transfers between E-Rec and ECC.
    Hope it helps!
    Arpita

  • Adobe HCM Processes and Forms Start processes iView error

    Hi,
    We are implementing Adobe HCM processes. The forms based on the PCR technology are working fine. However, we want the new HCM Processes and Forms technology. We have implemented Business packages for MSS, HR Administrator and XSS (PC_GUI). ADS is configured correctly as the PCR Adobe forms are working fine.
    We want to use the WebDynpro version of HCMPF and NOT the ABAP version. When starting the Start Processes IView (sap.com/paasrprocst) we get the error:
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name paasrprocst
    at com.sap.portal.pcm.iview.admin.AdminBaseiView.createAttrSetLayersList(AdminBaseiView.java:361)
        at com.sap.portal.pcm.iview.admin.AdminBaseiView.getAttrSetLayersList(AdminBaseiView.java:205)
        at com.sap.portal.pcm.iview.admin.AdminBaseiView.getCustomImplementation(AdminBaseiView.java:148)
        at com.sap.portal.pcm.admin.PcmAdminBase.getImplementation(PcmAdminBase.java:530)
        at com.sapportals.portal.ivs.iviews.IviewServiceObjectFactory.getObjectInstance(IviewServiceObjectFactory.java:448)
        ... 40 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 1.1.4322; .NET CLR 3.0.04506.648)
    Version null
    DOM version null
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:13:14[UTC], changelist=455669, host=pwdfm101), build date: Sat Jan 19 11:19:58 AST 2008
    J2EE Engine 7.00 patchlevel 109044.44
    Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_12-b03, vendor: Sun Microsystems Inc.
    Operating system SunOS, version: 5.10, architecture: sparcv9
    Session & Other
    Session Locale en
    Time of Failure Thu Mar 13 13:07:45 AST 2008 (Java Time: 1205402865554)
    Web Dynpro Code Generation Infos
    sap.com/pb
    SapDictionaryGenerationCore 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:42[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:50[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:44:42[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:26[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:30[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:23[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:54:53[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:00:50[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
    SapWebDynproGenerationCore 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:37[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
    sap.com/tcwddispwda
    No information available null
    sap.com/pb_api
    SapDictionaryGenerationCore 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:42[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:50[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:44:42[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:26[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:30[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:23[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:54:53[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:00:50[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
    SapWebDynproGenerationCore 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:37[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load page
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:527)
         at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:191)
         at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:748)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: javax.naming.NamingException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name paasrprocst [Root exception is com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name paasrprocst]
         at com.sapportals.portal.pcd.gl.JndiProxy.getObjectInstance(JndiProxy.java:51)
         at com.sapportals.portal.pcd.gl.PcdGlContext.getSemanticObject(PcdGlContext.java:919)
         at com.sapportals.portal.pcd.gl.PcdGlContext.getSemanticObject(PcdGlContext.java:692)
         at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:69)
         at com.sapportals.portal.pcd.gl.PcdURLContext.lookup(PcdURLContext.java:238)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.sap.portal.pb.data.PcdManager.doInit(PcdManager.java:72)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:525)
         ... 31 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name paasrprocst
         at com.sap.portal.pcm.iview.admin.AdminBaseiView.createAttrSetLayersList(AdminBaseiView.java:361)
         at com.sap.portal.pcm.iview.admin.AdminBaseiView.getAttrSetLayersList(AdminBaseiView.java:205)
         at com.sap.portal.pcm.iview.admin.AdminBaseiView.getCustomImplementation(AdminBaseiView.java:148)
         at com.sap.portal.pcm.admin.PcmAdminBase.getImplementation(PcmAdminBase.java:530)
         at com.sapportals.portal.ivs.iviews.IviewServiceObjectFactory.getObjectInstance(IviewServiceObjectFactory.java:448)
         at com.sapportals.portal.prt.jndisupport.DirectoryManager.getObjectInstance(DirectoryManager.java:56)
         at com.sapportals.portal.pcd.gl.JndiProxy.getObjectInstance(JndiProxy.java:47)
         ... 38 more
    Can anyone tell me more about the cause this might have? Also, are there any further prerequisites for this iView to work?
    Any help will be appreciated and rewarded accordingly.
    Regards,
    Thomas

    hello,
    how did you solve it ?
    Regards,
    Dimitry Haritonov

Maybe you are looking for

  • Mixing 4:3 and 16:9

    Hi Guys I'm working on a 16:9 project and I have new material shot with my Sony Z1E (16:9) and old material taken on a little Panasonic (4:3). On screen the Panasonic footage doesn't stretch to fit the screen. Will it all render to the same dimension

  • File Sharing creamed two Macs

    How we creamed two Macs running Leopard, and how we got them back. My husband got a new early 2008 MacPro and gave me his iMac. Initially we tried to use the Migration Assistant to move his data, but that hung, and caused us to have to start over. Th

  • Linking to a streaming video chapters..

    Hi all: What I am wondering if it is possible to do: I will have a quicktime file of a meeting on my server I want to put chapter markers into the quicktime file that is on my site, and then link to the chapter markers - so that viewers could click a

  • Moving Photoshop Elements & files from Windows XP to 8.1

    After a major upgrade of my pc I temporarily have PSE (10) on a drive running on an XP platform, with all my photos on a separate "data-drive". Question:  How can I best make programme and files work together on my new Win8.1-platform/drive without l

  • I can't find the remove application option on the NWA

    I'm developing an EJB 3.0 project using NWDS 7.1 SP05 and I need to remove my EJB application that deployed earily and not used anymore on the J2EE server. I remember that I used to remove my application in the Deploy service using the remove option