I'd echo Thomas's comment that if you are doing any navigation in the WDA app you should be using the object navigation API - not direct URL navigation - therefore there is no need for a portal URL.
However, I've often seen the need to generate a URL for embedding into an email, PDF, etc. (it should be noted that this isn't really a WDA question)
There is no direct link to the "portal" stored in SAP - this is especially the case where your portal is a standalone Java stack and not directly related to the ABAP stack. In these cases I have found that it is useful to store the base URL of the portal in the Home Page Framework configuration of server resources (in the IMG, cross app, home page framework, resources ) as the detail is also useful in configuring access to documents stored in the KM module of the portal when configuring the HPF.
Generally I find that every implementation of SAP finds their own method of storing this link - mainly driven by the need to embed links to the portal in WF emails, so I'd check with your WF team if they have not come up with a generic solution already. I recommend the approach of using the HPF resource as this means you don't have to create your own table/view - but has the downside that you'll have to fiddle to get a reference to the QAS portal in QAS, dev portal in dev and prod portal in prod.
Hope this helps,
Chris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.