SRM 7.0 - CRM middleware settigns for material replication

Hello SRM Guru's
Can you please provide me detail step by step process of CRM middleware settings for material replication from ECC 6.0 SRM 7.0?
Thanks.
Regards,
Magesh.

Hi,
Configuration Guides are available in SAP Solution Manager Server. Downloaded offline version is also available in SAP Service Marketplace. http://service.sap.com/srm-inst
Please check a good blog by Marcin Gajewski. /people/marcin.gajewski/blog/2007/02/05/how-to-replicate-material-master-from-r3-to-srm
SDN has search functions. You can find solutions for your issue.
Regards,
Masa

Similar Messages

CRM MIDDLEWARE QUERY FOR PRODUCT REPLICATION -URGENT

Hello All,
I am replicating the product categories(in SRM terminology) i.e. initia load of Material groups from backend(R/3) into the SRM system through the CRM Middleware.
At the r/3 side in the tcode SMQ1(Outbound Queue),i am getting the status as STOP while at SRM side(i.e. CRM middleware) in the tcode SMQ2(Inbound queue),i get the status READY.Also when I go in for the transaction of Monitoring Initial Load (R3AM1),I get the status as RUNNING.
Can anyone please tell me how much time it takes to download these objects because I had started the Initial Load for 4 Objects out of which the 1st object took 4 hrs to be downloaded!Please help.
Thanks & regards,
Disha D

Also I got an error in executing the report BBP_PRODUCT_SETTINGS_MW with the foll information text :-
The termination occurred in the ABAP program "SAPLSMSG" in "MESSAGE_STOR
The main program was "BBP_PRODUCT_SETTINGS_MW ".
The termination occurred in line 44 of the source code of the (Include)
program "LSMSGU02"
of the source code of program "LSMSGU02" (when calling the editor 440).
What customizatuon/configuration settings are required for this report to be executed succesfully????
Disha

Why do we need to define RFC destination and user for material replication

Dear Experts,
why do we need to define RFC destination and user for material replication? Here we use crm middleware only for material replication. Could you please help me to understand it?
regards,
Ranjan

Hello,
As far as I know, you can use the same RFC destination already available in ECC to SRM to replicate materials.
You can refer to note 720819.
Regards,
Ricardo

SMOEAC site settings for material replication

SRM Gurus,
While doing the settings for material replication, in SMOEAC transaction
I am trying to create site 'SRM' of type CRM, In the site attributes if I enter RFC destination 'SRMCLNT001' and click on get values I am getting the following message "RFC destination SRMCLNT001 does not exist. No valid backend system".
Can someone please suggest what I need to check/configure to fix this issue?
Info:
R/3 side : RFC destination SRMCLNT001 (for connecting to SRM 5.0 system) created and remote logon tested OK.
Completed all CRM* table settings
SRM side: RFC destination R3CLNT800 (for connecting to ECC 6.0) created and remote logon tested OK
Thanks,
Arun

Make sure you have created the RFC destination in SRM also. You need to create the following:
RFC destination of SRM in SRM and in R/3.
RFC destination of R/3 in R/3 and SRM.
Regards, IA

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

CRM Middleware help for rookie needed.. Replication of Business Transaction

Hi guys,
I try to set up replication of Business Transactions from R/3 to CRM and vice versa.
I have created:
- CRM site type (CRM) , R/3 type site (R46CLNT700)
then I created a subscription: SalesDocuments (R46CLNT700 is assigned to this subscription) for publication "All Business Transactions (MESG)".
a, Is this enough configuration of MW for needed replication? Or do I need more settings set up?
b, When I try to start initial load of the Replication object BUS_TRANS_MSG (which is "in" publication All Business Transactions), I am not able to start Load from CRM to R46CLNT700).. As target I can use only CDB... What is wrong?
c, If I create some sales transaction in CRM system and I want it to be replicated to R/3 and vice versa, how will I know, which replication object represents this document? For example, I create a Sales Order. How will I know, which replication object to set up for replication?
Thanx a lot! Peter

Peter,
1.If you are looking for Initial download from CRM to R/3, this should be possible from CRM v4.0.
2. Delta flow between the systems should happen once your initial download is complete.
3. Check the Inbound and Outbound queues in CRM. If they seems to be hanging for long time, check whether you have registered the Inbound & Oubtound queues in SMQR and SMQS transaction on both CRM and R/3.
Regards,
Phani.
Wipro Technologies

XI Integration scenario for material replication from SRM to SRM-MDM

Hi Guys,
We are working with the following landscape:
SRM Server 5.5
ECC 6.0
SRM-MDM 5.5 SP6
PI 2005_1_700 SP0006
I have a question for you about replication of the material master form SRM EBP to SRM-MDM.
In XI we are trying to configure this scenario. For this we have imported the following XI Content:
- SAP SRM Server 5.5
- SAP SRM-MDM 2.0
We have the following problem; that when tring to configure the this scenario we are getting GUID errors. Probable because some XI content is missing. In the SRM-MDM 2.0 XI content we also see that SRM 6.0 scenario's are avilable in the currenlty imported XI content, but when clicking on 'Edit action' in these scenario's we are getting the following error:
"Software component version with GUID XXXXXXXXXX... does not exists"
Can any one tell me why SRM 6.0 scenario's are availble in the XI content for SRM-MDM 2.0, and which additional XI content we need to import to get rid of these GUID error's?
Becasue of this the configuration in the Integration Directory fails.Transfering the integration scenario to the Integration directory gives a couple of errors: "Unable to load action. Check whether all necessary actions have been released in the integration repository".
Hopefully some of you know what to do, because I am currenlty stuck....... Do we need to import additional XI content, or maybe the Xi content for SRM 6.0. If so where can I get the XI content for SRM 6.0. It is not available on the SAP Support portal as a download.
Thx In advance.
Regards,
Wouter

Hi,
>"Software component version with GUID XXXXXXXXXX... does not exists"
try updating SLD (CIM DATA) with the latest patch available
Regards,
Michal KRawczyk

Error message in trans code SMQ1(backend) for material replication

Hi All,
I am wandering if someone can help me with this query. I have basically followed all the customisation steps requried to replicate replicate material masters from R/3 to SRM. I had infact closley followed the advise posted on the blog: How to replicate material master from R/3 to SRM
However, once I start the initial load in SRM with trans code R3AS and thebn goto trans code SMQ1(in R/3 backend), the load has failed with the 'status' or SYSFAIL. When I double click on this message, I get the error:
"Exception condition" EBCDIC_PROBLEM__OSSNOTE_33300 8" raised.
I have looked at note 333008 but cannot find any clues as to what is causing the load to fail. In trans code R3AM1, the job's status only remains as 'Running' and does not change.
Any pointers as to the cause and required workaound would be appreciated!
Thanks
SW.

Hi Muthu,
Thank you for your feedback. I have just this moment implemented the note you recommended, but this does not appear to have resolved the error message, even though the consumer has been changed from CRM to SRM in r/3 and srm.
I basically undertook the initial load for object 'dnl_cust_basis3' only with trans code R3AS, but the system still shows the following error message in the outbound que list (trans code SMQ1) in the sender R/3 backend system:
""Exception condition "EBCDIC_PROBLEM__OSSNOTE_33300
8" raised""
I am reluctant to implement the note number (333008) within the error message as the note heavily describes the CRM 2.0 component only and shows little relevance to SRM 5.0.
Any feedback would be appreciated. I have pasted the note contents below.
Thanks
SW.
Note 333008 - XML in R/3 Adapter
Summary
Symptom
For the Plugin PI 2000.1 (R/3 OLTP) and the CRM 2.0B Support Package 08, the R/3 Adapter was enhanced by an XML support.As of CRM 2.0B Support Package 7, SAP recommends to use R3A XML as a standardAs of CRM 2.0C, XML is automatically the standard setting in the server, only in the OLTP PlugIn, you have to maintain a setting.
Additional key words
CRM, R/3 Adapter, XML, CRM_SEND_XML, BAPIMTCS, IBM, AS/400 OS/400 S/390, DBIF_RSQL_SQL_ERROR, SQL error -302 accessing table SMOAUSP
Cause and prerequisites
System requirement:Plugin PI 2000.1 with at least PlugIn patch 03 or higher and CRM 2.0B Support Package 08 or CRM 2.0C on the server.(XML is possible with CRM 2.0B Support Package 07, however, Support Package 08 is recommended:if you only use Support Package 07, parameter CRM_CONVERT_ENDIAN has to be maintained even if this has no effect - see Note 207264.)
Solution
Introduction
To eliminate or minimize problems that occur during the data transfer between different operating and computer systems, an XML interface was implemented in the R/3 Adapter in addition to the binary transport, which has been used so far.
This XML interface consists of an XML generating program on the OLTP-Plugin and an XML parser on the CRM.
The generating program generates an XML document from the data stream to be sent to the CRM System and the XML parser converts this back into the original data stream. Except for the initial configuration, the mechanism is transparent and does not require further user activities.
Activation
To use XML in CRM 2.0B in the initial download, you have to enter the following new parameter in table SMOFPARSFA (Transaction SM30 or R3AC6) on the CRM server:
             Key:             R3A_COMMON
             Parameter name: CRM_SEND_XML
             Parameter value: 'X'
In CRM 2.0C, table SMOFPARSFA does not have to be maintained since XML is automatically the standard setting.
For the data transfer with XML in delta download you must do the following
Maintain parameter table CRMPAROLTP in PlugIn Release PI 2000.1, patch 03:Newly enter parameter name CRM_SEND_XML_FOR_DEFAULT_DEST with parameter value 'X'.
Maintain parameter table CRMRFCPAR as of PlugIn Release PI 2000.2:Transaction SM30, set field SEND_XML of CRMRFCPAR to value 'X' for the corresponding entries
Advantage
The data transport in the XML format solves both the endian problem (see Note 207264) and the code page problem which existed during a data transport from or to an IBM mainframe (AS/400, S/390) to or from an ASCII-based system (NT, UNIX).
Deactivation
Regarding the performance, the XML format has the disadvantage that the XML parser needs CPU time (which can be processed in parallel because no database access is made).If you want to do without the XML conversion in a specially defined system landscape, then set parameter CRM_SEND_XML to blank in the CRM System, and set table CRMPAROLTP (PI 2000.1) or CRMRFCPAR (PI 2000.2) without XML in the R/3 OLTP.In addition, parameter CRM_CONVERT_ENDIAN must be maintained correctly in the CRM System (see Note 0207264).
You can do without the XML conversion under the following conditions.
1. The OLTP system infrastructure and the CRM system infrastructure mustbe homogeneous. Example: all OLTP application servers UNIX and all CRMapplication servers NT.
2. You must also make sure that no application servers with different operating systems are used in future.
3. The OLTP system infrastructure must be homogeneous.In the CRM System it is possible to limit the application servers permitted for the processing of the queues by setting a specific server group.The application servers of these group servers must be homogeneous.However, the setting is valid for all inbound queues and cannot be restricted to specific queue names.
              You can set up a server group with Transaction RZ12, and in Transaction SMQR you can set up the server group used for the processing via menu option 'Edit' -> 'Change AS group'. For details on this, see Note 369007.
As SAP cannot check the customer's system landscape,this option is to be classified on project basis where the responsibility is the customer's and not SAP's.
If homogeneous system infrastructures do not exist, the time required for saving data and documents can nevertheless be significantly reduced by carrying out the XML conversion in one asynchronous step.For this, you must maintain parameter CRM_XML_BACKGROUND_PROCESSING_ON in table CRMPAROLTP. For this purpose, refer to Note 350176.
Notice
Since the IPC is currently not able to process the XML document of the R/3 Adapter, XML must not be activated for IPC targets in CRMRFCPAR!
Since, in addition to the existing data mapping and data transport, the XML generation and the XML parsing is included in the sequence of operations, you must expect a download runtime which might be twice as long as usual!
Due to performance reasons, only the '&', '<' and '>' characters are converted into XML escape sequences at present.Therefore, other special characters in text fields might cause problems and might not be output correctly on the target system.
The XML conversion does not solve problems with multi-byte texts, for example the data exchange between a Japanese and an English codepage is not supported.
Source code corrections
Header Data
Release Status: Released for Customer
Released on: 25.07.2001 22:00:00
Priority: Recommendations/additional info
Category: Special development
Primary Component: CRM-MW-ADP Middleware Adapter
Secondary Components: CRM-MW Middleware
Affected Releases
Software
Component Release From
Release To
Release And
subsequent
MDM 200 200 200
COM_CRMMDM 40 4.0 4.0
UIFRW 40 4.0 4.0
CGVMIC 10 100 100
BBPCRM 2.0 20B 20C X
BBPCRM 3.0 300 300 X
BBPCRM 3.1 310 310 X
BBPCRM 3.5 350 350 X
BBPCRM 4.0 400 400 X
Correction delivered in Support Package
Support
Packages Release Package
Name
BBPCRM 20C

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

Material replication from ECC to SRM

Dear SRM 7.0 Experts,
We are implementimg SRM 7.0 and we are trying to execute the Initial Load of materials into SRM 7 from ECC. We have completed all the Middleware settings and all the customising required for material replication. Whe we run the initial load (tcode R3AS) and select the first object DNL_CUST_BASIS3, it runs but the status remains "Running" in R3AM1. There is no errors in SMQ1as the entry runs and completes and therefore disappears. There is no errors recorded in SMW0 or SLG1 either. What could be the problem?
I checked in SMQ1 & SMQ2 as well, but there is no entries here for the object DNL_CUST_BASIS3. what we can do to resolve the issue ?
Regds,
Cb

Have you checked the outbound queue in backend R/3 system ?
Have you defined the additional user in CRMCONSUM table apart from the CRM user?
Verify and, if necessary, change or insert entries in tables CRMCONSUM and CRMRFCPAR as
described in SAP Note 430980. See also SAP Note 720819.
Hope this helps you.
Regards
Abhijeet

Material Replication Enhancements

Hello,
I was looking through the IMG looking for enhancements that can be implemented for material replication. I found these enhancements (COM_PRD_POST_FILTER and PRODUCT_SET) but I am not sure if they apply to material replication.
Does anyone know?
Points awarded accordingly.
Regards, Dean.

Hi,
When you change a (local)product/material in SRM,you can use teh BADi PRODUCT_SET to define your own cross-client checks that you would like to be performed before a product can be saved.
See the foll documentation
This enhancement can be used to define your own cross-client checks that you would like to be performed before a product can be saved.
This enhancement contains the method CHECK_BEFORE_UPDATE, in which you can formulate the check.
When creating a check (implementation), you must specify in the filter the data segment (set type ID) that contains the data fields you want to check.
If a product is rejected, you generate an error message with the:
Message type 'E' if the product can only be saved as an inactive version
Message type 'A' if the product cannot be saved at all
This message, together with the name of the field, is then placed in the application log in product maintenance. The error message is displayed and you can navigate to the data field that caused the error message with a double-click.
If you wish the field to be displayed in a table control on the screen, you must also specify the line number in the table control when inserting the error message in the application log.
Requirements
The current data and old data of a segment (set type) is passed to the method CHECK_BEFORE_UPDATE in the parameters IT_SETDATA and IT_SETDATA_OLD. They are not assigned a type. So that you can read the individual data fields, you must declare an appropriate work area. In the sample code, this variable is called ls_set.
The data structure required can be determined in the Maintain Set Types and Attributes function by choosing Environment ->Set Type Structures. The data structure is displayed together with the field names it contains. The transaction data fields that can be used for the check are highlighted.
You should create your own message to describe the error situation in the application log. Message 014 from message class COM_PRODUCT, which is used in the example, serves as a template and should not be used in your checks.
Activities
1. Clicking on the IMG activity starts the BAdI Builder, and a dialog box is displayed with all consistency check implementations (enhancements) that already exist. You can create a new implementation for the definition PRODUCT_SET by choosing Create. Use a name in the customer namespace.
2. Select the data segment containing the fields for which you want to define the check. To do this, you must first insert an empty entry in the filter settings by choosing Insert Line. The set types (data segments of the product) can be displayed using the possible entries pushbutton. You can re-sort the entries by clicking on the header, or select an entry with a double-click.
3. The sample code can be used as a template in your implementation. To do this, choose Goto -> Sample Code -> Copy.
4. You now have to adjust the sample code as you are using another data segment (set types) and formulate your check for other fields. To do this, choose the Interface tab page and select the method CHECK_BEFORE_UPDATE with a double-click. Your method is shown with the sample code in the Class Builder. You must replace the data structure of the work area (ls_setdata) and the field names and check conditions. The procedure for finding the name of the data structure for your set type and the field names it contains is described under Requirements. You are advised to start the Maintain Set Types and Attributes function in a separate session so that you can simply copy across the information you require with copy and paste.
5. Check whether your code contains syntax errors.
6. Activate the method IF_EX_PRODUCT_SET~CHECK_BEFORE_UPDATE.
7. Activate the implementation (enhancement).
Further notes
This enhancement contains sample source code which does not allow an active version of the product to be saved if
the data field F0010 (Quantity) has the value 0
the data field F0011 (Unit of measure) is 'PC'
in the data segment (set type SETTYPE01).
Caution
Note that you are not allowed to make data changes to the code of the implementation (such as deleting data records).
BR,
Disha.
<b>Pls reward points for useful answers.</b>

Update material replication

Hi! I did the material replication in SRM 5.0 with Server 5.5, but I create in R/3 some materials after the replication....
I have to run new material replication process?? or I have another posibility?? I don´t know, a job, etc...??
Thanks
Rose

Hi Rosa,
Look at this thread for explanations on replicating hierarchies:
Switching Backend System
With initial download of DNL_CUST_PROD1, SRM creates 2 new hierarchies:
- R3MATCLASS for material groups/product categoris
- R3PRODHIER for material/service types.
The system assign each of them to purchasing & product applications.
Predefined set types are also assigned in R3PRODHIER.
With next download of DNL_CUST_PROD1, you can update R3MATCLASS, but not R3PRODHIER.
In your case, you would have to delete the existing R3PRODHIER (see how in the thread), but as you have already replicated products (assigned to a material type from this hierarchy), this won't be possible.
So, you must first delete the replicated materials (Hope you didn't use them in some SC...).
Rgds
Christophe
PS: please reward points for helpful answers

Material replication done without my material

Hai Gurus
I created material No;21,22,23 in backend system.And carried required procedure for replicating all material.But material replication has done without my materials i.e..,21,22,23 etc
Could u guys help me on this
Thanks & Regards
chandrasekhar

Hello,
Please check the config from this blog.
/people/marcin.gajewski/blog/2007/02/05/how-to-replicate-material-master-from-r3-to-srm
New materials created in ECC for a already replicated product category in SRM... transfer happens by BDoc, you can view the queues in SMQ1 & SMQ2.
Check that there are no filters setup in R3AC1
In SMW01, you can check the list of BDoc, for material replication BDoc type is PRODUCT_MAT, click on show BDoc message, you will see list of materials replicated via BDoc & errors if any.
Material Replication R/3 to SRM 3.0 - material not in COMMPR01
Hope this helps.
Thanks
Ashutosh

Why SAP SRM material replication happens through CRM middleware?

Can some one help me to understand, Why SAP SRM material replication happens through CRM middleware? Is there any functional/Technical reason behind this design?

Dear Sridhar,
SRM releases later SRM 4.0 are working with the same middleware implementation,
there where no changes between the releases. The SRM middleware implementation
was decoupled from the CRM middleware development at that time.
(Middleware is based on the basis functionality of queued Remote Function Calls qRFC)
Regards
Laszlo

Material Master transfer by CRM middleware

Cannot able to transfer material from R/3 to SRM,
want to know whether system names are specified separately in the CRM middleware config.
what are the basic settings to be done in the this component

You can add these fields in your reduced message type /SAPSLL/MATMAS_SLL ( created with reference to MATMAS ) type that you would have created to send the Produc master data to GTS .
GTS Plugin - Basic Settings ---Activate change pointer for reduced Message type.
Once you include these field in your reduce message type correcpondinf entry has to be maintaine in table TBD62 so that changes to these fields can go to GTS , you can use Tcode BD52 to maintain the entry in TBD62
Hope this helps.
Kind Regards,
Sameer

SRM 7.0 - CRM middleware settigns for material replication

Similar Messages

Maybe you are looking for