Lock Actions in PA40

HI Folks,
We have a new requirement in our role redesign project that Iam working on, where in a particular users in a business group should not be able to do certain actions in the pA40 screen. Restricting at the infotype level is not the answer because for allowing them to do a certain action which need ITs X, Y and Z is also letting them perform any actions that would involve ITs X, Y and Z. The Business is able to complete some other actions as well, which we donot want them to perform. Is there any way of restricting/ providing additional security to  a selected actions in the PA40 screen. Smillar thoughts on the PA30 menu tabs as well is appreciated.
Any and all thoughts on this concern is highly appreciated!

Hi Madhavi,
The problem is with the P_ORGIN, if you have the Auth Level W for the infotypee 0000(actions)
then he will be able to perform the action tryby removing that n let me know, it should work.
Also if you want him to perform some actions then for IT 0000 adjust the subtype accordingly.
Say for Hiring action you need a combination of 0000 with Subtype 01 with Auth level write.
Hope this helps
Message was edited by: Manohar Kappala

Similar Messages

  • Appraisals having error "Unable to lock action log, Please try again"

    Hi all,
    We have some appraisal issues wherein most of the appraisal docs under certain appraisers cannot be opened.  We are receiving error "Unable to lock action log, Please try again".  Would anyone have an idea where to look in order for us to fix this problem?

    Hi Maria,
    Are you able to resolve this issue ? If yes, can you share your findings and solution, please ? Thank you.
    Regards
    Kir Chern

  • How we can arange the personnal actions in PA40 ?

    Hi SAP HR Experts .
    Plz Explain me How we arrange the personnal actions in PA40 ?
    can we change thier order or delete perticular action ?
    or it is managed through some config settings ????
    Kind Regards : rajneesh

    u need to arrange the infotypes in an order by useing proper operations
    check the following tables
    VV_T588C_G_ALO
    V_T588D   here u need to do some settings regarding infotypes operations
    V_T529A
    V_T530VV_T588C_M_ALO
    V_T588B_M
    check this tables with ur functional consultant as ur from ABAP HR

  • 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

  • CHARM: Lock actions if the same role is used

    Hi,
    is it possible to lock the actions, when a user is (e.g.) change manager and developer at the same time?
    in some our department it is possible that to different users got the role change manager and developer, but we dont want let one person commit changes and develop at the same time.
    kind regards
    dirk

    Hi Dirk,
    you could create a scheduling condition for the action that makes the action not show up in the action dropdown if the change manager and developer are the same BP.
    regards,
    Jason

  • Dynamic  Actions - only PA40 ?

    Can we use dynamic actions in PA30... or is it juust dedicated to PA40/Actions ?
    Thanks in advance

    If you want the spro path
    Personnel management -
    > PA -
    >customising procedures --->dynamic actions
    For recruitment
    Personnel management -
    > Recruitment -
    > dialog controls -
    > create
    dynamic actions for recruitment.
    All of them get stored in T588Z.
    Kindly reward in case useful.
    Regards & Thanks,
    Darshan Mulmule

  • Skip by default 0000 (Actions) from PA40 and shows any other like 0185.

    Hi Gurus.
    As you know, in PA40, its run infotype 0000 bydefult before executing any other defined infotype.  I would like to skip 0000 and want to run first 0185 then 0000 and after that any other infotype.  This is because when by default pa40 call 0000 (action) its first create employee then execute other infotypes in a sequence.  To display 0185 bydefault is to check first employee id either its exist in sap or not then proceed other infotypes. 
    Thanx and waiting for response.

    Thanks, Jim!
    So, here’s how I understand the steps I need to take:
    Create 6 slides, one for each question. Create captions and other elements to frame the question.  Create a Text Entry Box, one on each of the question slides, where the user will record their answer to each question.
    Create a caption on the first question slide where the total score will be compiled. Display this object for the rest of the project.  Type $$v_total$$ in the text of the caption.
    Create one variable for each question.
    Create an advanced action that adds all of the associated variables into the v_total variable.
    Apply the advanced action to the appropriate quiz slides.
    I was able to duplicate what you sent me, so I know that it works.
    One follow-up question:  If users want to retake the quiz, I need another action that will reset the v_total variable to zero, right? Where do I apply this advanced action?

  • Changes needed in OM while performing Actions in PA40

    Hi,
      I am new to SAP...I need to run an "Organizational change" action type. The action reason is "title change" . Can anyone let me know what are the changes need to be done in PA and OM to run this action?
    Best Regards,
    Satish

    Hi Satish
    Organization Reassignment Action is generally used when the employee gets transferred, gets promoted etc. This action allows changing IT0001 for the employee where you would be able to change his position, job, personnel subarea, payroll area etc. Along with IT0001 you are also allowed to change IT0007, IT0008 etc.
    When you execute this action in PA, the changes get reflected in OM as well provided your PA+OM integration switch (PLOGI + ORGA) is ON in table T77S0.You will not need to make any change in OM separately after executing this action if this intergration switch is on.

  • Text not getting displayed in PA40 action.

    Hello All,
    We upgraded from 4.6 to 5.0. When I doing the hiring or any other action, the text for the action type, reason for action or any other field is not getting displayed. Even when I select the entries the text for that is not getting displayed.
    like its displaying only 01- for Action type hiring.
    Thank You all in advance for your reponse!
    Chakri.

    Hello Sharath,
    I checked this and this table is having all the values properly maintained. Language, Action, Name of the action is maintained. Is there any place where we need to activate this in order for us to see the name of the action type also when we select an action in PA40.
    Thanks a lot for your response.
    Chakri.

  • How to retrieve the action type of a PA40 action?

    Hi there,
    I am trying to find out the way to identify what was the action type for the personnel action that is just being executed. I will try to explain myself with a concrete example.
    Let's take the hiring action.
    A user goes to PA40 and initiates the action to hire a new employee. The program will then start guiding the user through the different infotypes defined within the infogroup.
    Let's say that the order is IT0001, IT0002, IT0006, ...
    I have setup table T779X to call a Function Module of my own after inserting IT0006. At that point in time I can know that the IT has been modified through transaction PA40 (sy-tcode) but, how can I know what action is being executed?
    Thanks

    Jim,
    Actions can always be found afterwards in IT000 indeed
    My problem is that I need to know what action type was initiated in REAL TIME. When I am debugging the batch for IT0006, after the user initiated an action through PA40
    Thanks for the answer anyway

  • Personal Actions (PA40)

    There is always a strong possibility to create new future Personal Actions with PA40 transaction. The system may allow you to do this but unfortunately, when this actions are done and one personal action is intersperse between the future one and the last one created, the last Personal Action created in time (the future one) is inconsistent.
    Is there any way to avoid this to happen ?
    Thanks very much for your help in advance.

    I dont see any reason there for this to be inconsistent- Please note that, Only those actions that change the Employment Status of the Employee need to be stored in the Actions Infotype- for all other actions, please use the Additional Actions Infotype.
    Now, Actions IT has a time constraint of 1- which means, there can be only one record at all times- so, when you execute a future dated action, it would accept it and when you execute another action before the date of the future dated action, the future dated action gets superceded with the new action- which makes perfect sense.
    Or, if you have any specific scenario that you are facing, please share that here.
    Regards,
    Krish

  • Default Reason code in IT0008 during PA40 Actions

    Hi,
    My requiremnt is default the reason code in infotype 008 during actions in PA40. Itshould be same as the one the user selected during the initial Action screen.
    For Eg: Suppose user is selected the '01' as reson code in the initial action screen during the Hiring action, then when IT0008 appears, reason code should be defaulted as '01'.
    Pls share any idea to do it.

    Hi,
    I have got the user exit for poulating the data. But the problem is how to get values from the screen  for Infotype 0000  to screen for infotype 0008. Since the user may not save the data in 0000.So we can't read it from database.

  • Info group being not called while using Dynamic Actions

    Hi,
    I am facing a scenario that, while we execute some action from PA40 like termination, then it will call my subroutine for dynamic actions which will be calculating the last day worked and updating the same in Info Type 0041.
    For updating the IT 0041, i am using the function module HR_MAINTAIN_MASTERDATA. and IT0041 is getting updated properly. But now the problem is coming that when the control comes out of subroutine, it is going back to the PA40 Screen and not to the next screen of the Info group.
    What can be the cause for the same.
    RND I have done on my part: I have commented/uncommented the return parametre RP50D-Date1, commented/uncomented the use of function modules to lock and Unlock the pernr.
    Please give ur comments.
    Thanks in Advance.

    Hi Nisha,
    Not sure if I have understood correctly, but if you just wanted to calculate leaving date and write the same date in IT0041 then you don't need a function module:
    1. Create a small program, as follows:
    REPORT  ZHR_PY_R0008                           .
    INCLUDE MPPDAT00.
    TYPE-POOLS HRQTA.
    TABLES: P0000,
            RP50D,
            T001P.
    ROUTINE CALLED BY TABLE T588Z
    FORM CHANGE_DATE.
      RP50D-DATE1 = P0000-BEGDA - 1 .
    ENDFORM.                    " CHANGE_DATE
    This program will give you the last working day written to RP50D-DATE1
    2. Simply enter the following lines into table T588Z:
    0000 04 499*- LEAVING ACTION - Populate Infotypes with leave date -*
    0000 04 500 P T001P-MOLGA='08'
    0000 04 501 P PSPAR-TCLAS='A'
    0000 04 502 P PSPAR-MASSN='*'/X   (* equals your leaving action types)
    0000 04 503 P PSPAR-MASSN='*'/X   (* equals your leaving action types)
    0000 04 504 F CHANGE_DATE(ZHR_PY_R0008)
    0000 04 505 ******** INF.0041  ********
    0000 04 506 I COP,0041,,,(P0000-BEGDA),(P0000-ENDDA)/D
    0000 04 507 W P0041-DAR07='*'   (* equals your date type)
    0000 04 508 W P0041-DAT07=RP50D-DATE1
    or if you are simply looking to delimit IT0041 with the leave date then replace lines 506-508 with:
    0000 04 506 I MOD,0041,,,(RP50D-DATE1),(RP50D-DATE1)/D
    0000 04 507W     P0041-ENDDA=RP50D-DATE1
    This will solve your problem : - )

  • Detailed info on Leaving /Separation Action

    Hi Folks,
    I would like to know how Leaving/separation action works in PA, and what happens after that in-terms of Full & Final Calculation.
    if the scenario is as explained below;
    An employee's last date in company is 15.03.2008 and this 15 days he has worked has to be calculated as his/her full and final settlement.
    Action:
    Run Leaving/separation Action in PA40 effective 15.03.2008, Delimit all his records (Pls specify what all Infotypes has to be dellimited and what all infotypes should not be delimited)
    I would like to know what happens after this...?
    How would his payroll be run for full and final settlement calculation...?
    points will be rewarded.
    regards,
    Santhosh

    Hi TS,
    Appreciate your answer, it is more detailed.
    One more Info FYI - IT0007 should also not be delimited, other wise payroll while running throws error.
    regards,
    Santhosh

  • Locking Selected Fields on Submit

    Hello,
    I've been working on a multiple-item quote request form. My intention is that Party A (Requestor) will fill in the item description and details necessary for Party B (Vendor) to provide a quote. The form will be emailed to the Vendor who will complete the remaining fields (price and delivery) and email the form back to the Requestor.
    The item description and details (provided by Requestor) and the item price and delivery (provided by Vendor) are both wrapped in thier own subform and both are contained in a repeating subform. I've scripted the buttons that add/delete instances of the subform for each separate item being quoted and the button that emails the form to the Vendor. It took me a long time, but I finally got the buttons to work!
    Now I'd like to find a way to 'lock' the fields filled by the Requestor when the form is emailed but still leave the fields open that need to be completed by Vendor. I'd also like to lock the contact information fields at the top at the same time. I've attached a JPEG with the form layout to clarify...
    I've been reading a lot of old posts regarding similar topics and tried some of the solutions provided but cannot seem to make them work for my application. The closest I've been able to come is locking the entire form. I have the form set to email on event=click of the "Submit to Vendor via Email" button and the locking action on the event=mouseup of the same button.
    Does anyone know how I should approach this? I'm begining to think I designed my form and myself into a corner! Unfortunately I do not have a server on which to host the form but would be happy to email it to anyone willing to help.
    Thanks,
    Jake

    I dont know what I was thinking.  After some rest, and a second look, I can see this what the code is doing.
    I am trying to provide a button that will lock elements on individual pages that are part of multiple instances. Note, each instance will contain said button.
    Example: TRANSMITTAL[3].lockButton should only lock items on that instance of  TRANSMITTAL[3].
    The two attempts had different results
    form1.TRANSMITTAL.lockButton::click - (JavaScript, client)
    var j = _TRANSMITTAL.count;
    for (var i=0; i<j; i++){
         var currentSubform = xfa.resolveNode("TRANSMITTAL[" + i + "]");
         varLOCK.LockAllFields(currentSubform, "Lock");
    ..resulted in Locking ALL instances.
    form1.TRANSMITTAL.lockButton::click - (JavaScript, client)
    varLOCK.LockAllFields(form1.TRANSMITTAL);
    ..resulted in nothing.
    Any suggestions?

Maybe you are looking for

  • How to deactivate withholding tax base amount field

    Dear Experts, My in client is using the extended withholding tax with setting Define Formulas for calculating withholding tax, my client feel that the tax base amount field is open and user may accidentally input the wrong amount there thus can anyon

  • Wireless printer connection

    I lost my wireless printer connection. It keeps telling me the printer is "offline" What do I do?

  • Screen displaying negative image

    My 3 year old was hitting buttons on my laptop, I walked over to remove him and my screen is a complete negative image of what is being displayed. I am sure it was just a combination of buttons hit but I have no idea how to revert it. Anyone??? Anyon

  • Problem during runtime....

    hi.. can someone help me with a simple program i am creating... Its a program for getting 6 lucky random numbers... everytime i try and run the program, it is able to run, but when i click the button to start to get the random numbers, a problem come

  • Adobe FLASH Installation Error

    Hello, I just wanted to see if anyone had any tips for me. I have Adobe CS3 FLASH Professional and I run the installation and the first message that comes up is "Please Close Internet Explorer, before Setup can continue" Thing is, is I have internet