Cross Docking 01 Decision

Cross-Docking DecisionPDF download from SAP Help Portal:http://help.sap.com/saphelp_erp60_sp/helpdata/en/ad/81b6535fe6b74ce10000000a174cb4/content.htm

Created on April 30, 2015

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

NoteThis PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SEand its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided bySAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not beliable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and otherSAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and othercountries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 9

Table of content1 Cross-Docking Decision1.1 Planning Document1.2 Candidate Document1.3 Release Time1.4 Latest Release Time1.5 Planned Cross-Docking1.5.1 Cross-Docking Decision Optimization1.6 Opportunistic Cross-Docking1.7 Effect of Document Changes on Cross-Docking Decisions


Page 2 of 9

1 Cross-Docking Decision

DefinitionA cross-docking decision is a decision that either establishes a cross-docking link between a planning document and candidate document item, or designates adocument or item for cross-docking , without establishing a link.

Use

Linking Planning and Candidate Document ItemsDecisions linking planning and candidate document items can be created as part of the planned cross-docking or opportunistic cross-docking processes. Theycan be created in the following ways:

Manually created by the warehouse managerYou can plan cross-docking and establish links between documents via the Plan cross-docking monitor method . For more information, see Creating aCross-Docking Plan .You can also run the cross-dock planning in the background, accepting cross-docking decisions recommended by the system. For more information, seeCross-Docking Decision Optimization .Automatically created by the systemDuring the creation of a transfer order (TO) for an inbound or outbound planning document that has not been linked with a candidate document, the systemestablishes the link by searching for appropriate open TOs connected to candidate documents. For more information, see Opportunistic Cross-Docking .

Designating Documents or Items for Cross-DockingYou can designate both inbound and outbound documents or items for cross-docking via the Designate for cross-docking monitor method.In the case of an inbound document/item, the designation results in the creation of a putaway TO, at goods receipt for the inbound document/item, with the cross-docking storage type as its destination.In the case of an outbound document/item, if goods receipt is performed for an inbound document/item containing the required outbound material, the putaway TOis created to the cross-docking storage type or goods issue area. The designation does not, however, prevent the creation of any picking TO from storage to meetthe outbound material requirements.For more information, see Designating a Document or Item for Cross-Docking .

NoteYou can cancel cross-docking decisions via the Cancel monitor method. For more information, see Cross-Docking Monitor Methods .

StructureA cross-docking decision comprises of the following:

Decision numberDecision typeInbound and/or outbound document(s) and item(s)Document typeDecision statusDecision quantityInbound processed quantityInbound confirmed quantityOutbound processed quantityDecision unit of measureDecision originMaterial data, including material number, plant, storage location and stock categoryOutbound document warehouse movement type

ExampleA warehouse is customized so that two-step cross-docking is forced.The warehouse manager links item 10 of inbound delivery 180002452 with item 20 of outbound delivery 80001308 (4 loads). Each load represents a palletcontaining 10 pieces.The decision fields include the following values:

Doc. Item Doc. Item Status Dec. Qty Inb. Proc. Qty Inb. Cnf. Qty Out. Proc. Qty UoM180002452 10 80001308 20 Open 40 PCE

After delivery 180002452 arrives and goods receipt is performed, a TO to take 40 pieces from the goods receipt area and put them away in the cross-dockingstorage type is created. The decision fields are now as follows:

Doc. Item Doc. Item Status Dec. Qty Inb. Proc. Qty Inb. Cnf. Qty Out. Proc. Qty UoM


Page 3 of 9

Doc. Item Doc. Item Status Dec. Qty Inb. Proc. Qty Inb. Cnf. Qty Out. Proc. Qty UoM180002452 10 80001308 20 Inbound

complete40 40 PCE

At this point, release of delivery 80001308 will not trigger the creation of a picking TO since there is no inbound confirmed quantity.After the putaway TO is confirmed, the decision is updated as follows:

Doc. Item Doc. Item Status Dec. Qty Inb. Proc. Qty Inb. Cnf. Qty Out. Proc. Qty UoM180002452 10 80001308 20 Inbound

complete40 40 40 PCE

After delivery 80001308 is released, a TO to pick 40 pieces from the cross-docking storage type and take them to the goods issue area is created. The decisionnow looks as follows:

Doc. Item Doc. Item Status Dec. Qty Inb. Proc. Qty Inb. Cnf. Qty Out. Proc. Qty UoM180002452 10 80001308 20 Completed 40 40 40 40 PCE

1.1 Planning Document

DefinitionA planning document is a document for which cross-docking opportunities are analyzed.

UseYou can create a cross-docking decision by establishing a link between a planning document item and a candidate document item.For more information, see Creating a Cross-Docking Plan .

IntegrationPlanning documents can be inbound/outbound deliveries or transfer requirements.

ExampleIn the planned cross-docking process, if the planning direction is Inbound to Outbound , the inbound documents are the planning documents containing itemsfrom which outbound document items are to be fulfilled.

1.2 Candidate Document

DefinitionA candidate document is a document with an item that has potential to be linked to an item in a planning document , so as to create a cross-docking decision .

UseYou can create a cross-docking decision by establishing a link between a planning document item and a candidate document item.For more information, see Creating a Cross-Docking Plan .

IntegrationCandidate documents can be inbound/outbound deliveries or transfer requirements.

ExampleIn the planned cross-docking process, if the planning direction is Inbound to Outbound , the outbound documents, which contain items to be fulfilled from theinbound documents, are the candidate documents.

1.3 Release Time


Page 4 of 9

DefinitionThe release time for an outbound document is the time by which you to plan to create a transfer order for the document, enabling the document to be released forexecution.

UseYou can enter a release time for a group when creating the group and assigning to it outbound deliveries via the monitor. For more information, see AssigningOutbound Deliveries to a Group .If you do not enter a release time for a group, the system uses the default release time as defined in Customizing for LogisticsExecution WarehouseManagement Cross-Docking General Settings Maintain Warehouse Level Settings. In this Customizing activity, you define the release time in terms of an amount of time before the outbound document date and time reference.The release time has the following uses:

1. It is used by Yard Management as the beginning time of the time frame for which the system searches for available locations to schedule for the outbounddocument at the time the cross-docking decision is created.For more information, see System Scheduling in the SAP Library for Yard Management (LE-YM) .

2. Violation of the release time triggers a yellow alert in the alert monitor.For more information, see Alerts Provision .

1.4 Latest Release Time

DefinitionThe latest release time for an outbound document is the latest time by which you must create a transfer order for the document, enabling the document to bereleased for execution.The latest release time is also the latest point in time until which transfer order (TO) creation will be delayed.

UseYou can enter a latest release time for a group when creating the group and assigning to it outbound deliveries via the monitor. For more information, see AssigningOutbound Deliveries to a Group .If you do not enter a latest release time for a group, the system uses the default latest release time as defined in Customizing for LogisticsExecution Warehouse Management Cross-Docking General Settings Maintain Warehouse Level Settings.

In this Customizing activity, you define the latest release time in terms of an amount of time before the outbound document date and time reference.The latest release time has the following uses:

1. In the case of planned cross-docking , if the outbound document is released prior to the confirmation of a TO for the inbound document, the system delayscreation of picking TOs (from storage to the goods issue area) for the outbound document until the latest release time.

2. Violation of the latest release time triggers a red alert in the alert monitor.For more information, see Alerts Provision .

1.5 Planned Cross-Docking

PurposeCross-Docking enables you to generate cross-docking decisions priorto the actual arrival of incoming stock and release of outgoing documents (i.e. prior to

transfer order creation).The process differs, depending on:Whether the cross-docking decisions involve linking document items or designating a document or item for cross-dockingWhether the inbound TO is confirmed before or after the release of the outbound document (in the case of decisions linking items)Whether the document or item is an inbound or outbound document or item (in the case of cross-docking designation)

PrerequisitesInbound and outbound deliveries/transfer requirements (TRs) are created in the system.The documents have some quantity of stock available for picking or putaway.You have done the following:a. Maintained warehouse level settings in Customizing for Logistics Execution Cross-Docking Maintain Warehouse Level Settings. In particular, youhave entered the cross-docking storage type, and defined a time reference, planning time window and default latest release time.b. Defined warehouse movement types as being relevant for cross-docking inCustomizing for Logistics Execution Cross-Docking Define Cross-DockingRelevancy for Movement Typesc. Ensured that the Consider Pre-Alloc. Stock indicator is not set in Customizing for Logistics Execution Warehouse Management Activities Transfers Define Movement Types

d. Ensured thatthe cross-docking storage type is excluded from the stringent FIFO picking strategy in Customizing for Logistics Execution Warehouse


Page 5 of 9

Management Strategies Picking Strategies Define Strategy for Stringent FIFOe. Entered1(for inbound documents) or2(for outbound documents) in the TO Creation field (Screen Control) for your warehouse inCustomizing for LogisticsExecution Warehouse Management Activities Transfers Define Movement Types.

We also recommend that you ensure thatthe cross-docking storage type is excluded from every storage type search sequence in Customizing for LogisticsExecution Warehouse Management Strategies Activate Storage Type Search , to avoid a situation in which stock for cross-docking is picked forother deliveries.

Process Flow

Decisions Linking Planning and Candidate Document Items

Inbound OutboundYou do any of the following:Create a cross-docking plan consisting of one or more cross-docking decisions involving linked inbound and outbounddocument items. For more information, see Creating a Cross-Docking Plan .Create the system-recommended decisions in the background. For more information, see Cross-Docking DecisionOptimization .The stock arrives at the goods receipt area (storage type902) and you post goods receipt, or use the partial postingfunctionality.

You try to create a TO for the outbound document (i.e.release the outbound document).

You create a putaway TO for each of the document items.During TO creation, the system does the following:a. Fetches the previously created decision according to thedocument itemb. Determines the destination as:The cross-docking storage type in a case where two-stepcross-docking is forcedThe goods issue area (storage type 916) in all other cases

The system fetches the previously created decisionsaccording to the document items.

You try to create a TO for the outbound document (i.e.release the outbound document).If the goods to be cross-docked are at the cross-dockingstorage type, the system automatically creates the TOfrom the cross-docking storage type.

The system delays creation of picking TOs (from storage tothe goods issue area) for the outbound document as longas the latest release time has not yet arrived.If the relevant inbound document items arrive before thelatest release time, you perform goods receipt and create aputaway TO for each item. During TO creation, thesystem determines the destination as:The cross-docking storage type in the case where two-stepcross-docking is forced. Once the goods have beenconfirmed at the cross-docking storage type, the systemwill not delay the creation of a picking TO, and you cancreate a picking TO for the outbound document. When youcreate the picking TO, the system automatically creates itfrom the cross-docking storage type.The goods issue area in all other cases

Decisions Designating Documents or Items for Cross-Docking

Inbound Document/Item Designated for Cross-Docking

Outbound Document/Item Designated for Cross-Docking

You designate a document or item for cross-docking via the cross-docking monitor.For more information, see Designating a Document or Item for Cross-Docking .When the inbound document items arrive at thewarehouse, you perform goods receipt and create aputaway TO for each of the items.

When inbound document items containing the samematerials as the relevant outbound items arrive, youperform goods receipt and create a putaway TO for eachitem. During TO creation, the system determines thedestination as:The cross-docking storage type in the case where two-stepcross-docking is forced. Once the goods have beenconfirmed at the cross-docking storage type, you can createa picking TO for the outbound document. When you createthe picking TO, the system automatically creates it fromthe cross-docking storage type.The goods issue area in all other cases

( )The system does not prevent the creation of a picking TOfrom storage to meet the outbound material requirements.

During TO creation, the system does the following:a. Fetches the previously created decisionsb. Determines the destination as the cross-docking storagetypeA warehouse worker moves the relevant goods to thecross-docking storage type and confirms execution.You can manually create a picking TO from the cross-docking storage type to the goods issue area.

1.5.1 Cross-Docking Decision OptimizationPUBLIC 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 6 of 9

1.5.1 Cross-Docking Decision Optimization

UseAs part of the cross-dock planning process, the system optimizes cross-docking decisions linking inbound and outbound document items.

FeaturesThe system optimizes cross-docking decisions so that:

The maximum number of loadsare cross-dockedThe minimum number of links are established between deliveries/TRs, shipments or groups

NoteYou can create your own optimization algorithm using method PLANNING_DOCUMENTS_MATCH of Add-In LXDCK_CROSS_DOCK . For moreinformation, see Business Add-Ins .

This optimization is performed according to one of the following optimization levelsDelivery/TRShipmentGroup

The selected optimization level can influence the system-recommended cross-docking decisions. ( )

The following shipments and deliveries are within the cross dock planning time window:

Inbound OutboundDelivery 180003243BIKE x 10 Loads

Shipment 1245 Delivery 80005432BIKE x 9 Loads

Delivery 180003244BIKE x 5 Loads




Shipment 1249 Delivery 80005500BIKE x 10 LoadsDelivery 80005501BIKE x 5 Loads

If the optimization level is set at Shipment , the system will create a cross-docking decision linking inbound deliveries 180003243, 180003244 and180003245 (18 bike loads) with outbound shipment 1245 (16 bike loads), and not with outbound shipment 1249, which has only 15 bike loads.If the optimization level is set at Delivery/TR , the system will create cross-docking decisions linking the deliveries as follows:

Inbound delivery 180003243 with outbound delivery 80005500 ( shipment 1249 )Inbound delivery 180003244 with outbound delivery 80005501( shipment 1249 )Inbound delivery 180003245 with outbound delivery 80005444 ( shipment 1245 )

NoteYou select the optimization level in the cross-docking monitor selection screen. For more information, see Opening the Cross-Docking Monitor .

You can either prompt the system to create the decisions in the background, or you can view the system proposal and either accept the decisions in their entirety,or adjust them manually according to your requirements.

Activities

Creating the System-Recommended Decisions in Background1. From the Cross-Docking: Selection screen of the cross-docking monitor, you choose ( ) .2. The system creates cross-docking decisions linking inbound and outbound document items, according to the optimization algorithm.3. You can view these decisions in the cross-docking monitor ( Decision object class).

1.6 Opportunistic Cross-Docking

PurposeIn the opportunistic cross-docking process, the system generates a cross-docking decision during the process of TO creation ( after the arrival of the incomingstock or release of the outgoing document).


Page 7 of 9

NoteOpportunistic cross-docking involves one-step cross-docking execution only.

PrerequisitesYou have done the following:

1. Enabled opportunistic cross-docking in Customizing for Logistics Execution Warehouse Management Cross-Docking General Settings Maintain Warehouse Level Settings

2. Defined warehouse movement types as being relevant for cross-docking in Customizing for Logistics Execution Warehouse Management Cross-Docking General Settings Define Cross-Docking Relevancy for Movement Types

3. Ensured that the Consider Pre-Alloc. Stock indicatoris not set in Customizing for Logistics Execution Warehouse Management Activities Transfers Define Movement Types

4. Entered 1(for inbound documents) or 2(for outbound documents) in the TO Creation field (Screen Control) for your warehouse inCustomizing for LogisticsExecution Warehouse Management Activities Transfers Define Movement Types

5. Enabled one of the following, in the case of opportunistic cross-docking for inbound documents (HU-managed environment):Partial posting goods receipt at movement type level in Customizing for Logistics Execution Warehouse Management Interfaces Shipping

Define Shipping Control Define Shipping Control at the Movement Type Level (enter 4in field)Posting goods receipt before TO creation in Customizing for Logistics - General Handling Unit Management Basics Delivery DefineSequence of Transfer Order Goods Receipt

6. Enabled posting goods receipt before TO creation in Customizing for Logistics - General Handling Unit Management Basics Delivery DefineSequence of Transfer Order Goods Receipt , in the case ofopportunistic cross-docking for outbound documents

7. Entered Bin the Method field (Blocking logic) for your warehouse in Customizingfor Logistics Execution Warehouse Management Master Data Define Control Parameters for Warehouse Number

8. Ensured that automatic confirmation is not set (HU-managed environment only) by doing at least one of the following in Customizing for LogisticsExecutionWarehouse Management Activities Confirmation Storage Type:

Setting the Confirmation putaway indicator for the goods issue storage type (e.g. 916)Setting the Confirm stck removal indicator for the goods receipt storage type (e.g. 902)

Process FlowInbound Document Outbound DocumentAn inbound document is created.The stock arrives at the goods receipt area (storage type902) and goods receipt is performed if posting is allowedbefore TO creation.

An outbound document is released.

You create a putaway TO for each of the document items.During TO creation, the system checks whether a cross-docking decision already exists for each document item.If a decision already exists, see step 3 onwards in Planned Cross-Docking .If a decision does not already exist, the system analyzeswhether there are any available cross-dockingopportunities.

1. a. The system searches for any open picking TOitems from storage to the goods issue area (storagetype 916), according to the following criteria:

1. i. TO item status is not confirmed and TOitem is not locked by any resource.

2. ii. TO item contains the same material,quantity, plant and storage location (usuallyin terms of full loads) as the putaway TOitem to be created.

3. iii. The stock category of the TO item isAvailable Stock .

2. b. The system evaluates further criteria, such asFIFO and batch requirements.

If a decision does not already exist, the system analyzeswhether there are any available cross-dockingopportunities:

1. a. The system searches for any open putaway TOitems from the goods receipt area (storage type 902)to storage, according to the following criteria:

1. i. TO item status is not confirmed and TOitem is not locked by any resource.

2. ii. TO item contains the same material and alower or same quantity as the picking TOitem to be created.

3. iii. The stock category of the TO item isAvailable Stock .

4. iv. The handling unit (HU) of the TO item isposted (in HU-managed environment only)

2. b. The system evaluates further criteria, such asFIFO and batch requirements.

If the system finds a suitable picking TO item, it does thefollowing:

1. a. Cancels the picking TO item2. b. Creates a putaway TO item to the goods issue

area3. c. Updates the outbound document, for which the

picking TO item was cancelled, with the new cross-docking putaway TO item

If the system finds a suitable putaway TO item, thesystem does the following:

1. a. Cancels the putaway TO item2. b. Creates a picking TO item to the goods issue

area, with the source of the cancelled putaway TOitem (goods receipt area) as its source

3. c. Updates the inbound document, for which theputaway TO item was cancelled, with the newcross-docking picking TO item

The newly-created putaway/picking TO item is now connected to both the inbound and outbound documents.

1.7 Effect of Document Changes on Cross-Docking DecisionsType of Change Document Type Effect What You Should Know


Page 8 of 9

Deletion Delivery The statuses of all of the documents cross-docking decisions are set to Cancelled .

A document can be deleted as long asprocessing on it has not yet commenced.TR

Change in quantity Delivery When quantity is reduced, the quantities ofthe documents cross-docking decisions arereduced so that the total open quantity ofdecisions (decision qty minus processedqty) does not exceed the quantity left topick/putaway.

A documents quantities can be changedeven after processing on it hascommenced.TR

Change in material, plant or storagelocation

Delivery The statuses of all of the documents cross-docking decisions are set to Cancelled .

Changes are not allowed after deliveryprocessing has commenced.

TR Changes are not allowed at all.Change in stock category Delivery If stock category is changed to anything but

Available Stock , the statuses of all ofthe documents decisions are set toCancelled .

TR

Change in source or destination storagetype

TR If you enter a value in the destinationstorage type and bin of a picking TR, or thesource storage type and bin of a putawayTR, the statuses of all of the documentsdecisions are set to Cancelled .


Page 9 of 9

Cross Docking 01 Decision

Documents

Transcript of Cross Docking 01 Decision