"SYS FAIL" ECC to SRM Material Replication error & Middle ware settings

[former_member507]

Dear

ALL,

I'm facing difficulty while the material is not transferring from ECC to SRM. I have seen all the blogs and sap answers but after remote login from both clients ECC and as well as from SRM its working fine. Whereas from the SRM R3AS transaction when I load the components its says SYSFAIL. Anyone,

please help with this issue please see the screenshot.

Thanks

SAI.

[michael_piesche · Accepted solution]

Obviously, the connection has an authentication error, the login cannot be performed because the set user credentials are currently wrong. Check, correct and test the connection settings in SM59 in ERP for your ABAP connection to SRM.

Don’t you have a basis team that takes care of this?

Do you have to do everything yourself? while still lacking the required and most fundamental knowledge about Middleware connections between ERP and SRM? You have by now posted several questions regarding the MW connection and functions.

This is going to take you ages if you continue this way with tackling one problem at a time and seeking only for answers on the SAP community.

You should also look into answers/Blogs/books/courses about SAP CRM Middleware. CRM and SRM application are fundamentally the same and Especially use the same Middleware Logic (with some exceptions regarding specific download objects).

There is a lot more content about CRM than there is about SRM, but they are like twins.

[former_member507 · Accepted solution]

K Done now the issue resolved by the sap note

Thanks

sai

[Sriram2009]

Hi Reddy.

From ECC system check the RFC connection from ECC to SRM using the transaction SM59 check the user id credentials.

Regards

SS

[former_member507]

Dear

all

any update please

Thanks

sai.

[michael_piesche]

saikrishna-01, did you check out the SM59 ABAP destination and test the connection and if it failed, updated the username password that is set for that? If your connection is working now and you have a different error now, please accept answers if they were useful and close this question and open a new one for your new issue(s).