cancel
Showing results for 
Search instead for 
Did you mean: 

Material Replication

Former Member
0 Kudos

Hi,

While replicating the materila from R/3 to SRM we are getting the error as belo win SMQ1in R/3

Logical system changed.

Please advise.

Thanks,

Manu

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

resolved at my end

Former Member
0 Kudos

i AM ALSO FACING SAME ISSUE,

MANU CAN U TELL, HOW ITS RESOLVED?

Former Member
0 Kudos

Hello,

I would suggest you first go through the note 588701 and change the

logical system name to original one. After doing this please again

retest the scenario.

If you still have the problem then follow the note 765018 as described.

Hope these notes will resolve your issue.

the table CRMCONSUM in OLTP system (R/3 system).

Further please follow the all the steps mentioned in the note 720819

and compare your settings mentioned in the note.

Also once all setting are done, please use the T-code SE38 to

to execute the report BBP_PRODUCT_SETTINGS_MW in the EBP system.

Hope this helps you further.

Kind regards,

Gaurav

PLEASE GIVE FULL POINTS FOR USEFUL REPLIES

Former Member
0 Kudos

Also, when I start the initial upload in SRM I cant see any queues in

SRM(Tcode smq2) and MM(Tcode smq1).

Thanks,

Manu

0 Kudos

Hi Manu,

Do you followed the following procedure???

Basis Setup

Create system users for remote connection (RFC_CONN). This user must have SAP_ALL authorisation.

Create RFC connections in SRM system.

Go to transaction SM59 on SRM side and click on 'create' button. Set RFC destination name to backend system CLNT (eg. R3DCLNT200), connection type to 3 (abap / R/3 connection) and fill target host to your backend system. On tab Logon/Security add RFC_CONN user created in previous step. Save your settings.

Create RFC connections in backend system.

Go to transaction SM59 on backend side and click on 'create' button. Set RFC destination name to SRM system CLNT (eg. SR1CLNT300), connection type to 3 (abap / R/3 connection) and fill target host to your backend system. On tab Logon/Security add RFC_CONN user created in previous step. Save your settings.

Create a logical system name in SRM.

Go to transaction SPRO -> SAP Implemantation Guide -> Supplier Relationship Management -> SRM Server -> Technical Basic Settings -> ALE Settings -> Distribution -> Basic Settings -> Logical Systems -> Define Logical System Add a new value:

Log.System Name

R3DCLNT200 R3DCLNT200

Save your settngs.

Create logical system name in backend.

Go to transaction SPRO -> SAP Customizing Implemantation Guide -> SAP Web Application Server -> Application Ling Enabling -> Sending and Receiving Systems -> Logical Systems -> Define Logical System Add a new value:

Log.System Name

SR1CLNT300 SR1CLNT300

Save your settngs.

First of all you must set a RFC connectivity between SRM and backend system:

Middleware parameters setup Go to transaction SM30 on backend system and choose table CRMCONSUM. Add the following values:

User Active Description Q Prefix

CRM checked SRM connection R3A

Next, choose CRMSUBTAB for subscription table for Up and Download Object and add the following values:

User ObjectName U/D Obj. Class Function Obj. Type Funct. Name

CRM empty Download Material empty empty CRS_MATERIAL_EXTRACT

CRM empty Download Material empty empty CRS_CUSTOMIZING_EXTRACT

CRM empty Download Material empty empty CRS_SERVICE_EXTRACT

Next, choose CRMRFCPAR for definitions of RFC Connections and add following values:

User ObjectName Destination Load Type INFO InQueue Flag Send XML

CRM * SR1CLNT300 Initial Download SR1CLNT300 X Send XML

CRM * SR1CLNT300 Request SR1CLNT300 X Send XML

CRM MATERIAL SR1CLNT300 Delta Download SR1CLNT300 X Send XML

All other fields leave empty.

Now, configure filtering for material master:

Choose CRMPAROLTP table for CRM OLTP Parameters and add the following values:

Parameter name Param. Name 2 Param. Name 3 User Param. Value Param. Value 2

CRM_FILTERING_ACTIVE MATERIAL empty CRM X empty

Now we must edit the table for application indicator. Go to transaction SE16N on backend side and choose table TBE11. Search or add an application component BC-MID and edit activity settings (field AKTIV = X).

Save your settings.

Enterprise Buyer with/without CRM In this activity, you define whether you are running the Enterprise Buyer and CRM in the same system. This might accelerate the Master Data download performance. If you are using CRM in the client, then skip this activity.

In SRM system run transaction BBP_PRODUCT_SETTINGS, deselect 'Test mode' and choose Execute button.

The system generates a report containing all tables that have been deactivated.

Did you check whether IPC is running or not???

Did you check the following too??

1. Product number ranges equally maintained at both the places or not???

2.Filter settings for the material master

3.Backend systems properly mailtained or not?

4. Check logs in SMW01 and SMW02 , what errors you are finding??

Revert back, with findings.

Thanks

SRP

0 Kudos
jason_boggans
Active Contributor
0 Kudos

Hi,

Please firstly review notes 453154 & 902814 for details on

probable causes/effects of the LOGSYS change.

Also, please confirm that the new logical system is available in

customizing define backend systems and has been converted using

transaction BDLS.

Regards,

Jason

Former Member
0 Kudos

When I replicate the material I get the error as below:

Parent not O.K.:DNL_CUST_PROD1

in Monitor Objects in SRM.

However, Service master records were replicated successfully.

Edited by: Manu Agrawal on May 22, 2009 7:23 AM

Former Member
0 Kudos

hi,

Please check the SPRO settings in R/3.

Assigning the logical system -this should be same in the SRM server & SAP R/3 system

Regards

G.Ganesh Kumar