CRM to R3 partner flow via CRM Middleware ...

Hi all ,
Any one can tell me where the setting of the filter in standard has been done for the fields of the BUT000 which flows to ECC R3 in the middleware .
Actually the requirement is to send some specific data of all the ship_tos which is created in CRM .
It would be even greate if any one can share the document of CRM Middleware which will give from the basic of the Middleware configuration ,Adapter objects ,attribute settings .
Thanks ,
Kashim Raja

Hi Kashim,
You can maintain the filter settings for business partners in TCode "R3AC1". Please select the Business object "BUPA_MAIN", click on filter and maintain the required filters under "Table structure within object" for BUT000 table.
Please refer this help portal for more info :
http://help.sap.com/saphelp_crm70/helpdata/EN/56/6b34429cb0907ce10000000a114b1d/frameset.htm
http://help.sap.com/saphelp_crm70/helpdata/EN/1d/09d1e713d711d6999e00508b6b8a93/frameset.htm
Regards,
Chethan
Edited by: Chethan Kumar C M on Sep 27, 2009 7:46 AM

Similar Messages

Problem with Business partner flow from R/3 to CRM

Hi,
We are setting up a process to flow of Business Partners from R/3 to CRM.
We have configured PIDE correctly but the problem is when I am creating any customer in R/3 we are getting DUMP.
Kindly help me in this regards.
Thanks

Hi,
Check out the following Middleware Configuration :
     <b>CRM Middleware configurations</b>
1.     Source client for Client copy
     Using t-code SCC3 in both CRM and ISU to get the source client used for client copy.      Get source client for profile SAP_ALL.
2.     RFC Destinations
     Use t-code SM59 and check if the following RFC destinations have been created:
     CRM
o     R/3 Destination for CRM e.g. CRTCLNT240
o     R/3 Destination for ISU e.g. ISTCLNT240
o     Logical Destination for Middleware R&R queues one for current client and one for client 000.                                                                            e.g. SAPCRM_MW_RR_240, SAPCRM_MW_RR_000
o     TCP/IP Destination for IPC dispatcher e.g. IPC_RFC_DISPATCHER
o     TCP/IP Destination for IPC server e.g. IPC_RFC_SERVER
     ISU
o     R/3 Destination for CRM e.g. CRTCLNT240
o     R/3 Destination for ISU e.g. ISTCLNT240
3.     Logical Systems
     Using t-code SALE check if the following logical systems have been created:
     CRM
o     Own logical system e.g. CRTCLNT240
o     Logical system for ISU e.g. ISTCLNT240
o     Logical system for source client used in client copy e.g. CRTCLNT200
     ISU
o     Own logical system e.g. ISTCLNT240
o     Logical system for CRM e.g. CRTCLNT240
o     Logical system for source client used in client copy e.g. ISTCLNT200
     Check if own logical system is assigned to the client.
     Path: Sending and Receiving systems -> Logical Systems -> Assign Client to Logical      System.
     Convert Logical System name in application tables
     Use t-code BDLS to convert logical system names in the application system.
1.     Enter old logical system name retrieved in step 1. e.g. CRTCLNT200
2.     Enter new logical system name e.g. CRTCLNT240.
3.     Select radio button Conversion of Client-Dependent Tables and execute the transaction.
This process needs to be carried out 4 times: twice in CRM and twice in ISU.
     CRM
o     Old CRM logical system -> New CRM logical system. e.g. CRTCLNT200 -> CRTCLNT240.
o     Old ISU logical system -> New ISU logical system. e.g. ISTCLNT200 -> ISTCLNT240.
     ISU
o     Old CRM logical system -> New CRM logical system. e.g. CRTCLNT200 -> CRTCLNT240.
o     Old ISU logical system -> New ISU logical system. e.g. ISTCLNT200 -> ISTCLNT240.
4.     Middleware Parameter tables
     Use t-code SM30 to maintain middleware parameters in following tables
     CRM
o     Table SMOFPARSFA:
     Change value for following parameter entry:
     Key - R3A_COMMON
     Para name - CRM_DEFAULT_DESTINATION
     Value - Old ISU logical system -> new ISU logical system
          E.g. ISTCLNT200 -> ISTCLNT240
     ISU
o     Table CRMRFCPAR:
     Delete the previous entry for the following key:
     User - CRM
     Object name - *
     RFC Destination - Old RFC destination for CRM e.g. CRTCLNT200.
     Load types - All Load Types
     Create new entry with following data:
     User - CRM
     Object name - *
     RFC Destination - New RFC destination for CRM e.g. CRTCLNT240.
     Load types - All Load Types
     In Queue flag - X
     Send XML No XML
o     Table CRMPAROLTP:
     Change value for following parameter entry:
     Para name - CRM_DEFAULT_DESTINATION
     User - CRM
     Value - Old CRM logical system -> new CRM logical system
          E.g. CRTCLNT200 -> CRTCLNT240
5.     Admin Console (Sites and subscriptions)
     Using t-code SMOEAC in CRM change attributes for the following sites.
     CRM site
o     Name: Change name from old CRM logical system -> new CRM logical system e.g. CRTCLNT200 -> CRTCLNT240
o     Description: Change description from old CRM logical system -> new CRM logical system e.g. CRTCLNT200 -> CRTCLNT240
o     Site attributes: Change RFC destination from old CRM RFC destination to new CRM RFC destination e.g. CRTCLNT200 -> CRTCLNT240
o     Click on get values button to refresh logical system details.
     ISU site
o     Name: Change name from old ISU logical system -> new ISU logical system e.g. ISTCLNT200 -> ISTCLNT240
o     Description: Change description from old ISU logical system -> new ISU logical system e.g. ISTCLNT200 -> ISTCLNT240
o     Site attributes: Change RFC destination from old ISU RFC destination to new ISU RFC destination e.g. ISTCLNT200 -> ISTCLNT240
o     Click on get values button to refresh logical system details.
     Check if ISU site is assigned to following subscriptions.
     All Business Agreements (MESG)
     All Business Partner Relationship (MESG)
     All Business Partners (MESG)
     All Business Transactions
     IS-U Connection Objects (MESG)
     IS-U Contracts (MESG)
     IS-U Points of Delivery (MESG)
     Product Materials (MESG)
6.     CRM Middleware Queues
     Inbound Queues:
I.     Execute transaction SMQR.
II.     Change AS group from DEFAULT to parallel generators.                Path: Edit -> Change AS Group
III.     Register following queues:
     CRM
o     CSA*
o     R3A*
     ISU
o     R3A*
Outbound Queues:
I.     Execute transaction SMQS.
II.     Change AS group from DEFAULT to parallel generators.                Path: Edit -> Change AS Group
III.     Register following queues:
     CRM
o     CSA*
o     R3A*
     ISU
o     R3A*
R&R Queues:
I.     Execute transaction SMOHQUEUE in CRM.
II.     Check if all queues have status Released.
III.     Start Queue Demon by clicking on Start Queue Demon.
<b>Please reward points if it helps.</b>
Regards,
Amit Mishra

SAP CRM Middleware flow from R/3 to CRM

hi
I am new to CRM middleware I have some doubt about the replication from the R/3 to CRM.
I have some 4 basic questions Kindly help me out
1.in initial down lode how to know which object for which requirement? There is any list like these objects for this one?
2.when the initial download have to use and when the delta down lode have to use?
3.object creating is preferable option or not if yes in which condition we have to create the objects?
4.what is the difference between customizing objects and business objects? and when we have to use which object ?
wiht Regards,
prakesh..!

Hi Prakesh
Happy to hear that my answers were useful. Hope this new will solve your problem.
So let's reply to your new questions.
1) Yes it is the delta download. This means that you have already triggered the initial download. Now all changes or new creations are replicated into the CRM system. I do not suggest this approach. This is usually used when you have no other chance because this process is complex and very time consuming. I would suggest checking the BDoc before proceding with degugging the queue. Go to transaction code SMW01. Filter on time (when you made the change). You will find bdocwith a red or yellow traffic light. This means that data have been not processed in CRM system. You usually have an error message (just select the BDoc from the list and click the red button in the toolbar) attached to the BDoc that is explainatory of the error. Correct the error and reprocess the BDoc (there is a proper button).
2) To debug the queue go to transaction code SMQS and SMQR and deregistrate inbound and outbound queue in the CRM system. After you do this, apply the changes to the customer. You will find an inbound queue in transaction code SMQ2. Select the queue and click the last button in the header toolbar. You will process the flow in debug. Remember to register the queue when this is no more necessary otherwise you will have a mess in the system.
3) if you create new customer in CRM system, this are automatically replicated in the backend system basing on the scenario set. No additional tables are created. All the changes applied in the CRM system will be replicated in the backend with the same process except the Bdoc that are really CRM specific.
Hope this help you.
Regards,
Fabrizio

Regarding CRM middleware and XI

In SAP CRM middleware acts as a heart of CRM.
that means communications with CRM server from any other server is through middleware,right?
In netweaver ,XI acts also the same like the integration server.
right?(both SAP and NON SAP server)
please explain the above two statements clearly.
thanks in advance
kpsmoorthy.

The role of CRM "middleware" vs XI is often misunderstood.
Let's go back many many years and understand why we have CRM "middleware".
Before XI even existed SAP had to have a way to transfer data between an R/3 system and the CRM system. The CRM system needed to have a "replica" of the necessary master data to capture sales orders for e-commerce or mobile sales. Thus SAP created the "middleware". The middleware consist of a new dimension "plugin" on the R/3 system and code on the CRM system, built upon the concept of queued RFC. Basically the standard transactions such as XK01, XD01, VA01, etc. were modified to generate bdoc's whenever data was changed or created. These changes then flowed to CRM via queued RFC.
CRM middleware primary goal was to receive data from R/3 and to send data back to ERP. In release 3.0/3.1 it was expanded to allow external systems to receive and transfer data into CRM via the XIF adapter. After the XIF adapter was released, SAP introduced the XI system. The XI system was designed for integration between systems. However the CRM middleware being robust and not requiring extra systems still exists. If you want to integrate one SAP CRM system with an SAP ERP system then the "crm middleware" is the application tool that is isued.
If you need to integrate SAP CRM with external systems then you would use a combination of XI + the CRM XIF adapter. In CRM 52/60 you can use the web services toolset in addition to the XIF adapter.
To summarize:
"CRM Middleware" - Specialized integration scenario between SAP CRM & SAP ERP
XI - your integration server that can do a lot more than "crm middleware".
Take care,
Stephen

Using SAP PI instead of CRM Middleware

Hi experts,
Is it recommend to use SAP PI instead of SAP CRM Middleware.
If yes how can I do that.
I have read in forum requests that it can be implemented by using iDOC instead of BDocs.
I need a technical guideline how data (eg. Business Partner Data) can be tranferred from CRM to other ERP System.
Thank you for help.
Greetings
Mario
Edited by: Mario Bauer on Jun 22, 2010 9:24 AM
Edited by: Mario Bauer on Jun 22, 2010 9:28 AM

Hi!
SAP PI itself is a middleware Product but very roboust and capable enough to integrate any system to any other system, either it is SAP or Non-SAP. And there are two ways to integrate other ERP System to SAP CRM using SAP PI.
1. SAP PI will receive the message from back end ERP system & convert it to the XML format. SAP CRM receives the message using the Middleware XIF adaptor and convert the incoming XML Messages in the BDocs and the BDocs upload the data in the SAP-CRM Data base.
2. SAP PI will receive the message from back end ERP system & convert it to the XML format. SAP CRM receives the message and using the Functional Module convert the data into the BDocs and the BDocs upload the data in the SAPCRM Data base. In thsi situation, you need an expert ABAP Consultant to write the accurate functional Module.
The data inside the SAP_CRM System always transported in the BDocs not in Idocs. It is the BDocs data containers which transport the data from CRM Middleware to CRM Database and CRM Database upto CRM Middleware.

Is CRM Middleware Expertise Required if no R/3 Is In Scope?

Hello CRM Community,
I'm an XI developer, and I'm trying to get a handle on exactly when CRM Middleware (& thus a Middleware Resource) is required, and when it is not.
If a customer is implementing CRM 5.0 (with IC Web)in a landscape with non-SAP applications, would they necessarily require a Middleware consultant?
And if so, to what extent would that requirement be reduced in comparison to an implementation which interfaces to R/3?
Thanks in advance,
Jimmy

Hi,
CRM middleware is used in CRM whether or not the system is linked to other systems (SAP or non-SAP). CRM is based on it. Eg. whenever you create or change an object in CRM, a bdoc is created which contains the data.
The question is whether you'll need to use, influence or change the middleware in your project:
Image having integration with R/3: then you'll need the middleware for setting up the distribution (initial/delta load) between CRM & R/3. But as long as you stick to the standard solution, this will be very easy to setup.
Imagine having integration to other systems: then you'll need the middleware to interface to them (which can be done using idocs or XML).
Imagine having a CRM-MSA implementation: then the middleware is used to send data to the MSA client. This means setting up the data-distribution to the clients, which can be quite complicated.
Imagine having a stand-alone CRM system with an IC webclient and flows limited to the CRM system: then a middleware consultant won't have to much work.
Michael.

CRM Middleware Object extensions

Hi All -
Can someone send me the "CRM Middleware Object extensions for custom Bdoc developments/Bdoc Modeling" book and any stuff on Business Transaction Events (BTE)?
TIA,
Aarthi.

Hello Davy,
please do not request documents to be sent via Mail. Have you read Links to CRM Documentation.
Regards
Gregor

Entire List of CRM Middleware configuration Tables needed.

Hi All, Can any one give me the entire list of all the CRM Middleware configuration Tables.
Thanks in advance

CRM Tables:
SMOFPARSFA--Middleware Parameter
SMW3FDBDOC -
BDoc Type Specific Flow
SMW3FDCUST--Customer-Specific Flow
SMW3FDSTD--Flow: Standard Configuration
R/3 Tables:
CRMRFCPAR --n Definitions for RFC Connecti
CRMPAROLTP -- CRM OLTP Parameters
CRMFILTAB -- Filter Conditions for Download

Version Compatibility of SAP R/3 4.6 C with SAP CRM 5.2 + CRM middleware

Dear SDN team,
We are trying to Integrate SAP R/3 4.6c with SAP CRM 5.2 using CRM middleware.
We wanted to know the following :
1.Technical and Functional feasibility in integration of CRM 5.2 and R/3 4.6c. What are problems for these versions ? ( In Brief )
2.We are trying to move the Objects BP , Quotes and Products from R/3 to CRM 5.2. Has anyone done this and can someone give us a brief description of the problems while doing the same
3.Any other useful suggestions would be very helpful regarding CRM middleware.
Kindly reply on this post . Points would be awarded.
Thanks and Regards
Dinesh and Ritvij
Email : [email protected]

Hello Ritvij,
Regarding middleware ,are you down loading plants? bacause down load object objects DNL_PLANT is obsolete.
Unusable middleware objects :
DNL_CUST_BASIS3
DNL_CUST_PROD0
DNL_CUST_PROD1
DNL_CUST_SRVMAS
and the master data objects
MATERIAL
SERVICE_MASTER..
Find composite note for middleware at 872533..
What is the leading system for Order creation?
Please refer notes 490932 for more info about transactional doc replication between the two systems.
Please assign points.
regards,
Muralidhar Prasad Chatna

SMOEAC - CRM Middleware

Hi guys,
I configured the CRM middleware component to replicate materials,services and config objects but in the SMOEAC trx, on site selection, there only appears the CRM site, but not the R/3 backend site.
Table SMOF_ERPSH shows the following:
RFC DEST    ERP RELEASE ERPLOGSYS SITETYPEID
none              --                       -                       CDB
SRP             700                    SRP                  CRM
SRP is the Destination RFC defined in SAP R/3 and also the logical system ID of our SRM 5.0 System
What went wrong? How to resolve it?
Thanks for any help.
Aart

Hi Consultoresvision,
Can you pl. tell me what configuration you need to maintain for CRM middleware components.
After client copy for SRM 4.0 from Production to QA, the SMOEAC is totally erased and there is no objects. I am aware of how to create sites for R/3 and SRM after the object of "Site" is available. But here the object "Site" itself is missing.
Any inputs would be appreciated.
Thanks
Venkatesh

How can I send an update to CRM Middleware after changing BUPA longtext

Hi folks,
I am looking for the easiest way to send an update/insert of BP longtext change to SAP CRM Middleware (& MobileSales). I have implemented save of the text with function save_text within of a CRM application for changing bp data.
Text is available to standard CRM transaction bp, but now updates have been send to subscribed Mobile Sales clients.
I have already checked the bapi_bupa* functions, but it seems that they contain no notes/longtext segment.
Thanks for any help.
Daniel

Hi Daniel,
just wondering if you had a solution for this as I have the same issue to solve as well.
thanks, regards.

Notes on CRM Middleware and other

I am after some notes on CRM. Please can someone kindly send me the notes on CRM Middleware (CRM500) and CRM Services (CRM700) and any other similar notes.
My email is [email protected]
Thanks in advance,
Ruong

Hi Amit,
I appreciate if you could send me CRM middleware document to me as well @ [email protected]
thanks,
Amit

CRM Middleware Documentation and Training

Apologies as this is not a technical/functional question as such but I have been looking for SAP CRM Middleware documentation and/or training courses on the subject.
Particularly in relation to integration with Microsoft Exchange Server
So far I have found documentation on help.sap.com but little else. Nothing on integration with MS Exchange.
Firstly, does anyone know of any other good sources where this type of information can be found?
Secondly regarding training, the only course I have found has been the CRM Basics 5 day course that covers Middleware, but I don't know how in depth or even if it covers integration with Exchange.
Is anyone aware of any good CRM Middleware courses, preferably in the UK?
I would be grateful for any kind of help?
Many Thanks
David

Hi,
Check out
http://help.sap.com/saphelp_crm50/helpdata/en/2b/0bc5de1814b34b8f453fa5b07b8739/frameset.htm
Middleware courses are available:
CRM500(overview) & CR550(enhancements) & some mobile integration courses, but none of them realy cover groupware integration.
It's a pretty new functionality...
Michael.

Why we need crm middleware for material replication?

Hi Experts,
Why we need CRM middleware for material replication from ECC to SRM when we can do the vendor replication from ECC to SRM with ABAP report? IS there any technical limitation?
Thanks and regards,
Ranjan

Hello,
Vendors and locations, for example, you can replicate from ECC to SRM using ABAP reports.
However, if you want to replicate the following information, you should use the middleware:
- DNL-CUST-BASIS3 - Basis CRM online
- DNL-CUST-PROD0 - Material number conversions
- DNL-CUST-PROD1 - Product : categories
- DNL_CUST_SRVMAS - Customizing: Service Master
- MATERIAL - R/3 Material Master
- SERVICE_MASTER - R/3 Service Master
Check note 872533. It provides more information.
Regards,
Ricardo

USE OF CRM MIDDLEWARE AND XI in SRM LANDSCAPE

Hello All,
Please Can anyone tell me for communicating between SRM and different systems within a landscape,how do we recognise whether to opt for XI or CRM middleware
(Of SRM)???
Please Help.
Thanks,
Disha.

Hy Disha,
The different communication methods from SRM are:
1 CRM Middleware
This is only used for Master Data replication (init) with SAP Backends, and for Product master for init and delta uploads.
You can define your own BDocs for your needs (non easy way)
2 RFC
This is used for R/3 backend document creation (Reservation, PR and PO) in classic and extended scenarios, and for several checks in the SC creation
3 ALE/IDOCs
This is used for Good receipt and Invoice creation in R/3 in Classic and Extended scenario
4 XI
It is used for SUS integration, CCM upload and publishing scenarios, and PO send scenarios.
Regards.
Vadim

CRM to R3 partner flow via CRM Middleware ...

Similar Messages

Maybe you are looking for