Cross Docking EWM

Hi Experts,
the chapter "Merchandise distribution cross-docking " of the EWM-Manual (EWM 7.0) says: "SAP ERP ... sends inbound and outbound delivery documents to EWM, which contain the process methods and the purchase order item as a reference. ... The merchandise distribution process in EWM corresponds to the process method in SAP ERP"
SAP ERP sends the inbound and outbound delivery via "SHP_IBDLV_SAVE_REPLICA / SHP_OBDLV_SAVE_REPLICA". Which of the data fields contains the process method (e. g. Merchandise distribution cross-docking )
Thanks!
Kind regards
Ralf

kishore yerra wrote:
Because your scenario is working manually the above may not be a major issue.
That's right. I've checked my settings, but this doen't seem to be the problem. As said, it works fine when creating WT's manually.
kishore yerra wrote:
the way we can try and diagnose this would be to deactivate your entries for storage type search sequence and try to retain only one entry that you used for cross docking.
I've changed the storage type search sequence for putaway, so that the only available storage type is the Goods Issue zone. The system now creates a WT for putaway in 9020. However, it doesn't link the stock to the outbound delivery order, so it actually acts like a putaway. So, this is not the solution unfortunately.
kishore yerra wrote:
Along with this put a closs monitor on SLG1 to understand the determination used when warehouse tasks are created.
SLG1 shows the following error message when creating the WT:
Immediate Actions Only: Condition Is Not Evaluated (Message no. SPPF_DET_CRM002)
it also displays one interesting warning message:
Action Merging: One Unprocessed Action with Equality Check (Message no. SPPF062)
I'm not sure what to do next; any suggestions?
Regards,
Oliver

Similar Messages

EWM Opportunistic Cross Docking issue - Its put away instead of 2121 - Pick

Hi
We have checked all settings, configuration for Opportunistics cross docking - EWM (SCM) set up.
Storage type search sequence, activity type, WPT etc
But while performing following steps we are facing the issue :
1: We create PO in ERP
2: Inb delivery in ERP
3: Read Inb del in EWM - PRDI
4: Perform Follow on task - WT creation and SAVE
5: Create Sales order and outb del in ERP
6: Read the docu in SCM - EWM
5: See MOnitor - for Inbound delivery status is Put away
Outbound SHOULD HAVE BEEN 2121 (WPT) with PICK, but still Put away GR is already performed.
Its 1021 instead of 2121 WPT..
Any pointers please ?

Jacob,
Yes, I after I posted that message I retested and it worked as I expected. The only downside is that any GR reversals for the production orders will go to COGI due to the fact that 901 no longer allows negative stocks, but this is not that big of a deal.
Thanks for confirming my thinking.
Jeff

Cross docking in EWM

Hi all,
We are trying to create a cross docking scenario in EWM. We are trying for the EWM triggered opportunistic cross docking. With all the suggested config settings and master data, the process is not happening. Can anybody share a config document regarding steps to be followed for Cross docking (in EWM).

kishore yerra wrote:
Because your scenario is working manually the above may not be a major issue.
That's right. I've checked my settings, but this doen't seem to be the problem. As said, it works fine when creating WT's manually.
kishore yerra wrote:
the way we can try and diagnose this would be to deactivate your entries for storage type search sequence and try to retain only one entry that you used for cross docking.
I've changed the storage type search sequence for putaway, so that the only available storage type is the Goods Issue zone. The system now creates a WT for putaway in 9020. However, it doesn't link the stock to the outbound delivery order, so it actually acts like a putaway. So, this is not the solution unfortunately.
kishore yerra wrote:
Along with this put a closs monitor on SLG1 to understand the determination used when warehouse tasks are created.
SLG1 shows the following error message when creating the WT:
Immediate Actions Only: Condition Is Not Evaluated (Message no. SPPF_DET_CRM002)
it also displays one interesting warning message:
Action Merging: One Unprocessed Action with Equality Check (Message no. SPPF062)
I'm not sure what to do next; any suggestions?
Regards,
Oliver

Transporttaion Cross Docking between EWM and ECC across company codes

Seceanrio is as follows:
We have an EWM managed site in GB, and an IM managed site in IE.
We would like to use the transportation cross docking solution from within Service Parts Management to transfer goods from GB to IE, (ECC > EWM > ECC) across company codes.
Is this possible within the standard SAP solution?
Thanks in advance,
Craig Bramhald

Hi Hari
Inter Company Purchase scenario works when the same material exists in both the company codes... I dont know how SAP would manage this in the case of Assets, when the Same Asset No is not existent in the other Co Code...
However, Refer 1523976 PurchaseOrderERPRequest_In_V1:Asset account assignment fails
This applies to EhP4 / EhP5 - But I dont know if you are using the enterprise service PurchaseOrderERPRequest_In_V1 ....
If not, better create an OSS message to SAP and check with them mentioning the notes that you have mentioned in your message
BR,Ajay M

TCD- Unable to send Cross docking documents to EWM

Hi Experts,
I am working on TCD scenario with ref. to a Sales Order without Storage Control. I am able to get pair of documents created in ECC (Inbound Delivery and Outbound Delivery). But these documents not able to get distributed to EWM. SMQ2 show the following error.
Could not determine a supply chain unit for ERP warehouse number KS1
Message no./SCWM/ERPINTEGRATION018
Diagnosis
The delivery document from ERP contains a plant for which Extended Warehouse Management (EWM) cannot
find a corresponding supply chain unit.
System Response
EWM does not create an EWM delivery document.
Procedure
Define the missing supply chain unit. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management -> Master Data -> /SCMB/SCUMAIN - Maintain Supply Chain Unit.
KS1 is my cross docking WH and this WH has SCU and maintained in above path and also has hierarchy maintained. As mentioned in error, Plant in delivery document is Plant1 (Supplying plant) and WH is Cross Docking WH.
Supplying plant has SCU maintained in EWM, otherwise my initial Outbound Delivery could not have got processed in EWM.
Please suggest what setting that I am missing.
Appreciate your help in this regard.
Thanks
Mahesh.

Hi Mahesh,
Check the attributes for supply chain unit.
Check Availability group table assignment table (under GR assignment in customization )
Regards
Suraj

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 Warehouse Task with status "B" - Waiting -

Hi All,
Does anyone have any experience with Opportunistic Cross Docking using SAP EWM 7.1? We have successfully executed OCD and EWM creates a warehouse task to move goods directly from GR to GI Zones but somehow the task is marked as waiting (B) and can't be confirmed through RFUI or using the GUI. Also this task is not assigned to a Warehouse order.
Looking forward to your inputs.
Thanks.
Y

Hi,
the configuration of the first storage type is:
The second type is configurated:
The third is:
The first warehouse task is from AKL1 to EAR1 and it works.
The second warehouse task is from EAR1 to EARE and here is the problem.
Best regards,
Rodrigo!

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 Docking with GATP

I am considering ECC WM and / or EWM. One of my requirements is an opportunistic cross dock that will assign goods at GR to an open sales order line item. EWM opportunistic CD is synonomous with PFGR. Does ECC WM provide any benefits over EWM in terms of cross docking with GATP?
Many thanks.
Michael

Have you received any feedback from SAP or from third party consultants that the WM to EWM connection is feasilble? The benefits of EWM to GATP vs. ECC WM to GATP are very big, however , I am not even sure that WM to GATP is a real option. That is why I ask.

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 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 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 !

Not able to link inbound to outbound in cross dock

Hi,
we have a warehouse managment setup in our project we are using cross dock process linking of my inboun delivery to outbound delivery. In my inbound delivery consits of 2 materials amd my outbound also consists of the same materials while i am going to connect this inbound delivery to outbound delivery. The inbound is giving all the materials and while the outbound is showing only one item cross dock monitor but the second item is present in outbound delivery but it is not displaying in the monitor tool.
Can any one let me know.
sunil

Can you give me some more inputs on this? I need to know exactly what is the role of ware house there? What exactly you are doing in cross docking? Are you shipping the material received through inbound process by just putting in another truck? What mvt types are used here both for inbound and out bound?

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 EWM

Similar Messages

Maybe you are looking for