BOL Tree Customizing and Event Linking in Is-Utilites

Version 1.
0
04.08.2008
English
IS Utilities BOL Tree

Customizing and Linking
SAP GDC CRM Practice
SAP India Pvt. Ltd., SAP GDC

1.021.01.2015English
Page 1 of 14
Custom BSP Extension to disable a THTMLB link
Copyright
Copyright 2004 SAP India Pvt. Ltd. All rights reserved.
No part of this documentation may be reproduced or transmitted in any form or for any
purpose without the express permission of SAP India Pvt. Ltd.
SAP reserves the right to change the information contained in this document without prior
notice.
Author(s) Details
Gaurav Kapoor I054973
Contents
1
Introduction....................................................................................3
1.1
1.2
Goal........................................................................................................ 3
Definitions...............................................................................................4
Graphical view...............................................................................4
Documentation part.......................................................................4

1.019.06.08English
Page 2 of 14
Introduction
E.ON is a CRM 2007 Implementation with IS Utilities in the back end and CRM in the
front end. During project work the team has received a significant amount of custom UI
work.
One such requirement was to develop a custom master data view for Maintaining Device
Location data in CRM. This view is not part of the standard SAP product as of IS Utilities
release SAPK-60202INISUT. This view would have to be called from the standard BOL
Tree as shown below:
Both the Device Location number ( 7400000270 ) as well as the description are enabled
as a hyperlink. Clicking on any of these should result in the Device Location view being
called up.
1.1
Goal
The Aim of the enhancement is to :

a) Customize the BOL Tree so that the custom IsuDeviceLocation view can be called
both from the Tree Node as well as from the description of the IsuDeviceLocation as
shown below ( Links on the device location and description ).
b) Create a custom view (not part of IS Utilities) to help the user maintain
IsuDeviceLocation data in the ISU system with the front end being in the Web UI.

1.019.06.08English
Page 3 of 14
Definitions
1) Overview of Master Data in IS-Utilities

1.019.06.08English
Page 4 of 14
2) Device Location
3) How to identify and confirm a business partner in the IS-Utilites Web UI
D:\CRM Material\
02_RAUT60_CRM2006 - Master data and overviews.ppt
Graphical view
The ISU interaction center is shown below.
The user first identifies a business partner to confirm ( done by clicking on the weiter
( German for Confirm ) link at the bottom of the screen as shown in the snapshot above.
1.019.06.08English
Page 5 of 14
The BOL Tree for the business fact sheet is presented below.
The BOL Tree for the technical fact sheet is presented below.

1.019.06.08English
Page 6 of 14
A snapshot of the custom IsuDeviceLocation view is presented below.
Documentation part
An outline of how the development was done and the sample code is presented
below. The overall steps to configure the tree are:
a) Add an entry in the Tree profile ( Usually based on the GENIL Component
IUICOBJD ) for each node representing one master data.
b) Create a presentation ID for each node and maintain what needs to be shown the
columns of the table control
c) Add code in the enhanced component of the standard component IUICOVW so
that the new event is handled and navigation is done while passing the data
corresponding to the node clicked. For example, when the user clicks on the
device location description, this component will receive the event and capture
and pass on the device location data corresponding to the link clicked.

1.019.06.08English
Page 7 of 14
An outline of the steps required to develop the view are:

a) Develop the view in the BSP Component workbench.
b) Define work centers where a target id is specified and an object type is linked to
an inbound/outbound plug of the component to be navigated to.
c) Modify the navigation bar customizing to link up target ids with the object types.
An outline of steps to save data to the IS- Utilites system from CRM is as below:
1) Identify the BOL component to be used.
2) Identify the GENIL class associated with the component
3) Inherit from the standard class and over-ride methods :a. INIT_OBJECTS
b. MODIFY_OBJECTS ( If SAVE is required )
c.
GET_OBJECTS ( to bring IsuDeviceLocation Data from ISU to CRM )
BOL Tree customizing

Step 1: Go to the SPRO path as below:
Click on Define Object Hierarchies and Object Attributes.

1.019.06.08English
Page 8 of 14
Step 2: Select the technical fact sheet profile as below
Step 3: Define which nodes ( Master Data )need to show up in the tree:
Note that entries with // imply entries relative to its immediate parent. Presentation IDs
are created by clicking on Display in the left pane of the customizing transaction above.
Step 4: Customize each presentation Id as below. This example details customizing for 3
columns in the table control in which the BOL Tree is embedded.

1.019.06.08English
Page 9 of 14
Step 5: To enable the Device Location Description as a link, customize the 2 nd column
entry as below:
Step 6: Add in the component controller methods of enhanced component IUICOVW as

shown below:

1.019.06.08English
Page 10 of 14
At the end of these steps the device location description should now show up as a link.
An outline of steps to save data to the IS- Utilites system from CRM is as below:
Step 1: Identify the GENIL component to be used ( IUICOBJD ).
Step 2: Identify the class against this component and make an entry for a custom class.
This can be done in SPRO path shown below

1.019.06.08English
Page 11 of 14
Click on Basic Settings.

Step 3: Make a new class entry against ISUMD ( ISU Master Data ). This will be a Z class
that will inherit from the standard class CL_C_ISU_IL_MD.
Step 4: The following methods need to be over-ridden in the custom Z class.

1.019.06.08English
Page 12 of 14
Step 5: Put in the following code in LOCK_OBJECTS for IsuDeviceLocation as shown

below:
Step 6: The following code attachment below can be used as an example to understand
how to customize the standard code to now cater to saving ISU Device Location Data.
D:\CRM Material\
D:\CRM Material\
modify_isudevicelocation.txt
modify_internal.txt
Modify internal calls Modify ISUDeviceLocation.

Step 7: In the modify isudevicelocation method, there is a Z function module. This again
is a copy of the standard function module that can be found in the standard modify
objects method of the class CL_C_ISU_IL_MD. Modify this Z function module to update
data into ISU as necessary. This Function module is a Remote Enabled Function module
that sits in ISU. A similar function module is present for accessing data from ISU and can
be found in the GET_OBJECTS method of the standard class.
Step 8: Test the code written in MODIFY_OBJECTS and GET_OBJECTS via the BOL
Browser. The component name will be IUICOBJD.
1.019.06.08English
Page 13 of 14
Use the ConnectionObjectQueryCompleteKey Query with a business partner and work

your way down to IsuDeviceLocation .For details on the relationships visit the
GENIL_MODEL_BROWSER and put in IUICOBJD as the component. Use IUIBase as
the root component and drill down to IsuDeviceLocation via IsuPremise,
IsuPremiseInstallationPremiseRel, IsuDeviceRel, IsuDeviceDeviceLocationRel.

1.019.06.08English
Page 14 of 14

BOL Tree Customizing and Event Linking in Is-Utilites

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

BOL Tree Customizing and Event Linking in Is-Utilites

Încărcat de

Drepturi de autor:

Formate disponibile

Version 1.

IS Utilities BOL Tree

SAP GDC CRM Practice

SAP India Pvt. Ltd., SAP GDC

Custom BSP Extension to disable a THTMLB link

SAP India Pvt. Ltd., SAP GDC

Custom BSP Extension to disable a THTMLB link

The Aim of the enhancement is to :

SAP India Pvt. Ltd., SAP GDC

Custom BSP Extension to disable a THTMLB link

SAP India Pvt. Ltd., SAP GDC

Custom BSP Extension to disable a THTMLB link

3) How to identify and confirm a business partner in the IS-Utilites Web UI

The ISU interaction center is shown below.

Custom BSP Extension to disable a THTMLB link

SAP India Pvt. Ltd., SAP GDC

Custom BSP Extension to disable a THTMLB link

A snapshot of the custom IsuDeviceLocation view is presented below.

SAP India Pvt. Ltd., SAP GDC

Custom BSP Extension to disable a THTMLB link

An outline of the steps required to develop the view are:

GET_OBJECTS ( to bring IsuDeviceLocation Data from ISU to CRM )