application help for sap extended warehouse management add

USER GUIDE | CONFIDENTIALDocument Version: 1.0 – 2019-06-28

Application Help for SAP Extended Warehouse Management Add-On for Consumer Products

© 2

019

SAP

SE o

r an

SAP affi

liate

com

pany

. All

right

s re

serv

ed.

THE BEST RUN

Content

1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 Switchable BAdI Implementations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3 Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.4 Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 Extended Warehouse Management Cross Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92.1 Radio Frequency (RF) Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.2 Product Master Data Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.3 Adjust Packaging Specification Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92.4 Shipping Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.5 Quality Check Characteristics for Transportation Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Check Transportation Unit and Door Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.6 Custom Batch Numbering Logic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.7 Authorization Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3 Extended Warehouse Management Inbound. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.1 Put-Away of Allergen Materials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2 Bulk Receiving. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.3 Inbound Door Proposal for Transportation Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.4 Assign Transportation Unit to Door Monitor Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213.5 Radio Frequency Unloading by Door. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Scan Handling Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Homogenous Cross-Delivery Handling Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Mass Create Handling Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Create Mass Handling Unit Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3.6 Dock Transportation Unit to Door. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Mass Create Handling Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Create Mixed Handling Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.7 Unloading Completion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323.8 Mass Create Handling Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.9 Create Mixed Handling Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.10 Receiving from Another Plant (ICT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.11 Receiving Store Returns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.12 Product Master Validations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.13 Quality Check Request and Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.14 Printer Determination Based on Handling Unit Position. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

2 C O N F I D E N T I A LApplication Help for SAP Extended Warehouse Management Add-On for Consumer Products

Content

3.15 Capacity Check on Pick and Drop Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .443.16 Receipt from Production Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4 Extended Warehouse Management Outbound. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.1 Outbound Door Availability Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.2 Release Transportation Unit for Staging (RTS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .494.3 Staging Area Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514.4 Staging Result Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.5 Loading Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.6 Filtering and Rounding Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.7 Full Pallet Picking Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.8 Consolidate Picking to Full Pallets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614.9 Mixed-Layer Pallets Picking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624.10 Rounding to Available Pack Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624.11 Mixed Product Pallet Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634.12 Double-Deep/Multi-Deep Rack Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .634.13 Storage Type Search Sequence Redetermination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .644.14 Transportation Unit Loading Completion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654.15 Repacking/Kit to Stock with Subcontracting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674.16 Opportunistic Cross-Docking in Repacking Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704.17 Repalletization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714.18 Shipment Changes by IDoc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734.19 Inspection (Handling Unit Check). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734.20 Quality Checks During Automatic Staging & Loading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754.21 Cartonization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764.22 Printer Selection for Handling Unit Label Printing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784.23 Value Added Services Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794.24 Operative Loading by Door. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

5 Extended Warehouse Management Internal Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825.1 Pallet Mover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825.2 Plant-to-Plant Stock Postings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835.3 Short Shelf Life - Stock Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845.4 Quarantine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

6 Extended Warehouse Management Production Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . 886.1 Direct Loading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 886.2 Shuttle Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .906.3 Control Parameter for the Communication of Goods Receipt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

7 Simple UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957.1 Simple UI Basic Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957.2 Starting the Simple UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Application Help for SAP Extended Warehouse Management Add-On for Consumer ProductsContent C O N F I D E N T I A L 3

7.3 Customizing and Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967.4 Picking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977.5 Packing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987.6 Deconsolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987.7 Value Added Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007.8 Information UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101


Content

1 Overview

This user guide provides an overview of the functions and features for SAP EWM Add-On for consumer products.

1.1 Prerequisites

This section provides information on the prerequisites for SAP Extended Warehouse Management (EWM) Add-on for Consumer Products.

Make sure that the following prerequisites are met:

● You are running an installed component SCMEWM release 9.3 or higher.● You acknowledged the use of advanced functions in your warehouse. SCM Extended Warehouse

Management→ Extended Warehouse Management→ Master Data→ Acknowledge Use of Advanced Functions● You have set up the master data and maintained the Customizing settings for standard SAP Extended

Warehouse Management.

1.2 Switchable BAdI Implementations

EWMCP uses various BAdI implementations from the standard EWM component to control system behavior. They can be activated all at once using the Enterprise Business Function /EWMCP/EWM_BADI_1 in transaction SFW5 (special authorization required).

As many of the standard BAdIs are of the single-use type and EWMCP fills them with code, the coding provided by EWMCP contains BAdIs by itself to allow further custom coding inside single-use standard BAdIs.

CautionIf you have an existing BAdI implementation before installing the /EWMCP/ software package, there is the risk that this will be affected by the activation of the EWMCP code. You must review your own BAdI implementations, if applicable.

Application Help for SAP Extended Warehouse Management Add-On for Consumer ProductsOverview C O N F I D E N T I A L 5

1.3 Assumptions

The objective of this user guide is to list and explain the features of the add-on and to provide some guidance for the implementation project. Please be aware that the solutions are intended to complement a maintained EWM installation in clearly outlined situations.

The intended business background will be presented by trained consultants following the corresponding implementation methodology and using the appropriate BPD documents. This documentation follows the assumption that the basic settings and master data are set up as per the configuration guides.

1.4 Glossary

This section defines the terms and acronyms used in this document.

Term Abbreviation Definition

Enterprise Resource Planning Central Component

ECC

Extended Warehouse Management EWM

EWM for Industries EWMCP Software provided in package/EWMCP/

Easy Enhancement Workbench EEW A concept in EWM to extend data structures with custom fields.

First Expire, First Out FEFO This term is used in logistics and inventory management to describe a way of dealing with perishable products, or with a specified expiry date (source: Wikipedia).

First In, First Out FIFO A stock removal method in which the materials first transferred to a bin are the first to be removed from the bin, first in, first out.

Handling Unit HU Physical unit consisting of packaging materials and the products they contain.

A handling unit (HU) has a single, scan-able identification number.


Overview


Intermediate Document IDoc An IDoc is a specific message formatted with the IDoc type. An IDoc type can usually send more than one type of message. These are known as the “logical messages” that correspond to different business processes.

European Article Number EAN EAN is an outdated standard for Article Numbers, which has been replaced by GTIN in 2009. Some documents still use this term.

Internet Transaction Server ITS A server which enhances the three-tiered SAP architecture for use in the Internet.

Global Trade Item Number GTIN Global Trade Item Number (see Wikipedia).

Business Process Design BPD A document describing the intended business processes.

Outbound Delivery Order ODO The outbound delivery order is a document containing all the data required for triggering and monitoring the complete outbound delivery process.

Post Processing Framework PPF The Post Processing Framework (PPF) is a SAP basis technology used in Delivery Processing for scheduling and processing actions and messages regarding a document.

Production Supply Area PSA An area on the shop floor where material is if can be directly used for production.

Radio Frequency RF The term is generally used here for controlling and usage of handheld devices in warehouse operations.

Shelf-Life Expiration Date SLED The date up to which a material can be retained in storage and be acceptable for use.

Application Help for SAP Extended Warehouse Management Add-On for Consumer ProductsOverview C O N F I D E N T I A L 7


Transportation Unit TU Smallest loadable unit of a vehicle that is used to transport goods. The transportation unit (TU) can be a fixed part of the vehicle.

Intracompany Transfer ICT Stock Transfer process using a stock transfer order.

Planned Ship HU PSHU Preliminary object constructed during Cartonization to estimate number and nature of objects resulting from picking.

Inbound Delivery IDLV Object received from ERP to base Goods Receipts on.

Bin Access Type BAT Master Data associated with a storage bin to determine suitable resources that can access the bin.

Logistics-Batch Management LOBM Technical identifier for the SAP Batch Management component

User Interface UI Any way a computer communicates with humans. In this document, mostly screens displayed on handheld devices or monitors.

Value-Added Service VAS A processing step interfering with warehouse movements to perform certain activities on the goods

Enterprise Resource Planning ERP System to trigger goods movements that will be executed by EWM

Quality Control QC Quality Control

Document Management System DMS Software tool to store links between SAP business objects and various types of attached documents (for example, .pdf or .jpeg).


Overview

2 Extended Warehouse Management Cross Functions

This chapter provides details on the cross functions available in EWMCP.

2.1 Radio Frequency (RF) Framework

EWMCP comes with several logical transactions that can be mounted into the customer's RF presentation profiles. Transactions provided for mobile devices are shipped as SAP GUI versions.

As per experience, customers usually apply further adaptions to RF screens and optimize the transaction flows for their own purposes. For this reason, the EWMCP does not come with prepared HTML templates. Please refer to note 1070288 for details of ITS service generation.

2.2 Product Master Data Enhancements

EWMCP comes with an extension table /SCWM/MATLWHN associated with the product master.

You maintain this extension table using transaction MASSD and object type EWMCP_MWH, with the key fields being the Product Number and the Entitled to Dispose. One purpose of this extension is to have an Allergen Class available, controlling the put away strategy. There is also a stack-ability factor provided that is used in cartonization to sort products to be stacked in a PSHU (heavy items at the bottom). If you don't intend to use these two features, you can disregard the extension table.

Prerequisites

● You have started the report /EWMCP/2INB_MAT_MD_CHECK for each new product. The report will then generate a corresponding entry in /SCWM/MATLWHN.

2.3 Adjust Packaging Specification Description

EWMCP offers a batch capable report (transaction /EWMCP/1XRS_PACK_ADJ) to review selected Packaging Specifications and update the description text according to a predefined pattern. The text is concatenated from

Application Help for SAP Extended Warehouse Management Add-On for Consumer ProductsExtended Warehouse Management Cross Functions C O N F I D E N T I A L 9

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/1070288

the target quantities on different pack. spec. levels and assumes to find one of the following pack. spec. constructions:

● Two level: Content and HU Creating where Content is maintained in a non-Base UoM with quantity equal to 1 (the system will issue a warning 'Quantity is not equal to 1' when you maintain a pack. spec. like this, but it is still possible).

● Three level: Content is in Base UoM. Target quantity on level 1 describes a layer, target quantity on level 2 (marked as HU creating) describes the number of layers on a pallet.

The solution considers the fact that the units of measure entered on the Content level (level 0) will control the stock keeping UoM that you will find on the quantity.

You can apply a custom pattern using BAdI /EWMCP/EX_1XRS_PACK_SPEC_DESCR.

Notice that the 3 CHAR codes for units of Measure are language-dependent. The report can create descriptive texts in multiple languages. If you don't give particular languages in the start screen, texts will be provided for all languages which are currently installed in the system.

NoteAs this is a mass update of master data which cannot be reversed, please handle with care. Use the select options (for example, on Pack. Spec. Group) to restrict the selection.

ExampleFor a two-level Pack. Spec. with content in non-Base UoM, the text will show

Units on Pallet * Eaches per Unit = Total Eaches per Pallet

Technically the following elements are taken from the packaging specification:

● Units on Pallet: Target Quantity on HU creation level, expressed in the unit set on content level for the product

● Eaches per Unit: Conversion into Base units of measure (UoM), as set in Product Master


Extended Warehouse Management Cross Functions

ExampleA three-level Pack. Spec. with content in Base UoM will deliver a text like this:

Eaches per Layer * Layers = Total Eaches per Pallet

Note that LAY is not a unit taken from the product master. It is only an information taken from the convention to interpret the first level as layer. If the unit LAY is not defined in your system (transaction CUNI), the program will use 'LY' for all languages.

2.4 Shipping Cockpit

You may prefer to manage outbound processes using the standard Shipping Cockpit. The Shipping Cockpit can be accessed via transaction NWBC for the role /SCWM/EXPERT, using the path Shipping and Receiving → Shipping Cockpit Planning (or Execution)

Prerequisites

You have assigned the role /SCWM/EXPERT to your user transaction

SU01


2.5 Quality Check Characteristics for Transportation Units

This function is used to report definable characteristics of a Transportation Unit (TU) like cleanliness or pest control via RF devices. It will raise a configurable questionnaire in the specific RF transactions for TU docking, TU loading, and TU unloading. The questionnaire can be different for inbound and outbound TU's.

As a prerequisite for the inbound Quality Control (QC) check, the selected TU needs to be in an active state. The RF dialog (logical transaction CDSHDC) is providing a function (Key F1) for TU activation, if this has not been done yet.

There are two options to retain the collected data; on the TU itself or on the respective Shipping & Receiving (SR) activity. The latter does allow to inspect the same TU upon each arrival and keep a history of the final check results. Both information will be shown separately either as QC value or SR QC value on the TU header in transaction /SCWM/TU.

The collected data appears as a free text field. However, it is intended to hand out barcoded answers on a card for the processor to be scanned. It is also intended to re-execute the QC check for the TU, for example, upon unloading start or after potential issues have been resolved. A repeated QC check on the same TU or SR activity will update the previous data.

There is a BAdI /EWMCP/EX_1XRS_QCPROF_ITEM_GET to change the list of QC fields which will be displayed on the screen to the user. Using this BAdI, you may influence the requested QC items depending on for example, the means of transport used in the process.

Another BAdI /EWMCP/EX_1XRS_QC_CTRL can control if the QC questionnaire will be shown anew even if it had been answered in a previous step. The idea is to inspect the same criteria a second time after the potential issues have been fixed.

Prerequisites

● You have defined up to ten quality check characteristics and suitable profiles in Customizing under Extended Warehouse Management→ SAP Extended Warehouse Management, Add-on for Consumer Products→ 01 – General and Cross→ Define Quality Check Characteristics.

● You have assigned a default QC profile for inbound (unloading) our outbound (loading) in Customizing under Extended Warehouse Management→ SAP Extended Warehouse Management, Add-on for Consumer Products→ 01 – General and Cross→ Define Quality Check Characteristics.

● (optional) For outbound TU's (loading by door process with logical transaction CDSHDQ), you can deactivate the QC questionnaire per Warehouse number in Customizing under Extended Warehouse Management→ SAP Extended Warehouse Management, Add-on for Consumer Products→ 03 - Outbound→ Deactivate Checks during Radio Frequency Load.

● (optional) For outbound TU's (TU docking and QC with logical transaction CDTUDO), you can deactivate the QC questionnaire per Warehouse number in Customizing underExtended Warehouse Management→ SAP Extended Warehouse Management, Add-on for Consumer Products→ 03 - Outbound→ Deactivate TU QC during RF TU docking.

● You have configured the level of data retention in Customizing under Extended Warehouse Management→ SAP Extended Warehouse Management, Add-on for Consumer Products→ 01 – General and Cross→ Transportation Unit Quality Check→ Define TU Quality Check Settings.



2.5.1 Check Transportation Unit and Door Assignment

You can use this RF transaction to dock the TU to the door that is used for the loading and unloading process. The system performs a validation to ensure that door and TU are consistent, and the current TU status does allow docking.

Prerequisites

● You have created a TU (inbound or outbound).

Details and Execution

1. In RFUI, select Inbound Processes→ Unloading→ TU docking and QC (Logical Transaction CDSHDC).2. Enter the TU number and proceed .

○ Select F3 ChgLP to register or change the license plate information on the TU.○ Select F1 ActvTU to set the TU to active (register event 'arrival at checkpoint').

3. After this is done, you can enter a door number, which may deviate from the one you may have assigned earlier. EWMCP will assign this scanned door to the TU and sets the status to Docked to door, provided that new door is technically available

NoteBAdI /EWMCP/EX_1XRS_TU_DOCK_REFDOC allows you to use any reference document to look up the TU number. If the BAdI is implemented, a new multi-purpose field is shown in the TU docking and QC transaction. If you enter a value into this field, the system tries to look up a TU for this value. If this fails, the BAdI is called and the system tries to look up the TU by using the value as a reference document. Note 2355023 also contains an example implementation of the BAdI that tries to look up the TU by interpreting the entered value as a bill of lading (BOL).



2.6 Custom Batch Numbering Logic

This section provides information on creating custom batch numbers.

You can use batch numbering in the logistics processes which require a batch number naming convention to fulfill legal requirements. The rules for batch numbering might be different and they depend on country, material type, and other factors. In this scenario, we assume batch numbers assigned for homogenous pallets. The batch number will be printed on a label and attached to the pallet.

The length restriction of CHAR 10 for batch numbers is also valid in EWMCP.

The control parameter MATGRP for the batch numbering logic is assumed to be replicated from ECC as product group type MT (tab Properties 2). Depending on which algorithm you choose, context information from a production order (document type PPO) can be used as input.

If none of the prepared patterns suit your needs, you can consider implementing one of the EWMCPS4 specific BAdIs /EWMCP/EX_1XRS_BATCH_NUM_BFR and /EWMCP/EX_1XRS_BATCH_NUM_AFT.

Prerequisites

● You have defined batch numbering in Customizing under Extended Warehouse Management→ SAP Extended Warehouse Management, Add-on for Consumer Products→ 01 – General and Cross→ Batch Numbering.

● You have maintained suitable mapping of ECC Material Types in view /SCWM/V_MAPMTART (transaction SM31), pointing to Material Type Group MT.

● Your product is assigned to a corresponding material type group.




You can use this function in EWMCP receiving RF transactions. It provides the following:

● Check if the batch exists in the system and check the corresponding material type.● Check the batch number algorithm type based on the material type and warehouse.

The following algorithms are available with the batch numbering service:

● Algorithm I (Internal batch numbering)Checks if a batch number is blank. If it is blank, the system generates a new batch number from an internal batch number range. If the batch number is not blank it checks for the numbering convention and returns an error for exceptions.

● Algorithm II (Batch numbering based on traceability):Determines the traceability characteristics of the product from product classification data.○ If the batch number is blank and the traceability is ‘Yes’, the vendor batch is checked and the last ten

characters of the vendor batch are used. If the vendor batch is not available, the system generates a new batch number from an internal batch number range.

○ If the batch number is blank and the traceability is blank, the plant code with the first four characters is used.

○ If the batch number is not blank and the traceability is Yes, the batch number is validated against the last teb characters of the vendor batch and returns an error for exceptions.

○ If the batch number is not blank and the traceability is blank, the batch number is validated against the first four characters of the plant code and the system returns an error for exceptions.

● Algorithm III (Date-based batch numbering):Determines the format of the batch from the material classification system.

ExampleMMMDDYYPPB

MMM – Month (for example, DEC) or MM (for example, 12)

DD – day (for example, 25)

YY – year (for example, 13) or YYYY (for example, 2013) or Y (for example, 3)

PP – Manufactory code

B – Last digit of a production line.

If no classification is maintained, the Customizing entry determines the batch numbering format.

NoteYou can determine the last digit of the production line for algorithm III using an additional function, which works as follows:

The system gets the production order from inbound delivery item reference documents.

1. It selects the outbound delivery by production order number.2. It gets the line number from the Production Supply Area (PSA) based on the system configuration -

for example, character 5 and 6 taken from the technical identifier of the Production Supply Area.


2.7 Authorization Objects

EWMCP uses the following specific authorization objects:

Authorizations Extended Warehouse Management SCWM

EWM CP report: Program Shelf life blocking /EWMCP/BS

EWM CP report: ECC quality notifications /EWMCP/EQN

EWM CP report: Delete HU Header data /EWMCP/HUH

EWM CP report: Change HU status /EWMCP/HUS

EWM CP report: Stock update (IDoc) /EWMCP/IDO

EWM CP report: Product master data check /EWMCP/MDC

EWM CP New Repack Transaction /EWMCP/RT

EWM CP report: Staging bin determination /EWMCP/SBD

EWM Add-on for Consumer Products - Staging Functionality /EWMCP/ST



3 Extended Warehouse Management Inbound

EWMCP comes with many TU-related receiving features combined into a unified RF transaction.

These features include:

● Identify objects (for example, HU, product, and batch) using custom barcodes.● Create homogenous Handling Units based on Packaging Specifications.● Introduce new batches (can be switched on/off by configuration).● Create batch-split sub items in Inbound Delivery, if necessary.● Capture and validate Expiration Dates or Production Dates (can be switched on/off by configuration).● Change Packaging Material of a Handling Unit, based on alternative Packaging Specifications.● Change material quantities inside a Handling Unit.● Execute unloading of Handling Units using Warehouse Tasks, provided a corresponding Warehouse

Process is in place.● Create put-away task for Handling Units.● Confirm put-away task for single Handling Unit (can be switched on/off by configuration).● Post Goods Receipt● Observing over-delivery tolerance limits.● Option to highlight pending quality check activities and master data enhancements per product.● Apportion received totals to multiple inbound delivery items.● Set the TU status ‘Unloading completed’ upon scanning the door (can be switched on/off by

configuration).● Use a series of barcoded EAN 128-strings to identify and populate all input fields (‘receiving based on

custom labels’).

To limit the complexity, these features should not be combined at random. In fact, the receiving process needs to follow the Business Process Description (BPD) laid out in the collaterals of the Model Company. There is also a configuration view provided in the Implementation Guide to control screen behavior and expected input data.

Define Configuration for Harmonized RF Transaction

To support a smooth process, please pay special attention to the following master data:

● Packaging Specifications with quantity classifications

Application Help for SAP Extended Warehouse Management Add-On for Consumer ProductsExtended Warehouse Management Inbound C O N F I D E N T I A L 17

● Units of measure and their GTIN identifiers in Product Master● Shelf Life data● Put-away control indicators● Batch level, batch relevance, and batch classification● Mapping of inbound delivery item types

If you prepare for a large variety of issues in receiving, you should consider using a desktop transaction rather than RF dialogs. For example, violations of over-delivery tolerances or the arrival of previously undeclared batches need clarifications using the desktop transactions.

Assumptions

● If ECC does provide batch information in the inbound delivery:○ The batch data is replicated to EWM using a batch-split sub-item.○ The products are already packed (HU information is available in the inbound delivery).○ It is not allowed to receive any different batch other than the ones notified in the Inbound Delivery.

● If ECC does not provide any batch data upfront, the batches may be introduced manually by EWM prior to RF receiving. As ECC requires batch data for the packing process, you also cannot have packing data without batch data.

● Batch-relevant products are assigned to a Product Group Type MT (Properties 2 in /SAPAPO/MAT1) to determine the specific batch naming logic.

● Batch classification provides at least the LOBM standard characteristic Expiration Date.● Over-delivery tolerance checks are unaware of previous inbound deliveries for the same PO item.● An HU being received is always homogenous regarding its combination of Product/Batch/Expiration Date.● Every product received will have at least one valid packaging specification.● Receiving is based on active Transportation Units.● All inbound deliveries on a TU have the same ship-from party (vendor or site).● There are no serial numbers involved.● Only a single user is working on a TU at one time.● In a one-step put-away procedure, the resource is allowed to perform both unloading and put-away task.● The process-oriented storage control is set up to include an unloading step.

3.1 Put-Away of Allergen Materials

In food production, local regulations may determine the storage process for materials containing allergens.

In EWMCP, an add-on to the product master allows you to indicate specific allergen classes for a product. In the current version of EWMCP, there is no integration of allergen information with SAP ECC available. Furthermore, the process focuses on put-away only, so no outbound processes or co-loading rules (like for dangerous goods) are provided.

Limitations for the put-away strategy arise from a combination of product classification as allergen and a neighborhood information taken from storage bin master.


Extended Warehouse Management Inbound

You can use this process in warehouses dealing with allergen materials where the storage restrictions are considered during put-away. You can check and filter storage bins during put-away of allergen products for multiple allergen classes. For each possible put-away bin, the neighboring bins are checked during put-away.

Allergen Management

Prerequisites

● The configuration for the put-away task creation has been set up correctly and every storage bin is configured with reference to the aisle, stack, and level.

● You have maintained the Customizing settings for allergen products under Extended Warehouse Management → SAP Extended Warehouse Management, Add-On for Industries - Consumer Products → 04 - Internal → Define Allergen Products Configuration..


The process is initiated during the filtering and sorting of bins and works as follows:

1. The system checks whether the products are relevant for allergen checks.2. If they are relevant, the system checks if an allergen class is maintained for the product in the product

master data at warehouse level.3. Based on the allergy class check, the system triggers a new process (transaction /EWMCP/

1XRS_ALLG_MNG) to check and filter out the available bins to put-away the allergen products.

NoteYou can use transaction /EWMCP/1XRS_ALLG_MNG to maintain the following:

● Allergen classes that are displayed with a match code in the product master.


● Allergen class groups that allow combining several allergen classes into one group.● Storage restrictions to be checked during put-away.● Maintenance of flags for allergen check and number of bins to be checked horizontally and vertically on

warehouse level.

3.2 Bulk Receiving

EWMCP provides a predefined content for receiving bulk materials (like wheat or sugar) for storage in tanks (Storage Type T031). 'Bulk' in this context means that the products are not handled in Handling Units when they arrive and the destination bin is a silo with commingled stocks. The setting assumes that a tank itself is represented by a handling unit that takes the role of a destination HU.

Receiving in this scenario is running on standard transactions. In the desktop UI, you may point the receiving process to a specific tank (HU) or simply point to a specific storage type where the user can select a tank in RF.

3.3 Inbound Door Proposal for Transportation Unit

This feature complements the standard logic for door determination.

Assuming the standard procedure (transactions /SCWM/STADET_IN and /SCWM/STADET_ASS) is used to propose a door on the delivery item level, there is an option in EWMCP to consolidate the various results on the TU level. EWMCP offers a PPF action/EWMCP/DETERMINE_DOOR for the TU that is triggered upon TU activation. The core logic comes as an example class of BAdI /EWMCP/EX_2INB_DOOR_DETERM, which performs the following logic:

● The system applies a weighting factor to the various doors determined on each Inbound Delivery item and selects the door with the most common occurrence. The weighting factor per door is consolidated from the number of pallets asking for it. If no pallet information is provided, the system queries corresponding Packaging Specifications and estimates the number of (homogenous) pallets.

● The winning door is assigned to the TU and appears as an entry in the 'Assigned Doors' tab of transaction /SCWM/TU. Furthermore, you can follow the course of the algorithm by checking the execution log of PPF action /EWMCP/DETERMINE_DOOR.

Prerequisites

● You have configured the standard procedure for door and staging area determination on Inbound Delivery items.

● (Optional) You have scheduled PPF Action /EWMCP/DETERMINE_DOOR, which is calling method /EWMCP/2INB_DOOR_DETERMINATION.

● You have provided an implementation for BAdI /EWMCP/EX_2INB_DOOR_DETERM. You might want use the example class which is performing the above logic.



● If you want to do a rough estimation for the number of HU’s on unpacked items, you need to provide an active Packaging Specification with Condition Type 0PAL and a level with Quantity Classification = P (pallet) maintained.

3.4 Assign Transportation Unit to Door Monitor Node

EWMCP comes with a simple planning tool for Door-TU-Assignments. It is realized as a monitor node.

Warehouse Management Monitor

You can review the door occupancy situation structured in hourly time-slots. There may be overlapping assignments which can be seen in a detail screen. Using the monitor, you can assign and un-assign doors to active TU's.

3.5 Radio Frequency Unloading by Door

This section describes the unloading by door process using RF devices.

EWMCP mainly considers these receiving scenarios:

1. Homogenous full pallets according to packaging specification and batch information known in Inbound Delivery.

2. Neither HU nor batch is known, but pallets arrive with custom barcode labels identifying the product, quantity, batch, and HU number.

3. All information from the above point (2) need to be entered manually if there is no pallet label available.4. Batches are known, but the information is only available on paper. A preliminary dialog step is needed to

capture the batch data in EWM. HUs will be created upon RF receiving.


It is not intended to mix these scenarios during work on a single TU. Also, an HU should either be declared in ECC or in the RF transaction of EWMCP (that is, it should not be created in a standard EWM packing dialog upfront).

You can use this function for the following purposes:

● Unload the truck including goods receipt posting of HUs when pallets are scanned with an RF transaction.● Set status “Unloading Completed” using an RF transaction.● Create a warehouse task to move a truck from door to yard using an RF transaction (if Yard Management is

active).

The RF functions support one-step receiving (directly perform put-away to final storage) and two-step receiving. For two-step receiving, the process is separated by a handover from an unloading activity to a put-away activity. The pallets are buffered in a staging area, from where a second worker processes the corresponding put-away tasks (which are already created by EWMCP transaction).

RF Receiving Mode

You can use the following RF screens for the inbound processing:

● Door scan screen● HU scan screen● Create new HU screen● Create mixed HU screen● Create Mass HU screen● Packaging material selection screen● Save and put-away screen

The specific RF-dialogs are implemented as logical transaction CDDOSI, which needs to be mounted into the relevant presentation profile. The dialog starts by scanning the door where the incoming truck is docked.

Using the door information, the system provides the TU number and selects all inbound deliveries in the background.



Depending on your receiving scenario, you might also want to describe homogenous or mixed pallets that have not been declared in the document beforehand. To proceed, hit F4 HUcrt.

NoteWhen you test the scenario, please be aware that the information between Transportation Units and the received Handling Units is synchronized by a PPF action /SCWM/SR_SET_TU_SYNC_DLV. For performance reasons, you may not require this with every change to a delivery (see note 1423066 ), so it is fine to have the objects TU, Delivery, and HU objects temporarily out of sync.



3.5.1 Scan Handling Unit

The first screen of the logical transaction is intended to capture data from an HU label using a multi-purpose scan field. You can Scan field, you can scan the HU barcode, starting with Application Identifier 00. The system retrieves and displays corresponding data (such as product and batch) from the inbound delivery.

The dialog can also be enabled to process up to three custom strings to populate all the mandatory fields (such as Product, Batch, BBD, Quantity, and UoM), following the deconstruction rules defined in Customizing under Extended Warehouse Management→ SAP Extended Warehouse Management, Add-On for Industries – Consumer Products→ 02 Inbound→ Radio Frequency Unloading by Door→ Define Non-EAN128 Barcode Attributes.

You can navigate from this screen by either receiving the HU as it is (F2 or F3), or select one of the follow-on activities such as:

● Create a new HUStarting from giving the first Product number, you will be prompted to select a suitable packspec (if not unique) and fill in the batch data. The system can propose existing batch numbers from the inbound delivery, but can also discard the proposal and enter a different batch. Hitting F8 in the batch field brings up a list of potential batches associated with the current TU.

● Identify Pack-SpecIf more than one Packaging specification is active for the product, the system will branch into a selection list. You can use this feature to either propose different pallet sizes (like 1,5 m high and 2m high), and/ or to offer a selection of the Stockkeeping Units of Measure (for example, CAR or EA). After selecting a packspec, the system returns to the Scan Handling Unit screen, taking over the Quantity and Units of Measure selected. This behavior can be influenced by BAdI /EWMCP/ES_2INB_HU_CRTN_UOM. Furthermore, the feature F12 ChQt clears the Quantity field and toggles through all Units of Measure which are known for the Product.

● Create a new batch.This might be relevant if the vendor or shipping site did not declare batch information up front. You must be aware that new batches can only be introduced if no batch information at all was given in the ECC inbound delivery. SAP standard refuses to receive batches other than the ones coming from ECC in this case.

● Select batch from a listThe transaction can be configured to prohibit batch creation at runtime. In this situation, the user can select one of the batches given in the Inbound Delivery by selection from a list (Function key F8) for the batch field. These batches may already be a part of the replicated Inbound Delivery or manually prepared in an upstream transaction like /SCWM/PRDI

● Change the product quantity inside the HUIn case the data from inbound delivery does not represent the real pallet.You must be aware that in this situation also the vendor invoice might be wrong and additional activities need to be done using desktop transactions.

● Change the packaging material



This is a specific situation where the nature of the packaging material is important. You may handle regular pallets and sanitized pallets and need to trigger certain follow-on activities based on the packaging material type. The system exchanges the packaging material while keeping the rest of the HU data identical.

The NxtHU pushbutton discards uncompleted barcode scans - for example, unreadable barcodes - and initializes pallet/HU data.

Scan Pallet Bar Code

The following applies:

● Pallet barcode scans are not allowed for empty TUs - that is, TUs without inbound delivery assignment. TUs without assigned inbound delivery allow only “unloading complete” barcode, which is the door number.

● When an HU is scanned and the HU already exists (inbound delivery is packed), information for the remaining fields is displayed, if available.

● The information remains visible even after the goods receipt for the HU is posted. The fields are cleared when the next barcode is scanned.

● The screen has a unique field provision validation - that is, a barcode field (for example, batch) can have only one barcode.

● The system performs an automatic HU goods receipt posting after a certain number of scans; otherwise an error is raised.

● The system performs HU validation for product, batch, and quantity.● The system calls the Packaging Material Selection screen if more than one packaging specification is found.● Retrieves packaging material from packaging specification using “Create HU” indicator on level type.● Batch creation is performed using custom batch numbering algorithm per material type.● Applies batch split item logic if there is a need to create batch split items.● Creates and confirms HU unloading warehouse task (if warehouse process contains this step).● Creates put-away warehouse task (if warehouse process contains this step).

Scan Unloading Complete Barcode

This an optional feature you can activate in Customizing: If the door identification is scanned into the neutral 'Scan' field, the system sets the TU status to "unloading completed" and returns to the door scan screen. It locks the TU to avoid parallel unloading completion and sets the loading end date. The same applies if you leave the transaction after all received delivery items have reached the 100% level.

Create New Handling Unit

You can use this dialog if the Handling Units are not provided in the inbound delivery.


Press F4 and select the product ID first. The system looks up for a valid Packaging Specification and asks for the right one if there are multiple options. Products without a Packaging Specification are rejected.

After selecting the Packaging Specification, the dialog gathers batch characteristics and quantity information.

The data gets validated against requirements for remaining shelf life and over-delivery tolerance issues. Depending on the data received in the inbound delivery, a new batch number may also be introduced. Batch numbering can be influenced in EWMCP Customizing to reflect custom naming requirements. The system also proposes a batch number existing in the current inbound delivery. However, if you force the creation of a new batch (for example, because of a deviating production date), new batches can be created. You must be aware that new batches can only be introduced if the replicated inbound delivery notification does not already specify a batch.

Once all data is entered and validated, you can decide to continue unloading the next HU (F2) or finish the process by moving the pallet to the destination bin directly (F3).

If you continue by F3, the follow-on screen asks for a confirmation of the put-away into the destination bin.

Please note that the application actively creates put-away tasks in the background. This implies that the process steps for the incoming Handling Units involve both unloading and put-away, and that the put-away step is configured as non-automatic.



Verify Bin Access Type for Putaway

In the course of one-step putaway, the system checks if the current resource is allowed to perform the put-away. If a Bin Access Type is maintained at the destination bin, a check against the customized allowed Bin Access Types of the resource is executed.

If the check is negative, the system un-assigns the Warehouse Order from the current resource and issues a 'Task is not allowed for resource' message. The HU remains in the unloading bin and awaits a different resource to complete the put-away step.

NoteBe aware that a resource type with no restriction maintained is allowed for all bins. At the same time, bins with no BAT maintained can be accessed by any resource.

Scenario 2: EAN128 Barcodes

Relating to receiving scenario 2 from above, the screen data of the HU scan screen can also be populated by scanning several barcodes in a row (maximum 3). One barcode string might contain product and quantity; and a second string might deliver batch and production date. The system evaluates the string structure and populates the corresponding screen fields accordingly.

After three scans or after pressing F2 or F3, the HU processing continues as in scenario 1 - this is, controlled by the flag 'Auto GR' in Customizing for the harmonized RF receiving transaction.

3.5.2 Homogenous Cross-Delivery Handling Unit

One specific scenario describes the receiving of one homogenous HU that can be related to several delivery items within one TU.

Sometimes a vendor consolidates separate purchase orders for the same product and batch on a single HU but does not send packing information or batch data up front.

In this special case, the system apportions the total quantity of the HU to all potential reference items on the TU. Over-delivery quantities are distributed up to the consolidated maximum of all respective items.

Prerequisites

To produce reasonable results, the roles Entitled (ECC site) and Ship-from Party (ECC vendor) need to be identical on all inbound delivery items within the TU.


3.5.3 Mass Create Handling Unit

If you need to receive a large number of identical homogenous Handling Units, you can run the unloading transaction using a repetition factor (number of HUs to be created).

This feature is triggered by the button F8 MHUCr from the 'Scan Handling Unit' screen. The data to enter is the same as for a single HU receiving, but there is no option to post a one-step receiving in this context.

3.5.4 Create Mass Handling Unit Screen

If no Handling Unit information is provided with the Inbound Delivery, EWMCP allows you to declare mixed Handling Units upon RF receiving. Select 'F4 Create HU' to enter the first product for the pallet. After this is done, you can continue to add products using F12 Pack.

Once the entire pallet is done, leave the procedure using F2 save..

NoteThe program keeps the information in an internal table until it is finalized by the F2 command. One step, however, is executed upon each F12 step, which is the creation of a batch split item in the Inbound Delivery. If you have to interrupt the pallet building process, this step needs to be manually reversed.

Because only one packaging material can be used for the mixed pallet, the system ultimately uses the one from the last packed product's Packaging Specification.



3.6 Dock Transportation Unit to Door

When a TU enters the yard, it is supposed to identify itself while passing a checkpoint. EWM registers this event by setting a TU header status to Active.

The next anticipated step in the process is the docking to a specific door, if the particular door is currently available. The planning activity of door assignment itself is not supported by RF but can be done using the dedicated monitor node Door overview inbound , using the standard desktop transactions /SCWM/TU or /SCWM/DOOR or using the EWMCP feature Inbound Door Proposal for TU.

In EWMCP, the arrival of a TU in the yard and the docking to a door can be handled using RF. The user can activate a TU by pressing the corresponding buttons in the TU docking and Quality Check transaction. In the background, the system will create and confirm the necessary yard movements and update the status of the TU (Status CHKI and DD).

NoteDepending on your process, you may already have door assignments prepared for the TU. An existing suitable door assignment of the TU will either be activated, or it will be deleted and replaced by a new one pointing to the door which was actually used.

This behavior does not allow to prepare multiple stops of a TU for unloading. After successful docking via the EWMCP RF transaction, you will not find any other planned door assignments on the TU.

To simplify the way an RF user can identify a present truck, BAdI /EWMCP/EX_1XRS_TU_DOCK_REFDOC is provided that allows you to use any reference document to look up the TU number in the system. If the BAdI is implemented, a new multi-purpose field is shown in the TU docking and QC transaction. If the user enters a value into this field the system tries to find a currently active TU for this value.

An example implementation of the BAdI tries to look up the TU by interpreting the entered value as a bill of lading (BOL).

For statistical reasons, it might be required to capture the actual license plate ID of the truck. The TU docking and QC transaction displays the license plate if it is known from the TU data. The user can overwrite it by clicking the corresponding button, thus updating the TU header information.

Prerequisites

● A default checkpoint for the user should be stored using transaction /SCWM/CICO.


Transportation Unit Docking and Quality Check Screen

You can use this screen to identify and activate a TU (that is, set status CHKI In Yard). Once the TU is active, the transaction prompts for an available inbound door to be entered. Assuming the user is declaring the actually used door here, the system may generate a corresponding new activity for the TU and perform the docking to a previously unforeseen door.

Using the F3 Change License Plate feature, you can enter/ overwrite the license plate ID and the registering country of the truck.

Press Enter, to display the quality check questions if they have been defined in Customizing. You can define a different set of questions for loading and unloading, and you can also influence the presented questions using a BAdI.



After pressing F1 Save, the TU will be available at the door to start unloading.

Prerequisites

You have maintained the QC questions under Extended Warehouse Management → SAP Extended Warehouse Management, Add-On for Industries - Consumer Products → 01 General and Cross → Define Quality Check Characteristics.

3.6.1 Mass Create Handling Unit




3.6.2 Create Mixed Handling Unit

If no Handling Unit information is provided with the Inbound Delivery, EWMCP allows you to declare mixed Handling Units upon RF receiving.

Select F4 Create HU on the screen to enter the first product for the pallet. After this is done, you can continue to add products using F12 Pack.

Once the entire pallet is done, leave the procedure using F2 Save.

NoteThe program is keeping the information in an internal table until it is finalized by the F2 command. One step is however executed upon each F12 step, which is the creation of a batch split item in the Inbound Delivery. In case of interrupting the pallet building process, this step needs to be manually reversed.

As only one packaging material can be used for the mixed pallet, the system will ultimately use the one from the last packed product's Packaging Specification.

3.7 Unloading Completion

After unloading the last HU from a TU, you can scan the door into the 'Scan' field. This sets status UC (unloading completed) on the TU. Further processing, like differences clarification, needs to be done via a regular desktop UI.

There is a PPF action /EWMCP/TU_MOVE_DOOR_TO_YARD available to automatically move the TU from its door to a checkpoint. The checkpoint needs to be configured in transaction /SCWM/YM_CHKPT_BIN.

At the same time, you might want to synchronize the TU with all delivery and HU information according to SAP Note 1991980 .

To release the door again, you need to remove the TU in an additional step (which is different with or without Yard Management).




Prerequisites

● You have maintained your yard configuration, especially/SCWM/YM_CHKPT_BIN and /SCWM/YM_DOOR_BIN.

In addition to scanning the door number in the Unloading by Door + Put-away dialog , you can use the TU docking and QC transaction to complete the process. If you scan the TU number and continue with the function key F2 (Completion), the TU will be undocked and moved out of the checkpoint.

3.8 Mass Create Handling Unit



3.9 Create Mixed Handling Unit

If no Handling Unit information is provided with the Inbound Delivery, EWMCP allows you to declare mixed Handling Units upon RF receiving.

Select F4 Create HU on the screen to enter the first product for the pallet. After this is done, you can continue to add products using F12 Pack.


Once the entire pallet is done, leave the procedure using F2 Save.

NoteThe program is keeping the information in an internal table until it is finalized by the F2 command. One step is however executed upon each F12 step, which is the creation of a batch split item in the Inbound Delivery. In case of interrupting the pallet building process, this step needs to be manually reversed.

As only one packaging material can be used for the mixed pallet, the system will ultimately use the one from the last packed product's Packaging Specification.

3.10 Receiving from Another Plant (ICT)

This section describes the process for intracompany stock transfers.

There is a special procedure intended for intracompany stock transfers (ICT). Other than receiving from external vendors, the sending side might also be controlled by SAP ECC or EWM and the transit stock and TU is monitored for both sides of the transfer. This presents some restrictions in the handling of unexpected situations upon receiving. In general, an ICT process is more restrictive in terms of unknown batches, unexpected HU's and over-deliveries, because all goods receipts need to correspond to a suitable goods issue on the other side.

In case your actual activities produce problems like this, you should apply a manual process using differences handling on both sides. There is also the SAP consulting note 2190855 available which proposes an automatic handling in certain situations.

In EWMCP, an ICT process is detected using a configurable item type in the inbound delivery. To distinguish between external receiving and ICT, you can use the differentiation attribute in the ERP interface to control different item types to be created in EWM.

A user in RFUI will not notice which scenario he is currently working on. However, ICT processing will disallow over-deliveries and new batches to be introduced for ICT.




Prerequisites

● You have configured the scenario determination in Customizing under Extended Warehouse Management → SAP Extended Warehouse Management, Add-On for Industries - Consumer Products → 02 - Inbound → Item Types relevant for ICT scenario.

● You have configured the Item Type determination so that Inbound Delivery items result in a dedicated ICT item type.

3.11 Receiving Store Returns

This scenario is based on a setup for the retail industry, where the warehouse serves as a supplying entity for many stores.

There are several reasons why these stores decide to return previously received merchandise to the DC, for example, end-of-season clearance or product recalls.

The returns scenario is primed in ECC by a Stock Transfer Order with Returns indicator or by a Returns Sales Order. Subsequently, an inbound delivery and Handling Units are being created by the store as mixed pallets. Items subject for Batch Management in the DC can receive a dummy batch in order to allow HU creation.

The stores also execute their Goods Issue posting so the pallets to be received by the DC are currently posted transit stock when the truck arrives. To avoid inconsistencies, EWMCP always receives the pallets in full, once they are scanned.

In a second step, a user deconsolidates the pallets and verifies the contents. Overages and differences are posted against a difference bucket on account of the DC. Real batch numbers can step in for an initially declared dummy batch.

NoteThere are a number of SAP Fiori apps available to support these store activities, such as App ID F2449 (https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps('F2449')/S9OPTransfer Products).

Prerequisites

● You have set up the packing and the returns delivery process in ECC.● You have made the optional settings in Customizing under Extended Warehouse Management→ SAP

Extended Warehouse Management, Add-On for Industries – Consumer Products→ 02 – Inbound→ Radio Frequency Returns from Store.

● You have maintained a packaging specification 0PAL to propose a packaging material and maximum quantities as destination for the deconsolidation process.



1. To receive an incoming returns HU, start the Register Returned HU (logical transaction CDRHHU) transaction and scan the HU number.

If no errors occur, the transaction does not give any confirmation message, so you can keep scanning HUs without interruption.

2. You can deconsolidate the received HU. As a preparational step, you must first log on to a deconsolidation station (for exaple, Work Center DEC1 from EWMCP default setup). You can follow the subsequent postings via desktop UI in transaction /SCWM/DCONS.



Once this is done, you can continue with the dialog for Returns HU Counting (CDRSHU).


3. In the dialog, identify one of the HUs in the work center.4. Start scanning the products and enter the counted quantities. The respective Units of Measure will be

determined either by a Packaging Specification (Condition Type 0PAL, Unit used on level ‘Content’) or you can force a user entry in Base Units of Measure by configuration.



5. Select F4 Next. The system determines a destination pallet in the work center that has the identical batch and Units of Measure already stocked. The pallet must have the free capacity, that is, the current quantity on the pallet does not exceed the quantity for the pallet level of the Packaging Specification. If this is not found, you are prompted to introduce a new pallet.


You can print a pallet label for the new pallet using the standard PPF action HU_LABEL in action profile /SCWM/HU. After confirming the physical transfer from the incoming pallet to the destination pallet, you are returned to the initial dialog where you can either continue scanning products or finish the deconsolidation procedure by pressing F3. In case of discrepancies, you see an overview of the encountered differences.

Positive differences (unexpected findings) trigger a direct goods receipt into the destination pallet within the work center. Missing quantities remain on the source pallet until the process is declared finished by the user. Only then is a direct Goods Issue posted to clear the stock.



Each line is identified by a letter that signifies the nature of the difference:

● M – Missing quantity of the product compared to the original HU.● E – Extra quantity of the product compared to the original HU.● B – The different batch number was identified than originally advised in the inbound delivery (for example,

dummy batch replaced by real batch).● U – Postings resulting from a different Units of Measure in receiving and counting.

Once you decide to put away the resulting homogenous pallets, you need to create an ad-hoc warehouse task (for example, Warehouse Process Type 1030) using a standard RF dialog.

NoteYou can influence the ECC integration for these movements in different ways. You can use BAdI /SCWM/EX_ERP_GOODSMVT_EXT to derive special ECC Goods Movement types from the field CT_GOODSMVT_ITEM-MOVE_REAS, or you can map the configured reason codes under SAP Extended Warehouse Management→ Interfaces→ ERP Integration→ Goods Movements→ Map EWM Reason Code to ERP Reason for Movement.

.

3.12 Product Master Validations

EWMCP offers a new validation transaction /EWMCP/MD_CHECK to check predefined fields that must be filled for all products in the warehouse. In case any of the specified fields is not maintained, the product will be listed in the report, and receives a marker in a corresponding master data field.

The program also removes the marker after the master data has been completed. The following data can be marked as relevant for checking:

● Warehouse product group on product master● Slotting status on product master● Fixed bin for material● Weight indicator● Capacity consumption on product master● Weight (gross and net) on product master● Volume on product master● Dimensions on product master (length, width, height)● Maximum weight on packaging specification – pallet level, for all available pack-specs of the product● Hazardous substance master for hazardous products● Measurements for base units of measure on product master

The incompleteness marker can be evaluated during RF receiving, if a corresponding control flag is set in the RF receiving configuration. After a corresponding product is identified, the system will present an error to the user.


NoteThe solution offers three BAdIs within enhancement spot /EWMCP/ES_2INB_REC_MD_CHEKS:

/EWMCP/EX_2INB_MDC_MAT_SEL - Change Material Selection for Material Master Data Checks

/EWMCP/EX_2INB_MDC_ADD_CHECKS - Perform Additional Material Master Data Checks

/EWMCP/EX_2INB_MDC_ADD_ACTION - Perform Additional Actions for Material Master Data Checks

With these BAdIs, you can control the entire selection, nature of the checks and follow-on actions by custom logic, if required.

Prerequisites

● You have configured the SAP Extended Warehouse Management, Add-On for Consumer Products → 01 General and Cross → Maintain Product Master Data Validations.

● You have configured the SAP Extended Warehouse Management, Add-On for Consumer Products → 01 General and Cross → Maintain Excluded UoM for Product Master Data Validation.

● You have activated the check for RF validations in Customizing under SAP Extended Warehouse Management, Add-On for Consumer Products → 02 Inbound → Radio Frequency Unloading by Door → Define Configuration for Harmonized Radio Frequency Transaction.

3.13 Quality Check Request and Monitoring

This process leverages a simplistic idea of quality check, where the receiving clerks perform all relevant checks directly on the ground.

The user is prompted to perform an inspection, and his or her confirmation is registered and monitored.

After receiving an item that is relevant for checking, an additional RF screen appears requesting that a sample of the product be inspected. The user is responsible for performing the requested action and confirms the dialog.



When you click Enter, the receiving process continues. In addition to directly interfering with the Goods Receipt, EWMCP provides a monitor node to show an overview of the registered activities (Path: Inbound → Quality Inspection). Using the resource, the user is identified and held responsible for the accuracy of his or her actions.

Prerequisites

● You have configured your product and quality inspection rules (MM01 Quality Management view and /SCWM/QRSETUP).

● You are using the simplified QM integration (no inspection type needed).

● You have activated the inspection for Object Type 4 in Customizing under SCM Extended Warehouse Management Extended Warehouse Management Cross-Process Settings Quality ManagementBasics Warehouse-Dependent Activation of Inspection Object Type .

● You have implemented BAdI /EWMCP/EX_2INB_QIE_CHKS. There is an example class /EWMCP/CL_2INB_QIE_CHKS provided which you can use in an own implementation (for example, build a custom table to hold statistics of QI). Besides the BAdI, there is no further action required to activate the EWMCP logic.

3.14 Printer Determination Based on Handling Unit Position

In receiving, you have the option to identify the relevant printer for HU label printing based on the current position of the HU.

This is useful if you have placed several printers in your receiving area, serving specific doors.

The solution can even locate HUs that are still to be unloaded by reading their goods movement bin. The corresponding bin and storage type is provided at runtime via a BAdI and can be evaluated in a custom condition table for the printer determination. The field catalog for the condition table has been enhanced by fields for bin and storage type.


Prerequisites

● You have configured the HU printing features under SAP Extended Warehouse Management → Cross-Process Settings →Handling Units → Basics →Print .

● You have provided a custom condition table using the fields PHU_VLPLA and PHU_LGTYP.

3.15 Capacity Check on Pick and Drop Area

You can use this function during the put-away when you need a capacity check for pick and drop (P&D) bins.

This function is called during the inbound warehouse task creation at the time of source bin determination that checks the existence and available capacity of P&D area to determine the destination bin.

Prerequisites

● You have maintained the configuration related to the put-away process and the layout-oriented storage control.

● You have defined a P&D area as an intermediate storage bin in the layout-oriented storage control.● The inbound delivery from production has only one item.


This function is called during inbound warehouse task creation during the filtering and sorting of bins. It checks for available capacity in the P&D area for destination bins, as proposed by the standard function, and filter out bins if the capacity is not sufficient.

The P&D bin determination process runs as follows:

● The system checks if the inbound delivery process is relevant for put-away from production.● The standard configuration of layout-oriented storage control is retrieved by the source storage type,

section and the bin of the warehouse task after checking if a layout-oriented storage control is relevant for the current warehouse task.

● The P&D area is determined based on the layout-oriented storage control definition.● The bin sequence, sorting, and filtering is performed based on the setup and available capacity of the P&D

area.● If no P&D bins are available, the standard logic is used to determine the bins according to the storage type

search sequence configuration.



3.16 Receipt from Production Site

This scenario contains two steps to simplify a constant receipt of pallets from a production site. EWM will first introduce an incoming pallet and hold the stock in a dedicated movement bin, while the actual stock synchronization with ECC represents a separate activity (batch job).

This way you can decouple the events of receiving and the ECC communication, which is especially useful if you want to equalize the data traffic towards ECC during the day.


You can declare the receipt of a pallet using the method 'Create Stock from Production' which is mounted to the monitor node 'Storage Bin'.

The method summons a pop-up to capture data.


When the data is successfully saved, a new HU (and batch, if required) will be posted on the selected storage bin. At the same time, this goods entry is registered in a buffer table that will be processed later by transaction /EWMCP/2INB_RFC_STCK or a corresponding batch job.

The procedure is also integrated into the EWMCP concept of quarantine. So, pallets received may be quarantined from the moment of arrival in EWM and released later, regardless of the ECC communication.

Prerequisites

● You have maintained the control settings in Customizing under SCM Extended Warehouse Management → Extended Warehouse Management, Add-on for Consumer Products → 02 Inbound → Receiving from Production Site.

● You have mounted the method /EWMCP/2INB_MONITOR_GR_ADV into your version of the EWM Monitor (see SAP Note 2703754 for an instruction).

NoteIn Enhancement Spot /EWMCP/ES_2INB_GR_MON, you will find several BAdIs to control data entry, enrichment, and verification.

There is also an option to bypass the user dialog by calling Function Module /EWMCP/2INB_API_GR_PROC_ADV, which is designed as an Interface to populate the buffer table in a custom program (for example, to integrate a Material Flow System).




4 Extended Warehouse Management Outbound

EWMCP offers support for special picking and shipping procedures. Along the supply chain, three different warehouse types are considered: for production, central storage, and wholesale distribution. All of them face their typical customer structure, storage behavior, and handling requirements.

A warehouse for production supply will be mainly driven by planned replenishments and handle large quantities of a relatively limited number of products and basically one customer. These tasks are often supported by automatic storage and retrieval systems.

Wholesale distribution on the other side needs to serve various customers, and may also keep merchandise from external vendors in storage. Here, small parts picking and human resources are often combined with specific machinery, which needs to be coordinated.

EWMCP provides additional settings for wave templates and warehouse processing types intended to support these processes.

Process Flow for Outbound

4.1 Outbound Door Availability Report

You can monitor the door shipping and receiving activity using a special monitor feature. The function provides an overview of door activity in the defined timeslots, checks the details of the assigned TUs, enables users to change time intervals for the existing door - TU assignments, creates new door - TU assignments, and deletes existing assignments.

Application Help for SAP Extended Warehouse Management Add-On for Consumer ProductsExtended Warehouse Management Outbound C O N F I D E N T I A L 47

The function consists of the following:

● A node in the EWM monitor that displays a detailed report for door availability to enable:○ Display of door-transportation unit (TU) assignment with fixed time intervals (60 minutes).○ Detailed information for TU and the assigned time intervals for door- transportation unit.○ You can assign a TU to the selected door and define the time interval of the assignment.○ You can change and delete the time interval of the TU-door assignment.

A door can be assigned to multiple TUs at the same time (planned assignments), however, only be one of them can be active at the given time. The expected duration of occupancy is entered manually when the door assignment is carried out.

A TU can be used multiple times (like a truck coming in every day). The feature is designed to encounter only one planned activity for a TU. You receive an error if there is more than one planned S&R activity registered for a TU.

Door Occupation Planning and Transportation Unit Assignment

Prerequisites

You have enabled the node in the EWM Monitor for the door availability function, using standard EWM configuration.


Extended Warehouse Management Outbound

Door Availability Report

4.2 Release Transportation Unit for Staging (RTS)

Release TU for Staging is a logic processing block that allows you to manage picking processes driven by outbound truck loads.

It is assumed that TU planning and delivery assignment is provided by a separate application (for example, SAP TM). This planning should consider the truck capacity, and the staging area/staging bay setup should generally be suited to handle the expected volumes.

Once the TU is planned and scheduled, you can start a fine-tuning of picking processes, using the TU as a process driver and its assigned door to manage the staging logic.

ExampleFor your upcoming deliveries, you can identify unit picks (less than one pallet) and full pallet picks. You decide to filter two separate types of picking waves:

● Unit Picks: This wave is started five hours prior to the arrival of the outbound truck. This wave is subject to cartonization rules and the picking results get parked in a dedicated Pick & Drop storage type.

● Full Pallet Picks: This wave is released by the door assignment of the outbound TU.

A further feature of the RTS is considers the loading sequence for multi-stop shipments and a weight balancing for the truck placement. This is done by managing bins within the staging area and their corresponding target spot inside the trailer. The system will position heavy pallets preferably close to the axles and in the center aisle. Pallets that had been pre-picked will also be considered and called off to the assigned staging position via ad-hoc tasks.


Picking and Staging Process

Prerequisites

● You have configured the Wave Template determination based on Quantity Classifications.● You have configured suitable picking strategies for large/small quantities and batches.● You have configured the EWMCPS4 settings for Staging.● Different wave types are created in SAP EWM to differentiate between layer picking, full pallets picking,

special activities, and manual picking.● You have configured the cartonization features of EWMCP template with its Planned Ship HU logic and

Packaging Specification.● You have configured the Process-Oriented Storage Control for Handling Units.● You have configured the EWMCP settings for Staging.● You have defined the warehouse structure with an appropriate layout for staging, loading, and door

assignment.● The TU is assigned to door and an outbound delivery is assigned to TU and to the waves.● Staging directions and sequencing are predefined.● Delivery items are packed into HUs.


Enter the EWM Monitor and select the node 'Transport Unit Header Outbound'.



Once you select a TU, you can call the monitor method 'Release TU for Staging'. A pop-up screen is displayed to confirm the processed activities.

NoteThere is an option to create the resulting Warehouse Tasks in a blocked status (Release TU blocked). This is helpful if an automatic storage and retrieval system is connected and you need to start its activities manually. Unblocking can be done via the standard transactions or by using the monitor node by selecting Release TU for Staging on the same TU.

4.3 Staging Area Management

EWMCP provides new features to manage staging areas associated with outbound doors.

In Customizing, you can assign one or more staging areas to a door (for example, one to the left, and one to the right of the door). You can also use the same staging area to support two doors in a kind of shared usage.

In case the staging area is not unique per door, the system will prompt you for a manual selection during RTS. The appearing pop-up will show both the calculated number of HU's to be staged and the available free bins within the potential staging area.

These bins inside the staging area get reserved for HU's during the RTS procedure. The system collects all pallets to go on the TU into a wave and calculates an optimal lineup inside the staging area. Technically, this is realized as an intermediate step after Wave release. The wave will initially create Warehouse Tasks in a blocked status. RTS will manage the staging bin assignment and will finally release the tasks. Tasks that did not find a staging bay (for example, due to overflow) may or may not be canceled, depending on a Customizing setting in the RTS configuration.

The below-mentioned option 2b is also considering two bins to remain empty in order to physically separate the set of pallets going on different TU's. You can customize the number of bins that will be considered as 'delimiter' between the two TU's Customizing under SCM Extended Warehouse Management → Extended Warehouse Management, Add-on for Consumer Industries → 03 Outbound → Staging → Define Block Size for Staging Areas


Staging Area Selection Screen in Case of Multiple Options

Four options to structure staging areas

NoteEWMCP assumes 1:1 relationship between bin and pallet.

There is a detailed log available to follow the steps of RTS.



The result is shown in the monitor if you hit the button 'Staging Result'.


4.4 Staging Result ReportingThe staging result feature collects all Handling Units from three different picking techniques and can also handle three different whereabouts (sitting in a bin, in a TU, and on a resource).

The information is updated as picking goes on.

Pallets may result from:

● Full Pallet Pick: They are shown with their original HU number and their current location.● Partial Pallet Pick: They (Mixed HU, also called Unit Pick) are initially shown as Planned Ship HU numbers

seemingly sitting on a specified handover or buffer bin (for example, TPHU-PALLET-PICKUP). The data gets subsequently replaced by actual data as picking proceeds.

● Bulk Picking: They are initially displayed using a temporary ID, which will be replaced by the picked HU once picking is executed.

The report also shows information about the intended staging bin in front of the door which is the result of the staging bin assignment algorithm. It also displays the Stop Sequence and Loading Sequence, which are potential input parameters for the staging bay assignment.

The field Storage Bin shows where the pallet is currently located.

The HU number shown can be an actual HU or a dummy number representing a calculated PSHU which is still to be produced by the pickers or a pick from bulk where the real HU number has not yet been selected by the picker. While picking proceeds, the temporary numbers will be replaced by the real HU number.

Prerequisites

● You have configuredSAP Extended Warehouse Management, Add-On for Industries - Consumer Products → 03 - Outbound → Staging → Release TU for Staging Configuration.

● You have created your Master Data for Doors, Staging Area, Staging Bin definition, and the corresponding assignments in Customizing underSAP Extended Warehouse Management → Master Data → Warehouse Door .

● You have set up the standard door determination logic in transaction /SCWM/STADET_OUT.

4.5 Loading SequenceThe topic of sequencing relates to both sorting deliveries (reversed stop sequence) and the arrangement of pallets designated for a particular stop. Both finally determine the loading sequence for a truck.

The stop sequence is assumed to be predefined by a planning system and communicated to EWM using IDOC SHPMNT05. .

NoteBAdI /SCWM/EX_ERP_LE_TRA_IN can be used to change the way the system determines the stop sequence upon receiving IDOC SHPMNT05 (see /EWMCP/EI_2INB_ERP_LE_TRA_IN).



Note

The SAP Note 2525519 describes an option to manage load and stop sequence via the EWM monitor.

The loading sequence can internally sort pallets according to their weight and apply a 'light-heavy-light' pattern to place the heavier pallets in the center aisle of a three-aisle truck. If you are loading a two-aisle truck (for example, holding industrial pallets), the identical method also leads to an equal distribution of heavier pallets. This is an optional feature also called weight balancing, which is to avoid a critical road handling of the vehicle.

You can activate this logic in Customizing under SAP Extended Warehouse Management, Add-On for Industries - Consumer Products → 03 - Outbound → Staging → Release TU for Staging Configuration by setting the field 'DlvLoadSeq' to BLANK. Refer to the F1 Help in this field to see alternative sorting options.

Placing heavier pallets on every third position in a three-aisle schema and in a two-aisle schema. Both result in a more balanced picture for the truck

To control a loading sequence, it is assumed that there is a fixed relationship between the structure of the staging area and the final position of a pallet inside a truck, so the system actually assigns spaces on the warehouse floor.

Once the pallets are staged in the right way, the warehouse workers have a routine to systematically move them to a corresponding position inside the truck.

Prerequisites

● You have defined the warehouse structure with an appropriate layout for staging, loading and door assignment.

● You have set up a staging/loading area layout with appropriate staging and loading direction where each bin in the trailer (TU) has a corresponding bin in the staging area.

● Number of HUs per TU should be <= 45 (1-36 for fixed bins and 37-45 for extra bins).



● Staging directions and sequencing are predefined.● Loading direction and sequencing are predefined.● Cartonization has created planning HUs for all deliveries of the TU for picking of pallets.● Delivery items are packed into HUs.

Staging/Loading Area Layout with Staging and Loading Direction


You can use this function to perform staging bin determination for a warehouse, TU, and wave (optional).

As the staging area represents the TU loading sequence, the staging bin determination considers all rules listed below relevant for loading sequence determination.

● Staging bin determination is calculated based on the results of the cartonization (refer to cartonization planning).

● Staging bin determination is performed based on delivery item HUs. This is based on the results of picking and staging (refer to picking and staging).

● The staging sequence already considers the delivery sequence within the TU, based on the sequence of stops during the transportation process.

● Weight balancing rules are considered (refer to picking and staging).



Staging Bin Determination Based on Delivery Sequence

Loading Sequence in a Trailer

The feature is both available as standalone report /EWMCP/3OUT_STAG_BIN_DET and as an integrated procedure called during the RTS activities.

This is based on planned shipping handling units (PSHUs) determined by cartonization, delivery sequence within the TU (sequence of stops during the transportation process) and weight balancing logic determined through the staging bin determination function. For full pallets, the staging bin determination is called during the wave release.

The loading sequence process consists of the following steps, performed by the system:

1. Retrieve TU.2. Check that TU is assigned to a door.3. Determine the staging area and bins via the door number.4. Retrieve outbound deliveries by TU (S&R activity).5. Sort outbound deliveries by delivery sequence.6. Retrieve PSHUs created for outbound deliveries.


7. Check if the number of PSHUs per TU are <= 45.8. The staging bin assignment in PSHUs is updated based on delivery sequence and weight balancing logic.

4.6 Filtering and Rounding Rules

This is a collection of features that can be combined to manage multi-deep storage and non-equalized pallet quantities at the same time.

Multi-deep storage implies that the bin holds several comparable pallets, but only the front one is accessible to the picker. As more than one picker might be sent to that bin during an ongoing picking wave, it is impossible to predict which pallet will be in front at the time the picker arrives. So, the task creation can only request a pick to happen from a specific bin and batch, but not from a specific handling unit.

The EWMCP solution for this scenario is considering an option to select one specific pallet inside a multi-deep storage bin. As the system does not generally request a specific HU number, the picker is guided to the bin where he or she can identify the HU he or she intends to remove. However, if the removal task is created to accept a specific HU only, the picker gets a message that a different pallet is intended to be picked (‘Pick other Pallet’ behavior).

Non-equalized-pallet quantities address the fact that the HU contents might slightly vary against the pack-spec quantity. For instance, a pallet of powder should contain 1.000 kg, but the real quantities vary between 950 and 1.050 kg. This is the use case for rounding rules, both at task creation and task confirmation to allow some fuzzy logic for picking optimization.

NoteAny rounding up and rounding down operations present substantially different issues to the system.

Rounding down leaves the fulfilment considerations with an unprocessed quantity. EWMCP would normally start a second attempt to retrieve the remaining quantity. If you are allowed to short-pick your requirement, it is often required to stop ('abort') the search for additional stock and consider the requirement closed at this point. To control this, EWMCP uses a combination of warehouse process type (signifies for example an internal replenishment) and source storage type (for example, the bulk storage type with non-equalized pallets).

Rounding up, however, can result in an over-fulfilment of the original requirement. External customers might refuse to pay for over deliveries, so this rounding direction does require an agreement with the customer. Documents received from ERP need to allow a corresponding over delivery percentage , if quantities are increased by adjustments.

In any case, you need to consider that systematic rounding may affect a service KPI for the warehouse.

Besides managing non-standardized pallet sizes in bulk storage, there is another use case represented in EWMCP. This pertains to the handling of variable pack sizes. In addition to the standard EWMCP procedure which considers a preferred pack size already upon task creation, the EWMCP scenario is assuming a Units of Measure-agnostic picking strategy such as fixed bin picking. However, the requested quantity is rounded up to a multiple of the very Units of Measure which has been encountered in the source bin. As described in the above note, the deliveries need to tolerate an over delivery in this case.

Another situation considered by EWMCP is the handling of layers. This may be relevant for production supply plants that are equipped with an automatic handling device (Robot) for pallet layers. To control this process,



the ability to identify and manage complete layers is essential. Outbound pallets can be stacked layer by layer, also considering auxiliary packaging materials (slip sheets) defined in a suitable packaging specification.

During the pick task creation, there is also a procedure called ‘abortion’. Forcing this ends the system’s attempt to fulfill a requested quantity. EWMCP takes advantage of this when the number of pallets is more important than the requested quantity. One usage is in staging for production, if the PSA can only hold one pallet but the calculated quantity requested might not be exactly met.

Filtering is the technical procedure called during the selection of suitable stock. EWMCP provides additional control options here:

● Generic exception attributes at HU level: This can be used to exclude certain HU’s from picking. There are reports provided which set and re-set the respective attributes using a user status. A use case can be a defrosting or quarantine process that keeps a pallet out of circulation for a few hours.

● Mixed layer pallet filter: This can be used to exclude pallets from the search result which contain incomplete layers (also described as ‘robot stock removal indicator’)

● Manipulate quantity classifications in the storage type search sequence: Use Case: Customer requires that pallets delivered to his warehouse are maximum 1,50 m high. Although EWM’s master data would regard the ordered quantity as ‘large quantity’ (quantity class L and 2m height), the picking should select a case pick area (quantity class C), where 1,50m high pallets are built.

● Pick to Clear:. This strategy is attempting to free up bins in multi-deep storage (set up as bulk storage types). The system will sort according to the maintained removal rule, but further evaluate the number of stored pallets per bin and prefer bins with the smallest number of pallets. In a last sorting step, bins with the smallest total quantity are prioritized.

● Over pick behavior: Removals that have been triggered by a Warehouse Request (Outbound delivery Order) can be set to avoid any over delivery. This logic complements a setting which tries to pick complete HU's, so you can decide if the 'Abort WT' feature will round up or down.

EWMCP uses these features in combination to provide support for the following scenarios:

1. DC to DC Scenario○ (Optional) Abort WT creation (that is, when number. of PAL for full Truck has been reached)○ (Optional) Pick-to-clear○ Change WT quantity based on HU quantities in Bin○ During RF picking: “Pick other Pallet”

2. DC to Customer or Store○ No Abort (that is, need to pick the quantity the customer ordered)○ (Optional) Pick-to-clean (if potential remaining quantities can be picked from non-full pallet area)○ Change WT Quantity based on HU quantities in Bin○ During RF picking: “Pick other Pallet”

3. Multi-deep Bulk to Production Supply Area○ (optional) Abort WT creation, when certain number of Pallet Tasks is reached○ Staging Full-Pallets to Production, through /SCWM/STAGE report○ Create according to largest QTY in the Bin to avoid negative available Quantities.○ Avoid RF message “Pick other pallet” in Multi-deep, that is, 6 or 10 deep bins this is not practical.

4. Multi-deep Bulk Replenishment to Fixed Bin○ (optional) Abort WT creation, when certain number of Pallet Tasks is reached○ Staging Full-Pallets to Production, through /SCWM/STAGE report○ Create according to largest QTY in the Bin to avoid negative available Quantities.○ Avoid raising RF message “Pick other pallet” in Multi-deep, i.e. 6 or 10 deep bins. This is not practical.


Prerequisites

You have performed the Customizing under SAP Extended Warehouse Management, Add-On for Industries→ Consumer Products→ 03 - Outbound→ Stock Removal Strategy.

4.7 Full Pallet Picking Process

The assumption in the picking process is that full pallets can be picked with a shorter notice than mixed pallets.

Besides the activities being carried out in a dedicated storage type with specific behavior and put-away logic, full pallet removal can be triggered after EWM has assigned a suitable door and staging area, and potentially even a bin within the staging area.

EWMCP’s Bulk Picking scenarios in addition allow a fuzzy definition of ‘full pallet’. This is realized by a mixture of packaging specification definition and quantity classification which can be exchanged in certain situations. Select the relevant business process for your products as not all combinations (of Full Pallet/ Bulk Picking/ Multi-Deep Storage/ Batch Management requirements) make sense.


● The system selects the staging area according to the door assignment.● The process starts once the delivery items relevant for full pallet picking are assigned to the wave (for

example, template 1000) for full pallet picking.● The process ends when the picking warehouse tasks are created and released and the staging bay has

been assigned according to the loading sequence of the pallet.● EWMCP performs the tasks in several steps:

○ Wave items for the particular TU are split from the wave containing items for multiple TUs.○ The full pallet picking wave is released.○ The picking warehouse tasks are created in blocked status.○ The staging bay is calculated and assigned, based on loading sequence rules.○ The warehouse tasks are unblocked.

The procedure can consider ‘dummy source’ pallets from double-deep or bulk storage. Once the picker confirms a corresponding task, this preliminary pallet ID is replaced by a real one, and the planned staging bay is taken on to the real pallet. Upon scanning one of the available pallets in a bulk storage type, the system can request the user to scan another pallet if the required quantity on the HU is not the expected one (Picking Quantity Check activation).



4.8 Consolidate Picking to Full Pallets

This process can switch to a full pallet picking process after an analysis of multiple smaller warehouse tasks with identical recipient and outbound TU. If you activate this feature in EWMCP Customizing, the RTS procedure will evaluate if there is an option to perform consolidated picking rather than multiple partial quantities.

ExampleFor the same customer and product, you have three ODO items assigned to the same outbound TU:

● ODO1: 10 CAR● ODO2: 40 CAR● ODO3: 25 CAR

The total demand of 75 CAR will be compared to the Pallet Quantity of example, 60 CAR derived from the Pack.Spec. Considering this, you decide to revise your picking strategy. Instead of performing three individual picks from the pick face, you provide a full pallet from the pallet area and feed only the remainders of 15 CAR to the pick face process.

The system will handle the picking from the bulk part on a consolidated perspective, using an EWMCP-specific RF dialog.


● During Wave Release, the system evaluates whether several wave items of the same product & same consolidation group can be consolidated into a full pallet pick.

● For this consolidated quantity, a new search strategy is determined with the quantity classifier P (Pallet), to pick from the full-pallet area. This might be bulk or single-deep.

● During pick confirmation, all line-items for the individual demands are confirmed in background. The system also performs a movement for the entire source pallet onto the resource and to the final staging bay assigned in the RTS process.

Prerequisites

● You have activated the Full-Pallet Consolidation check Customizing under SAP Extended Warehouse Management, Add-On for Industries - Consumer Products → 03 Outbound → Consolidation Settings.


4.9 Mixed-Layer Pallets Picking

As mentioned above, mixed layer pallets take longer in preparation and present a medium between full pallet picks and item picks. Cartonization can identify Layer Picks to manage special handling activities, which may involve special machinery (robots) and corresponding handover bins where several full pallets will be converted into one or many mixed layer pallets.

You can set up a default value for the Full Pallet filter, which represents a storage bin where the system can expect these Mixed-Layer Pallets to be constructed. This intermediate bin is used in the rough bin determination which in turn is used for the wave creation algorithm. It needs to allow negative quantities, because the picking process from RTS will use it as an unlimited source for Mixed-Layer Pallets.

The process will initially calculate the future mixed-layer pallet as a PSHU originating from the intermediate bin. In the course of picking, this PSHU is replaced by an actual one, and the 'staging result' - overview in the monitor will be updated accordingly. The RTS process will identify these buffered pallets and call them off upon RTS execution. EWMCP uses Warehouse Process Type 2017 to identify this logic.

As a separate process, the negative stock inside the intermediate bin needs to be settled by a suitable replenishment run (that is, feeding the pallet-building facility).

Prerequisites

● You have performed the Customizing under SAP Extended Warehouse Management, Add-On for Industries - Consumer Products → 03 - Outbound → Stock Removal Strategy → Define Default values for Full Pallet Filter.

4.10 Rounding to Available Pack Size

In this scenario, a product can appear in various pack sizes, for example, 6-packs and 8-packs.

The way this is managed is different from the standard EWM idea where one of the variants is regarded as 'to be discontinued'. It is also not intended to deliver exactly the units of measure which was ordered by the customer.

This idea of 'Rounding to Pack Size' is leaving the decision about the Units of Measure for picking undecided until the source quant for picking is identified. If you maintain the corresponding control settings, the pick task will analyze the requested quantity and units of measure. It also ensures that the resulting quantity will not exceed a full pallet quantity as per the packaging specification.

Prerequisites

● Your picking storage type is not set up as bulk storage.



● You have maintained a packaging specification for the pallet quantity.● You have performed the Customizing under SAP Extended Warehouse Management – Consumer

Products→ 03 – Outbound→ WT Rounding up to Full Units.

NoteFor background information about the standard behavior, see knowledge base article 2745415

4.11 Mixed Product Pallet Process

EWMCP comes with a preconfigured process to handle Mixed Pallet picks, which involves a buffering step.

The process starts once the delivery items relevant for mixed pallet picking have been assigned to a wave (for example, template 2000) for pallet building. This wave is released and processed prior to the RTS activities and results in buffer stock which will be called off later during RTS.


● Cartonization is performed within the wave to determine optimized PSHU.● The wave is released, and the picking warehouse tasks are created.● The picking warehouse tasks are confirmed.● The shipping HUs are moved to the high bay (buffering) where they wait for shipping.● The loading sequence is calculated and the HUs are assigned to the staging bay based on the loading

sequence.● An ad-hoc warehouse task is created by RTS for the shipping HU from the high bay to the staging bay.

4.12 Double-Deep/Multi-Deep Rack Scenario

For multi-deep storage, EWMCP comes with a scenario using the bulk storage setting in the respective storage type. Other than the standard procedures, EWMCP evaluates both the total contents of a bin and the way this stock is distributed onto pallets. This logic is implemented in several places such as picking strategy, rounding rules, RF dialogs and production integration. All strategies can handle fuzzy logic when selecting the storage type, bin and pallet requested.

The logic also distinguishes internal requests (created by /SCWM/REPL or /SCWM/STAGE) and external requests (outbound delivery for customers). Customer demands might not accept rounding or multiple partial quantities for fulfillment.

Further characteristics of the scenario are:

● Within a bulk bin, there may be one or two Pallets with non-standard quantities. In general, the pack spec is good enough to distinguish full pallets storage from small quantities.


● Pallets are all the same SKU and batch (if the product is batch managed).● Pick tasks are created with a preliminary HU number. This transparent HU will be replaced based on the

picker's input and automatically propagates its planned destination data to the actual HU.● Warehouse Task confirmation dialog will not display a specific HU for picking. All standard pallets in this bin

are interchangeable, and any HU is accepted. However, for the non-standard pallets, the system will only accept the one with exactly the quantity given in the WT.

4.13 Storage Type Search Sequence Redetermination

In two-step picking, you move a full pallet from a high rack into a deconsolidation center and deconsolidate individual cases from there.

While the pallet is sitting in that deconsolidation work center, you can optimize all upcoming pick tasks by redirecting them to get picked from here. This option is only temporarily available - it will be gone once you decide to put the pallet back into the rack storage.

This function is called during the outbound warehouse task creation at source bin determination, for specific processes such as SLED (Short Life Expiration Date) case picking, and to subsequently update the storage type search sequence.

The change search sequence and stock removal rule function perform checks for the warehouse number, two-step picking flag, warehouse process type, quantity classification and batch selection criteria. It determines a new search sequence that is to pick from the deconsolidation work center prior to picking full pallets from the high rack and subsequently updating the storage type search sequence.

The storage type search sequence redetermination scenario runs as follows:

Storage Type Search Sequence Determination

1. Stock for the outbound delivery (determined using shelf life expiration date) is found in the high rack.



2. The full pallet is picked from the high rack and moved to the Pick and Drop (P&D) area.3. The full pallet is moved from the P&D area to the work center for deconsolidation.4. The full pallet is deconsolidated, and the single case is picked and staged to the shipping bay. The pallet

remains in the deconsolidation work center.5. For all subsequent outbound deliveries, which have the same scenario, picking is performed from the

deconsolidation work center rather than picking further full pallets from the high rack. This is due to the temporary availability of a pallet in the deconsolidation work center.

6. 6. The stock removal rule ensures that based on First Expire, First Out (FEFO), the storage type search is carried out in the following sequence:1. Pick Face2. Deconsolidation Work Center3. High Rack

7. At the end of the shift or at another agreed time, the pallet is moved from the deconsolidation work center to the high rack.

Prerequisites

● You have performed the following Customizing underSAP Extended Warehouse Management, Add-On for Industries - Consumer Products → 03 - Outbound → Define Criteria for Storage Type Search Sequence Redetermination.

4.14 Transportation Unit Loading Completion

This transaction combines several processing steps in one dialog.

It starts with a docked TU and potentially open picking and loading processes. After execution, you have a free door, a TU moved to the checkpoint, and pending activities automatically finished.

It performs a couple of verifications:

● Check if scanned TU is docked to the scanned door.● Check if all HUs assigned to the TU are loaded.● Check if there are any open warehouse tasks for deliveries linked to the TU.

The RF transaction (logical transaction CDSHCP) consists of two screens. After the potential quality checks, the TU is automatically moved from the door to the yard bin, using the standard Post Processing Framework (PPF) action.


Transportation Unit Loading Completion

The other feature provided by this transaction is to check for open loading quantities in the deliveries that are assigned to the TU. So, if you decide to close the TU and the system is still expecting items to be loaded, you have the option to close all processes and declare the delivery complete nonetheless.

This closing will not cause a delivery split. Instead, the existing delivery receives a process code to accept differences without a new delivery attempt for the remaining items.

Delivery Quantity Adjustment

After declaring the TU completion, the system posts Goods Issue for all affected outbound deliveries and move the TU to the outbound checkpoint. The door is released and the staging area gets cleared. As a final step, you only need to check out the TU from the checkpoint to conclude the process.



Prerequisites

● You have maintained the Customizing under Extended Warehouse Management→ SAP Extended Warehouse Management, Add-on for Consumer Products→ 01 – General and Cross and Configure Transportation Unit Loading Completion under Extended Warehouse Management→ SAP Extended Warehouse Management, Add-on for Consumer Products→ 01 – General and Cross.

● You have defined Warehouse Process Types that can stop the process if corresponding open tasks exist under Extended Warehouse Management → SAP Extended Warehouse Management, Add-on for Consumer Products → 01 – General and Cross → Warehouse Process Type to be Checked During Goods Issue.

● You have configured the PPF actions for TU movement and for posting goods issue.● You have defined the ERP interface for Goods Issue under Extended Warehouse Management → Interfaces

→ ERP Integration → Transportation → Define Default Values for IDOC Outbound.


You can use RF screens to perform the following activities:

● TU and door scanning: This screen checks if the scanned TU is docked at the scanned door and if all HUs linked to the TU are loaded with no open picking warehouse tasks for the deliveries linked to the TU.

● Loading completion: This screen can be used to perform TU loading completion and subsequently move the TU from the door to the yard and post the goods issue using standard PPF actions after performing validations.

NoteDuring the execution of the loading completion RF transaction, you can check if there are open loading quantities in the delivery assigned to TU. If such delivery items are found, a new RF screen is displayed with materials and quantities that are to be adjusted. You can set a control flag (automatic deficits acceptance) if you want to proceed automatically or if you require to run loading completion for the second time.

● When you choose the Adjustment button, a pop-up asks you to confirm delivery adjustment and the system checks if the open delivery quantities match the tolerances for the resource.

4.15 Repacking/Kit to Stock with Subcontracting

The repacking process transforms several components into a new product.

The repacking process transforms several components into a new product. This can be

● Turn production sizes of products into marketable units. For instance, a large container of ice cream (unit kilogram) is packed into calibrated boxes of three liters each. The process implies a BOM-based activity (consuming both a box and the ice cream) and the transformation of a kg-based product into a different product (base unit EA) that can be sold. As this is a production-like activity, it is assumed that the resulting product is immediately palletized, so the output will be a number of uniform handling units.


● Combine various items into a sales display, for example, the ‘1€ – display’ for various household items. This would represent an alternative to the standard kitting (kit to stock) process.

The business process starts in ERP with a subcontracting Purchase Order (Item Type L), followed by an inbound delivery. The vendor in this context may be a dummy vendor or a third-party service provider. Anyway, the components are not intended to get shipped to an external site – repacking is executed inside the warehouse’s premises. Furthermore, the process does not rely on a fixed BOM as it creates VAS orders in EWM individually per Purchase Order.

The output is a pallet of the new product and a newly created batch with expiration date characteristic. The expiration date of the new product is derived from the minimum of the used components.

EWMCP provides background features that result in a packaging specification for VAS orders. This Packaging Specification reflects the BOM you have maintained in the individual PO (see SLG1, sub-object /EWMCP/3OUT_REPACK to analyze the background activities upon IBDLV replication).

Prerequisites

● The subcontracting vendor (Business Partner) is carrying the ID Type specified under SAP Extended Warehouse Management, Add-On for Industries – Consumer Products → 03 – Outbound→ Repacking→ Define Configuration for Repacking Transaction.

● You have configured a suitable Delivery Type and Item Type for Inbound Deliveries to be used in kitting under SAP Extended Warehouse Management, Add-On for Industries – Consumer Products→ 03 – Outbound→ Repacking→ Define Configuration for Repacking Transaction. It is intended to use a copy of the standard Delivery Type IDN and Item Type IDLV for this purpose.

● The VAS orders are assigned to a properly configured work center.● Components with suitable quantities and expiration dates are available in the work center.● No parallel repacking as per VAS order, since the new repack transaction cannot be used in parallel for one

VAS order.● The bill of material (BOM)/components corresponding to a product are maintained in the ECC

subcontracting purchase order.● There is a default packaging specification configured for the final product. This packaging specification

defines packaging material and components as below:○ Level type: AUX (components for repacking)○ HU relevance (of assigned elements): 1: Main packaging 3: Components

The BOM for the ingredient components will be compiled at runtime based on the PO.● You have maintained a Unit of Measure considered as a pallet under SAP Extended Warehouse

Management, Add-On for Industries – Consumer Products→ 03 – Outbound → Repacking→ Define Unit of Measure for Pallets.

● All components and the resulting Kit product is batch managed with expiration dates.




The process is designed as follows:

1. You have created a subcontracting PO with a specific vendor (that is, the service provider for packing). In the PO, specify a Bill of Materials for the components to be consumed.

2. You have created an Inbound Delivery which is replicated to EWM. When an inbound delivery for the specific vendor reaches EWM, two background steps are triggered using qRFC. They result in a VAS order relating to the BOM you created in the Purchase Order.

3. You have assigned a work center to the VAS Order.4. You have selected suitable HU’s of components and move them to the corresponding work center.5. You have physically executed the pallet building and confirmed the process by pressing Save in

transaction /EWMCP/RP_REPACK.6. The system executes a goods movement for the used components into subcontracting stock and

synchronizes the stock with ECC with Movement Type 541.7. The system determines a batch for the resulting HU’s of final product. The batch creation function checks

if an existing batch from the batch master can be used with a specific format. If no batch is found, a new batch number is generated according to a specific format.

8. The components are consumed again from subcontracting, and the final HU is received using an Inbound Delivery for the subcontracting PO. Be aware that the shelf life of the finished product is derived from the most critical component and needs to fulfill the requirements from the subcontracting PO.

Repack Transaction

The transaction displays in its lower section all components staged for the production process. The status is set to green if the quantity sitting in the work center suffices to produce the intended number of pallets. You can refresh the calculation using the ‘Undo/Refresh’ button. The two buttons ‘Add HU’ and ‘Delete HU’ perform a selection within the HUs staged in the work center. These will be the pallets and batches from which the system consumes the stock.

The process is executed like this:

1. On the main repack screen, enter a VAS order number.2. You perform all repack activities on this screen (add/delete/print).


3. After entering the actually packed quantities, the system displays an HU assignment.4. You can create and maintain an HU assignment to a component product.5. After successful HU assignment (all components in status ok/green), you can save your entries. This

triggers the goods issue posting for subcontracting components, batch creation, and inbound delivery update, handling unit creation, inbound delivery packing and goods receipt posting.

Batch creation in the kitting process is using a pattern YDDDSL999 with the following:

● Y = Last digit of the year from the system date.● DDD = Date sequence number derived from the system date.● S = Shift code, starting with A (up to Z): Check if the generated batch number exists with a different BBD,

otherwise create a new batch number (generate next shift code from A up to Z).● L = Line from packing work center (is determined in the packing transaction, last digit from the work center

of the VAS order).● 999 Manufactory Code from Customizing under SAP Extended Warehouse Management, Add-On for

Industries – Consumer Products → 01 – General and Cross- → Batch Numbering → Define Manufactory Codes.

NoteYou must be aware that each subcontracting PO for the specified vendor causes the creation of one Packaging Specification and a corresponding condition record. You may want to clean up the condition records after some time.

4.16 Opportunistic Cross-Docking in Repacking Scenario

'Opportunistic Cross Docking' supplements the kitting scenario from above by adding demand information to the entire process.

Basically, it turns it to a kit-to-order process, using a subcontracting order. To leverage this scenario, ECC needs to provide a reference to a sales order both in the subcontracting PO/inbound delivery and the outbound delivery.

The sales order reference between inbound and outbound deliveries enable opportunistic cross-docking (inbound) for inbound and outbound deliveries for a subcontracting repack order.

Prerequisites

● You have performed the standard configuration related to delivery document references for sales orders.● The sales order reference is added to the standard inbound delivery interface extension.● You have performed the following Customizing under SAP Extended Warehouse Management, Add-On

Consumer Products → 02 - Inbound → Define Warehouse Process Type Relevance for Opport. Cross-Docking Inbound.




● The sales order reference function is executed during the inbound delivery replication. It provides a reference field for the EGR and goods receipt notification (GRN) inbound delivery document items.

● Opportunistic cross-docking starting from inbound deliveries limits the cross docking to outbound delivery items with identical sales order reference as the corresponding inbound delivery.

● During opportunistic cross-docking, the warehouse process type defined for a warehouse is used to identify the subcontracting process. Based on the selection of inbound delivery items through the sales order reference filters all outbound delivery items without identical sales order reference as an inbound delivery item.

NoteThe process uses the standard BAdIs for opportunistic cross Docking:

● /EWMCP/EI_3OUT_CD_OPP_INBOUND● /EWMCP/EI_2INB_CD_OPP_OUTBOUND

4.17 Repalletization

This section describes the repalletization process.

Customers may require specific packaging materials for their ordered goods. Even if a complete original pallet is to be shipped, it might be sitting on the wrong sort of pallet (for example, whitewood, but instead the customer prefers CHEP). This results in a full pallet pick wave which however requires a repalletization VAS.


With this EWMCP feature, you can exchange the pallet, thus keeping all stock information of the HU - including its ID - intact. It is realized as an additional tab in the desktop transaction /SCWM/VASEXEC:

Work Center with tab for Repalletization

Prerequsites

● You have performed the standard configuration for VAS orders.● A work center has been assigned to derive the correct destination area for repacking.● Warehouse orders and tasks are created with a destination bin as the work center assigned to VAS.


The repalletization process runs as follows:

1. When the outbound delivery is distributed to EWM, a VAS order is created, based on the ship-to criteria.2. On the day of shipping, the VAS orders for repalletization can be evaluated in the monitor report for TUs

that are leaving that day. A work-center must be assigned on which the activity can be executed.3. You can release the full pallet picking wave. HUs to be repalletized can also be included in the special

activity pick wave from another wave template (for example, 3000).4. The pallets with VAS activities for repalletization are released a few hours earlier than the other waves.5. When the VAS orders wave is released, the door has already been determined with the wave release of

standard TUs and TUs with similar VAS orders.6. The relevant HUs for repalletizing can then be moved to the work-station through layout-oriented routing.7. The repalletizing activity takes place and the VAS order is completed (Button 'Execute' on Repalletization

tab).



8. The user declares the Work Center activities finished, which triggers the creation of a follow-on task9. The HU is finally moved to the staging area.

4.18 Shipment Changes by IDoc

Using EWMCP, you have the option to update planned shipments (Inbound and outbound) using the regular SHPMNT05 IDoc, This could be relevant if you need to see a TU as an early object in EWM, but the contained deliveries may not be clear yet. You can update the TU information in EWM now as long as the TU has not reached the yard.

The changes can pertain to the set of deliveries assigned to the TU, or to the sequence in which the deliveries shall be loaded.

Upon receiving a SHPMNT IDoc, the EWMCP solution will delete the previous TU and create a new object while keeping the external number. In this procedure, you can evaluate either the sequence of the incoming E1EDL20 segments or a deliver header field (LIKP-ANZPK) and move it into a specific field /EWMCP/LOAD_SEQ on the ODO header.

Prerequisites

● You have set up the master data and performed the standard configuration related to the shipment IDOC processing.

● The affected shipment is not yet in status 'Arrival at Checkpoint' (CHKI) .

4.19 Inspection (Handling Unit Check)

EWMCP provides an additional RF dialog to verify the contents of a particular Ship-HU.

This process can be applied to a single HU staged for an ODO and works without Physical Inventory documents, while the HU is placed in the outbound staging area.

The process can be split between a processor and a supervisor role who have different authorizations and screen controls. The intention is to follow a four-eye principle, especially if one of the parties is a third-party service provider. However, checking itself is an ad-hoc exercise based on the decision of the floor staff.

A processor will be prompted to identify a suitable pallet and continue to scan products and quantities he finds on it. For a homogenous pallet, a Ti/Hi factor is verified. A Cancel button (F3) is provided to interrupt the counting process and rollback all results in case the pallet needs to be shipped before counting is completed.

If after closing the count, the resulting differences exceed the limits configured in his resource master, the pallet will receive a status which makes it relevant for an additional checking by a supervisor. The status can be displayed in the shipping cockpit. With this status set, the pallet is blocked from loading activities.


The supervisor has additional authorizations for differences handling. He can also close deliveries so that no re-picking of missing items can start.

Supervisor View - List of Contents for a Specific HU

Supervisor View - Declare Actual Quantity and Damaged Quantity at the Same Time.

NoteCounted quantities include the damaged quantity (in the screenshot example: Theoretical Stock = 10 PC, Counted = 9 PC, therefore Damaged = 1 PC).

Differences are posted using the standard exception code DIFW, applied to a circular dummy posting from/to the same HU.

The system internally determines these discrepancy types:

● D (Damaged): The stock is posted from the HU to a dedicated storage bin (also physically). Picking is canceled for the concerned quantity. A re-start of the picking can be triggered manually.

● S (Shortage):Tthe missing stock is logically posted from the HU to a dedicated storage bin, using the exception code provided in the configuration table. There is also an option to trigger a goods movement posting in ERP, providing the reason code given in Customizing. The supervisor can decide to accept the short pick and release the HU for loading, thus reducing the target quantity of the outbound delivery. Also in Loading Completion dialog, the user can declare all picking attempts finished and provide a final delivery with a reduced quantity.

● X (Extra): The stock is logically sourced from a specified storage bin onto the HU. If the product is batch managed, the system assumes the first batch encountered in the outbound delivery item. The delivery item quantity is increased using a process code. Extra quantities might exceed the tolerance limits defined in the outbound delivery. If this presents an issue to your delivery process, you can disallow any overages during HU check in the corresponding Customizing settings (disable flag ‘AdjOverage’).



Prerequisites

● You have executed the Customizing under SAP Extended Warehouse Management, Add-On for Consumer Products → 03 – Outbound → Radio Frequency Counting.

● You have configured a suitable exception code (See note 2469810 for details).● You are not handling different batches within the HU.● You have not packed different Units of measure for the same product into the HU.● You have declared the corresponding resource as processor or supervisor in transaction /EWMCP/

ADJ_PRM.

NoteOnly the discrepancy types D, S, and X are used in this context. The other values E, M, B and U belong to the 'Returns Receiving' Process.

4.20 Quality Checks During Automatic Staging & Loading

When the TU loading and the staging warehouse tasks are processed via a system-guided RF transaction (logical Transaction CDWKGQ), the loading loading warehouse tasks are created and confirmed automatically after the staging warehouse task has been confirmed.

You may want to perform checks for the TU also in this system-guided process. When the checks are successfully passed, you can continue with the standard logic for the system-guided RF transaction and display the screen to process a staging warehouse task.

You can use this process to enhance the standard system-guided RF transaction to check whether a TU is docked to a door and to perform additional quality-related checks.

Prerequisites

● You have performed the following Customizing activities:○ SAP Extended Warehouse Management, Add-On for Consumer Products → 02 - Inbound → Activate

Quality Control Validation for the RF System-Guided Transaction.○ SAP Extended Warehouse Management, Add-On for Consumer Products → 01 -General and Cross →

Define Quality Check Characteristics .● The TU loading process is done via an RF transaction.● You have configured the staging and loading process.● The staging warehouse tasks are selected and confirmed via system-guided RF transaction.● The loading warehouse tasks are created and confirmed automatically after the staging warehouse tasks

are confirmed.




You can use this process to perform additional checks during the system guided selection at warehouse and document type level. When the operator requests a new staging warehouse task, the following activities are performed:

● The system retrieves warehouse orders.● The system retrieves the warehouse tasks corresponding to each warehouse order.● Based on the configuration settings for a warehouse and a document type, the staging warehouse tasks

warehouse orders are filtered to perform additional checks, that is, whether the TU is docked to a door and whether additional quality-related checks are required.

● When all the TUs from the warehouse orders have been checked, the warehouse task screen is displayed using standard RF processing.

4.21 Cartonization

Cartonization results in the creation of planned shipping HUs (PSHUs) that can be used as templates for creating real shipping HUs during picking or packing.

Cartonization planning provides you with information about volume, weight, and number of shipping HUs at an early point in time during the outbound process.

The Cartonization planning function improves the creation of PSHUs based on additional information from product master data and outbound delivery orders and subsequently adjusts cartonization algorithm to consider the following restrictions:

● For some customers, only one article is permitted on a wooden pallet and therefore no mixed pallet shall be planned for the mixed pallet picking.

● Some customers may have specific packaging specifications, which means that standard packaging specifications must be overwritten.

● You may need to add pallet separators as an additional auxiliary product between different products if the HU packaging specification contains packing products at the product level.

● You may need to add slip-sheets as an additional auxiliary product for a product that has a packaging specification with an auxiliary product maintained.

● You may need to consolidate multiple line-items with less than a pallet quantity to a combined pallet quantity and pick from full pallet area, instead of pick face for case quantities.



Cartonization in Outbound

Prerequisites

● You have set up the master data related to cartonization.● You have performed the Customizing under Extended Warehouse Management → SAP Extended Warehouse

Management, Add-on for Consumer Products → 01 - General and Cross → Maintain Warehouse specific settings.

● You have defined an algorithm profile for a warehouse to be used for the custom cartonization planning.


This function is executed during the cartonization planning based on profiles defined for specific customers. It comprises the following:

● Full pallet consolidation algorithm: This algorithm groups outbound delivery order items by product, batch selection criteria, and consolidation group and ship-to party. Then, based on the pallet quantity, the system groups items into PSHUs. The total quantity of products in items packed into one PSHU is equal to the full pallet quantity. Wave items can be further split into a ‘Full pallet’ part and a ‘Less than full pallet’ if the corresponding flag is maintained to allow the outbound delivery item to split.

● Mixed pallet algorithm: This algorithm determines packaging specifications for a product of delivery items to be packed into PSHUs. The system first checks if a packaging specification has an auxiliary product and if an auxiliary product exists. The function takes the volume of auxiliary products into total volume calculation, keeping the existing standard logic from cartonization algorithm for capacity calculation.


4.22 Printer Selection for Handling Unit Label Printing

With this feature, you can direct an HU label print to any suitable printer.

The printer name may be scanned from a barcode label or entered manually (supported by a value list).

Prerequistes

● You have activated the printing feature in Customizing under SAP Extended Warehouse Management, Add-On for Consumer Products → 01 General and Cross → Maintain Warehouse Specific Settings , folder "Scan Printer in RF Picking' (alternative view /EWMCP/V_PRNT in SM 31.

● You have maintained the standard condition technique for print form and printer determination procedures.



4.23 Value Added Services Determination

The general feature of Value-Added Services forms part of the standard functions set of EWM. However, EWCMP is providing a way to control the VAS determination based on the contents of any field given in the Outbound Delivery Order. You can specify the technical field name together with an expected content of it and assign a Value-Added Service which you intend to be performed by the system.

This additional selection logic is triggered as soon as an entry for your delivery item type is found in the underlying control table.

NoteTechnically, the solution will not override the standard VAS determination using Pack. Spec. with dedicated Level Types. Instead, it works as a subsequent filter to remove all VAS items from a set of generously determined VAS activities if these do not pass the EWMCP - specific conditions. So, the solution needs to be complemented by a VAS Order creation logic which will find the totality of all possible VAS activities in the first place.

The procedure creates a log (transaction slg1) with object /EWMCP/ and sub-object EX_VAS_CRT_ACTIVTS

Another feature of the EWMCP Add-on is related to the way the VAS Order logic influences the Process-Oriented Storage Control. In standard, finalizing a work step will trigger a movement task towards the executing bin for the following activity. This is however not required if you intend to perform several activities in the same Work Center. To avoid these intra-workstation movements, you can configure a list of process steps which trigger an additional check. A movement task will only be created if current and next bin belong to different Work Centers.

Prerequisites

● You have configured a standard VAS processing scenario including Process-Oriented Storage Control and VAS determination using a suitable Pack. Spec.

● You have set up the master data for Work Centers and their bins.● You have configured the EWM-Specific VAS controls in Customizing activities underSAP Extended

Warehouse Management, Add-On for Consumer Products → 03 Outbound → Value Added Services .

4.24 Operative Loading by Door

In this scenario, you expect a TU from a freight forwarder who will basically accept any HU you load into it. The door to dock this TU to is not decided upfront, and so the Ship-HU's get staged independent of the final docking door.

When the TU arrives, it is directed to any door and the task is now to have all staged pallets loaded onto that truck. To handle this, the user calls the EWMCP specific RF transaction and scans the staged HU's. These HU's get loaded into the TU and the corresponding Outbound Delivery Order is assigned to the TU.


NoteThere is a BAdI /EWMCP/EX_3OUT_RF_LOADING available to implement custom validations for matching HU and TU. You may, for example, throw an error if carrier data on ODO and TU contradicts.

Prerequisites

● You have defined an outbound process which includes the steps Staging and Loading.● The loading process will always be executed via complex loading: a storage process is assigned to the

Handling Unit to be loaded with an active Loading step.● The ODOs are not assigned to a TU in advance.

● You have maintained the name of the relevant loading step in Extended Warehouse Management SAP Extended Warehouse Management, Add-on for Consumer Products 03 - Outbound Set Loading Step for Operative Loading by Door .

● You have mounted the RF transaction CDHUSI into your RF menu path.


Execute a delivery-based outbound process up to the point where staging is completed. The next step for the staged HU's would be a loading of the Warehouse Process Type which you have set up in EWMCP Customizing for Operative Loading by Door.

On the other hand, you have prepared an empty outbound TU. You activate the TU and dock it to any available outbound door.

To bring HU and TU together, you call the logical transaction CDSHDO and scan the respective HU.

With ENTER, you get to confirm the door.



After this, the HU and its ODO are assigned to the TU and the HU receives status 'loaded'.


5 Extended Warehouse Management Internal Functions

This chapter provides information on the internal functions of EWMCP.

5.1 Pallet Mover

The idea of Pallet Mover is a resource that is occupied with transferring a larger number of Handling Units inside the warehouse.

This can be a tractor dragging a chain of roll cages, or a forklift bearing several (stacked) pallets at the same time. All Handling Units need to have an open warehouse task attached so their destination is known.

The EWMCP solution is controlled by the capability of resource types. This can limit the number of HUs that can be transported at one time, and the number of destinations addressed by the total set of Handling Units.

Furthermore, you can allow or disallow the operator to mass confirm his tasks.

A user can choose three different ways to pick up HUs:

● Selection by Bin and HU: The user is prompted to identify certain pallets after declaring a source bin (for example, a receiving area). The HUs get counted up to the limit, or the user actively completes the pick-up.

● Selection by Bin: The entire HU stock on the bin can be picked up at once (for example, the entire P&D zone will be cleared in one go).

● Semi-Guided by Queue: The system will provide a source bin and ask for HUs to be scanned.

Regarding the confirmation, the user can confirm all tasks at once (if this is allowed by customizing) or scan each HU while dropping it.

Prerequisites

● You have maintained the following Customizing activity: SAP Extended Warehouse Management, Add-On for Industries - Consumer Products → 03 Outbound → Define Maximum Resource Capacity.

● You have mounted the logical transactions CDPMBH, CDPMBI, and CDPMSQ into your RF menu.


Extended Warehouse Management Internal Functions

5.2 Plant-to-Plant Stock Postings

You can use this process when two different plants are assigned to one physical warehouse.

For example, a regional plant supplies a broader market and a local production plant replenishes a local distribution center. In this scenario, you may be required to make a plant-to-plant posting but there is no physical movement associated with this posting as the pallet remains in the same bin.

The process is triggered by a stock transfer order which is created in ECC to replenish the local distribution center with stock from the regional distribution center. As both ECC plants are managed in the same warehouse, only a plant-to-plant posting may be required. The stock transfer order is transferred into an outbound delivery in ECC. The outbound delivery is distributed to EWM where a posting change is created and confirmed automatically. The posting change is used to change the owner as well as the party entitled-to-dispose. Other attributes (e.g. product, batch, HU, HU bin, etc.) are not to be changed.

Plant-to-Plant Posting Without Physical Movement

Prerequistes

● You have performed the Customizing activities under SAP Extended Warehouse Management, Add-On for Industries - Consumer Products → 04 - Internal → Plant-to-Plant Stock Posting.

● You have performed the Customizing activities under SAP Extended Warehouse Management, Add-On for Industries - Consumer Products → 04 - Internal → Define No Movement During Warehouse Task Creation.

● The information regarding the destination owner/party entitled to dispose is determined based on the destination plant which is transferred from ECC.

Application Help for SAP Extended Warehouse Management Add-On for Consumer ProductsExtended Warehouse Management Internal Functions C O N F I D E N T I A L 83


This function is executed with a one-step transfer when the outbound delivery from a stock transfer order is replicated to EWM as a posting change and performs the following steps:

1. The system determines the delivery process indicator for a delivery type and item category definition, based on the Customizing settings.

2. It determines the destination data for the posting change during the inbound processing of the posting change request.

3. The destination owner/party entitled to dispose is determined based on the destination plant which is transferred from ECC.

4. The system fills all the stock and product-related information to perform a posting change in EWM instead of using a two-step procedure with an outbound/inbound delivery where a physical movement is involved.

5. The destination bin is made equal to the source bin because the HU is not physically moved. The determination of data is made flexible during the warehouse task creation for the posting change when the bin adjustment is set active for a warehouse and a warehouse process type.

6. HU information can be added to the ECC delivery for a posting change for a warehouse number document type/item type and warehouse process type.

5.3 Short Shelf Life - Stock Administration

Managing shelf life expiration dates may require special treatments for stock which comes close to expiration. For instance, you might want to display a separate stock figure in ERP, whereby you decide to run a push allocation into certain stores of your distribution chain.

As ERP usually has no insight into the expiration date structure of the stock, you can trigger stock postings based on the remaining life span of your stock. If you link your selected stock type to a specific storage location, you can trigger an implicit transfer posting in ECC.

Transaction /EWMCP/BLOCK_STK can be started with two variants, 'expiry date' and 'short shelf life blocking'. The tool can change the present stock type of selected quantities for example, from 'Unrestricted' to 'Short Shelf Life Stock'. The concept of stock being 'short' is operationalized via a BAdI which implements a custom decision model based on for example, an additional batch characteristic denoting the relevant time span before expiration.

You can start /EWMCP/BLOCK_STK as a selection of several storage types. However, the background activities and potential stock changes are controlled by Customizing. For this reason, the system highlights entries within the result set, which can be subject to a change posting as 'relevant'. Be aware that actual postings can only be executed if the stock is available at runtime, that is, at the time of execution, there are no open tasks or inventory processes attached to the respective quantity.

The report is intended to run in the background on a scheduled basis. You can, however, run it in foreground mode (manual selection) to verify that the selected items meet your expectations.

NoteYou can also use the monitor /SCWM/MON to manage expiration date stock.



Prerequistes

● You have performed the following Customizing activity: SAP Extended Warehouse Management, Add-On for Industries - Consumer Products → 04- Internal → Define Shelf-Life Blocking.

● You have performed the standard ECC configuration to trigger storage location changes for stock type change.

● Short shelf life date is calculated based on the best before date (stock / batch characteristics), which is populated for the respective products and batches.

● No multiple pallets in a bin or mixed storage for stock types allowed in the respective storage type.

5.4 Quarantine

Pallets may be put in Quarantine Status for several reasons, for example, waiting for customs clearance or acclimatization/defrosting.

The definition of ‘Quarantine’ for this EWMCP feature goes like this:

● The status should be applied to an entire pallet for a predefined number of hours.● The status automatically starts after HU receiving.● Quarantine (as opposed to blocked stock) is not communicated to ECC.● Stock from quarantined pallets is unavailable for picking.● Apart from that, quarantined Pallets are not restricted in movements or changes inside the warehouse

number.● The respective HU's may be carrying mixed materials and batches. If any one of the items calls for

quarantine at the time of receiving, the entire HU is relevant. The overall quarantine duration will be the maximum of all relevant products.

● After the predefined time span, the quarantine status is automatically removed.● Pallets may have multiple user status at the same time; quarantine being one of them.

Prerequisites

● You have enabled your Warehouse Number under SAP Extended Warehouse Management, Add-On for Industries – Consumer Products → 01 General and Cross → Maintain Warehouse Specific Settings.

● You have activated the quarantine logic for your Warehouse under SAP Extended Warehouse Management, Add-On for Industries – Consumer Products → 04 Internal → Quarantine functionality → Activate Quarantine for Warehouse Number.

● You have defined the corresponding user status as a status without status number under Cross-Process Settings → Delivery – Warehouse Request → Status Management → Define Status Schema for User Status.

● You have declared the user status under SAP Extended Warehouse Management, Add-On for Industries – Consumer Products → 04 Internal → Quarantine functionality → Define Quarantine Status.

● You have assigned your user status profile on the packaging material type for your relevant pallets under Cross-Process Settings → Handling Units → Basics → Define Packaging Material Types.


● You have maintained a quarantine duration for your product in the material master MM02.● You have scheduled a background job of program /EWMCP/4INT_USER_STATUS_UPD to remove the

quarantine status at the given time.

NotePlease bear in mind that quarantined pallets show as available stock in the monitor stock overview. The quarantine status of an HU is used as a filter in the picking strategy, but it is no stock attribute.

NoteThe Quarantine concept is also integrated into the scenario 'Receipt from Production Site'.


A quarantine requirement can be declared per product using standard master data. The data can be maintained in ECC maintenance transaction MM02 and will be synchronized with EWM (/SAPAPO/MATIO-QQTIME, see also F1 help on the field).

To execute the process, you can build a new pallet, for example, by using the packing feature of an inbound delivery, and trigger a Goods Receipt posting. The technical feature which triggers a quarantine status analysis is integrated into the Goods Receipt interface to ECC (implementation of BAdI /EWMCP/EIS_4INT_CORE_GM_UPDATE).

Once a pallet goes into quarantine, EWM sets the predefined user status on the HU header. A log is provided with log object/EWMCP/, sub-object/EWMCP/4INT_HUST_UPD.

As the user status is a standard concept, it will be visible in all standard dialogs such as the EWM monitor. In addition, EWMCP populates a new field on HU header level with the timestamp for the quarantine release.

A quarantined pallet will be excluded from the list of potential source HUs upon picking, if a corresponding picking strategy is enabled.



The quarantine status will be terminated by the report /EWMCP/4INT_USER_STATUS_UPD which is intended to run frequently in the background, for example, every five minutes. It writes a log to document its activities. Alternatively, you will find this report as transaction EWMCP/HU_QRNT_RESET in the Easy Access Menu.


6 Extended Warehouse Management Production Integration

This section contains two EWMCP-specific receiving scenarios from a connected production site. They complement the general standard scenarios for Production Supply, Consumption for Production, and GR/GR Reversal from Production.

6.1 Direct Loading

This scenario is checking homogenous full pallets of finished goods arriving from production for corresponding requirements on the outbound side.

The 'Direct Loading' scenario is checking homogenous full pallets of finished goods that have been received from production for corresponding requirements on the outbound side. This requirement may either be a pending customer delivery, or a dummy outbound delivery used to absorb any production output and immediately direct it to a commuting truck.

Both sorts of TU's are identified by an ODO for that particular product, already assigned to the TU. To designate that the TU is intended for Direct Loading, the ODO needs to show a special item type which is maintained in a control table.

It is recommended to have a dummy quantity of 1 on that special delivery so that all subsequent loading activities will result in a systematic over-delivery for that ODO.

In case of a concurring demand for Direct Loading and actual Customer demand (ODO with reference), the customer demand is automatically prioritized.

NoteThere is a reworked version of this transaction available called 'Direct Loading simple' CDLPSI which offers additional BAdIs (Enhancement Spot /EWMCP/ES_3OUT_LOAD_CHANGE) and a simplified screen flow.

In the default setup of EWMCP, both transactions are mounted under 'Receiving HU by Manufacturing Order' in the RFUI menu.

Please check the options in Customizing under SAP Extended Warehouse Management, Add-On for Industries - Consumer Products → 03- Outbound → Radio Frequency Loading HU into TU Simple.

Prerequisites

● You have configured the settings for goods receipt from production via work center.● You have activated Direct Loading under SAP Extended Warehouse Management, Add-On for Industries –

Consumer Products → 02- Inbound → Activate Direct Loading.


Extended Warehouse Management Production Integration

● You have specified the relevant outbound item types for shuttle deliveries in SAP Extended Warehouse Management, Add-On for Industries – Consumer Products → 03- Outbound → Item Types Relevant for Shuttle Deliveries.

● You have defined a TU (shuttle truck) and docked it to an outbound door.● You have assigned an outbound delivery order using the respective product and item type to the TU.


The process runs as follows:

● At the time of receiving for production order, the user will introduce a new pallet number and batch.● While creating the put-away task, the system checks if EWMCP direct loading is activated.

● The user is prompted for a list of potential TU's that are active and ready to take the pallet.

● In case of multiple choices, the user can select the TU from a list and is then guided to the corresponding door. Confirming the door will register the HU as loaded.

● If no suitable TU can be found, the user can decide to put the pallet into a buffer. The buffer bin is derived from the putaway control indicator of the product. Later, the user can move the pallet either to storage or continue Direct Loading.

● Scanning a HU either in buffer or in the rack via the Direct Loading transaction will drive the process on until loading on a TU is confirmed. This option of starting with a previously parked HU is similar to the

Application Help for SAP Extended Warehouse Management Add-On for Consumer ProductsExtended Warehouse Management Production Integration C O N F I D E N T I A L 89

'Shuttle Service' process, but is based on different prerequisites regarding delivery type and TU preparation.

6.2 Shuttle Service

The idea of the Shuttle Service process relates to regular traffic between a manufacturing unit and one or more related warehouses.

It is close to the ‘Direct Loading’ process, but not dependent on a receipt from production. Also, there is a BAdI driving the decision whether a HU should be shuttled and to where it shall go.

These are the features:

● There is a new field in HU header that is supposed to hold the receiving Business Partner. A BAdI is available to determine the required data in custom coding. You may start a test scenario by manually setting the recipient for a HU in monitor method /SCWM/HUHDR-/EWMCP/STPRT(Assign Business Partner).

● There also is a new field in the TU header which can hold a set of addressed business partners for a TU ('Destination'). The Destination is additional master data in the EWMCP context. A Destination is manually assigned to an outbound TU using the desktop dialog /SCWM/TU.

● EWMCP provides a feature to create/extend outbound deliveries on a TU. The delivery type can be configured in standard EWM/ ECC to trigger a Stock Transfer Order generation in the connected ECC system and immediately include the delivery into the document flow.

The process starts by scanning an unassigned pallet that already carries a designated recipient in its header data. As a goods issue is eventually posted, the HU should sit in a storage type that allows a direct goods issue posting.

The system looks for all active and docked TUs whose destination matches the recipient of the HU. The user can select a TU to load onto, or alternatively decide to move the pallet to any other destination bin. Customizing activities provides a setting for the corresponding movement type in this situation.

One advantage of this scenario is that the TU does not need to have any delivery assigned to it for preparation; the delivery is generated or updated by the EWMCP solution. By standard configuration, this specific delivery type can be set up to drive a Stock Transfer Order being created on the ECC side along with the outbound delivery replication.

There are several BAdIs available within the EWMCP code, for example, to fill the recipient field on the HU and to influence the sorting of TUs in the RF dialog. The BAdIs are listed under SAP Extended Warehouse Management, Add-On for Industries – Consumer Products → 03 – Outbound → Radio Frequency Loading HU into TU simple.

Prerequisites

● You have set up a new outbound delivery type in EWM with a packing item that is relevant for loading, but not relevant for picking.

● You have configured the ECC interfacing for the new delivery type.



● You have configured the delivery item category determination on ECC side for usage ‘PACE’.● You have configured the process for Stock Transfer Order and Delivery handling between the

corresponding Business Partners (in ECC: Sites).● You have maintained potential TU destinations in transactions /EWMCP/DEST and /EWMCP/DEST_SHTO.● You have set up a logic to determine a recipient for a HU, for example, as a PPF action upon Goods Receipt.● You have specified the relevant outbound item types for deliveries in SAP Extended Warehouse

Management, Add-On for Industries - Consumer Products → 03- Outbound → Item Types Relevant for Shuttle Deliveries

● You have configured the relevant delivery type, item type and warehouse process type in Customizing under SAP Extended Warehouse Management, Add-On for Industries – Consumer Products → 03 – Outbound → Radio Frequency Loading HU into TU simple → Define 'Loading HU into TU' settings.


You start with an existing HU and assign a recipient to it. As mentioned, this can be done via custom coding or using the monitor method 'Assign Business Partner'

The Business Partner should be listed in at least one Destination defined in transaction/EWMCP/DEST_SHTO .


Also, you must provide an active TU with a suitable destination assigned to it and dock it to a door.

The RF dialog transaction CDSHHU (Loading HU into TU) starts by scanning a Handling Unit. The HU should be placed in a Storage Type that allows goods issue posting.



You can execute the loading process now by pressing Enter. Also, you can change the defaulted TU using F2 where you can select suitable TUs from a list by entering/scanning their door number into the selection field.

The system displays the TU number, its destination and, in the column on the right, the number of HU's that have already been loaded. The button F3 is an alternative to the Enter key to perform a selection within the list.

Once you confirm the door, EWMCP creates or extend an existing outbound delivery, assign the HU to it, assign it to the TU, and register the loading status both on HU and TU (if necessary).

You may decide to finally dispatch the TU using RF transaction 'Loading Completion'. HU information will get updated in ECC upon Goods Issue posting.

To complete the process on ECC side, you might want to set up the message SPED according to note 1119073.

NoteThere are several BAdIs available under SAP Extended Warehouse Management, Add-On for Industries - Consumer Products → 03 - Outbound → Radio Frequency Loading HU into TU Simple (Enhancement Spot /EWMCP/ES_3OUT_LOAD_CHANGE). Via these BAdIs, you can determine a suitable recipient for a HU, and control the way the system creates/ appends the Outbound Deliveries in this Shuttle Service context.

6.3 Control Parameter for the Communication of Goods Receipt

When products are received in the warehouse, inbound deliveries are created in ECC and distributed to EWM.

Full and partial goods receipts, goods receipt cancellation and correction for inbound deliveries in EWM are sent back to ECC. The goods receipt mode determines when the changes are sent to ECC.




In the standard solution, EWM goods receipt mode is customized at the business system level (ECC). This means to standardized ECC, one of the following three options can be used:

● ‘Space’ – Immediately send goods receipt postings and partial goods receipt to ECC● ‘1’ – Only send full goods receipt at the end of the put-away process● ‘2’ – Send full goods receipt when goods receipt has been posted for all items

This feature facilitates control per document type in addition.

The function is executed during the process control parameters determination. Sending of the standard PPF action /SCWM/SPC_MSG_SEND is based on the goods receipt mode.

The following steps are performed:

1. The system determines the document types.2. It determines the goods receipt mode defined for the document type.3. It determines the process control parameters for the communication of goods receipt through standard

PPF actions.

Prerequisites

● You have performed the Customizing activities under SAP Extended Warehouse Management, Add-On for Industries – Consumer Products → 05 – Production Integration.

● You must use standard PPF action /SCWM/SPC_MSG_SEND.● ECC integration has been set up.



7 Simple UI

7.1 Simple UI Basic Concept

EWMCP provides a set of Web Dynpro applications as a starting point for your own developments, which include, in addition to the run-capable examples, reusable service provider classes and assistance classes for your own developments.

Each Web Dynpro component uses an assistance class for methods and functions such as CSS handling and definition of constants. Technically, there is one common assistance superclass for all Simple UIs and inheriting individual classes per Web Dynpro.

To access business data from EWM, the EWMCP package also contains a service class as superclass for all Simple UIs and inheriting special ones per Simple UI. The service classes contain methods for data access to EWM business objects.

7.2 Starting the Simple UI

As a prerequisite, you need to follow the procedure to establish the Internet Communication Framework in your system. Once this is enabled, you can add the applications to your user menu.

To do so, on the SAP Easy Access screen, Create a favorite using Add Other Objects

Application Help for SAP Extended Warehouse Management Add-On for Consumer ProductsSimple UI C O N F I D E N T I A L 95

https://help.sap.com/viewer/fc79a39b30fe4d9aa983bad6787ab9ad/7.latest/en-US

https://help.sap.com/viewer/6da114706c4b1014bfedc1de475963c2/7.01.21/en-US/48d40aca1904154ee10000000a421937.html

Select ‘Web Dynpro Application’ in the popup:

You will find the Web Dynpros as objects starting with ‘/EWMCP/WDC_’.

7.3 Customizing and Master Data

Features such as the one-click HU creation or the exception codes that are implicitly triggered by difference confirmations can be controlled using the nodes below this customizing path:

SAP – Implementation Guide Extended Warehouse Management SAP Extended Warehouse Management, Add-on for Consumer Products 01 General and Cross Simple UI

You must also verify the standard settings for your workstation, especially the master data transaction /SCWM/TWORKST where the origin bin is maintained for the one-click HU creation.

Unlike the standard execution transactions /SCWM/DCONS, /SCWM/PACK, /SCWM/VASEXEC, the Simple UI does not check for any particular transaction type of the work center screen layout; which means, the Simple UI can be called up for any given work center. However, there will be checks for a specific context once a HU is scanned for further processing.


Simple UI

7.4 Picking

This UI requires a source HU with an active picking task. The task needs to be created for the RF-Queue which is maintained as Active Queue in SAP – Implementation Guide Extended Warehouse Management SAP Extended Warehouse Management, Add-on for Consumer Products 01 General and Cross Simple UIConfigure Additional Features for Work Centers . Here, you can also define the exception codes which will be applied in case of differences.

After scanning the source HU, the screen displays the quantity to be removed as well as the quantity that will remain in the source HU after the picking is completed. You can edit both fields and declare a difference using the corresponding button. You may also decide to split the task to introduce an additional destination HU.


7.5 Packing

The Packing UI represents a stripped-down version of the /SCWM/PACK transaction. Here you shift products from a Pick-HU into a Shipping-HU.

One-Click HU Creation

One-Click HU Creation is a feature available in the Simple UI for picking, packing, and deconsolidation. You can configure several pushbuttons to appear on the screen. Once you click on a button, , the system will create an empty HU on the bin which has been maintained in transaction /SCWM/TWORKST.

The assigned packaging materials, as well as the description for the buttons, are maintained under SAP – Implementation Guide > Extended Warehouse Management > SAP Extended Warehouse Management, Add-on for Consumer Products 01 General and Cross Simple UI Configure 1-Click HU Creation in Work Center.

7.6 Deconsolidation


Simple UI

This UI supports an inbound process where a mixed pallet is deconsolidated after goods receipt posting. The UI shows all putaway warehouse tasks in status Waiting that are assigned to the selected inbound HU.

NoteThe table showing warehouse tasks has more fields than the ones that are immediately visible. You can use the horizontal scroll bar or rearrange the columns just like in the usual SAP GUI Dynpros.

Button ‘Pack item’

Once a warehouse task is selected on the left side, the material/ batch from the task will be shown in the center part of the screen, including the quantity from the warehouse task.

If the physically received quantity matches the quantity shown in the Quantity field, you must execute a packing into a new destination HU by choosing the Pack item button.

Once packing is completed, the content of the new HU is displayed in the HU-items grid on the right side.

Destination HU

Packaging Material

You have several options to create a destination HU:

● You prepare a packaging material for deconsolidation and create a packaging specification. Using condition technique and standard condition type 0DKS, you can prepare a proposal of packaging material, for example based on Work Center and Packaging Specification (transaction /SCWM/PSCT6).

NoteIf you define your consolidation groups in a suitable way (for example, separate consolidation group per destination storage type), you can base this packaging specification determination on consolidation groups and have a suitable packaging material proposed according to the destination storage type.

If condition records of type 0DKS are created in the system, it proposes the packaging material on the Simple UI accordingly. You can overwrite the proposal by pressing one of the One-Click HU buttons at the bottom of the screen.

● In addition to this automatic proposal function, the one-click HU creation can also be used to select a packaging material.

Destination HU number

● Depending on the settings you made for your packaging material type, the system will either provide an internal number or wait for an external number of the HU.

● You can also scan an existing HU as destination HU as long as it is not closed (in case of external number range assignment).

Button ‘Close HU’

Once deconsolidation into a new destination HU is completed, choose button Close HU to set the status of the putaway task to Open.

Button ‘Save’

You choose Save to perform deconsolidation into a new HU without immediately closing it. In this way, you can use the same HU for additional warehouse tasks. When you click on Save, the repacking into a new HU is executed, but the putaway task is not opened.


Difference Handling

The Quantity Differences button, when clicked, prepares the configured exception code (for example, DIFD) on the warehouse task and the underlying inbound delivery Item. The exception code is only in a pending state until it is either implicitly confirmed (using button Save) or reversed by pressing Quantity Differences again. A pending exception is indicated by the field Exception Code on the screen.

When pressing this button, by default, quantity from the warehouse task is set to zero. You must press the Save button to confirm the quantity difference to zero. It is also possible to overwrite the quantity, for example, if quantity in the warehouse task is 10PCs, but the received quantity is 7PCs. In such a case, the exception code must be set, 7PCs must be repackaged into a new handling unit, and the quantity difference must be confirmed by pressing Close or Save button.

Delivery Item Text

If a text is assigned to the inbound delivery item and that text type is allowed in the work center (in Customizing), the text will be shown in the left grid at the bottom, once the warehouse task is selected.

7.7 Value Added Service

The Value-Added Services (VAS) Simple UI represents a simplified version of /SCWM/VASEXEC and requires all standard configuration to execute value added services in a suitable Work Center. The Confirm button corresponds to the standard End, w/o Variances, and the Close HU option will complete the process step for the HU and trigger the follow-on task creation.


Simple UI

The VAS Overview tab provides an alternative way of handling the tasks. Deliveries will be marked as Rush Order if their delivery priority matches the setting in field Del.Prio in Customizing for Configure Additional Features for Work Centers under SAP – Implementation Guide Extended Warehouse Management SAP Extended Warehouse Management, Add-on for Consumer Products 01 General and Cross Simple UI .

There is another indicator named DLV complete in WS that shows a green light once all items for a delivery have been moved into the work center.

You can also rearrange the view by selecting Toggle View’ followed by one of the buttons Delivery', VAS Order’ or Activity

.

7.8 Information UI

The information UI is not bound to a physical work center – it can be used on a mobile station, for example, in the outbound areas.


Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.


Important Disclaimers and Legal Information

Application Help for SAP Extended Warehouse Management Add-On for Consumer ProductsImportant Disclaimers and Legal Information C O N F I D E N T I A L 103

www.sap.com/contactsap

© 2019 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 purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html