default error page

[Former Member]

Hi guys,

currently users do not like the error page, you alll know it quiet well I guess.

Is it possible to somehow replace the default error page with another redirect or error page that is customer friendly?

regards

Stefan

probably that question has been up yet, but the search returned a lot on that topic

[abhimanyu_lagishetti7 · Accepted solution]

Go to SICF transaction and search for the web dynpro Applicaiton in the SICF tree

double click the service and choose in Error page input give URL to any page which you want to display as standard default error page.

http://help.sap.com/saphelp_nw04/Helpdata/EN/f9/4b8e3a89210f25e10000000a11405a/content.htm

Abhi

[Former Member · Accepted solution]

thanks, appears to be the right place. Alas I cannot find my "service", I can neither find a web dynpro application nor a component.

Do I need to build some kind of proxy here?

regards

stefan

[abhimanyu_lagishetti7 · Accepted solution]

Not Exactly,

go through this note to get Web dynpro Application Service Node :

https://service.sap.com/sap/support/notes/1120682

Abhi

[alejandro_bindi · Accepted solution]

You can access the node from the WD application, refer to this thread:

[Former Member · Accepted solution]

cool, I found it and it works to add an error page, thank you for that!

still one thing I need: in documentation it is mentioned that one can add html tags for error display. how is the correct usage of that? I have not used htmlb or bsp...

any code snippet? html tags for example SYMANDT, ERRORCODE

thanks a lot!

Stefan

[Former Member]

I tried

<<h1>foo des<HTMLB:SYMANDT></HTMLB:SYMANDT></h1>

and also added

<%@page language="abap" %>

<%@extension name="htmlb" prefix="htmlb" %>

to the header, it still doesn't work.

Stefan

[Former Member]

I'm really starting a monologue here...

Anyway I found out what was wrong. As I suggested it was my lack of experience with bsp.

In fact the attributes are passed via http request and my be printed out in the form <%="name of variable"%> e.g.

<%=MESSAGE%>

have fun, with it

I also tried to create a WDA application who is able to present the error in a more user friendly way using standard WDA elements and the portal theme,but unfortunately the formatted text view doesn't accept the tag <%=MESSAGE%> I'll see if I can make a work around

regards

Stefan