you're reading...

Cross Docking Functionality in SAP ECC 6

Cross-dock in SAPThis blog Post is for SAP consultants and WM Teams to understand the cross dock functionality in SAP ECC6 (WMS).
The post also discuss about planning for Cross docking and how the cross docking actually taking place with or with out cross dock monitor.
I personally feel that deciding which type of cross-docking and what kind of materials suitable for Cross Docking is important. Most Clients may use to customize the SAP Cross-docking function based on their requirements.  Type of material suitable for cross docking are like a) pre-picked, pre-packed customer orders from another plant or warehouse b) materials that are pre-tagged, pre-ticketed c) promotional material d) Staple retail materials with a constant demand or low demand variance.

Let’s talk about Cross-Docking: In very simple SAP terminology “Cross docking matches inbound and outbound deliveries to avoid having to store material in the warehouse”. Not all material is suitable for cross docking, but when it can be used it reduces labor costs, delivery time to the customer, and the amount of warehouse space.

Types of Cross Docking: A number of cross-docking scenarios are available for warehouse management.

a) Manufacturing Cross Docking- Warehouse may receive the material and issue for production orders, b) Distributor Cross Docking- example: computer parts distributors often source their components from various vendors and manufactures and combine them into one shipment for the customer , c) Transportation Cross Docking- Combines shipments from different shippers in the less than -truckload (LTL) and small package , d) Retail Cross Docking- Receipt of material from multiple vendors and sorting onto outbound trucks for a number of retail stores, e) Opportunistic Cross Docking -The like is manually created, transferring a material directly from the goods-receiving dock to the outbound shipping dock to meet a known demand; i.e a customer sales order.

SAP enables warehouse managers to plan the cross docking process by decisions. A cross docking decision is a link that can be made between a planning document, which can be an inbound or outbound delivery, and a candidate document, which is another inbound or outbound delivery.

Cross Docking Movements:
When cross docking decision is made before material arrives, the movement can be processed as a one-step or two-step cross docking process.

One-Step Cross Docking: Movement process directly from the inbound goods-receiving area to the outbound goods issuing area. For one-step cross docking to be active, check the configuration for the warehouse to ensure that the two-step cross docking indicator is not set. So there will not be any Cross-dock storage type required. This can be a opportunistic cross docking, transferring a material directly from goods receiving dock to the outbound shipping dock. After due configurations for one -step system process steps are..
You need to create either Putaway TO/Pick TO and then system checks the cross doc config 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.

Two-Step Cross Docking: When a link is created between an inbound and outbound delivery as part of a cross docking decision. If system active for two-step process, the system will create  two transfer orders: 1) A transfer order for the inbound delivery materials from the goods receipt storage type (902) to the cross docking storage type (XCD). 2) A transfer order from the cross docking storage type(XCD) to the goods issue storage type(916).

Configuration for Cross Docking

Configure for planned and opportunistic cross docking for the warehouse and the storage type. IMG> Logistics Execution> Warehouse Management> Cross Docking> General Setting> Maintain Warehouse Level settings.

The next configuration step is to confirm that a movement type that is to be used for cross docking is set to allow cross docking. IMG> Logistics Execution> Warehouse Management> Cross Docking> General Setting> Define Cross-Docking Relevancy for movement Types. The CD Relevant indicator should be set for movement types to be used cross docking.

Accessing the Cross Docking Monitor
Transaction: LXDCK or SAP> Logistics> Logistics Execution> Cross Docking> Cross Docking Monitor
Cross Docking Alert Monitor
Transaction: LXDCA or SAP> Logistics> Logistics Execution> Cross Docking> Alert Monitor

Note: The cross dock decision made automatically by the system (means no cross dock monitor used) will not give good results for all the materials for cross docking. SAP checks Material and Qty for both inbound and outbound documents will not able to do more fields checking before deciding the automatic link between documents.

Click the link here for more Cross-Dock help at SAP

All product names are trademarks of their respective companies.  The content on this site may not be reproduced or redistributed without the express written permission of the content author.

Website help.sap.com’s logos,pictures and links are trademarks or registered trademarks of SAP AG in Germany and other countries.

About TKReddy

Working in SAP environment. This is a blog of my personal experience. Most of my posts are related to SAP, Websites and other personal topics.


10 thoughts on “Cross Docking Functionality in SAP ECC 6

  1. Hi,

    In ECC 6.0 I did not able to find tab of “Cross Docking Configuration” in WM. Is there anything to be activated ?


    Posted by Praveen | March 11, 2011, 2:30 am
  2. We want the system to create the TO to send to 916 at time of receipt. The documentation I’ve indicates that a TO must exist already for Opportunistic XDock and that an Outbound Delivery (OBD) must exist for Planned XDock.
    The system does not create an OBD or a TO until a receipt is done and ATP has run to allocate the stock.


    Posted by Jim Murray | July 27, 2011, 3:14 pm
  3. Hi,
    Yes, me too. Just cannot find the configuration path you mentioned.

    Posted by Colin | October 20, 2011, 3:56 am
  4. You need extension set 2.0 activated in order to view the Cross Docking SPRO node or the LXDCK tcode.
    Also this may be in your tcode list but not activated, in that case you need to activate the tcode through Basis.

    Posted by MacJT | February 14, 2012, 10:42 am
  5. I have done the config, created XCD storage type, etc. But I get either of the following messages when I click on the plan button in the grid:-
    No matching outbound documents found
    No matching inbound documents found
    Time ref. 01.05.2012 00:00:00 of plan.doc. 180000062 does not match cand.documents time refs

    This is frustrating me, as SAP will always default 00:00 in the time field. In the IMG I have 8.0 | 1.0 | 1.0 in the time fields. I have tried everything, changeing delivery dates in VL32N/VL02N and still it says one of the above messages. The message itself is dynamic so I cannot put a breakpoint in the ABAP code.

    I notie too on SCN that many other consultants have had the same issue.

    Posted by Warren | May 1, 2012, 11:39 pm
  6. Have you ever set up crossdock where you stock teh product in the dc and Crossdock it and if so how?

    Posted by Warren | September 3, 2012, 5:17 am
  7. Can we calculate tax on the movement of goods by using this configuration?

    Posted by anuj | May 15, 2013, 3:21 pm
  8. 1step and 2 step cross dock. For both case we need to create inbound and outbound. For cross dock we need to create the outbound delivery with quantity for planning purpose. We cannot create outbound if no stock

    Posted by JP | October 1, 2013, 7:58 am
  9. When cross docking decision is made before material arrives. How does outbound created if stock is not available ?

    Posted by JP | October 2, 2013, 12:22 am


  1. Pingback: 2010 in review « TKReddy's blog - January 2, 2011

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


All SAP Posts


SAP Blog Posts

Blog Stats

  • 386,703 hits
All product names and images are trademarks of their respective companies.
Note: if you see ads on this site, they are placed by WordPress, not me

Get every new post delivered to your Inbox.

Join 104 other followers

%d bloggers like this: