Opportunistic cross-docking not working

[former_member601401]

Hi All,

We are trying to implement opportunistic cross-docking process. My understanding is that during the creation of the goods receipt TO the system looks for any open picking TO and accordingly directly moves material from 902 to 916 storage type. The following configuration is done

1. For the warehouse opportunistic cross-docking has been activating by selecting option 4.

2. Cross-docking relevancy has been defined for movement type 101

3. For movement type 101, the 'Consider pre-allocated' check box is not ticked

4. In the respective movement types 1 & 2 for 'TO creation' are entered as screen control in movement types 101 and 601

5. No automatic confirmation for TO is set up

The following transactions are now done

1. Create a sales order with outbound delivery and TO created (not confirmed)

2. PO with MIGO (we are not using HU and hence no inbound delivery)

3. Now during the creation of the TO for the goods receipt, the expectation is that the system will look for the open picking TO and will cancel the same and then create the putaway TO directly from 902 to 916. But this does not happen.

Not sure if I am missing some setting or some transaction needs to be done differently. I went through SAP help but it does not give more details on what setting might be missing.

Regards,

Ketan

[JL23]

The docu actually talks about 8 prerequisites, and is quite detailed in the process

https://help.sap.com/saphelp_erp60_sp/helpdata/en/3e/49503e30a9d549e10000000a114084/content.htm

[former_member601401]

Hi Jurgen,

Thanks for the link. But I had already gone through it and configured the system accordngly. The surprising part is that corss-docking is working for outboud documents i.e. if i create a TO for inbound first and then for outbound then while creating the TO for outbound it automatically takes the source as 902 and cancels the put away TO. However for other way round where the outbound TO is first created and then the inbound, the expectation is that reverse should happen i.e. the destination in the TO should be taken as 916 and original picking TO should be cancelled. However it is not happening.

In the link it talks about points 5 & 6 which are only for HU environment and since we do not have the same I have not configured those. But my question now would be is it that opportunistic inbound cross-docking can only be possible with HU but not required for outbound. Else I do not see any other reason why this might be happening.