Getting error "Parameter has invalid value: Parameter TSTMP1 has invalid value 0" while testing WebDynpro service "asr_personnel_file"

[Former Member]

Hi,

I am getting below error while testing the service "/default_host/sap/bc/webdynpro/sap/asr_personnel_file".

Error while processing your query   What has happened? The URL call http://indcldaess15.dir.svc.accenture.com:8000/sap/bc/webdynpro/sap/asr_personnel_file was terminated because of an error.

Note   The following error occurred in system BDE : Parameter has invalid value: Parameter TSTMP1 has invalid value 0 . The error occurred on application server INDCLDAESS15_BDE_00 and in work process 7 . The termination type was: RABAX_STATE The ABAP call stack was: Method: SUBTRACT of program CL_ABAP_TSTMP=================CP Method: SUBTRACT_TIMESTAMPS of program CL_HRASR00_PROCESS_UTILITIES==CP Method: GET_CURRENT_TIME_DATA of program CL_HRASR00_PROCESS_UTILITIES==CP Method: START_TRACKING of program /1BCWDY/0O2THPAM2K3EWCYOIXSM==CP Method: IF_COMPONENTCONTROLLER~START_TRACKING of program /1BCWDY/0O2THPAM2K3EWCYOIXSM==CP Method: HANDLEDEFAULT of program /1BCWDY/0O2THPAM2K3EWCYOIXSM==CP Method: HANDLEDEFAULT of program /1BCWDY/0O2THPAM2K3EWCYOIXSM==CP Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/0O2THPAM2K3EWCYOIXSM==CP Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_IF_VIEW=====CP Method: DISPLAY_TOPLEVEL_COMPONENT of program CL_WDR_CLIENT_COMPONENT=======CP

What can I do? If the termination type is RABAX_STATE, you will find more information on the cause of termination in system BDE in transaction ST22. If the termination type is ABORT_MESSAGE_STATE, you will find more information on the cause of termination on the application server INDCLDAESS15_BDE_00 in transaction SM21. If the termination type is ERROR_MESSAGE_STATE, you can search for further information in the trace file for the work process 7 in transaction ST11 on the application server. INDCLDAESS15_BDE_00 . You may also need to analyze the trace files of other work processes. If you do not yet have a user ID, contact your system adminmistrator.

I have also checked the ST22 dump as shown below:

Category               ABAP Programming Error
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_PARAMETER_INVALID_RANGE
ABAP Program           CL_HRASR00_PROCESS_UTILITIES==CP
Application Component  PA-AS
Date and Time          19.06.2012 10:00:15

Short text
     An exception occurred that was not caught.

What happened?
     The exception 'CX_PARAMETER_INVALID_RANGE' 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_ABAP_TSTMP=================CP' has to be
     terminated.

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_PARAMETER_INVALID_RANGE', was not
      caught in
     procedure "SUBTRACT_TIMESTAMPS" "(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:
     Parameter has invalid value: Parameter TSTMP1 has invalid value 0.

Please help me out to resolve this

[Abhijeet-K]

Hi CNRCOE,

As the error and the dump clearly states, the problem lies in the value. Apparently the variable that is being supplied to the method SUBTRACT of class CL_ABAP_TSTMP is incorrect. Check your binding. The context variable that is bound with the screen UI element should be of the type P. If the error emanates from standard components, check if your data input is correct.