CRM and CX Blogs by Members
Find insights on SAP customer relationship management and customer experience products in blog posts from community members. Post your own perspective today!
cancel
Showing results for 
Search instead for 
Did you mean: 
29,558

SAP CRM Middleware Overview

Topics to be discussed

Introduction

BDOC introduction

BDOC classes

sBDOC(Synchronization BDOC)

mBDOC(Messaging BDOC)

Initial setup steps for BDOC

BDOC monitoring steps

Introduction

SAP has a very strong middleware tool when compared to other applications like Oracle where it is pretty easy for SAP CRM application to connect with and exchange data with other SAP Applications like SAP BW, SAP R/3 system etc. This connection and data transfer is established through middleware. From an ERP application perspective this is an extremely important aspect the data exchange among the systems is kind of back-bone and the crux of very existence of the application. This data exchange can be of following types between other systems and CRM:

1. Initial data transfer which is also called as Initial Load in SAP terminology

2. Intermediate synchronization of data among the applications also called as Delta Load in SAP terminology

3. Synchronization.

Introduction

Just to throw some light on the kinds of data exchange mentioned above, it can be better understood if we look at the frequency of the data exchange. Initial load is primarily a one time activity wherein when the connectivity is established between the systems, the data is transferred from one system to another. This data can range from configuration data (like pricing conditions) to master data (like Business Partners and Products) to transactional data (like Sales Quotations, Contracts and Sales Orders).

Delta load is an activity of intermediate data transfer among the systems. This activity takes place more often than not to keep the data in various systems in sync and also take care of the changes to details of the data in various systems. It also takes care of newly created data in the system and distributes the same to other connected applications. Primarily this takes place in real-time and is primarily done automatically.

Synchronization activity is to take care of any out of sync data. This may be a cause of connectivity failure or might as well be an outcome of maintenance activity. This is primarily done manually as and when needed.

SAP CRM Middleware in SAP CRM Architecture

sBDoc (Synchronization BDoc)

Only used for data synchronization with mobile clients.

sBDoc types contain direct mappings to tables of the consolidated database. sBDoc types are used to make data persistent in the CDB and to exchange messages between the CRM Server and mobile clients.

Realignment and dependencies between sBDoc types are supported.

Initial setup steps for BDOC

Setting up of RFC connection

Selection of Industry

Maintain Default Customer Industry

Generation of Industry specific objects

Configuration of Publication, Sites and Subscription

Define Middleware Parameters

Registration of Destinations

Registration of Inbound Queues

Maintain Organization Unit Objects

Maintain Object Number Ranges

Set Up Objects Exchange

Steps involved in data exchange

Start Initial Load

Monitor Objects

Setup Delta Load

Create Synchronization Request

Start Synchronization Request

Monitor Synchronization Request

SAP CRM Middleware monitoring steps

Firstly use SMW01 to monitor BDOCS to check whether there are any BDOCS in error

Secondly check for inbound queues whether they are in error or no using transaction SMQ2

thirdly check  for inbound queues whether they are in error or no using transaction SMQ1

6 Comments
Labels in this area