Navigation within a 'complex' transaction (app) results in a: 500 Internal Server Error
Typical example of this are the "MM" transactions like ME23N, ME22N etc
- Calling any transaction via WebGUI directly or via FioriLaunchPad (FLP)
- Navigation within a 'complex' transaction (app) results in a: 500 Internal Server Error
- Typical example of this are the "MM" transactions like ME23N
Complex is where one has many different screen elements on a screen, for example large tab control with many tabs.
Manage Purchase Orders App, ME23N, ABORT_MESSAGE_STATE, SYSTEM-EXIT, CALL_SCREEN, SAPLMEGUI, START-OF-SELECTION, "diag: Too many subscreens", "diag: Cannot update the session state" , KBA , BC-FES-WGU , SAP GUI for HTML , BC-FES-ITS , SAP Internet Transaction Server , Problem
About this pageThis 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.