Risk Assessment Internal Error

[Former Member]

Hello everyone,

I hope you are well.

I was wondering if anyone had any insight into this "500 SAP Internal Server Error" that I receive whenever I click on the "Risks" or "Tasks" tab on the Risk Assessment OIF.

Please see the screenshots below and the ST22 error dump attached.

This is an "UNCAUGHT_EXCEPTION", Except. "/BOBF/CX_FRW_FATAL" in program "BOBF/CL_CONFRT_COMPLETE======CP"

We have ran report "/BOBF/CONF_SHM_CHECK" and all checks seem to be successful.

Category               ABAP Programming Error

Runtime Errors         UNCAUGHT_EXCEPTION

Except.                /BOBF/CX_FRW_FATAL

ABAP Program           /BOBF/CL_CONFRT_COMPLETE======CP

Application Component  AP-RC-BOF-CFN

Date and Time          06/22/2016 17:54:24

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

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

|Short text                                                                                        |

|    An exception occurred that was not caught.                                                    |

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

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

|What happened?                                                                                    |

|    The exception '/BOBF/CX_FRW_FATAL' 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                                             |

|     '/BOBF/CL_CONFRT_COMPLETE======CP' has to be                                                 |

|    terminated.                                                                                   |

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

error 6.22.txt.zip

[former_member678632]

Hi Joachim,

           I am facing  similar kind of issue in SAP EHSM - Risk Assessment .

Issue :

     When trying to open the the link 'Create Comprehensive Industrial Hygiene Assessment'

     from Enterprise Portal and upon selecting the Risk Tab, I get a short dump . I have attached the        relevant snapshots for your reference .

Analysis:

     On analyzing, few classes related to this application are not called. Please find the list below

List of Missing Classes after upgrade.

1. CL_EHHSS_RAS_OIF_RSK_LST
2. CL_EHHSS_RAS_STEP_LST
3. CL_EHHSS_RAS_REGUL_LST
4. CL_EHHSS_RAS_OIF_STEP_DETAIL

Note : This Issue occurs in EHSM6 upgrade from EHSM4 .

Kindly help us to resolve this dump as this is go-live critical  .

Best Regards,

Arundathi Veeraraghavan.

[Joachim]

Hello Arundathi,

this seems to be another issue than the on described by Reinell.

Though without the full callstack of the short dump it is hard to tell what really is failing here and why you are receiving this error message. Could you share the full error stack / maybe create a new thread for it?

Thanks

Joachim

[Joachim]

Hello Reinell,

by reading through the error message and the ST22 dump I see that during resolving all associations of the Risk Assessment BO an error occurs (callstack no 31). Could you please double-check whether the association key specified in ZCL_EHFND_FBI_CONTROLLER_NEW, Method OVERRIDE_CONFIG_TABBED is actually the right one?

It seems like the basic info all node of an incident should be loaded in the risk assessment. Is this correct?

... if you look at IV_ASSOC_KEY in the callstack no 31. The value is F61D37494DDAFE4FE10000000A1555E1 which is the root to basic_info_all association of the incident. The hosting node specified (IV_BO_NAME) is EHHSS_RISK_ASSESSMENT. Therefore this association fails.

Best regards

Joachim