0% found this document useful (0 votes)
99 views

Middleware Studdy Guide

Middleware is a tool within SAP CRM that enables data exchange between SAP CRM and other SAP and non-SAP systems. Adapters are used to map and convert data between different formats during data exchange via middleware. Several important tables and transactions related to middleware configuration, connectivity, replication settings and troubleshooting are discussed, including defining logical systems, RC connections, replication filters, subscriptions, and monitoring tools for BDoc messages.

Uploaded by

markyray
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
99 views

Middleware Studdy Guide

Middleware is a tool within SAP CRM that enables data exchange between SAP CRM and other SAP and non-SAP systems. Adapters are used to map and convert data between different formats during data exchange via middleware. Several important tables and transactions related to middleware configuration, connectivity, replication settings and troubleshooting are discussed, including defining logical systems, RC connections, replication filters, subscriptions, and monitoring tools for BDoc messages.

Uploaded by

markyray
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 7

SAP CRM: Master Data &

Middleware
Middleware is a tool which is inbuilt within SAP CRM that enables the SAP CRM
system to interact with various other SAP (R/3, BW, AP etc!" and non SAP
systems (3rd #arty web channel etc!"
$sin% middleware we can control what data should &low in and out o& the CRM
system and also monitor the same!
'he data e(chan%e between the CRM Middleware and e(ternal systems is
#er&ormed via ada#ters! 'he ada#ters ma# and convert data between various
&ormats!
)oad ob*ects can be e(chan%ed between a source and tar%et system, &or
e(am#le, between an SAP R/3 Bac+end and the CRM server! ,or -(am#le.
Business #artner master data and #roduct master data!
General Middleware settings for Data
Exchange
/atae(chan%e in CRM carries a very uni0ue #ers#ective and utili1es the CRM
Pro#rietary called CRM Middleware! -s#ecially we will see about the basic
settin%s which are re0uired &or the e(chan%e between CRM and -RP systems
considerin% Business #artners! Be&ore %ettin% into the im#ortant tables to be
chec+ed, we will loo+ into &ew im#ortant thin%s which are o& #rime interest!
Logical System:
A )o%ical system is #retty much im#ortant to be #resent #rior hand
because this is im#ortant to establish the connection with that
system!
When data is distributed between di&&erent systems, each individual
system within a networ+ has to be clearly identi&iable!
A )o%ical system is an a##lication system in which the a##lications
wor+ to%ether on a common data conte(t!
2n SAP terms, lo%ical system is considered to be a C)2-3'!
Since lo%ical system is the name used to identi&y a system uni0uely
within the networ+, two systems cannot have same name i& they
are connected to each other!
RC Connection:
R,C connections are the ones which #hysically enable the system
to share the in&ormation over the networ+!
'o create a R,C connection, use transaction SM45!
A&ter these two entities are ready, we can loo+ at certain tables which are
im#ortant at the -CC system &ollowed by the tables and certain transactions in
CRM system!
!m"ortant ta#les in ERP system:
CRMRCPAR $ Definitions for RC Connections%
Parameter
&ame
Descri"tion Recommended 'al(es
C)&S*ME
R
*ser of cons(mer that (ses the
)L+P "l(gin or the r,- ada"ter
f(nctionality to recei'e the data.
CRM
)/0&AME
or which o#1ect the destination
is allowed to recei'e the data
%2means all sending data
3.
RCDES+
S"ecifies the destination of the
CRM ser'er.
Any connected CRM
ser'er 2RC destination
for crm system 3
D)4&L)A
D
4hich 5ind of load wo(ld #e
allowed to send to destination.
%2all Load ty"es3
SE&D 6ML
6ML s(""ort2sho(ld data #e sent
in 6ML s(""ort3
Mixed Mode
% $ All the details indicated for the ta#les are for ill(strati'e "(r"oses
only. Any re7(ired data can #e (sed.

CRMC)&S*M $ Possi#le *sers of R,- Ada"ter (nctionality

Parameter
&ame
Descri"tion
Recommended
'al(es
C)&S*MER
*ser of cons(mer that (ses the )L+P
"l(gin or the r,- ada"ter f(nctionality to
recei'e the data.
CRM
A8+!9
lag to indicate whether the a""lication is
acti'e.
6
+E6+ Descri"tion CRM
:;PRE!6 Prefix for the : &ame (sed R-A
CRM!L+A/ $ ilter Conditions for Download
When there is a &ilter de&ined in R3AC6 transaction and the &ilters are
synchroni1ed, then all the &ilters will be #resent in this table in -CC! 2n CRM it
will be #resent SM,,2)'AB!

CRMPAR)L+P $ CRM )L+P Parameters
When the &ilters are maintained in CRM system, then there should be an entry
with the te(t CRM7,2)'-R2387AC'29- &or the corres#ndin% ada#ter ob*ect!
Sam#le screenshot.


CRMS*/+A/ $ S(#scri"tion +a#le for *"load and Download
)#1ects
'his is the table which will have the &unction modules &or the u#load or
download ob*ects!


!m"ortant ta#les and transaction in CRM system:
SM);ERPS< $ ERP$Site <eader ta#le
'his table &ills automatically whenever you create the site in the
CRM system by usin% the administration console (SM-AC"
Site 2/ is the uni0ue 2/ #rovided &or the each site created via
SM-AC!
CRMM;/*+;CRM)/0 $ /(ffer: 4hich /Ps are in 4hich Systems
'his table will carry the #artners which are success&ully re#licated
and the S2'- 2/ o& the system to which the data is re#licated!
SM)EAC 2+ransaction for Administraton console3
2n CRM server every system which is connected to it are de&ined
as sites and to enable the data e(chan%e the sites must be de&ine
in the CRM system usin% the tool SM-AC!
'o enable the data e(chan%e between the CRM server and the
connected system &irst we have to create the site &or the #articular
R,C destination in the SM-AC!
,ollowin% are the ste#s to create site.
#en transaction smoeac!
choose ob*ect ty#e S2'-!
Clic+ on create!
,ill all the re0uired &ields li+e name o& site , ty#e o& site!
Clic+ on site attribute button!
-nter the R,C destination in our case it should be any -CC
system and hit enter the system will automatically &etch all
the relevant data &or the site li+e lo%ical system name,release
o& the system etc!
A&ter creatin% the site the screen will loo+ li+e the below screen!
nce the site is created, the connected site has to be subscribed &or the
available #ublication!
P(#lication:
Publication is the de&inition o& one or more re#lication ob*ects with
s#eci&ic criteria &or re#lication means to say that Publication is +ind
o& container which may consist di&&erent re#lication ob*ect!
S(#scri"tion:
Subscri#tion is a re#lication ob*ect within the #ublication which
connected site can subscribe to it!
Subscri#tion is a means by which the site can subscribe &or some
#articular set o& re#lication ob*ects &rom #ublication which he want
to %et it &rom the CRM server!!
,or e%! Site can subscribe &or the all the business #artner to &low to
him or only the relationshi# should be re#licated to him! 2t all
de#ends on the customer re0uirement that what data he want to
re#licated to the connected site!

2n our case most o& the time we subscribe &or two business ob*ects
B$PA7MA23 i!e! all business #artner and B$PA7R-) i!e! all
business #artner relationshi# means to say that the connected -CC
side can acce#t all BP data and BP relationshi# data &rom the CRM
system other than this it will discard all other ty#es o& data!
A&ter de&inin% the -CC as a site in the CRM system we must assi%n
subscri#tion to it below are the screenshot which will show how to
create and assi%n subscri#tion to the -CC site!
,ollowin% will be the ste#s where the subscri#tion will be created
and assi%ned to the site!





2n the above scenario, we have only assi%ned one subscri#tion i!e :A))
B$S23-SS PAR'3-R R-)A'23S;2P< durin% re#lication only the
relationshi# &rom the CRM server will send to the -CC and not the
B$S23-SS PAR'3-R!
'here are mainly two +ind o& subscri#tion are available in the CRM
server!

+y"es of S(#scri"tion.
Sim#le Bul+ subscri#tion!
Sim#le bul+ subscri#tion is the standards subscri#tion which
%iven by the SAP standard SAP delivery and customer are not
allowed to ma+e any chan%e in this subscri#tion! 8eneral
recommendation is to have bul+ subscri#tion!
Sim#le intelli%ent subscri#tion!
Sim#le intelli%ent subscri#tion is somethin% which customer
can create their own subscri#tion with some &ilter criteria
accordin% to their re0uirement!
Middleware uses Business /ocument (B/oc" messa%es when trans&errin%
data between systems!

Sometimes #roblem durin% the re#lication re0uires monitorin% the Middleware!
SAP o&&ers standards tools to monitor B/oc errors messa%es in the system!
'he most used transaction is SMW=6 (/is#lay B/oc messa%es" accessed via
menu #ath Middleware>Monitoring>Message Flow>Display BDOC Messages!
;owever there are other use&ul transactions in the system!
Middleware Common +ransactions
When chec+in% Middleware #roblems, a review o& con&i%uration is necessary!
'he &ollowin% transactions are use&ul!

CRM Generation
SM8''A)
8enerate re0uired ob*ects &or CRM
Re#lication
8-3S'A'$S
Chec+ Status o& 8eneration
>obs
SM823/ 8enerate 2ndustry S#eci&ic b*ects
SM?R 0R,C Monitor/ Re%ister CSA ?ueue
SM;?$-$
- ?ueue demon


CRM Connecti'ity
SA)- /e&ine )o%ical system
SM45 Con&i%uration o& R,C Connections
SM-AC Administration Console


ERP Connecti'ity
SM?6 utbound ?ueue
SM?@ 2nbound ?ueue
SA)- /e&ine )o%ical system
SM45 Con&i%uration o& R,C Connections
CRM Re"lication Setting
R3AC3
Ada#ter ob*ect overview (re#lication &ilter
&or customi1in% ob*ects"
R3AS Start 2nitial )oad
R3AM6 Monitor re#lication status
R3AC6 Ada#ter b*ect verview


+ro(#leshoot /Doc Re"lication

When a B/oc is not re#licated success&ully, is necessary to chec+ the lo%s and
understand the reason that causes the #roblem!
'he &ollowin% transactions are use&ul.
SMW=6 /is#lay B/C Messa%es
SMW=@A B/oc Messa%e -rror Analysis.
Sum o& -rrors
SM?R 0R,C Monitor
SM?6 utbound 0R,C Monitor
SM?@ 2nbound 0R,C Monitor
SMWP CRM Middleware Monitorin%
Coc+#it
SMW' Middleware 'race
SM;?$-
$-
Monitor RAR ?ueues
SMBR-R
8
/elete Processed B/ocs
SMW=3 Show stats o& un#roc! B/oc
messa%es
SMW65 Co#y B/oc and #rocess
SMW@= Process B/ocs
SMW3RBM Convert B/oc Messa%es to
CM)
SMW3RC B/oc Messa%e -rror Recovery
SMW3W/ Watchdo% &or &ailed B/oc
Messa%es
Tx SMW02A BDoc Message Error Analysis: Sum of Errors

'his transaction is use&ul to %et a detailed error messa%e &or :B/C ty#e<! 'hat
allows summarisin% all errors &ounded in the system!


'he result list not only show the :Bdoc 'y#e< but also the com#onent a&&ected
that is use&ul in&ormation when researchin% SAP 3otes that could %ive any
indication o& the reason &or the error!



When #ressin% button :/etail Analysis< system navi%ate automatically to
transaction :SMW=6 /is#lay B/C Messa%es< and dis#lays the B/ocs Messa%e
a&&ected!






Tx SMO8REORG Delete processed BDocs

'his transaction allows deletin% B/ocs lo%s &rom the system! 2t could be run in
a test mode and &iltered by B/oc 'y#e, B/oc Messa%e 2/, $ser or chan%e
date/time! Cleanin% the lo% will allow users to &ocus on unresolved system
issues!



2n summary, middleware #roblems are usually based on con&i%uration! Always
have a loo+ not only to the middleware con&i%uration but also to the
com#onent con&i%uration! $sin% monitor tools, issues in more detail could be
chec+ed and +nowin% the DA##lication Com#onentD, a better &ilter could be
used when loo+in% &or SAP 3otes.

You might also like