cancel
Showing results for 
Search instead for 
Did you mean: 

Material Replication

Former Member
0 Kudos

Hello Folks,

We are on SRM Server 5.5 support package 9 - strategic souricng scenario. We have done the material replication setting according to the blog https://weblogs.sdn.sap.com/pub/wlg/5728. [original link is broken] [original link is broken] [original link is broken] One strange problem we are facing while we replicate object DNL_CUST_BASIS3 . In the transaction R3AM1 we are getting the status as running with 0 block. In the transaction smq1 (ECC) and smq2 (srm) there are 0 queue displayed. Also in the transaction smw01 there is no selection. Although there are some red in the transaction smwp but I am not able to understand (not sure if that is the cause).

Please suggest full points who answer first

Thanks in advance

Amit

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Amit,

In addition to what Suren has suggested, also check the Queues in both SRM & R/3 side.Both smq1 & smq2 in SRM & R/3 not just the outbound queue of SRM & inbound queue of R/3.

Check the table settings once again in SRM & R/3 for CRMCONSUM, CRMSUBTAB, CRMRFCPAR, CRMPAROLTP in R/3 side and SMOFPARSFA.

Also check the SMOEAC (administrator console) settings in SRM for the site definitions.

I think the issue might be in the settings of middle ware parameters and ensure to clear all the queues (inbound & outbound) in both SRM & R/3 before replication.

Hope this will help you in resolving the issue.

Clarifications are welcome.

Award points for helpful answers.

Rgds,

Teja

Former Member
0 Kudos

Hello Suren/Teja,

RFC connections works fine in SRM and ECC and they able to login into the other system.

I think that the queue has not been defined by basis. Can anybody tells me what all queue we need to define in SRM and in ECC and how can I check them if they are defined or not.

Thanks,

Amit

Former Member
0 Kudos

Hi Amit,

In both SRM & R/3 you have both inbound and outbound queues.

SMQ1 & SMQ2 are the transaction codes that are used in both SRM & R/3.

Whenever you send some doc. from SRM to R/3 it reaches the outbound queue of SRM and if the queue is clear it reaches inbound queue of R/3 and then posts the doc. if the queue is clear and vice-versa.

In the same way when material replication happens, the customizing object request goes to R/3 from SRM and then collects the info. from R/3 and brings back to SRM.

During this process it may get stuck up in the queue on either side if something is already in the queue. So we need to clear the queue before doing the replication for the smooth data transfer.

Hope this makes you more clear and helps in resolving the issue.

Award points for helpful answers.

Rgds,

Teja

Former Member
0 Kudos

thanks points given to you...

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi All,

We too are facing the same problem as Amit (regarding the DNL_CUST_BASIS3 object not turning green) . We cleared all the queues in SRM and ECC but it still doesnot work.

Could you suggest some other steps which may help us resolve the same?

Rest assured, points would be rewarded for the answers

Regards,

Ancy

Former Member
0 Kudos

Amit,

This could be RFC connection issue. Double check if your RFC destinations in SM59 on both SRM and ECC and make sure they are able to remote logon to other system.

- Suren