CRM BUPA SAP

  • View
    600

  • Download
    31

Embed Size (px)

DESCRIPTION

Business Partners in CRM (SAP)

Text of CRM BUPA SAP

CRM Geschftspartner 3.0

( Quickstart

Copyright 2001 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation.

IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX, S/390, AS/400, OS/390, and OS/400 are registered trademarks of IBM Corporation.

ORACLE is a registered trademark of ORACLE Corporation.

INFORMIX-OnLine for SAP and Informix Dynamic ServerTM are registered trademarks of Informix Software Incorporated.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology.

JAVA is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP Markets and Commerce One. All other product and service names mentioned are the trademarks of their respective owners.

Contents

3Introduction

3Step-by-step Instructions

3Extension Scenarios

3Notes

3Preconditions

3Creating Data Elements and Domains

3Extending and Creating R/3 Tables

3Registering Extension Modules

3R/3 Customer Master-Use

3R/3 Customer Master Data Exchange

3Extension and Creation of CRM Tables

3Short Introduction to the BDT

3Creating a BDT Application

3Creating a BDT Function Group

3Function Module for the ISSTA Event

3Function Module for the ISDST Event

3Function Module for the XCHNG Event

3Function Module for the DSAVB Event

3Function Module for the DLVE1 Event

3Function Module for the ISDAT Event

3Function Module for the DTAKE Event

3Function Module for the DSAVC Event

3Function Module for the DSAVE Event

3Function Module for the DLVE2 Event

3Function Module for the FCODE Event

3Function Module for the DCUAC Event

3Creating a BDT Screen

3ABAP Coding for the PBO Flow Logic

3ABAP Coding for the PAI Process

3ABAP Coding for the PBC Process

3Creating New BDT Field Groups

3Creating a New View in the BDT

3Creating a BDT Section

3Creating a BDT Screen

3Registering BDT Event Functions

3Structures for Data Exchange

3CRM Business Partner: Outbound

3CRM Business Partner Inbound

3Programming CRM Middleware Exits

Introduction

In CRM 3.0 customers can extend Business Objects. To do this, customers can either append fields to existing tables or define new tables. In this way additional information can be created for these Business Objects.

This applies not only to the CRM Online application, but also for connected R/3 OLTP Systems, applications on Mobile Clients or Business Information Warehouses.

If, for example, you want to enter and analyze the promotional events that prompted a customer to buy something, then you not only need to extend the CRM Sales Order but also the Mobile Sales application and the CRM Middleware that transports the order to the Mobile Client and the Business Information Warehouse.

This documentation describes such extensions for the CRM Business Partner. For the Business Partner it is possible to extend the standard tables BUT000 and BUT020 as well as add user-defined tables.

This documentation will grow step by step. The first version, which you read here, describes only extensions to the CRM Business Partner interacting with the R/3 Customer Master. CRM Mobile and BW have not yet been described here.

This documentation is valid for CRM 3.0, CRM 3.1 and CRM 4.0.

Also see Notes on Copyright and Support.

Step-by-step Instructions

This unit describes all single steps you need to take in order to understand the process behind a customer enhancement. In addition to the explanations there are also several concrete Example Scenarios, the source code for which is contained in this documentation.

Preconditions Activities in the R/3 OLTP

1. Creating Data Elements and Domains2. Extending and Creating Customer Tables3. Registering Extension Function Modules

4. Extending the R/3 Customer Master: Application5. Extending the R/3 Customer Master: Data Exchange Activities in the CRM Server

Extending the CRM Online Data Model

1. Creating Data Elements and Domains

2. Extending and Creating Business Partner Tables Extending the Business Data Toolset (BDT)3. Creating a BDT Application4. Creating a New Function Group

5. Function Module for the ISSTA Event6. Function Module for the ISDST Event7. Function Module for the XCHNG Event8. Function Module for the DSAVB Event9. Function Module for the DLVE1 Event10. Function Module for the ISDAT Event11. Function Module for the DTAKE Event12. Function Module for the DSAVC Event13. Function Module for the DSAVE Event14. Function Module for the DLVE2 Event15. Function Module for the FCODE Event16. Function Module for the DCUAC Event17. Creating a Screen

18. ABAP Coding for the PBO Process

19. ABAP Coding for the PAI Process20. ABAP Coding for the PBC Process21. Creating BDT Field Groups22. Creating a New View in the BDT23. Creating a New BDT Section24. Creating a BDT Screen25. Registering the event function module Extending the Data Exchange CRM Online R/3 OLTP26. Structures for Data Exchange

27. Registering Extension Function Modules28. CRM Business Partner: Outbound29. CRM Business Partner: Inbound30. Exits in the CRM MiddlewareExtension Scenarios

Use

Several example extension scenarios have been prepared in order to give you some practical examples of CRM object extensions and facilitate your initial steps.

These scenarios have been tested carefully, including the data exchange between the OLTP R/3, the CRM Online application and the Mobile Client when uploading and downloading.

However, you should regard these scenarios as demonstration examples only, and not as proposed solutions to customer enhancements. When modifying or reusing coding you should note that it has been tailored specifically to one scenario.

In this documentation you access the extension scenarios via the icon above, never directly via the general description of the extension process. In this way the extension scenario is kept separate from the general description. In case of doubt, all objects in the customer namespace Z belong to an extension scenario.

Note: Several coding examples are valid for several scenarios, particularly in the units on Middleware. In this case you may ignore superfluous coding when implementing a scenario. The comment lines in the coding will tell you when this is so.

At present there are the following extension scenarios:

Business Partner - New Fields for BUT000

A new field ZZSAPCUSTMR (which should specify if the customer is an SAP customer) is appended in the CRM to the Business Partner Database Table BUT000 by Append technique and can bring this to the interface.

It also shows how a connected R/3 OLTP can be extended accordingly. This takes into account both R/3 Running with Customer Master and, in future, R/3 Running with Business Partner.

This document focuses on the extension of the data exchange between R/3 and the CRM.

The procedure for doing this is described in the units on the CRM Business Partner. If this unit is also valid for another example scenario, you will see the header Example: Business Partner - New Fields for BUT000.

Business Partner - New Fields for BUT020

A new field ZZADRKIND (which specifies the address type concerned) is appended in the CRM to the Business Partner Database Table BUT020 and several other internal structures. All relevant screens are extended too and permit maintenance of the new fields.

It also shows how a connected R/3 OLTP can be extended accordingly. This takes into account both R/3 running with Customer Master and, in future, R/3 running with Business Partner.

This document focuses on the extension of the data exchange between R/3 and the CRM.

The procedure for doing this is described in the units on the CRM Business Partner. If this unit is also valid for another example scenario, you will see the header Example: Business Partner - New Fields for BUT020.

Business Partner - New Tables

The new table ZSAP_PRODUCTS is created in the CRM. It contains a relationship between the Business Partner and the SAP products in use (for example, R/3, R/2, APO). It describes how this extension can be incorporated into the Business Partner Maintenance.

It also sh