Getting error while executing /scwm/erp_stock check

[former_member539540]

Hi,

In SAP EWM system , while executing /scwm/erp_stockckeck getting error qRFC configuration failed for target system.

[sap_robin]

Hi,

Just an addition to this solution.

In our case, we had maintained the RFC destination for method calls in BD97, and also the Control for RFC Queue in Customizing, but we still got the same error. This was caused by a typo in our Own Business System. This can be maintained in SPRO via EWM -> Interfaces -> ERP Integration -> General Settings -> Define Own Business System.

The error (/SCWM/ERPINTEGRATION149) is generated in program /SCWM/ERP_STOCKCHECK_01I when the system is checking the business system against table /SCWM/TWMEQUEUE (which is filled in Customizing step "Control for RFC Queue"). So either the business system is not defined properly, or an entry is missing in the Control for RFC Queue step.

[JuergenPitz]

OK, I hope the original posters problem was solved. But this is probably because there is no RFC destination assigned for synchronous method calls (In Customizing: SAP NetWeaver --> Application Server --> IDoc Interface / Application Link Enabling --> Communication --> Determine RFC Destinations for Method Calls).

Create an entry for the "Standard BAdI Destination". This can be the same as the RFC destination you use anyway.

Brgds

Juergen

[former_member699064]

Hello,

I Have the same error in transaction /scwm/erp_stockckeck --> "qRFC configuration failed for target system XXXCLNTXXX". I have the same configuration in control for RFC queue in two systems, in one this functionality does not work otherwise in the other system is workint.

¿Do you solve this problem?

[Ajit_Routray]

Hi Mayur,

Please check the interface settings in EWM.

SCM Extended Warehouse Management->Interfaces->ERP Integration->General Settings

I guess Control for RFC Queue is missing.

Kind Regards,

Ajit

[former_member616119]

Hi Ajit,

Even after maintaining the entries for Control for RFC Queue, I'm getting the same error.

Regards,

Vinay