SAP Knowledge Base Article - Preview

2563456 - /sapapo/om16 short dump

Symptom

When you're navigating through /SAPAPO/OM16, select "ORDMAP" tab and enter a number order, 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 NetWeaver 7.1 onwards.
  • SAP Live Cache 7.7 onwards.

Product

SAP NetWeaver all versions ; SAP Supply Chain Management all versions

Keywords

/sapoapo/om16, /sapapo/om_lc_browser_class2, ordmap, shortdump , 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 ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.