SAP CRM 7.0 for Newbies: (Part 1) Simple BOL Object Creation for CRM Webclient UI

Transcription

1 SAP CRM 7.0 for Newbies: (Part 1) Simple BOL Object Creation for CRM Webclient UI Applies to: This article applies to SAP Netweaver 7.0, CRM ABAP 7.0. For more information, visit the Customer Relationship Management homepage. Summary If you are new to CRM ABAP 7.0 and want to get familiar with technical aspects of CRM ABAP 7.0 then this is the right tutorial for you. In this tutorial, you will learn how to develop a simple BOL object that allows you to add, delete, search the table entries using GENIL/BOL layer. Followed by this article, will publish further more articles related to CRM 7.0 Web UI. Author: Shanmuganathan Rajkumar Company: Kaar Technologies Created on: 16 May, 2011 Author Bio Rajkumar is a SAP Certified Netweaver Consultant Working in Kaar Technologies. Raj has a B.Tech. in Information Technology from Anna University and an MBA, working in SAP since He has been involved in various projects as a technical consultant in ABAP, Business server pages, CRM ABAP, ABAP webdynpro, Adobe Flex and Business Objects(Xcelcius). SDN - sdn.sap.com BPX - bpx.sap.com BOC - boc.sap.com UAC - uac.sap.com 2011 SAP AG 1

2 Table of Contents Creation of Simple Transparent Table:... 3 Creation of Simple Root Object and its Configuration... 4 Table Operation using BOL/GENIL Layer:... 6 Related Content... 8 Disclaimer and Liability Notice SAP AG 2

3 Creation of Simple Transparent Table: Let us build a simple table that will have the information about the service request for an Equipment plant. Create a simple transparent table YDATA_TUTORIAL_1 as shown below in SE11 transaction. Create the fields and corresponding data elements as shown below. Once the table is created, we need to define this table in the Generic Interaction Layer/Object Layer as shown below SAP AG 3

4 Creation of Simple Root Object and its Configuration Create a simple Root Object named Y_TUTORIAL_ROOT SAP AG 4

5 I have defined GUID as one of the field in the table because of the following reason, 1) I can use this field as the key field for the table that can create unique service order for the table. 2) Also, the implementation class CL_CRM_GENIL_GEN_TABLE_OBJ will look for this key field when trying to create the GUID for this table. 3) Also, this root object Y_TUTORIAL_ROOT will be created under the Component set SO2. Once you create the root object, assign the search object to it as shown. In this simple example, I have not defined any relation/method definitions. Create the mapping entries for this simple table in the customizing table CRMV_TBLOBJ_MAP, Create the entries with the same ROOT object name created while creating the simple object SAP AG 5

6 Table Operation using BOL/GENIL Layer: As mentioned above, the created root object and search object will be available under the component set SO2 and you can run the same in the transaction GENIL_BOL_BROWSER. Click the button New Root Object, where you can find the newly created object named Y_TUTORIAL_ROOT. Double click the created object and click the Create Object button SAP AG 6

7 You can see the results in the table YDATA_TUTORIAL_1 as shown. You can search the created entries through the same transaction as well. Click New Search button, type the text/value and click the find button. Search results as shown below, 2011 SAP AG 7

8 Related Content Introduction to BOL programming. BOL for CRM Web client. For more information, visit the Customer Relationship Management homepage SAP AG 8

9 Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document SAP AG 9