Skip to Content

CROSS DOCKING IN SAP WAREHOUSE MANAGEMENT- One Step


Introduction :

Cross docking is a Business operation which is highly recommended in today’s warehousing scenarios where customers strive to achieve profits by reducing the material handling cost, labour and time. In general terms cross docking enables warehouse to map inbound delivery documents to outbound deliveries to reduce the material handling and storing in the warehouse.


Business Process and assignments :

In our scenario we are dealing with planned cross docking that enables us to plan the cross docking before goods arrive into warehouse via cross docking decisions in Cross dock monitor.In general business process cross docking is normalized at material levels, certain specific material are designated for cross docking. We here by in this document use special movement indicator ‘S’ and custom WM movement type ‘990’ with respect to 101 IM movement to distinguish cross docking. [ Note : this is purely conditional and depends on how the solution is designed]


One step cross docking movement process directly from Inbound GR area to Outbound shipping area.

We have the below Prerequisites :

a) Check the warehouse configuration in SPRO> IMG> Logistics Execution >Warehouse Management > Cross docking >General settings >Maintain Warehouse Level settings



/wp-content/uploads/2016/07/p1_988105.png

ensure that for relevant warehouse 2step cross docking indicator is not checked.


b) No pre allocation stock check in  movement types 990 ( in this case ) in general for 101 and 601. “consider Pre-alloc stock”


/wp-content/uploads/2016/07/n1_988365.png


c) stock placement and stock removal confirmation required for storage type 902 and 916. In our case we have used custom storage type CD1 in place of 902 standard.


Configuration:


a) SPRO>IMG> Logistics Execution > Warehouse Management > Cross docking > General settings > Maintain Warehouse level settings


/wp-content/uploads/2016/07/p3_988344.png


For our warehouse XY1, 2 step is unchecked, and opportunistic CD for both INB and OBD are selected with planning time of 24 HRs.


b) SPRO>IMG> Logistics Execution > Warehouse Management > Cross docking > General settings > Define Cross-Docking Relevancy for Movement Types

/wp-content/uploads/2016/07/p4_988345.png

For our movement type 990 Cross dock is relevant

c) SPRO>IMG> Logistics Execution > Warehouse Management > Cross docking > General settings > Define Cross-Docking Decision Number Range

/wp-content/uploads/2016/07/p5_988346.png

Internal number range maintained for Cross dock decision during cross dock planning.


Business Transactions :


a) Create purchase order and wrt to PO, create the inbound delivery.

/wp-content/uploads/2016/07/p6_988347.png

Inbound del # 180000115 created for 5 EA


b) Create Sales order for 5 EA and create the Outbound delivery.

/wp-content/uploads/2016/07/p7_988348.png

Delivery created

c) Now we need to plan the cross docking in cross dock monitor – LXDCK transaction

/wp-content/uploads/2016/07/p8_988349.png


Execute:

/wp-content/uploads/2016/07/p9_988350.png

Select ‘plan’ and system will show the below screen:

/wp-content/uploads/2016/07/p10_988351.png

Left side is the inbound delivery which is the candidate and right is the outbound delivery which is the planning document. Select both and click on ‘Add to Plan’

/wp-content/uploads/2016/07/p11_988355.png

Once you save , system will create a decision number.

/wp-content/uploads/2016/07/p14_988356.png

Both the documents are now linked to perform the cross docking.


d) Create TO wrt to the Inbound delivery.

/wp-content/uploads/2016/07/p15_988357.png

create in foreground.

/wp-content/uploads/2016/07/p16_988358.png

We can see that the destination storage type is automatically selected as 916 and the storage bin is our outbound delivery number from the GR area as CD1 with PO#4500017274 That means that the stock is directly moving from interim GR area to shipping area deliverables. Note : For the movement type 990 in our scenario , the source storage type configured is CD1 in SPRO. In general for 101 movement it is 902

/wp-content/uploads/2016/07/p17_988359.png/wp-content/uploads/2016/07/p18_988360.png

e) Confirming the TO using LT12.


WM stock before confirmation:

/wp-content/uploads/2016/07/p19_988361.png

After TO confirmation

/wp-content/uploads/2016/07/p20_988362.png

We can see that now the available stock in 916/800015848 is 5EA

f) The document flow for outbound delivery shows the TO is confirmed

/wp-content/uploads/2016/07/p21_988363.png

same goes with inbound delivery case,where the TO is confirmed and GR is done. This completes the process.

/wp-content/uploads/2016/07/p22_988364.png

Help and links:

a) https://help.sap.com/saphelp_erp60_sp/helpdata/en/98/81b6535fe6b74ce10000000a174cb4/content.htm?current_toc=/en/b3/81b6535fe6b74ce10000000a174cb4/plain.htm&show_children=true

To report this post you need to login first.

9 Comments

You must be Logged on to comment or reply to a post.

  1. Mark Suarez

    Hi Yogi,

    I followed your post from the Cross-dock configuration to the creation of inbound and outbound documents. But on LXDCK transaction, there’s no any delivery documents can be seen in the monitor when I highlight the row of a document then click the “Plan” button. You may see the attached screenshot. Is there any other settings or data that we need to check further aside from the delivery date/time of Inbound and Outbound deliveries? Furthermore, is there a need to follow a specific time or a schedule when executing the Cross-dock plan?

     

    Thanks,

    Mark

    (0) 
    1. yogi kumar Post author

      Hi Mark,

      Please check the planning time for cross dock should be within the range of delivery document creation, what we setup in the customising.

      As the example is for planned CD, therefore we are using a timeline to plan the goods movements. As per my knowledge these are the only settings.

       

      Regards,

      Yogi

      (0) 
  2. Andre Hartono

    Dear Yogi Kumar,

    Thanks a lot for your sharing on Cross Docking Process, btw may I know whether this feature is available in ECC 6.0 without implement SAP EWM? any adds on we can install to activate the configuration that you mentioned?(Eg. SPRO> IMG> Logistics Execution >Warehouse Management > Cross docking >General settings >Maintain Warehouse Level settings)

    Eventhough we did not activate SAP EWM actually I can call LXDOCK transaction code, thus I hope there is a way to use cross docking feature without implement EWM, thanks..

     

    (0) 
    1. yogi kumar Post author

      Hi Andre,

      Yes, the process mentioned is designed in ECC 6.0 version only. Cross docking is a basic feature which is available both in ERP WM as well as in SAP EWM.

      Regards,

      yogi

      (0) 
  3. Amarnath Reddy

    Hi Yogi,

    Your article is very nice and easy to follow. Thanks for sharing.

    I successfully created both Inbound and Outbound. Both are showing in Cross dock monitor however when I tried to select Plan it is throwing error “No inbound documents have been selected for planning”.

    Could you please advise. Thanks in advance.

     

    Amar

    (0) 

Leave a Reply