Skip to Content
author's profile photo Former Member
Former Member

Incident Management in EHSM 3.0 - Error While Creating an Incident- Pls help


Hello Friends,

I am new into EHSM 3.0 and am configuring and Testing for Incident Management Business Scenarios. Presently am testing the cycles in Report Incident, Near Miss and Safety observation in NWBC and in all the activities, am getting the following error when I try to send after complition of filling basic informations. I appriciate if any one who has faced similar errors help me understand what is causing this Error. How this can be resolved ?

Thanks in advance,

Sudharshan M

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Note
  • The following error occurred in system C80 : The current application triggered a termination with a short dump.
  • The error occurred on application server WICOMP14_C80_00 and in work process. 6
  • The termination type was: RABAX_STATE
  • The ABAP call stack was:
    Method: SET_APPLICATION_ERROR of program /BOBF/CL_FRW==================CP
    Method: DO_DETERMINATIONS of program /BOBF/CL_FRW==================CP
    Method: /BOBF/IF_FRW_SERVICE_LAYER~FINALIZE of program /BOBF/CL_FRW==================CP
    Method: /BOBF/IF_TRA_SERV_MGR_TRANSACT~FINALIZE of program /BOBF/CL_TRA_SERVICE_MGR======CP
    Method: FINALIZE of program /BOBF/CL_TRA_TRANSACTION_MGR==CP
    Method: /BOBF/IF_TRA_TRANSACTION_MGR~SAVE of program /BOBF/CL_TRA_TRANSACTION_MGR==CP
    Method: IWCI_IF_FPM_TRANSACTION~SAVE of program /BOFU/CL_FBI_CONTROLLER_NEW===CP
    Method: IWCI_IF_FPM_TRANSACTION~SAVE of program CL_EHFND_FBI_CONTROLLER_NEW===CP
    Method: IWCI_IF_FPM_TRANSACTION~SAVE of program CL_EHHSS_INC_QAF_CNTRLR_NEW===CP
    Method: SAVE of program /1BCWDY/005OX85YQHL5EXGBVFQZ==CP

What can I do?

  • If the termination type was RABAX_STATE, you will find more information on the cause of termination in system C80 in transaction ST22.
  • If the termination type was ABORT_MESSAGE_STATE, you will find more information on the cause of termination on the application server WICOMP14_C80_00 in transaction SM21.
  • If the termination type was ERROR_MESSAGE_STATE, you can search for further information in the trace file for the work process 6 in transaction ST11 on the application server WICOMP14_C80_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.

Error Code: ICF-IE-http -c: 130 -u: SUDHARSHAN -l: E -s: C80 -i: WICOMP14_C80_00 -w: 6 -d: 20140102 -t: 164923 -v: RABAX_STATE -e: MESSAGE_TYPE_X -X: 001517AAF6951ED39CF3F603733D276A_001517AAF6951ED39CF3F62411ABC76A_1 -x: BA9F73E31763F101876A001517AAF695


HTTP 500 - Internal Server Error

Your SAP Internet Communication Framework Team

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jan 02, 2014 at 12:17 PM

    Hi Sudharshan,

    Have you checked if the workflow is configured properly ?

    In SPRO, follow the path SAP EHS Management / Foundation for EHS Management / Process Foundation / Basic Settings.

    Click on Perform Automatic Workflow Customizing.

    Also you can check what has been configured here :

    SAP EHS Management / Foundation for EHS Management / Process Foundation / Checks and Tools.

    Regards,

    Philippe

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Sudarshan

      I believe there is no issue in from standard system point of view, if the OSS notes 1776424 & 1824932 is already applied. I guess Dynpro screen calling is failed when you are trying to send the incident. Check with technical team for activation of Missing Objects.

      Balajee

  • author's profile photo Former Member
    Former Member
    Posted on Jan 07, 2014 at 01:50 PM

    Hi Sudarshan,

    From the short dump it looks as if the error occurred during a determination method of the BOPF layer: "DO_DETERMINATIONS" - are you working on a vanilla system or have you created (or enhanced) any determinations for any of the nodes on the incident? (this is done by enhancing the business object node).

    This could likely be also triggered by incorrect config in the field control configuration.

    I would get a technical resource to look at the dump in ST22 and set a break point in the relevant code to see why the error is being raised?

    It would also be good to check the application log that is written using transaction SLG1 for more information on this error.

    Regards, Warren

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member


      Hi All,

      The issue is resolved. Infact certain EHSM configuration values were not populated in SPRO when we did a Copy of 000 Client to the Testing Server. It was copied line by line later and the issue resolved. I appriciate you all for your responses.

      Thanks,

      SM

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.