Error when updating shipment from EWM to ERP

[former_member573898]

Hello EWM experts,

I am setting up the integration between S/4HANA LE-TRA and embedded EWM.

I have followed the guideline suggested by SAP for EWM as an add-on to ERP.

So far, the IDoc from ERP to EWM works perfectly fine.

The problem is when the GI is posted and the update is sent to ERP.

In the outbound IDoc, the system picks up the sender as ERP and receiver also as ERP logical system. In another word, the sender and receiver are the same.

This gives me a status error 029 in IDoc processing.

I have re-checked all configuration and find no unusual settings. From the partner profiles to the distribution model.

What could the cause of this issue?

[mengutu1]

Hi Tri Le,

Did you find a solution for this issue?

I am getting same problem.

Thanks

Tufan

[former_member573898]

Hello Tufan Mengus,

Unfortunately, I haven't found a solution to it even after debugging.

It is said in the documentation that with direction from EWM to S/4HANA, the system gets the destination system from the distribution model but that's not the case in the codes.

Anyway, I have ignored the issue since LE-TRA is not the target solution and our organization is investing more in TM from now on.

However, if you ever find out the answer, feel free to comment 😄

[steveliu678]

Hi Tufan,

Could you please share your solution if you have resolved this issue?

Thanks.

Steve

[former_member573898]

Hello Juergen Pitz,

I agree with you, embedded EWM is not the same as EWM as an add-on since the environment is different.

Nonetheless, SAP has not published much documents about configurations in embedded EWM.

I have checked the system integration between embedded EWM and EWM as an add-on and found that there is a huge similarity. So I think the same may apply to integration with LE-TRA.

I have configured the distribution model to send from EWM logical system to ERP logical system. The same error appeared.

As stated by SAP, for IDoc from EWM to ERP, the flow is still <ERP system> to <EWM system>.

As said, I have made the distribution model for both cases, ERP to EWM and EWM to ERP. Still, same error.

Probably because the 2 systems point to the same port??

[former_member573898]

Hello Juergen Pitz,

Regarding the business system, I only create 1 business system.

The embedded EWM can only manage stock of plants in the same client, as stated by SAP. This means there is only one ERP logical system to connect to. Hence, there is only one business system, which is set as own business system and connects to the ERP logical system.

The setting is similar to the deployment option where EWM is an add-on to ERP.

The business system is specified in the Define default values for IDoc Outbound as below

I understand that in decentralized EWM, the IDoc from ERP gets the ERP logical system from Define default values for IDoc Outbound. However, this is embedded EWM. It should be different.

Even if the IDoc is sending from EWM to ERP, the direction of the logical system is

<ERP Log Sys> --> <EWM Log Sys>

As regards the distribution model, I have created one according to instruction from SAP

Strangely, I did manage to set up the integration successfully in 1610 system. But that was a few years ago and now the system is long gone. There is no reference for me to re-check =))

There is a part below, in the guide that I don't fully understand

Does it mean to use the RFC destination named "NONE" or create a new one?

What is connection between the new RFC destination and the connection "NONE" if I'm to create a new one?

Do I need to create a new dummy EWM system for IDoc and assign the new RFC destination to the EWM system via BD97?

[JuergenPitz]

Hi,

That embedded EWM can only administer stock of one system is clear. But in a decentral EWM you always have (at least) TWO business systems, one for the ERP, and one for the EWM system. As you also need a dummy RFC destination for EWM in embedded EWM, I thought this might be true for the business systems as well. But I just checked in our embedded landscape, that seems not to be the case. So one business system only.

I would be careful to rely too much on documentation for EWM as add-on, this has a lot of different things then embedded EWM.

But what does look wrong for me is the distribution model you have in the one screenshot. While the documentation you quote says that the sender is the own logical system (the EWM system, because this distribution model is only for EWM direction ERP) and the receive is the ERP system, you screenshot shows as sender S17CLNT102, which is the ERP system, and as receiver the EWM system, S17EWM102, right? So I think this is the wrong way around.

Also in the very first screenshot you showed, the problem is probably less the recipient, but the sender.

Brgds

Juergen

[former_member573898]

Hello Juergen Pitz,

You are correct, the outbound IDoc is used only for updating the shipment in ERP.

GI message is transmitted via qRFC successfully.

Below is the status error in the IDoc.

Below is the setting in partner profile. This is embedded EWM so the recipient is the dummy system for EWM.

[JuergenPitz]

Hi,

ok, clearly a different problem then the one I wrote about.

How is that again with the business system settings in embedded EWM? You have two? Or only one? If two, what are your settings in "Define default values for IDoc Outbound"? Because here you enter the ERP business system.

And at least in a decentralized EWM you also need a distribution model, just from EWM to ERP. How is that in embedded EWM?

Brgds

Juergen

[JuergenPitz]

Hi,

the outbound Idoc is for updating the status in the LE-TRA shipment, yes? The GI posting is not done through the IDoc. Does the status say anything specific? Or just that it can not be processed? Because there is the common problem that this IDoc can not be processed. The issue is that the system tries to lock the outbound deliveries for setting this status - but at the same time the good issue posting is happening, so the lock can not be set, and the IDoc can not be processed. Can you process the IDoc manually? Then this should be what is happening.

There was a fix in a certain release, the IDoc was send with a little delay, and that usually was enough to solve the issue. The other solution is to schedule the report RBDMANI2, which will process the IDoc (I guess this is still true for embedded EWM, my experience with that is only in a decentralized environment).

Brgds

Juergen

---

Want to learn EWM?
Check for EWM courses @ https://training.sap.com/trainingpath/Applications-Logistics+Execution+%26+Warehouse+Management-SAP+...
Get a SAP Learning Hub Subscription: https://training.sap.com/shop/learninghub

And it is EWM. NOT eWM - Duh!
And if your question includes the word "transfer order" - do NOT tag the question with Extended Warehouse Management!

[steveliu678]

Hi Juergen,

How does the embedded EWM to identify the EWM link to more than one ERP system? Whether it is determined by the count of business system defined in the system? I see this is one snote explained error occurred once EWM linked to more than one ERP.

And for the IDOC to update the shipment’s status from EWM to S4HANA(my system version is S4 1909), if I modify it sender from S4HANA”s logical system to the EWM Dummy logical system, the IDOC will posted successfully.