cr500_en_bbpcrm310_col22_fv_251104.pdf
DESCRIPTION
SAP CRM MiddlewareTRANSCRIPT
© SAP AG CR500 1
SAP AG 2001
&5����&50�0LGGOHZDUH
&5���&5���
�&50�0LGGOHZDUH�2YHUYLHZ�&50�0LGGOHZDUH�2YHUYLHZ
n BBPCRM 310 R/3 Release 620
n 2002/Q3
n Material number 5005 5032
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2
SAP AG 2001
&RS\ULJKW������6$3�$*���$OO�ULJKWV�UHVHUYHG�1R�SDUW�RI�WKLV�SXEOLFDWLRQ�PD\�EH�UHSURGXFHG�RU�WUDQVPLWWHG�LQDQ\�IRUP�RU�IRU�DQ\�SXUSRVH�ZLWKRXW�WKH�H[SUHVV�SHUPLVVLRQ�RI6$3�$*��7KH�LQIRUPDWLRQ�FRQWDLQHG�KHUHLQ�PD\�EH�FKDQJHGZLWKRXW�SULRU�QRWLFH�$OO�ULJKWV�UHVHUYHG�
&RS\ULJKW
7UDGHPDUNV�n Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
n Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registeredtrademarks of Microsoft Corporation.
n 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.
n ORACLE® is a registered trademark of ORACLE Corporation.
n INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated.
n UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
n HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World WideWeb Consortium, Massachusetts Institute of Technology.
n JAVA® is a registered trademark of Sun Microsystems, Inc.
n JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license fortechnology invented and implemented by Netscape.
n SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries allover the world. All other products mentioned are trademarks or registered trademarks of theirrespective companies.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3
SAP AG 2002
l %DVLF�NQRZOHGJH�RI�&50l %HLQJ�IDPLOLDU�ZLWK�:LQGRZV�17�����l &5������&50�2YHUYLHZ�FRXUVHl 5HFRPPHQGHG�FRXUVHV
�GHSHQGLQJ�RQ�WKH�VFHQDULR��n &5������0RELOH�6DOHV��0RELOH�6HUYLFHn &5������,QWHUDFWLRQ�&HQWHU�LQ�&50n &5������,QWHUQHW�6DOHV
&RXUVH�3UHUHTXLVLWHV
n General understanding of CRM and basic Windows NT and R/3 knowledge is essential for thiscourse.
n To put this course into the general SAP CRM context, an overall understanding of the CRM SAPlandscape is necessary. The CR010 course provides this overview.
n Depending on your involvement in CRM and on your scenario, further background knowledge maybe helpful. The SAP CRM curriculum provides many courses for the various scenarios.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4
SAP AG 2002
l $XGLHQFH�n 7HFKQLFDO�FRQVXOWDQWVn $Q\RQH�FXVWRPL]LQJ�DQG�RU�DGPLQLVWHULQJ
WKH�&50�0LGGOHZDUH
l 'XUDWLRQ����GD\V
7DUJHW�*URXS
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 1-1
SAP AG 2001
l &RXUVH�*RDOVl &RXUVH�2EMHFWLYHVl &RXUVH�&RQWHQWl &RXUVH�2YHUYLHZ�'LDJUDP
&RQWHQWV�
&RXUVH�2YHUYLHZ
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 1-2
SAP AG 2001
7KLV�FRXUVH�ZLOO�SUHSDUH�\RX�WR�
&RXUVH�*RDOV
l 8QGHUVWDQG�WKH�VHWXS�DQG�FRQILJXUDWLRQ�SURFHVVl ([SODLQ�FXVWRPL]LQJ�DVSHFWVl 3HUIRUP�DGPLQLVWHULQJ�WDVNV
RI�WKH�&50�0LGGOHZDUH
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 1-3
SAP AG 2001
&RXUVH�2EMHFWLYHV
$W�WKH�FRQFOXVLRQ�RI�WKLV�FRXUVH��\RX�ZLOO�EH�DEOH�WR�l ([SODLQ�WKH�EDVLF�FRQFHSWV�RI�WKH�&50�0LGGOHZDUHl 6HW�XS�DQG�FRQWURO�WKH�GDWD�H[FKDQJH�EHWZHHQ�WKH
&50�6HUYHU�DQG�DQ�6$3�5���%DFN�(QGl ([SODLQ�WKH�FRQQHFWLRQ�WR�QRQ�6$3�V\VWHPVl ([SODLQ�WKH�UHSOLFDWLRQ�PHFKDQLVPl 0RQLWRU�WKH�&50�0LGGOHZDUHl 'HILQH�WKH�W\SLFDO�FXVWRPL]LQJ�VWHSV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 1-4
SAP AG 2001
Unit 1 &RXUVH�2YHUYLHZUnit 2 0LGGOHZDUH�2YHUYLHZUnit 3 &RQFHSWV�RI�WKH�&50
0LGGOHZDUHUnit 4 5HSOLFDWLRQ�$GPLQLVWUDWLRQUnit 5 'DWD�([FKDQJH�ZLWK�5��
%DFN�(QGVUnit 6 'DWD�([FKDQJH�ZLWK�RWKHU
6\VWHPV
3UHIDFH
Unit 7 6SHFLDO�)HDWXUHV�IRUPRELOH�6FHQDULRV
Unit 8 0RQLWRULQJ��(UURU+DQGOLQJ
Unit 9 ,QVWDOODWLRQ�&RQILJXUDWLRQ
Unit 10 )XUWKHU�,QIRUPDWLRQUnit 11 &RXUVH�:UDS�8S
&RXUVH�&RQWHQW
$SSHQGL[
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 1-5
SAP AG 2001
&RXUVH�2YHUYLHZ�'LDJUDP
0LGGOHZDUH�2YHUYLHZ0LGGOHZDUH�2YHUYLHZ
&RQFHSWV�RI�WKH�&50�0LGGOHZDUH&RQFHSWV�RI�WKH�&50�0LGGOHZDUH
5HSOLFDWLRQ�$GPLQLVWUDWLRQ5HSOLFDWLRQ�$GPLQLVWUDWLRQ
0RQLWRULQJ��(UURU�+DQGOLQJ0RQLWRULQJ��(UURU�+DQGOLQJ
,QVWDOODWLRQ��&RQILJXUDWLRQ,QVWDOODWLRQ��&RQILJXUDWLRQ
6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ
'DWD�([FKDQJH�ZLWK�5��%DFN�(QGV'DWD�([FKDQJH�ZLWK�5��%DFN�(QGV
'DWD�([FKDQJH�ZLWK�RWKHU6\VWHPV'DWD�([FKDQJH�ZLWK�RWKHU6\VWHPV
)XUWKHU�,QIRUPDWLRQ)XUWKHU�,QIRUPDWLRQ
&RXUVH�:UDS�8S&RXUVH�:UDS�8S
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-1
SAP AG 2001
&50�0LGGOHZDUH�2YHUYLHZ
l P\6$3�&50�2YHUYLHZl P\6$3�&50�$UFKLWHFWXUH�2YHUYLHZl 7\SLFDO�&50�0LGGOHZDUH�&RPSRQHQWVl &50�0LGGOHZDUH�7DVNV
&RQWHQWV�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-2
SAP AG 2001
l 'HVFULEH�WKH�FRPSRQHQWV�RI�WKH�P\6$3�&50V\VWHP�ODQGVFDSH
l ([SODLQ�WKH�FRQQHFWLRQ�DQG�GDWD�H[FKDQJHEHWZHHQ�WKH�YDULRXV�&50�FRPSRQHQWV�ZLWKWKH�&50�0LGGOHZDUH
l ([SODLQ�WKH�PDLQ�WDVNV�RI�WKH�&50�0LGGOHZDUH
$W�WKH�FRQFOXVLRQ�RI�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�
0LGGOHZDUH�2YHUYLHZ��8QLW�2EMHFWLYHV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-3
SAP AG 2001
&RXUVH�2YHUYLHZ�'LDJUDP
0LGGOHZDUH�2YHUYLHZ0LGGOHZDUH�2YHUYLHZ
&RQFHSWV�RI�WKH�&50�0LGGOHZDUH&RQFHSWV�RI�WKH�&50�0LGGOHZDUH
5HSOLFDWLRQ�$GPLQLVWUDWLRQ5HSOLFDWLRQ�$GPLQLVWUDWLRQ
0RQLWRULQJ��(UURU�+DQGOLQJ0RQLWRULQJ��(UURU�+DQGOLQJ
,QVWDOODWLRQ��&RQILJXUDWLRQ,QVWDOODWLRQ��&RQILJXUDWLRQ
6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ
'DWD�([FKDQJH�ZLWK�5��%DFN�(QGV'DWD�([FKDQJH�ZLWK�5��%DFN�(QGV
'DWD�([FKDQJH�ZLWK�RWKHU6\VWHPV'DWD�([FKDQJH�ZLWK�RWKHU6\VWHPV
)XUWKHU�,QIRUPDWLRQ)XUWKHU�,QIRUPDWLRQ
&RXUVH�:UDS�8S&RXUVH�:UDS�8S
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-4
SAP AG 2001
:KDW�LVP\6$3�&50"
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-5
SAP AG 2001
&XVWRPHU�5HODWLRQVKLS�0DQDJHPHQW�ZLWK�P\6$3&50
0RELOH
7HOHSKRQ\
,QWHUQHW
&&ROODERUDWLYH22SHUDWLRQDO�
$$QDO\WLFDO7KH�1HZ�&XVWRPHU�&HQWULF�(�%XVLQHVV�6ROXWLRQ
IRU�WKH�(QWLUH�&XVWRPHU�/LIH�&\FOH�
n Customer Engagement
é Marketing Analytics, Campaign Management, Telemarketing, E-Marketing, Lead Management
n Business Transaction
é Sales Analytics, Account and Contact Management, Opportunity Management, Telesales, FieldSales (Mobile Sales, Handheld Sales), E-Selling, Internet Pricing and Configuration, OrderAcquisition
n Order Fulfillment
é Fulfillment Analytics, Logistics Management, Credit Management, Billing
n Customer Service
é Service Analytics, Customer Care and Helpdesk, Contracts and Installed Base Management,Enterprise Intelligence, Field Service and Dispatch (Mobile Service, Handheld Service), E-Service
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-6
SAP AG 2001
P\6$3�&50�$UFKLWHFWXUH2YHUYLHZ
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-7
SAP AG 2001
P\6$3�&50�$UFKLWHFWXUH
PXOWL�&OLHQWV
&50�0LGGOHZDUH���'DWD([FKDQJH
3RUWDO
&50
%: 5��
&50�0LGGOHZDUH��0RELOH�&OLHQW
6\QFKURQL]DWLRQ
0RELOH3UHVHQWDWLRQ
&OLHQW
3UHVHQWDWLRQ/D\HU
$SSOLFDWLRQ
'DWDEDVH�/D\HU
6\QFKURQL]DWLRQ�'DWD�([FKDQJH
/D\HU���
0RELO
H�&50
�$SS
OLFDWL
RQV
0RELOH�&OLHQW
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-8
SAP AG 2002
��&50�6HUYHU
$V�RQH�ELJORJLFDO�ER[$V�RQH�ELJORJLFDO�ER[
6$3�3RUWDOV
,QWHUQHW7HOHSKRQH
QRQ�5���%DFN�(QG�
6$3�5��%DFN�(QG
%:
'DWD�([FKDQJH�&KDQQHOV
(PDLO
0RELOH�&OLHQWV
n The mySAP.com application component for &XVWRPHU�5HODWLRQVKLS�0DQDJHPHQW��&50� consistsof a central &50�6HUYHU and various extensions to support different ways of accessing the system.This slide shows different possibilities to access the CRM applications. Depending on your actualbusiness requirements, not all extensions need to be installed or used.
n Some applications like the Interaction Center, Internet Sales or Marketing run on the CRM Server.These applications are called the &50�6HUYHU�$SSOLFDWLRQV.
n The CRM Server may be accessed via various communication channels, such as:
é The CRM Server Applications can be accessed via the mySAP Workplace by CRM users such assales managers or contact center agents.
é Internet users may configure and order products or services using the Internet components of theCRM application component.
é The mobile sales force or mobile service engineers can connect to the system from their laptops orpervasive devices to exchange the latest information with the CRM Server Application.
é Finally, customers may use the phone, fax, or email to reach the sales or service representativesusing the integrated contact center solutions.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-9
SAP AG 2002
,QWHUQHW
0RELOH�&OLHQWV
7HOHSKRQH
P\6$3�&50�����6\VWHP�/DQGVFDSH
&R�EURZVH
��&50�6HUYHU
$V�RQH�ELJORJLFDO�ER[$V�RQH�ELJORJLFDO�ER[
&RPPXQLFDWLRQ6WDWLRQ
3%;
(�0DLO
&7,
(�0DLO6HUYHU
:HE6HUYHU
(�6HOOLQJ
n The Mobile Sales and Mobile Service Applications of mySAP CRM support a company’s mobilesales force and mobile service engineers respectively, providing full access to all the necessary dataon laptop computers. This data is kept up-to-date by regular data exchange using the middlewarecomponent contained on the central CRM Server.
n CRM Mobile Sales and Service users carry a full-blown PC application including a local database ontheir laptops. They connect to the CRM Server from time to time via phone or network to exchangedata accumulated and stored in queues at both ends. This connection is established via aCommunication Station, where DCOM calls from the mobile clients are transformed to RFC callsthat go to the CRM Middleware.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-10
SAP AG 2001
6$3�5��%DFN�(QG0RELOH�&OLHQWV
%:
&50�0LGGOHZDUH�UHODWHG�/DQGVFDSH
QRQ�5���%DFN�(QG�
��&50�6HUYHU
$V�RQH�ELJORJLFDO�ER[$V�RQH�ELJORJLFDO�ER[
&RPPXQLFDWLRQ6WDWLRQ
n &50�6HUYHU: The CRM Server contains the CRM Middleware, which handles the data exchangewith internal applications and external major components, such as an SAP R/3 Back-End, an SAPBusiness Information Warehouse or non-SAP systems. The CRM Middleware also synchronizes thedatabases of Mobile Clients with the CRM database. The CRM Server is built upon the SAP WebApplication Server, formerly known as the SAP R/3 Basis.
n 0RELOH�&OLHQWV: usually laptops running the 0RELOH�6DOHV�6HUYLFH�$SSOLFDWLRQ, which may includethe Sales Configuration Engine (SCE) and the Sales Pricing Engine (SPE). Mobile Clients typicallyconnect temporarily (e.g., via modem) to the CRM Server for data exchange. They may also bepermanently connected to the Server. The Mobile Clients are connected to the CRM Server via the&RPPXQLFDWLRQ�6WDWLRQ.
n 6$3�5���%DFN�(QG: it is a standard SAP R/3 Back-End with an 5���3OXJ�,Q for data exchange withthe CRM Server.
n %:: the Business Information Warehouse is the SAP data warehouse solution.
n 1RQ�6$3�6\VWHPV: the CRM Middleware can exchange messages with non-SAP ERP systems viastandard interfaces, e.g., XML – SOAP.
n Solid lines: permanent network connections; dotted lines: temporary (e.g., modem) connections.External systems may also be linked with each other as depicted here between an SAP R/3 Back-Endand a BW System or with additional systems not shown.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-11
SAP AG 2001
&50�6HUYHU�$UFKLWHFWXUH
&50�6HUYHU
6$3�:HE�$SSOLFDWLRQ�6HUYHU����&50�'DWDEDVH
&50�0LGGOHZDUH�PDLQ�SDUW�
&50�6HUYHU�$SSOLFDWLRQV•� ������������� �������������
•� ������������������ ��
• � ����������� ������� ������� ��������� ����! "#��� ��� � �����#����!$����• % % %
%XVLQHVV�2EMHFWV•���& ���'�(�
• ) '���� ����� ����� �*�#���• ) '���� �����,+-�&���.�#��.��� ��• % % %
/10/20 3 4�57698;:=<3>4=5�698�:�<
? @BA 3>4=5�698�:=<? @$A 3 4�5�6�8;:=<C�D 5�E&F 475�8GF HJICKD 5=E�F 4�5�8GF H2IL :�<;MNF O�:�PL :=<�M7F O�:�P
Q�R&S 3>4�5�6�8T:�<QUR&S 3�4�5=698T:�<C�Q AWVCKQ AXV YY R�Z H=O�PR�Z H=O9P
3 L[? R R 3>4=5�698�:�<3 L[? R\R 3 4�5�698�:7<
@ Y^] 3>4�5�6�8T:�<@ Y^] 3�4�5=698T:�<
A HJ_=F\E : ? E\F :=I98A HJ_=F\E : ? E F :�I983>4�5=698�:�<3>4=5=698;:7<
n The data exchange between the CRM Middleware and H[WHUQDO�V\VWHPV is performed via DGDSWHUV.The adapters map and convert data between various formats.
n The CRM System supports the handling of &50�EXVLQHVV�REMHFWV, like customers and prospects,activities and opportunities, products and product catalogs in a variety of CRM components likeInternet Sales, Service Interaction Center, Telesales, Campaign Management and various others. TheCRM Server Applications exchange data with the CRM Middleware via the &50�$GDSWHU.
n The 6$3�:HE�$SSOLFDWLRQ�6HUYHU is the successor of the SAP Basis System. The kernel releaseused with CRM 3.0 is 6.10.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-12
SAP AG 2001
6FDODELOLW\
&50'DWDEDVH6HUYHU
0RELOH&OLHQWV
(53�6\VWHP
$SSOLFDWLRQ6HUYHU
&50�6HUYHU&RPPXQLFDWLRQ
6WDWLRQ���
076&20��
Q�
���
(53�6\VWHP
���
076&20��
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-13
SAP AG 2001
&50�0LGGOHZDUH
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-14
SAP AG 2001
l 0LGGOHZDUH�l 6RIWZDUH�WKDW�FRQQHFWV
VHSDUDWH�DSSOLFDWLRQV
,QWURGXFWLRQ�WR�&50�0LGGOHZDUH
l��&50�0LGGOHZDUH�l�$�PHVVDJH�EDVHG�LQWHJUDWLRQ�RI��WKH�FRPSRQHQWV�ZLWKLQ�D�P\6$3VROXWLRQl�$Q�LQWHJUDO�SDUW�RI�WKH�&50�6HUYHUl�,QGHSHQGHQW�IURP�EXVLQHVV�ORJLF
n The term middleware describes software that connects two otherwise separate applications. It is,therefore, distinct from import and export features that may be built into one of the applications.However, it may have import and export facilities.
n The &50�0LGGOHZDUHé Is an SAP Product. It uses proven technologies for the data exchange in an ABAP environment
and offers a future-oriented approach in terms of linking a CRM System to any other ERP system(exchange of XML-based messages).
é Is an integral part of the CRM Solutions. It offers crucial functions for the load of business orcustomizing data to and from a CRM System and links the CRM Server Applications to theMobile Applications. Its task include data conversion, routing and error handling.
é It does not provide business logic. Application consultants or technical consultants working withindividual CRM applications will thus have to handle specific BDoc types, enhance BDoc typesand, if necessary, create the corresponding mapping services.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-15
SAP AG 2001
6RPH�+LVWRU\��,�
l�����&50����
0RELOH�&OLHQWV
$GPLQLVWUDWLRQ6WDWLRQ
2/73�5��6\VWHP
&50�0LGGOHZDUH6HUYHU
1R�%XVLQHVV/RJLF %XVLQHVV�/RJLF
9DOLGDWLRQ
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-16
SAP AG 2001
6RPH�+LVWRU\��,,�
l�����&50����0RELOH�&OLHQWV
&RPPXQLFDWLRQ6WDWLRQ
2/73�5��6\VWHP
&50�6HUYHU�
&50�0LGGOHZDUH&50�2QOLQH
%XVLQHVV�/RJLF/RFDO�9DOLGDWLRQ�
%:
%XVLQHVV�/RJLF9DOLGDWLRQ
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-17
SAP AG 2001
6RPH�+LVWRU\��,,,�
l�����&50����0RELOH�&OLHQWV
&RPPXQLFDWLRQ6WDWLRQ
5��%DFN�(QG
&50�6HUYHU�
&50�0LGGOHZDUH&50�6HUYHU�$SSO�
%:
1RQ�6$3
%XVLQHVV�/RJLF9DOLGDWLRQ
%XVLQHVV�/RJLF*OREDO�9DOLGDWLRQ�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-18
SAP AG 2001
6$3�5���%DFN�(QG
&50�6HUYHU
0RELOH�&OLHQW
&RPPXQLFDWLRQ6WDWLRQ
5��3OXJ�,Q
&50�0LGGOHZDUH�PDLQ�SDUW�
&RPPXQLFDWLRQ6WDWLRQ
�6$3�'&20&RQQHFWRU�
&RQQHFWLRQ+DQGOHU
0RELOH�&OLHQW
&RQQHFWLRQ+DQGOHU
7KH�&50�0LGGOHZDUH
&RPSRQHQWV�RI�WKH�&50�0LGGOHZDUH
n The CRM Middleware consists of the following components:
é On the &50�6HUYHU: the main parts of the &50�0LGGOHZDUH, which handles the BDoc flowwith services such as replication and realignment as well as communication with Mobile Clientsand other linked application components. Part of it is the $GPLQLVWUDWLRQ�&RQVROH for the centralmaintenance of the replication repository with rules for distribution control.
é On the &RPPXQLFDWLRQ�6WDWLRQ: The 6$3�'&20�&RQQHFWRU, which converts the MobileClients‘ DCOM calls into qRFC calls to the CRM Middleware.
é On the 0RELOH�&OLHQWV: The &RQQHFWLRQ�+DQGOHU which represents the entire functionality of theinterface for the data exchange with the CRM Server. The %'RF�/D\HU deals with local dataaccess and client communication with the central communication station via Microsoft’s DCOMprotocol and the &OLHQW�&RQVROH which provides administration functions on laptops, for examplestarting the connection handler for connection control, queue observation, error handling and soon.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-19
SAP AG 2001
7KH�&50�6HUYHUl ,V�EXLOW�RQ�WRS�RI�WKH�6$3�:HE�$SSOLFDWLRQ
6HUYHU` 6FDODELOLW\` 3ODWIRUP�LQGHSHQGHQFH` )XOO�$%$3�GHYHORSPHQW�HQYLURQPHQW` 6RIWZDUH�ORJLVWLFV
l ,W�FRQWDLQV` 7KH�&50�6HUYHU�$SSOLFDWLRQV` 7KH�PDLQ�SDUWV�RI�WKH�&50�0LGGOHZDUH` &50�GDWDEDVH
l &50�0LGGOHZDUH�IXQFWLRQDOLW\` 'DWD�TXHXLQJ�DQG�WUDQVSRUW` 5HSOLFDWLRQ�DQG�UHDOLJQPHQW
&50�6HUYHU
n The &50�6HUYHU is scalable, since it is based on a SAP Web Application Server (formerly: SAPBasis System). The SAP Web Application Server�provides SAP basis technology and the ABAPworkbench as a development environment known to many application developers.
n The CRM Server contains the &50�6HUYHU�$SSOLFDWLRQV and the main parts of the &500LGGOHZDUH. The &50�GDWDEDVH is the central database for the CRM Server Applications.
n The main parts of the CRM Middleware provide the following functionality:
é Data queuing and transport,
é Replication and realignment service, which ensures that Mobile Clients or external systems obtainthe data they require and
é Data exchange and mapping.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-20
SAP AG 2001
7KH�0RELOH�&OLHQWV
l &50�0RELOH�6DOHV�6HUYLFH$SSOLFDWLRQ` 8VHU�,QWHUIDFH�/D\HU��8,�` %XVLQHVV�2EMHFW�/D\HU��%2/�` %'RF�/D\HU��%/�
l 6DOHV�&RQILJXUDWLRQ�(QJLQH��6&(�
l 6DOHV�3ULFLQJ�(QJLQH��63(�l 0DLO�&OLHQW��2IILFH�6XLWH��HWF�
l &OLHQW�0LGGOHZDUH�&RPSRQHQWV` &RQQHFWLRQ�6HUYLFH` 0HVVDJH�7UDQVIHU�6HUYLFH
0RELOH�&OLHQW
n The Mobile Sales / Service Clients contain the &50�0RELOH�$SSOLFDWLRQV�and a ORFDO�GDWDEDVH.
n The CRM Mobile Application consists of three layers: the 8VHU�,QWHUIDFH�/D\HU (UI), the %XVLQHVV2EMHFW�/D\HU (BOL) and the %'RF�/D\HU (BL). The UI layer and the BOL layer may be enhancedusing the 0RELOH�$SSOLFDWLRQ�6WXGLR (MAS). The BDoc Layer is the middleware componentneeded for data synchronization with the CRM Server. The BDoc layer also serves as the interface tothe local database. For more information about the MAS refer to the CR310 course.
n The Mobile Clients may also contain the 6DOHV�&RQILJXUDWLRQ�(QJLQH (SCE) and the 6DOHV�3ULFLQJ(QJLQH (SPE).
n Further middleware components on the mobile client are:
é The &RQQHFWLRQ�6HUYLFH, which handles the actual connection to the CRM Server and calls one ormore transfer services.
é The 0HVVDJH�7UDQVIHU�6HUYLFH handles the data exchange between the client and the CRMServer. Another transfer service can be, for example, a MAPI service (Microsoft MessagingApplication Programming Interface).
n For more information about the mobile client refer to the courses CR200 (Mobile Sales) or CR210(Mobile Service).
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-21
SAP AG 2001
l 3OXJ�LQ�RQ�WKH�6$3�5���%DFN�(QG�DFWV�DV�FRXQWHUSDUW�WR�WKH�5���$GDSWHU
l 'DWD�WUDQVSRUW�LV�SHUIRUPHG�WKURXJK�%$3,�FDOOV�YLD�W5)&�DQG�T5)&
l $XWRPDWLF�DQG�VFKHGXOHG�GDWD�H[FKDQJH
7KH�6$3�5���%DFN�(QG
&50�6HUYHU
6$3�5��%DFN�(QG
5��3OXJ�,Q
5��$GDSWHU
6XSSRUWHG�5���UHOHDVHV����L�����%�����%�����%�&������
n The data exchange via the CRM Middleware requires that an 5���3OXJ�,Q is installed on the SAPR/3 System.
n 6XSSRUWHG�5���UHOHDVHV are 3.1I, 4.0B, 4.5B, 4.6B/C and above.
n The 6$3�5���%DFN�(QG (one or several SAP R/3 Back-Ends) serves as
é provider for customizing and business data (master data, transaction data)
é Receive business data for further execution (currently primarily with mySAP Financials andmySAP SCM for accounting and logistics execution)
n The CRM release 3.0 is a standalone system, that means that R/3 is no longer required for theexecution of CRM-related tasks.
n For more information on the actual data exchange, see unit 'DWD�([FKDQJH�ZLWK�5���%DFN�(QGV�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-22
SAP AG 2001
%:�,QWHJUDWLRQ���,QWHJUDWLRQ�ZLWK�QRQ�5���%DFN�(QGV
1RQ�5��%DFN�(QG
%:
l ,QWHJUDWLRQ�RI�D�%:�V\VWHP�ZLWK�WKH�&50�6HUYHU�YLD�WKH�&50�0LGGOHZDUH�
l ,QWHJUDWLRQ�RI�QRQ�6$3�5���%DFN�(QGV�LQ�WKH&50�ODQGVFDSH��YLD�WKH�&50�0LGGOHZDUH�` 9DULRXV�IRUPDWV��H�J��;0/��,'RFV��$6&,,
n Other systems connected to the CRM System may include:
é The SAP Business Information Warehouse (BW) provides data analyses in the form of SolutionWorkbooks.
é Non-SAP R/3 Back-Ends may serve as data sources and receivers for the CRM System.
é The SAP Advanced Planner and Optimizer (APO) offers additional functionality such as anavailability check of ordered products. It does not use CRM Middleware functionality.
n For further information, see unit 'DWD�([FKDQJH�ZLWK�RWKHU�6\VWHPV.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-23
SAP AG 2001
l 'LVWULEXWLRQ�RI�GDWD�WKURXJKRXW�WKH�V\VWHP�ODQGVFDSH` 3XEOLVKHU�6XEVFULEHU�FRQFHSW` &RQWUROOHG�E\�WKH�UHSOLFDWLRQ�PRGHO` $GPLQLVWHUHG�FHQWUDOO\��YLD�WKH�$GPLQLVWUDWLRQ
&RQVROH�
D
A
B
C
E
6$3�5���%DFN�(QG
QRQ�5���%DFN�(QG
0RELOH�&OLHQWV
'DWD�5HSOLFDWLRQ
n The data distribution is controlled via a Publisher-Subscriber principle. The key idea is to offermessages grouped according to their business content, e.g. all Business Partners from a certaincountry and whose ZIP code lies within a certain range. Such offerings are called 3XEOLFDWLRQV. It ispossible to select specific business object data contained in a Publication by providing specificvalues for those fields, e.g. all Business Partners in Denver (ZIP code between 80200 and 80299) inthe United States (country code = US). Such selections are called 6XEVFULSWLRQV. The datadistribution can then be controlled by assigning receiver systems to subscriptions.
n 7KH�UHSOLFDWLRQ�PRGHO consists of Publications and Replication Objects. Replication Objects arecovered in the course CR540 CRM Middleware for Mobile Scenarios. For more information onPublications see unit Replication Administration.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-24
SAP AG 2001
6$3�5��%DFN�(QG
&50�6HUYHU
0RELOH�&OLHQWV
%:
&RPPXQLFDWLRQ6WDWLRQ
%$3,�
'DWD�([WUDFWV��([FHO�:RUNERRNV
;0/�62$3��,'RFV��RU$6&,,�)LOHV
QRQ�5���%DFN�(QG�
%'RF0HVVDJHV
'DWD�)ORZ�2YHUYLHZ
n %'RF�PHVVDJHV are filled data container that are used for data processing on the CRM Server and forthe data exchange between the CRM Server and the Mobile Clients.
n Data from SAP R/3 Back-Ends and other systems are received via %$3,��;0/�62$3��,'RFV�RU$6&,,�ILOHV. Data in form of BAPI, XML documents or IDocs is mapped to BDoc messages forfurther processing and distribution.
n Several layers may be distinguished in order to technically enable the data transfer between thesystems involved:
é On the network usually the TCP/IP transfer protocol is used
é Remote Function Calls (RFC calls) or the File Transfer Protocol (ftp) provide data
é BDoc messages, IDocs, XML messages or ASCII flat files contain the actual data
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-25
SAP AG 2001
l &50�0LGGOHZDUH�DGPLQLVWUDWLRQa 8VHU�DQG�VLWH�PDQDJHPHQWa 5HSOLFDWLRQ�DGPLQLVWUDWLRQa 'DWD�H[WUDFWVa /RDG�VFKHGXOLQJ
l 0RQLWRULQJa 'DWD�H[FKDQJHa 6\VWHP
$GPLQLVWUDWLRQ��0RQLWRULQJ
n There are several Monitoring tools available on the CRM Server, the Communication Station, theMobile Clients and on other involved systems (e.g. an SAP R/3 Back-End), which may be used toanalyze:
é The load object status
é The status of BDoc messages
é The inbound and outbound queues
é The connections (connection check, tRFC monitoring)
é The system performance (system monitoring and CRM Middleware monitoring)
é Error handling
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 2-26
SAP AG 2001
<RX�DUH�QRZ�DEOH�WR�
0LGGOHZDUH�2YHUYLHZ��6XPPDU\
l 'HVFULEH�WKH�FRPSRQHQWV�RI�WKH�P\6$3�&50V\VWHP�ODQGVFDSH
l ([SODLQ�WKH�FRQQHFWLRQ�DQG�GDWD�H[FKDQJH�RIWKH�YDULRXV�&50�FRPSRQHQWV�ZLWK�WKH�&500LGGOHZDUH
l ([SODLQ�WKH�PDLQ�WDVNV�RI�WKH�&50�0LGGOHZDUH
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-1
SAP AG 2001
&RQFHSWV�RI�WKH�&50�0LGGOHZDUH
l 7KH�6LWH�7\SH�&RQFHSWl 7KH�%'RF�&RQFHSWl 5HSOLFDWLRQ�7\SHVl 3URFHVVLQJ�%'RF�0HVVDJHV�LQ�WKH�&50
6HUYHU
&RQWHQWV�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-2
SAP AG 2001
l 'HVFULEH�WKH�FRQFHSWV�EHKLQG�%'RFVl /RRNXS�%'RF�W\SHV�LQ�WKH�V\VWHPl ([SODLQ�WKH�SURFHVVLQJ�RI�%'RF�PHVVDJHVl ([SODLQ�WKH�GLIIHUHQW�UHSOLFDWLRQ�W\SHV
$W�WKH�FRQFOXVLRQ�RI�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�
&RQFHSWV�RI�WKH�&50�0LGGOHZDUH��8QLW�2EMHFWLYHV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-3
SAP AG 2001
&RXUVH�2YHUYLHZ�'LDJUDP
0LGGOHZDUH�2YHUYLHZ0LGGOHZDUH�2YHUYLHZ
&RQFHSWV�RI�WKH�&50�0LGGOHZDUH&RQFHSWV�RI�WKH�&50�0LGGOHZDUH
5HSOLFDWLRQ�$GPLQLVWUDWLRQ5HSOLFDWLRQ�$GPLQLVWUDWLRQ
0RQLWRULQJ��(UURU�+DQGOLQJ0RQLWRULQJ��(UURU�+DQGOLQJ
,QVWDOODWLRQ��&RQILJXUDWLRQ,QVWDOODWLRQ��&RQILJXUDWLRQ
6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ
'DWD�([FKDQJH�ZLWK�6$3�5��%DFN�(QGV'DWD�([FKDQJH�ZLWK�6$3�5��%DFN�(QGV
'DWD�([FKDQJH�ZLWK�RWKHU6\VWHPV'DWD�([FKDQJH�ZLWK�RWKHU6\VWHPV
)XUWKHU�,QIRUPDWLRQ)XUWKHU�,QIRUPDWLRQ
&RXUVH�:UDS�8S&RXUVH�:UDS�8S
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-4
SAP AG 2001
6LWH�W\SHV%'RFV5HSOLFDWLRQ�W\SHV,QWHUQDO�GDWD�IORZ
0DLQ�&RQFHSWV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-5
SAP AG 2001
6LWH�7\SH�&RQFHSW
5���%DFN�(QG 1RQ�5���%DFN�(QGV�YLD�;0/0RELOH�&OLHQWV
6LWH�% 6LWH�& 6LWH�' 6LWH�(
6DPHVLWH�W\SHV
6LWH�$
6DPHVLWH�W\SH
n Every receiver of messages is represented within the CRM Middleware by a VLWH. There is a one-to-one relationship between sites and physical receivers. Sites are the only addressable unit for theReplication (not users). They are identified by a globally unique identifier (GUID).
n Each site is of a VLWH�W\SH. Sites of the same type use the VDPH�DGDSWHU for exchanging data betweenthe CRM Server and the sites. SAP provides a number of standard site types: CRM, CDB, R/3,Mobile client, External interface for XML, External interface for IDocs. A site representing an SAPR/3 Back-End is of site type R/3.
n Sites are maintained in the Administration Console, which is a transaction on the CRM Server.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-6
SAP AG 2001
,GHD��SURFHVV�WUDQVSRUW�EXVLQHVV�REMHFWV�DV�RQH�XQLW
%XVLQHVV�'RFXPHQWV��%'RFV����0RWLYDWLRQ
&50�6HUYHU0RELOH�&OLHQWV
&50�6HUYHU0RELOH�&OLHQWV
([FKDQJHFXVWRPHU��³6PLWK´
.1$� $'5& .199���
%'RF�³6PLWK´
n The motivation of using %XVLQHVV�'RFXPHQWV��%'RFV� as data container for processing businessobjects and for transporting them as one unit, instead of having to process/transport severalindividual table entries.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-7
SAP AG 2001
&XVWRPHU�%'RF�³6PLWK´��7$6.� �³XSGDWH´)LHOGV��&,7<�� �³1HZ�<RUN´��675((7� �³��%URDGZD\´
:KDW�DUH�%'RFV"
�������
�����
��� ���
&XVWRPHU�%'RF�³6PLWK´�1$0(� ���³6PLWK´1$0(� ���³-RKQ´.8115 ���³����´����
�DOO�ILHOGV�
�DOVR��³LQVHUW´�RU�³GHOHWH´
�FRQWDLQV�RQO\�PRGLILHG�ILHOGV�
'LVWLQFWLRQ�� %'RF�W\SH��VWUXFWXUH�
� %'RF�LQVWDQFH
� %'RF�PHVVDJH
n When talking about %'RFV, the BDoc type, the BDoc instance and the BDoc message have to bedistinguished.
é A %'RF�W\SH or structure has to be defined for each required business object, e.g. Contact Person,Sales Order etc. It contains all the fields that make up the corresponding business object.
é A %'RF�LQVWDQFH is a concrete example of a given BDoc type containing all field values, e.g. thecustomer Smith.
é A %'RF�PHVVDJH (or just %'RF) contains “modified“ fields only. These include modified fields aswell as deleted fields. The difference between a BDoc message and a BDoc instance is that there isonly one BDoc instance for a Business Object, but there can be multiple BDoc messages (withtheir own Ids) for one BDoc instance. However, if an entire BDoc instance is replicated to aMobile Client, a BDoc message, where all fields are filled, is used.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-8
SAP AG 2001
'LIIHUHQW�5HSUHVHQWDWLRQV�IRU�%'RF�0HVVDJHV
%'RF%'RF�PHVVDJHV�FDQ�EH�UHSUHVHQWHG�LQ�YDULRXV�ZD\'HSHQGLQJ�RQ�WKH�HQYLURQPHQW�DQ�RSWLPDO�UHSUHVHQWDWLRQ�LVXVHG��H��J�
� &50�6HUYHU� ,QWHUQDO�WDEOHV� /DSWRSV� $'2�UHFRUG�VHWV� 1RQ�6$3�6\VWHP� ;0/
n The definition of BDoc types does not contain implementation details.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-9
SAP AG 2001
'HFRXSOLQJ�RI�0HVVDJLQJ�DQG�6\QFKURQL]DWLRQ
5���%DFN�(QG
1RQ�5���%DFN�(QG
6$3�%:
&50�6HUYHU
6\QFKURQL]DWLRQ�OD\HU0HVVDJLQJ�OD\HU
:HE�$SSOLFDWLRQ�6HUYHU
7KH�V\QFKURQL]DWLRQ�OD\HU�SURYLGHV�PRUHVRSKLVWLFDWHG�UHSOLFDWLRQ�VHUYLFHV
l 7ZR�LQWHJUDWLRQ�OD\HUV�� 0HVVDJLQJ� 6\QFKURQL]DWLRQ
n Two integration layers decouple messaging and synchronization. The messaging layer usesPHVVDJLQJ�%'RFV for data exchanges with the CRM Server Applications, R/3 Back-Ends andexternal systems. The synchronization layer exchanges data with mobile clients and uses6\QFKURQL]DWLRQ�%'RFV.
n The synchronization of mobile clients is a much more sophisticated integration and thereforedifferent BDoc types are necessary to support the additional services.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-10
SAP AG 2001
6\QFKURQL]DWLRQ�DQG�0HVVDJLQJ�%'RF�&ODVVHV
&50�0HVVDJLQJ�0LGGOHZDUH0HVVDJLQJ�%'RFV
&50�0RELOH�$SSOLFDWLRQ
&50�6\QFKURQL]DWLRQ�0LGGOHZDUH��� ��������� ��� � �"!#� � �%$ � ���'&
0DSSLQJ
5���%DFN�(QG%$3,V
0DSSLQJ
1RQ�5��&50�;0/
0DSSLQJ
• Replication DQGRealignment
• Replication, butQR Realignment
&50�6HUYHU�$SSO�&50�6WUXFWXUHV
�0DSSLQJ�
n Two integration layers decouple messaging and synchronization. The messaging layer usesPHVVDJLQJ�%'RF�W\SHV for data exchanges with the CRM Server Applications, R/3 Back-Ends andexternal systems. The synchronization layer exchanges data with mobile clients and uses6\QFKURQL]DWLRQ�%'RF�W\SHV.
n Synchronization BDoc types are based on data stored in the Consolidated Database (CDB), and areused for synchronizing mobile clients. They allow the full replication and realignment rules based onall data in the CDB to be applied.
n The CRM Middleware can apply „Simple Intelligent Replication“ to Messaging BDoc types. This is„simpler“ than the full replication and realignment because it cannot access data in the message, butonly address data. A messaging BDoc type is like an envelope, with data inside the envelope whichCRM middleware cannot access, and data on the envelope, which the CRM middleware can access.Each application uses different address information, so that for example sales orders can be routedaccording to the sales organization.
n The price for the different BDoc classes is an additional mapping step between messaging andsynchronization BDoc messages.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-11
SAP AG 2001
%'RF�&ODVVHV���2YHUYLHZ
V%'RF
P%'RF
6\QFKURQL]DWLRQ�%'RFV��V%'RFV�� IRUPHU��ZULWH�%'RFV
0HVVDJLQJ�%'RFV��P%'RFV�� IRUPHU��RQOLQH�'RFV
0RELOH�$SSOLFDWLRQ�%'RFV IRUPHU��UHDG�%'RFV
n BDocs can be categorized into three classes:
é 0HVVDJLQJ�%'RFV��P%'RFV��- No exchange with Mobile Clients, not stored in CDB, No mapping between segments and
database tables in the CRM Middleware but in the CRM Server Applications, transport entireinstances (gross data)
é 6\QFKURQL]DWLRQ�%'RFV��V%'RFV��- Only be used for data synchronization with Mobile Clients, mapping between of BDoc
segments and CDB tables, previously called Write BDocs, transport changed fields (deltainformation, net data)
- Can be assigned to messaging BDoc types (n:1 relationship)
é 0RELOH�$SSOLFDWLRQ�%'RFV�- Mobile Application BDocs are used by the mobile sales/service application on the mobile client
to query data from the database.
- Mobile Application BDocs were previously called Read and Query BDocs.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-12
SAP AG 2001
6\QFKURQL]DWLRQ�%'RF�7\SHV��,�
V%'RF6\QFKURQL]DWLRQ�%'RF�7\SHV� )RUPHU��ZULWH�%'RFV� 2QO\�XVHG�IRU�GDWD�V\QFKURQL]DWLRQ�ZLWK�PRELOH�FOLHQWV� 3HUVLVWHQW�LQ�WKH�&RQVROLGDWHG�'DWDEDVH��&'%�� 0DSSLQJ�RI�%'RF�VHJPHQWV�WR�&'%�WDEOHV� 6XSSRUW�UHDOLJQPHQW�DQG�GHSHQGHQFLHV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-13
SAP AG 2001
6\QFKURQL]DWLRQ�%'RF�7\SHV��,,�
%RG\�
+HDGHU�
%XVLQHVV�3DUWQHU�0DVWHU
%XVLQHVV�3DUWQHU�$GGUHVV
V%'RF�VWUXFWXUH
(UURU�VHJPHQW
'DWD�VHJPHQW
'DWD�VHJPHQW���
(�J��&XVWRPHU��2UGHU�����&RQWURO�VHJPHQW
�7\SH��VHQGHU��WLPHVWDPS�����
n A %'RF�W\SH consists of a header and a body.
é The %'RF�KHDGHU consists of one single segment, the so-called control segment.
é The %'RF�ERG\ consists of one or more data segments and of one error segment.
n The FRQWURO�VHJPHQW merely contains header information, whereas the individual GDWD�VHJPHQWVcontain the actual table entries that make up the corresponding business object.
n The HUURU�VHJPHQW can be used to store error information.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-14
SAP AG 2001
6\QFKURQL]DWLRQ�%'RF�7\SHV��,,,�
%XVLQHVV�REMHFW %'RF�W\SH�QDPH&XVWRPHU�DQG�SURVSHFW&RQWDFW�SHUVRQ6DOHV�RUGHU0DWHULDO2SSRUWXQLW\$FWLYLW\&DPSDLJQ3URPRWLRQ6HUYLFH�1RWLILFDWLRQ(PSOR\HH&RQGLWLRQ�REMHFWV&XVWRPL]LQJ�REMHFWV
&$3*(1B2%-B:5,7(&21*(1B2%-B:5,7(6$/(6'2&*(1B2%-(&7B:5,7(35'&7B2%-(&723325781,7<B:5,7($&7,9,7<B2%-(&7&$03$,*1B:5,7(352027,21B:5,7(127,)1B:5,7((03/2<((B:5,7('1/B&21'B '1/B&867B
&RPPRQ�V%'RF�W\SHV�IRU�PRELOH�VFHQDULRV
n This slide lists the most common business objects and the corresponding synchronization BDoc typenames.
n Note that the definition and modification of BDocs require a deep knowledge of the application. TheCRM Middleware does not have the business logic to create or modify BDocs. From this point ofview, it is just a data container to transport and process BDoc messages.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-15
SAP AG 2001
0HVVDJLQJ�%'RF�7\SHV� 8VHG�IRU�PHVVDJLQJ�EHWZHHQ�PDMRU�FRPSRQHQWV��H�J��5����&50�� P%'RF�W\SHV�FRQVLVW�RI�WZR�SDUWV
w &ODVVLFDO�SDUW( +LHUDUFKLFDO�VHJPHQW�VWUXFWXUH( 0RGHOHG�ZLWK�WKH�%'RF�0RGHOHU( *HQHUDWHG�VWUXFWXUH( &RQWDLQV�GDWD�UHOHYDQW�IRU�UHFHLYHU
GHWHUPLQDWLRQ
w ([WHQVLRQ( &RPSOH[�GDWD�W\SH( 0RGHOHG�ZLWK�'',&��VH���( &RQWDLQV�WKH�WUDQVDFWLRQ�GDWD
0HVVDJLQJ�%'RF�7\SHV��,�
P%'RF
) *,+.-"/10"2,) +"-./ 3�465'7 8:9;4=< >?9�@;2#2BA
5'7DC646>FE 4G/"91E H
n A messaging BDoc consists of up to two parts:
é 3DUW�����&ODVVLFDO�3DUW"- This part is mandatory.
- The classical part consists of a BDoc header and segments, which may be arranged in ahierarchical fashion. It is called “ classical part”, because of the similarities to write BDoc typesof the 2.0B/C releases. However, the segments of the classical part are not mapped to databasetables.
- This part is to be modeled with the (CRM Server based) BDoc Modeler.
- Only the classical part is used to determine the receivers of mBDoc messages.
- Since there is no mapping to database tables (i.e. no CDB), this part always needs to be filledcompletely by the application at runtime.
é 3DUW����([WHQVLRQ- This part is optional.
- The complex data type is modeled with the Data Repository Tools (SE11).
- The extension does only exist for messaging BDocs (new with CRM 3.0).
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-16
SAP AG 2001
0HVVDJLQJ�%'RF�7\SHV��FRQWLQXHG�� 7ZR�UHSOLFDWLRQ�W\SHV�DUH�VXSSRUWHG
w 6LPSOH�LQWHOOLJHQW�UHSOLFDWLRQ
w 6LPSOH�EXON�UHSOLFDWLRQ� 1R�ORRNXS�WDEOHV�H[LVW�IRU�UHSOLFDWLRQ�FDOFXODWLRQV� 1R�UHDOLJQPHQW�VXSSRUWHG� 1R�GHSHQGHQFLHV�VXSSRUWHG
0HVVDJLQJ�%'RF�7\SHV��,,�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-17
SAP AG 2001
%'RF�0RGHOHU
6HJPHQW�6WUXFWXUHRI�%'RF�W\SH�%83$B0$,1ZLWK�KHDGHU�VHJPHQW�ILHOGV
([SORULQJ�D�%'RF�7\SH
n The %'RF�0RGHOHU is a tool used for displaying, creating and enhancing BDoc types.
n The existing BDoc types are listed in the BDoc overview (navigation tree) of the BDoc Modeler.Here you can select and expand a BDoc type to display its structure. The structure shows thehierarchy of the data segments.
n Note that the definition and enhancement of BDoc types require knowledge of the application. TheCRM Middleware does QRW have the EXVLQHVV�ORJLF�WR�FUHDWH�RU�HQKDQFH�%'RFV. From this point ofview, it is just a data container to transport and process BDoc messages.
n New BDoc modeling features of the CRM release 3.0:
é Modeling of messaging BDoc types.
é Assignment of one or more synchronization BDocs type to a messaging BDoc type (n:1relationship).
é Assignment of site types (see unit “ Replication Administration”) to synchronization andmessaging BDoc types.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-18
SAP AG 2001
5HSOLFDWLRQ� �0HVVDJH�IRUZDUGLQJ�WR�RQH�RU�PRUH�VLWHV
'LIIHUHQW�7\SHV�RI�5HSOLFDWLRQ
%'RF
" "
"
""
'LIIHUHQW�7\SHV�l Bulk replication
l Intelligent replication
n BDoc messages are replicated to VLWHV (local databases) and not to individual persons.
n Two different replication types can be distinguished: EXON�UHSOLFDWLRQ and LQWHOOLJHQW�UHSOLFDWLRQ.
n Both BDoc classes, message and synchronization BDoc types, can be replicated in both ways.However, every BDoc type can only be replicated via one replication type.
n By default all messaging BDoc types are replicated in bulk, whereas most the synchronization BDoctypes use intelligent replication. This is necessary because of the very demanding data distribution inmobile scenarios. However, the replication types for BDoc types can easily be changed. For furtherinformation about this consult the course &5����±�&50�0LGGOHZDUH�IRU�PRELOH�VFHQDULRV..
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-19
SAP AG 2001
%XON�5HSOLFDWLRQ
A B C D
I��KJLJI�MNJLJI�ONJLJI"P%JLJI�QNJLJI�RNJLJI�SNJLJI�TNJLJI�UNJLJI�TNJLJ
I��KJLJI�MNJLJI�ONJLJI"P%JLJI�QNJLJI�RNJLJI�SNJLJI�TNJLJI�UNJLJI�TNJLJ
IV�WJLJI�MXJLJI�OXJLJI1PYJLJI�QXJLJI�RXJLJI�SXJLJI�TXJLJI�UXJLJI�TXJLJ
I��KJLJI�MNJLJI�ONJLJI"P%JLJI�QNJLJI�RNJLJI�SNJLJI�TNJLJI�UNJLJ
'HILQLWLRQ�RI�WKH�UHVSRQVLEOH
VLWHV
%'RF�PHVVDJHVRI�RQH�W\SH
)LOWHU�RQ�%'RFW\SHV
n %XON�5HSOLFDWLRQé The simplest replication type is the bulk replication.
é Bulk replicated BDoc messages are distributed according to their type, regardless of the messagecontent and their relation to other BDoc messages. In this example, all bulk BDoc messages arereplicated to site A, B and D.
é These objects do not cause content-based realignment (data redistribution).
é Bulk replication is especially suitable for small tables.
é Typical examples for bulk-replicated data are customizing data (the T* tables) or employee data.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-20
SAP AG 2001
,QWHOOLJHQW�5HSOLFDWLRQ
I��KJLJI�MNJLJI�ONJLJI"P%JLJI�QNJLJI�RNJLJI�SNJLJI�TNJLJI�UNJLJI�TNJLJ
I��KJLJI�MNJLJI�ONJLJI"P%JLJI�QNJLJI�RNJLJI�SNJLJI�TNJLJI�UNJLJ
I��KJLJI�MNJLJI�ONJLJI"P%JLJI�UNJLJ
I�TXJLJI�UXJLJ
IV�WJLJI�OXJLJI1PYJLJI�SXJLJI�TXJLJI�UXJLJ
'HILQLWLRQ�RI�WKH�UHSOLFDWLRQ�UXOHV
A B C
D%'RF�PHVVDJHVRI�RQH�W\SH
)LOWHU�RQ�%'RFPHVVDJHV
n ,QWHOOLJHQW�5HSOLFDWLRQé The more sophisticated replication type.
é Replication objects are distributed depending on their contents and their relation to otherreplication objects (in this example, only site A receives the complete set of data; sites B, C and Dobtain a subset only).
é Specific replication rules are necessary.
é Example: synchronization BDoc type “ CAPGEN_OBJECT_WRITE” (customer and prospects).
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-21
SAP AG 2001
,QWHUQDO�'DWD�)ORZ��,�
&50�6HUYHU
,QERXQG3URFHVVLQJ 9DOLGDWLRQ
5���%DFN�(QG 0RELOH�&OLHQWV
2XWERXQG3URFHVVLQJ
5���%DFN�(QG 0RELOH�&OLHQWV
V%'RFZ�[�\.]
P%'RF
P%'RFV%'RFZ1[�\.]
n The internal data flow consists of three main steps:
é Inbound processing,
é Validation and
é Outbound processing.
n ,QERXQG�SURFHVVLQJ: Incoming data of different formats, e.g., BAPI structures from an SAP R/3Back-End, synchronization BDoc messages, XML/SOAP or IDocs, are converted into messagingBDoc messages. Note that an inbound synchronization BDoc can be processed in two ways:
é If it is assigned to a messaging BDoc type, it is mapped to a messaging BDoc message.
é If not assigned to a messaging BDoc type, the synchronization BDoc message is directly passed tooutbound processing (i.e. the Synchronization Flow).
n 9DOLGDWLRQ: the incoming data in form of messaging BDoc messages is validated by the application.In case of a successful validation, the messaging BDoc message is passed to the outboundprocessing. In case the incoming data is not valid, the message is sent back to the sender.
n 2XWERXQG�SURFHVVLQJ: the receiving systems, e.g., SAP R/3 Back-Ends, external systems or MobileClients, are determined. Then the messaging BDoc message is passed to the corresponding outboundadapter, which converts the message into the data formats of the receivers.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-22
SAP AG 2001
,QWHUQDO�'DWD�)ORZ��,,�
&50�6HUYHU$SSOLFDWLRQ
0RELOH�&OLHQW
0RELOH�&OLHQW
^ �`_�_��L��aX�cb��ed��L�.b�f���V���g$ � ���ihkj^ &�al$ � ���
monqp��sr ��_"!tb��
u�v.wGx�y z;{}|q~�y ��� � �su1�'�'� y �G�:x�y v1zD�
��^��}r ��_"!�b`�
monqp��sr ��_"!tb��
��O��sr ��_"!tb��
� �Dx�� ��zG� �Gy zGx�� �q���G�F�6�s| ���o�o�'~�� [�\"�D] �`v �F�
� �Dx�� ��zG�'�Dy zGx�� �q���G�G�=��| �V�o���s~���[�\"�D]L��v.�=�
^ �c���L� bX$��#� r a`b�f^ &�a�$ � ���ihkj�c�V���g$ � �V�
u�� �.� y �=�=x�y v�z=�u��F�'� y {1z;���'zFx
� ��Z�~1�.� 1y �F�
�¡wFx�¢;v1w.zF£s[�£ �'�=x��'�
c��O��sr ��_"!�b`�
Both XML/SOAP and IDocs can be generatedfrom the ABAP complex data type used todefine the external interface
¤�^¥�¤r �`_�!eb�����G�6�;�G{�y z;{�¦'� vD§
~.¨"zD� © �kv"z.y ª6�=xty v�z¤¦'� vD§
~"¨"zD� ©'��v.z.y ª:�Fxty v�z}¦'� vG§
u1�L«oZ`�=�'¬:�k��z;£
u1�L«oZ`�=�'¬:�k��z;£
Example – New customer created in the Mobile Client
é When a sales representative dials in to headquarters to synchronize his/hers Mobile Client, the new customeris sent via a synchronization BDoc to the CRM Middleware. An inbound adapter reads the synchronizationBDoc message of the inbound queue and starts a 6\QFKURQL]DWLRQ�)ORZ. The Synchronization Flow calls a0DSSLQJ�6HUYLFH, which creates a messaging BDoc based on the content of the synchronization BDoc andstarts a 0HVVDJLQJ�)ORZ. The first step in the Flow is to call the &50�$GDSWHU, which validates the dataand creates a new customer by updating the CRM server application tables. The update of the CRM serverapplication object “ customer” causes a software event to be triggered, which in turn causes a new messagingBDoc to be created and passed to the Messaging Flow. The next step in the Flow is to call the 6LPSOH5HSOLFDWLRQ�6HUYLFH, which determines which systems should get the message – this could be one or moreSAP R/3 Back-Ends or non-SAP R/3 Back-Ends. According to which systems should receive the newcustomer information, the corresponding adapters are called:
- for each non-SAP R/3 Back-End determined, the external-system (XML) adapter is called and
- for each SAP R/3 Back-End determined, the 5���$GDSWHU is called.
- If a mobile scenario is activated, the data is relevant for the CDB, and hence for mobile clients: thus the0RELOH�%ULGJH is called. The Mobile Bridge creates a synchronization BDoc based on the content of themessaging BDoc and starts a Synchronization Flow. The first step in the synchronization flow is to callthe CDB service, which writes the data to the CDB. The next step is Replication and Realignment, whichdetermines which Mobile Clients should receive the new customer information. The final step invokesthe outbound adapter for each Mobile Client determined in the previous step and places a synchronizationBDoc containing the customer information in the outbound queue for that client.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-23
SAP AG 2001
)ORZ�&RQWH[WV
w ,QIRUPDOO\�GHVFULEHG�VWHSV�LQ�WKH�JHQHUDO�PHVVDJH�SURFHVVLQJ�PRGHO
w 3UHGHILQHG�DQG�DVVRFLDWHG�ZLWK�OLVWV�RI�VHUYLFHV�WR�EH�FDOOHG�LQ�WKLV�FRQWH[W
,QWHUQDO�'DWD�)ORZ��,,,�
,QERXQG 2XWERXQG9DOLGDWLRQ
9DOLG
n A sequence of services for a BDoc type is called Flow Context. The entire Flow of a BDoc type mayconsist of one or more Flow Contexts.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-24
SAP AG 2001
®�¯�°²±¤³`´`µ1¶�·`¸c¹Lº¡´`»L¼L³`´.¶B¼ ½�¾�¿®�À�ÁÃÂ�·`¸�Ä�¼ Å.·
¯�·�µ�» ¼ Å.´.¶B¼L½ ¾W´`¾�³¯�·�´`»L¼ Æ�¾�Çg·�¾"¶�Âc·�¸eÄ�¼ Å"·
¯�·`µ�»L¼ Å1´.¶B¼ ½ ¾KÂ�·`¸�ÄV¼ Å.·¹e¡¼ Çlµ�» ·Y¯c·`µ�»�¼ Å"´.¶#¼ ½�¾�¿
°�½ È�¼L» ·NÁ�¸É¼ ³�Æ`·
°�´�µ�µ�¼L¾�ÆNÂc·`¸eÄV¼ Å.·
Ê�Ë1¶BÈ�½ Ë�¾�³i±s³�´`µ"¶t·�¸¹B¯VÌeÍ�Î;Ï�°gÐ�´`¾�³lÑqÀ�½�Å'Ò�¿
&50�0LGGOHZDUH�6HUYLFHV
ÊWË"¶BÈ�½�Ë�¾�³X±o³`´�µ"¶t·`¸¹,°�½ È�¼�» ·K®s»�¼ ·`¾"¶tÒ�¿
0HVVDJLQJ)ORZ
6\QFKURQL]DWLRQ)ORZ
Ñ�¾�È�½ ËV¾�³K±¤³`´`µ1¶�·`¸¹B¯VÌeÍ�Î;Ï�°gÐ�´`¾�³lÑqÀ�½�Å'Ò�¿
Ñq¾�È�½ Ë�¾�³K±}³�´`µ"¶�·`¸¹,°�½ È�¼�» ·K®s»�¼ ·`¾"¶tÒ�¿
2YHUYLHZ��)ORZV�DQG�6HUYLFHV
n Some services within the CRM Middleware are:
é The &50�$GDSWHU is called from the Messaging Flow to pass inbound BDoc messages to theCRM Server Application for validation.
é The 5HSOLFDWLRQ�DQG�5HDOLJQPHQW Service determines whether a replication and/or a realignmentis necessary or not. If a realignment has to be performed for a BDoc message, this message iscopied into a separate realignment queue for further processing. If realignment is not required, thereceiving sites for a BDoc message are determined.
é The 0DSSLQJ�6HUYLFH maps synchronization BDoc messages to messaging BDoc messages. Thereverse direction is mapped using the 0RELOH�%ULGJH. The Mobile Bridge takes a messaging BDocmessage and creates one or more synchronization BDoc messages (1:n relationship). It also takesone or more synchronization BDoc messages and produces exactly one messaging BDoc messageof one predefined type (n:1 relationship).
é The &'%�VHUYLFH saves the content of a synchronization BDoc message in the corresponding CDBtables.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-25
SAP AG 2001
,QERXQG3URFHVVLQJ
&50�$GDSWHU��9DOLGDWLRQ�6HUYLFH�
&50'DWDEDVH
$3,
2XWERXQG3URFHVVLQJ
&50�6HUYHU�$SSOLFDWLRQV
7KH�&50�$GDSWHU
n The &50�$GDSWHU receives data from the Messaging Flow and sends this data to the CRM ServerApplications. It receives the data contained in BDoc messages from the inbound processing. In caseof the success validation by the CRM Server Applications, the content of the BDoc (from theextension part) is written into the corresponding tables of the CRM database. If the validation wasnot successful, the BDoc message is send back to the sender.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-26
SAP AG 2001
([DPSOHV��5���$GDSWHU��;,)�$GDSWHU��,QERXQG�$GDSWHU
$GDSWHUV���2YHUYLHZ
%'RF
5���%DFN�(QG
0RELOH�&OLHQW
1RQ�5��%DFN�(QG
&500LGGOHZDUH
$GDSWHUÓ 'DWD�ILHOGUHVWULFWLRQ
Ó 0DSSLQJÓ &RQYHUVLRQÓ .H\FRPSOHWLRQ
Ó 'HIDXOWLQJ
n $GDSWHUV are services that provide connectivity to external systems in order to exchange BDocmessages between the CRM Middleware and the Mobile Clients, R/3 Back-Ends or other non-SAPSystems. The content of the BDoc message may be modified in the following ways.
n Examples:
é 'DWD��ILHOG�UHVWULFWLRQ� Some control segments like the recipient list are not delivered to theMobile Client.
é 0DSSLQJ� The R/3 Adapter fills up the import fields of R/3 BAPI with data coming from a BDoc.
é &RQYHUVLRQ� Data that is imported from external systems via the XIF Adapter via XML or IDocsis converted into BDoc messages before it is passed on to the CRM Server Applications.
é .H\�FRPSOHWLRQ� The different key systems of the external components need to be translated.
é 'HIDXOWLQJ��Fields which need to be filled obtain default values.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-27
SAP AG 2001
3XUSRVH��GDWD�H[FKDQJH�EHWZHHQ�PDMRU�V\VWHPV
&RPPRQ�$GDSWHUV
5���%DFN�(QG0RELOH�&OLHQW 1RQ�5���%DFN�(QG
0RELOH�&OLHQW$GDSWHU
5���$GDSWHU
([W��,QWHUIDFHV�;0/���,'RFV�
$GPLQLVWUDWLRQ&RQVROH
$GDSWHUV
7KH�0LGGOHZDUH�DOORZV�HDV\�LQWHJUDWLRQ�RI�RWKHU�DGDSWHUV$GDSWHUV�UHFHLYH�GDWD�YLD�WKH�UHSOLFDWLRQ�PHFKDQLVP
� New features of the CRM release 3.0:
• The Adapter services are no longer called in the main message flow.
• Several ERP backend systems are supported, with some restrictions.
• Status tracking will be available for each object instance and SAP R/3 site.
• Filtering in SAP R/3 is possible as of CRM Plug-In version 2001.1.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-28
SAP AG 2001
1RZ�\RX�DUH�DEOH�WR�
l 'HVFULEH�WKH�FRQFHSWV�EHKLQG�%'RFVl /RRNXS�%'RF�W\SHV�LQ�WKH�V\VWHPl ([SODLQ�WKH�SURFHVVLQJ�RI�%'RF�PHVVDJHVl ([SODLQ�WKH�GLIIHUHQW�UHSOLFDWLRQ�W\SHV
&RQFHSWV�RI�WKH�&50�0LGGOHZDUH��6XPPDU\
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-29
�([HUFLVHV
8QLW� &RQFHSWV�RI�WKH�&50�0LGGOHZDUH7RSLF� %'RF�7\SHV�DQG�)ORZ�&RQWH[WV
At the conclusion of this exercise, you will be able to:
• Examine the structure of a BDoc type
• Determine the Flow Contexts for a BDoc type
BDoc types are the main data structure within the CRM Middleware fordata processing and data transfer. The internal structure of BDoc typescan be viewed using the BDoc Modeler.
BDoc messages are processed within the CRM Middleware by severalservices. The services that are called for a BDoc type can be looked upfor each Flow Context.
1-1 Examine the structure of a BDoc type.
1-1-1 Start the BDoc Modeler.
1-1-2 Examine the structure of the messaging BDoc type and the synchronizationBDoc type for the business partners.
1-2 Determine some Flow Contexts for BDoc types.
1-2-1 Which services are called in the Messaging Flow for business partnersa) during the inbound processing?
1. _______________________
b) during the outbound processing (normal delta processing)?
1. _______________________2. _______________________3. _______________________
1-2-2 Which services are called in the Synchronization Flow for businesspartners during the outbound processing (normal delta processing)?
1. _______________________2. _______________________3. _______________________
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-30
�6ROXWLRQV
8QLW� &RQFHSWV�RI�WKH�&50�0LGGOHZDUH7RSLF� %'RF�7\SHV�DQG�)ORZ�&RQWH[WV
1-1 Examine the structure of a BDoc type.
1-1-1 Start the BDoc Modeler via the menu:
0LGGOHZDUH�→�'HYHORSPHQW�→�%'RF�0RGHOHU��WUDQVDFWLRQ�6%'0��
1-2-2 Examine the structure of the messaging BDoc type and the synchronizationBDoc type for the business partners.
When you use the transaction for the first time, a pop-up asks for a displayselection. For the exercise, mark %'RF�&ODVVHV ³0HVVDJLQJ´ and³6\QFKURQL]DWLRQ��:ULWH�´� Later on, you may change your selection byusing the ILOWHU button or “ Ctrl + F6”.
The messaging BDoc type used for business partners is called BUPA-MAIN.It is marked as a messaging BDoc type and has the site types R/3, IDoc andXML assigned to it (see units 'DWD�([FKDQJH�ZLWK�6$3�5���6\VWHPV�and'DWD�([FKDQJH�ZLWK�QRQ�6$3�5���6\VWHPV).The header CRMW_BUPA_MAIN contains among other things the businesspartner number and the business partner GUID. The extension is labelledRelated Data Type, for BUPA_MAIN it is called BUS_EI_MAIN. It may beviewed using transaction SE11 (Data Dictionary).
The synchronization BDoc type for business partner is calledCAPGEN_OBJ_WRITE. The slide Synchronization BDoc Types (V) liststhe most common synchronization BDoc types.
1-2 Determine some Flow Contexts for a BDoc type.
1-2-1 Which services are called in the messaging Flow for business partners?
The transaction to display Flow Contexts may be found in the menu under0LGGOHZDUH�→�0HVVDJH�)ORZ�→�'HILQH�DQG�&KHFN�)ORZ�'HILQLWLRQV�WUDQVDFWLRQ�602�)'��Enter the BDoc type BUPA_MAIN and start the function ([HFXWH. Thesystem will now display the available messaging Flow Contexts for businesspartner.
The messaging Flow Context 9DOLGDWH�(MI0) only contains the validationservice: CRM_BUPA_MAIN_VAL.
The Flow Contexts for the distribution of change messages are the1RWLILFDWLRQ (MO1) and 1RWLILFDWLRQ�0XOWLSOH (MO2) contexts. They containthe following services:
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 3-31
1. SMOH_REPLICATION_WRAPPER_MSG2. SMW3_OUTBOUNDADP_CALLADAPTERS3. BP_MAIN_CRM_TO_CDB_DELTA (the mobile bridge, optinal).
The Replication Wrapper calls the Replication service. The function module SMW3_ OUTBOUNDADP_CALLADAPTERS calls the outbound adapter.
1-2-2 Which services are called in the synchronization Flow for business partners?
Restart the transaction0LGGOHZDUH�→�0HVVDJH�)ORZ�→�'HILQH�DQG�&KHFN�)ORZ�'HILQLWLRQV�WUDQVDFWLRQ�602�)'��Enter the BDoc type CAPGEN_OBJ_WRITE and start the function ([HFXWH.The system will now display the available synchronization Flow Contexts forbusiness partner.
The synchronization Flow Context ,QERXQG (SI1) does not show the mappingservice. This service can be found in the table SMW3BDOCIF.
The Flow Context for the distribution of change messages is the 1RWLILFDWLRQ(SO1) context. It contains the following services:
1. /1CRMG0/CAPGEN_OBJ_WRITE_CDB 2. SMOH_REPLICATION_WRAPPER_SYNC 3. SMW3_OUTBOUNDADP_CALLADAPTERS
The CDB Service updates the CDB and performs a net field calculation. The Replication Wrapper calls the Replication & Realignment service. The function module SMW3_ OUTBOUNDADP_CALLADAPTERS calls the outbound adapter for mobile clients.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-1
SAP AG 2001
5HSOLFDWLRQ�$GPLQLVWUDWLRQ
l 7KH�$GPLQLVWUDWLRQ�&RQVROHl 6LWH�DQG�6LWH�7\SHVl $GPLQLVWUDWLRQ�RI�6LWHV�DQG�6XEVFULSWLRQV
&RQWHQWV�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-2
SAP AG 2001
l /LVW�WKH�WDVNV�SHUIRUPHG�XVLQJ�WKH$GPLQLVWUDWLRQ�&RQVROH
l 'HVFULEH�WKH�VLWH�W\SH�FRQFHSWl 0DLQWDLQ�VLWHV�DQG�VXEVFULSWLRQV
$W�WKH�FRQFOXVLRQ�RI�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�
5HSOLFDWLRQ�$GPLQLVWUDWLRQ��8QLW�2EMHFWLYHV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-3
SAP AG 2001
&RXUVH�2YHUYLHZ�'LDJUDP
0LGGOHZDUH�2YHUYLHZ0LGGOHZDUH�2YHUYLHZ
&RQFHSWV�RI�WKH�&50�0LGGOHZDUH&RQFHSWV�RI�WKH�&50�0LGGOHZDUH
5HSOLFDWLRQ�$GPLQLVWUDWLRQ5HSOLFDWLRQ�$GPLQLVWUDWLRQ
0RQLWRULQJ��(UURU�+DQGOLQJ0RQLWRULQJ��(UURU�+DQGOLQJ
,QVWDOODWLRQ��&RQILJXUDWLRQ,QVWDOODWLRQ��&RQILJXUDWLRQ
6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ
'DWD�([FKDQJH�ZLWK�6$3�5��%DFN�(QGV'DWD�([FKDQJH�ZLWK�6$3�5��%DFN�(QGV
'DWD�([FKDQJH�ZLWK�RWKHU6\VWHPV'DWD�([FKDQJH�ZLWK�RWKHU6\VWHPV
)XUWKHU�,QIRUPDWLRQ)XUWKHU�,QIRUPDWLRQ
&RXUVH�:UDS�8S&RXUVH�:UDS�8S
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-4
SAP AG 2001
D
A
B
C
E
6LWH�'�5���%DFN�(QG�
6LWH�(���QRQ�5��%DFN�(QG�
���������� ��� ������ ���� �������� �
6LWHV�$�&�0RELOH�&OLHQWV�
l 6WDU�OLNH�UHSOLFDWLRQl 1R�KLHUDUFKLFDO�GLVWULEXWLRQ�QHWZRUNVl 5HSOLFDWLRQ�WR�VLWHV��QRW�SHUVRQV
5HSOLFDWLRQ�$GPLQLVWUDWLRQ
n The replication takes place in a star-like fashion from the CRM Server to the Mobile Clients (sites A,B and C), SAP R/3 Back-Ends (site D) or non-SAP R/3 Back-Ends).
n There is no KLHUDUFK\ in this system. That means that data is only stored in the CRM database and inthe local databases of the clients; there is no “medium level” storage which regulates distribution.
n Data is replicated to VLWHV (local databases) and not to individual persons.
n The rules how data is distributed is defined by a UHSOLFDWLRQ�PRGHO. The model is created andadministered in the $GPLQLVWUDWLRQ�&RQVROH.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-5
SAP AG 2002
6LWH�7\SH�&RQFHSW
5���%DFN�(QG 1RQ�5���%DFN�(QG�YLD�;0/0RELOH�&OLHQWV
6LWH�% 6LWH�& 6LWH�' 6LWH�(
6DPHVLWH�W\SHV
6LWH�$
6DPHVLWH�W\SH
n Every receiver of messages is represented within the CRM Middleware by a VLWH. There is a one-to-one relationship between sites and physical receivers. Sites are the only addressable unit for theReplication (not users). They are identified by a globally unique identifier (GUID).
n Each site is of a VLWH�W\SH. Sites of the same type use the VDPH�DGDSWHU for exchanging data betweenthe CRM Server and the sites. SAP provides a number of standard site types: CRM, CDB, R/3,Mobile client, External interface for XML, External interface for IDocs. A site representing an SAPR/3 Back-End is of site type R/3.
n Sites are maintained in the Administration Console, which is a transaction on the CRM Server.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-6
SAP AG 2002
³3XEOLVKHU�6XEVFULEHU´�&RQFHSW��,�
l 3XEOLFDWLRQV��GHVLJQ�WLPH�� Grouping BDocs to be distributed� Containing only one intelligent BDoc type (and all dependent ones)
or� Containing multiple bulk BDoc types
l 6XEVFULSWLRQV��UXQ�WLPH�� Specification of values for the criteria fields of publications� Sites can be assigned to subscription
l 'HILQLWLRQ�RI�3XEOLFDWLRQV�6XEVFULSWLRQV�LQ�WKH�$GPLQLVWUDWLRQ&RQVROH
n Depending on the replication type, BDoc types may be grouped for the replication. The messagingBDoc types mostly use the EXON�UHSOLFDWLRQ. Here each BDoc type corresponds to one publicationand one subscription.
n 3XEOLFDWLRQV group BDocs for data replication.
é Grouping of BDoc types to be distributed by UHSOLFDWLRQ�W\SHV (for example bulk, intelligent).Contain only one intelligent BDoc type (and all dependent ones) or multiple bulk BDoc types.
é Intelligent replication: Specification of FULWHULD�ILHOGV� which may be used to select the businessobjects of a particular type (for example all customers in a particular postcode area).
é Intelligent replication: Definition of GHSHQGHQFLHV (relationships) between differentsynchronization BDoc types (for example, if certain customers are replicated to one Mobile Client,then the corresponding contract persons are also replicated to the same Mobile Client).
n 6XEVFULSWLRQV correspond to publications.
é The creation of subscriptions for synchronization BDoc types triggers the actual distribution ofdata to the sites.
é Determination of values for criteria fields (for example, all customers in postcode area 6)
é Pre-defined publications are delivered by SAP as industry templates. Subscriptions are veryindividual and are maintained by customers.
é Sites are assigned to subscriptions (receiver determination).
n Publications, subscriptions and the assignment of sites to subscriptions are defined and maintainedwithin the $GPLQLVWUDWLRQ�&RQVROH.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-7
SAP AG 2001
3XEOLFDWLRQV�
6XEVFULSWLRQV
([DPSOH��%XVLQHVV�3DUWQHU
����� �"!$#&%('�)* '+!,�.-/%102�3�54/6'7% 8�9 !�:<;3�(=�>�!.0�?
@BA A =��/�$9 :1%2� �*.C '���:1%,'7�&;7#5=�>�!.0D?
³3XEOLVKHU�6XEVFULEHU´�&RQFHSW��,,�
$VVLJQPHQW�RI�VLWHVWR�VXEVFULSWLRQV
@EA A =�/�.9 :1%�� � *(C '3�F:�%.' �GIHKJ,L�M/NPOPQPL�GPR
�S�/� �+!.#T%1'+�<)* '+!1��-/% 02�7�54/6U'3%18�9 !�:
GIHBQPN�V
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-8
SAP AG 2001
L :$4,!��.: WX � %$��%
H ����4,!��.: WX � %$�/%
L :$4,!.�.:1WX �/%.�/%
L :(4,!��.:/WX ��%.�/%
H �2�F41!��.:1WX �/%$� %
H �2�F4,!.�.:1WX �/%$� %
�������* �.4 A 9 0 C �Y9 !�:
G !.Z,[* �.4 A 9 0 C �Y9 !�:
G !$Z \* �.4 A 9 0 C �Y9 !�:
G !$Z(:
L :(41!��.:1WX � %$�/%
H �/�Y4,!��.:1WX � %(�/%
L :$4,!��.: WX � %$� %
H �/�Y4,!��.:/WX � %$�/%
L :$4,!��.: WX ��%$� %
H �/�Y4,!��.: WX � %$� %%'RF�
%'RF�
%'RF %'RF� �
%'RF�%'RF�
%'RF�%'RF�
3XEOLVKHU�6XEVFULEHU�([DPSOH��,,�
&500LGGOHZDUH
0RELOH�&OLHQW 0RELOH�&OLHQW 0RELOH�&OLHQW
] �$4 � 0('^9 -2�F9 !�:G !(Z \
] �(4 � 0('^9 -���9 !�:G !$Z,[
] �(4 � 0('^9 -/�Y9 !.:G !(Z(:
n ([DPSOH of a data flow:
é A BDoc message is generated on a client and appended to its outbound queue (1).
é After uploading the BDoc message to the CRM Server with the &RQQ7UDQV program, the BDocmessage is appended to the inbound queue for the client (2).
é Depending on the type of the BDoc message, the message is assigned to one or more publications(here: No. 1 and No. n) (3).
é The BDoc message is replicated to the sites that are assigned to the subscriptions that match thedata of the BDoc message (4).
é After the clients synchronized their queues with the CRM Server, the BDoc messages areappended to the corresponding inbound queue of the clients for further processing (5).
n Note, that this processing is a very simplistic view of the processing, which should onlydemonstrated the relationship between subscriptions and publications.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-9
SAP AG 2001
$GPLQLVWUDWLRQ�&RQVROH
l 6LWH�DQG�0RELOH�&OLHQW�XVHU�HPSOR\HHV��PDQDJHPHQW
l 5HSOLFDWLRQ�PRGHOLQJl &XVWRPL]LQJ
� 5HSOLFDWLRQ�REMHFWV� 3XEOLFDWLRQV
l $GPLQLVWUDWLRQ� 6XEVFULSWLRQV� $VVLJQLQJ�VLWHV�WR�VXEVFULSWLRQV
l 0RELOH�6FHQDULRV�l 3HUIRUPLQJ�GDWD�H[WUDFWV�l 0DLQWHQDQFH�RI�RUJDQL]DWLRQDO�KLHUDUFK\�RI�VLWHV
7KH�$GPLQLVWUDWLRQ�&RQVROH
n The main tasks of the $GPLQLVWUDWLRQ�&RQVROH are:
é Setting up and maintaining the UHSOLFDWLRQ, i.e. maintaining replication objects, publications undsubscriptions.
é Management of mobile employee (users) and their passwords.
é Definition of sites, the logical representation of data receivers within the CRM Middleware.
é For sites of site type Mobile Client only: assignment of employees to sites.
é Definition and administration of organizational structures.
n Via the extract functionality, it is possible to extract the complete or partial data for a Mobile Client.This could be important, for example, in the case, where a Mobile Client needs to be replaced.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-10
SAP AG 2001
0HQX��0LGGOHZDUH��!�$GPLQLVWUDWLRQ��!�$GPLQLVWUDWLRQ�&RQVROH
6WDUWLQJ�WKH�$GPLQLVWUDWLRQ�&RQVROH
6HOHFW�REMHFWW\SH
0HQX�EDU
$SSOLFDWLRQWRROEDU
1DYLJDWLRQDUHD
,QIRUPDWLRQDUHD
n The Administration Console may be accessed via the menu:0LGGOHZDUH�→�$GPLQLVWUDWLRQ�→�$GPLQLVWUDWLRQ�&RQVROH (or via the transaction 602($&).
n 2EMHFW�W\SHV are used for the replication modeling:
é Sites
é Replication objects
é Publications
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-11
SAP AG 2001
9LHZLQJ�6LWH�7\SHV
6WDQGDUG�6$3�&50�6LWH�7\SHVn�5���%DFN�(QGn�0RELOH�&OLHQWn�([WHUQDO�,QWHUIDFH�IRU�,'2&Vn�([WHUQDO�,QWHUIDFH�IRU�;0/
6SHFLDO�VLWH�W\SHVn�&50n�&'%��&RQVROLGDWHG�'DWDEDVH�IRU����0RELOH�&OLHQWV�
0DLQWDLQHG�YLD�WKH�$GPLQLVWUDWLRQ&RQVROH
n The different adapters in Adapter framework are associated with predefined site types:
é R/3 Back-End: R/3 adapter
é Mobile Client: Mobile bridge
é External Interface for IDOCs: IDOC adapter
é External Interface for XML: XIF adapter
n Site types CRM and CDB
é In CRM 3.0 only one instance allowed
é Important for starting initial loads, but no subscriptions possible
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-12
SAP AG 2001
9LHZLQJ�6LWHV
2EMHFW,QIRUPDWLRQ
1DYLJDWLRQDUHD
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-13
SAP AG 2001
2Q�WKH�&50�6HUYHU� &UHDWH�DQ�5)&�GHVWLQDWLRQ�IRU�HDFK
6$3�5���%DFN�(QG� &UHDWH�D�VLWH�RI�W\SH�5��
�PDLQWDLQ�WKH�VLWH�DWWULEXWHV�
6\VWHP�&RQILJXUDWLRQ�IRU�5���6LWHV
2Q�WKH�5���%DFN�(QG� &UHDWH�5)&�GHVWLQDWLRQ�IRU�WKH
&50�6HUYHU� &UHDWH�DQ�HQWU\�LQ�WKH�WDEOH
&505)&3$5
n The screen shots show the following examples:
é CRM Server:
- Administration Console: R/3 Site attributes for the system X03.
é R/3 Back-End:
- CRM Server can be reached via the RFC destination X04. For more information about thisscreen shot refer to the unit 'DWD�([FKDQJH�ZLWK�6$3�5���%DFN�(QGV.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-14
SAP AG 2001
&UHDWLQJ�6LWHV
&UHDWH
6LWH'HWDLOV
6DYH
$VVLJQ�WKH�VLWHWR�VXEVFULSWLRQV
�
�
�
�
�
n Four steps are required to create a new VLWH.
é Press the FUHDWH button.
é Providing the site details, such as
- a site name and a site description,
- select the site type, such as Mobile Client, R/3 Back-End, External Interface for XML/IDocs.
- Specify the site attributes depending on the site type, e.g. an RFC destination for R/3 Back-Ends.
é Assign the site to one or more subscriptions.
é Finish the creation process by pressing the VDYH button.
n There are two SAP roles that specify the authorization to create or maintain objects within theAdministration Console:
é role SAP_CRM_MWAC_ADMINISTRATOR for employees, sites, organizational units andsubscriptions and
é role SAP_CRM_MWAC_CUSTOMIZER for replication objects and publications
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-15
SAP AG 2001
l 6LWHV�DUH�DGPLQLVWHUHG�YLD�WKH�$GPLQLVWUDWLRQ�&RQVROHl &UHDWLRQ�RI�DQ�5���VLWH�
� &KRRVH�W\SH�5��
$GPLQLVWUDWLRQ�RI�5���6LWHV��,�
0XVW�EH�HQWHUHGPDQXDOO\
$XWRPDWLFDOO\GHWHUPLQHG
$XWRPDWLFDOO\GHWHUPLQHG
� 5���DWWULEXWHV�IRU�5���VLWHV5)&���'HVWLQDWLRQ ORJLFDO�V\VWHP 5���UHOHDVH
n R/3 Sites are determined by an RFC destination, a logical system and the release of the R/3 Back-End.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-16
SAP AG 2002
l 5HPDUNV� $GPLQLVWUDWLRQ�&RQVROH�VXSSRUWV
w �&UHDWLRQ�w �&KDQJH�DQGw �'HOHWLRQ�RI�5���VLWHV
� ([FHSWLRQ��5���6LWHV�ZLWK�VXEVFULSWLRQV�FDQ�QRW�EH�GHOHWHG�WKH�VXEVFULSWLRQV�PXVW�EH�UHPRYHG�ILUVW�
� 5���VLWHV�DUH�DVVRFLDWHG�WR�PHVVDJLQJ�%'RFV
$GPLQLVWUDWLRQ�RI�5���6LWHV��,,�
��������&50�6HUYHU
5���5���
P%'RF
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-17
SAP AG 2001
2QH�RU�PRUH�5���6LWHV�FDQ�FRQQHFWHG�EH�YLD�WKH�UHSOLFDWLRQ�VHUYLFH� 2QO\�P%'RFV�DUH�UHSOLFDWHG�WR�5���6LWHV� 2QO\�P%'RFV�FDQ�EH�VXEVFULEHG�IRU�5���6LWHV
� %$3,�VWUXFWXUHV�DUH�XVHG�IRU�WKH�GDWD�H[FKDQJH�EHWZHHQ�&50�VHUYHUDQG�5���%DFN�(QG
5HSOLFDWLRQ�WR�5���6LWHV
��������&50�6HUYHU
5���5���
�5���%DFN�(QG
�5���%DFN�(QG
P%'RF
%$3,6WUXFWXUHV
%$3,6WUXFWXUHV
n Note that it is technically possible to connect one CRM Server to multiple R/3 Back-Ends. However,there are a lot of restrictions for such scenarios. Please consult the Component Integration Web pagefor further information (SAPNet alias: FUP�FL).
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-18
SAP AG 2001
9LHZLQJ�3XEOLFDWLRQV
3XEOLFDWLRQQDPH�DQG�W\SH'HWDLOHG
,QIRUPDWLRQ
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-19
SAP AG 2001
9LHZLQJ�6XEVFULSWLRQV
6XEVFULSWLRQQDPH�DQG�W\SH
'HWDLOHG,QIRUPDWLRQ
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-20
SAP AG 2001
(QWHU�WKH�VXEVFULSWLRQ�QDPHDQG�VHOHFW�D�SXEOLFDWLRQ
(QWHU�FULWHULD�YDOXHV��LI�\RX�KDYHFKRVHQ�D�SXEOLFDWLRQ�RI�UHSOLFDWLRQ�W\SH�LQWHOOLJHQW
$VVLJQ�6LWHV��RSWLRQDO�
)LQLVK��DXWRPDWLF�DFWLYDWLRQ�
&UHDWLQJ�6XEVFULSWLRQV
n For the FUHDWLRQ�RI�D�VXEVFULSWLRQ (assignment of publications to a site using certain criteria) youhave to enter:
é A publication
é In the case of an intelligent or simple intelligent publication the FULWHULD�YDOXHV (primarily used ina mobile scenario) for your subscription.
- Via criteria values you can decide whether a site ID should obtain the whole set of datareferring to a replication object or only a subset of this data. It is possible to define a valuerange for each field in this object. This reduces the amount of data that is sent to a MobileClient.
- There is no limit to the number of criteria fields you can define for the replication of one object.
- Example for criteria fields:The BDoc type Customer contains the field Sales Area, which is defined to be a criteria field.Based on the content (criteria values) of this field, the Customers are made available to thevarious sites.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-21
SAP AG 2001
/HYHO�,
/HYHO�,,
/HYHO�;
���
2UJDQL]DWLRQDO�6WUXFWXUHV
n Using an organizational structure you create hierarchical subscriptions by using the LQGLUHFWLRQIXQFWLRQ, e.g. a regional manager receives all data his or her sales representatives receive (danger ofinformation overflow). This function is rather relevant for a PRELOH�VFHQDULR.These organizationalstructures are not integrated into the CRM organizational model. They are maintained separately inthe Administration Console.
n Features are:
é It is possible to define up to ten hierarchical levels.
é The definition of the organization may be used to build hierarchies within subscriptions.
é Sites, subscriptions and users can be assigned on each level of an organization.
n The use of the indirection function is controlled through a special authorization object(CRM_MW_AC with ACTVT „78“).
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-22
SAP AG 2001
<RX�DUH�QRZ�DEOH�WR�
5HSOLFDWLRQ�$GPLQLVWUDWLRQ��6XPPDU\
l /LVW�WKH�WDVNV�SHUIRUPHG�XVLQJ�WKH$GPLQLVWUDWLRQ�&RQVROH
l 'HVFULEH�WKH�VLWH�W\SH�FRQFHSWl 0DLQWDLQ�VLWHV�DQG�VXEVFULSWLRQV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-23
([HUFLVHV
8QLW� 5HSOLFDWLRQ�$GPLQLVWUDWLRQ7RSLF� ,QWURGXFWLRQ�WR�WKH�$GPLQLVWUDWLRQ�&RQVROH
At the conclusion of this exercise, you will be able to:
• Use the Administration Console to view CRM Middlewareadministrative data
• Create Sites and Subscriptions
• Assign Sites to Subscriptions
As a CRM Middleware administrator/consultant/responsible, you are in charge ofadministering the data replication from the CRM Middleware to external systems. Yourrole is the definition of Sites and Subscriptions as well, as assigning Sites toSubscription.
This exercise deals with the basic CRM Middleware administration tasks, i.e. creatingSites and Subscriptions and assigning Sites to Subscriptions. Your tool to perform thesetasks is the Administration Console.
1-1 Familiarization with the Administration Console
1-1-1 Start the Administration Console.
1-1-2 View all site details:
Which Site types are displayed?_________________________________
What other Site types are available?
_________________________________
What is the difference between a Site of type R/3 and a Site of type MobileClient?
__________________________________
View the details of the R/3 Site. What are the RFC destination and thelogical system of that Site?
_________________________________________________________
1-1-3 Examine the existing Publications and Subscriptions. View all Subscriptionsassigned to the R/3 Site.
Where do you find all Subscriptions for a Publication? Are there criteriavalues assigned to the Subscriptions?
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-24
1-2 Creating a new Site
1-2-1 Create a new Site of type Mobile Client using the following values:
6LWH�1DPH ³&5������´����� �JURXS�QR��6LWH�'HVFULSWLRQ ��\RXU�FKRLFH�!6LWH�7\SH 0RELOH�&OLHQW
Choose the Site Attributes, so that the Mobile client for the new Site willuse a dial-up connection, i.e. the Client is NOT permanently connected tothe Communication Station. Furthermore, the new Mobile Client willexchange Mobile Sales/Service data as well as email Data with the CRMServer.
1-3 Creating a new Subscription
1-3-1 Create a new Subscription for your new Mobile Client, which contain all thecustomers and prospects that live in Denver, United States and assign yourMobile Client to this Subscription. You may use the following values:
6XEVFULSWLRQ�1DPH ³&$3��86��'HQYHU��*URXS����´�ZKHUH���� �JURXS�QR�
3XEOLFDWLRQ &XVWRPHU��3URVSHFWV��E\&RXQWU\���=,3�&RGH�
$'5&')/7 ³6´�YLD�)��+HOS&28175< ³86´3267B&2'(� ³�����´�±�³�����´�
ZKHUH���� �JURXS�QR�1-4 Monitor the Outbound Queue
1-4-1 As soon as a Site is assigned to a Mobile Client, the data for thatSubscription is appended to the corresponding Outbound Queues in theCRM Middleware. View the items in the Outbound Queues.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-25
6ROXWLRQV
8QLW� 5HSOLFDWLRQ�$GPLQLVWUDWLRQ7RSLF� ,QWURGXFWLRQ�WR�WKH�$GPLQLVWUDWLRQ�&RQVROH
1-1 Familiarization with the Administration Console
1-1-1 Start the Administration Console.
The Administration Console is called via the menu path:
0LGGOHZDUH�→�$GPLQLVWUDWLRQ�→�$GPLQLVWUDWLRQ�&RQVROH��WUDQVDFWLRQ602($&��
1-1-2 View all site details:
Which Sites types are displayed?
The object type Sites contains all sites that exist in the CRM Middleware.Enter the object type 6LWHV and press the button 'LVSOD\�REMHFWV. Thefollowing Site types are displayed:
CDB, CRM, Mobile Client, R/3. The site types CDB and CRM are pre-configured by SAP (including their RFC destination 1RQH).
What other Sites types are available?
The other existing Site types are: External Interface for IDocs and ExternalInterface for XML. Other site types such as My Site Type or SAP Examplecannot be used.
What is the difference between a Site of type R/3 and a Site type MobileClient?
The Site attributes differ. Furthermore the site-specific outbound queues ofthe R/3 sites are not displayed.
View the details of the R/3 site. What are the RFC destination and thelogical system of that site?
Click on the button 6LWH�$WWULEXWHV in order to view the RFC destination ofthe site and its logical system.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 4-26
1-1-3 Examine the existing Publications and Subscriptions. View all Subscriptionsassigned to the R/3 Site.
Where do you find all Subscriptions for a Publication?
All Subscriptions of a Site are listed in the menu
6LWH�→��VLWHBW\SH!��!��VLWHBQDPH!�→�6XEVFULSWLRQV�The Subscriptions for a particular Publication may be viewed by selectingthe object type
3XEOLFDWLRQV�→��SXEOLFDWLRQBQDPH!�Are there criteria values assigned to the Subscriptions?
Whether criteria values can be used for the replications depends on thereplication type of the relevant Publication. Publications of type VLPSOH�EXON�PVJ� for messaging BDocs and Publications of type EXON forsynchronization BDocs cannot be filtered using criteria values.
1-2 Creating a new Site
1-2-1 To create a new site choose object type 6LWHV and press &UHDWH�2EMHFW-button(F6 button).Enter the name, a description and choose the site-type 0RELOH�&OLHQW. For6LWH�$WWULEXWHV select 'HIDXOW�&RQQHFWLRQ�*URXS and 'HIDXOW�7UDQVIHU*URXS. The 'HIDXOW�&RQQHFWLRQ�*URXS determines that the ConnTransprogram on the Mobile Client establishes a new connection to theCommunication Station via dial-up networking. This option may also beused for connections within the local network. However, if Mobile Clientsare always connected to a local network, the option $OUHDG\�&RQQHFWHG maybe chosen.The entry 'HIDXOW�7UDQVIHU�*URXS has the effect that the ConnTransprogram exchanges Mobile Sales / Service data as well as email data withthe CRM Server.As long as the Site ID of the new Site has not been exchanged with theMobile Client, the site is marked as 1RW�DVVLJQHG�WR�FOLHQW.
1-3 Creating a new Subscription
1-3-1 Choose object type 6XEVFULSWLRQV�and press &UHDWH�2EMHFW-button (F6button). Enter as Description &$3��86��'HQYHU��*URXS����. Select thePublication &XVWRPHU��3URVSHFWV��E\�&RXQWU\���=,3�&RGH�. Select thecriteria values as specified in the exercise and assign your site via the$VVLJQ-Button.
1-4 Monitor the Outbound Queue
1-4-1 After assigning a site of type Mobile Client to a Subscription, the majorRealignment is triggered. As a result all the messages that belong to theSubscription are appended to the Outbound Queue of the Mobile Client. TheOutbound Queue can be displayed within the Administration Console. Viewthe details of the Site. In the area 'HSHQGHQW�,QIRUPDWLRQ, select the 4XHXHtab. A double click on the Queue name (R = read = Outbound Queue, W =write = Inbound Queue) navigates to the corresponding queue.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-1
SAP AG 2001
l 7\SHV�RI�'DWD�([FKDQJH�EHWZHHQ�WKH&50�6HUYHU�DQG�RWKHU�&RPSRQHQWV
l 6HWWLQJ�)LOWHUVl 3HUIRUPLQJ�WKH�YDULRXV�/RDGVl 0RQLWRU�WKH�/RDGV
&RQWHQWV�
'DWD�([FKDQJH�ZLWK�5���%DFN�(QGV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-2
SAP AG 2001
l ([SODLQ�WKH�GLIIHUHQW�W\SHV�RI�GDWD�H[FKDQJHEHWZHHQ�WKH�&50�6HUYHU�DQG�RWKHU�PDMRUFRPSRQHQWV
l 3HUIRUPLQJ�WKH�/RDGV�EHWZHHQ�WKH�&506HUYHU�DQG�6$3�5���%DFN�(QGV
l 0RQLWRU�WKH�GDWD�/RDGV
$W�WKH�FRQFOXVLRQ�RI�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�
'DWD�([FKDQJH�ZLWK�5���%DFN�(QGV��8QLW�2EMHFWLYHV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-3
SAP AG 2001
&RXUVH�2YHUYLHZ�'LDJUDP
0LGGOHZDUH�2YHUYLHZ0LGGOHZDUH�2YHUYLHZ
&RQFHSWV�RI�WKH�&50�0LGGOHZDUH&RQFHSWV�RI�WKH�&50�0LGGOHZDUH
5HSOLFDWLRQ�$GPLQLVWUDWLRQ5HSOLFDWLRQ�$GPLQLVWUDWLRQ
0RQLWRULQJ��(UURU�+DQGOLQJ0RQLWRULQJ��(UURU�+DQGOLQJ
,QVWDOODWLRQ��&RQILJXUDWLRQ,QVWDOODWLRQ��&RQILJXUDWLRQ
6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ
'DWD�([FKDQJH�ZLWK�5��%DFN�(QGV'DWD�([FKDQJH�ZLWK�5��%DFN�(QGV
'DWD�([FKDQJH�ZLWK�RWKHU6\VWHPV'DWD�([FKDQJH�ZLWK�RWKHU6\VWHPV
)XUWKHU�,QIRUPDWLRQ)XUWKHU�,QIRUPDWLRQ
&RXUVH�:UDS�8S&RXUVH�:UDS�8S
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-4
SAP AG 2001
l 8VH�WKH�$GPLQLVWUDWLRQ�&RQVROH�WR� 'HILQH�WKH�SRWHQWLDO�GDWD�UHFHLYHUV��L�H��6LWHV�� 0DLQWDLQ�WKH�GDWD�GLVWULEXWLRQ�PRGHO� 7ULJJHU�WKH�GDWD�H[WUDFWV�WR�0RELOH�&OLHQWV
'DWD�([FKDQJH���2YHUYLHZ
$GPLQLVWUDWLRQ&RQVROH
l 8VH�WKH�$GDSWHUV�WR� 3HUIRUP�WKH�GDWD�/RDGV�EHWZHHQ�WKH�&50�6HUYHU�DQG
w 6$3�5���%DFN�(QGVw ;0/�62$3�UHFHLYHUVw ,'RF�UHFHLYHUV
� ,QFOXGLQJ�GDWD�IRUPDW�FRQYHUVLRQ
n The $GDSWHU�)UDPHZRUN offers adapters and Adapter Objects for the data exchange with datareceivers of site type R/3, XML, IDoc, CRM and CDB for loading data through the CRMMiddleware.
n The replication described in the last unit and performed in the $GPLQLVWUDWLRQ�&RQVROH permitsloading data from a CRM Server towards external systems: R/3, XML, IDoc and Mobile Clients.
n This unit describes the R/3 Adapter and its Adapter Objects. The R/3 Adapter is used to performLoads between the CRM Server and an R/3 Back-End.
n Usually, a project implementation will start performing initial Loads from external systems (backendsystems). The Administration Console with its replication functionality has been introduced first (seelast unit) as the replication is a basic concept of the CRM Middleware. Source sites for an InitialLoad (described in this unit) also have to be created in the Administration Console first.
n A data format conversion between the CRM Middleware and the R/3 Back-End is necessary,because the BDoc types are not known in the R/3 Back-End.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-5
SAP AG 2001
3RVVLEOH�GDWD�H[FKDQJHV�� ,QLWLDO�/RDG��EXVLQHVV�DQG�FXVWRPL]LQJ�GDWD�
� 'HOWD�/RDG��EXVLQHVV�GDWD�RQO\�
� 6\QFKURQL]DWLRQ�/RDG��&'%�FXVWRPL]LQJ�GDWD�RQO\�
� 5HTXHVW�RI�VSHFLILF�GDWD��EXVLQHVV�DQGFXVWRPL]LQJ�GDWD�
QRQ�5��%DFN�(QG
'DWD�([FKDQJH�YLD�$GDSWHUV
�&50�6HUYHU
5���%DFN�(QG
%:
n The following types of data transfer to and from the CRM System towards SAP R/3 Back-Ends aredistinguished:
é ,QLWLDO�GDWD�WUDQVIHU��EXVLQHVV�GDWD�DQG�FXVWRPL]LQJ�GDWD�� After the installation of the CRMMiddleware all data needed (pre-defined objects) from an external system is loaded in bulk to theCRM Server. Note that the business data also contain conditions.
é 'HOWD�GDWD�WUDQVIHU��EXVLQHVV�GDWD�RQO\�� Only delta information is loaded from the externalsystem during normal operation. For example, when modifying business partner on the externalsystem, only the modifications are transferred to the CRM Server.
é 6\QFKURQL]DWLRQ��FXVWRPL]LQJ�GDWD�� The Synchronization Load may be used to updatecustomizing object changes in the R/3 Back-End or in the CRM Database with the CDB. This typeof data exchange is provided only for customizing data and must be started manually, i.e. there isno automatic delta mechanism for customizing objects.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-6
SAP AG 2002
3RVVLEOH�,QLWLDO�/RDGV�EHWZHHQ�WKH�YDULRXV�GDWDEDVHV
��������&50�6HUYHU
0DLQ�&50�'DWDEDVH
'%�IRU�PRELOH�VFHQDULRV
'DWD�([FKDQJH�±�,QLWLDO�/RDGV
&'%
&50�'%
1RQ�5��%DFN�(QG
�5���%DFN�(QG5���'%
'DWDEDVH
2QO\EXVLQHVV
GDWD
%:%:�'%
n The ,QLWLDO�/RDG�XVXDOO\ takes the following steps:
1. SAP R/3 Back-End → CRM System to provide the CRM Database with data.
2. In case a mobile scenario is used, data may then be transferred further from the CRM Databaseto the CDB. Note: Before doing so, the Mobile Bridges have to be activated.
n Use�0LGGOHZDUH�→�'DWD�([FKDQJH�→�,QLWLDO�/RDG�→�6WDUW��transaction R3AS) in order to transferdata (for both steps).
n At present, only some business objects are supported for the Initial Load from the CRM Server to anR/3 Back-End, e.g. Business Partner. Note that a corresponding subscription needs to exist in theAdministration Console.
n For information about a general analysis of the Initial Load refer to OSS note: 443900 (especially429423).
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-7
SAP AG 2001
l 6LQJXODU�GDWD�/RDG�IURP�RQH�V\VWHP�RU�GDWDEDVH�WR�DQRWKHUl 'XH�WR�GHSHQGHQF\�RI�REMHFWV�D�VSHFLILF�VHTXHQFH�GXULQJ�GDWD
/RDG�LV�QHFHVVDU\� &XVWRPL]LQJ� %XVLQHVV�2EMHFWV� 3DUHQW���FKLOG�UHODWLRQVKLS�EHWZHHQ�GLIIHUHQW�REMHFWV
l 6SHFLI\�ILOWHU�VHWWLQJVl 6WDUW�RI�/RDG�E\�VHOHFWLQJ�REMHFW��VRXUFH�VLWH�DQG�WDUJHW�VLWHl &KHFN�SURFHVV�PRQLWRUl ([WHQVLYH�XVH�RI�T5)&�WHFKQLTXH
� 6HTXHQFLQJ�RI�GDWD� %DVHG�RQ�W5)&��WUDQVDFWLRQDO�5)&�� 3DUDOOHOL]DWLRQ�SRVVLEOH
l �
,QLWLDO�/RDG���2YHUYLHZ
n An Initial Load is a singular Load of data from one system to another
n Initial Load from the R/3 Back-End to the CRM Database, from the CRM Database to the CDB,from the R/3 Back-End to the CDB, from the CRM Database to external site etc.
n Use of qRFC mechanism
n For more information refer to
é the 6$3�6HWXS�DQG�/RDG�*XLGH (may be found in the SAPNet via the alias: LQVWJXLGHV�→�P\6$3&50�→�6$3�&50�����→�)LHOG�6DOHV�→�,QVWDOODWLRQ��WKHQ�&50�6HUYHU�&RQILJXUDWLRQ),
é the Adapter Framework documentation (same location as the SAP Setup and Load Guide) and
é the documentation about the XIF Adapter (SAPNet alias: crm-ci → Media Center →Documentation).
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-8
SAP AG 2001
l )LOWHUV�DUH�DSSOLHG�GXULQJ�WKH�GDWD�H[WUDFW��L�H�� )URP�5���WR�&50��,QLWLDO�DQG�'HOWD�/RDGV� )URP�&50�WR�DOO�RWKHU�6LWHV��,QLWLDO�/RDG�RQO\�
�ILOWHU�IRU�'HOWD�/RDGV�DUH�GHILQHG�YLD�6XEVFULSWLRQV�l 3XUSRVH�
� 5HGXFH�WKH�GDWD�YROXPH�EHWZHHQ�WKH�5���%DFN�(QG�DQG�WKH�&506HUYHU
� .HHS�WKH�5���VSHFLILF�GDWD�ZLWKLQ�WKH�5���%DFN�(QGl 2SWLRQV�
� )LOWHUV�VWRUHG�DQG�DSSOLHG�RQO\�LQ�VRXUFH�GDWDEDVH��H�J��5���� )LOWHUV�VWRUHG�DQG�DSSOLHG�RQO\�LQ�WDUJHW�GDWDEDVH��H�J��&50�� )LOWHUV�VWRUHG�DQG�DSSOLHG�LQ�ERWK�GDWDEDVHV
l %XVLQHVV�REMHFWV�DQG�FRQGLWLRQ�REMHFWV��RQO\�VSHFLILF�ILOWHUV�DUHDOORZHG���H�J��IRU�3DUWQHU�QXPEHU�IRU�%87����
l &XVWRPL]LQJ�REMHFWV��QR�UHVWULFWLRQV�EXW�FKHFN�IRU�'',&FRQVLVWHQF\
)LOWHU�6HWWLQJV��,�
n Filter settings are part of customizing the system.
n If data is filtered in the source system, i.e. the R/3 Back-End, the filter will be applied to the databefore it is send to the CRM Server. This reduces the data traffic between the R/3 Back-End and theCRM Server. The filters are also available for Delta Loads (R/3 Back-End to the CRM Server). Notethat not all business objects support this feature yet.
n This concept is new with the CRM release 3.0.
n The filter settings must be activated manually. Please refer to the application documentation forfurther information.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-9
SAP AG 2001
2EMHFW�VSHFLILF�ILOWHU�FULWHULD�
)LOWHU�6HWWLQJV��,,�
%XVLQHVV�2EMHFWV��������� ��� �����������
������� �!�"��# $% �'&��(!)*��� �!�,+-� ./10���� 23)4�3.��5+'��3�6� +-7
8 +-7 ��&39!(;:��;)<��.�
= = =
>��1?�@�ACBED1FGB HJI% 7 +'&'&!� KL� :M+'L� (�.-NM�OPL� � �!�'P�
�� 7 7Q(;KR�5+S��-�T� +�7�O�'&!� .3�M&�&4�!+;�PL.'�-�% �Q&�T(�)4�;�1�,+'&'P�!�8 �!� UR� :'�V/-0R�!� 2�)W�-.M��+���;� � +!7M��+M&3P�;�8 +-7 ��&4X�(!:;��)W��.'�&
= = =
Y�B�Z F �OA ?��!F F[B�I�\�?]]]]]]]]
^PIR�R@!F[B _��````a```
b!+��!7 � c!� �-7 9 �W� d;(�e
f�$!�5g f�b-�hf�X /1i j3jQj3k
l�� m�n2EMHFW�ILOWHU�VHWWLQJV
n The objects to be exchanged between CRM and SAP R/3 Back-Ends may be filtered using filtercriteria��These criteria are applied to the Adapter Objects for the Load (initial or delta) from an SAPR/3 Back-End.
n Filter options allow the filtering of business objects at the source, at the target or at both the sourceand the target for business objects. However, business data are usually filtered at the source.Customizing, materials or condition objects can be filtered at the source only. Filtering the data inthe source has the advantage that less data is transferred to the CRM Server.
n Saving a filter entry triggers the automatic transfer to the Plug-In in the R/3 Back-End.
n The transaction to specify the filter criteria is found under: 0LGGOHZDUH�→ 'DWD�([FKDQJH�→ 2EMHFW0DQDJHPHQW�→ %XVLQHVV�2EMHFW��5�$&�����&XVWRPL]LQJ�2EMHFWV��5�$&�����&RQGLWLRQ�2EMHFWV�5�$&���
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-10
SAP AG 2001
l 6HOHFW�WKH�REMHFWV�WR�EH�ORDGHG�IURP�WKH�5���%DFN�(QG�RU�IURPWKH�&50�'DWDEDVH
l 6HOHFW�WKH�VRXUFH�DQG�WDUJHW�VLWHVl 6WDUW�WKH�,QLWLDO�/RDG����0RQLWRULQJl 0RQLWRU�2EMHFWVl 7KH�0LGGOHZDUH�3RUWDO
6WDUWLQJ�DQG�0RQLWRULQJ�WKH�,QLWLDO�/RDG
n The transaction to start the Initial Load can be found at:0LGGOHZDUH�→�'DWD�([FKDQJH�→�,QLWLDO�/RDG�→�6WDUW��5�$6��
n If the Initial Load finishes unsuccessfully, consult OSS note 443900, which gives useful advice for aJHQHUDO�HUURU�DQDO\VLV.
n The location of the transaction to PRQLWRU�WKH�,QLWLDO�/RDG is:0LGGOHZDUH�→�'DWD�([FKDQJH�→�,QLWLDO�/RDG�→�0RQLWRU�2EMHFWV��5�$0���
n You may also use the 0LGGOHZDUH�3RUWDO to view the status of Initial Loads. The Middleware Portalcan be accessed via0LGGOHZDUH�→�0RQLWRULQJ�→�&HQWUDO�0RQLWRULQJ�→�0LGGOHZDUH�3RUWDO��60:3��
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-11
SAP AG 2001
0RQLWRU�,QLWLDO�/RDG
n Screen shot of the Initial Load monitor.
n Usually all traffic lights should be green. If an Initial Load is still running the traffic lights show thestatus running (yellow light). There are two cases were the monitor shows the status waiting:
é The parent objects are not yet loaded. In this case the Initial Load of the parent objects must beperformed first. As soon as the Initial Load of the parent objects has finished successfully, theobject with the status waiting are loaded automatically.
é The number of objects, for which Initial Load was started, is higher than the number ofavailable system processes. In this case the available processes are used for the Initial Load andthe remaining objects are set to the status waiting. These objects are loaded automatically assoon as system processes are available.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-12
SAP AG 2002
��������&50�6HUYHU
0DLQ�&50�'DWDEDVH
'%�IRU�PRELOH�VFHQDULRV
'DWD�([FKDQJH�±�'HOWD�/RDGV
'HOWD�GLVWULEXWLRQ�RI�EXVLQHVV�GDWD
&'%
&50�'%
1RQ�6$3�6\VWHP
�5���%DFN�(QG5���'%
'DWDEDVH
2QO\EXVLQHVV
GDWD
%:%:�'%
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-13
SAP AG 2001
6$3�5��
&50�0LGGOHZDUH
l &RQWLQXRXV�V\QFKURQL]DWLRQEHWZHHQ�DQ�6$3�5���%DFN�(QGDQG�WKH�&50�0LGGOHZDUH
l 'DWD�FKDQJHV�DUH�VHQW�WR�WKHUHFHLYHUV�LPPHGLDWHO\
l 5HFHLYHG�GDWD�LV�SURFHVVHGDXWRPDWLFDOO\
l $OO�SUHGHILQHG�/RDG�2EMHFWV�DUHVXSSRUWHG��H[FHSW�FXVWRPL]LQJWDEOHV
l T5)&�LV�XVHG�IRU�VHULDOL]DWLRQ
'HOWD�/RDG���2YHUYLHZ
n The 'HOWD�/RDGV allow a continuous synchronization of predefined Adapter Objects (exceptcustomizing data) between R/3 Back-Ends and the CRM Server, that means that data updates aresent to the CRM Server LPPHGLDWHO\. Received data is processed automatically. qRFC is used forthe serialization.
n Delta Loads may also consist of /RDGV from the CRM Server to an SAP R/3 Back-End. In this casethe R/3 site must be assigned to subscriptions, in order to receive data.
n Changes of the CRM Database are automatically sent to the CDB via the BDoc Flow, if the MobileBridges are activated. Mobile Bridges map messaging BDoc messages to synchronization BDocmessages.
n The Delta Load is activated after a successful Initial Load.
n Note that the Delta Load from the CDB to the CRM DB is not directly possible, since the CDB isupdated after the CRM Database is updated. However, delta messages from Mobile Clients gothrough the Synchronization and Messaging Flow to the CRM Adapter, which updates the CRMDatabase.
n More information about the general analysis of the Delta Load from the R/3 Back-End to the CRMServer consult OSS note 430980. To analyze the Delta Load from the CRM Server to the R/3 Back-End refer to OSS note 431345.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-14
SAP AG 2001
l 6HUYLFH�GDWD� 6HUYLFH�UHTXHVW� 6HUYLFH�RUGHU� 7LPH�FRQILUPDWLRQ
l ,QYRLFH�GDWD� %LOOLQJ�GRFXPHQWV
l 0DUNHWLQJ�GDWD� &DPSDLJQV
/RDG�2EMHFWV�DQG�ORDG�GLUHFWLRQ�GHSHQG�RQ�WKHEXVLQHVV�REMHFWV�
5�� &50([DPSOHV�
l &XVWRPL]LQJ�GDWDl &RPPRQ�EXVLQHVV�GDWD
� %XVLQHVV�3DUWQHU� 3URGXFW� &RQGLWLRQV
l 6DOHV�GDWD� 6DOHV�RUGHU
'DWD�([FKDQJH�EHWZHHQ�DQ�5���%DFN�HQG�DQG�&50
n /RDG�2EMHFWV can be exchanged between a source and a target system, for example, between anSAP R/3 Back-End and the CRM Server. Examples are business partner master data, orders, andproduct master data. They are grouped as follows:
é Business objects
é Customizing objects
é Condition objects
é The objects are stored in the table SMOFOBJECT.
n Please consider that the question what objects are loaded to what target systems depends on thebusiness process and has to be defined for each application. Generally, Initial Loads and Delta Loadsmay be performed from R/3 to CRM and vice-versa (and CRM to CDB in case of a mobile scenario).Examples:
é Conditions will only be loaded from the R/3 Back-End to the CRM Server.
é Sales orders will usually be loaded from CRM to R/3 for further execution. There is no InitialLoad, only a Delta Load.
é For more information refer to the relevant applications.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-15
SAP AG 2001
'HOWD�/RDG�IURP�5���%DFN�(QGV�WR�WKH�&50�6HUYHU
6WDUWLQJ�DQ�,QLWLDO�/RDG�IURP�DQ�5���%DFN�(QG�DFWLYDWHV�WKH�'HOWD/RDG�LQ�WKH�5���3OXJ�,Q��%7(V�
1R�'HOWD�/RDGV�IRU�FXVWRPL]LQJ�REMHFWV�DYDLODEOH
4XHXH�QDPLQJ�FRQYHQWLRQ��5�$'B�REMBQDPH�SDUW!�,'�SDUW!
'HOWD�TXHXHV�DUH�VWRSSHGGXULQJ�DQ�,QLWLDO�/RDG
'HOWD�TXHXHV�DUH�UHOHDVHGDIWHU�D�VXFFHVVIXO�,QLWLDO/RDG
0DQXDO��GH�DFWLYDWLRQSRVVLEOH
n During an Initial Load all delta messages are collected by stopping the delta queues. This ensuresthat all delta messages that are created during the initial load are not lost and that the order in whichthey occur remains the same.
n After a successful Initial Load the stopped delta queues will be released, so that the delta messagescan be processed. Note that this also guarantees that the CRM Server receives delta messages onlyfor business objects, which have been loaded to the CRM Server before.
n Manual (de)activation of Delta Loads is possible via the transaction:0LGGOHZDUH�→�'DWD�([FKDQJH�→�'HOWD�/RDG�IURP�5���%DFN�(QG�→�6HW�8S�'HOWD�/RDG��5�$&���
n Sometimes it can make sense to activate the Delta Load for certain objects without having performedan Initial Load first. For an Internet Sales scenario, for example, it may not be always necessary toLoad already processed Sales Orders from an R/3 Back-End to the CRM Server. In this case it issufficient to activate the Delta Load for Sales Order manually.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-16
SAP AG 2001
l 5���6LWHV�UHFHLYH�GDWD�YLD6XEVFULSWLRQV
l 7KLV�GLUHFWLRQ�LV�KDQGOHGE\�WKH�5HSOLFDWLRQ�0RGHO
'HOWD�/RDG�IURP�WKH�&50�6HUYHU�WR�5���%DFN�(QGV
n The Delta Load from the CRM Server to the R/3 Back-End is Maintained via the assignment of R/3Sites to Subscriptions. For more information refer to the unit $GPLQLVWUDWLRQ�5HSOLFDWLRQ.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-17
SAP AG 2001
6\QFKURQL]DWLRQ�/RDG�RI�&'%�FXVWRPL]LQJ�GDWD
��������&50�6HUYHU
0DLQ�&50�'DWDEDVH
'%�IRU�PRELOH�VFHQDULRV
'DWD�([FKDQJH�±�6\QFKURQL]DWLRQ�/RDGV
&'%
&50�'%
�5���%DFN�(QG
5���'%
n The Synchronization Loads may be used to synchronize the R/3 or CRM database with the CDB.6\QFKURQL]H�2EMHFWV (sometimes called COMPARE) creates net field information. Data loadedfrom the CRM Database is compared with the contents of the CDB and only modified or deleted datais updated in the CDB and replicated to the mobile clients.
n The Synchronization Load may be started automatically as a batch job in regular time intervals.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-18
SAP AG 2001
� $YDLODEOH�IRU�FXVWRPL]LQJ�REMHFWV�WKDW�DUH�H[FKDQJHGZLWK�WKH�&'%��DQG�PRELOH�FOLHQWV�
� 'DWD�IURP�5���%DFN�(QGV�&50�'DWDEDVH�DUH�FRPSDUHGZLWK�WKH�GDWD�LQ�WKH�&'%�
� $OO�WKH�V\QFKURQL]HG�GDWD�LV�UHSOLFDWHG�WR�WKH�0RELOH&OLHQWV�WR�JHW�WKHP�³,Q�6\QF´
� 6\QFKURQL]DWLRQ�/RDG�RQO\�ZRUNV�IRU�&XVWRPL]LQJ2EMHFWV�OLQNHG�WR�D�6\QFKURQL]DWLRQ�%'RF
6\QFKURQL]DWLRQ�/RDG
n Synchronization is necessary for those objects which don‘t have a Delta Load.
n The Synchronization Load is a generic mechanism only available for synchronization BDoc types,i.e. CDB tables.
n Make sure that before enabling the Synchronization Load that the prerequisites are fulfilled. Pleaseconsult the SAP note 452582 for further details.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-19
SAP AG 2002
6\QFKURQL]DWLRQ�/RDG�IRU�0RELOH�&XVWRPL]LQJ�'DWD
1 . . . .
1 . . . .
2.
1R�$FWLRQ
2 . A . .
2 . B . .
'DWD�'LIIHUHQFH
3 . . . .
1R�'DWD4 . . . .
'HOHWLRQ�RQ�5��
8SGDWH&'%
5HSOLFDWH'DWD
:ULWHWR
&'%5HSOLFDWH
'DWD'HOHWHIURP&'%
5HSOLFDWH'HOHWH
0HVVDJHV
/RDG
&RPSDUH$FWLRQV
6$3�5���%DFN�(QG���&50'DWDEDVH
6\QFKURQL]DWLRQ�/RDG
���
���
���1R�'DWD�5HFHLYHG
%'RF %'RF %'RF
&'%
12345
. . ..A . ... . ..
. . ..deleted
n 6\QFKURQL]DWLRQ�PHFKDQLVP: The synchronization mechanism creates net field information. Dataloaded from the SAP R/3 Back-End is compared to the contents of the Consolidated Database andonly modified or deleted data is updated in the CDB and replicated to the mobile clients.
n This method is used to update data not included in automatic Delta Loads, since it changesinfrequently or only in small amounts, e.g. customizing tables.
n The 6\QFKURQL]DWLRQ�/RDG can also be used to fix inconsistencies, should they be detected. Missingor redundant data in the CDB can be updated, e.g. after archiving on the SAP R/3 Back-End.
n Individual Load Objects may be compared.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-20
SAP AG 2001
/RDG�RI�EXVLQHVV�DQG�FXVWRPL]LQJ�GDWD��FRQGLWLRQV
��������&50�6HUYHU
0DLQ�&50�'DWDEDVH
'%�IRU�PRELOH�VFHQDULRV
'DWD�([FKDQJH�±�5HTXHVW
&'%
&50�'%
�5���%DFN�(QG
5���'%
UHTXHVW
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-21
SAP AG 2001
5HTXHVW
8VH�5HTXHVWV�WR�ORDG�GHGLFDWHG�GDWD�RQO\6WDUW�RI�5HTXHVW�VLPLODU�WR�,QLWLDO�/RDG5HTXHVWHG�GDWD�LV�UHSOLFDWHG�WR�DOO�VXEVFULEHG�FRPSRQHQWV�LQFOXGLQJ�PRELOH�FOLHQWV��H[FOXGLQJ�VHQGLQJ�V\VWHP�LWVHOI�
n Requests may be started via the menu 0LGGOHZDUH�→�'DWD�([FKDQJH�→�6\QFKURQL]DWLRQ�→�6WDUW�5HTXHVWV��5�$5���
n The 5HTXHVW loads selected data from an R/3 Back-End to the CRM Database or vice versa. Notethat the Request of objects from the CRM Database to an R/3 Back-End is not supported for allobjects.
n The request filters are merged with the general Adapter Object filters. &DXWLRQ� general AdapterObject filters for the table fields are ignored during a Request, if the filters of that Request aredefined for the same table fields. The reason for this is that the extractors, i.e. the modules thatextract the data from the database, combine filters for the same table fields with an “or” statement. Ifthe filter of a Request is also be combined with an “or” statement, the result would be the entire datavolume of the Initial Load. Thus, please keep this in mind, if you define filters for Requests.
n Request can also be planned via batch jobs
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-22
SAP AG 2001
<RX�DUH�QRZ�DEOH�WR�
'DWD�([FKDQJH�ZLWK�5���%DFN�(QGV��6XPPDU\
l ([SODLQ�WKH�GLIIHUHQW�W\SHV�RI�GDWD�H[FKDQJHEHWZHHQ�WKH�&50�6HUYHU�DQG�RWKHU�PDMRUFRPSRQHQWV
l 3HUIRUPLQJ�WKH�/RDGV�EHWZHHQ�WKH�&506HUYHU�DQG�6$3�5���%DFN�(QGV
l 0RQLWRU�WKH�GDWD�/RDGV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-23
([HUFLVHV
8QLW� 'DWD�([FKDQJH�ZLWK�6$3�5���6\VWHPV7RSLF� ,QLWLDO�'DWD�/RDG��([DPSOH�6$3�5���WR�&50�
At the conclusion of this exercise, you will be able to:
• Set filter objects for an object to be loaded
• Perform the initial load
• Monitor the loadThe exchange of data with external systems is an important task of the CRMMiddleware. You need to transfer customizing and/or business data to the CRM Serverand from the CRM Server to other systems, e.g. to back-end systems for furtherexecution.
Technically, the initial load demands a number of steps taken before (parameter settings,replication administration, customizing of the CRM applications etc.) and is it a pre-requisite for the delta load of change objects.
You want to load customizing objects for the first time from an external system into the CRMServer. As the back-end system used in this exercise is an SAP R/3 System, you will use theR/3 Adapter functionality.
1-1 Compare the tables in the source system and in the target system.
View the (customer-defined) customizing table ZCR500_## in the SAP R/3System.
2-1 Set your load filters. Since the back-end system for this exercise is an SAP R/3System, you use the R/3 Adapter functionality.
What transaction will you use to set the filter?
_______________________________________________________________
You want to filter the data load according to the field &RXQWU\. Select one countryfrom the source table.
3-1 You may now perform the initial load for the table ZCR500_## from the R/3System into the CDB:
What transaction will you use to perform the load?
Which data do you have to provide for the initial load?
Start the initial load.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-24
4-1 Where can you monitor the load? Check the system and name a few possibilities!
_______________________________________________________________
5-1 Use the path from Exercise 1 to view the table content on the CRM Server.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-25
6ROXWLRQV
8QLW� 'DWD�([FKDQJH�ZLWK�6$3�5���6\VWHPV7RSLF� ,QLWLDO�'DWD�/RDG��([DPSOH�6$3�5���WR�&50�
1-1 Compare the tables in the source system and in the target system.
View the (customer-defined) customizing table ZCR500_## in the SAP R/3System.
Use the transaction SE11 to go to the Data Dictionary, enter ZCR500_## forDatabase Table and press Display.
Here the structure of the table ZCR500_## is shown.
By pressing the button Contents or via Utilities�→�Table contents�→�Display youmay view the table content.
A similar table exists on the CRM Server (use the same transaction and the samepath). However, here the table is still empty.
2-1 Set your load filters. Since the back-end system for this exercise is an SAP R/3System, you use the R/3 Adapter functionality.
What transaction will you use to set the filter?
0LGGOHZDUH�→�'DWD�([FKDQJH�→�2EMHFW�0DQDJHPHQW�→�&XVWRPL]LQJ�2EMHFWV�WUDQVDFWLRQ�5�$&��You want to filter the data load according to the field &RXQWU\. Select one countryfrom the source table.
Mark the line with the name of customizing object =&5���B��B'�, click on the&KRRVH�button, go to 7DEOHV�6WUXFWXUHV, press the 'LVSOD\�→�&KDQJH�button andpress the )LOWHU button.
Then, you set the 6RXUFH�6LWH�1DPH (the name of your R/3 site in theAdministration Console) and enter the field name you want to filter the data with:&RXQWU\.Set the operator to (TXDOLW\� �/RZ and enter a country of table ZCR500_## in field/RZ.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 5-26
3-1 You may now perform the initial load for the table ZCR500_## from the R/3System into the CDB:
What transaction will you use to perform the load?
0LGGOHZDUH�→�'DWD�([FKDQJH�→�,QLWLDO�/RDG�→�6WDUW��WUDQVDFWLRQ�5�$6�Which data do you have to provide for the initial load?
You need to enter the name of the load object (=&5���B��B'�) and the name ofthe source site (the SAP R/3 System). The possible sites (R/3 site and the CDB)have been defined for the adapter object.
Start the initial load.
The initial load may be either started immediately or it can be scheduled in abackground task:
a) immediately:3URJUDP�→�([HFXWH�or just press the ([HFXWH button
b) in the background:
3URJUDP�→�([HFXWH�LQ�EDFNJURXQG�→��&RQILUP�WKH�%DFNJURXQG�3ULQW3DUDPHWHUV�→�(QWHU�WKH�VWDUW�WLPH��H�J��LPPHGLDWHO\��DQG�VDYH�
4-1 Where can you monitor the load? Check the system and name a few possibilities!
0LGGOHZDUH�→�'DWD�([FKDQJH�→�,QLWLDO�/RDG�→�0RQLWRU�2EMHFWV��5�$0��Enter the object name =&5���B��B'� and execute. Use the 5HIUHVK button in orderto update the display.
The same transaction can be found via
0LGGOHZDUH�→�0RQLWRULQJ�→�'DWD�([FKDQJH�→�0RQLWRU�2EMHFWVor
0LGGOHZDUH�→�0RQLWRULQJ�→�&HQWUDO�0RQLWRULQJ�→�0LGGOHZDUH�3RUWDO�→5XQWLPH�,QIRUPDWLRQ�→�$GDSWHU�6WDWXV�,QIRUPDWLRQ�→�,QLWLDO�/RDG�6WDWXV�→��/RDG6WDWXV�or ,QERXQG�4XHXHV�LQ�&50�6HUYHU�IURP�2/73�6\VWHP�V�
5-1 Use the path from Exercise 1 to view the table content on the CRM Server.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-1
SAP AG 2001
l ;,)�$GDSWHUl ';�:RUNEHQFKl &50���%:�,QWHJUDWLRQl $6&,,�$GDSWHU
&RQWHQWV�
'DWD�([FKDQJH�ZLWK�RWKHU�6\VWHPV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-2
SAP AG 2001
l ([SODLQ�KRZ�;0/�DQG�,'RF�LQWHUIDFHV�FDQ�EHXVHG�IRU�GDWD�H[FKDQJH�ZLWK�QRQ�6$3�V\VWHPV
l ([SODLQ�WKH�PDMRU�VWHSV�QHFHVVDU\�WR�LPSRUWOHJDF\�GDWD�YLD�WKH�';�:RUNEHQFK
l 'HVFULEH�WKH�LQWHUDFWLRQ�EHWZHHQ�D�%XVLQHVV,QIRUPDWLRQ�:DUHKRXVH��%:��DQG�WKH�&500LGGOHZDUH
l 'HVFULEH�WKH�LPSRUW�RI�GDWD�LQ�IRUP�RI�$6&,,ILOHV�WR�WKH�&50�0LGGOHZDUH
$W�WKH�FRQFOXVLRQ�RI�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�
'DWD�([FKDQJH�ZLWK�RWKHU�6\VWHPV��8QLW�2EMHFWLYHV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-3
SAP AG 2001
&RXUVH�2YHUYLHZ�'LDJUDP
0LGGOHZDUH�2YHUYLHZ0LGGOHZDUH�2YHUYLHZ
&RQFHSWV�RI�WKH�&50�0LGGOHZDUH&RQFHSWV�RI�WKH�&50�0LGGOHZDUH
5HSOLFDWLRQ�$GPLQLVWUDWLRQ5HSOLFDWLRQ�$GPLQLVWUDWLRQ
0RQLWRULQJ��(UURU�+DQGOLQJ0RQLWRULQJ��(UURU�+DQGOLQJ
,QVWDOODWLRQ��&RQILJXUDWLRQ,QVWDOODWLRQ��&RQILJXUDWLRQ
6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ
'DWD�([FKDQJH�ZLWK�5��6\VWHPV'DWD�([FKDQJH�ZLWK�5��6\VWHPV
'DWD�([FKDQJH�ZLWK�RWKHU6\VWHPV'DWD�([FKDQJH�ZLWK�RWKHU6\VWHPV
)XUWKHU�,QIRUPDWLRQ)XUWKHU�,QIRUPDWLRQ
&RXUVH�:UDS�8S&RXUVH�:UDS�8S
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-4
SAP AG 2001
;,)�$GDSWHU
;,)�$GDSWHU
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-5
SAP AG 2002
,QWHUIDFHV�WR�QRQ�6$3�6\VWHPV
&50�����VXSSRUWV�WKH�IROORZLQJ�LQWHUIDFHV��YLD�DGDSWHUV��� ;0/���,'RF
w %XVLQHVV�SDUWQHU��KLHUDUFK\��UHODWLRQ�±�LPSRUW���H[SRUW
w %XVLQHVV�7UDQVDFWLRQ��VDOHV���VHUYLFH�RUGHU��DFWLYLW\��±�LPSRUW���H[SRUW
w 3URGXFW�±�LPSRUW
w &RQGLWLRQ���LPSRUW
w ,QYRLFH�±�H[SRUW� )LOH�EDVHG�LPSRUW
w 6$3�'DWD�7UDQVIHU��';��:RUNEHQFK
w $6&,,�$GDSWHU
n The CRM Middleware provides the following interfaces for initial or delta loads from/towards non-SAP systems:
é XML messages,
é Intermediate Documents (IDocs) via ALE, the SAP Business Connector or the SAP Data TransferWorkbench (DX Workbench),
é ASCII flat files.
n The messaging interfaces can be used for a number of scenarios:
é Migration from a legacy system that will be replaced by mySAP CRM,
é Integrating CRM with non-SAP backend systems,
é B2B communication with business partners.
n The CRM Middleware provides interfaces for products (e.g. materials or services), business partners(e.g. customers, contact persons or employees), business partner hierarchies, business partnerrelations and sales orders. This allows customers to exchange this data with legacy backend systemsinitially and on a regular basis. Delta loads take place, when changes to existing objects are made orwhen new objects are created. The exchange of customizing data is not relevant to the data exchangewith non-SAP backend systems. Product configuration and marketing data is also not exchanged.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-6
SAP AG 2001
;,)�$GDSWHUP%'RF
;0/�ILOH
,'RF
&50�6HUYHU��&50�0LGGOHZDUH
([WHUQDO6\VWHPV
l 7KH�([WHUQDO�,QWHUIDFH�$GDSWHU��;,)��SURYLGHV�� $�VHUYLFH�LQ�WKH�0HVVDJH�)ORZ� ,'RF�DQG�;0/�LQWHUIDFHV�IRU�H[WHUQDO�V\VWHPV
7KH�;,)�$GDSWHU���2YHUYLHZ
n The external interface adapter (XIF adapter) provides:
é Services in the CRM Server Messaging Flow
é Bulk-message capable IDoc and XML interfaces for external systems.
n More information about the XIF Adapter may be found in the SAPNet via the alias: crm-ci.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-7
SAP AG 2001
�([WHUQDO�,QWHUIDFH�$GDSWHU
���������� �������� ��� �������� �� ��������! �"#�$�
% �&���'�&(
&50�6HUYHU
)+*�,.-/&0 �$�1��2!� 043
)�,!-�65����'��������7�������$8�9� 0
,!: �<;'�#=$��5��>$?* 5��@=$��5��>/ 5#�$8�A� ���
)+*B,.-�CED % :
;E�+�
�AF / �
G �H�@� I 0 > - � 0 �H"% � >>�� �82J� 0 �
/ � ��� / �'� �
KLK'K�KMK'KKLK'K�KMK'K
/ ; : �
9DOLGDWLRQ0HVVDJLQJ)ORZP%'RF
&50�0LGGOHZDUH
�& $�H� 0 �����) "��$�N�&�
([WHUQDO�,QWHUIDFH�$GDSWHU
n In outbound transactions, for example, creating or changing a Data Object within an applicationtransaction, an mBDoc is created and transferred to the CRM Middleware. Possible externalreceivers for the mBDoc are determined within the CRM Middleware and are transferred to the XIFadapter together with the mBDoc. The data in the mBDoc is converted in the XIF adapter into anXML-like complex Data Structure and an appropriate basic service (SOAP, ALE) is started thatsends the Data Object to the external receiver; for example, via a third party Middleware Tool.
n In inbound transactions, incoming messages in XML- or IDoc format are received by the XIFadapter via the basic services (SOAP, ALE) and converted into the structures in the mBDoc. TheCRM Middleware then starts, calling an appropriate application validation service that updates theapplication after successful checks on the message.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-8
SAP AG 2001
�&50�0LGGOHZDUH
7KH�([WHUQDO�,QWHUIDFH�$GDSWHU��62$3�;0/
([WHUQDO�,QWHUIDFH�$GDSWHU
&50�6HUYHU
)#,!-�75$��'��������7�������8��� 0
D % :�CN)O*P,Q-G ���@�
D % :
D % :% ��������(��'�$() "$���H���
0HVVDJLQJ)ORZP%'RF
� �RF % , ���'�'����@� �S�
D % :
n More detailed overview of SOAP/XML Processing
n SOAP/XML messages can be send to XML Messaging systems that convert the XML into otherXML schemata based on mapping rules and send these messages to other applications based onrouting rules.
n For CRM <-> Business Connector communication IDocs should be used: An IDoc transfer is quickerin comparison to SOAP/XML because the IDoc document contains no metadata information (tags)unlike an XML document, and therefore the size of document sent down the line is substantiallysmaller in comparison.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-9
SAP AG 2001
�&50�0LGGOHZDUH
7KH�([WHUQDO�,QWHUIDFH�$GDSWHU��,'RF
([WHUQDO�,QWHUIDFH�$GDSWHU
&50�6HUYHU
I 0 > - � 0 �T",!: �������U$� 0 �H� 0 �
;E�O� �AF / �
/ �L� �
D % :
I 0 > - � 0 �T",!: �% �������$(��'�$() "����H�$�
)S,J-�V5����'��������6�S��������� 0
;E�O��
�+�W; ?;N� * �
0HVVDJLQJ)ORZP%'RF �PF % , ���'� ����@� ���
�+�W;) 5= CL) "$���H�$� �W�W;/ �L� �
/ � ����X@�L� ��M�1;E�O��X�� 0 �Y���
n More detailed overview of IDoc Processing.
n IDocs can be used to send messages to the Business Connector where an IDoc XML document willbe established and mapped into other XML Schemata such as Rosetta Net, xCBL or customer‘s ownschemata.
n IDocs can be used to send messages to a flat file.
n IDocs can be used to send messages to an ALE converter, where IDocs are mapped into standardizedmessage formats (EDI communication).
n IDocs can be used to send messages to an ALE Messaging System. In contrast to an ALE converterthe message handler will not perform any conversion or mapping but instead receives IDocs andsends them to applications for processing.
n IDocs can be used to send messages to an EDI Sub-System. In contrast to an ALE converter the EDI-Sub-System does not use direct program-to-program communication for transferring IDocs.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-10
SAP AG 2001
n &UHDWH�DQ�5)&�'HVWLQDWLRQZ ) %J[�\�]#^�_+`$a9b'`c_Wd&ee�f�g�hEiNd$en &UHDWH�D�/RJLFDO�6\VWHPZ )O,J: � ] � K ( Kkj _l�_+m7nJo6bLpn �&UHDWH�D�5HFHLYHU�3RUWZ q �O�7; ]#^�r4s�e�t�s�g�hLiTd�es�u�m6p�_ � 0�p�i'uNfn &UHDWH�D�3DUWQHU�3URILOHZ q �O�7; ] - � 0 �4�$� 0 �"#���Yv�w�2x� � G 0 �����H��><� ��(�� ����y��"��$�T����z��Y���L���H�&�E� % �����$�$(&�! �"����!X�� 0* 5��@=$�S5�$> - � 0 �$�Y����� 0 �n (QWHU�2XWERXQG�3DUDPHWHUVZ q �O�7; ] � K ( K ^8rAs�e�t&{9fkr�bE|Bdgyt1s�hd�e�g�f z�S����� �} �"���� _Om6nBoBb'p�l+~'l w��!��� l�n��� z % �����$��(&� "���� _�m�nBo�b'p�lO~'l w��!��� l�n z�F��$��&� U$� 0 - � 0 �������1��L���H�&�L����>n &UHDWH�D�6LWHZ ) % * � , � ] ) � ���Q2Y� � G ) � ���} &"����Y��� h�fkr4es�u�b'e�hHf�rA{Ms&g�f!{�d$r+b'|Pd�g�t 2Y� � G �1�&�L�$�T��L���$> - � 0 �@��� 0- 0 ��X@�M� �n 0DLQWDLQ�6XEVFULSWLRQV�IRU�3XEOLFDWLRQVZ ) % * � , � ] * =y�H��8�# �"#���Yw+��� tg8rAi �WhEiTd$e z8������ (��1�1��'������ �$�$>1�� ���.�@���5=��$ 0 �M���9� �S�n $VVLJQ�PDLQWDLQHG�6LWH�WR�,QWHUIDFH�7\SHZ �JF % D ; /k� �P� ] �Y�&�M���H�&�E���6�+�! &"#���!��$>�;'����� 0 XH����� �"������ _�m�nBoBb'p�l�~Ll w#�}�&���&X�� 0 � G ����82��#� �H�
&XVWRPL]LQJ�,'RF�2XWERXQG�3URFHVVLQJ
n When using IDocs for outbound processing, the above settings have to be made.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-11
SAP AG 2001
n &UHDWH�DQ�+773�'HVWLQDWLRQu 60����+773�&RQQHFWLRQV�WR�H[WHUQDO�V\VWHPV
n &UHDWH�D�6LWHu 602($&��6LWH�ZLWK�6LWH�7\SH�([WHUQDO�,QWHUIDFH�IRU�;0/�DQG�DVVLJQ�+773
GHVWLQDWLRQ
n 0DLQWDLQ�6XEVFULSWLRQV�IRU�3XEOLFDWLRQVu 602($&��2EMHFW�7\SH�6XEVFULSWLRQ��DVVLJQ�PDLQWDLQ�VLWH�WR�VXEVFULSWLRQ
n $VVLJQ�PDLQWDLQHG�6LWH�WR�,QWHUIDFH�7\SHu &50;,)B&���PDLQWDLQ�%'RF�7\SH�DQG�,QWHUIDFH�7\SH��&50;,)B B6$9(��IRU
WKH�QHZ�VLWH
&XVWRPL]LQJ�62$3�;0/�2XWERXQG�3URFHVVLQJ
n When using SOAP/XML for outbound processing, the above settings have to be made.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-12
SAP AG 2001
&XVWRPL]LQJ�,QERXQG�3URFHVVLQJ
n &XVWRPL]LQJ�,'RF�,QERXQGu &UHDWH�/RJLFDO�6\VWHP�YLD�6$/(�→�3UHSDUH�6HQGHU��DQG�5HFHLYHU�6\VWHPV
→�6HWXS�/RJLFDO�6\VWHPV�→�1DPH�/RJLFDO�6\VWHPu &UHDWH�D�3DUWQHU�3URILOH�YLD�7UDQVDFWLRQ�:(����3DUWQHU�7\SH�/6�u (QWHU�D�VXLWDEOH�0HVVDJH�7\SH�&50;,)B B6$9(B0��&50;,)B B6$9(B6��LQ
WKH�,QERXQG�3DUDPHWHUV
n �&XVWRPL]LQJ�62$3�;0/�,QERXQGu 1R�&XVWRPL]LQJ�LV�UHTXLUHG�LQ�WKH�&50�V\VWHP�IRU�UHFHLYLQJ�62$3�;0/
GRFXPHQWVu &50�+773�3RUW�6HWWLQJ�YLD�7UDQVDFWLRQ�60,&0�→�*RWR�→�6HUYLFHV
n When using IDocs or SOAP/XML for outbound processing, the above settings have to be made.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-13
SAP AG 2001
';�:RUNEHQFK
';�:RUNEHQFK
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-14
SAP AG 2001
) ��5 0 ��) "$���T���
�([WHUQDO�,QWHUIDFH�$GDSWHU�<�6�+� ) � 0 5�8�@5 0 � �����<�� �8 <�S���9�! �"��$�
% �����'�$(
�&50�6HUYHU
; ���$� 0 �&U#� ��� D�Cq � 043 =$�&�$ G
,!: ��;'�=$�S5�$>/ 5��$8�4� ��� ;E�+�
% �����'�$(U#� � :�) % C
q � 043 =$�&�$ G
) ��5 0 ��/ �L� �
/ �E� ���'��JF %/ � 0 �1���
,QLWLDO�/RDG�YLD�';�/60�:RUNEHQFK
&50�0LGGOHZDUH0HVVDJLQJ
)ORZ
P%'RF
� �&�'�'>&���@� �S�
KLK'K�KLK'KKLK'K�KLK'K
n Graphical Overview of the initial load via DX-/LSM-Workbench
n From the source system a source file is extracted (e.g. ASCII-Format). In the LSM-Workbenchstructures of the source file are mapped into IDoc structures. Within DX-Workbench IDocs are readand loaded into the system via the generated ALE Inbound function.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-15
SAP AG 2001
)XUWKHU�,QIRUPDWLRQ
$GG�2Q /LWHUDWXUH 3UHVHQWDWLRQ
http://service.sap.com/lsmw�&�����8� ���y� � � � � � � � � � � � � � �7� ��� �V� � �¡ ��¢
7UDLQLQJ�&RXUVH�%&����±�'DWD�0LJUDWLRQ
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-16
SAP AG 2001
%:�,QWHJUDWLRQ
%:�,QWHJUDWLRQ
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-17
SAP AG 2001
%:�6\VWHP
&50�6HUYHU
&50�0LGGOHZDUH
)ORZ&RQWURO
%:$GDSWHU
%'RF
'RZQORDG�RI�6ROXWLRQ:RUNERRNV
([WUDFW�RI�&50%XVLQHVV�2EMHFWV
5HSOLFDWLRQ�RI6ROXWLRQ�:RUNERRNV
,QWHJUDWLRQ�&50���%XVLQHVV�,QIRUPDWLRQ:DUHKRXVH
n The following slides provide an overview of the integration of the CRM system with the mySAPBusiness Information Warehouse (BW).
n The SAP BW is linked to the CRM Server partly by the CRM Middleware, partly by direct RFCcalls and BAPIs.
n The %:�$GDSWHU extracts data into the SAP Business Information Warehouse (SAP BW) for thefollowing BDoc types:
é Sales orders, opportunities, leads, activities, contracts, billing documents (mBDoc types)
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-18
SAP AG 2001
%:�6\VWHP
&50�0LGGOHZDUH
)ORZ&RQWURO
%:$GDSWHU
%'RF
([WUDFW�RI�&50�%XVLQHVV�2EMHFWV
l ([WUDFWLQJ�&50�GDWD�LQFOXGHV�WKH�IROORZLQJ�VWHSV�� 6HWXS�WKH�FRQQHFWLRQ�EHWZHHQ�WKH�&50�0LGGOHZDUH�DQG�WKH
%:�V\VWHP� %:�UHTXHVWV�IRU�GDWD�IRU�D�SDUWLFXODU�&50�EXVLQHVV�REMHFW
RI�WKH�&'%�DUH�LVVXHG�→�,QLWLDO�XSORDG� $IWHU�D�VXFFHVVIXO�LQLWLDO�XSORDG��GHOWD�LQIRUPDWLRQ�IRU�WKH
&50�REMHFW�LV�SDVVHG�WR�WKH�%:�V\VWHP�→�'HOWD�XSORDG
n After you have set up the connection between the CRM Middleware and your BW system, you canissue BW requests in order to obtain data for a particular CRM business object contained on theCRM Server. This will extract all data that can be used by a data source. This leads to the LQLWLDOORDG of CRM data to the BW system. This step needs to be performed only once.
n After a successful initial upload, GHOWD�ORDGV are performed automatically if required. Only the deltais transferred to SAP BW with subsequent extractions. This delta is determined by the CRMMiddleware.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-19
SAP AG 2001
3URGXFW0DQDJHPHQW
$FWLYLW\0DQDJHPHQW
6DOHV�3URFHVV0DQDJHPHQW
2SSRUWXQLW\0DQDJHPHQW
0DUNHWLQJ0DQDJHPHQW
&DPSDLJQ0DQDJHPHQW
&XVWRPHU�6HUYLFH0DQDJHPHQW
5HWHQWLRQ0DQDJHPHQW
6DOHV�3HUIRUPDQFH0DQDJHPHQW
([WUDFWHG�%XVLQHVV�2EMHFWV
n This is a collection of those CRM business objects, from which data can be extracted by the BWsystem.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-20
SAP AG 2001
6ROXWLRQ�:RUNERRNV�IRU�0RELOH�&OLHQWV
l %:�6ROXWLRQ�:RUNERRNV�DUH�XVHG�IRU�RIIOLQH�%:�UHSRUWV�RQ0RELOH�&OLHQWV
l 7KHUH�DUH�JHQHUDO�RU�XVHU�VSHFLILF�ZRUNERRNVl (DFK�ZRUNERRN�FDQ�EH�UHSOLFDWHG�WR�VHYHUDO�0RELOH�&OLHQWVl $XWRPDWLF�XSGDWHV�WR�ZRUNERRNV�DUH�GHOLYHUHG�RQ�D
VFKHGXOHG�EDVLV
&500LGGOHZDUH
%:�6\VWHP
)ORZ&RQWURO
n Online users (of CRM Server Applications or Mobile Clients) can analyze the BW data directly (viaSAPGUI / Workplace). For accessing this data RIIOLQH�RQ�WKH�0RELOH�&OLHQW, %:�6ROXWLRQ:RUNERRNV (with the corresponding queries) are used.
n Solution Workbooks are Excel files created and managed using the Business Explorer Analyzer ofthe Business Information Warehouse solution. BW queries contain the BW reporting data itself andcan be inserted into the workbooks. The�Solution Workbooks are generated and stored in the BWSystem. They are subscribed to in the same way as other data to be replicated, that is, via theAdministration Console. The CRM Middleware UHTXHVWV Solution Workbooks from the BW system.The requests can be maintained in the CRM Server via the transaction SMOBILEBW.
n After receiving a workbook update, a new Synchronization Flow�is started in the CRM Middleware.The Synchronization Flow passes the workbook updates in form of BDoc messages to the replicationservice, which computes the receivers of the updates. The outbound adapter, which is called after thereplication service, adds the workbook updates to the outbound queues of the corresponding MobileClients.
n During the next communication session, the Mobile Client receives the new workbook or an updateof query data contained within the workbook, stores it in the local database, and makes it available tothe mobile user through the Mobile Sales/Service Application.
n It is possible to define user-specific variants of workbooks in BW. When such a workbook isrequested for a Mobile Client, the user-specific variant is generated and processed.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-21
SAP AG 2001
([DPSOH��6ROXWLRQ�:RUNERRN�LQ�0RELOH�6DOHV
n This is an example of how a Solution Workbook downloaded from BW would be displayed withinthe 0RELOH�6DOHV application.
n Such a workbook not only contains data, but also 9LVXDO�%DVLF��9%��FRGH�IRU�UHSUHVHQWLQJ�WKLVGDWD in one way or the other (e.g. as bar chart, pie chart etc.).
n The VB code contained in a given workbook is replicated to the Mobile Clients only once, whereasthe data updates are replicated to the Mobile Clients more frequently.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-22
SAP AG 2001
6ROXWLRQ:RUNERRN
4XHULHV•�&RQQHFW�%:�V\VWHPV•�&UHDWH�DQG�VFKHGXOH��UHTXHVWV�IRU�PRELOH�XVHUV•�0RQLWRU�GHOLYHU\
:RUNERRN�5HSOLFDWLRQ�$GPLQLVWUDWLRQ
n From within the Administration Console, all available %:�ZRUNERRNV�FDQ�EH�UHTXHVWHG for mobileusers and are then delivered to the corresponding 0RELOH�&OLHQWV. 3DWK�IURP�WKH�$GPLQLVWUDWLRQ&RQVROH��(QYLURQPHQW�→ 'LVSOD\�%:�6\VWHPV��%XWWRQ�Ä5XQ�5HTXHVWV³
n Regular updates of workbooks can be scheduled. These updates usually only refer to the query datacontained within the workbook, since the workbook itself (the framework) is already present on theMobile Client and need not be transferred again.
n The workbooks (based on publications like „BW Workbook Reports“ and „BW Query Reports“ haveto be subscribed by sites. Queries provide you different views of the data to be analyzed.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-23
SAP AG 2001
7KH�$6&,,�$GDSWHU��RSWLRQDO�
7KH�$6&,,�$GDSWHU�RSWLRQDO�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-24
SAP AG 2001
&50�6\VWHP2WKHU�6\VWHP
£4¤E¥A¦¨§¨©Mª ¤ ¦«©Nª ¤'¥¬¦¬§4¤L©4¥¦¨¤ ª'¥¨¦§4¤E¥4¦®§�ª ¤ ©4¥¨¦¤'¦§�ª ¤ ¦9ª ¤'¦A§�ª ¤E©@¥¦®§@¤'©Nª §©Nª ¤'¦§�ªL©�¤L¥A¦¨§¬©Nª ¤ ¥¨¦¬§$6&,,�)LOH
$6&,,�$GDSWHU���2YHUYLHZ
l 7KH�$6&,,�$GDSWHU�LV�D�GHYHORSPHQW�WRROl 6LPSOH�LPSRUW�RI�GDWD�LQWR�WKH�&50
V\VWHPl 1R�EXVLQHVV�ORJLF�LV�SURYLGHG
n The ASCII (American Standard Code for Information Interchange) Adapter is an interface for dataimport from H[WHUQDO�V\VWHPV that cannot provide XML Documents or IDocs. In this case theexternal systems can export their data in form of ASCII files, which are loaded into database tablesby the ASCII adapter. The database tables are then converted into synchronization BDoc messagesand a Synchronization Flow is started.
n There is no site of type ASCII in the Administration Console as the data export is not supported.However, (outgoing) XML messages may be mapped into ASCII files using external tools.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-25
SAP AG 2001
$6&,,$GDSWHU
�H[WHUQDO�SDUW� )ORZ&RQWURO ���
$6&,,�$GDSWHU��LQWHUQDO�SDUW�
V%'RF
£4¤E¥A¦¨§¬©Tª ¤ ¦¡©Mª ¤'¥¨¦A§A¤'©A¥¦¨¤ ª'¥¨¦A§A¤L¥A¦®§�ª ¤ ©4¥¬¦¤'¦§�ª ¤ ¦9ª ¤ ¦§�ª ¤E©4¥A¦¨§A¤ ©Nª §©Nª ¤'¦§�ª'©9¤'¥¦®§©Nª ¤'¥¦¬§$6&,,�)LOH
V%'RFV%'RF
7HPSRUDU\'DWDEDVH7DEOH
&50�0LGGOHZDUH
%'RF¶%'RF¶%'RF¶%'RF¶*HQHUDWRU
6WUXFWXUH0DSSHU
2YHUYLHZ�RI�'DWD�,PSRUW�DQG�0DSSLQJ
n Data import with the $6&,,�$GDSWHU involves two major steps:
é The external part of the ASCII Adapter handles the import of data from ASCII files on operatingsystem level to temporary database tables in the CRM database on the CRM Server that werecreated for this purpose. Each ASCII file is mapped to exactly one database table. Each line of theASCII file represents one database record.
é The internal part of the ASCII Adapter consists of two parts, the %'RF¶�*HQHUDWRU and the6WUXFWXUH�0DSSHU.
- The BDoc’ Generator reads data from the temporary database tables and converts it into aBDoc’ (temporary BDoc). This is necessary to group records of different temporary tables intoone single object (the BDoc’).
- The Structure Mapper converts the BDoc’ into a proper synchronization BDoc message byapplying mapping rules. The resulting synchronization BDoc messages are then passed to theFlow Control for regular processing.
n The internal part of the ASCII Adapter serves as the user interface for the ASCII Adapter. After allparameters and mapping instructions have been entered for a particular import scenario, the actualimport (and mapping) function modules are generated and then executed from here.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-26
SAP AG 2001
([WHUQDO6\VWHP
([WHUQDO'DWD
0DSSLQJ7RRO
$6&,,�$GDSWHU��LQWHUQDO�SDUW�
6WUXFWXUH�0DSSHU
3UH�0DSSLQJ&XVWRPHU
([LW
3RVW�0DSSLQJ&XVWRPHU
([LW
���
&50�0LGGOHZDUH
£A¤L¥A¦¨§¨©Nª ¤ ¦¡©Tª ¤'¥¨¦§4¤E©@¥¦®¤ ªL¥¬¦§4¤E¥A¦¨§�ª ¤ ©4¥¨¦¤'¦§�ª ¤ ¦9ª ¤'¦§�ª ¤L©4¥A¦®§4¤ ©Tª §©Tª ¤'¦§�ªL©�¤E¥A¦¨§©Nª ¤'¥¬¦¬§$6&,,�)LOH��� ���
%'RF¶ V%'RF
$GGLWLRQDO�'DWD�0DSSLQJ�3RVVLELOLWLHV
n The CRM Middleware and in particular the ASCII Adapter GR�QRW provide any business logic. Thevalidation of the imported data is performed in the CRM Adapter. To get the data to the CRMAdapter, the synchronization BDoc messages are passed to the Synchronization Flow, converted intomessage BDoc messages and then handed over to the CRM Adapter.
n Extra mapping or business rules can be applied on ASCII file level by using an external datamapping tool in producing the ASCII files for subsequent import.
n Customer exits are provided in the generated mapping function modules before and after the actualmapping takes place. These exits can also be used to apply additional mapping or data validation.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-27
SAP AG 2001
l 'HILQH�WHPSRUDU\�GDWDEDVH�WDEOH�V����RQH�SHU�ILOHl &UHDWH�VHWWLQJV�IRU�H[WHUQDO�WR�LQWHUQDO�PDSSLQJ�VWHS
¯ 3DUDPHWHU�WDEOHVl $GMXVW�H[WHUQDO�$6&,,�$GDSWHU�VHWWLQJV
¯ 3DUDPHWHU�ILOH�RQ�RSHUDWLQJ�V\VWHP�OHYHOl &UHDWH�VHWWLQJV�IRU�LQWHUQDO�WR�%'RF¶�PDSSLQJ�VWHS��$6&,�l 'HILQH�PDSSLQJ�IURP�%'RF¶�WR�%'RF��60$3�l 7ULJJHU�FRGH�JHQHUDWLRQ
¯ 0DSSLQJ�DQG�$6&,,�$GDSWHU�IXQFWLRQ�PRGXOHVl ([HFXWH�GDWD�LPSRUW�DQG�PRQLWRU
¯ )LUVW�H[WHUQDO��WKHQ�LQWHUQDO
1HFHVVDU\�6WHSV�IRU�'DWD�,PSRUW
n The steps outlined above are required for importing external data.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-28
SAP AG 2001
Smith John Sales assistent "3242453" 01. Jan 45Jones Deborah Sales manager "5562543" 06. Dez 56Cook James Sales assistent "6545344" 03. Mrz 68Taylor Frank Sales assistent "454543" 29. Feb 72Butler Robin Sales manager "464566" 04. Jan 61Cooper Keith District manager "4345778" 09. Okt 64
6DOHV�DVVLVWDQW�6PLWK�-RKQ������������-DQ����*%6DOHV�PDQDJHU�-RQHV�'HERUDK������������'H]����)56DOHV�DVVLVWDQW��&RRN�-DPHV�������������0U]����*%6DOHV�DVVLVWDQW��7D\ORU�)UDQN������������)HE����'(6DOHV�PDQDJHU��%XWOHU�5RELQ������������-DQ����*%'LVWULFW�PDQDJHU��&RRSHU�.HLWK�������������2NW����*%
&ROXPQ'URS
7\SH&RQYHUVLRQ
&ROXPQ5HDUUDQJHPHQW
&RPPD6HSDUDWHG�9DOXHVRU�)L[HG�/HQJWK
7UDQVSDUHQW�WDEOHGHILQHG�LQ�$%$3ZRUNEHQFK��H�J�
=&217$&7
([WHUQDO�WR�,QWHUQDO�0DSSLQJ
n After the temporary tables have been created using the ABAP workbench, the mapping of externalASCII data to the internal tables is specified in two parameter tables:
n Table 602�$6&$'é One entry per temporary table
é Assignment of external file name to target temporary table
é Used fields and decimal delimiters, formats, etc.
é Additional settings
é See the documentation for a complete description of possible settings.
n Table 602�$6&675é One entry per temporary table field
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-29
SAP AG 2001
$6&,,$GDSWHU
�H[WHUQDO�SDUW�&50
0LGGOHZDUH£A¤L¥A¦¨§¨©Nª ¤ ¦¡©Tª ¤'¥¨¦§4¤E©@¥¦®¤ ªL¥¬¦§4¤E¥A¦¨§�ª ¤ ©4¥¨¦¤'¦§�ª ¤ ¦9ª ¤'¦§�ª ¤L©4¥A¦®§4¤ ©Tª §©Tª ¤'¦§�ªL©�¤E¥A¦¨§©Nª ¤'¥¬¦¬§$6&,,�)LOH
([WHUQDO�$6&,,�$GDSWHU�6HWWLQJV
l ([WHUQDO�SDUDPHWHU�ILOH&�?3URJUDP�)LOHV?6$3�$*?$6&,,�$GDSWHU?SDUDP?&50$6&$'�3$5
l &RQWDLQV�VHWWLQJV�OLNH° VWUXFWXUH��QDPH�DQG�ORFDWLRQ�RI�LPSRUW�ILOH° GDWH�IRUPDW��GHOLPLWHU�YDOXHV��RWKHU�SDUDPHWHUV° FRQQHFWLRQ�WR�&50�6HUYHU�DQG�GDWDEDVH
n The external ASCII Adapter settings are contained in a parameter file kept at operating system level.
n This parameter file contains settings needed by the external part of the ASCII Adapter to
é read and interpret the data from the ASCII files.
é access the CRM Server and the underlying database directly (via the DBSL interface provided bythe SAP Basis system).
n The external part of the ASCII Adapter is invoked in command line mode once all internal settingsand mappings have been specified.
n The external part of the ASCII Adapter may be easily configured, tested and executed via the $6&,,$GDSWHU�&RQILJXUDWLRQ�7RRO.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-30
SAP AG 2001
l $VVLJQ�WHPSRUDU\�%'RF¶�QDPH�WR�UHSUHVHQW�LPSRUW�WDEOHV
l 6SHFLI\�%'RF¶¯ ,PSRUW�WDEOHV��NH\�ILHOGV��GHSHQGHQFLHV��KLHUDUFK\
l 6SHFLI\�WDUJHW�%'RF¯ %'RF�QDPH��PDS�QDPH��IURP�VWUXFWXUH�PDSSHU�
l *HQHUDWH�FRGLQJ¯ $)7(5�PDSSLQJ�KDV�EHHQ�JHQHUDWHG
%'RF¶��!�%'RF
%'RF¶�GHWDLOV
=35263(&7�����
VLQJOH�JHQHUDWLRQ
=&217$&7�����
,QWHUQDO�$6&,,�$GDSWHU�6HWWLQJV
n Choose transaction $6&, to invoke the ASCII Adapter user interface.
n An internal temporary name (BDoc’ name) is assigned to represent one or more temporary tables.This makes it possible to join data from several import files before mapping them to one targetBDoc.
n The BDoc’ details relate the temporary tables to the BDoc’ and also contain information aboutinterdependencies between several source tables (if applicable).
n A target BDoc type is specified from the list of existing BDoc types.
n A map name is assigned for later use by the 6WUXFWXUH�0DSSHU, where the actual field mappingfrom source tables to BDoc table fields takes place.
n Once all settings have been entered, and the structure mapping coding has been generated, thegeneration of the ASCII Adapter function module for the particular import scenario can be triggered.
n For more information about the internal ASCII Adapter settings refer to the SAP Library.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-31
SAP AG 2001
)RU�HDFK�PDS�QDPH�
6WUXFWXUH�0DSSHU
l (QWHU�PDSSLQJ�GHWDLOV¯ 6RXUFH��WHPSRUDU\��WDEOH�WR�WDUJHW�%'RF�WDEOH¯ ,QSXW�W\SH��PDS�RUGHU��DFWLYH�VWDWXV
l (QWHU�PDS�ILHOG�GHWDLOV¯ 6RXUFH�ILHOG�WR�WDUJHW�ILHOG¯ 0DSSLQJ�IXQFWLRQV��VWULQJ�IXQFWLRQV�¯ $VVLJQPHQW�RI�FRQVWDQW�YDOXHV¯ &RQGLWLRQV¯ $GGLWLRQDO�6HWWLQJV
l *HQHUDWH�PDSSLQJ�FRGH
n Choose transaction 60$3 to invoke the Structure Mapper user interface.
n In the Structure Mapper, the data mapping and conversion from the BDoc’ to the BDoc structures isspecified and the corresponding function modules are then generated.
n The user interface represents map data on several sheets with growing detail level.
n After having entered a map name on the first sheet, the mapping for this name on table level can bespecified on the subsequent sheet.
n By selecting a particular source and destination table on the 0DSSLQJ�GHWDLOV sheet and then going tothe 0DS�ILHOG�GHWDLOV sheet, individual data fields can be mapped from source to destination table. Itis possible to
é employ string functions like Substring, Concatenation, or Padding.
é assign constant values to destination fields.
é specify conditions for the mapping process.
n Once the mapping has been configured, the actual mapping code (function module) is generated.This is a precondition for generating the related ASCII Adapter function module.
n For more information about the internal ASCII Adapter settings refer to the SAP Library.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-32
SAP AG 2001
l 7ULJJHU�LPSRUW�LQWR�WHPSRUDU\�WDEOHV¯ &RPPDQG�OLQH�PRGH¯ H�J��µ&50$6&$'�FUPDVFDG�SDU�=35263(&7¶
l 6WDUW�PDSSLQJ�LQWR�%'RF�VWUXFWXUH¯ 7UDQVDFWLRQ�$6&,�
l 6WDUW�IORZ�SURFHVVLQJ�IURP�LQERXQG�TXHXHV��LI�QHFHVVDU\�¯ 7UDQVDFWLRQ�604���VWDUW�$6&,,�$GDSWHU�LQERXQG�TXHXH
WHPSRUDU\�WDEOHSDUDPHWHU�ILOH
GDWD�LPSRUW
'DWD�,PSRUW�([HFXWLRQ
n The steps outlined above are required for executing the data import.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 6-33
SAP AG 2001
<RX�DUH�QRZ�DEOH�WR�
'DWD�([FKDQJH�ZLWK�H[WHUQDO�6\VWHPV��6XPPDU\
l ([SODLQ�KRZ�;0/�DQG�,'RF�LQWHUIDFHV�FDQ�EHXVHG�IRU�GDWD�H[FKDQJH�ZLWK�QRQ�6$3�V\VWHPV
l ([SODLQ�WKH�PDMRU�VWHSV�QHFHVVDU\�WR�LPSRUWOHJDF\�GDWD�YLD�WKH�';�:RUNEHQFK
l 'HVFULEH�WKH�LQWHUDFWLRQ�EHWZHHQ�D�%XVLQHVV,QIRUPDWLRQ�:DUHKRXVH��%:��DQG�WKH�&500LGGOHZDUH
l 'HVFULEH�WKH�LPSRUW�RI�GDWD�LQ�IRUP�RI�$6&,,ILOHV�WR�WKH�&50�0LGGOHZDUH
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 7-1
SAP AG 2001
l %'RF�GHSHQGHQFLHVl 5HDOLJQPHQWl &RQVROLGDWHG�'DWDEDVH��&'%�
6SHFLDO�)HDWXUHV�IRU�0RELOH�6FHQDULRV
&RQWHQWV�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 7-2
SAP AG 2001
l 'HVFULEH�WKH�YDULRXV�SRVVLEOH�GHSHQGHQFLHVEHWZHHQ�V\QFKURQL]DWLRQ�%'RFV
l ([SODLQ�WKH�UHDOLJQPHQWl ([SODLQ�WKH�GDWD�PRGHO�XVHG�LQ�WKH
&RQVROLGDWHG�'DWDEDVH
$W�WKH�FRQFOXVLRQ�RI�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�
6SHFLDO�)HDWXUHV�IRU�0RELOH�6FHQDULRV��8QLW2EMHFWLYHV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 7-3
SAP AG 2001
&RXUVH�2YHUYLHZ�'LDJUDP
0LGGOHZDUH�2YHUYLHZ0LGGOHZDUH�2YHUYLHZ
&RQFHSWV�RI�WKH�&50�0LGGOHZDUH&RQFHSWV�RI�WKH�&50�0LGGOHZDUH
5HSOLFDWLRQ�$GPLQLVWUDWLRQ5HSOLFDWLRQ�$GPLQLVWUDWLRQ
0RQLWRULQJ��(UURU�+DQGOLQJ0RQLWRULQJ��(UURU�+DQGOLQJ
,QVWDOODWLRQ��&RQILJXUDWLRQ,QVWDOODWLRQ��&RQILJXUDWLRQ
6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ
'DWD�([FKDQJH�ZLWK�6$3�5��%DFN�(QGV'DWD�([FKDQJH�ZLWK�6$3�5��%DFN�(QGV
'DWD�([FKDQJH�ZLWK�RWKHU6\VWHPV'DWD�([FKDQJH�ZLWK�RWKHU6\VWHPV
)XUWKHU�,QIRUPDWLRQ)XUWKHU�,QIRUPDWLRQ
&RXUVH�:UDS�8S&RXUVH�:UDS�8S
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 7-4
SAP AG 2001
&RQWHQW�� 'HFRXSOLQJ�RI�PHVVDJLQJ�DQG
V\QFKURQL]DWLRQ� %'RF�GHSHQGHQFLHV� 5HDOLJQPHQW
w �0LQRU�UHDOLJQPHQW
w �0DMRU�UHDOLJQPHQW� 7KH�&RQVROLGDWHG�'DWDEDVH��&'%�
6SHFLDO�)HDWXUHV�IRU�PRELOH�6FHQDULRV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 7-5
SAP AG 2001
'HFRXSOLQJ�RI�0HVVDJLQJ�DQG�6\QFKURQL]DWLRQ
5���%DFN�(QG
1RQ�5���%DFN�(QG
6$3�%:
&50�6HUYHU
6\QFKURQL]DWLRQ�OD\HU0HVVDJLQJ�OD\HU
:HE�$SSOLFDWLRQ�6HUYHU
7KH�V\QFKURQL]DWLRQ�OD\HU�SURYLGHV�PRUHVRSKLVWLFDWHG�UHSOLFDWLRQ�VHUYLFHV
7ZR�LQWHJUDWLRQ�OD\HUV�� 0HVVDJLQJ� 6\QFKURQL]DWLRQ
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 7-6
SAP AG 2001
l ,QWHUOLQNDJHV�� 0RUH�IOH[LEOH�VFKHPH�WR�FRQVWLWXWH�IUHH
GHSHQGHQFLHV�EHWZHHQ�%'RFV�� 0D\�EH�F\FOLF�RU�UHIOH[LYH�
%'RF�'HSHQGHQFLHV��6\QFKURQL]DWLRQ�
l 'LUHFW�GHSHQGHQFLHV�� 'HSHQGHQW�UHSOLFDWLRQ�
%'RFV�IROORZ�RQO\�RQH�LQWHOOLJHQW�%'RF�� ,QWHOOLJHQW�GHSHQGHQW�UHSOLFDWLRQ�
%'RFV�PD\�IROORZ�PXOWLSOH�LQWHOOLJHQW�%'RFV�
n When replicating BDoc messages, dependencies between different BDoc types can be modeled.Dependencies only exist for LQWHOOLJHQW replication. Examples for an intelligent dependent replicationare sales documents that follow the corresponding customer, which means that sales documents arereplicated to the same sites as customers.
n There are two different types of dependencies:
é 'LUHFW�GHSHQGHQFLHV, where a BDoc message follows directly one or more other BDoc messages.In this case the parent BDoc messages are specified within the replication model.
é Indirect dependencies or ,QWHUOLQNDJHV, where multiple level of dependencies may be specified.For example a BDoc message $ depends on a BDoc message %, which itself depends on a thirdBDoc message &. In this case the CRM Middleware replicates the BDoc & to the same sites,where the BDoc messages $ and % are replicated to.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 7-7
SAP AG 2001
7KH�SURFHVV�RI�UHGLVWULEXWLQJ�GDWD�DFFRUGLQJ�WR�FKDQJHV� LQ�UHSOLFDWLRQ�UHOHYDQW�GDWD�ILHOGV��PLQRU�UHDOLJQPHQW�� WR�VXEVFULSWLRQ�UXOHV��PDMRU�UHDOLJQPHQW�
8SGDWLQJ�WKH�GDWDEDVHV�RQ�WKH�PRELOH�FOLHQWV0LQRU�PDMRU�UHDOLJQPHQW�LV�SHUIRUPHG�DXWRPDWLFDOO\
5HDOLJQPHQW��6\QFKURQL]DWLRQ�
0RELOH�&OLHQW 0RELOH�&OLHQW&50�6HUYHU
������������� ����
� ��� ������������� ����
n 5HDOLJQPHQW is a redistribution of data that ensures that all sites receive the data assigned to themthrough subscription. It has to ensure that the distributed local databases remain consistent with thestatus of the central Consolidated Database.
n A PLQRU realignment is triggered by FKDQJHV�WR�GDWD, i.e. when a value of a criteria field is changed.In this case deletion or update BDoc messages are replicated to the Mobile Clients.
n A PDMRU realignment is triggered by FKDQJHV�WR�VXEVFULSWLRQV, i.e. when creating or deletingsubscriptions. In this case the corresponding deletion or creation messages for the BDoc messagesbelonging to the subscriptions are replicated to the Mobile Clients.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 7-8
SAP AG 2001
��� ��������� ��! �������"�# �� $"%'&
68169Bill Miller
CRM Server=,3������WR������
=,3������WR������
=,3������WR������
��� ����"�(�� ��) �����"���� *� $�%+&
Bill Miller
��� ����"�(�� ��) �����"���� *� $�%+&
Bill Miller 68169 71259
�
�71259
��
�
��� ����"�"�� *�) �����"���� �� $�%,&
Bill Miller 71259
�
�
0LQRU�5HDOLJQPHQW��6\QFKURQL]DWLRQ�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 7-9
SAP AG 2001
-/.1020-#3*020-#4*020-5�020-#6*020-#7*020
'HOHWH6XEVFULSWLRQ
'HOHWH6XEVFULSWLRQ
(QWHU6XEVFULSWLRQ
(QWHU6XEVFULSWLRQ
-�.8020-�3�020-�4�020-�59020-�6�020-�7�020
0DMRU�5HDOLJQPHQW��6\QFKURQL]DWLRQ�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 7-10
SAP AG 2001
l :K\�DQ�DGGLWLRQDO��ORJLFDO��GDWDEDVH"
l :KDW�GRHV�WKH�&'%�FRQWDLQ"
7KH�&RQVROLGDWHG�'DWDEDVH��&'%��6\QFKURQL]DWLRQ�
&'%
&506HUYHUGDWD
5��GDWD
&50�PRELOHGDWD
$GYDQWDJHV�•�FHQWUDO�EDFNXS��UHFRYHU\•�UHDOLJQPHQW•�FRQIOLFW�UHVROXWLRQ•�SHUIRUPDQFH
&OLHQW��
&OLHQW��
&OLHQW�Q
n The data for mobile clients is kept in a separate cache on the CRM Server for performance andreplication reasons. The cache is called the &RQVROLGDWHG�'DWDEDVH��&'%�. From the technical pointof view the Consolidated Database is just a set of tables within the CRM Database.
n The data model for mobile clients is lighter than the CRM Server Application data model. Hence, adata conversion is necessary. The CDB contains the already converted data. Further more the cacheis required for delta data calculations, so that the messages send to mobile clients only contain themodified fields. This reduces the data send to mobile client. Also complex replication scenarioscontaining dependencies and data redistribution (realignment) can only be efficiently supportedusing the CDB.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 7-11
SAP AG 2001
'DWD�0RGHOV�LQ�P\6$3�&50
&50�6HUYHU
0RELOH�&OLHQWV
0DSSLQJ
'DWD�
'DWD�
&50�6HUYHU�$SSOLFDWLRQ�'DWD�0RGHO
&50�0RELOH�$SSOLFDWLRQ�'DWD�0RGHO
'LIIHUHQWEXVLQHVV��WHFKQLFDO
UHTXLUHPHQWV
n There are GLIIHUHQFHV�LQ�WKH�GDWD�PRGHOV�RI�5���%DFN�(QGV��WKH�&50�'DWDEDVH�DQG�WKH�&'%.
é The CDB data model partly corresponds to the R/3 Data Dictionary (DDIC). This is especially thecase for sales documents and the product master. It has been optimized for the use for MobileApplications.
é Other business objects of Mobile Applications such as business partners, activities, opportunities,campaigns, target lists and so on have their own structures or structures similar to CRM ServerApplications.
é Special CRM data, e.g. activity or opportunity data, is only kept in the CDB and not in thedatabase of the SAP R/3 Back-End.
n Data must therefore be PDSSHG before or during loads between the CRM Server Applications andexternal systems.
n The CRM Mobile Application data model is QRW a 1:1 copy of the CRM Server Application datamodel.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 7-12
SAP AG 2001
.H\V�LQ�&50��*8,'V�
l $GYDQWDJHV�RI�RZQ�NH\�V\VWHP�LQ�PRELOH�VFHQDULRV�� *OREDO�8QLTXH�,'HQWLILHUV��*8,'��DUH�XQLTXH�LQ�WKH�ZRUOG�GXH�WR
JHQHUDWLRQ�PHWKRG� 1R�QXPEHU�UDQJH�LQWHUYDOV�RI�5���NH\V�DUH�QHHGHG� *8,'�LV�D�WHFKQLFDO�NH\�DQG�FRQWHQW�IUHH� &DQ�EH�XVHG�WR�PRGHO�UHODWLRQV�EHWZHHQ�REMHFWV
l 'LIILFXOW\��5���%DFN�(QG�GRHV�QRW�NQRZ�&50�NH\V��*8,'V�
7DEOH .1$�.H\ .XQQU��&KDU����
7DEOH 602.1$�.H\ 6)$.1$���&KDU�����*8,'�
)LHOG .XQQU��&KDU����
&50�0LGGOHZDUH���0RELOH�&RPSRQHQWV5���%DFN�(QG
�&XVWRPHU�0DVWHU�'DWD�
n *8,'V��*OREDOO\�8QLTXH�,GHQWLILHUV� serve as primary keys for all tables in the CDB. A GUID isgenerated by a special algorithm using as input data certain hardware information of the hostcomputer, the current system time, and a randomly generated number. The GUID can be representedin two formats: a 32-byte character field or a 16-byte raw sequence. It is globally unique in the sensethat two GUIDs produced on any two computers (or even on the same one) at any time can never bethe same.
n 3ULPDU\�NH\V of all tables are called 6)$�WDEOH�QDPH�ZLWKRXW�WKH�602�SUHIL[!, such as SFAKNA1,SFAMARA.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 7-13
SAP AG 2001
&50�6HUYHU
&50�6HUYHU�$SSOLFDWLRQ%87����.H\� 3$571(5)LHOG�3$571(5B*8,'&500B%87B&86712.H\� 3$571(5B*8,')LHOG�&86720(5B12
&'%602.1$�.H\� 6)$.1$�)LHOG�.8115
6$3�5���%DFN�(QG
.1$�
.H\� .8115
l ([DPSOH�&XVWRPHU
&RUUHVSRQGHQFH��&50�6HUYHU�$SSOLFDWLRQ�±�&'%���5��
n The slide shows the relationship of key fields for customer tables. The main customer table on theSAP R/3 Back-End is the KNA1 with the customer number (KUNNR) as the key field. Thecorresponding CDB table is the SMOKNA1 with the GUID (SFAKNA1) as the key. The fieldKUNNR is an ordinary table field. The main table for customers in CRM Server Applications is theBUTØØØ table with the key field PARTNER. The R/3 customer number is kept in the fieldCUSTOMER_NO in the table CRMM_BUT_CUSTNO. The link between this table and the tableBUTØØØ can be established via the field PARTNER_GUID.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 7-14
SAP AG 2001
<RX�DUH�QRZ�DEOH�WR�
6SHFLDO�)HDWXUHV�IRU�0RELOH�6FHQDULRV��6XPPDU\
l 'HVFULEH�WKH�YDULRXV�SRVVLEOH�GHSHQGHQFLHVEHWZHHQ�V\QFKURQL]DWLRQ�%'RFV
l ([SODLQ�WKH�UHDOLJQPHQWl ([SODLQ�WKH�GDWD�PRGHO�XVHG�LQ�WKH
&RQVROLGDWHG�'DWDEDVH
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-1
SAP AG 2001
l *HQHUDO�&50�0LGGOHZDUH�0RQLWRULQJl 6WDWLVWLF�0RQLWRUVl 0HVVDJH�7UDFNLQJ�DQG�(UURU�+DQGOLQJ
0RQLWRULQJ��(UURU�+DQGOLQJ
&RQWHQWV�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-2
SAP AG 2001
l ([SODLQ�WKH�YDULRXV�PRQLWRULQJSRVVLELOLWLHV
l 8VH�WKH�VWDWLVWLF�PRQLWRUl 3HUIRUP�PRQLWRULQJ�WR�GHWHFW�HUURUVl &RQILJXUH�WKH�&HQWUDO�(UURU�+DQGOHU
$W�WKH�FRQFOXVLRQ�RI�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�
0RQLWRULQJ��(UURU�+DQGOLQJ��8QLW�2EMHFWLYHV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-3
SAP AG 2001
&RXUVH�2YHUYLHZ�'LDJUDP
0LGGOHZDUH�2YHUYLHZ0LGGOHZDUH�2YHUYLHZ
&RQFHSWV�RI�WKH�&50�0LGGOHZDUH&RQFHSWV�RI�WKH�&50�0LGGOHZDUH
5HSOLFDWLRQ�$GPLQLVWUDWLRQ5HSOLFDWLRQ�$GPLQLVWUDWLRQ
0RQLWRULQJ��(UURU�+DQGOLQJ0RQLWRULQJ��(UURU�+DQGOLQJ
,QVWDOODWLRQ��&RQILJXUDWLRQ,QVWDOODWLRQ��&RQILJXUDWLRQ
6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ
'DWD�([FKDQJH�ZLWK�6$3�5��%DFN�(QGV'DWD�([FKDQJH�ZLWK�6$3�5��%DFN�(QGV
'DWD�([FKDQJH�ZLWK�RWKHU6\VWHPV'DWD�([FKDQJH�ZLWK�RWKHU6\VWHPV
)XUWKHU�,QIRUPDWLRQ)XUWKHU�,QIRUPDWLRQ
&RXUVH�:UDS�8S&RXUVH�:UDS�8S
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-4
SAP AG 2001
$FWLRQV'HWHFWHGHUURUV
8QGHWHFWHGHUURUV
3UHYHQWLRQE\�UHJXODU�PRQLWRULQJ
(�J��PHVVDJHWR�V\VWHP
DGPLQLVWUDWRU
6WDQGDUG5���WRROV
8VH�RISURFHVVLQJPRQLWRUV
$XWRPDWLFDOO\JHQHUDWHG
&RPSXWLQJ�&HQWHU�
0DQDJHPHQW�6\VWHP
� 0LGGOHZDUH�3RUWDO� 'LVSOD\�%'RF�0HVVDJHV� 0RQLWRULQJ�RI�TXHXHG�5)&� 0LGGOHZDUH�7UDFH� 5)&�ORJ�ILOHV
6WUDWHJ\�RI�0RQLWRULQJ�DQG�(UURU�+DQGOLQJ
n *HQHUDO�VWUDWHJ\� In error handling two strategies principally exist: either errors inform the user orerrors remain undetected and only will be discovered by regular monitoring. Different levels ofmonitoring exist: technical communication between systems, inside a system and information onindividual message level (BDoc status and content).
n The CRM Middleware offers full &RPSXWLQJ�&HQWHU�0DQDJHPHQW�6\VWHP��&&06� integration aswell as flow traces and qRFC queue monitors in order to track messages.
n The modular architecture of the CRM Middleware allows a FHQWUDO�HUURU�KDQGOLQJ� where eachservice or adapter can return error messages or codes to the overall flow. Depending on these codes,different error actions can be triggered, leading to a resolution of the problem.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-5
SAP AG 2001
l *HQHUDO�2YHUYLHZ�� &&06�,QWHJUDWLRQ� 0LGGOHZDUH�3RUWDO� %'RF�PHVVDJH�GLVSOD\
l 6WDWLVWLFV�� .HUQHO�VWDWLVWLFV���IORZ�VWDWLVWLFV
l 7HFKQLFDO�GHWDLOV� 0LGGOHZDUH�7UDFH� )XUWKHU�PRQLWRUV� 6WDQGDUG�5���7RROV� &HQWUDO�(UURU�+DQGOLQJ
0RQLWRUV���2YHUYLHZ
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-6
SAP AG 2001
*HQHUDO�2YHUYLHZ
*HQHUDO�2YHUYLHZ
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-7
SAP AG 2001
&&06�PRQLWRU�VWUXFWXUH�RI�WKH�&50�0LGGOHZDUH
&&06�,QWHJUDWLRQ
&50�6HUYHU
&RPPXQLFDWLRQ6WDWLRQ
�%'RF�VWDWXV�4XHXH�,QIRUPDWLRQ
�6$3�5���2XWERXQG�TXHXHV��T5)&��&50�,Q��2XWERXQG�TXHXHV��T5)&��&50�5HSO���5HDOLJQPHQW�TXHXHV
�&RPPXQLFDWLRQ�6WDWLRQ�VWDWXV
n For more information on how to activate the CRM Middleware alert monitoring refer to OSS note437187.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-8
SAP AG 2001
� $OHUW��LI�WKHUH�LV�D�%'RF�PHVVDJH�ZLWK�DQ�HUURU�VWDWXV� $OHUW��LI�%'RF�PHVVDJHV�ZDLW�WR�ORQJ�IRU�DQ�DQVZHU�IURP�5��
� $OHUW�IRU�TXHXH�JURXSV�LQ�FDVH�RI�HUURUV� $OHUW�IRU�TXHXH�JURXSV��LI�WKHUH�DUH�PDQ\�HQWULHV�LQ�WKH�RXWERXQGTXHXHV
� $OHUW��LI�WKHUH�LV�DQ�HUURU�ZLWK�WKH�TXHXH�VFKHGXOHU� $OHUW��LI�TXHXHV�DUH�QRW�UHJLVWHUHG
&&06�$OHUWV�,
�%'RF�VWDWXV
�5�����&50�TXHXHV��T5)&�
�&50�,QERXQG�TXHXHV��T5)&���LQ�DGGLWLRQ�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-9
SAP AG 2001
� $OHUW��LI�WKH�TXHXH�GHPRQ�LV�VWRSSHG� $OHUW��LI�TXHXHV�DUH�RQ�KROG� $OHUW��LI�WKH�QXPEHU�RI�TXHXH�HQWULHV�H[FHHG�D�WKUHVKROG
� $OHUW��LI�D�&RPPXQLFDWLRQ�6WDWLRQ�LV�XQUHDFKDEOH� $OHUW��LI�LPSRUWDQW�SURFHVVHV�DUH�QRW�UXQQLQJ� $OHUW��LI�WKHUH�LV�DQ�HUURU�LQ�WKH�/RJ
&&06�$OHUWV�,,
�&50�5HSO���5HDOLJQPHQW�TXHXHV
�&RPPXQLFDWLRQ�6WDWLRQ�VWDWXV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-10
SAP AG 2001
&50�0LGGOHZDUH�3RUWDO
n�*HQHUDWLRQu %'RF�W\SH��VWUXFWXUHVu �%'RF�W\SH��RWKHU�UXQWLPH
REMHFWVu �5HSOLFDWLRQ�REMHFWVu �3XEOLFDWLRQVu �0LVVLQJ�GDWDEDVH�LQGLFHVu �*HQHUDWLRQ�RI�IORZ
GHILQLWLRQVn�5XQWLPH�LQIRUPDWLRQ
u 5���$GDSWHU�VWDWXVLQIRUPDWLRQ
u �55��TXHXH�GHPRQu �%'RFV�LQ�WKH�IORZ
n The CRM Middleware Portal may be accessed via the menu:0LGGOHZDUH�→�0RQLWRULQJ�→�&HQWUDO�0RQLWRULQJ�→�0LGGOHZDUH�3RUWDO��60:3��
n In order to view the most up-to-date information it is necessary to schedule two backgroundprocesses:
é SMWP_BATCH – to update the displayed runtime information and
é SMWP_GE_BATCH – to update the generation (= design time) information.
n The reason to update the runtime and design time information via two separate batch processes isthat the runtime information needs to be updated more frequently (maybe every hour) than the designtime information (maybe once a day).
n The two background processes may be scheduled either via
é the CRM Middleware Portal →�%XWWRQ�6FKHGXOH�%DFNJURXQG�-RE or via
é the transaction SM36 →�%XWWRQ�-RE�:L]DUG.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-11
SAP AG 2001
6WHS�RQH��VHOHFW�D�%'RF�PHVVDJH
'LVSOD\�%'RF�0HVVDJHV��,�
6HOHFW�D�%'RFPHVVDJH
'LVSOD\�0:7UDFH
3URFHVVLQJ�VWDWHRI�D�%'RF
)ORZ�&RQWH[W�RID�%'RF
'LVSOD\�WKHFODVVLFDO�SDUW
'LVSOD\�WKHGDWD�SDUW
�
�
'LVSOD\�WKH(UURUV
n The transaction to for the Middleware Trace can be found under:0LGGOHZDUH�→�0RQLWRULQJ�→�0HVVDJH�)ORZ�→�'LVSOD\�%'RF�0HVVDJHV��60:��).
n The function Ä'LVSOD\�%'RF�0HVVDJHV³ lists all BDoc messages. It displays:
é The BDoc ID and BDoc type, the BDoc state, the flow context, the queue name, the date and timewhen the BDoc message was sent.
é The flow trace, the data and error segments, the service, in which the error occurred (last servicereached), the recipient list.
é The link between synchronization and messaging BDoc messages, e.g.CAPGEN_OBJECT_WRITE, CUST_HIERARCHY and BUPA_MAIN.
n Successfully processed messages appear with a green light, those still in process with a yellow light,and those with a terminal error condition with a red light.
n If a message is in process and does not get processed within a reasonable amount of time, it ispossible to restart the message, view the message content, or discard the message. A BDoc messagemay be processed in one of the following ways:
é Mark as deleted (note that deleting BDoc messages can cause data inconsistencies)
é Retry processing (note that this can course data inconsistencies, since other BDoc messagestransporting the same instance may already have gone through the system).
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-12
SAP AG 2001
l 'LVSOD\�%'RF�0HVVDJHV�SURYLGHV�LQIRUPDWLRQ�RQ�� %'RF�PHVVDJH�LGHQWLILHU��%'RF�QXPEHU�� %'RF�VWDWH� )ORZ�&RQWH[W� %'RF�GDWD
�FODVVLFDO�SDUW�H[WHQVLRQ�SDUW�
� %'RF�6HJPHQW�WUHH
'LVSOD\�%'RF�0HVVDJHV��,,�
n The function 'LVSOD\�%'RF�0HVVDJHV allows to display individual BDoc messages and allows toview their content.
n There is also an overview function: →�'LVSOD\�%'RF�0HVVDJH�6XPPDU\�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-13
SAP AG 2001
6WDWLVWLFV
6WDWLVWLFV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-14
SAP AG 2001
�0LGGOHZDUH
.HUQHO
0HVVDJH�)ORZ�6WDWLVWLFV
%'RF�W\SH&38�7LPH 'DWDEDVH�7LPH
5HVSRQVH�7LPH
%'RF%'RF%'RF
%'RF
%'RF
:DLW�7LPH
,QERXQG�SURFHVVLQJ
� �
2XWERXQG�SURFHVVLQJ
5���NHUQHO�DSSOLFDWLRQ�VWDWLVWLFV
6WDWLVWLF�PRQLWRU�IRU�%'RF�W\SHV��VLWHV�DQG�TXHXHV
n The message flow statistics monitor is launched via:0LGGOHZDUH�→�0RQLWRULQJ�→�0HVVDJH�)ORZ�→�'LVSOD\�0HVVDJH�)ORZ�6WDWLVWLFV��60:0)/2:��
n The 5���NHUQHO�DSSOLFDWLRQ�VWDWLVWLF�PRQLWRU requires that the standard CCMS batch jobs aredefined.
n In order to activate the statistic monitor, choose *RWR�→�$FWLYDWH�6WDWLVWLFV��+HUH�WKH�.HUQHODSSOLFDWLRQ�VWDWLVWLFV�DQG�WKH�0LGGOHZDUH�PHVVDJH�IORZ�VWDWLVWLFV can be activated individually.Further information on how to active the monitors can be found in the SAP Library.
n The time to process BDoc messages in the CRM Middleware can be displayed using the VWDWLVWLFPRQLWRU�IRU�%'RF�W\SHV��VLWHV�DQG�TXHXHV. This monitor shows the total execution time for a BDocmessage, which consists of the time it was waiting in an inbound queue plus the processing time. Theprocessing time is the sum of the time the BDoc spend in the Inbound Adapter and in the two Flows.This monitor displays either the average execution time for all BDoc messages of one type or theexecution time for only one single BDoc message.
n The kernel application statistics monitor provides the CPU time and the database time that was usedto process all BDoc messages of a BDoc type. The response time includes the CPU time and thedatabase time. Note that the database time also includes some CPU time, so that these two times notnecessarily sum up to the response time (compare SAP note 351207). It is also possible to displaythe executed times for the various services that were called with the selected BDoc type by pressingthe 3HU�VHUYLFH button.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-15
SAP AG 2001
,QERXQG�3URFHVVLQJ0RELOH�&OLHQW 5���$GDSWHU ([WHUQDO
6LWH4XHXH
��0HVJ�)ORZ&50�6HUYLFH9DOLGDWLRQ
&RPPLW�ZRUN
2XWERXQGSURFHVVLQJ
��6\QF�)ORZ,QERXQG$GDSWHU0DSSLQJ
��0HVJ�)ORZ5���$GDSWHU
0DSSLQJ
��0HVJ�)ORZ;,)�$GDSWHU
0DSSLQJ
5���,QE�4XHXH
([WHUQDO4XHXH4XHXH�WLPH
,QERXQG$GDSWHUWLPH
0DSSLQJWLPH
0HVVDJH)ORZ
SURFHVVLQJWLPH
7RWDOSURFHVVLQJ
WLPH
n The tap ”BDoc type” shows the processing time sorted by BDoc types, whereas the tab “Site type”displays the processing times for each site separately.
n Based on the decoupling of the Messaging and the Synchronization Flow, PHVVDJH�SURFHVVLQJ�LVGLYLGHG into two asynchronous steps, which run not necessarily on the same application server.,QERXQG processing is therefore distinguished from RXWERXQG processing for monitoring messageflows.
n The display of the VWDWLVWLFV�RQ�SURFHVVLQJ�DQG�TXHXLQJ�WLPHV provides you with summarizedvalues from the database on individual BDoc types, sites and queues. You can display the workloadeither as a total or how it is distributed on the individual application servers.
n Within the selected time period (day or week) you can display the load distribution of BDocs using atime profile. The day view also displays individual records that the statistics are based on.
n The tap ”BDoc type” shows the processing time sorted by BDoc types, whereas the tab “Site type”displays the processing times for each site separately.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-16
SAP AG 2001
2XWERXQG�3URFHVVLQJ
0RELOH�&OLHQW
5��
([WHUQDO
4XHXH
��0HVJ�)ORZ6LPSOH
5HSOLFDWLRQ
0RELOH%ULGJH
2XWERXQG$GDSWHU
&RPPLW�ZRUN
��6\QF�)ORZ&'%
2XWERXQG$GDSWHU
5HSOLFDWLRQ
0DSSLQJ
0DSSLQJ
4XHXH�WLPH
0HVVDJH)ORZ
SURFHVVLQJWLPH
6\QF�)ORZSURFHVVLQJWLPH��DOOV%'RF
PHVVDJHV�
7RWDOSURFHVVLQJ
WLPH
«
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-17
SAP AG 2001
7HFKQLFDO�'HWDLOV
7HFKQLFDO�'HWDLOV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-18
SAP AG 2001
&50�$GDSWHU
T5)&�,QERXQG
��������� �������������������� �����! ��#"%$�'&(�)�*�! ��
+-,/.�0-1����324���
5�6�7984: ;=<?>/@�: A'BDC E-5FEGBGC : H9IJ84: 6F;LK
+�,/.M0-1����32N���
OQPSRM0-1����32N���
�' �T��U ���*�V 1�������W& �X�*�Y ��#"%$����(������ �� 5(EDB�C : HZIZ8N: 6(;Z[
5(E\I�C : <F;LA�EG;\8
]�^�_ @ EG` a3: H9E
b 7\8dc=6F7�;\e-f�eDIGBZ8SEG`
O�PSR�0-1����324���
ghE9iji=I9<(: ;=<'kGC 6Ll
@3m3;9HDnG`S6F;�: ojI\8d: 6(;WkDC 69l
@�m3;LHDnD`%63;�: oJI98N: 6(;pkGC 6Ll
T5)&�,QERXQGT5)&�,QERXQG
T5)&�2XWERXQGT5)&�2XWERXQG
T5)&�2XWERXQG
,QERXQG�DQG2XWERXQG�4XHXH
0RQLWRULQJ
'LVSOD\�%'RF0HVVDJHV�
0LGGOHZDUH�7UDFH
5HSOLFDWLRQ�5HDOLJQPHQW
4XHXHV
0HVVDJH�7UDFNLQJ���2YHUYLHZ
n This slide gives an overview on message tracking facilities in a CRM System. In this course theCRM Server tools and the R/3 tools are discussed. The course CR540 – CRM Middleware forMobile Scenarios covers the mobile scenario relevant monitoring, such as the Replication andRealignment queues, the monitoring of the Mobile Clients and the Communication Station.
n This unit presents the following tools:
é The function 'LVSOD\�%'RF�0HVVDJHV �0LGGOHZDUH�→�0RQLWRULQJ�→�0HVVDJH�)ORZ�→�'LVSOD\%'RF�0HVVDJHV��60:����
é The function 0LGGOHZDUH�7UDFH �0LGGOHZDUH�→�0RQLWRULQJ�→�0HVVDJH�)ORZ�→�'LVSOD\0LGGOHZDUH�7UDFH��60:7��
é ,QERXQG�DQG�RXWERXQG�TXHXH�PRQLWRULQJ �0LGGOHZDUH�→�0RQLWRULQJ�→�4XHXHV�→�'LVSOD\2XWERXQG�4XHXHV��604���DQG�0LGGOHZDUH�→�0RQLWRULQJ�→�4XHXHV�→�'LVSOD\�,QERXQG�4XHXHV�604���
n 5HSOLFDWLRQ��5HDOLJQPHQW�TXHXH�PRQLWRULQJ �0LGGOHZDUH�→�0RQLWRULQJ�→�4XHXHV�→�0RQLWRU55�4XHXHV��602+48(8(����LV�FRYHUHG�LQ�WKH�FRXUVH�&5����±�&50�0LGGOHZDUH�IRU�0RELOH6FHQDULRV�
n The monitoring of the tRFC connections �0LGGOHZDUH�→�0RQLWRULQJ�→�7UDQVDFWLRQDO�5)&�→'LVSOD\�7UDQVDFWLRQDO�5)&�5HTXHVWV��60���� is a standard transaction to examine tRFC problems.
n The Data Loads with R/3 Back-Ends can be monitored Initial Load monitor �0LGGOHZDUH�→0RQLWRULQJ�→�'DWD�([FKDQJH�→�0RQLWRU�2EMHFWV��5�$0����
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-19
SAP AG 2001
0LGGOHZDUH�7UDFH
6HOHFW�WKHREMHFW
�
'LVSOD\�WKHGHWDLOV
�
6WHS�WZR��GLVSOD\�IORZ�GHWDLOV�IRU�D�%'RF�0HVVDJH
n From the transaction Display BDoc Messages you can access the 0LGGOHZDUH�7UDFH.
n An alternative path is to the middleware trace with additional information is:0LGGOHZDUH�→�0RQLWRULQJ�→�0HVVDJH�)ORZ�→�'LVSOD\�0LGGOHZDUH�7UDFH��60:7��
n Note: You need to perform settings in the table SMOFPARSFA (via the parameter TRACE-LEVEL)in order to use the function Display Middleware Trace. Please see the SAP Library.
n The Ä'LVSOD\�%'RF�0HVVDJH�6XPPDU\³ function lists the same BDocs as „Display BDocMessages“ but grouped according to site, message type (E, A, W, S. I) and BDoc type.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-20
SAP AG 2001
&OLHQW
���������
4XHXH�1DPH
���&50B6,7(B�������������
'HVWLQDWLRQ
���&50B6,7(B��������������
(QWULHV
��������
���
&O�
���
4XHXH�1DPH
&50B6,7(B����������
���'DWH
��������
6WDWXV
1RVHQG
���
���
���7LPH
����
1[W'DWH
��������
1[W7LP
����
&O�
���������
)XQFWLRQ�0RGXOH
FOLHQWBHPSOR\HHBZULWHFOLHQWBHPSOR\HHBZULWH���
8VHU
&211B06$B06(&211B06$B06(���
7LPH
�����������
'DWH
�������������������
���
���������
l 1RUPDO�FRQGLWLRQ��QR�HUURU�HQWULHV�LQ�DQ\�TXHXHV
,QERXQG�DQG�2XWERXQG�4XHXH�0RQLWRULQJ
n The consistency of all distributed data and processes is guaranteed even if individual components ofthe integrated system are temporarily unavailable. All calls and data transports take placeasynchronously via buffers (TXHXHV). This ensures that if individual components can not be accessed,no information is lost and no delays occur in the overall schedule. There are inbound and outboundqueues.
n qRFC queues are displayed in three steps:
é After specifying one or more clients, queue names and queue destinations, the transaction SMQ1or SMQ2 displays a list of all queues that match the specified values.
é Now it is possible to select particular queues of interest and view further details.
é From the detailed view on the selected queues, it is possible to display the queue entries bydouble-clicking the corresponding queue.
n System paths:0LGGOHZDUH�→�0RQLWRULQJ�→�4XHXHV�→�'LVSOD\�2XWERXQG�4XHXHV��604��0LGGOHZDUH�→�0RQLWRULQJ�→�4XHXHV�→�'LVSOD\�,QERXQG�4XHXHV��604���
n The same qRFC outbound queue monitoring used on the CRM Server can also be employed on theR/3 Back-End.
n If an object is not processed correctly within the R/3 Back-End, and an error condition is notreturned via BAPI parameters, the R/3 Back-End itself has to be checked.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-21
SAP AG 2001
&O�
���������
6WDWXV
,1$&7,9(,1$&7,9(
���
/DVW�6FKHGXOHU�8SGDWH
�����������������������������������
2OGHVW�4XHXH
&50B6,7(B��������&50B6,7(B�����������
2OG��6W�
67236723���
���
���������
4XHXH�ZLWK�WKHROGHVW�HQWU\
l 'LVSOD\�VWDWXV�RI�T5)&�VFKHGXOHU�IRU�DOO�&50�FOLHQWV
7KH�6WDQGDUG�4XHXH�6FKHGXOHU
n The Scheduler is used for the processing of LQERXQG�TXHXHV�n The scheduler as well as the R/3 queues (queue name „R3A*“ ) need to be DFWLYDWHG. This is
automatically done by the system when an Initial Load is started.
n Display the status of the T5)&�VWDQGDUG�VFKHGXOHU for all CRM clients via0LGGOHZDUH�→�0RQLWRULQJ�→�4XHXHV�→�'LVSOD\�T5)&�6FKHGXOHU�,QIRUPDWLRQ�60:06&+('8/(5��The number of entries in the queues together with the corresponding time stamps are displayed.
n The Replication & Realignment queues used for the realignment calculations are no qRFC queues.Thus, these queues are not displayed here. For more information about the Replication &Realignment queue consult the course &5������&50�0LGGOHZDUH�IRU�0RELOH�6FHQDULRV�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-22
SAP AG 2001
7UDQVDFWLRQDO�5)&��W5)&��0RQLWRULQJ
)XQFWLRQ�0RGXOH
VZHBHYHQWBORJBZULWHVPR�BIORZBUHVWDUW���
&DOOHU
7UDLQLQJ&50���
7LPH
�����������
'DWH
�������������������
���
���������
'HWDLOHGDQDO\VLV
6WDWXV�WH[W
7UDQVDFWLRQ�UHFRUGHG��/8:)LHOG�V\PERO�KDV�QRW�\HW�EH���
1RUPDO�FRQGLWLRQ��QR�HUURU�HQWULHV����������������������������������6WDWXV�WH[W��7UDQVDFWLRQ�H[HFXWLQJ�
n The tRFC monitor may be accessed via the menu:0LGGOHZDUH��!�0RQLWRULQJ��!�7UDQVDFWLRQDO�5)&��!�'LVSOD\�7UDQVDFWLRQDO�5)&�5HTXHVWV��60����
n Executing transaction SM58 generates a selection screen, on which you can select the display period,user name, function, destination and status of transactional RFCs. Almost any combination (single ormultiple values, ranges and exclusions) of these parameters is possible.
n If a system or application exception is raised during the processing of a tRFC Logical Unit of Work(LUW), the target system returns this error back to the sending system. The status of this LUW isupdated with the exception error message (red background color of status message).
n You obtain information about the caller, function module, target system, date, time and status text(see slide). Additionally, you obtain information about the transaction ID, host, current transactioncode, program, client, and number of attempts to establish the connection.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-23
SAP AG 2001
6WDQGDUG�5���0RQLWRULQJ�7RROV
1R��RI�GXPSV�
�7RGD\���<HVWHUGD\
��
qsr(�32�rF�����F��F�(1�t
u/u�uqsr(�32�����M�� Qvw1� �t
u/u�ux��y�4 Q����F��U �F&� &
u/u�uu/u�u
6\VWHP�ORJ�
)URP�GDWH���WLPH ���7R�GDWH���WLPH ���
8VHU� ������5HDGLQJ�1XPEHU�RI�UHFRUGV�UHDG�����������
6KRUW�GXPS�DQDO\VLV
9LHZLQJ�V\VWHP�ORJV
n The ABAP short dump analysis may be called via transaction ST22.
n The system log may also provide important information to find errors in the system. The system logis viewed via transaction SM21.
n For further information refer to standard R/3 Back-End administration courses, e.g. SAPTEC.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-24
SAP AG 2001
,QWHJUDWLRQ�RI�WKH�&HQWUDO�(UURU�+DQGOLQJ�6HUYLFH
6HUYLFH��
6HUYLFH��
6HUYLFH��
$FWLRQV
:RUNIORZ0DLOV�6KRUW�GXPS�����
&(6
,QERXQG
)ORZ&RQWURO
6HUYLFHV�PD\UHWXUQ�DQ�HUURU
VWDWXV
&HQWUDO�(UURU+DQGOLQJ�6HUYLFHSHUIRUPV�HUURU
DFWLRQV
n The &HQWUDO�(UURU�+DQGOLQJ�6HUYLFH��&(6� is started by the Flow Control after receiving internalor external error conditions, e.g. if a service returns the error code E. Errors can be grouped intotechnical errors (e.g. connection errors) and validation errors (result of the CRM service).
n Each service uses the CES for error handling. The Error Handler starts an error action specified inthe error handling definitions. This action is generally asynchronous and may require userinteraction. Error actions can cause a restart of the processing flow with the previous service, thetermination of the flow, or the start of other processing logic.
n The central unit of all error information is the HUURU�VHJPHQW, which is part of all BDoc messagesand contains, e.g., the message type, the service return code and the last service.
n Depending on the error segment information, the CES starts error actions. It performs the erroraction that are specified for a message. Most HUURU�DFWLRQV are pre-defined by SAP. You can changethe assignment of error actions to individual messages and restore the SAP standard settings anytime. You can also define your own error action as an ABAP function module. Error actions can beassigned to message types (BDoc types), services and sender sites.
n The transaction for configuring the error handling may be found at:0LGGOHZDUH�→ 0HVVDJH�)ORZ�→ (UURU�+DQGOHU�6HWWLQJV��60:����
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-25
SAP AG 2001
(UURU�+DQGOLQJ�ZLWKLQ�WKH�)ORZ�&RQWURO
6HUYLFH�L
(UURU
6HUYLFH�L��
No
(UURU�+DQGOHU (UURU�$FWLRQVYes
"""
0DLO
:RUN)ORZ
�'HWHUPLQHV�DQGSHUIRUPV�SRVVLEOH
HUURU�DFWLRQV
n By definition, an error has occurred when a service returns an $ or ( in the field MSGTY of thestandard interface parameter BAPIRET2 DQG there is no subsequent service specified in the FlowDefinition for this particular situation.
n Error actions can cause a restart of the processing flow with the previous service, the termination ofthe flow, or the start of other processing logic.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-26
SAP AG 2001
3RVVLEOH�(UURU�$FWLRQV
:RUNIORZ�HYHQW��(9(17�6HQG�PDLO��0$,/�6WDUW�FXVWRPHU�IXQFWLRQ��&867�5HWU\�ODVW�VHUYLFH��5(75<�
n EVENT: A standard event is preconfigured and appears by default in the inbox of all CRMMiddleware users. When the event is executed, you can view the message and decide what to dowith it, i.e.:
é delete the message
é resume the message
é resume processing with the next service
n MAIL: An e-mail message is sent to a specified user. This e-mail may contain the BDoc messageand processing information.
n CUST: Any customer function module may be called. The interface of the customer function mustbe defined as shown in the sample function module SMW_ERR_CUST_SAMPLE. The flowcontinuation mode is determined by the value of the RESOLUTION parameter.
n RETRY: The last service (the one which returned the error) is retried up to ten times in intervals of 5seconds. This can help in case of temporary problems (e.g. database access or network problems). Ifretrying the last service is successful, no other error actions are executed.
n The transaction for configuring the error handling may be found at:0LGGOHZDUH�→�0HVVDJH�)ORZ�→�(UURU�+DQGOHU�6HWWLQJV��60:����
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-27
SAP AG 2001
&RPPXQLFDWLRQ6WDWLRQ
5��&50�0LGGOHZDUH
&RQQHFWLRQ�IDLOXUH�PD\�EH�FDXVHG�E\z WKH�JDWHZD\�QRW�EHLQJ�VWDUWHGz WKH�WDUJHW�V\VWHP�QRW�EHLQJ�DFWLYHz LQFRUUHFW�RU�LQFRPSOHWH�HQWULHV�LQ�WKH�5)&�GHVWLQDWLRQz V\VWHP�RYHUORDG
&DXVHV�DQG�6RXUFHV�RI�&RQQHFWLRQ�(UURUV
n In case of connection errors FKHFN�WKH�IROORZLQJ�é Check all parameters for the RFC destination. Do all the parameters match the settings of the
target system?
é Is the hostname correct?
é Is the service/system number correct?
é Is the user/password set correctly?
é Is the target system active?
é Did you save the destination?
é Make sure that the target machine can be addressed by the host on which the gateway process isrunning.
é Check that the gateway processes are running on both systems.
é Check the network connection.
n For further information refer to SAP notes 169550, 351887 and 372202.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-28
SAP AG 2001
([DPSOH��'HOWD�/RDG�&50�6HUYHU�WR�5���%DFN�(QGl &KHFN�'LVSOD\�%'RF�0HVVDJHVl &KHFN�WKH�RXWERXQG�TXHXH�RI�WKH�&50�6HUYHUl &KHFN�WKH�RXWERXQG�TXHXH�RI�WKH�5���%DFN�(QGl &KHFN�WKH�LQERXQG�TXHXH�RI�WKH�&50�6\VWHP
&DXVHV�DQG�6RXUFHV�RI�/RDG�(UURUV
5���%DFN�(QG
6WDWXV,QIRUPDWLRQ
&50�6HUYHU2XWERXQG4XHXH
'HOWD/RDG
,QERXQG�4XHXH 2XWERXQG4XHXH
'DWD�/RDG�WR$SSOLFDWLRQ
P%'RF
� �
��
�
n Possible error situation: a business object has been changed in a CRM Server Application, but thechange (Delta Load) is not received in the R/3 Back-End.
n In case of Load errors FKHFN�WKH�IROORZLQJ�é Check Display BDoc Messages including the error segments, middleware trace information and
the message contents.
é Check the outbound queue
é Check the outbound queue of the R/3 Back-End
é Check the inbound queue of the CRM System
n Furthermore, verify the RFC destination and the logical system assigned to your site (in theAdminstration Console) and the CRM Middleware parameter settings in the CRM System and theR/3 Back-End (e.g. CRMRFCPAR, see also unit ,QVWDOODWLRQ�DQG�&RQILJXUDWLRQ).
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-29
SAP AG 2001
<RX�DUH�QRZ�DEOH�WR�
0RQLWRULQJ��(UURU�+DQGOLQJ��6XPPDU\
l ([SODLQ�WKH�YDULRXV�PRQLWRULQJSRVVLELOLWLHV
l 8VH�WKH�VWDWLVWLF�PRQLWRUl 3HUIRUP�PRQLWRULQJ�WR�GHWHFW�HUURUVl &RQILJXUH�WKH�&HQWUDO�(UURU�+DQGOHU
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-30
([HUFLVHV
8QLW� 0RQLWRULQJ��(UURU�+DQGOLQJ7RSLF� 0RQLWRULQJ�RI�'DWD�/RDGV
At the conclusion of this exercise, you will be able to:
• Monitoring data loads
Monitoring data exchanges is an important task. A CRM Middlewareadministrator should know how to monitor and track down individualBDoc messages in order to find the potential sources for errors.
1-1 Creating a new business partner
1-1-1 Examine the CRM System and the R/3 System whether a business partnerwith your name exists.
The path in the SAP R/3 System is
/RJLVWLFV�→�6DOHV�DQG�'LVWULEXWLRQ�→�0DVWHU�'DWD�→�%XVLQHVV�3DUWQHUV→�&XVWRPHUV�→�'LVSOD\�→�6DOHV�DQG�'LVWULEXWLRQ��WUDQVDFWLRQ�9'����The path to view business partner in the CRM Server is
0DVWHU�'DWD�→�%XVLQHVV�3DUWQHU�→�0DLQWDLQ�%XVLQHVV�3DUWQHU�WUDQVDFWLRQ�%3��
1-1-2 Create a business partner (person) with the role “ Sold-To Party” on theCRM Server. If you receive a pop-up, confirm with &UHDWH.
7DE�5LGHU )LHOG 9DOXHTitle 0U��RU�0V�First name <RXU�FKRLFHLast name <RXU�FKRLFHLanguage (QPostal Code �����City $WODQWLF�&LW\Country 86
Address
Transportation Zone ����������Central Data Correspondance
language(Q
Please write down the number of your business partner.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-31
1-1-3 Check if the business partner was loaded into the SAP R/3 System.
2-1 Check whether the corresponding BDoc message was processed properly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-32
6ROXWLRQV
8QLW� 0RQLWRULQJ��(UURU�+DQGOLQJ7RSLF� 0RQLWRULQJ�RI�'DWD�/RDGV
1-1 Creating a new business partner
1-1-1 Create a business partner (person) with the role “ Sold-To Party” on theCRM Server. If you receive a pop-up, confirm with &UHDWH.
7DE�5LGHU )LHOG 9DOXHTitle 0U��RU�0V�First name <RXU�FKRLFHLast name <RXU�FKRLFHLanguage (QPostal Code �����City $WODQWLF�&LW\Country 86
Address
TransportationZone
����������
Central Data Correspondancelanguage
(Q
The transaction to maintain business partner in the CRM Server may be accessed via
0DVWHU�GDWD��!�%XVLQHVV�3DUWQHU��!�0DLQWDLQ�%XVLQHVV�3DUWQHU��WUDQVDFWLRQ�%3��Please write down the number of your business partner.
2-1 Check whether the corresponding BDoc message was processed properly.
� Start the function “ Display BDoc Messages”
� Select your business partner.
� Examine the following data:• the BDoc header
• the extension data
• the receivers of the message.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 8-33
:KDW�KDSSHQG�The change is not displayed as the inbound processing has been interrupted. Theinstructor has deactivated the standard RFC scheduler via
0LGGOHZDUH�→�$GPLQLVWUDWLRQ�→�5HJLVWHU�'HUHJLVWHU�4XHXHV��WUDQVDFWLRQ�6045�.Since the inbound processing has not yet taken place, you may view the relevantinbound queue (open a new session).0LGGOHZDUH�→�0RQLWRULQJ�→�4XHXHV�→�'LVSOD\�,QERXQG�5)&�4XHXHV��WUDQVDFWLRQ604���The queue name is 5�$'B&86720(����[[[[[[ (xxxxxx stands for your customernumber). Queue names are controlled by the CRM Server Applications. As the CRMMiddleware has not processed the data yet, the conversion from the BAPI structuresinto a BDoc has not taken place.
You may view the data as follows:0LGGOHZDUH�→�0RQLWRULQJ�→�4XHXHV�→�'LVSOD\�,QERXQG�5)&�4XHXHV��WUDQVDFWLRQ604���Mark the queue line, press button 'LVSOD\�VHOHFWLRQ, mark the line, press button&KRRVH, press button 'LVSOD\�/8:. The Logical Unit of Work (LUW) contains thedata in a BAPI structure. You’ll find your P.O. Box number by using the Findbutton. Enter your P.O. Box number with a blank between the digits.
After the instructor has registered (activated) the standard RFC scheduler again,verify if your change can be displayed in the CRM System.
0DVWHU�GDWD�→�%XVLQHVV�3DUWQHU�→�0DLQWDLQ�%XVLQHVV�3DUWQHU��WUDQVDFWLRQ�%3��
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 9-1
SAP AG 2001
l 6\VWHP�ODQGVFDSH�DQG�LWV�VFDODELOLW\l 2YHUYLHZ�RI�WKH�VRIWZDUH�LQVWDOODWLRQ�SURFHGXUHl &RQILJXULQJ�QHWZRUN�FRQQHFWLRQVl )XUWKHU�LQIRUPDWLRQ
,QVWDOODWLRQ�DQG�&RQILJXUDWLRQ
&RQWHQWV�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 9-2
SAP AG 2001
l 'HVFULEH�WKH�VRIWZDUH�LQVWDOODWLRQ�SURFHGXUHl &RQILJXUH�WKH�PDMRU�QHWZRUN�FRQQHFWLRQV
EHWZHHQ�WKH�YDULRXV�PLGGOHZDUH�FRPSRQHQWV
$W�WKH�FRQFOXVLRQ�RI�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�
,QVWDOODWLRQ�DQG�&RQILJXUDWLRQ��8QLW�2EMHFWLYHV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 9-3
SAP AG 2001
&RXUVH�2YHUYLHZ�'LDJUDP
0LGGOHZDUH�2YHUYLHZ0LGGOHZDUH�2YHUYLHZ
&RQFHSWV�RI�WKH�&50�0LGGOHZDUH&RQFHSWV�RI�WKH�&50�0LGGOHZDUH
5HSOLFDWLRQ�$GPLQLVWUDWLRQ5HSOLFDWLRQ�$GPLQLVWUDWLRQ
0RQLWRULQJ��(UURU�+DQGOLQJ0RQLWRULQJ��(UURU�+DQGOLQJ
,QVWDOODWLRQ��&RQILJXUDWLRQ,QVWDOODWLRQ��&RQILJXUDWLRQ
6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ
'DWD�([FKDQJH�ZLWK�6$3�5��%DFN�(QGV'DWD�([FKDQJH�ZLWK�6$3�5��%DFN�(QGV
'DWD�([FKDQJH�ZLWK�QRQ�6$35���%DFN�(QGV'DWD�([FKDQJH�ZLWK�QRQ�6$35���%DFN�(QGV
)XUWKHU�,QIRUPDWLRQ)XUWKHU�,QIRUPDWLRQ
&RXUVH�:UDS�8S&RXUVH�:UDS�8S
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 9-4
SAP AG 2001
� ������������ ������ �������������
5���%DFN�(QG&50�6HUYHU��
&50�0LGGOHZDUH
� � �"!#�$�%�'&���(*)) ��� +,�-�.� �/�-0
� � �"!1!2� 33/� �- *�%���� 45�%6 (*)�) �7� +,�8�9� �/�����'&��%�
� � ( �5:��<;=!�>�/���8�8+?���@�
� !BA�DC�!2� +%���E0��%�� �
&RPPXQLFDWLRQ6WDWLRQ
F &50�0RELOH�$SSOLFDWLRQF &RQQHFWLRQ�+DQGOHU
0RELOH�&OLHQWV
&RPSRQHQWV�RI�D�P\6$3�&50�6ROXWLRQ
n A mySAP CRM solution may comprise an SAP R/3 Back-End, the CRM Server and – in case of amobile scenario - the Communication Station and several Mobile Clients. Please note that both theinstallation and configuration of the Communication Station and Mobile Clients are covered in thecourse &5����±�&50�0LGGOHZDUH�IRU�PRELOH�VFHQDULRV�
n The CRM Server consists of the SAP Web Application Server, the CRM Server Applications and theCRM Middleware.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 9-5
SAP AG 2001
7KH�,QVWDOODWLRQ�RI�WKH�&50�0LGGOHZDUH
7LPH
:LQGRZV����17��.
06�64/�'%
0RELOH�6DOHV��6HUYLFH�$SSOLFDWLRQ
0RELOH�6DOHV��6HUYLFH�$SSOLFDWLRQ
0RELOH&OLHQW
+RW�3DFNDJHV+RW�3DFNDJHV
3OXJ�,Q3OXJ�,Q
5���%DFN�(QG
2SHUDWLQJ�6\VWHP
'DWDEDVH�6\VWHP
&50�6HUYHU�&50�0LGGOHZDUH�
&50�6HUYHU�&50�0LGGOHZDUH�
&50�6HUYHU�
&50�6HUYHU���&50�0LGGOHZDUH
7KLUG�SDUW\�VRIWZDUH6$3�5���%DFN�(QG
6RIWZDUH�SDFNDJHV�
:LQGRZV�17��.
�076��'&20�&&
7UDQVIHU&RPSRQHQWV7UDQVIHU
&RPSRQHQWV
&RPP�6WDWLRQ
n This is an overview of a typical installation of CRM Middleware relevant components. Note thatthere is no additional installation on the CRM Server for the CRM Middleware required!
n For more information refer to the 6$3�&50�6HWXS�DQG�/RDG�*XLGH� which provides a step-by-stepguide to install the CRM Server. The 6$3�&50�6HWXS�DQG�/RDG�*XLGH can be accessed via theSAPNet, alias: LQVWJXLGHV.
n Detailed information about the required hot package level on the SAP R/3 Back-End can be found inthe Plug-in area in the SAPNet, alias: r3-plug-in.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 9-6
SAP AG 2001
&RQQHFWLRQ��&50�0LGGOHZDUH�±�6$3�5���%DFN�(QG
0RELOH�&OLHQWV
&RPPXQLFDWLRQ6WDWLRQ
&50�0LGGOHZDUH
5���%DFN�(QG
7&3�,31HWZRUN
5)&YLD�'&20�&&�076
5)& 5)&
n Firstly, the connection between the SAP R/3 Back-End and the CRM Middleware has to be set up.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 9-7
SAP AG 2001
5)&
5)&�'HVWLQDWLRQ&OLHQW8VHU3DVVZRUG
�5�������&50�
&50�6HUYHU5)&�'HVWLQDWLRQ&OLHQW8VHU3DVVZRUG
�&50�����&50�
5���%DFN�(QG
l &UHDWH�WKH�5)&�GHVWLQDWLRQV�RQ�HDFK�V\VWHPVl 6HW�WKH�5)&�GHVWLQDWLRQ�DV�WKH�GHIDXOW�GHVWLQDWLRQ�RQ�ERWK
V\VWHPVl 2Q�WKH�5���%DFN�(QG��PDLQWDLQ�WDEOH�&505)&3$5l 2Q�WKH�&50�6HUYHU��FUHDWH�6LWH�RI�W\SH�5��
l 0DLQWDLQ�D�ORJLFDO�V\VWHP�RQ�HDFK�V\VWHP
&RPPXQLFDWLRQ��&50�0LGGOHZDUH���6$3�5���%DFN�(QG
n &UHDWH�WKH�5)&�GHVWLQDWLRQV of all systems (CRM System, SAP R/3 Back-End(s):
é RFC destinations are maintained via: ,0*�→�&XVWRPHU�5HODWLRQVKLS�0DQDJHPHQW�→�&500LGGOHZDUH�DQG�5HODWHG�&RPSRQHQWV�→�&RPPXQLFDWLRQ�6HWXS�→�'HILQH�5)&�GHVWLQDWLRQV(transaction SM59). An RFC destination, which has already been assigned to an existing SAP R/3Back-End, should not be changed.
é A CPI-C user (Common Programming Interface for communication) provides a higher level ofsecurity, since it can not be used to logon to an SAP R/3 Back-End as a dialog user. This user willbe used for SAP Support Dialog Users.
é In addition, you need to define a logical system for the client on the SAP R/3 Back-End using thecustomizing transaction SALE for ALE settings. However, ALE is not used for data exchangebetween the SAP R/3 Back-End and the CRM Middleware.
n 0DLQWDLQ�WKH�5)&�GHVWLQDWLRQ�RI�WKH�SDUWQHU�V\VWHP�é The RFC destination of the CRM System must be specified in the table CRMRFCPAR in the SAP
R/3 Back-End (Plug-In 2001.1 and later releases). Use the transaction SM30.
é When a Site of type R/3 is created with the Administration Console on the CRM Server, anexisting R/3 RFC destination may be entered. The logical system is assigned automatically.
n For more information please refer to the 6$3�&50�6HWXS�DQG�/RDG�*XLGH�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 9-8
SAP AG 2001
&RQQHFWLRQ��0RELOH�&OLHQW���&50�0LGGOHZDUH
0RELOH�&OLHQWV
&RPPXQLFDWLRQ6WDWLRQ
&50�0LGGOHZDUH
7&3�,31HWZRUN
5)&YLD�'&20�&&�076
5)& 5)&
5���%DFN�(QG
n The following slide explains the connection between Mobile Clients and the CRM Middleware viathe Communication Station.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 9-9
SAP AG 2001
&20�2EMHFWV�DV�&RPPXQLFDWLRQ�,QWHUIDFHV
T5)&'&20&DOOV
0RELOH&OLHQW
!��,0-0����%�=A����%�80-����$�%�'&�� +8�
&RPPXQLFDWLRQ�������6WDWLRQ
076�'&20�&&
&20�2EMHFWA@����-0-������$����G8H
&500LGGOHZDUH
I �6E�/���3J�;��-�K6��/�L��3( 3%� ) �'��
$%$3
7KH�0HVVDJH�7UDQVIHU�6HUYLFH�FDOOV�PHWKRGV�RI�D�&20�REMHFWRQ�WKH�&RPPXQLFDWLRQ�6WDWLRQ7KH�7UDQVIHU�3UR[\�WUDQVODWHV�&20�IXQFWLRQ�FDOOV�LQWR�T5)&IXQFWLRQ�FDOOV7KH�'&20�DQG�T5)&�IXQFWLRQ�FDOOV�FRQWDLQ�V\QFKURQL]DWLRQ%'RF�PHVVDJHV
n Connection between
é 6$3 components (written in ABAP or ABAP Objects) and
é &20 components (written in VB, Java, C++, Cobol, Delphi, etc.)
n &RPSRQHQW�2EMHFW�0RGHO��&20� is an open architecture for cross-platform development ofclient/server applications based on object-oriented programming. The applications and systems mayeven be supplied by different vendors. This technology supports development in variousprogramming languages. With the COM technology, clients have access to an object throughinterfaces implemented on that object. COM is language-independent, so that any language thatproduces ActiveX components can also produce COM applications.
n 'LVWULEXWHG�&20��'&20� enables COM software components to communicate directly over anetwork, e.g. between a mobile client and the CRM Middleware.
n The '&20�&RPSRQHQW�&RQQHFWRU��'&20�&&� runtime environment offers a general interfaceto call the remote function modules used in this context.
n The 0LFURVRIW�7UDQVDFWLRQ�6HUYHU��076� serves as a transaction processor over distributedsystems. It efficiently supports connection pooling and increases network security by providing anauthentication system.
n As soon as the connection between the client and the object on the server side is established (viaMTS and DCOM CC), the various methods of an object can be called.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 9-10
SAP AG 2001
&RQQHFWLRQ��&RPPXQLFDWLRQ�6WDWLRQ���0LGGOHZDUH
&RPPXQLFDWLRQ6WDWLRQ
&50�0LGGOHZDUH
Connection
MessageTransfer
7KH�FRQQHFWLRQ�M 076�VHFXULW\�VHWWLQJVM &UHDWH�DQ�5)&�GHVWLQDWLRQ��'&20�&&�M &RQQHFWLRQ�FKHFN�
n The set up of the connection between the Communication Station and the CRM Middleware involvesthe following steps:
é The MTS security settings have to be specified. This specifies the authentication level and dataencryption between the mobile client and the Communication Station.
é An RFC destination has to be defined for the DCOM Component Connector on theCommunication Station.
é The communication between the Communication Station and the Middleware can be tested usingthe program QmtCheck.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 9-11
SAP AG 2001
&RQQHFWLRQ��0RELOH�&OLHQW���&RPPXQLFDWLRQ�6WDWLRQ
0RELOH�&OLHQWV
&RPPXQLFDWLRQ6WDWLRQ
&50�0LGGOHZDUH
7&3�,31HWZRUN
5)&YLD�'&20�&&�076
5)& 5)&
5���%DFN�(QG
n The configuration of the RFC connection between the Mobile Clients and the CommunicationStation may be performed by the program ‘ASiteID’, which requires that the Users and the MobileClients are already known on the CRM Middleware. The User and Sites Administration on the CRMMiddleware will be discussed in the course &5����±�&50�0LGGOHZDUH�IRU�PRELOH�VFHQDULRV.
n At this stage it is sufficient to provide an ordinary TCP/IP connection to the Communication Station.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 9-12
SAP AG 2001
l *HQHUDWLRQ�RI�UXQWLPH�REMHFWV
���������&50�0LGGOHZDUH
%'RF
0HWD�/HYHO�2EMHFWV� )XQFWLRQ0RGXOHV)XQFWLRQ*URXSV'',&
2EMHFWV
5XQWLPH�2EMHFWV�
%'RF %'RF
%'RF
)XUWKHU�,QIRUPDWLRQ��*HQHUDWLQJ�WKH�&500LGGOHZDUH
n The CRM Middleware distinguishes between two different types of objects: meta level objects andruntime objects. Meta level objects only contain the definitions, such as the names and datastructures of the objects. To be able to process such meta level objects, R/3 runtime objects areneeded, such as function modules, function groups and DDIC objects. These runtime objects can begenerated from the meta level data by the CRM Middleware.
n The slide shows BDoc types as an example of meta level objects.
n All tools for runtime generation may be found under 0LGGOHZDUH�→��'HYHORSPHQW�→�*HQHUDWLRQ�Note that developer authorizations are required to generate runtime objects.
n For more information about meta level objects and runtime objects, refer to the course &5����±(QKDQFLQJ�WKH�&50�0LGGOHZDUH�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 9-13
SAP AG 2001
l %'RF�7\SHV�DUH�FOLHQW�LQGHSHQGHQW�L�H��RQO\�RQH�%'RF�W\SH�SRVVLEOH
l ,QGXVWU\�WHPSODWHV�DUH�FOLHQW�LQGHSHQGHQWL�H��RQO\�RQH�YHUVLRQ�RI�D�WHPSODWH�SRVVLEOH
l 'LIIHUHQW�FOLHQWV�PD\�XVH�GLIIHUHQW�LQGXVWU\WHPSODWHV
l 6XEVFULSWLRQV�DQG�6LWHV�DUH�FOLHQW�GHSHQGHQW�
���������&50�6HUYHU
&OLHQW����
3+
3+
&$3
)XUWKHU�,QIRUPDWLRQ��0XOWLSOH�&50�&OLHQWV
&OLHQW����&OLHQW����&OLHQW����
&*
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 9-14
SAP AG 2001
T5)&M $OZD\V�XVH�WKH�ODWHVW�T5)&�YHUVLRQM *HQHUDO�T5)&�GHVFULSWLRQ��6$3�QRWH�������
5���3OXJ�,QM ,V�WKH�5���3OXJ�,Q�XS�WR�GDWH"M 5���UHOHDVH�VXSSRUWHG"M ,QVWDOO�WKH�ODWHVW�YHUVLRQM 6$31HW��DOLDV��U��SOXJ�LQ
)XUWKHU�,QIRUPDWLRQ��8VHIXO�266�1RWHV��,�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 9-15
SAP AG 2001
5���$GDSWHUM *HQHUDO�5���$GDSWHU�LQIRUPDWLRQ��6$3�QRWH�������M *HQHUDO�HUURU�DQDO\VLV��������M $QDO\VLV�±�,QLWLDO�/RDG��������M $QDO\VLV�±�'HOWD�/RDG�5����!�&50��������M $QDO\VLV�±�'HOWD�/RDG�&50��!�5����������M 'DWD�H[FKDQJH�SHUIRUPDQFH�EHWZHHQ�5���DQG�&50��������
,QVWDOODWLRQ���*HQHUDWLRQM ,QVWDOODWLRQ�SRVW�SURFHVVLQJ��������M 8SJUDGH�SRVW�SURFHVVLQJ��������
)XUWKHU�,QIRUPDWLRQ��8VHIXO�266�1RWHV��,,�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 9-16
SAP AG 2001
<RX�DUH�QRZ�DEOH�WR�
,QVWDOODWLRQ�DQG�&RQILJXUDWLRQ��6XPPDU\
l 'HVFULEH�WKH�VRIWZDUH�LQVWDOODWLRQ�SURFHGXUHl &RQILJXUH�WKH�PDMRU�QHWZRUN�FRQQHFWLRQV
EHWZHHQ�WKH�YDULRXV�PLGGOHZDUH�FRPSRQHQWV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 10-1
SAP AG 2001
l 5HOHYDQW�FRXUVHVl 6$31HWl ,0*
)XUWKHU�,QIRUPDWLRQ
&RQWHQWV�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 10-2
SAP AG 2001
&RXUVH�2YHUYLHZ�'LDJUDP
0LGGOHZDUH�2YHUYLHZ0LGGOHZDUH�2YHUYLHZ
&RQFHSWV�RI�WKH�&50�0LGGOHZDUH&RQFHSWV�RI�WKH�&50�0LGGOHZDUH
5HSOLFDWLRQ�$GPLQLVWUDWLRQ5HSOLFDWLRQ�$GPLQLVWUDWLRQ
0RQLWRULQJ��(UURU�+DQGOLQJ0RQLWRULQJ��(UURU�+DQGOLQJ
,QVWDOODWLRQ��&RQILJXUDWLRQ,QVWDOODWLRQ��&RQILJXUDWLRQ
6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ
'DWD�([FKDQJH�ZLWK�6$3�5��6\VWHPV'DWD�([FKDQJH�ZLWK�6$3�5��6\VWHPV
'DWD�([FKDQJH�ZLWK�QRQ�6$35���6\VWHPV'DWD�([FKDQJH�ZLWK�QRQ�6$35���6\VWHPV
)XUWKHU�,QIRUPDWLRQ)XUWKHU�,QIRUPDWLRQ
&RXUVH�:UDS�8S&RXUVH�:UDS�8S
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 10-3
SAP AG 2001
&5����&50�0LGGOHZDUH�IRU�0RELOH�6FHQDULRV� &RQQHFWLQJ�PRELOH�FOLHQWV�WR�WKH�&50�0LGGOHZDUH� $GPLQLVWHU�PRELOH�VFHQDULRV� 5HSOLFDWLRQ�PRGHOLQJ� 2EMHFW�GHSHQGHQFLHV
&5����0RGLILFDWLRQV�LQ�WKH�&50�0LGGOHZDUH� %'RF�PRGHOLQJ� 5���$GDSWHU�FXVWRPL]LQJ� ;,)�$GDSWHU�FXVWRPL]LQJ� ([FKDQJH�RI�PRGLILHG�EXVLQHVV�REMHFWV�ZLWK�WKH
6$3�5���V\VWHP
)XUWKHU�&50�0LGGOHZDUH�&RXUVHV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 10-4
SAP AG 2001
2WKHU�UHOHYDQW�&RXUVHV
&5������� 0RELOH�$SSOLFDWLRQ�6WXGLR%,7��� %XVLQHVV�,QWHJUDWLRQ�7HFKQRORJ\%,7��� ,QWHJUDWLRQ�7HFKQRORJ\�$/(%&��� 5)&%&��� 'DWD�0LJUDWLRQ&5��� %:�,QWHJUDWLRQ:'($/� :RUNLQJ�ZLWK�&&06��RQ�'HPDQG�
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 10-5
SAP AG 2001
)XUWKHU�,QIRUPDWLRQ�,6$31HW�$OLDVHVl �FUP�PZ &50�0LGGOHZDUH
l �LQVWJXLGHV ,QVWDOODWLRQ�DQG�8SJUDGH�*XLGHV��LQFO��6HWXS�DQG�'RZQORDG�*XLGH
l �QRWHV 6$3�266�1RWHV�VHDUFK
l �VL]LQJ &50�KDUGZDUH�UHTXLUHPHQWV��0HGLD�&HQWHU��!�/LWHUDWXUH
l �SODWIRUPV 3ODWIRUP�DQG�7HFKQRORJ\�,QIRUPDWLRQ�&HQWHU
l �U��SOXJ�LQ &50�3OXJ,Q
l �GHYHORSPHQWQHZV
l �UHOHDVHQRWHV
l �WUDLQLQJ ,QIRUPDWLRQ�DERXW�FRXUVHV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 10-6
SAP AG 2001
)XUWKHU�,QIRUPDWLRQ�,,
.QRZOHGJH�:DUHKRXVH��6$3�/LEUDU\��
,0*l�7UDQVDFWLRQ�FRGH�6352��
�→�&XVWRPHU�5HODWLRQVKLS�0DQDJHPHQW� →�&50�0LGGOHZDUH�DQG�5HODWHG�&RPSRQHQWV
l��+HOS�3RUWDO����KWWS���KHOS�VDS�FRP���mySAP.com Cross Industry Solutions, mySAP CRM
l��+HOS�→�6$3�/LEUDU\�CRM/BBP → Basis Technology → CRM Middleware
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 11-1
SAP AG 2001
&RXUVH�:UDS�8S��2YHUYLHZ�'LDJUDP
0LGGOHZDUH�2YHUYLHZ0LGGOHZDUH�2YHUYLHZ
&RQFHSWV�RI�WKH�&50�0LGGOHZDUH&RQFHSWV�RI�WKH�&50�0LGGOHZDUH
5HSOLFDWLRQ�$GPLQLVWUDWLRQ5HSOLFDWLRQ�$GPLQLVWUDWLRQ
0RQLWRULQJ��(UURU�+DQGOLQJ0RQLWRULQJ��(UURU�+DQGOLQJ
,QVWDOODWLRQ��&RQILJXUDWLRQ,QVWDOODWLRQ��&RQILJXUDWLRQ
6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV6SHFLDO�)HDWXUHV�IRU�PRELOH6FHQDULRV&RXUVH�2YHUYLHZ&RXUVH�2YHUYLHZ
'DWD�([FKDQJH�ZLWK�6$3�5��6\VWHPV'DWD�([FKDQJH�ZLWK�6$3�5��6\VWHPV
'DWD�([FKDQJH�ZLWK�QRQ�6$35���6\VWHPV'DWD�([FKDQJH�ZLWK�QRQ�6$35���6\VWHPV
)XUWKHU�,QIRUPDWLRQ)XUWKHU�,QIRUPDWLRQ
&RXUVH�:UDS�8S&RXUVH�:UDS�8S
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 11-2
SAP AG 2002
3UHIDFH
&RXUVH�:UDS�8S
Unit 1 &RXUVH�2YHUYLHZUnit 2 0LGGOHZDUH�2YHUYLHZUnit 3 &RQFHSWV�RI�WKH�&50�0LGGOHZDUHUnit 4 5HSOLFDWLRQ�$GPLQLVWUDWLRQUnit 5 'DWD�([FKDQJH�ZLWK�6$3�5���6\VWHPVUnit 6 'DWD�([FKDQJH�ZLWK�QRQ�6$3�5���6\VWHPVUnit 7 6SHFLDO�)HDWXUHV�IRU�PRELOH�6FHQDULRVUnit 8 0RQLWRULQJ��(UURU�+DQGOLQJUnit 9 ,QVWDOODWLRQ��&RQILJXUDWLRQUnit 10 )XUWKHU�,QIRUPDWLRQUnit 11 &RXUVH�:UDS�8S
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 11-3
SAP AG 2001
<RX�DUH�QRZ�DEOH�WR�
&RXUVH�2EMHFWLYHV
l ([SODLQ�WKH�EDVLF�FRQFHSWV�RI�WKH�&50�0LGGOHZDUHl 6HW�XS�DQG�FRQWURO�WKH�GDWD�H[FKDQJH�EHWZHHQ�WKH
&50�6HUYHU�DQG�DQ�5���V\VWHPl ([SODLQ�WKH�FRQQHFWLRQ�WR�QRQ�6$3�V\VWHPVl ([SODLQ�WKH�UHSOLFDWLRQ�PHFKDQLVPl 0RQLWRU�WKH�&50�0LGGOHZDUHl 'HILQH�WKH�W\SLFDO�FXVWRPL]LQJ�VWHSV
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 11-4
SAP AG 2001
5HFRPPHQGHG�)ROORZ�XS�$FWLYLWLHV
l *R�WKURXJK�WKH�H[HUFLVHV�XVLQJ�,'(6�GDWDRU�\RXU�RZQ�GDWD
l +DYH�D�ORRN�DW�8QLW�µ)XUWKHU�LQIRUPDWLRQ¶
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 12-1
SAP AG 2001
l *ORVVDU\&RQWHQWV�
$SSHQGL[
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 12-2
*ORVVDU\
$%$3Advanced Business Application Programming.
ABAP is an object-oriented programming language and environment for development,deployment, and operation of mySAP solutions.
$'2ActiveX Data Objects.
Microsoft’s newest high-level interface for data objects. It can be used to access all sorts ofdifferent types of data.
%$',Business Add-In. Enhancement concept for ABAP applications. Standardization of user-exitsand BTEs (business transaction events).
%$3,Business Application Programming Interface. Release-independent, standard SAP interface forthe creation and processing of business objects.
%'RF�PHVVDJHBusiness document message. A message that contains information on changes made tobusiness objects. BDoc messages are used for data exchange and data processing within aCRM system environment. The underlying message format is defined in a BDoc type (businessdocument type).
%'RF�W\SHStructure definition of BDoc message data segments. There are three classes of BDoc types:
• BDoc types exclusively used for non-mobile applications (mBDoc types) consisting of ahierarchical segment structure without direct assignment to database tables and anextension part with the business data (of complex data type modeled in ABAP Dictionary)
• BDoc types for synchronization between the consolidated database from the CRM Serverand mobile applications (sBDoc types) consisting of hierarchical segment structure withdirect assignment to database tables
• BDoc types exclusively used for mobile applications consisting of a hierarchical segmentstructure with assignment to database tables
The hierarchical segment structure is modeled with the BDoc Modeler.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 12-3
%7(Business Transaction Event.
Event-oriented enhancement concept for ABAP applications based on a publish-and-subscribeconcept.
&KDQJH�DQG�7UDQVSRUW�6\VWHP��&76�A set of tools in the SAP System for managing and transporting ABAP Workbench andcustomizing changes made in systems in the SAP System landscape and distributed betweenthese systems.
&20����'&20(Distributed) Component Objects Model. Defined by Microsoft. Comparable to CORBA(Common Object Request Broker Architecture). Defined interfaces for calling up distributednetwork services.
&7,�6HUYHUComputer-telephony integration server. CTI is an optional third-party software component inthe Interaction Center (SIC, Telesales and Telemarketing scenario).
Being part of the CRM Server, the standard SAPPhone API works as an interface between theapplication components and the CTI server and telephone components to provide directcommunication between telephony and the CRM system.
'HOWD�/RDGThe transfer of information about changes between sites of type R/3, CRM or CDB.
(UURU�+DQGOHUTool that handles BDoc messages with errors within flow control. Error activities that havebeen defined for a given error situation are carried out.
)ORZ�FRQWH[WInformally described steps in the general message processing model. A flow context ispredefined and associated with lists of services to be called in this context
,'RFIntermediate Document. The SAP standard document format for the message exchangebetween SAP business solutions or between SAP business solutions and external systems.
Part of Application Link Enabling (ALE).
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 12-4
,QLWLDO�/RDGFirst load of business, customizing, and condition objects from an SAP R/3 back-end systeminto the consolidated database (CDB) of the CRM Server. This way the CRM Server isprovided with an initial dataset.
5HSRVLWRU\��&50�0LGGOHZDUH�5HSRVLWRU\�Central storage location for various repositories for all CRM meta-data on the CRM Server.Runtime objects are generated using these meta-data.
0HVVDJH�)ORZProcessing steps of a BDoc message within the CRM Middleware, whereby each flowdefinition (depending on the BDoc type) comprises a sequence of registered services.
3XEOLFDWLRQDefinition of one or several replication objects with specific criteria for replication.Publications can be subscribed for sites.
T5)&��TXHXHG�5)&Queued Remote Function Call. A qRFC is a transactional remote function call with aguaranteed processing sequence.
5HDOLJQPHQWRedistribution of mobile application data that ensures that all mobile sites receive the dataassigned to them through subscription. Changes to data trigger a minor realignment, whilechanges to subscriptions trigger a major realignment.
5HSOLFDWLRQRule-based distribution of data to sites.
6$3�%:The 6$3�%XVLQHVV�,QIRUPDWLRQ�:DUHKRXVH is a component of a mySAP Business Intelligencesolution for analyzing data from operative SAP R/3 applications as well from any otherbusiness application and external data source such as databases, online services and theInternet.
6$3�%:�$GDSWHUGeneric mechanism for extracting business objects from the CRM application component foranalyses within BW. The SAP BW Adapter provides a simple framework for definingextraction for any CRM business object that is stored in the CDB and communicated via theCRM Middleware in BDoc format.
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
© SAP AG CR500 12-5
6$3�5���SOXJ�LQInterface that enables the exchange of data between one or several SAP R/3 systems and othermySAP solutions.
6LWHSender and recipient of data in a mySAP solution landscape.
6XEVFULSWLRQThe assignment of a site to a publication, specifying criteria values if necessary. The creationof subscriptions triggers the actual distribution of data to the sites.
6\QFKURQL]DWLRQ��RI�FXVWRPL]LQJ�GDWD�Transfer of delta customizing data from an SAP R/3 back-end system to the CRM Server basedon dataset comparisons
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly
Fo
r
in
te
rn
al
u
se
b
y
CS
C
on
ly