Auto TO Confirmation

[Former Member]

Hi Experts

We are implementing IS Retail Solution and using STO for sending goods from Store to Distribution Center. STO generates a Outbound delivery which further generates TO. This TO is getting Automatically confirmed. As per my understanding Auto TO Confirmation setting is at movement type level in WM. I have made all the changes for no Auto TO confirmation at movement level, but still it is happening. We are using movement type 641 for STO from Store to DC.

Please tell me where should I make the changes to stop Auto TO confirmation.

Thanks

Manav

[Former Member]

There was some table overwrite in background due to which it was happening. I created a new movement type and it started working correctly.

[JL23]

in OMLX you define if the confirmation indicator is proposed

[Former Member]

Already made changes in OMLX but still of no use.

[JL23]

what exact did you do there?

[Former Member]

I checked separate confirmation at warehouse level, checked confirmation at putaway & stock removal at storage type level and removed checks for confirm immediately & Propose Confirmation at movement type level. I have already done these changes but still TO is getting confirmed immediately at the time of creation.

[JL23]

remove 'EQ' and 'RC' checkboxes in storage type contrl config of your warehouse and try again

[Former Member]

It did not change anything, still TO is getting confirmed immediately.

[JL23]

can you describe a bit more the process around TO from creation to confirmation, what transactions you use and what you do in detail.

[Former Member]

We are using following transactions:

ME21N for STO creation

VL10B for delivery creation in background

TO gets created automatically by Delivery and gets confirmed. It should get created but not confirm. Delivery is getting created as we have assigned delivery type to document type for STO. Further movement type 641 (which is in delivery) is assigned to WM movt type. WM movt type is configured for no immediate auto TO confirmation at creation. So really confused as what is triggering the TO confirmation.

[JL23]

do you do VL10b manually or is there a job that does this wihtout any interaction of a user?

The delivery does only create a TO automatically if there is a message type WMTA in your delivery.

If that is not the case, then you may have a report in the system that does this creation and confirmation more or less hardcoded.

[Former Member]

VL10B is run manually by user. Message type is WMTA for delivery type and there is no background job run to confirm TO. TO needs to be confirmed manually using RF guns in the Warehouse.

[JL23]

are you using decentralized warehouse?

[Former Member]

no

[JL23]

Actually I run out of ideas.

Just a last question:

can you confirm that you did the changes in OMLX for the correct warehouse?

I would not ask this question, but I often saw that one is just searching for movement types, and forgets to look at the warehouse number left of the movement type. (Each warehouse has its own movement types)

[Former Member]

To be true I have also run out of ideas that why is it happening. I did changes in the correct warehouse at movmt type level. I am stuck in this for past 3 days and even after doing everything what SAP says and does I am not able to get the desired results. So do tell me if you have something in ur knowledge treasure which I may have missd.

[JL23]

debug, to find out from where SAP gets the autoconfirmation while creating the TO.

[Former Member]

Debug what? There is no custom transaction or development done in whole process.

[Former Member]

Did you check the setting at IM-WM integration ??? i mean where we assign the IM movement type to WM Movement type ..

In the Immediate TO creation colum see if option A is selected ..

Thanks

rahul

[Former Member]

Yes I have checked the settings at IM-WM interface for movt type. It is correctly assigned. No Auto TO confirmation is working for one Site and not for others. Whereas all of the sites are same in all configurations at WM level.

[JL23]

you can even debug a SAP standard program to find the root cause.

[Former Member]

Ok I have never done that in the past. Let me try that also, in the meantime if something pops up in ur mind then please do share with me.

Thanks

Manav