Cross Docking from a Factory

Hi all,
I´m doing a first approach to cross docking, So far what I read about it is that the goods are taken from goods receipt to goods issue without being placed in storage in the meantime.
My customer is a factory. They heard about the Cross Docking advantages improving the process in the Warehouse and avoiding storage and inventory tasks (they are using WM).
Iu2019m not sure if Cross Docking can be the way for improving the process of producing and sending to costumers without storing in the warehouse or there is a easy way to follow with not Cross Docking involved.
Thank You
Al

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

Similar Messages

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

RE: from PO allocation to cross-docking TO

Hi,
User created Allocation plan and convert to PO.
Before the stock arrives, how can I convert the planned qty and planned site into respective TO for picking when the stock arrived in the warehouse.
I am think about using cross-docking / Flowthrough features in WMS.
please advice
Bye

Hi ,
You can use crossdock & flow thorugh to ship inventory direct to shipping dock after you receive it.
When you do GR for these allocation TO can be created to direct to shipping location instead on bins.
Hope it helps
Jinoy

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

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 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 readily in ECC 6.0

Hi,
I am in ECC 6.0. I wanted to know if the Cross docking function is in.
Do I need to turn on any activation switch?
Someone, I am not able to locate any reference or folder for CROSS DOCK in the IMG.
I read up the SAP Help but cannot find the path to perform the configuration.
I also cannot find the sample storage type to reference. Is it true I will need to create a fresh storage type?
Can some one share?
Thanks

I have a standard setup/config for cross docking functionality. However, all the outbound deliveries are getting dumped in the Alert monitor with error "Del - Release time in past". I tried changing the delivery dates but no success.
Should I remove the object class (571), which checks for the Delivery release time, from the alert monitor? Any advice on how to fix this issue?
All responses will be rewarded.
Thanks !

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 functionality in SAP F&R

Hi All,
    I want to know how the cross docking functionality is handled in SAP F&R.
   Whether I should give RP type 11 in store level and RP type 01/02 in DC level for these cross docking products?
   Whether anyone has done the dynamic allocation functionality for cross docking products in which there should be an option to send the latest Order proposal values to ECC from SAP F&R so that STO s can be done with those new OP values?
Regards,
Resmi Raj.

Hi Eduardo,
Thanks for your reply. I have the similar scenario
Herein, we have kept relationship as mentioned below
Article: 100050
Store: FRS4
DC: FRD4
Vendor - TESTVEND1
For Vendor -> DC, we have maintained the distribution profile as FTM (Cross docking) and the RP type for article as 01
For DC -> Store, we have maintained RP type as 11
Now when we have updated the consumption data for both DC & store for the article at DC / store. We ran FRP for both DC (FRD4) and store (FRS4). The order proposal was getting created correctly for store, while no order proposal was created for DC as per the RP type.
Now, how is it being classified as a Cross docking scenario as we expect that the OP (STO's), once their inbound delivery is created, then they should be cumulated in ECC and generated a collective PO for Cross docking. Is that correct. Also, can you please let know the exact process to be followed for the same.
thanks
Best Regards
Prashant

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.

Cross docking in WM

HI,
can anyone explain about the usage of cross docking functionality and how to use it.
how to link an inbound docume

Hi Susil,
Cross-docking implies moving materials directly from the incoming to the outgoing physical areas of the warehouse. To process these materials without first putting them into storage, the warehouse must be aware of what deliveries are coming in and which deliveries are going out.
Inbound delivery helps in planning of incoming Materials in the Warehouse hence can make use of effective implementation of Cross Docking.
Cross docking can be monitored using Cross Docking Monitor. Details of the Cross docking monitor are well explained in the link below
http://help.sap.com/SCENARIOS_BUS2004/helpdata/EN/fc/efc43f82ab6d3fe10000000a114084/content.htm
Regards,
Ramakrishna

Cross Docking TO creation

Dear experts,
I am going for planned cross docking, I am able to successfully plan the documents (inbound and outbound deliveries) through LXDCK, but am not sure about what to do after this. After planing if post GR and go for TO creations it directs me for normal storage type instead of directing me to 916 (from 901). Pl let me know the sequence of steps after this. I have done all the necessary config as per my knowledge.
Pl reply on priority,
Thanks and regards,
Pranab.

Hi,
Planned cross docking enables two-step cross-docking, where goods to be cross-docked are first moved from the goods receipt (GR) area to a cross-docking storage type. The goods are subsequently moved to the goods issue (GI) area upon release of the outbound document. Hence after the system suggesting normal storage type, you need to transfer stock to cross docking area. Thanking you.

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.

Cross-Docking, Deliveries and availability check

Friends & Gurus,
From what I read, Cross Docking (ECC 6.0) works with deliveries. I can link an inbound to an outbound delivery so as soon as the goods are received they head straight to the outbound delivery.
If I plan to use X-Docking for stockouts, how can I link the deliveries if the outbound cannot be created because of availabity check (no stock on hand).
Question: Should I change the availability check of the outbound deliveries so I can create them without stock on hand in order to use X-Docking functionality?
Thanks stranger!

Hi
If you are talking about blocked stock you can remove the check for blocked stock in OPJJ transaction. this will make availability check will not consider blocked delivery
If useful reward points
Regards
Ranga

Cross-docking in RMS.

Hi,
Can anybody let me know how cross-docking works in RMS?
If a allocation meant for cross-docking is creates, does it have to be associated to a PO that time itself.
Thanks.

From the Allocations user guide:
Cross Dock: A purchase order is created that directs the goods from the
supplier to a warehouse where it is immediately allocated to the proper store
or warehouse.
From RAL you can generate POs (WhatIf-functionality), and for cross dock, the PoType should hence be set to CrossDock.
This will generate a PO with associated predist allocation.
I think that the allocation indeed needs to be associated to a PO, because it is a PO that is being cross-docked.
Maybe you can create the PO first, independently, in RMS, and then add later and allocation to it to define the cross-dock details.
From the RMS user guide:
On transfers:
Cross Dock: A purchase order is created that directs the goods from the
supplier to a warehouse where it is immediately allocated to the proper store
or warehouse.
For me it is not clear from the RMS user guide whether Cross Dock POs generate allocations to execute the move from WH to store, or transfers (transfertype=CrossDockPO), or that both may occur, in different business scenarios.
Hope this is somewhat helpful, can check my CRP notes later...
Best regards, Erik

Cross Docking from a Factory

Similar Messages

Maybe you are looking for