Exit Button in Travel Assistant - Area does not exist message

Question

My client is on EHP2 for SAP NW 7.0 SP15 & EHP5 for SAP
ERP 6.0 SP12. I believe the portal is also in the process of being upgraded
from 7.01 to 7.4 (although the issue I am having occurs in both new and old
portal systems).
The Homepage Framework was originally customised for Travel
Management to use predominantly Z* Area Group Pages/Areas etc (rather than the
SAP-standard config) and is all working fine apart from one issue with the Exit
button in the Travel Assistant application (FITV_POWL_ASSISTANT).
Note that the FITV_POWL_ASSISTANT application is called with
parameter SAP_FITV_EXIT_OP=CallAreaPage. The presence of this parameter means
the Exit button is available within the application, and the area page should
be called when the button is pressed.
When pressing the Exit button however the message “Critical
Error: Area ZASSISTANT_TRAVEL_ERP2005 does not exist” is raised.
The Travel Assistant portal role contains the same iViews as
the Travel Employee portal role, but has an extra iView called “Self Services Assistant”
which appears as an additional subtab in the portal.
The parameters passed within this iView are:
“sap.xss.menuarea=ZASSISTANT_TRAVEL_ERP2005&sap.xss.menuargrp=ZSAPDEFAULTTRA_ERP2005&sap.xss.menuhdr=SAPDEFAULT&sap.xss.menunobuffer=true”.
Press Exit:
What I don’t understand is that the area page is appearing correctly
and the application is called without issue but when pressing Exit the
navigation can’t return to the area page.
Can anyone suggest what might be causing this error?

Answer 1

Thanks for the suggestions Siddharth.
We do have FIN_TRAVEL_1 active but the business function mentioned in note 1577326 is not.
In the end the issue was resolved by changing the Link Resource assigned to the ZASSISTANT_TRAVEL_ERP2005 Area Page to a resource with a different portal PCD URL, so that now the correct page is called when Exit is pressed.
I think the way this Area Page was implemented was not ideal as all other Area Pages in our setup are called from a separate Area Group Page/tab, whereas this one was not.