System ignoring cross-docking decision during LT0F

Hi all,
I'm trying to do some planned cross-docking between and inbound delivery and a TR for production supply.
I've created a CD decision which is sitting there waiting, however when I create the putaway TO via LT0F for inbound delivery, the TO is created ignoring completely the CD decision which is linking that delivery item to the TR.
Any suggestions - and please don't just post a link to the SAP help prerequisites - I've already been through this!
Regards,
Mark.

HI
The second point says that the quantity in inbound delivery and outbound delivery should same as Pallitization data maintained in the material master WM 2 view(LE quantity)or multiples of it.
If you have a quantity less than the Palletization Quantityin the deliveries then the deliveries will not appear in the Cross dock moniter.
LE quantity: 20 in the material master
your deliveries qty should be 20 or multiples of 20.
please try with this.
Regards
Srinivas

Similar Messages

WM: opportunistic cross-docking

Hi all,
According to my understanding of the help.sap.com online documentation, we are NOT supposed to use the Cross-docking Monitor while trying to achieve an opportunistic cross-docking stock transfer between an inbound delivery and an outbound delivery. Once we appropriately complete the Customizing, the system is supposed to generates BY ITSELF a cross-docking decision during the process of TO creation (after the arrival of the incoming stock or release of the outgoing document).
Am I right ? Up to now, I can't achieve it...
I've checked my Customizing several times against this documentation these last days. According to it, there are two points of view regarding the creation of the opportunistic cross-docking decision:
- either the system does it by itself (= killing the Outbound delivery TO, modifying the destination of the Inbound delivery TO and updating related documents);
- or involved Inbound and Outbound deliveries must be manually designated for cross-docking throught the use of the monitor (like it is necessary to create Planned cross-docking decisions).
So, my questions are:
1. Do we need to manually designate Inbound and Outbound deliveries candidates for cross-docking using the monitor in order to create an opportunistic cross-docking decision?
2. If so, how can we automate the creation of the candidate designation?
Thx in advance for valuable inputs!
Edited by: al7sap on Oct 22, 2008 5:23 PM

Hello,
For Oppertunistic Cross dock..
You need to create either Putaway TO/Pick TO and then system checks the cross doc and cancel the TO and create a new TO from 902 to 916. and also updates in the document flow. This you can do with out Cross dock monitor. With out planning the cross dock you can do the cross docking by following the config in help.sap.com.
for more information about the complete config you need to see the sap link below. sure it will help you.
http://help.sap.com/saphelp_erp60_sp/helpdata/en/c6/f85c504afa11d182b90000e829fbfe/frameset.htm
thanks.
tkreddy

Cross-Docking Config.

I am working on Cross-docking scenario in ECC system and I am stuck at "Generating a Cross-Docking" Decision. This is the 6th step as per Best Practice GZ6.
What are config settings that should be maintained to generate a decision?
I have maintained General Settings of Cross-docking at WAMS and got stucked at Monitoring settings.
Kindly help.
Thanks!
Abdul Saleem

W71 is a BPP for executing Opprotunistic Cross Docking and, quite frankly, I found it makes no sense at all. It has a step to create an Outbound Delivery using MB1A - VL10B is usually used to ccreate and Outbound Delivery. MB1A just creates a Goods Issiue. The same applies the the step for creating an Inbound Delivery - MB1C??? That creates a Goods Receipt - not a Delivery.
The best I've found for actually setting up Cross Docking is:
http://help.sap.com/erp2005_ehp_02/helpdata/en/3e/49503e30a9d549e10000000a114084/content.htm
http://help.sap.com/saphelp_rc10/helpdata/en/6f/dadd4424b711409384ce2382728f57/content.htm
Even still, I have run into a problem allowing the Goods Receipt of an Inbounde Delivery prior to confirming the WM Transfer Order. The steps in the config doc show where it should be set, but it is in the Handling Units section of the IMG. The documentation implies this should work for non-HU receipts as well. I keep getting the error that the GR cannot be completed because the WM TO is not complete.
I'm still looking for an answer to this.
Jim

EWM Opportunistic Cross Dock

Hi All,
I am doing the following scenario and I have all the config and master data setting that is needed to do cross dock.
This scenario is cross dock from the Inbound side
1. Create Sales order for qty 10 in ECC and that is replicated in EWM.
2. Wave the ODO in EWM and that creates an WT to pick 10 qty from the GNL location. The WT is still open and I did not confirm it yet. The WT has source and destination HU determined. The WO has Queue assigned based on Queue determination
3. I now create an Inbound delivery in ECC for same prod and Qty 10 and it is replicated in EWM.
4. In EWM, I pack the qty 10 in a HU and then I do a 'Goods Receipt' to the GR-ZONE. I don't have a POSC
5. Now I am manually creating a putaway WT for the ID.
Now this is where my problem is. I was hoping that system will cross dock this inbound delivery with the outbound delivery and in doing so, it will cancel the open Pick WT that was created for the ODO and will create a new cross dock WT but system did not do so. It is creating a direct putaway WT to the GNL location.
ALSO, this process works when for the ODO, I do not create any open WT. In that case, during putaway WT creation it is cross docked.
So the question is, does EWM consider open WT's during XDock? In some texts, SAP writes that the open WT's will get cancelled and cross docked but that is not happening.
Thanks for your inputs and help
James

Hi,
EWM can cancel an open pick WT. What it says in the docu is " If open pick warehouse tasks of this kind exist, EWM cancels these without violating the FIFO principle."
Well, in reality it is not that simple. First of all the open WTs must be RF relevant (you wrote you have a queue, but it must be an RF-queue (which I suppose you have)). The other thing is the question with FIFO. Now it does make sense that EWM does not cancel a WT if the already assigned quantity is older then the one you have in the GR zone. But what acutally happens is that the system checks the goods removal rule being used for the open WT. If this one uses the GR date or the SLE date, then the system does NOT cancel the WT. This is part of the standard BADI implementation you have to have to CD. And this is where you have to put in your own logic.
Brgds
Juergen
Want to learn EWM?
Check for EWM courses @ https://training.sap.com/curriculum/scm_ewm
Get a SAP Learning Hub Subscription: https://training.sap.com/shop/learninghub

Opportunistic Cross-Docking Quantity

I am sorry if I cannot test this, but we need this information in order to make the recommandation to acquire EWM. We do not have it yet.
Here is the question : in the SAP documentation:
http://help.sap.com/erp2005_ehp_02/helpdata/en/3e/49503e30a9d549e10000000a114084/content.htm
Point 4.a.ii in the process flow says that " TO item contains the same material, quantity, plant and storage location as the putaway TO item to be created."
"SAME QUANTITY" is what I do not understand.....
If I have 3 open Picking TOs (quantity of 1 for each) for a material and I receive 5 on a PO, will the system create one putaway TO (quantity of 1 ) for each of those 3 open picking TOs ( to Goods Issue Area) and one Putaway TO ( to storage area ) for the 2 remaining ?
We are a manufacturing facility and we need to replace a system that cross dock everything missing or due in the short term when we receive.
Thanks,
Alain

Hi,
As per what I have observed, cross-docking happens in case of Full pallets. Usually TOs are created to pick full pallets or partial pallets. Also receiving happens in terms of Full pallets or partial pallets. If my receiving quantity is a full pallet quantity, then in case of opportunistic cross docking(Inbound to Outbound), it looks for possible open Pick TO items with same quantity(full pallet), cancels it and creates a cross dock TO from GR area to GI area for that outbound delivery.
Hope that helps.
Thanks
Vinod.

Cross dock

HI
While executing Cross docking decision in cross dock monitor the error " NO inbound documents have been selected for planning " is displayed. request suggestions
Thanks and regard
vivek

Hi Vivek,
For cross docking decision you must have an Inbound delivery whose GR has been doen, but not the Putaway. If you don't have such a delivery then it will give you the error mentioned by you.
please check if you have done this step in your execution.
Shailesh

Setting Time for decision in Cross docking opportunistic

Hi, Gurus, I have a request for you.
I have configure Cross Docking Opportunistic and it is working fine.
Now, I need the Cross Docking decissions to be taken only during 20 minutes. If there is not any candidate doccument during this time I want to release the plan doccument for doing Cross Docking any more.
Anybody knows how to configure this?
Thanks,
Al
Edited by: agmogena on Dec 27, 2011 10:38 AM

Solved, I need to use a BADI ZLXDCK_CROSS_DOCK

Cross-docking with external WM system

Hello Gurus,
We are trying to implement cross docking but we donu2019t have wm on the SAP ERP. We would like to know if this is possible. And this is possible, how can we manage this scenario for example: A delivery from PLANT A to a client that uses PLANT B as cross-docking plant. When the shipment leaves PLANT A what movement we need to do. When the materials of the delivery are received on PLANT B what movement should we do. When the shipment leaves PLANT B we make the goods issue?
Is this correct? If this is correct you have to change the plant of the sales order and delivery from PLANT A to PLANT B.
Best regards,
Tiago Magalhães

Managed by process not by any configuration.

Opportunistic cross-docking not working

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

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.

Cross Docking for stock category Q (inspection stock)

Hello everyone,
My client uses cross docking in 4.7 release and recently a requirement came up where they wanna be able to cross dock stock received from production while the User Decision from QM is still pending.
I have tried to walkthrough the code behind planned/opp cross docking and realised that only available stock is taken into consideration.
I d be really grateful if anyone could suggest how to best approach and tackle this issue? Please consider that the quant should not lose the inspection lot number so that once UD is given, the stock category changes automatically.
Thank you
Kind Regards

Yes it is possible. In the IM/WM interface tables, in the second table, you can vary the process according to stock status. See the third column.
LogisticsExecution \ Warehouse Management \ Interfaces \ Inventory Management \ Define Movement Type
Following is the config. help text for the field
Special Stock Indicators for Whse Mgmt
Use
In the Materials Management system you can post different transactions using one movement type. For example, posting goods receipt to unallocated stock or goods receipt to
stock in quality inspection.
These transactions are treated differently by the system on the basis of this indicator. Together with other indicators of a movement type in the Materials Management system, this indicator is used to correctly allocate a movement type in the Warehouse Management system so that the transaction can be posted accordingly.
Regards,
Nick

Cross Docking with LE-WM - or - Reactivating Back Orders upon Goods Receipt

I have been reviewing the documentation for Opportunistic and Planned Cross Docking in LE-WM. The requirement is to release Back Orders upon receipt of a shipment to avoid putting them away and picking them right away from the bin. We want to release the Back Orders for picking in the GR area at the time of receipt.
So far it appears that Opportunistic Cross Docking depends on a Transfer Order already existing. The system then cancels the existing TO and replaces it with a TO to pick from the receipt Storage Type.
Planned Cross Docking appears to require an existing Outbound Delivery to the expected Inbound Delivery.
In the case of a Back Order, no Outbound Delivery or Transfer Order exist since there is no stock to release until the goods are received.
Is there a way to release Back Orders to be picked directly from Goods Receipt?
Thanks;
Jim

The problem is that all the information I found so far about it is over the process of external goods coming and sending they out without the need of storing in the warehouse. They go directly to the picking area (one step) or in two step process going first from 902 (Good receive from external) to Cross docking Sorage type.and another movement from Cross Docking Storage type to 916 Good issue Storage type.
I need to know if it is possible to implement a solution of Cross Docking for certain number of products having a factory and a warehouse. If so, would you give me a brief process flow?.
Thank You very much.
Al
Edited by: agmogena on Aug 22, 2011 12:01 PM

Cross Docking in SAP R/3 ECC 6.0

Folks,
I'm struggling to make 2-step w/ planned cross docking work. Basically, unable to connect the planned with the candidate document.
Here is the scenario:
1. (Candidate) Outbound delivery created with a delivery date / time of 09/04/08 - 10:00 (No TO initiated)
2. (Planned) Inbound delivery created with a delivery date / time of 09/04/08 - 12:00 (No TO initiated)
The system invokes different messages based on the following config. settings: (These messages occur when I right click on the inbound delivery and select "plan cross docking")
Setting 1:
Planning time: 1 D
Default Release: 1D
Def Latest Release: -
Message: No inbound documents have been selected for planning
Setting 2:
Planning time: 1 D
Default Release: 1D
Def Latest Release: 1D
Message: Time ref. 09/04/2008 10:00:00 of plan.doc. xxxxxxxxx does not match cand.documents time refs
BTW, it's a simple setup WITHOUT transportation, yard management, HUM or SUT.
Thanks in advance for your valuable comments!!

Dear Christiane,
First & foremost appreciate your quick response.
As per what you say (& If I have understood it correctly) having the Delivery Date & Time of the Inbound as 09.04.2010 10:00 would solve the issue ? I did change the Inbound Delivery time but to no avail.......as per my example.....what do you think should be the Inbound/Outbound Date & Time
If I understood right, as per my example, the Outbound Delivery time is set to 12:00, the latest release time is set to 1 hr thus the latest time for the outbound to be released is 11:00 (Outbound Del time - latest rel time)
Planning time is again 1hr, so planning window is from 10:00 to 11:00 - [(Outbound Del time - latest rel time) - Planning time]. Hence if I set the Inbound time to 10:00 it should work right ?
The release time, what effect does this have ?
Looking forward to your help.
Imran

Cross docking

Gurus,
How does the system identifies materials are subjected to cross docking?
Regards
Sid

Hi Vineet,
I have maintained the setting you have mantioned. However I get an error when I try to plan the document in cross dock monitor.
No inbound documents have been selected for planning
or
No outbound documents have been selected for planning
I am wondering, when we can see both the inbound and the outbound document in the monitor, why can we plan them. I have tried all sorts of permutation and combination in the configuration but it never seems to work.
Can you please guide me, how to find a solution for this problem.

Cross Docking Process Flow - ECC6.0

Hi,
Can some explain what is the process flow for cross docking in ECC 6.0. How to mark a customer as Cross docking customer?
Thi sis the process flow we are trying to map in ECC6.0 for croos docking.Please let me know is this process flow can me mapped in ECC? Thanks
     Goods Receipt
     X-dock temporary bin allocated
     Put-away label printed [X-dock put-away bin]
     Delivery created
     Picking TO created
     Picking TO confirmed
     Packing created
     Delivery Note printed
     Shipping labels printed
     Post Goods Issue posted

Hello,
For Oppertunistic Cross dock..
You need to create either Putaway TO/Pick TO and then system checks the cross doc and cancel the TO and create a new TO from 902 to 916. and also updates in the document flow. This you can do with out Cross dock monitor. With out planning the cross dock you can do the cross docking by following the config in help.sap.com.
for more information about the complete config you need to see the sap link below. sure it will help you.
http://help.sap.com/saphelp_erp60_sp/helpdata/en/c6/f85c504afa11d182b90000e829fbfe/frameset.htm
thanks.
tkreddy

Cross Docking Pick TO cancellation

Hi Experts
I am trying to Configure the Cross docking scenario
I have configured the following
1. Cross-dock Warehouse level customization in SPRO-LE-WM-Cross Docking-Maintain Warehouse level Settings
2. Cross dock relevancy for movement types in SPRO-LE-WM-Cross Docking-Define Cross docking relevancy for movement types
3. There is no Pre-allocated stock check for both movement types 101 and 601
4. Stock placement and stock removal confirmation required for storage types 902 and 916.
Transaction Steps:
1.Outbound delivery, TO created
2.Inbound delivery created, GR done, while creating Putaway TO system is moving the stock from 902 storage type to 916 storage type
But the pick TO created against the Outbound delivery is not cancelled and the Outbound delivery is not updated with the Putaway TO.
Which step or config i am missing?
Regards
Venkat

Hi, you have two options to configure cross-docking. Take a look at these documents for detailed explanation.
1) Planned Cross-Docking
Planned Cross-Docking - Cross-Docking (LE-WM-DCK) - SAP Library
2) Opportunistic Cross-Docking
Opportunistic Cross-Docking - Cross-Docking (LE-WM-DCK) - SAP Library
I figure you are using opportunistic xDck based on your question.
Could you just go through all the steps on the document I linked?
Just go through all of the requirements, carefully inspecting if any
of those doesn't match the process.
First you have the settings required. Make sure they are OK.
Then check the process flow and your documents you are testing
with.

System ignoring cross-docking decision during LT0F

Similar Messages

Maybe you are looking for