sapnote_0001494536_obnissue

8/12/2019 sapnote_0001494536_OBNIssue

http://slidepdf.com/reader/full/sapnote0001494536obnissue 1/4

17.02.2012 of 4

SAP Note 1494536 - Object Based Navigation - SpecificComponent Note

Note Language: English Version: 3 Validity: Valid Since 05.09.2010

Summary

Symptom

Required information for messages opened in the EP-PIN-OBN component.

This note will provide you with information regarding the most common

problems and the information that SAP Support needs in order to provide you

with assistance.

Other terms

object based navigation, OBN, business object, EP, Enterprise Portal, SAP

NetWeaver Portal, portal, Help, prerequisites, SAP Support, message,

guidelines, creating messages, There is no iView available for system

Reason and Prerequisites

Reason:

The following information is required to ensure speedy processing when

opening messages in the EP-PIN-OBN component. This may seem like a lot of

information, but having it available will avoid the necessity to return the

message to you to gather additional information and will help SAP Support

to identify the issue faster.

Prerequisites:Verify that the relevant navigation is indeed object based navigation.

If the navigation fails returning the message "There is no iView available

for system <System_alias_name>, object <Business_Object_name>" then this is

OBN for certain.

If the navigation fails with the error message "Page not found or not

available" then it might be a normal navigation.

Using the HTTP Watch tool, record the relevant navigation and look for a

request where one of its POST parameters looks like this:

NavigationTarget=OBN://BOTechnicalName=<Business_Object_name>/BOSystemAlias

=<System_alias_name>/Operation=<Operation_name>.

SAP Business package applications use OBN (SRM, Purchasing,

ESS, MSS, etc.).

Customizing roles from business packages can cause OBN problems.

For instance, creating a new role, and applying an application that uses

OBN for portal navigation, can cause OBN errors if the target application

is not assigned to that role as well.

If the problem is related to your customer-specific role or this is an

original role from an SAP business package, the selection of component

EP-PIN-OBN is incorrect.

Choose the appropriate component of the specific application to avoid

delays in routing the message. Using a note search can help you find the

component of a specific application.

Solution



17.02.2012 of 4


Basic information:

----------------------------------------------------------------------

OBN (object based navigation) is a runtime portal capability of navigating

and passing business data between applications in the scope of the user

roles or only in the source role.

OBN is used in many SAP applications and business packages.

Most OBN errors are caused by wrong configuration of the OBN scenario.

More information on OBN can be found in SAP NetWeaver Portal documentation

under

http://help.sap.com/saphelp_nw70/helpdata/En/3e/97e33d7f9c47af85a2543e3a2cc

e4c/frameset.htm

Basic OBN Terms:

----------------------------------------------------------------------

Source Application - The iView from which the OBN action is launched.

Target Application - The iView or page that is launched as a result of the

OBN action, or an iView/page that implements a certain operation.

There are two types of OBN:

----------------------------------------------------------------------

1) OBN that calls an OBN-specific portal component.

In the HTTP Watch trace, the request will look like this:

http://<SERVER>:<PORT>/irj/servlet/prt/portal/prtroot/com.sap.portal.n

avigation.objbased.ObjBasedNavigation.

The OBN parameters are sent in the POST parameters.

2) OBN that uses normal navigation with the NavigationTarget parameter.

In the HTTP Watch trace, the request will look like this:

http://<SERVER>:<PORT>/irj/servlet/prt/portal/prteventname/Navigate/prtroot

/pcd!3aportal_content!2fevery_user!2fgeneral!2fdefaultDesktop!2fframeworkPa

ges!2fframeworkpage!2fcom.sap.portal.innerpage.

The OBN parameters in this case are sent in the NavigationTarget parameter

in the following way:

NavigationTarget=OBN://BOTechnicalName=

<Business_Object>/BOSystemAlias=<Alias>/Operation=<Operation>.

Searching targets within the scope of the user roles:

-----------------------------------------------------------------------

OBN can search for targets in two possible scopes, depending on the

resolvingMode value (a parameter that is sent in the OBN event):

1)resolvingMode = SourceRole -> The search for targets is performed only inthe role that the navigation was performed from (the role that contains the

source application).

2)resolvingMode = Default -> The search for targets is performed in all the

roles assigned to the user that launched the OBN action.

If there is no resolvingMode parameter in the request the default is to

search in the scope of all the user roles.

Steps for solving OBN problem:

-----------------------------------------------------------------------

1) Finding the relevant OBN data.

As explained above, using HTTP Watch, OBN parameters can be tracked easily.The most important parameters are: SystemAlias, BusinessObject, Operation

and resolvingMode.



17.02.2012 of 4


2) Make sure the relevant business object and operation exist in the portal

(under the 'Business Objects' folder).

The business object ID is composed of the system alias and the business

object with the period sign ('.') as a separator: for example "SAP_SRM.sc".

3) Understand what should be the target application (iView or page) for the

OBN action.

4) Check that the target application implements the given operation using

the Business Object Editor:

o Open the business object, choose the relevant operation and press

on the 'Display iViews/Pages' button. This can take a while.

o Look for the target application in the results. The results table

provides information of which target application is tagged with the

given operation and whether this target is assigned to a role or

not.

For detailed explanation, refer to the attached 'Analyzing Business Object

Results Table.docx'.

For detailed explanation of how to tag a target application with thedesired operation, refer to attached 'Tag Application As Target.docx'.

5) Make sure that the target application is located in the scope of the

search.

The role that includes the target application must be assigned to the

relevant user and in case of source role mode, the target application must

be located in the same role as the source application.

In case that the note doesn't help solving the problem, the following is

essential for investigation the problem:

1)Http trace for reproducing the issue.

Make sure to record only the fraction of the above issue.

The result should be an hwl file. Zip the file and attach it to the

message.

A basic free version of httpwatch can be downloaded from

http://www.httpwatch.com/download

Remote Connections:

If the problem can be reproduced, provide an HTTP connection to your system

and provide user/password information (in the secure area) of the user who

is able to reproduce the issue and also of the super admin user. This

greatly improves the processing time of messages.

Header DataRelease Status: Released for Customer

Released on: 05.09.2010 14:43:09

Master Language: English

Priority: Recommendations/additional info

Category: Help for error analysis

Primary Component: EP-PIN-OBN Object Based Navigation

Valid Releases



17.02.2012 of 4


Software Component Release From

Release

To

Release

and

Subsequent

EP-PSERV 7.00 7.00 7.02

Related Notes

Number Short Text

1646042 Information required for issue handling in OBN area

1416756 OBN Configuration in Performance Management

1408243 Configuration for object-based navigation

1386141 There is no iView available for system "XYZ", object "ABC".

1354803 OBN is not working in new window scenario

Attachments

File

Type

File Name Language Size

ZIP OBN_Documents.zip E 244 KB