URL in SAP Netweaver

Short URL

Easy way:

Step 1:

Click on add to Browser favorites in the page title bar in the right-top corner of the page.

Check the favorites and determine the URL link for the iView.

Hard way:

STEP1: Go to a PCD object in the Portal content directory and determine the path under PCD location properties.

Step 2: Copy the link and go to system administration > navigation > short URL >

Step 3: Type ROLES:// followed by the PCD location and determine your short URL.

Step 4: concatenate the URL (check the below example) For example, the user mapping iView can be displayed with the following URL: http://myServer:50000/irj/portal?NavigationTarget=

ROLES://portal_content/every_user/general/eu_role/

com.sap.portal.portal_personalization/com.sap.portal.persoUserMapping

A short version of the URL might be the following, with the navigation target hashed and shortened: http://myServer:50000/irj/portal?NavigationTarget=navurl:

//b3d6d9ebac16a46574d62757803b05d4

I know it’s goofy to add a hard and easy way to work this but the hard way is for the GEEKS!

And of course the Slackers enjoy the easy one J

URL for Portal Quick Links:

Quick links are shortcuts to iViews and pages. Each quick link is a string that you add to the default portal URL in order to navigate to a specific iView or page. Quick links provide a meaningful name for iViews and pages to which users may want to navigate.

For example, if the base address of the portal is http://myServer:50000/irj/portal and the quick link to the page is email, a URL to the page would be: http://myServer:50000/irj/portal/email

Portal Theme Editor Concept

Prior to 7.0 version of Netweaver the idea of changing the web templates of BI Reports were completely dependent on modifying the contents in the BWReports.css cascading style sheets in the MIME repository via T-code SE80. The various elements in the file were edited using a CSS editor and later imported back with the respective changes. With the changes the reports were generated on a web browser and the template would adapt the cascading style sheet that was modified. These URL’s were later linked to the Portal or sometimes a different application.

Now things have changed a bit. The concept of Portal Theme Editor has taken precedence over the use of the MIME objects in the backend BI system. Developers can now use this editor as a central editing location for all the web applications that are executed in the Portal browser. Just for clarifications or for some naïve learners, Web Templates are created in the Web Application Designer (BEx Tool), these web templates when executed on a browser is called BEx Web Application and this Bex Web Application when executed on a Portal Browser is called a BEx Web Application iView.

So getting back to the point after taking the beginners detour, these web applications can be assigned a specific Portal theme by using certain components in the Theme Editor. Some of them are Global Formats Content Area, Complex Elements, Basic Elements, and Component-Specific Formats.

Lets feed the baby using a spoon and follow the below steps to achieve the invincible: Execute the BEx Web application in the Web browser and Decide what needs to be changed. Open the same as a template in your WAD and identify which web item needs to be changed and use the theme editor to make the necessary changes. (System admin > portal display)

Now let’s get graphical. Consider the below screen print. It is an example of a standard web application as seen on a BEx web analyzer.

(Click on image to see a larger version)

To change or modify certain parts of the template consider the below screen prints: