Scribd
Upload
59 views3 pages

1 General Remarks: How To Access External Components

This document explains how to access a specific component from outside CRM by specifying URL parameters. It details the central class, CL_CRM_UI_EXT_NAV_SERVICE, and parameters needed including object type, action, optional value and key name. It provides an example URL and explains how the customizing maps object types and classes.

Uploaded by

rajusampathirao
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
59 views3 pages

1 General Remarks: How To Access External Components

This document explains how to access a specific component from outside CRM by specifying URL parameters. It details the central class, CL_CRM_UI_EXT_NAV_SERVICE, and parameters needed including object type, action, optional value and key name. It provides an example URL and explains how the customizing maps object types and classes.

Uploaded by

rajusampathirao
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Version 1.

1
How to access External Components

1 General Remarks.......................................................................................................................... 1
2 How to access a specific component and object from outside CRM:.......................................... 1
2.1 ULR parameter for object type and action........................................................................... 2
2.2 BOL object name of the object type .................................................................................... 2
2.3 BOL object name and take the class name .......................................................................... 3



1 General Remarks
This document explains how to access a specific component from outside CRM when
considering the launch of the full L-Shape in order to enable cross-component navigation
for the address page.

This process can only be used to launch a new CRM WebClient session. Remote navigation of
existing sessions is not supported.


2 How to access a specific component and object from
outside CRM:

The Central Class is CL_CRM_UI_EXT_NAV_SERVICE.

You can specify four URL parameters that have to be added to crm_ui_frame/default.htm or any alias
pointing to it (e.g. crm_logon):
ULR Parameter for Object Type: crm-object-type
As defined in customizing, section 2.1 (see below)
URL Parameter for Object Action: crm-object-action
As defined in customizing, section 2.1 (see below)
URL Parameter for Object Value (optional): crm-object-value
Actual value of the field to be searched (e.g. Business Partner ID 112)
URL Parameter for Object Key Name(optional): crm-object-keyname
Name of the attribute the value is used for


If a value and key name are used, there must be a mapper class defined in customizing for that object type.
Check customizing in section 2.2 for the "BOL object name" of the object type.

Then check the view CRMV_UI_OBJ_MAPS (for our standard delivered customizing, see section 2.3 below)
or view CRMV_UI_OBJ_MAP (customer) for that BOL object name and take the class name.

This class must have an implementation of IF_CRM_UI_OBJ_MAPPER~GET_ENTITY_FROM_UI_OBJECT
that is able to create a BOL entity based on the key name and value.


Here is a sample URL that will display business partner 112 in
CC6/300:http://uscicc6.wdf.sap.corp:50010/sap/crm_logon/default.htm?sap-client=300&sap-
syscmd=nocookie&crm-object-type=BP_ACCOUNT&crm-object-action=B&crm-object-
value=112&crm-object-keyname=PARTNER

It works based on the customizing in section 2.1, 2.2, 2.3 (see end of the document). Method
CL_CRM_BUPA_UIU_OBJ_MAPPER->GET_ENTITY_FROM_UI_OBJECT is able to understand all fields
that are defined in the BOL Query 'BuilHeaderSearch'. This is a great example for other implementations.

The class for 'BTOrder' (CL_CRM_UIU_BT_OBJ_MAPPER->GET_ENTITY_FROM_UI_OBJECT) only
understands GUIDs.
Version 1.1


Customizing of the example:
2.1 ULR parameter for object type and action
(Transaction CRMC_UI_NBLINKS)



2.2 BOL object name of the object type




Version 1.1
2.3 BOL object name and class name

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy