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

Similar Messages

  • Cross Docking Functionality - ECC6.0

    Hi,
    Can some explain in detail what are the Cross Docking Functionalities has been provided in ECC 6.0 compared to the previous versions.
    Thanks,
    Chak.

    Hi chakku,
    Cross docking changes in ECC 6.0.
    Effects on Customizing
      To use Cross-Docking, you must define the following in Customizing for
      Logistics Execution -> Warehouse Management - Cross-Docking:
      o   General warehouse level settings, including the cross-docking
          storage type, outbound document release and latest release times,
          and FIFO tolerance duration.
      o   The relevancy of cross-docking for warehouse movement types
      You also have the option of personalizing the monitor and alert monitor,
      as well as implementing project-specific logic via Business Add-Ins.
    See also
      o   IMG for Logistics Execution -> Warehouse Management -> Cross-Docking
      o   SAP Library for Logistics Execution -> Warehouse Management ->
          Cross-Docking
    Regards,
    hareesha

  • 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

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

  • Cross-Docking and VAS

    Hi All,
    I'm wondering if anyone has experience working with both Opportunistic/Planned Cross-Docking and VAS directly in ECC.
    How do they integrate with each other?
    At my client we are going to use VAS to handle repacking at GR at storage type 923. After the VAS task has been completed and the second TO is created for the putaway, I'm hoping this will trigger cross-docking (either OCD or PCD).
    Is anyone else doing this - are my expectations correct?
    Regards,
    Mark.
    Edited by: busaboy99 on Feb 6, 2012 5:05 PM

    Hi,
    Explore following URL
    Collective Purchase Order
    Bye,
    Muralidhara

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

  • 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

  • Cross-Docking using ECC 6.0 SP12 - How to configure?

    People,
    we are using ECC 6.0 SP 12 and we would like to configure Cross-Docking.
    I cannot find the option in SPRO:
    Logistics Execution -> Warehouse Management -> Cross-Docking
    I believe this configuration path is related to SP 14.
    How can I configure it in SP 12?
    Thanks a lot!

    We are using the versions:
    EA-APPL     600     0010     SAPKGPAD10
    SAP_ABA     700     0012     SAPKA70012
    SAP_BASIS 700     0012     SAPKB70012
    I have to install a service pack in this components to get this funcionality?
    Thanks a lot,
    Cristiana

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

  • Customizing-IMG-structure cross docking not visible

    The customizing-IMG-structure "cross docking" is not visible / available within SAP ECC 6.0-system altough WM-module is used. It is visible via SIMGH but can not be used / displayed via SPRO.
    Could you please tell me what is the reason for this?
    In addition the cross-docking transactions can not be executed (e.g. lxdck ; "You are not authorized to monitor XDOCK").

    Hi
    Please check the following thread.
    Cross-Docking functionality in ECC 6.0
    Thanks
    Anandha

  • 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

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

  • 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

Maybe you are looking for