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.

Similar Messages

  • 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

  • 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

  • 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)'/>

  • 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

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

  • Workflow creating new name when Publishing

    Hi team,
    I am having an issue with workflows really weird.
    I would edit the workflow to change a setting on the (for example, change who the workflow would send an email to) the workflow and publish it, the name of the workflow would change and add a parentheses to the workflow.
    For example, Email TEST would change to Email TEST (1), Email TEST (2), etc.
    Because of this, there are 4 workflows in progress. The old ones and the new ones and the users will get 4 emails from all 4 workflows. Granted, changes to the workflow would be made while the workflow was active.
    In designer, if I click on one of the Email TEST(1), it would open the original Email TEST. If you try to run the workflow manually, all the workflows appear as choices to select from. It’s like it creates a completely new workflow, however when you open
    it designer it still reverts to the original one.
    when we delete all workflows in Progress, and change who the email is being sent to, it still creates a new name of the workflow.
    In the test environment, we terminated all the workflows. Modified the Send email to user, and published it. It would change the name to Email ATAM (1), while the original workflow still had the same changes.
    Ideas??

    Hi,
    Whenever you publish a SPD workflow, it will add a new instance of the workflow with (n) added to the new instance.
    Usually, the old instance will not be active, if active you can still remove the instances on the same page you have attached.
    One suggestion is to remove all the previous instances of the workflow and publish the new workflow and assign it to the list / doc lib.
    While editing the workflow, it always edits the actual workflow that you have developed using SPD.
    I think its little confusion with Workflow instance that was assigned to the list and workflow that you are editing using SPD.
    Hope this helps!
    Ram - SharePoint Architect
    Blog - SharePointDeveloper.in
    Please vote or mark your question answered, if my reply helps you

  • Workflow for new starters/leavers

    Hello All,
    I am new to workflow.  I have a requirement to send an email to an administrator when a new starter is employed and when an employee leaves.
    Any ideas on how to do this?
    Thanks,
    Nick.

    hai nick bligh 
    Follow SDN sdn and do practice
    For more information look at these links
    Here is a step by step document to create a workflow:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/fb/135983457311d189440000e829fbbd/frameset.htm
    Workflow tutorials with step-by-step and with screenshots are available at
    http://www.****************/Tutorials/Workflow/Workflow.htm
    Workflows for Dummies - Introduction(Part I)
    /people/sapna.modi/blog/2007/02/19/workflows-for-dummies--introductionpart-i
    Workflows for Dummies - Workflow Builder(Part II)
    /people/sapna.modi/blog/2007/04/27/workflows-for-dummies--workflow-builderpart-ii
    regards
    rose.

  • New ASUG Workflow and BPM Chairperson

    Allow me to introduce myself as the new ASUG Workflow and Business Process Management Chairperson. I am happy to be able to give some time back to ASUG to help promote SAP workflow and process automation as it has been a significant part of my career.  I have been working with SAP or
    using one of its many products since 1995. I started off as a workflow developer and then moved into IT management.  During my career I have
    implemented or used many SAP applications and have always been involved in process re-engineering.  If you would like to learn a bit more about SAP workflow please check out our upcoming webcast on August 4 – Workflow Classics II.  This is a follow up webcast that highlights out of the box SAP workflow automation capabilities and how easy it is to implement them.  You must be an ASUG member to attend this event.  The link to register is  https://www.asug.com/events/detail/Workflow-Classics-II.  If you are interested in learning more about workflow or even presenting on what you have accomplished using workflow feel free to reach out to me.

    Please ask only one (or closely related) questions per thread. This makes it a lot easier to get a good structure in the database of previously answered questions. While we are on the subject of previously answered questions, I think you should have a look at them....
    My suggestion is therefore:
    1. Close this thread
    2. Read the Frequently Answered Questions. Before you ask (here are many workflow answers)
    3. Search the forum.
    4. Create new threads if you have questions afterwards.

  • 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

  • Process Controlled Workflows VS Applicaiton Enabled Workflows-What to chose

    G'Day All,
    We are upgrading from SRM5.0 to SRM7.0
    There are these bespoke shopping cart approval workflows developed previously. I have to do some sort of assessment to include
    1) Why would we go for PCWs instead of just migrating the old ones in SRM 7.0 as business is pretty happy with the functionality they have got and are not interested in revising the workflow processes. Answer :  Application enabled workflows are in maintainence mode so newer functionality would be delivered using PCWs.( is there any other justification ? )
    2) Would we be able to map the existing workflow process to PCWs, here i need some pointers. I understand the PCWs are based on BRF though i don't know much about BRF( updating myself ). The key question i have is, whatever is there in bespoke workflow templates would i be able to  replicate that using this i.e. a different technology. Since my exposure to either PCWs or BRF is not great so as a general rule i am asking, is it possible or are there any sort of technical limitations on what you can and what you can't do using PCWs which you could design using a normal workflow template?
    I am sure this would be a common analysis which many of you might have done or are doing if you are involved in an upgrade.
    An Interesting Fact : There is no documentation available on existing SRM 5.0 workflows as what differently they have done to standard. The only thing i know at this stage is they have a bespoke level 1 template which call different standard templates for n level approval process. The apporval process( agent determination ) is based purely on custom logic. I am not that worried about the agent determination as i know i could get that as rule evaluation in BRF. The crux for me is to understand how BRFcontrols or connects to workflow templates in this particular case and what permutation conbinations are possible.
    So, i want to have a discussion on this and if possible some insight on all this new PCWs.
    Hope to see some valuable comments.
    Regards
    Praveen

    Hi everyone:
    My question is the following.
    We will implement SRM 7.01 with Process Controlled Workflow.
    However in the manual is the following note:
    Note: Even if you decide to use Process-Controlled Workflow in general,
    there are a few workflows still on the old technology:
    WS10400022 . Contract Alert Workflow
    WS10000192 - Approval Workflow for Internal Users
    WS10000209 - Approval workflow for new bidder/supplier     
    WS10000093/WS10000100 -Procurement Card Approval
    Probably We will required some of this.
    My question is if we are planning to configure process and application the correct strategy will be:
    1.     Start the configuration with the application controlled workflow and then
    2.     Follow with the change of the configuration application to process controlled workflow
    3.     And configure the workflowu2019s in process.
    u2022     Is there any problem when if we change the check  application to process?  Are there any chance that we loss the configuration?
    u2022     Is there any problem in the functionality that both kinds of workflow (application-process) work at the same time?
    u2022     If is possible to make change or maintenance of the application workflow?
    Thanksu2019 a lot for all the help
    Best Regards

  • Sharepoint 2010 Workflow successful: Sharepoint 2013 Workflow UNsuccessful:

    Observation 1 
    1. I created 2 workflows that write "completed" to the workflow history 
    a. 1 workflow uses sp2010 workflow manager 
    b. 1 workflow uses sp2013 workflow manager 
    2. sp2010 workflow works fine; it will start either manually or automatically (when a new item is created ) without issue; "completed' is written to the log as expected. Good. 
    3. sp2013 does not start automatically (when a new item is created ); when trying to start manually I get error message "Something went wrong. To try again, reload the page and then start the workflow." Which I do, but still fails.
    Bad. 
    4.On Workflows.aspx I can see the links to start the 2 workflows manually. 
    a. When I hover over the sp2010 workflow link I can see something that look like this: 
    http://playground/sites/falcontt/_layouts/15/IniWrkflIP.aspx?List={ae95de8e-508b-4aa6-b4b6-490288e35e9f}&ID=53&ItemGuid={697E4218-D889-4FB8-A27B-D188F5D93250}&TemplateID={199c3d86-89a8-4286-b285-37e2d2067b52}&Source=http%3A%2F%2Fplayground%2Fsites%2Ffalcontt%2FLists%2FTrouble%2520Tickets%2Fall%2520requests%2Easpx 
    b. But when I hover over the sp2013 workflow link I can see something that look like this: 
    javascript:StartWorkflow4('949cb889-9b46-4959-9673-842e60cc5a42', '53', '{697E4218-D889-4FB8-A27B-D188F5D93250}') 
    Should this link also look similar to the sp2010 workflow link? If so, do you have any idea why it is different? 
    Observation 2 
    In Sharepoint Designer 2013, when I goto Navigation -> Workflows and click on the 2010 workflow, I see a file listed under "Forms" that looks like this "sp2010 test workflow.xsn". By the way the name of the workflow happens
    to be "sp2010 test workflow". 
    But when I goto Navigation -> Workflows and click on the 2013 workflow, I see a NO file listed under "Forms". Should I see "sp2013 test workflow.xsn" listed there? If yes, can you think of why it is not listed there? 
    I saved the workflow debug logs from Event Viewer but won't share that info here unless necessary, to avoid making things look more complicated than they have to be. 
    Thanks for any comments suggestions, tips, questions, anything, etc. 
    Thanks and have a great weekend. 
    George 

    Hi George,
    First of all, I'd like to clarify that workflow manager is dedicated for SharePoint 2013 workflow platform. SharePoint 2010 workflow is integrated in SharePoint server, while 2013 workflow is based on a new platform named workflow manager server.
    In SharePoint 2013 designer, 2010 workflow has forms while 2013 workflow doesn't have forms.
    For this issue, I suspect there is something incorrect with workflow manager. From the error message "Something went wrong. To try again, reload the page and then start the workflow",  please flush the DNS cache via executing
    IPCONFIG /FLUSHDNS, and restart workflow manager related services such as below, then recreate 2013 workflow to test the issue:
    Service Bus Gateway
    Service Bus Message Broker
    http://blog.houratious.com/2014/05/sharepoint-2013-workflow-something-went.html
    Regards,
    Rebecca Tu
    TechNet Community Support

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

Maybe you are looking for