Inventory in ECC is not updating against STO, after Goods issue in EWM

[Former Member]

Hi Experts,

Pls throw some light and give me inputs in solving my issue.

My Scenario is STO (Plant to Plant within comp.code) integrated with EWM:

1. Created STO: (Supplying plant/sloc and Receiving plant/sloc are EWM managed)

2. Created Outbound delivery: Distributed successfully to EWM

3. Done the all activities in EWM like Picking, Loading & Goods issue

4. In ECC stock is not reduced and no update of Mat.doc/indbound, and still the ECC Outbound delivery is in open status

5.If I want to try post MIGO wrt Outbound or STO PO is also not possible as my Outbound delivery is greyed out (once its distributed, its not allowing to change).

Thats how I got struck. Dont know what to do, If I am right I followed the correct process.

Thanks to All

Srinivas

[former_member331951]

Hi Sreenivasa,

1. The issue with updation of stock back to ECC could be because of some missing links/ config. You will have to check this in SMQ1/ SMq2/ SLg1 as suggested by Shriharsha. You can post a screenshot of the log in case you need more help on this.

2. You can setup automatic creation of inbound delivery for replenishment deliveries. System creates an inbound delivery in the receiving plant with respect to the outbound delivery based  on output determination procedure. To enable this, maintain output type SPED in the output determination procedure assigned to delivery type NL.

LE --Shipping -- Basic shipping functions --Output Control --Output Determination --Maintain Output Determination for Outbound Deliveries

Based on the above setup, system will automatically create an inbound delivery in receiving plant when you post GI in the supplying plant. You can then complete putaway activities in the EWM receiving plant wrt this inbound delivery.

Regards,

Smitha

[Former Member]

Thanks for Smitha & Harsha on your reply,

I didn't see any logs in SMQ1, SMQ2 & as well as in SLG1 in both the system, seems Inbound delivery is not creating and the status of the  Outbound delivery shows as "Open". I will check the Output determination mentioned by Harsha and check if it goes.

Trying to execute the VL71 in debug mode to see what is missing.

Thanks

Sreenivas

[Former Member]

Hi Sreenivas,

If you don't find the entries in the logs or queues, also check the PPF tab of the delivery. What is the state of PPF action, is it successful? If no, then the PPF log will provide you the error details. I suspect if no stuck entries then it should be problem with the PPF.

regards,

-Harsha

[Former Member]

Hi Harsha,

I have checked the PPF in Outbound delivery, everything looks in green. If I am right the Send ERP message is in green, but in the Container instance nothing is there. Not sure what should it show. pls below is the screen shot.

In other way, we have executed the VL71 to trigger the automatic inbound delivery and found the status of Outbound delivery is open and when we changed that to "C" the document got created. So here my question is Why its not changing automatically after goods issue.

You said there could be an issue with PPF, could you pls let me know in which PPF I should check and do correction.

And one more point I would like to bring here, I am getting the error "Goods issue is not carried out yet" when I am trying to execute VL71 with an outbound delivery for which goods issue was already done in EWM. see the below screen shot

Thanks for the replies

Srinivas

[Former Member]

Hi ,

I am also facing the same to inbound delivery creation .

Are you able to get to the end of the issue so far, please let me know any  additional config

you have done apart from the setting above .

Refer to the below screen shot for more info .

Not sure what is the next step as I have done all the necessary config .

Please help

Thanks

Richard

[Former Member]

Hi Srinivas,

This gives me an idea that you delivery document may be stuck in either inbound queue of ECC(smq2) or outbound queue of EWM(smq1).

In both the queues search first with the delivery number in the stuck queue entries. Once found, check why queue was stuck and then reprocess the queue.

Regards,

-Harsha