Hi,
I have the following business process:
PO is created in ECC -> EGR is distributed to EWM -> Inbound Delivery is created in EWM -> GR is posted in EWM -> Stock is put into final storage bin
(ECC 6.0 / S/4 EWM 1909)
Now I need to create ret...
Hi,
on decentral S/4 1909 EWM I get a lot of warnings in SLG1 with the following message even though we use ALE and not DRF:
No configuration found for replication of business object 194 (Produkt)
This only occurs in the production sys...
Hi,
I have a strange issue on S/4 EWM 1909 regarding material number length. Material master is configured to be 18 chars long.
When I read an EGR document via delivery service provider the material number is 18 chars long even though the underly...
Hi,
I'm triggering WM staging on a released production order in ECC. WM staging is successful but there is no PMR created in the decentral S/4 EWM 1909.
WM staging protocol shows no errors. SLG1 shows nothing.
I have stopped the outbound queue ...
Hi,
I'm trying to trigger WM-staging for a production order in ECC to distribute a PMR to a decentral S/4 EWM but I get the following error:
"No Receiver maintained in the distribution model for warehouse 980"
The distribution model looks as...
I guess I found the answer:|{ xyz ALPHA = IN }|This is the embedded expression for the conversion exit CONVERSION_EXIT_ALPHA_INPUT which operates on the underlying data type,What is used for converting the Matnr according to the specified settings in...
Alright, this is going to be rather embarassing, but maybe someone in the future is as dumb as I am and will find this answer helpful:I was concentrating so much on debugging the WM staging code and wondering why, after seeing the success message, th...
Hi Juergen,BERKZ in the control cycle is set to 5 (EWM staging) and distribution model looks as follows:From debugging I know that the right distribution model and receiver is being determined.Regards,Tim
So I finally was able to solve this problem, unfortunately the error message is very misleading.The problem was not that NO receiver could be determined, but that too many receivers were being determined. This happened due to no filter being maintain...