EWM - Two-Step Stock Transfer via KANBAN : inbound delivery 315 not generated

[former_member524593]

Dear EWM and Kanban Gurus

I am currently working on implementing a two-step stock transfer via KANBAN (EWM managed)

http://saphelp.ucc.ovgu.de/NW750/EN/a6/a50a0b6aa54e338ba886f06d68b00b/content.htm

The target is to prepare & send a material from one storage location C011 to another C012 (same plant) via KANBAN (PK13n)

As per documentation i have configured :

Logistics Execution > Extended Warehouse Management Integration > Production Planning and Control > Define Delivery Type Determination

Production > KANBAN > Replenishment Strategies > Define Stock Transfer Strategies

I have generated PSA & PKMC control cycle with this stock transfer strategy.

Beginning of the process is okay

1. Go to KANBAN board, select container click “empty button” : OK
2. Generates outbound delivery in ERP : OK
3. Replicates outbound delivery in EWM : OK
4. Create & complete manually the warehouse tasks : OK
5. Post good issue from EWM : OK
6. Back to ERP (MMBE) stock if moved from unrestricted use to transfer (SLoc) : OK

As per documentation, system is supposed to set Kanban status to “In transit” automatically and therefore create an inbound delivery for production storage location (mvt 315)

However, KANBAN status does not change and remains “empty" – status 2 (red color).

Does anyone know why does this status remain unchanged? Seems that nothing happened after GI.

Thanks for your valuable support

Best regards

[vinaykumar_sharma]

Hello Guillaume,

Please suggest if you found issue for Inbound Delivery not created and Kanban Container status not changed.

I am facing exactly same issue.

Hello Aslam,

Thanks for help. Please suggest also.

Thanks ,

Vinay

[former_member788724]

Hello,

Please go through below blog if you are still stuck at inbound delivery creation.

https://blogs.sap.com/2022/04/06/2-step-kanban-stock-transfer-with-ewm-managed-storage-locations/#

Regards- ASLAM

[former_member788724]

Hello,

all the steps look fine except change of KANBAN status to FULL after 315 is posted. IBD distrubution is fine after SMQ2 error is resolved.

That is because of SAP Note 3134379. I will get the implemented and update the blog.

thanks.

[former_member524593]

Brillant !

Did you implement the two notes you were linking before to make it work ?

Best regards

[former_member788724]

Not yet.

Those notes I will take it later once I see KANBAN status is not green after GR.

Current issue-automatically created 315 IBD is stuck in SMQ2.

[former_member524593]

Thanks Aslam for reply.

These notes are talking about good receipts.

My issue occurs after good issues where system should generates inbound delivery.

I will anyway check these two notes to see if it might impact good issues.

Best regards

[former_member788724]

hello,

I have reached at a stage where Inbound delivery is created.

Also, Inbound delivery is connected to right PSA, so system won't follow normal put away strategy, rather will put away stock to PSA bin.

[former_member788724]

at a better position now 🙂

1- GI is posted for 313 OBD from EWM

2- KANBAN status is changed to in -transit automatically and 315 IBD is also created automatically.

Issue: But this is related with my authorization may be. 315 IBD is stuck in the queue (Error-No authorization for warehouse request or delivery and activity "Add or C). However, if I create 315 IBD manually then that is distributed to EWM successfully. Strange!!

I will try to check the SMQ2 access issue and complete the full cycle as soon as possible.

[former_member788724]

3132236 - No Update of Kanban Container Status after Goods Receipt for Inbound Delivery

[former_member788724]

Hello,

Please check SAP note

3134379

for KANBAN status change.

Please check if this is valid for your system.

[former_member788724]

Hello

Did you find solution for this?

I checked this. even after posting inbound delivery, KANABN remains in EMPTY status.

I created inbound delivery in MIGO by using option place into storage - Material document 313

May be we are missing some other setups. I noticed that inbound delivery created does not has PSA storage bin as destination. System follows normal put away strategy for the storage. This also does not look good as PSA should be the destination for the put away.

Do we need to activate some BC sets? Not sure.