CX_HRPA_INVALID_PARAMETER

hi Experts
We have developed a function module which calculates certain amount based on certain criteria and update the amount in a wage type in Infotype 15.
The function module calculates the amount , but when im trying to update infotype 15 using HR_INFOTYPE_OPERATION it gives error
CX_HRPA_INVALID_PARAMETER
How to resolve this
I read few notes on sdn which says to check SAP notes , which i checked , all things are in place. Still it is not working.
Regards
sameer

hi
please not the code below.
REPORT ZHR_TEST_2.
include ZHR_T_DATA.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
  PARAMETERS : p_pernr TYPE pernr_d.
SELECTION-SCREEN END OF BLOCK b1.
**----- First Enqu
CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
EXPORTING
NUMBER = P0015-pernr
IMPORTING
RETURN = RETURNE.
Update
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
  EXPORTING
    infty                  = '0015'
    number                 = P0015-pernr
    SUBTYPE                = P0015-SUBTY
  OBJECTID               =
  LOCKINDICATOR          =
  VALIDITYEND            =
  VALIDITYBEGIN          =
  RECORDNUMBER           =
    record                 = P0015
    operation              = 'INS'
   TCLAS                  = 'A'
   DIALOG_MODE            = '2'
  NOCOMMIT               =
  VIEW_IDENTIFIER        =
  SECONDARY_RECORD       =
IMPORTING
   RETURN                 = RETURN
   KEY                    = KEY
*CALL FUNCTION 'HR_INFOTYPE_OPERATION'
*EXPORTING
*INFTY = '0015'
*NUMBER = P0015-PERNR
*SUBTYPE = P0015-SUBTY
*OBJECTID = P0015-OBJPS
*LOCKINDICATOR = P0015-SPRPS
*VALIDITYEND = P0015-ENDDA
*VALIDITYBEGIN = P0015-BEGDA
*RECORDNUMBER = P0015-SEQNR
*RECORD = P0015
*OPERATION = 'INS'
*TCLAS = 'A'
*DIALOG_MODE = '2'
*IMPORTING
*RETURN = RETURN
*KEY = KEY.
IF RETURN IS NOT INITIAL.
WRITE :/ 'Error Occurred'.
ENDIF.
Dequeue
CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
EXPORTING
NUMBER = P0015-PERNR
include code -
*&  Include           ZHR_T_DATA
Data
DATA : P0015 LIKE P0015.
DATA : SECT_AMOUNT  TYPE  PAD_AMT7S.
DATA : RETURN LIKE BAPIRETURN1.
DATA : KEY LIKE BAPIPAKEY.
DATA : RETURNE LIKE BAPIRETURN1 .
data : v_airfare_amount type PAD_AMT7S.
P0015-PERNR = '17287'.
P0015-BEGDA = sy-datum.
P0015-ENDDA = sy-datum.
P0015-LGART = '5014'.
*P0015-PREAS = '01'.
P0015-WAERS = 'QAR'.
*p_pernr = P0015-PERNR.
clear v_airfare_amount.
CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
EXPORTING
NUMBER = P0015-pernr
IMPORTING
RETURN = RETURNE.
       CALL FUNCTION  Zamt_calc
         EXPORTING
           pernr             = '17287'
        IMPORTING
          SECT_AMOUNT        = v_airfare_amount.
CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
EXPORTING
NUMBER = P0015-PERNR.
*PERFORM calc_air.
*sect_amount = '10'.
P0015-BETRG = v_airfare_amount.

Similar Messages

  • Runtime error in activation BADI (CX_HRPA_INVALID_PARAMETER)

    In activation BADI i get a runtime error using 'HR_INFOTYPE_OPERATION'
    An exception occurred that is explained in detail below.                       
    The exception, which is assigned to class 'CX_HRPA_INVALID_PARAMETER', was not 
      caught in                                                                     
    procedure "RESOLVE_EXCEPTION" "(FORM)", nor was it propagated by a RAISING     
      clause.                                                                       
    Since the caller of the procedure could not have anticipated that the          
    exception would occur, the current program is terminated.                      
    The reason for the exception is:                                               
    Ongeldige parameter EXCEPTION waarde                                                                               
    The occurrence of the exception is closely related to the occurrence of        
    a previous exception "CX_HRPA_VIOLATED_PRECONDITION", which was raised in the  
      program "CL_HRPA_MASTERDATA_FACTORY====CP",                                   
    specifically in line 6 of the (include) program                                
      "CL_HRPA_MASTERDATA_FACTORY====CM004".                                        
    The cause of the exception was:                                                                               
    Niet aan voorwaarde voldaan                                                    
      DATA: personaldatakey   TYPE bapipakey.
      DATA: return            TYPE bapireturn1.
      DATA: l_p0025           TYPE p0025.
      DATA: l_citem           TYPE t71adm09-citem.
      DATA: l_resultaat(2)    TYPE n.
    l_p0025-pernr = p0759-pernr.
    Begindatum is begindatum binnengekomen IT0759 record - 1 jaar
        CALL FUNCTION 'RP_CALC_DATE_IN_INTERVAL'
          EXPORTING
            date      = p0759-begda
            days      = 0
            months    = 0
            signum    = '-'
            years     = 1
          IMPORTING
            calc_date = l_p0025-begda.
    Einddatum is 31 december van het jaar binnegkomen IT0759
        CONCATENATE: p0759-endda(04) '1231'  INTO l_p0025-endda.
        l_p0025-infty = '0025'.
        IF p0759-cpamt >= 100.
    *GENERATE ERROR
        ELSE.
          l_resultaat = p0759-cpamt.
         IF l_resultaat < 10.
           CONCATENATE '0' l_resultaat INTO l_p0025-krt01.
         ELSE.
         l_p0025-krt01 = l_resultaat.
         ENDIF.
    write data
          CLEAR: return, personaldatakey.
          CALL FUNCTION 'HR_INFOTYPE_OPERATION'
            EXPORTING
              infty         = '0025'
              number        = l_p0025-pernr
              validityend   = l_p0025-endda
              validitybegin = l_p0025-begda
              record        = l_p0025
              operation     = 'INS'
              nocommit      = ''
              tclas         = 'A'
            IMPORTING
              return        = return
              key           = personaldatakey
            EXCEPTIONS
              OTHERS        = 0.
          IF NOT return-number IS INITIAL.
    GENERATE ERROR
          ELSE.
            is_ok = 'X'.
            process_standard = 'X'.
          ENDIF.

    Hello Richard
    The exception is raised in method SET_FRAMEWORK of class CL_HRPA_MASTERDATA_FACTORY. Perhaps the SAP note mentioned in the coding (on ECC 6.0) may be useful:
    METHOD set_framework.
      IF a_is_initialized = true.
    *   This indicates some complex problem which often can be easily
    *   fixed. For details see NOTE 493984 (2003).
        RAISE EXCEPTION TYPE cx_hrpa_violated_precondition.  " line 6
      ELSE.
        CALL METHOD delayed_constructor
          EXPORTING
            read_infotype     = read_infotype
            masterdata_buffer = masterdata_buffer
            additional_buffer = additional_buffer
            legacy_mode       = legacy_mode.
      ENDIF.
    ENDMETHOD.
    Regards
      Uwe

  • SAP EP ESS CX_HRPA_INVALID_PARAMETER

    Dear Experts,
    Iam getting the below error while accessing the SAP EP ESS webdynpro screen.
    Category          
    ABAP Programming Error
    Runtime Errors    
    UNCAUGHT_EXCEPTION
    Except.           
    CX_HRPA_INVALID_PARAMETER
    ABAP Program      
    CL_HRESS_PER_OVERVIEW=========CP
    Application Component  PA-ESS-XX-WDA
    What can you do?                                                                             
    |
    |
    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                                                                               
    |
    |
    An exception occurred that is explained in detail below.                                 
    |
    |
    The exception, which is assigned to class 'CX_HRPA_INVALID_PARAMETER', was not           
    |
    |
    caught in                                                                               
    |
    |
    procedure "GET_INFTY_SUBTY_DATA" "(METHOD)", nor was it propagated by a RAISING          
    |
    |
    clause.                                                                                 
    |
    |
    Since the caller of the procedure could not have anticipated that the                    
    |
    |
    exception would occur, the current program is terminated.                                
    |
    |
    The reason for the exception is:                                                         
    |
    |
    Invalid parameter EXCEPTION, value                                                       
    |
    |                                                                                             
    |
    |
    The occurrence of the exception is closely related to the occurrence of                  
    |
    |
    a previous exception "CX_HRPA_INVALID_SUBTYPE", which was raised in the program          
    |
    |
    "CL_HRPA_READ_TIMECONSTRAINT===CP",                                                     
    |
    |
    specifically in line 142 of the (include) program                                        
    |
    |
    "CL_HRPA_READ_TIMECONSTRAINT===CM002".                                                  
    |
    |
    The cause of the exception was:                                                          
    |
    |                                                                                             
    |
    |
    Subtype  Not Permitted for Infotype 0105 &TCLAS&

    Hi Philip
    Check this SAP Notes
    1030938 - Infotype 0001: Dump CX_HRPA_INVALID_PARAMETER during saving
    1147540 - IT0008: Dump CX_HRPA_INVALID_PARAMETER
    BR
    SS

  • CX_HRPA_INVALID_PARAMETER DUMP

    hi Experts
    We have developed a function module which calculates certain amount based on certain criteria and update the amount in a wage type in Infotype 15.
    The function module calculates the amount , but when im trying to update infotype 15 using HR_INFOTYPE_OPERATION it gives error
    CX_HRPA_INVALID_PARAMETER
    How to resolve this
    I read few notes on sdn which says to check SAP notes , which i checked , all things are in place. Still it is not working.
    Regards
    sameer

    hi please not the code below.
    REPORT ZHR_TEST_2.
    include ZHR_T_DATA.
    SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
    PARAMETERS : p_pernr TYPE pernr_d.
    SELECTION-SCREEN END OF BLOCK b1.
    **----- First Enqu
    ** CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
    EXPORTING NUMBER = P0015-pernr
    IMPORTING RETURN = RETURNE.
    * **------------- Update
    CALL FUNCTION 'HR_INFOTYPE_OPERATION'
    EXPORTING infty = '0015'
    number = P0015-pernr
    SUBTYPE = P0015-SUBTY
    * OBJECTID =
    * LOCKINDICATOR =
    * VALIDITYEND =
    * VALIDITYBEGIN =
    * RECORDNUMBER =
    record = P0015
    operation = 'INS'
    TCLAS = 'A'
    DIALOG_MODE = '2'
    * NOCOMMIT =
    * VIEW_IDENTIFIER =
    * SECONDARY_RECORD =
    IMPORTING
    RETURN = RETURN
    KEY = KEY .
    *CALL FUNCTION 'HR_INFOTYPE_OPERATION' *EXPORTING *INFTY = '0015' *NUMBER = P0015-PERNR *SUBTYPE = P0015-SUBTY *OBJECTID = P0015-OBJPS *LOCKINDICATOR = P0015-SPRPS *VALIDITYEND = P0015-ENDDA *VALIDITYBEGIN = P0015-BEGDA *RECORDNUMBER = P0015-SEQNR *RECORD = P0015 *OPERATION = 'INS' *TCLAS = 'A' *DIALOG_MODE = '2' *IMPORTING *RETURN = RETURN *KEY = KEY.
    IF RETURN IS NOT INITIAL.
    WRITE :/ 'Error Occurred'.
    ENDIF.
    **--------- Dequeue
    CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
    EXPORTING NUMBER = P0015-PERNR .
    ------------ include code -----
    *&---------------------------------------------------------------------* *& Include ZHR_T_DATA
    *----------------- Data
    DATA : P0015 LIKE P0015.
    DATA : SECT_AMOUNT TYPE PAD_AMT7S.
    DATA : RETURN LIKE BAPIRETURN1.
    DATA : KEY LIKE BAPIPAKEY.
    DATA : RETURNE LIKE BAPIRETURN1 .
    data : v_airfare_amount type PAD_AMT7S.
    P0015-PERNR = '17287'.
    P0015-BEGDA = sy-datum.
    P0015-ENDDA = sy-datum.
    P0015-LGART = '5014'.
    *P0015-PREAS = '01'.
    P0015-WAERS = 'QAR'.
    *p_pernr = P0015-PERNR.
    * clear v_airfare_amount.
    * CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE' EXPORTING NUMBER = P0015-pernr IMPORTING RETURN = RETURNE.
    CALL FUNCTION Zamt_calc EXPORTING pernr = '17287'
    IMPORTING SECT_AMOUNT = v_airfare_amount.
    CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
    EXPORTING NUMBER = P0015-PERNR.
    *PERFORM calc_air.
    *sect_amount = '10'.
    P0015-BETRG = v_airfare_amount.

  • Error Exception CX_HRPA_INVALID_PARAMETER  while updating IT0014 using FM

    Hello Experts,
    When i am updating IT0014 for Benefits Wage types with Amounts, i am getting the below Run-time Error .
    UNCAUGHT_EXCEPTION
    CX_HRPA_INVALID_PARAMETER
    Pl let me know, if any inputs.
    Thanks.
    Linga

    Hello Richard
    The exception is raised in method SET_FRAMEWORK of class CL_HRPA_MASTERDATA_FACTORY. Perhaps the SAP note mentioned in the coding (on ECC 6.0) may be useful:
    METHOD set_framework.
      IF a_is_initialized = true.
    *   This indicates some complex problem which often can be easily
    *   fixed. For details see NOTE 493984 (2003).
        RAISE EXCEPTION TYPE cx_hrpa_violated_precondition.  " line 6
      ELSE.
        CALL METHOD delayed_constructor
          EXPORTING
            read_infotype     = read_infotype
            masterdata_buffer = masterdata_buffer
            additional_buffer = additional_buffer
            legacy_mode       = legacy_mode.
      ENDIF.
    ENDMETHOD.
    Regards
      Uwe

  • Error CX_HRPA_INVALID_PARAMETER in PA30

    Hello Experts,
    Im geting this error
    UNCAUGHT_EXCEPTION         
    CX_HRPA_INVALID_PARAMETER  
    when i work with the IT0706.
    I choose CREATE in PA30 ( With a pernr and IT0706)
    And in the screen of creation, when i press enter over a input fild or if i press SAVE, the error show up.
    Any idea why?
    Thanks!

    Hello Experts,
    When i  am updating IT0014 for Benefits Wage types with Amounts, i am getting the above Run-time Error similar to above Question.
    UNCAUGHT_EXCEPTION
    CX_HRPA_INVALID_PARAMETER
    Pl let me know, if any inputs.
    Thanks.
    Linga
    Edited by: reddy linga on Mar 9, 2012 12:47 PM

  • Personal Data changes were not saved

    Hi,
    From the Personal Profile, I am able to edit and save data in all the sections but not for the Personal Data. Once after clicking on the Edit button from the Personal Data as shown below:
    We are getting below Edit Personal Data screen. Upon clicking on Save we are getting the error:
    Error:
    Here's the dump from st22:
    Category               ABAP Programming Error
    Runtime Errors         UNCAUGHT_EXCEPTION
    Except.                CX_HRPA_INVALID_PARAMETER
    ABAP Program           CL_HRPAD_IL===================CP
    Application Component  PA-ESS-XX-WDA
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_HRPA_INVALID_PARAMETER', was notcaught in procedure "MODIFY_LINE_RECORDS"          (METHOD)", nor was it propagated by a RAISING clause.
         Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated.
         The reason for the exception is:
         Invalid parameter SECONDARY_RECORD-PSKEY, value 0000099132589999123119860415000
    After running the report RPUPAV00, I get the below message:
    Regeneration of Additional ITs for Views
    2 ERP016X"Start of Subsequent IT Generation in Client:" "120" " " " "
    2 ERP016X"    New Personnel Number:" "00000991" " " " "
    2 ERP016 "*" "00000991" "No Conversion Routines for CGr:" "24"
    2 ERP016X"Statistics" " " " " " "
    2 ERP016 "No Database Conversion Occurred" " " " " " "
    This is this happening for country Colombia
    I have checked the sap note: 1815863, I found the table V_T582V & V_T582W. as per sapnote: 1542198, i maintained tcode-GENIL_MODEL_BROWSER.
    Thanks
    Regards

    For this table :
    If I delete the entries for the following tables , work fine.
    However this not is the solution.
    Other suggestions?
    Thanks

  • Error in BOR Method

    Hi Experts,
    I need to update Infotype 2002 (Employee Attendance) in travel request approval work flow.
    For that I  am using set of standard BAPI 's
    "BAPI_EMPLOYEE_ENQUEUE"
    "HR_INFOTYPE_OPERATION"
    "BAPI_EMPLOYEE_DEQUEUE"
    But I am getting the error
    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.
    When I am using same code in program, It's working fine without any error.
    can anyone suggest me , why this error is in BOR method and how to solve it.
    Thanks in advance.
    Regards,
    Priya

    Dear Vimal,
    I checked Note 1087428.
    That note says :
    You try to use transaction PA30 to create infotype 0706. In the run up, you did not use transaction PA40 to plan for the relevant personnel number. Therefore, infotype 0710 does not exist.
    Upto my understanding, transaction PA40 is for employee action, PA30 for employee master data maintainance and PA20 for employee master data display. so i have to use PA30 transaction for master data maintanance.
    For master data maintainance there is group of SAP standard function modules,
    BAPI_EMPLOYEE_ENQUEUE
    HR_INFOTYPE_OPERATION
    BAPI_EMPLOYEE_DEQUEUE
    If we use these function modules, they are same as PA30 transaction.
    When I used these FMs in my report program, they are working fine as their behaviour.
    But when i used these FMs in BOR method in Work Flow, FM 'HR_INFOTYPE_OPERATION' is throwing dump.
    I asked this to SAP, they reply that they didn't release FM 'HR_INFOTYPE_OPERATION' for custom programs, so they will provide any support on this problem.
    So I did work around for the same : I created one FM and inside FM i m calling BDC. That's working fine.
    Thanx to all for help.
    Regards,
    Priya

  • RFC_ERROR_SYSTEM_FAILURE occured when updating P0210 in ESS

    Hello,
    I got the following message error in ESS when I tried to create a new entry in the infotype P0210 using  W-4 Tax Withholding service.
    I checked the table T7XSSPERSUBTYPE and also the user authorizations and all things are fine.
    The problem doesn't occur when I update P0210 in SAP with PA30.
    Can some one know how to fix this issue?
    Thanks a lot.
    SAP version ECC 6
    Portal : NetWeaver 2004s
    Run time error in SAP under ST22
    -  UNCAUGHT_EXCEPTION with exception CX_HRPA_INVALID_PARAMETER
    - OBJECTS_OBJREF_NOT_ASSIGNED_NO with exception CX_SY_REF_IS_INITIAL
    Error message display on the portal
    An exception occurred that was not caught., error key: RFC_ERROR_SYSTEM_FAILURE
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: An exception occurred that was not caught., error key: RFC_ERROR_SYSTEM_FAILURE
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
         at com.sap.xss.hr.per.us.w4.fc.FcPerW4.modifyRecord(FcPerW4.java:231)
         at com.sap.xss.hr.per.us.w4.fc.wdp.InternalFcPerW4.modifyRecord(InternalFcPerW4.java:573)
         at com.sap.xss.hr.per.us.w4.fc.FcPerW4Interface.modifyRecord(FcPerW4Interface.java:116)
         at com.sap.xss.hr.per.us.w4.fc.wdp.InternalFcPerW4Interface.modifyRecord(InternalFcPerW4Interface.java:205)
         at com.sap.xss.hr.per.us.w4.fc.wdp.InternalFcPerW4Interface$External.modifyRecord(InternalFcPerW4Interface.java:281)
         at com.sap.xss.hr.per.us.w4.detail.VcPerW4Detail.onFlush(VcPerW4Detail.java:215)
         at com.sap.xss.hr.per.us.w4.detail.wdp.InternalVcPerW4Detail.onFlush(InternalVcPerW4Detail.java:235)
         at com.sap.xss.hr.per.us.w4.detail.VcPerW4DetailInterface.onFlush(VcPerW4DetailInterface.java:144)
         at com.sap.xss.hr.per.us.w4.detail.wdp.InternalVcPerW4DetailInterface.onFlush(InternalVcPerW4DetailInterface.java:136)
         at com.sap.xss.hr.per.us.w4.detail.wdp.InternalVcPerW4DetailInterface$External.onFlush(InternalVcPerW4DetailInterface.java:212)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:491)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$600(FPMComponent.java:78)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseReviewAndSaveEvent(FPMComponent.java:946)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.raiseReviewAndSaveEvent(FPMComponent.java:1109)
         at com.sap.xss.per.vc.detailnavi.VcPersInfoDetailNavi.next(VcPersInfoDetailNavi.java:226)
         at com.sap.xss.per.vc.detailnavi.wdp.InternalVcPersInfoDetailNavi.next(InternalVcPersInfoDetailNavi.java:163)
         at com.sap.xss.per.vc.detailnavi.DetailNaviView.onActionNext(DetailNaviView.java:153)
         at com.sap.xss.per.vc.detailnavi.wdp.InternalDetailNaviView.wdInvokeEventHandler(InternalDetailNaviView.java:161)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
         at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1358)
         at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:327)
    at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:871)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: An exception occurred that was not caught., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
         at com.sap.xss.hr.per.us.w4.model.HRXSS_PER_P0210_US.hrxss_Per_Modify_P0210_Us(HRXSS_PER_P0210_US.java:239)
         at com.sap.xss.hr.per.us.w4.model.Hrxss_Per_Modify_P0210_Us_Input.doExecute(Hrxss_Per_Modify_P0210_Us_Input.java:137)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
         ... 64 more

    it is to do with time contraint and subtype settings
    the issue is usually caused by a mismatch between T591A, view
    V_T591A, (settings for the backend) and T7XSSPERSUBTYP tables, view
    V_T7XSSPERSUBTYP, (setting for the portal).
    Have you tried using different use cases in V_T7XSSPERSUBTYP
    to see if this helps - please follow this as a guide
    TC1 can use A1,A4,B1,B4
    TC2 can use A1,A2,A3,A4,A5,B1,B2,B4,B5
    TC3 can use A6,B3
    Please also check SAP Note No. 953852.

  • HR_ECM_INSERT_INFOTYPE produces runtime error

    Hi All,
         Good Afternoon. I have been trying to us the FM HR_ECM_INSERT_INFOTYPE or the FM HR_INFOTYPE_OPERATION
    and I am receiving runtime errors such as
    CX_HRPA_VIOLATED_ASSERTION or
    CX_SY_REF_IS_INITIAL
    it seems that the message handler is not functioning as I have expected it to function. I have tried to enqueue the pernr prior to this code, but that doesn't help either.
      CALL FUNCTION 'HR_ECM_READ_INFOTYPE'
        EXPORTING
          pernr           = p_pernr
          infty           = '0002'
          message_handler = message_handler
        IMPORTING
          infotype_tab    = p0002_tab
          is_ok           = is_ok.
      CHECK is_ok EQ true.
      SORT p0002_tab DESCENDING.
      READ TABLE p0002_tab INTO w_p0002 INDEX 1.
      MOVE sy-datum TO w_p0002-aedtm.
      CALL FUNCTION 'HR_ECM_INSERT_INFOTYPE'
        EXPORTING
          pnnnn           = w_p0002
          message_handler = message_handler
        IMPORTING
          is_ok           = is_ok.
      CHECK is_ok EQ true.
    Please advise.
    Kind Regards,
    Daniel A. La Mendola

    The FM HR_INFOTYPE_OPERATION  bombs with either
    CX_HRPA_INVALID_PARAMETER or
    CX_HRPA_VIOLATED_ASSERTION or
    CX_SY_REF_IS_INITIAL
    I believe that I am not providing some pertinent information
    CALL FUNCTION 'HR_INFOTYPE_OPERATION'
       EXPORTING
         infty         = c_infotype_0008
         number        = p0759-pernr
         validityend   = w_rec_it0008-endda
         validitybegin = w_rec_it0008-begda
         record        = w_rec_it0008
         operation     = c_actio_ins
       IMPORTING
         return        = w_return
         key           = w_infty_key.
    and that is why it bombs.
    Kind Regards,
    Daniel A. La Mendola

  • Strange Dump while using HR_INFOTYPE_OPERATION.

    Hi frnz,
    I am facing dump while using the FM 'HR_INFOTYPE_OPERATION' as below. <b>If I swap positions of w_p0041-endda and w_p0041-begda it does not give a dump but error msg is generated saying that no selection in the period(as obviously dates are in propper range).</b> <u>Whlie testing the FM in SE37 with the same data, it works fine.</u> Please help me find the problem.
    data: TCLAS like PSPAR-TCLAS,
          OPERATION like PSPAR-ACTIO,
          infty like PRELP-INFTY.
          infty = '0041'.
          OPERATION = 'MOD'.
          TCLAS = 'A'.
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'
        EXPORTING
          INFTY                  = infty
          NUMBER                 = w_p0041-pernr
      SUBTYPE                =
      OBJECTID               =
      LOCKINDICATOR          =
         VALIDITYEND            = w_p0041-endda
         VALIDITYBEGIN          = w_p0041-begda
      RECORDNUMBER           =
          RECORD                 = w_p0041
          OPERATION              = OPERATION
          TCLAS                  = TCLAS
      DIALOG_MODE            = '0'
        NOCOMMIT               = SPACE
      VIEW_IDENTIFIER        =
      SECONDARY_RECORD       =
       IMPORTING
         RETURN                 =  Return
      KEY                    =

    Hi all ,
    I have already tried converting date to internal format, the data types are also fine. I am not able to paste the screen shot so here is a part of it. Please help.
    ************DUMP************************************
    If we can not remap we would like to just re-raise the
    exception like below like "RAISE EXCEPTION exception.".
    Unfortunately the kernel will then forget about the
    original source position.
    So this is the fallback strategy. Calling this method
    is only allowed if the exception can be resolved. Since
    this is not the case we indicate a parameter violation.
      RAISE EXCEPTION TYPE cx_hrpa_invalid_parameter
        EXPORTING
          previous  = exception
          parameter = 'EXCEPTION'.
    ENDMETHOD.
    ********************END**************
    Thanks
    Sachin

  • Run time error for program: RPCALCU0_CE

    Hi Abapers,
    When we execute the standard program: RPCALCU0_CE from SE38. Below run time error is getting trigerred before selection screen is displayed. Below are the run time error details -
    Runtime Error          UNCAUGHT_EXCEPTION
    Exception              CX_HRPA_INVALID_PARAMETER
           Occurred on     08/04/2010 at   01:22:17
    What happened?
    The exception 'CX_HRPA_INVALID_PARAMETER' was raised but was not caught at any
    stage in the
    call hierarchy.
    Since exceptions represent error situations, and since the system could
    not react adequately to this error, the current program,
    'CL_HRPA_RESOLVE_EXCEPTION=====CP', had to
    be terminated.
    Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_HRPA_INVALID_PARAMETER',
    was neither
    caught nor passed along using a RAISING clause, in the procedure
    "RESOLVE_EXCEPTION" "(FORM)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    Invalid parameter EXCEPTION, value
    The occurrence of the exception is closely linked to the occurrence of a
    previous exception, "CX_HRPA_VIOLATED_PRECONDITION", which occurred in the
    program "CL_HRPA_MASTERDATA_FACTORY====CP" -
    specifically in line 6 of the (Include) program
    "CL_HRPA_MASTERDATA_FACTORY====CM004".
    The reason for the exception was:
    Precondition violated
    Please suggest the solution to overcome this.

    Hey,
        I could not figure your exact problem. But you can go to the transaction ST22 to take a better look at the error that you got. This gives a detailed explanation of the exact error that you are getting. The moment you enter this transaction, you will see the number of runtime errors you got today. Just click on 'Today'. This will give you the list of runtime errors. Click on the relevent error and you can get a much more detailed explanation of the same.
    Hope this helps.

  • Exception from BAPI_PTMGRATTABS_MNGCREATION

    Hi,
    We are using BAPI - BAPI_PTMGRATTABS_MNGCREATION it is working fine but at times it is giving exception from Class - CL_HRPA_INFOTYPE_FACTORY and method - SET_CONTEXT ( cx_hrpa_violated_precondition) and giving dump.. When it raise exception variable a_context value is having value and raising exception.. Please advice what can be the issue...
    METHOD set_context.
      IF a_context IS INITIAL.
        CASE context.
          WHEN context_default OR
               context_legacy.
            a_context = context.
          WHEN OTHERS.
            RAISE EXCEPTION TYPE cx_hrpa_invalid_parameter
              EXPORTING
                parameter = 'CONTEXT'.
        ENDCASE.
      ELSE.
    *   context must never be set twice
        RAISE EXCEPTION TYPE cx_hrpa_violated_precondition.
      ENDIF.
    Regards,
    Rajesh

    Hi, Issue is resolved. I have call the function module with new task..
    CALL FUNCTION '<..FM..>' STARTING NEW TASK 'TXT'
    Thanks
    Rajesh

  • Getting dump when you hire an emp in Development system

    Hi,
    We are getting an ABAP dump when we hires an emp in development system where as the dump is not coming in Quality system. Kindly suggest any config settings need to changed.
    Please find the dump below for reference:
                                                                                    Error analysis                                                                               
    An exception occurred that is explained in detail below.                                
         The exception, which is assigned to class 'CX_HRPA_INVALID_PARAMETER', was not          
          caught in                                                                               
    procedure "RESOLVE_EXCEPTION" "(FORM)", nor was it propagated by a RAISING              
          clause.                                                                               
    Since the caller of the procedure could not have anticipated that the                   
         exception would occur, the current program is terminated.                               
         The reason for the exception is:                                                        
         Invalid parameter EXCEPTION, value                                                                               
    The occurrence of the exception is closely related to the occurrence of                 
         a previous exception "CX_HRPA_INVALID_INFOTYPE", which was raised in the                
          program "CL_HRPA_INFOTYPE_FACTORY======CP",                                            
         specifically in line 18 of the (include) program                                        
          "CL_HRPA_INFOTYPE_FACTORY======CM004".                                                 
         The cause of the exception was:                                                                               
    Infotype 0529 not permitted                                                                               
    Rgds
    Kumar

    Hi,
    Maybe specific to your master data maintainance, as it is working inQS1.
    Regards
    Team Member.

  • [Ugrapde ECC 5.0] Dump in PA-CM

    Hi all,
    We are currently upgrading from 4.6C to ECC 5.0
    We have got a problem when switching from Display to Modify in the HRCMP0001D transaction. A dump is generated with the following text :
    The exception 'CX_HRPA_INVALID_PARAMETER' was raised but was not caught at any 
    stage in the                                                                  
    call hierarchy.                                                                               
    Since exceptions represent error situations, and since the system could        
    not react adequately to this error, the current program,                       
    'CL_HRPA_RESOLVE_EXCEPTION=====CP', had to                                    
    be terminated.
    It did find a OSS Note <b>885513</b> which seems to be related but is for FI-TV-COS and not for PA-CM. And - I assume - the corrections apply to FI-TV programs...
    Has anybody experienced something similar ?
    Best regards,
    Guillaume

    Hi Sinchan, hi Suresh
    Sorry for the delay.
    What I did is that I added the
    * an event to avoid a short dump due to CE framework
    LOAD-OF-PROGRAM.
      PERFORM do_nothing(sapfp50p).
    into the program RHCMP_STARTNF that is called when you launch the transaction HRCMP0001D
    It is far better now ! 
    For the moment, we are just upgrading 'existing' functionalities but we are studying ECM also, for the future.
    Best regards,
    Guillaume

Maybe you are looking for

  • Trying to install itunes but keep getting windows error126 message and libicuin.dll missing

    trying to install itunes but keep getting windows error 126 message and libicuin.dll missing have reinstalled numerous times and keep getting same messages.

  • Doesn't working SD card slot

    i bought Macbook pro with retina few days ago I was checking SD card slot but doesn't working it.... how can i do... when I try to SD card put in Macbook there is no reaction I try to reset OS and pram, SMC already

  • Missing frames importing from .mov

    I'm trying to import several .mov files into imovie, and am having problems with imovie removing many frames from each. The help file said that it may be a problem with FileVault being on, but I checked and it is, and has been, off. Any idea how to f

  • Download WRT54G v6 CD copy.

    Hi ladies and gentlemen I recently found that many people lost their WRT54G v6 CD copy(heard it works with v5 also, not sure.), so I decided to upload my own CD copy for you all in my spare time. It's splited in 3 parts  (2 50Mb each, and the last on

  • I need to change my email add for my contact form

    Hi there I'm making a homepage in Muse for friend of mine. She needs online booking on her page. How is it possible with Muse? Please help, if someone knows how to do Thanks Sara