No recipient could be determined for object BUS2015 method SAVEREPLICA Message no. VLBAPI005

[former_member660993]

Diagnosis

The distribution model for decentralized Warehouse Management System (decentralized WMS) is not set up correctly with reference to the recipient determination for object BUS2015 method SAVEREPLICA. This means that the system cannot determine a recipient for object BUS2015 method SAVEREPLICA.

System Response

The system reacts by issuing a warning message, or by terminating processing in critical situations. If a warning message is issued, changes are made to the object. If processing is terminated, the object retains its original status.

Procedure

Inform your system administrator. After the distribution model has been corrected with regards to recipient determination for object BUS2015 method SAVEREPLICA, you can save the document and then restart distribution or repeat the workstep that was canceled.

Procedure for System Administration

The system attempts to determine a recipient for object BUS2015 method SAVEREPLICA using the filter object types WHSE_NO. The system cannot determine a recipient. Define a filter object type WHSE_NO with a valid filter value for recipient determination for object BUS2015 method SAVEREPLICA.

[hemalatha-12]

Hi,

I am also facing the same error can some one help to sort it out?

[former_member836120]

Any body got the solution ?

[Ali_EDD]

This due to missing distribution model for your warehouse,

Go to the following path in SPRO : IMG ---> Logistics Execution ---> Extended Warehouse Management Integration ---> Basic Setup of Connectivity ---> Generate Distribution Model for Transaction Data Transfer to SAP EWM

Select the WM warehouse number, LS for EWM and Distribution Model View (usually EWM)... tick All and Create Entries.

[KoshelekovR]

Проверьте модель распределения bd64

Для BAPI InboundDelivery.SaveReplica должен быть установлен клиент вашей системы

[mikhail_shafiyeu]

Да, но EWM же присвоен собственной логической системе, даже если он embedded, верно?

[S_Sriram]

Hi Sai

Check this SAP note 2037820

Regards

SS

[barys_mikhno]

I found out that sometimes missing entries in table TBLSYSDEST can cause the issue if you have EWM setup in same system. It should be specified for virtual RFC destination EWM main RFC client as destination.