You are on page 1of 91

CR2012 - SAP CRM Middleware

Enhancement

India SAP CoE, Slide 1

Middleware Enhancement
PrepareMe

TellMe

5
India SAP CoE, Slide 2

ShowMe

LetMe
HelpMe

Middleware Enhancement
PrepareMe

TellMe

5
India SAP CoE, Slide 3

ShowMe

LetMe
HelpMe

Introduction

Purpose
Use
Challenges

India SAP CoE, Slide 4

Purpose
Integration with all CRM applications and the existing Backend
landscape.
Develop a completely new application which has the full
integration with other applications provided by the CRM
Middleware.
Enhancing Middleware to have full integration with for any
enhancement in CRM

India SAP CoE, Slide 5

Use
Customizing Objects, often it is table existing in one system (e.g.
R/3 Backend), which should also be available in the connected
system (e.g. CRM server).
Typically Customizing Objects are not validated by an
application, because they normally contain data that is used for
validation itself. Customizing objects can be loaded from an R/3
Backend to CRM, to CDB or from the CRM system to the CDB.

India SAP CoE, Slide 6

Challenges
No considerable challenges are identified during this
replication. The RFC connection needs to be ensured between
R/3 and CRM systems.

India SAP CoE, Slide 7

Middleware Enhancement
PrepareMe

TellMe

5
India SAP CoE, Slide 8

ShowMe

LetMe
HelpMe

Object Replication
Most projects have additional requirements like customer-specific
fields and tables, which should be fully integrated with all CRM
applications and the existing Backend landscape. In some cases it
might also be required to develop a completely new application
which has the full integration with other applications throughout
the whole landscape.
Here we are going in details about 3 common Use Cases.

India SAP CoE, Slide 9

Table Replication Scenarios

Load Customizing Object from R/3 to CRM (new table)

Load Customizing Object from R/3 to CRM (new table)


using BDoc
Add new field in R/3 table communicated to the CRM
Online application

India SAP CoE, Slide 10

Middleware Enhancement
PrepareMe

TellMe

ShowMe

LetMe

5
India SAP CoE, Slide 11

HelpMe

Table Replication Scenarios

Load Customizing Object from R/3 to CRM (new table)

Load Customizing Object from R/3 to CRM (new table)


using BDoc
Add new field in R/3 table communicated to the CRM
Online application

India SAP CoE, Slide 12

Syntax Description
Important Transactions used in this exercise
SE11 : To create Custom table in R/3 as well as in CRM
SE37 : To create Function group and to copy
standard function Module in CRM
R3AC3 : Create adapter Object

(In CRM)

R3AS : Execute Adapter Object

(In CRM)

SMQ1 : Outbound Queue monitor (In R/3)

SMQ2 : Inbound Queue Monitor

(In CRM)

SMWP: Monitor Work Process

(In CRM)

India SAP CoE, Slide 13

Syntax Description
Important Function Modules used in this Exercise
MAP_BAPIMTCS_TO_CUSTOMIZING : Signature FM used for Mapping
in CRM
Important Tables / Structures used in this document
BAPIMTCS : Middleware Transaction Container Structure

India SAP CoE, Slide 14

Table replication without Bdoc


SAP CRM

SAP R/3
1.

- Create new table in R/3

India SAP CoE, Slide 15

2.

-Create a similar tables as of R/3

3.

- Create a Mapping Function


Module ( Use template
MAP_BAPIMTCS_TO_CUSTOMI
ZING)

4.

-Create MW Adaptor Object


*Object Class = Customizing
*Source Site type=
SMOF_ERPSITE R/3
*Table/Structure = new table of
R/3
*Mapping Module R/3 to CRM =
newly created Mapping F.M

5.

Process Initial Load

Create Custom Table in R/3


Create a customizing table
EX: ZCOUNTRY
Field

Key

Data Element

MANDT

Yes

MANDT

COUNTRY

Yes

TEXT30

CONTINENT

No

TEXT30

India SAP CoE, Slide 16

Create Custom Table in CRM


Create a new table as a copy of table ZCOUNTRY in the R/3 Backend
using the transaction SE11.
The final table structure should be similar to R/3:
Table ZCOUNTRY:
Field

Key

Data Element

MANDT

Yes

MANDT

COUNTRY

Yes

TEXT30

CONTINENT

No

TEXT30

India SAP CoE, Slide 17

Custom Table in CRM & R/3

India SAP CoE, Slide 18

Create a mapping function module in CRM


Use function module AP_BAPIMTCS_TO_CUSTOMIZING
as a template and copy it to the new function module say
ZMAP_BAPIMTCS_TO_CUSTOMIZING. (create custom
function group)

India SAP CoE, Slide 19

Code for custom FM


Map all data from container into database structure and
update database table
Loop the Bapimtcs.
Check DA for data
Populate the data into the custom table.
ENDLOOP.
Update the database table directly
INSERT THE DATA INTO THE CUSTOM TABLE
Ensure that no validation flow is called
E_DO_NOT_CALL_GDH = 'X'.20
India SAP CoE, Slide 20

Create a MW adapter object to enable initial


load
To create the adapter object, go to transaction R3AC3 (Maintenance of
customizing objects). Click on Create
Create

India SAP CoE, Slide 21

Adapter Object Overview


Enter a name for the object. In our example the object name is
ZCRMCOUNTRY,

Description is Countries and continents.


Press return so that the other fields are ready for input.
Enter a description of your object in the field right of the object name
e.g. Countries and Continents CRM.
The object class is already filled with CUSTOMIZING.
Leave the field Linked BDoc type - empty
Enter a block size 1000

India SAP CoE, Slide 22

Adapter Object Overview


Adapter Object Name

Enter Description
This will come automatically for
customizing objects

Block Size

India SAP CoE, Slide 23

Adapter Object details


Tab strip Initial Flow Contexts
In our example the source site type is R/3. Choose the entry from the
combo box. All the other fields are filled automatically, especially the
target site type CRM.

Provide R/3

India SAP CoE, Slide 24

Adapter Object details


Tab strip Tables/Structures
Enter the table name ZCOUNTRY in column table (source site). All
other fields can be left empty as we provide the mapping with our mapping
function module.

Provide Table Name

India SAP CoE, Slide 25

Adapter Object details


Tab strip Mapping Modules R/3 to CRM
Provide the mapping function module created for this object in
our case it is ZMAP_BAPIMTCS_TO_CUSTOMIZING

Tab strip Mapping Modules R/3 to CRM

Provide Custom Mapping FM

India SAP CoE, Slide 26

Test initial load (Tcode: R3AS)


To test the work, go to transaction r3as, select object
ZCRMCOUNTRY, Execute and start the initial load.

Execute

Provide The Adapter Object

When you press enter these


fields will be filled automatically

India SAP CoE, Slide 27

Test initial load (Tcode: R3AS)


Once the initial load is started you will find the popup

India SAP CoE, Slide 28

Table Replication

Load Customizing Object from R/3 to CRM (new table)


Load Customizing Object from R/3 to CRM (new table)
using BDoc
Add new field in R/3 table communicated to the CRM
Online application

India SAP CoE, Slide 29

Table replication using Bdoc


SAP CRM

SAP R/3
1.

- Create new table in R/3

2.

3.

-Create a similar tables as of R/3

- Create a Transfer Structure


(Table Fields without Client)

India SAP CoE, Slide 30

4.

- Create a Transfer Structure


(Table Fields without Client)

5.

-Create a extension part Structure


for new table

6.

-Create a Message BDoc

7.

-MW adapter mapping function


module in CRM (using template
SAMPLE_INTERFACE_BAPIMTC
S_BDOC )

Table replication using Bdoc


SAP CRM

SAP R/3
8.
9.

- Create a mapping function


module with table parameters 1.
newly created table, 2.
BAPIMTCS

10.

- Create a Extract Function


Module (using template
CRM_SAMPLE_EXTRACT_MOD
ULE )

11.

- Registering the extractor module


in table CRMSUBTAB

12.

-Create a Validation F.M

13.

-Maintain the flow table in


SMW3BDOCIF (entering Validation
F.M)

14.

India SAP CoE, Slide 31

-Create a MW Adaptor Object,


*Object Class = Customizing Class,
*Source Site type=
SMOF_ERPSITE R/3,
*Table/Structure = new table of R/3,
*Mapping Module R/3 to CRM =
newly created Mapping F.M

Process Initial Load

Syntax Description
Important Transactions used in this exercise
SE11 : To create Custom table in R/3 as well as in CRM
SE37 : To create Function group and to copy
standard function Module in CRM
R3AC3 : Create adapter Object

(In CRM)

R3AS : Execute Adapter Object

(In CRM)

SMQ1 : Outbound Queue monitor (In R/3)

SMQ2 : Inbound Queue Monitor

(In CRM)

SMWP: Monitor Work Process

(In CRM)

India SAP CoE, Slide 32

Syntax Description
Important Function Modules used in this Exercise
CRM_SAMPLE_EXTRACT_MODULE:
Extractor FM used for extracting data in R/3.
SAMPLE_INTERFACE_BAPIMTCS_BDOC:
Signature Mapping FM from R/3 to CRM.
Z_CRS_MAP_ZUOM_BAPIMCTS:
Custom FM to send data from R/3 to CRM
server via the MW adapter framework.
Important Tables / Structures used in this document
BAPIMTCS :
Middleware Transaction Container Structure

India SAP CoE, Slide 33

Create Custom Table in R/3


Create a customizing table
EX: Z_UOM
Field

Key

Data Element

MANDT

Yes

MANDT

UOM

Yes

CHAR10

DESCRIPTION

No

CHAR25

India SAP CoE, Slide 34

Custom Table in CRM


Create a customized transfer structure. The data exchange
between R/3 Backend and CRM server realized by transfer
structures, which are then sent via BAPIMTCS data containers.
EX: Z_UOM_TRANSFER
Component

Data Element

UOM

CHAR10

DESCRIPTION

CHAR25

India SAP CoE, Slide 35

Create a mapping function module in R/3


Create a mapping FM (Z_CRS_MAP_ZUOM_BAPIMTCS) in R/3

Use function module SAMPLE_INTERFACE_BAPIMTCS_BDOC


as a template and copy it to the new function module say
Z_CRS_MAP_ZUOM_BAPIMCTS . (create custom function group)

India SAP CoE, Slide 36

Code for custom FM in R/3


FUNCTION Z_CRS_MAP_ZUOM_BAPIMCTS.
Create transfer structure LIKE ZDC_K_UOM_TRANSFER.
* Map all selected R/3 table entries
LOOP AT r3tables.
* Map R/3 table entry into transfer structure
MOVE-CORRESPONDING r3tables TO transfer structure.
* Store transfer structure into data container
et_bapimtcs-tabname = 'Z_UOM_TRANSFER'.
MOVE lv_transfer_structure TO bapimtcs data field.
* other fields of BAPIMTCS are not relevant for this example
APPEND et_bapimtcs.
ENDLOOP.

India SAP CoE, Slide 37

Create an extractor FM in R/3


Create an extractor FM (Z_EXTRACTR3_UOM) by copying the
standard FM (CRM_SAMPLE_EXTRACT_MODULE) to extract data
from the custom table created.

India SAP CoE, Slide 38

Register the extractor FM in R/3


In CRMSUBTAB of R/3 Maintain the following entries
Field

Value

Consumer

CRM

Object name

Z_CRM_UOM

Up or download

Object class

Z_CRM_UOM_CL

Function module Z_EXTRACTR3_UOM

India SAP CoE, Slide 39

Create custom Table in CRM


Create custom table Z_UOM
Field

Key

Data Element

MANDT

Yes

MANDT

UOM

Yes

CHAR10

DESCRIPTION

No

CHAR25

India SAP CoE, Slide 40

Create custom Transfer Structure in CRM


Create a customized transfer structure. The data exchange between R/3
Backend and CRM server realized by transfer structures, which are then
sent via BAPIMTCS data containers.
EX: Z_UOM_TRANSFER
Component

Data Element

MANDT

CHAR3

UOM

CHAR10

DESCRIPTION

CHAR25

India SAP CoE, Slide 41

Creating mBDoc
Create structure Z_CRM_UOM_ROOT_CONTROL
Component

Component type

TASK

Char1

Create structure Root Data Z_CRM_UOM_ROOT_DATA


Component

Component type

GUID

SMO_GUID

UOM

CHAR10

DESCRIPTION

CHAR25

India SAP CoE, Slide 42

Creating mBDoc
Create structure Root Data Z_CRM_UOM_ROOT_DATAX
Component

Component type

UOM

CHAR10

DESCRIPTION

CHAR25

Create structure Z_CRM_UOM_ROOT for the entire root segment with the following
component.
Component

Component type

CONTROL

Z_CRM_UOM_ROOT_CONTROL

DATA

Z_CRM_UOM_ROOT_DATA

DATAX

Z_CRM_UOM_ROOT_DATAX

India SAP CoE, Slide 43

Creating mBDoc
Create structure Z_CRM_UOM_ROOT_TABLE with line type
Z_CRM_UOM_ROOT in order to carry multiple messaging BDoc
instances, i.e. root segments, it is necessary to create the standard
table.

Finally it is necessary to create the entire extension part, which


should hold all data segments. The structure Z_CRM_UOM_EXT
Component

Component type

Z_CRM_UOM_ROOT Z_CRM_UOM_ROOT_TABLE

India SAP CoE, Slide 44

Creating a Messaging BDoc


Create and activate a new messaging BDoc type that can transport the
content of the table Z_UOM.

Call transaction SBDM. Press the Button create BDoc, F5 or


Go via the menu BDoc -> Create BDoc.
Details of BDoc
Tab strip BDoc Overview
Enter a name and a short name for the BDoc, here for example
name= ZUOM_MESG, short name=ZUOM_MESG.

India SAP CoE, Slide 45

Creating a Messaging BDoc


Enter a description for your BDoc, e.g. MESG BDoc for UOM &
Description.

Make sure, the BDoc Class is set to Messaging BDoc


Fill the field Related Data type in tab General Data" with the name of the
extension part structure. Enter Z_CRM_UOM_EXT.

India SAP CoE, Slide 46

Creating messaging BDoc type.


Classical part of the new mBdoc
The classical part is used to determine the receiver of BDoc
messages. To create the classical part, add a segment to the BDoc
type.
Creating the Segments
Press the Button Create Segment,
F7 or select via the menu BDoc -> Create Segment.
Tab strip Segment Overview
Enter the name and description for the segment, for example
segment name = Z_CRM_UOM_ROOT, description Table Z_UOM.

India SAP CoE, Slide 47

Creating Classical part of the new


messaging BDoc type.
Tab strip Segment Fields
Go to the Segment Fields tab and specify the fields of the new segment. Use
the following fields:
Field Name

Key

Data Element

GUID

SMO_GUID

DESCRIPTION

TEXT25

Save your changes. Check your new messaging BDoc type and activate it.

India SAP CoE, Slide 48

Creation of MW Adapter object to enable


initial load.
Object Overview
Enter a name for the object. In our example the object name is
Z_CRM_UOM;
Provide description Adaptor Object UOM using
MBDoc.
Press return so that the other fields are ready for input.
Enter a description of your object in the field right of the object
name, e.g. Adaptor Object UOM using MBDoc.
The object class is changed to Z_CRM_UOM_CL .

India SAP CoE, Slide 49

Creation of adapter object to enable initial


load.
Select the value ZUOM_MESG for the field Linked BDoc type

Enter a block size (eg 1000) .

India SAP CoE, Slide 50

Creation of adapter object to enable initial


load.
Tab strip Initial Flow Contexts
In our example the source site type is R/3. Choose the entry from the
combo box. All the other fields are filled automatically, especially the
target site type CRM.

Tab strip Tables/Structures


In this tab strip the tables which are to be selected can be entered.
Enter the table name Z_UOM in column table (source site). And mention
Z_UOM in the mapped Table structure.

India SAP CoE, Slide 51

Creation of adapter object to enable initial


load.
Tab strip Mapping modules

Enter Z_MAP_UOM_BAPIMTCS_MBDOC in column Module


name.

Save your changes.

India SAP CoE, Slide 52

Creation of mapping function module in


CRM (Inbound )
To process the data in the CRM server it is necessary to map the data
sent via the container structure BAPIMTCS into an mBDoc.
Copy the Signature FM SAMPLE_INTERFACE_BAPIMTCS_BDOC
to Z_MAP_UOM_BAPIMTCS_MBDOC and select the function group
you created in the previous step.

India SAP CoE, Slide 53

Test initial load


To test the work, go to transaction r3as, select object Z_UOM, Execute
and start the initial load.
Execute
Provide The Adapter Object

When you press enter these


fields will be filled automatically

India SAP CoE, Slide 54

Test initial load: (tcode. R3AS)


Once the initial load is started you will find the popup

India SAP CoE, Slide 55

Table Replication

Load Customizing Object from R/3 to CRM (new table)


Load Customizing Object from R/3 to CRM (new table)
using BDoc
Add new field in R/3 table communicated to the CRM
Online application

India SAP CoE, Slide 56

Syntax Description
Important Transactions used in this exercise
SE11 : To create Custom table in R/3 as well as in CRM
SE37 : To create Function group and to copy
standard function Module in CRM
R3AC3 : Create adapter Object

(In CRM)

R3AS : Execute Adapter Object

(In CRM)

SMQ1 : Outbound Queue monitor (In R/3)

SMQ2 : Inbound Queue Monitor

(In CRM)

SMWP: Monitor Work Process

(In CRM)

India SAP CoE, Slide 57

Syntax Description
Important Function Modules used in this Exercise

MAP_BAPIMTCS_TO_CUSTOMIZING : Signature FM used for


Mapping in CRM
Important Tables / Structures used in this document
BAPIMTCS : Middleware Transaction Container Structure

India SAP CoE, Slide 58

Add new field in R/3 table communicate to the


CRM Online application
SAP R/3
1.

- Extend database table by using


Append Structure

2.

- Create a transfer structure, the


fields are similar to append
structure

3.

-Create F.M which returns the


value of global fields with export
parameters
*Enhanced table name,
*Enhanced table name

4.

-Write macro to fulfill Unicode


support

5.

-implement user exit in R/3 adapter,


outbound direction

6.

-Register the user exit in tables


TBE24, TPS34

India SAP CoE, Slide 59

SAP CRM

Add new field in R/3 table communicated to the CRM Online application
SAP CRM

SAP R/3
7.

- Add new fields which are added


in R/3 by using EEWB

8.

- Create a transfer structure

9.

- Enhance mBDoc type

10.

-Write macro to fulfill Unicode


support

11.

-Implement the user exit in R3


adapter, inbound direction.

12.

-Create F.M in CRM which maps


the field coming from R/3 to the
field created by EEW in CRM

13.

-Register the user exit in tables


TBE24, TPS34,
CRMC_BUT_CALL_FU

14.
India SAP CoE, Slide 60

Process Initial Load

Extend DDIC in R/3


Create a new domain (ZCONTINENT)

Create a new data element (ZCONTINENT)

India SAP CoE, Slide 61

Extend DDIC in R/3


Extend database table (KNA1 Table)
Go to -> Append structure
Append structure as ZZCONTINENT
Component ZZCONT and data element ZCONTINENT

India SAP CoE, Slide 62

Extend DDIC in R/3


Create the structure ZCONTINENT_TRANSFER
Component ZZCONT and data element ZCONTINENT

India SAP CoE, Slide 63

Implement User Exit in R/3


To transfer the field in both initial and delta load you can use a user exit of
the R/3 adapter which is in a central place. The user exit with interface
CRM0_200 is called in function module CRS_SEND_TO_SERVER, which
is the central sending functionality of the MW adapter framework.
Create function module
Z_USER_EXIT_BEFORE_SEND_TO_MW (Copy FM
SAMPLE_PROCESS_CRM0_200 as a template)

India SAP CoE, Slide 64

Implement User Exit in R/3


Code in the function Module:
Z_USER_EXIT_BEFORE_SEND_TO_MW

Check Object Class is BUPA.


Check Object Name is CUSTOMER_MAIN.
Define a macro for Unicode support
Determine next free CURRDNO
Get KUNNR (Customer Number) from BAPIMTCS structure
Field I_BAPICRMDH2- DWNLOADTYP distinguish between
delta or initial Load
7. If delta load Read the data from global memory
8. If initial load read the data from KNA1 table
9. Add new BAPIMTCS Business Partner - New Field: City
Code
1.
2.
3.
4.
5.
6.

India SAP CoE, Slide 65

Implement User Exit in R/3


Parameters of the Function Module:
Z_USER_EXIT_BEFORE_SEND_TO_MW

India SAP CoE, Slide 66

Register user exit (R/3 Backend)


Table maintenance: TBE24
Parameter

Value

Product

ZCRM

Text

User Exits in R/3


adapter

RFC Destination

Initial

Active

India SAP CoE, Slide 67

Register user exit (R/3 Backend)


Table maintenance: TPS34
Parameter

Value

Process

CRM0_200

Country

Initial

Application

Initial

Function Module

Z_USER_EXIT_BEFORE_SEND
_TO_MW

Product

ZCRM

India SAP CoE, Slide 68

Enhance DDIC in CRM


1. Create a new domain (ZCONTINENT)

2. Create a new data element (ZCONTINENT)

India SAP CoE, Slide 69

Enhance DDIC in CRM


3. Extend database table (BUT000 Table)
Goto -> Append structure
Append structure as ZZCONTINENT
Component ZZCONT and data element
ZCONTINENT

India SAP CoE, Slide 70

Enhance DDIC in CRM


4. Create the structure ZCONTINENT_TRANSFER
Component ZZCONT and data element
ZCONTINENT

India SAP CoE, Slide 71

Enhance mBDoc Type


1. Business Partner BDoc type BUPA_MAIN uses the
structure BUS_EI_EXTERN
2. For the data type BUS_EI_EXTERN in the ABAP
Dictionary in change mode. Then double-click on the
component CENTRAL_DATA, after that on the
component COMMON, and finally on DATA. You are now
in the substructure BUS_EI_BUPA_CENTRAL_DATA;
where you can create a new append structure
3. Add the name ZCONTINENT with component ZZCONT
and component type ZCONTINENT

India SAP CoE, Slide 72

Enhance mBDoc Type


Structure : BUS_EI_EXTERN

India SAP CoE, Slide 73

Enhance mBDoc Type


Structure : BUS_EI_CENTRAL_DATA

India SAP CoE, Slide 74

Enhance mBDoc Type


Structure: Append Structure of
ZBUS_EI_BUPA_CENTRAL_DATA

India SAP CoE, Slide 75

Implement user exit in R/3 adapter, inbound


direction (CRM)
Create function module Z_USER_EXIT_BAPI_CRM_SAVE
Pseudo Code:
Check whether Exit was called during Download
Check E_BAPICRMDH2-REF_ID is initial and
BAPICRMDH2-DWNLOADTYP is D
Check Object Name (Business Transaction) is BUPA_MAIN or
CUSTOMER_MAIN
Define a macro to get full Unicode support
Move MESSAGE_EXT to BUS_EI_MAIN (structure).
Process TI_BAPIMTCS with condition TABNAME as
'ZCONTINENT' .
Process BUS_EI_MAIN with condition
header-object_instance-bpartnerguid = ti_bapimtcs-objkey
Assign the value to data-ZZCOUNT field

India SAP CoE, Slide 76

Implement User Exit in R/3


Parameters of the Function Module:
Z_USER_EXIT_BAPI_CRM_SAVE

India SAP CoE, Slide 77

Register user exit (CRM)


Table maintenance: TBE24
Parameter

Value

Product

ZCRM

Text

User Exits in MW adapter

RFC Destination

Initial

Active

India SAP CoE, Slide 78

Register user exit (CRM)


Table maintenance: TPS34
Parameter

Value

Process

SMOUTIL3

Country

Initial

Application

Initial

Function Module

Z_USER_EXIT_BAPI_CRM_SAVE

Product

ZCRM

India SAP CoE, Slide 79

Enhance the validation service for the


mBDoc
Create function module Z_CRMIN_APPEND_FIELDS
Pseudo Code:
Get Partner Guid, Partner external number from
BUS_EI_EXTERN structure
Retrieve Partner Number by calling Function Module
BUPA_NUMBERS_GET
If Partner Number is initial, then retrieve the data from the
memory by using the Function Module
BUP_MEMORY_BUT000_GET
Move the ZZCONT value (c_bp_struct-central_datacommon-data-zzcont) to bus000 structure
Put table back to global memory by using Function Module
BUP_MEMORY_BUT000_FILL

India SAP CoE, Slide 80

Implement User Exit in R/3


Parameters of the Function Module: Z_CRMIN_APPEND_FIELDS

India SAP CoE, Slide 81

Register validation functionality


Table maintenance: CRMC_BUT_CALL_FU
Parameter

Value

Event

CRMIN

Object

BUPA or Business Partner

Item

Enter a 6-figure item number


greater than existing entries

Function Module

Z_CRMIN_APPEND_FIELDS

Call

Tick the check-box

India SAP CoE, Slide 82

Start Initial load


Transaction: r3as

India SAP CoE, Slide 83

Middleware Enhancement
PrepareMe

TellMe

ShowMe

LetMe

5
India SAP CoE, Slide 84

HelpMe

Exercises
Create a custom table with 2 fields in ERP side and get it
replicated in CRM with some validations.

India SAP CoE, Slide 85

Middleware Enhancement
PrepareMe

TellMe

ShowMe

LetMe

5
India SAP CoE, Slide 86

HelpMe

HelpMe
Tips and Tricks
Additional Info

India SAP CoE, Slide 87

Tips and Tricks


In inbound Queue (Tcode SMQ2 in CRM as the CRM is the inbound to this
process) if the process of initial load is successful you will not find your entry
in this.
If your adapter object is in the list of adapter object queues, to know
the details of the queue, double click on the adapter object.

India SAP CoE, Slide 88

Tips and Tricks


Double click on the corresponding status to find the description of the Error
Double Click

India SAP CoE, Slide 89

Tips and Tricks


To monitor all the queue objects go with the tcode SMWP
CRM Middleware monitoring cockpit

India SAP CoE, Slide 90

Tips and Tricks


To monitor the current running adapter object double click on
running objects you can see the status of the running objects

India SAP CoE, Slide 91