Symptom
When navigating through /SAPAPO/OM16, and, for example, select "ORDMAP" tab and enter a order number, the following DUMP will show:
Category ABAP Programming Error
Runtime Errors UNCAUGHT_EXCEPTION
Except. ERROR
ABAP Program PROGNYLSJKXARIHX00002IUAS0
Application Component Not assigned
Short Text
An exception has occurred that was not caught.
What happened?
Exception 'ERROR' 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, ABAP program 'PROGNYLSJKXARIHX00002IUAS0' had to be
terminated.
Error analysis
An exception has occurred which is explained in more detail below. The
exception is assigned to class 'ERROR' and was not caught in procedure
"FIRST_DATA_TO_DISPLAY" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated this
exception, the current program was terminated.
The reason for the exception is:
An exception occurred
Missing RAISING Clause in Interface
Program PROGNYLSJKXARIHX00002IUAS0
Include /SAPAPO/OM_LC_BROWSER_FORMS2
Row 139
Module Type (FORM)
Module Name FIRST_DATA_TO_DISPLAY
Trigger Location of Exception
Program PROGNYLSJKXARIHX00002IUAS0
Include /SAPAPO/OM_LC_BROWSER_CLASS2
Row 5,980
Module Type (FORM)
Module Name MESSAGE
Read more...
Environment
- SAP Supply Chain Management
- SAP LiveCache
Product
Keywords
/SAPAPO/OM16, /SAPAPO/OM_LC_BROWSER_CLASS2, ORDMAP, shortdump, short dump, dump, n/SAPAPO/OM16, UNCAUGHT_EXCEPTION, /SAPAPO/OM_LC_BROWSER_FORMS2, OM16 , KBA , BC-DB-LCA , liveCache Applications , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.