Goods marking on cross-docking orders

Dear colleagues,
Will you please help me with another conceptual issue in IS-Retail? I thought that the difference between the cross-docking and flow-through was that the goods are not repacked in the former case, i.e. the vendor marks the final destination of the goods (the store), so that the DC can merely move the parcel from the receiving ramp to the dispatch ramp and send them further.
However, I see that the system generates vendor orders for the total quantities per article (no split of the total quantity per store). I wonder then how the vendor will know how to pack the goods and mark them with the address of the end destination?!
Or otherwise, what is the idea of cross-docking?
TIA
Raf

H Rafael,
I understand your question. I was not clear earlier. If I work through your example, Let us say you have 3 stores - A, B and C
and you have ordered 12 units - 4 for each Store. The Vendor has only 9 units.
Now we have the following options -
A) You agree with this vendor on predetermined rules to distribute in case of under delivery. You could decide to distribute proportionally (standard adjustment profile) or a custom version (your own function module) which kicks in at Goods Receipt automatically.
B) You do not have a predetermined rule and hence the Vendor contacts you to ask for instructions, this would mean you would give a manual instruction on the rule to be used. In this case I would rather do a manual distribution than an automatic one at GR. However this option is not optimal for any business as the whole point of cross-docking and SLS automation is to avoid manual communications with the Vendor.
Ideally I would do the following. Sit with the Vendor who would pre-pack and agree the set of predetermined rules that will be applicable. For example - You could have one rule for all Mens Clothing, and another for Womens Shoes. etc.
You can then use your Custom Function module to pick the right rule based on the article and apply the rule at the GR. Since the rules are agreed in advance with the Vendor, the Vendor would have packed the right quantities.
Hope that helps.
Cheers,
Naveen

Similar Messages

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

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

  • 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

  • One step cross docking

    hi,
        i am working on one step cross docking scenorio , i am missing some where in configuration.  plz guide me.
    steps i followed
    i) checked the preallocated check box in omlj transaction for 101 - movt type
    ii)entered the preallocated stock details in lt51 transaction.
    iii)enter the goods receipt with respect to purchase order in migo.
    iv)create transfer order for inbound delivery with refrence to TR.
    v)create transfer order for outbound delivery without refernce.
    i follow the above steps but  still  the entry in preallocated stock in lt51 there.where i miss the configuration guide me.
    i already view the help.sap.com,i cant understood  where i missing the config.
    appreciate your help always
    muthuraman.d
    Edited by: muthuraman d on Feb 12, 2010 2:52 PM

    Hi
    KIndly check the below OSS notes for the same
    559708 - LT51: Deleting and updating preallocated stock entries
    556490 - Incor.pre-allocatd actual stock aft.confirm.fm SU bulk stor.
    555340 - Preallocated stock table entries are deleted too early
    Regards
    Damu

  • Please please help me Can anyone help in Cross Docking Please

    I did cross dock many time succussfully but i am trying now I am either getting following error
    "No inbound documents have been selected for planning"
    Please help me as I set up warehouse relevant, movmenttype relevent set up time reference for release, ref etc too
    But I am getting error please please help me

    Hello,
    Cross docking is process where goods movement do not happen within warehouse house (No putaways & picking)
    The process flow for the same is as follows;
    Sales order creation>>Purchase requistion>>Purchase order>>>Inbound delivery creation(stock is inventory managed)>>Post goods reciept is done>>Outbound delivery creation (reference to sales order)>>stock is picked in delivery itself>>post goods issue.
    Warehouse managment is not involved as there is creation of transfer orders in cross docking. So you need to cerate inbound delivery, do the put away directly in inbound delivery stock placement tab and do the post goods reciept. This will maintain the stock in inventory managed storage location.
    Once PGR is done you can create outbound delivery with refernce to sales order and do the picking in picking tab in delivery and then post goods issue.
    Br,
    Tushar

  • One step cross docking in wm

    hi,
    i am working on one step cross docking scenorio , i am missing some where in configuration. plz guide me.
    steps i followed
    i) checked the preallocated check box in omlj transaction for 101 - movt type
    ii)entered the preallocated stock details in lt51 transaction.
    iii)enter the goods receipt with respect to purchase order in migo.
    iv)create transfer order for inbound delivery with refrence to TR.
    v)create transfer order for outbound delivery without refernce.
    i follow the above steps but still the entry in preallocated stock in lt51 there.where i miss the configuration guide me.
    i already view the help.sap.com,i cant understood where i missing the config.
    appreciate your help always
    muthuraman.d

    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

Maybe you are looking for