SAP CRM Middleware Basic Overview
Middleware is a tool which is inbuilt within SAP CRM that enables the SAP CRM system to interact with various other SAP (R/3, BW, APO etc.) and non SAP systems (3rd party web channel etc.)
Using middleware we can control what data should flow in and out of the CRM system and also monitor the same.
The data exchange between the CRM Middleware and external systems is performed via adapters. The adapters map and convert data between various formats.
Load objects can be exchanged between a source and target system, for example, between an SAP R/3 Backend and the CRM server. For Example: Business partner master data and product master data.
They are grouped as follows:
Business objects; transaction R3AC1
Customizing objects; transaction R3AC3
Condition objects; transaction R3AC5
The objects are stored in the table SMOFOBJECT.
R3AS is used to trigger an initial load.
The following are a few t-codes which are commonly used within Middleware:
SMW01 – Display BDoc Messages.
SMW03 – Display Unprocessed BDoc Messages.
SMQ1 – Monitor Outbound Queue.
SMQ2 – Monitor Inbound Queue.
SMWP – Middleware Monitoring Cockpit.
Thanks Kamlesh for sharing and have below query
CRM Middleware is also used in master data transfer from ECC to SRM (7.0 or may be below versions too). In this case, do we need to have CRM as a separate box?
If not required, then could you tell me how this CRM Middleware acts in the above case?
Vinoth
Hi Vinoth,
I checked this with my basis team for a particular SRM 7.0 project, in this scenario they have just used the RFC connection to replicate data from R/3 to SRM and vice versa.
Will update you if I get any other info on the same.
You can check the wiki as well, if you have not done that already:
http://wiki.sdn.sap.com/wiki/display/SRM/SAP+SRM
Regards,
Kamlesh.
Hi Kamlesh,
Good one,
Need to know more on themiddleware part.
for any CRM implementation projects, wat are the essentional things that need to be done if R/3 exists .which includes all settings,
who will do the site creation too,, is it a functional.
Thanks & regards
Prajith Prabhakarakurup.
Hi Prajith,
Most of the huge CRM implementation projects will have a specialist Middleware consultant to take care of all the replication activities. But as a Functional consultant you should be aware of monitoring the errors and analyzing them at the functional level.
For Example: If a particular BP is not being replicated from CRM to R/3, a functional consultant will check the detail of the BDOC in error by going to SMW01 and based on the error message check if all the necessary fields are maintained for the particular BP. Even after maintaining all the required fields the error still persists then check with the technical team/ Middleware consultant who can analyze the BDOC in detail.
Coming to your questions:
When R/3 exists and CRM is being implemented with R/3 integration the following steps need to be checked:
1) Check connectivity between the R/3 and CRM system in SM59 (Maintained by Basis team)
2) Maintain all the sites and subscription in SMOEAC for all the master data that will need to be replicated. (Yes you can create this as a functional consultant if basis is not aware of the same)
3) If required filters can be maintained in R3AC1 for Products, Customer and Sales order and more if necessary.
4) Correct number ranges have to be maintained, account group mapping should be correct for BP replication, relevant item categories need to be maintained for sales order replication.
You can find details of all the above mentioned steps and more at the following wiki link for CRM Middleware:
http://wiki.sdn.sap.com/wiki/display/CRM/CRM+Middleware
Regards,
Kamlesh
Hi kamlesh,
thanks for the answer.
Thanks & regards
Prajith P
Hello, David.
Please consider SAP CRM Middleware Optimization Guide - SAP PRESS Bookstore
Hi,
Some time before I reply with this question:
"Did you really enjoyed this lecture? 😈 "
And the funny thing is I didn't meant that, is a "lost in translation problem" instead of lecture I meant reading, in Spanish reading = Lectura, I mixed the languages, and the result was quite catastrophic, but indeed funny( if you see it from a cold prespective). so sorry Andrei wasn't my intention to offend so from now on I would check google translator more often 😀
So I will launch the question agan with the supervision of the almight google translator.
Did you really enjoyed this reading?
Edit: I already had this discussion:
http://scn.sap.com/thread/3393042
Cheers!
Luis
SCN - the place where you can gain the knowledge for free! You're welcome.
good..
other transactions from the crm middleware administration point of view which is also used by middleware developers often are.
SMWP - This is middleware cockpit. Where we get bird's eye view of message flow and system settings.
MW_CHECK - All the upgrade logs, if something has gone wrong or not.
MW_MODE - In time of emergency, where middleware flow immediately needs to be stop for what ever reason and its too late to register the queues. This transaction comes in handy. just "Off- Deactivate the processing of messages".
Hi Kamlesh,
Thanks for the informative post. During the initial data transfer how the load objects are created. How we will create a BDoc for master data transfer.
Regards,
Anuj kalra
Hi Kamlesh,
I am CRM Technical guy and would like to get in touch with you. Can you please share me your email / linkedin profile?
Thanks,
Pradeep