Cross docking process with SD

Hello Experts!
I woukd like to know the impact of the crossdocking process in ERP without WM and only with SD.
Which movemens are made in SD?
How the system responds only with an SD process with sales order -> outbound delivery when we have an cross docking process?
Thanks
Lina

Hi Lina,
Refer to this link, hope this will help.
[Cross Docking Customization|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/business_maps/guid/eg1slxvyat1odhrwoi8vc29sdxrpb25jb21wb3nlci5zyxauy29tl3nvy292awv3l21jcgdl%0d%0adc5hc3a/cgfja2fnzwlkpsz2awv3pxnty3jlbmrlcjimawq9otq3mdy1mufenzg4ndc0otgzmeu1%0d%0aotlbq0y0ntreouumjnhzbc1iyxnlpwh0dha6ly9zb2x1dglvbmnvbxbvc2vylnnhcc5jb20vc29j%0d%0ab3zpzxcvbwnwz2v0x21pbwuuyxnwp3vybd1zzg5fbmv3lyymd2vilxvybd1odhrwczovl3nvbhv0%0d%0aaw9uy29tcg9zzxiuc2fwlmnvbs9zb2nvdmlldy9ty3bnzxrfbwltzs5hc3a/dxjspsymehnslwxp%0d%0ac3q9c2rux2dlbmvyywxfcmvuzgvylnhzbhq7c2rux2xpbmtyzxdyaxrpbmcuehnsddtnzw5lcmf0%0d%0azuhutuxfu0rolnhzbhqmjnbhy2thz2utawq9jizyzxnvdxjjzxr5cgu9c2rux3nvbhv0aw9ux2nv%0d%0abxbvc2vyx2z1bgxwywdljizwyxjlbnrssuq9l2j1c2luzxnzx21hchmvnkjfody2rjk5oeiwney4%0d%0anjlbnzc4mzm4mungqtcxnzavrdgzoda5qkq5ntbbndzfqke1mzk1mja3rjy4mzmxruivm0e2njc4%0d%0aqzzgmerendddnkjfmjkzmja4q0y0ouixruyvrja5n0uyquexmjzenejbodhbnde3meq4mevdrkmw%0d%0amjivmjjcotjgqza1otlenenfmeeyrtuwnzayrkqwmdi5qzeueg1sjiz0axrszt1dcm9zcybeb2nr%0d%0aaw5njiz2axj0dwfspxrydwu=?prtmode=default]
Thanks,
Raja

Similar Messages

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

EDI for cross docking process (pull and push)

We need to send in the EDI process, the allocation by store information to the vendor using pull and push process.
When we have pull process, we can do some enchacement in ORDERS IDOC, by the push process, somebody knows what IDOC we can use to send this information to vendor?
Regards,
Laura Yunaka

Hello,
Order information is sent to vendors using IDOC type ORDERS05 with message type ORDERS/ORDCHG (Create/Change).
Thanks,
Venu

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

WM cross docking

Hello WM expert,
Can anyone please explain i details step by step process of Cross docking along with required customization.
Regards,
Charu

Hi,
Kindly refer the process flow in the below link.
http://help.sap.com/scenarios_bus2004/helpdata/en/fc/efc43f82ab6d3fe10000000a114084/content.htm
regards,

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

RLM - Error at MIGO (Cross Dock) for supply process Stock / Non Stock

Hello Friends!
I am experiencing a strange error at time of MIGO for a RLM Stock / Non Stock supply process. I believe it could be due to RLM's effort in creating a (Cross Dock) Delivery in the background.
Error details: 'Enter a material or an item category' -- Message no. VL383
Please help!. Thanks!

Hello Friends!
I am experiencing a strange error at time of MIGO for a RLM Stock / Non Stock supply process. I believe it could be due to RLM's effort in creating a (Cross Dock) Delivery in the background.
Error details: 'Enter a material or an item category' -- Message no. VL383
Please help!. Thanks!

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.

Cross-docking in WM with use of MIGO

Dear SAP experts,
I'm looking for my company to install cross-docking in SAP ECC6.0 were they use MIGO to do the goods receipt. Which are the possibilities I have to active/setup cross-docking in SAP based on MIGO receipts?
Many thanks for your help on this one,
Michael

Dear experts,
Is it possible? Can I make use of cross-docking in standard SAP without the use of inbound deliveries?
Many thanks for your help!
Michael

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

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 process with SD

Similar Messages

Maybe you are looking for