Navigating in the CRM Portal

Define Highlighting in the CRM Portal

You can define which entries are highlighted in the cross-component navigation in the portal. Highlighting means the special marking of an object to distinguish it from others, for example, color, bold border, and so on.

You enter a logical link in the Highlight field; this logical link needs to be assigned to a work center in the same navigation bar profile. The system evaluates the logical link entered in this field and highlights the corresponding work center in the portal. No entry in the Highlight field means that there is no highlighting of cross-component navigation.

You define highlighting in the CRM portal in Customizing for Customer Relationship Management, by choosing Start of the navigation path UI Framework Next navigation step Technical Role Definition Define Navigation Bar Profile End of the navigation path .

Select your business role under Define Profile and select one of the following folders:

Under Define Generic OP Mapping, you enter the logical link in the field Highlight.
Under Override Generic OP Mapping for Component, you can define the highlighting for exceptions of single components.

Example Example

Role: Sales Professional
Object Type: BP_ACCOUNT
Object Action: Display
Target ID: MD-BP-OV
Highlight: MD-BP-SR

The logical link to be highlighted is the Account search page.

End of the example.

Define Navigation from Non-CRM Applications to CRM Applications

To navigate from a non-CRM application, for example, a SAP NetWeaver Business Intelligence (BI) iView, to a CRM application, you use the object-based navigation (OBN). If you click a hyperlink in the non-CRM application, the object-based navigation starts and navigates to the CRM application.

For more information about object-based navigation (OBN) in the portal, see SAP Help Portal at Start of the navigation path http://help.sap.com Next navigation step SAP NetWeaver SAP NetWeaver 7.0 (2004s) SAP NetWeaver 7.0 Library SAP NetWeaver Library SAP NetWeaver Developer's Guide IT Scenario-Driven Enhancements to Applications Running an Enterprise Portal Core Development Tasks Modifying the Desktop and Navigation Object-Based Navigation End of the navigation path and Start of the navigation path Navigating in the Portal Next navigation step Overview Navigation URLs .

Define Object-Based Navigation (OBN) Target

To execute object-based navigation in the CRM portal, the following parameters are necessary:

crm-object-type: <Name of UI object type>
crm-object-action: <Type of UI object action>
crm-object-keyname: <Key name>
crm-object-value: <Key value>

These parameters are concatenated with & (ampersand), URL-encoded, and assigned to the URL parameter dynamicParameter.

The BSP framework converts the content of the dynamic parameter, to a form parameter that is evaluated in the URL analysis section of the portal application controller in the CRM system.

Example Example

This is an example of the object-based navigation via UI object type:

crm-object-type: BP_ACCOUNT
crm-object-action: B (Execute)
crm-object-keyname: PARTNER
crm-object-value: 108

These parameters already exist. Additionally, a descriptor object is created, which is added to the data collection.

End of the example.

Define Navigation from CRM Applications to Non-CRM Applications

To navigate from CRM applications to non-CRM applications, you can use the transaction launcher to define the navigation target.

To enable the navigation, activate the indicator Portal Integration in Customizing for Customer Relationship Management, by choosing Start of the navigation path UI Framework Next navigation step Technical Role Definition Transaction Launcher Define URLs and Parameters End of the navigation path .

If the indicator is activated, the transaction launcher calls the object-based navigation (OBN) of the SAP NetWeaver Portal. The OBN uses the parameters systemAlias, businessObjName, and Operation, which are maintained in the IMG activity. The target iView is determined by the settings in the SAP NetWeaver Portal.

Application-specific parameters use the OBN variable ObjValue. If the indicator Combine OBN Parameters is not activated in the IMG activity, the plain name value pairs are put into the parameter objValue. If the indicator is activated, the name value pairs are URL-encoded and put into objValue as a value of the parameter dynamicParameter.

Example Example

You want to transfer the following value pairs:

price = net
rebate = 10%

If the indicator Combine OBN Parameters is activated, objValue has the value dynamicParameter='price%3dnet%26rebate%3d10%25'. If the indicator is not activated, objValue has the value price=net&rebate=10%.

End of the example.