EWM WT immediate confirmation and LOSC

[ales_knor01]

Hi, I have putaway process from production with multiple LOSC steps A->B->C->D. Everything is working as it should. The problem comes when I want the first step to be confirmed automatically. When I set the warehouse process to confirm from A to B wt immediately, LOSC does not work. I understand this because the LOSC logic is called when the wt is confirmed and in this case the wt is created as confirmed. I can run a job to confirm wt in the background but I'm looking for a more elegant solution. Any idea is welcome..

[Eckhard_Siefer]

Hi,
without knowing the details about your layout of the warehouse, but if Step A to B can be confirmed automatically, then why have it in the first place?

Just wondering about what reason is making this step necessary in your process, if it may be confirmed automatically.

Best regards

[ales_knor01]

Hi, In this case, the output from the production line is connected by a conveyor to the automated warehouse. Point A is GM bin, B is MFS ID point and C is next MFS communication point. Before HU arrive at point B I need to send HU destination (B->C or B->X) to MFS PLC. I don't want to do the goods receipt straight to the MFS entry point.

Best regards

[laurinpaulschlereth · Accepted solution]

Hi, we faced a similiar issue with the standard auto-confirmation. We implemented BAdI /SCWM/EX_CORE_CR_POST and call function /SCWM/TO_CONFIRM in RFC mode. May not be the best option but it works and the performance is good.

[ales_knor01 · Accepted solution]

Thank you! I thought the same thing, but I wasn't sure if it was possible. I was worried about wt being committed in the database before confirmation in update task.