New Hire Workflow

Hi Experts,
I am using the Standard New Hire Workflow (WS17900011) with the Generic Services for the Back end update. First level will be the HR Administrator and then need to save the data. We have initiated the process through PORTAL and successfully sent the work item to the HR Admin. Whenever we tried to execute the work item in the Portal it's giving  the dump, stating as
'The exception 'CX_HRPA_INVALID_PARAMETER' was raised, but it was not caught
anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CL_HRPA_RESOLVE_EXCEPTION=====CP' has to be
terminated.
Then i have changed the workflow first step as SAVE and the HR Admin, if we are doing this its working fine... But as per the requirement we cant follow this...
Please kindly let me know how to proceed.
Thanks,
Srikag
Edited by: SRIKAG on Oct 4, 2011 9:04 AM

Hi
  Try to execute the process from HRASR_TEST_PROCESS and check.also make sure that you include the program exit CL_HRASR00_POBJ_WF_EXIT  in the basic data  of the copies workflow template and also the task which you are sending to the workflow administrator. What is the name of the program exist class please check the standard workflow template . Might be this could be the issue.
Regards
Pavan
Edited by: Pavan Bhamidipati on Oct 5, 2011 6:58 AM

Similar Messages

  • Including Bank Workflow in New Hire Workflow

    Hi Experts,
    I 've a requirement to include the bank (pay details) workflow in the new hire (HRSSA) workflow. While trying to embed the bank details process in HRSSA, I noticed that the new hire record is getting committed upon navigating out of the bank details page and a new HR API TRANSACTION (id) is initiated starting from the bank details page.
    Has anyone faced a similar issue. Can you please share any pointers on how to achieve this/ resolve the commit issue. The customer is on 12.0.4 version. Any pointers on how achieve this (and get rid of the commit issue) will be immensely helpful.
    Thanks,
    Ganapathi

    It was documented in 9.3.1:
    http://docs.oracle.com/cd/E10530_01/doc/epm.931/hp_93100_readme.pdf
    Under task list:
    If you select a task and see the message, "Loading the requested task - this may take a moment..." for a long time, select the task list itself (the top-level folder), and then select the task again. (8-539094369)
    I guess you are on 11.1.2.x, need to check.
    Cheers..!!
    Rahul S.

  • 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

  • SSHR - MSS ICD (Individual comp Distr) if chained in Hire workflow commits

    hello -
    I have inlcuded the ICD(Individual Compensation Distribution) workflow function inside the seeded Hire workflow processes.
    the seeded sequence is -
    Emp Details > Asg Details > Pay Rate > Change Manager > Review
    I have customized it to -
    Emp Details > Asg Details > Pay Rate > ICD> Change Manager > Review
    However, I as soon as I am moving from the pay rate page to the ICD page, the data is committed to the tables and there is a row in the per_all_people_f table with null employee number. The same behavior is replicated if ICD is after the change manager function. Upon submitting the workflow background process, the a new row in person table is getting generated with a valid employee number.
    Please advise whether I am making some error in the chaining process , or do we need to set up some attributes differently to prevent this commit. Or is this a bug with Oracle.
    Page 8 of chapter 1 ( Page 40 in document SSHR User guide version 4.2 ) says that ICD workflow is chainable, hence I am trying to chain this function in the Hire Process between the pay rate function & Change Manager Function.
    Edited by: Tushar Kumar on Jan 26, 2010 2:33 PM

    Hi Vinayaka -
    Thanks for your reply. It does provide me some insight into the reasons for this behavior, however when I searched for the participation process requests submitted in the last 2 days, I could not find any request related to the participation process.
    Also, I tried to include the ICD in the Worker Status Change ( WSC ) Process, and it works perfectly fine there. If the participation process runs in commit mode, then half of the data entered in the pages prior to the ICD page should be committed, is this not correct ? But in WSC, it does not commit the data.
    Hence, I am not too sure whether this is the intended functionality or whether it could be a bug.
    Please do let me know your thoughts.
    Thanks
    Tushar

  • 11.1.2 - Workforce and CAPEX issue - Add New Hires and Add New Asset Rules

    Hi All,
    We are working on Oracle Fusion 11.1.2 and are using the out of box functionality for Workforce and CAPEX.
    We are facing a weird issue in case of the above Modules when we try to Add a new Hire or a new Asset in the respective modules using the Add TBH Hourly , Add TBH Salary and Add Asset rules.
    The Issue is sometimes the correct number of New Hires or Assets is added as specified in the prompt. For instance, if specify Number of New Hires as 5, then 5 rows of TBH are added on the web form dynamically with other employee properties populated on the form as mentioned in the prompt. However, at times this does not happen, so if I specify 5, 4 rows are added, if I specify 15, 7 rows are added and so on.
    The out of box rule looks okay, we are not sure why this should happen?
    Has anyone of you faced a similar issue, It would be really helpful if you can share your thoughts.
    Thanks a ton in advance.
    Madhavi

    Have you try to check the related Business Rule? In older version Add TBH menu related to a Business Rule. Never configure this module on 11.1.2 but maybe the add tbh menu related to a Business Rule or Script on Calculation Manger

  • 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

  • HR_MAINTAIN_MASTERDATA: Not Able to Create a New Hire Employee

    I am trying to create a new hire employee. To do this, I use FM HR_MAINTAIN_MASTERDATA.
    The requirement is to create new employee with data for IT0000 (Actions), IT0001 (Org Management) & IT0002 (Personal Data) only.
    The FM is not working and the given error is "Fill in all required entry fields". When I use parameter DIALOG_MODE = 1 (stop on error), SAP stops on the infotype 0006 screen and prompts me to enter the required fields. The problem is I do not want to create employee data on infotype 0006 and the following screens after that. My intention is to create employee
    data for infotype 0000, 0001 & 0002 only.
    Any idea on the workaround for the problem above?
    Filled the proposed_values tables with following fields:
    IT0000 ***
    'P0000-MASSN'
    'P0000-MASSG'
    'P0000-STAT1'
    'P0000-STAT2'
    IT0001 ***
    'P0001-BUKRS'
    'P0001-WERKS'
    'P0001-BTRTL'
    'P0001-ABKRS'
    'P0001-PLANS'
    'P0001-OTYPE'
    IT0002 ***
    'P0002-NACHN'
    'P0002-VORNA'
    'P0002-CNAME'
    'P0002-TITEL'
    'P0002-GESCH'
    'P0002-GBDAT'
    'P0002-NATIO'
    'P0002-SPRSL'
    'P0002-KONFE'
    'P0002-FAMST'
    'P0002-GBJHR'
    'P0002-GBMON'
    'P0002-GBTAG'
    'P0002-NCHMC'
    'P0002-VNAMC'
    CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
    EXPORTING
       pernr                             = p_pernr
       massn                           = '01'
       actio                              = 'INS'
       tclas                              = 'A'
       begda                            = p_begda
       endda                            = p_endda
      *objps                              =
       seqnr                             = '000'
      *sprps                             =
      *subty                             =
       werks                            = 'US01'
       persg                             = '1'
       persk                             = 'EC'
       plans                             = '00042933'
       dialog_mode                  = '1'
       luw_mode                     = '1'
       no_existence_check     = 'X'
      *no_enqueue                 = 'X'
    IMPORTING
       return                            = lt_bapireturn
       return1                          = lt_bapireturn1
      TABLES
       proposed_values          = lt_value.

    In the methode VIEKN of the class CL_HRPA_VIEKN there is a test to see if PA0003 exists before it is created.
    Use the enhancement to INSERT PA0003 at the begin and to DELETE PA0003 at the end.
    METHOD viekn.
    """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""$"$\SE:(1 ) Classe CL_HRPA_VIEKN, Méthode VIEKN, Début D
    *$*$-Start: (1 )--------------------------------------------------------------------------------$*$*
    ENHANCEMENT 1 ZDIH_APPLICATION_EXTERNE_CREAT.    "active version
    DATA : lw_pa0003 TYPE pa0003.
    DATA : fl_pa0003 TYPE flag.
    CLEAR fl_pa0003.
    *  If coming from Web dynpro
    IF sy-cprog EQ 'SAPMHTTP' ANd pernr NE '00000000'.
    *  Check if the infotype 3 already exists
      SELECT SINGLE * FROM pa0003 INTO lw_pa0003 WHERE pernr = pernr.
      IF sy-subrc NE 0.
        fl_pa0003 = 'X'.
        MOVE pernr TO lw_pa0003-pernr.
        MOVE '18000101' TO lw_pa0003-begda.
        MOVE '99991231' TO lw_pa0003-endda.
        MOVE '12' TO lw_pa0003-viekn.
        INSERT pa0003 FROM lw_pa0003.
      ENDIF.
    ENDIF.
    ENDENHANCEMENT.
    *$*$-End: (1 )--------------------------------------------------------------------------------$*$*
    ----> original code of method <----
    """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""$"$\SE:(2 ) Classe CL_HRPA_VIEKN, Méthode VIEKN, Fin D
    *$*$-Start: (2 )--------------------------------------------------------------------------------$*$*
    ENHANCEMENT 2 ZDIH_APPLICATION_EXTERNE_CREAT.    "active version
      IF sy-cprog EQ 'SAPMHTTP' AND pernr NE '00000000'.
        IF fl_pa0003 = 'X'.
          DELETE FROM PA0003 WHERE pernr = pernr.
        ENDIF.
      ENDIF.
    ENDENHANCEMENT.
    *$*$-End: (2 )--------------------------------------------------------------------------------$*$*
    ENDMETHOD.

  • Error On Creating New 2013 Workflow

    Hi;
    When i create a 2013 workflow on English site, everything is OK;
    But on creating 2013 workflow on non-English site (with language pack installed), i get following error:
    Server-side activities have been updated.You need to restart SharePoint Designer to use the updated version of activites.
    i delete sharepoint designer cache but nothing changes.
    any ideas?

    Hi,
    According to your post, my understanding is that you failed to create new 2013 workflow.
    Please make sure you have downloaded the correct version of SharePoint Designer 2013. You can download it via the following link:
    http://www.microsoft.com/en-us/download/details.aspx?id=35491
    Please troubleshoot for Workflow Manager 1.0 publishing, management and execution. You can refer to
    http://technet.microsoft.com/en-us/library/jj193529.aspx
    Here is a similar thread for your reference:
    http://social.msdn.microsoft.com/Forums/sharepoint/en-US/f255f4b4-1828-4ccb-983a-5efbf0e020ae/sharepoint-designer-2013-server-side-activties-have-been-updated-prompt?forum=sharepointcustomization
    Best Regards,
    Linda Li
    Linda Li
    TechNet Community Support

  • 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

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

  • HR Report for finding details for the new hires and leavers

    Dear All,
    I am very new to SAP HR ABAP.
    Need Help
    I have to create a report which fetches all the details <Details are mentioned below>
    for all the
    1)     New hires
    2)     Leavers
    in between a time range.
    <Details to be fetched :~ 
    Title
    Fax
    Mobile
    Nationality
    Domicile
    Religion
    Passport
    Place of issue
    Issue date
    Valid till
    Date of Hire
    Action Reason
    Reporting to
    Date of exit interview
    Leave Date
    Leaving Reason
    Street
    Address Line2
    City
    District
    Region
    Country
    Postal Code
    Communication Number
    Personal ID
    Date Of Last Hire
    Location
    Job
    Payroll area
    OrgLvl1
    OrgLvl2
    OrgLvl3
    OrgLvl4
    Personnel Number
    Date of seniority
    EEBankName
    Bank account no
    Bank account type
    PERID
    Thanks a lot !!!
    Joy
    Edited by: joydip majumder on Jul 11, 2008 10:46 AM

    Hi  joy ,
    you can create ur own z-report for this requirement  , for this u have to  read the  employee data with in the date rage for   infotype 0 (Action) for hiring and leaving dates. Other related infomation  u can fetch from the related infotypes tables like PA0001 etc using simple select queries.All required fields can be dispalyed in the  ALV output.
    Regards
    Lakhan
    Edited by: lakhan on Jul 11, 2008 2:35 PM

  • I am new to workflow and I have and issue

    Hi Experts,
    I am very new to workflow and Ive got an issue which I need know where to start with.
    I am working with an application whose UI is Java and back end is SAP.
    When a sales order is created in the UI this creates a order record in SAP and triggers a business object which inturn calls the func module SWE_EVENT_CREATE for initiating the workflow.
    The workflow sends a mail in which the data is coming wrong in the preview mode(i.e whn u single click on the message it appears at the bottom ) and when u double click on the message u can find correct info.Y its like that ?
    Any ideas??
    Neeraj

    Hi,
    Neeraj not in perticular that case but in every case when you click once it will appear at bottom and when you double click on it it gives you a pop p window which helps you to see whole message.
    So,It's a functionality Dear nota problem.
    Hope you understand.
    Regards,
    Purvesh.

  • Replace AR Credit Memo Request Workflow with a new Custom Workflow

    Hello friends,
    We have a business requirement to replace the AR Credit Memo Request Workflow with a new Custom Workflow whenever an Invoice is disputed (Oracle Advanced Collections).
    The Credit Memo Request workflow is being launched within the Oracle API arw_cmreq_cover. We thought of an approach wherein the Oracle form IEXINDTL.fmb can be renamed and the Custom workflow to be called in the WHEN-BUTTON-PRESSED trigger on Dispute Button instead of calling the program Unit IEXINDTL_CONTROL.DISPUTE (as in standard form) which inturn calls several API's and hence the AR Credit Memo Request Workflow. But this would override the other standard processes being carried out in these API's. Our requirement is to only replace the AR Credit Memo Request Workflow and not to override the other standard processes.
    Does anyone have come across the similar requirement? Please let us know your inputs.
    Thanks in Advance !

    I ran across the same error today. Since it's been over a month, I assume you've fixed it already or decided you didn't need it at all? What was your fix?
    For me, I noted that in the sample directory, a similar "createView" call (in End User Anonymous Enrollment) also includes this argument:
    <Argument name='viewId' value='User'/>
    When I added that to my createView call, the "Missing view id" error went away, and the user are gets created.
    I'm not entirely comfortable with the value specified, though; seems like view IDs should be more unique. I would have thought it should have been something like this instead:
    <Argument name='viewId' value='User:$(accountId)'/>

  • Can we create a fillable W4 form for new hires and sign it electronically

    Can we create a fillable w4 form for new hires.  can the new hire sign electronically and what is the cost for having electronic signatures?

    We don't support electronic signatures. You should check out our sister service Adobe Echosign - www.echosign.com

Maybe you are looking for