3. 10 LE Logistics Execution 1
10.1 LE-DSD Direct Store Delivery Backend 1
10.1.1 Direct Store Delivery Backend 1
10.1.2 LE-DSD-MD Master Data 2
10.1.2.1 Master Data for Direct Store Delivery Backend 2
10.1.3 LE-DSD-VC Visit Control 3
10.1.3.1 Visit Control in Direct Store Delivery Backend (DSD Backend) 3
10.1.4 LE-DSD-RP Transportation Planning 5
10.1.4.1 Direct Store Delivery Backend (DSD Backend
Planning 5
10.1.5 LE-DSD-VSO Vehicle Space Optimization 7
10.1.5.1 Direct Store Delivery Backend (DSD Backend
Optimization 7
10.1.5.2 Warehouse Process in Vehicle Space Optimization 9
10.1.6 LE-DSD-RA Route Accounting 11
10.1.6.1 Direct Store Delivery Backend (DSD Backend) Route Accounting 11
10.2 LE-WM Warehouse Management 12
10.2.1 LE-WM-CD Cross-Docking 13
10.2.1.1 Cross-Docking (LE-WM-CD) 13
10.2.2 LE-WM-VAS Value-Added Services 14
10.2.2.1 Value-Added Services (LE-WM-VAS) 14
10.2.2.2 Screen Conversion Tool 15
10.2.3 LE-WM-DCC Dynamic Cycle Counting 16
10.2.3.1 DCC (LE-WM-DCC) 16
10.3 LE-YM Yard Management 17
10.3.1 Yard Management (LE-YM) 17
10.3.2 Screen Conversion Tool 19
10.4 LE-TRM Task & Resource Management 20
10.4.1 Definition of Capacity Check for Nodes 20
10.4.2 Changes in Task & Resource Management (LE-
2.0 21
10.4.3 Log Monitor 21
10.4.4 Screen Conversion Tool 22
______________________________________________________________
SAP AG iii
SAP System Table of Contents SAP AG______________________________________________________________
4. 10 LE Logistics Execution
10.1 LE-DSD Direct Store Delivery Backend
10.1.1 Direct Store Delivery Backend
Use
As of SAP R/3 Enterprise 2.00 (EA-APPL 200) you can use Direct Store Delivery Backend (DSD
Backend). DSD Backend is a business process used in the consumer products industry to distribute goods
that are not distributed via retail company warehouses to end customers.
Using DSD Backend goods are available quickly in the branches and at the end customer, and consumer
products manufacturers have a direct influence on the end customer. DSD Backend allows perishable
goods to be distributed fast (foodstuffs, beverages, flowers, and newspapers). It also generates greater
profits for consumer products manufacturers than an indirect distribution model where logistics service
providers are often responsible for the replenishment logistics, and retail companies organize the logistics
for the stores.
Success factors for greater profits using DSD Backend:
o Integration of a mobile solution to support the drivers activities
o Excellent coordination of the sales and distribution processes
o Low logistics costs through efficient visit planning
Effects on Existing Data
Processes that have already been implemented and existing data from previous releases are not affected.
The system generates additional data in the master data for customers, material, vehicle, and tours (SAP
EASY ACCESS menu: Logistics -> Logistics Execution -> Direct Store Delivery Backend -> Master
Data).
Effects on Data Transfer
You do not have to transfer data from an R/3 standard system; DSD Backend is an upwardly compatible
standard development for new DSD customers.
Effects on System Administrationn
You get the full range of DSD functions in the mySAP BusinessSuite using the interface to the mobile
solution Mobile DSD.
If you want to use the map display in visit planning, you must install third-party map data.
Effects on Customizing
You configure the new DSD Backend processes in the SAP Reference IMG under: Logistics Execution
-> Direct Store Delivery Backend.
DSD Backend is contained in the Extension Set for Supply Chain Management. You activate DSD
Backend under Logistics Execution -> Direct Store Delivery Backend -> Basic Functions -> Activate
______________________________________________________________
SAP AG 1
SAP System______________________________________________________________
5. DirectStore Delivery.
You activate the interface to third-party software for vehicle space optimization under Logistics
Execution -> Direct Store Delivery Backend -> Basic Functions -> Activate Vehicle Space
Optimization.
See also
For more information, see the Release Notes on DSD Backend Master Data, Visit Control, Transportation
Planning, Vehicle Space Optimization, Route Accounting, and the SAP Library.
10.1.2 LE-DSD-MD Master Data
10.1.2.1 Master Data for Direct Store Delivery Backend
Use
As of SAP R/3 Enterprise 2.00 (EA-APPL 200) you can use Direct Store Delivery Backend (DSD
Backend). Existing master data has been enhanced and new master data created for DSD Backend.
All transactions for maintaining master data can be called from the same menu option: Logistics ->
Logistics Execution -> Direct Store Delivery Backend -> Master Data.
Customers:
You can store calendars for planned deliveries, telephone calls, and visits in the customer master.
Customer address data can be geocoded. Clear coordinates such as degree of latitude and degree of
longitude are assigned to an address. If you want to geocode house numbers, you must purchase and
install the relevant map data for the area from a third party.
You can make enhancements to the payment conditions for on the spot payments, such as cash payer or
allowed means of payment.
Drivers:
You create the drivers in the customer master. When you create a driver in the customer master, you can
use an existing customer group or a separate customer group for drivers. You determine the account
group for drivers in Customizing.
In the DSD additional data you specify the transportation planning points in whose area a driver works.
You can assign a driver the drivers license categories you have specified in Customizing.
You can determine lock times during which the driver is not taken into account in dynamic transportation
planning.
Vehicle:
You create the vehicles in the equipment master or fleet master.
You can assign a vehicle the drivers license categories you have specified in Customizing.
Tour:
______________________________________________________________
SAP AG 2
SAP System______________________________________________________________
6. A tour is created for a route with a visit plan type, and optionally for a transportation planning point. The
tour contains information on the driver and alternate driver, and on the vehicle and trailer. The system
checks whether the required drivers license categories for the vehicle are covered by the drivers license
categories.
If multiple tours are created for the same route with the same visit plan type and transportation planning
point, the deliveries are distributed to shipments in dynamic transportation planning according to the
order of the tours.
Material:
On the DSD Additional Data tab in the material master, you can determine the DSD grouping you want
the system to use to determine the delivery calendars in the DSD process if the requested delivery date is
determined in order entry.
This let you set up different delivery cycles for different materials for the same customer groups (for
example, newspapers daily, but magazines only once a week).
On the Vehicle Space Optimization Data and Vehicle Space Optimization Plant Data tabs, you can enter
control parameters that are transferred via an interface to an external vehicle space optimizer.
Effects on Existing Data
Existing data is not affected.
Effects on Data Transfer
You do not have to transfer data from an earlier release.
Effects on System Administration
If you use geocoding at street level, you must purchase, install, and administer the relevant third-party
map data.
Effects on Customizing
You call the DSD processes using the DSD Backend node in the Reference IMG: Logistics Execution ->
Direct Store Delivery Backend.
Existing Customizing settings are not affected.
See also
For more information on DSD Backend, see the SAP Library.
10.1.3 LE-DSD-VC Visit Control
10.1.3.1 Visit Control in Direct Store Delivery Backend (DSD Backend)
Use
As of SAP R/3 Enterprise 2.00 (EA-APPL 200) you can use Visit Control in Direct Store Delivery
Backend (DSD Backend) to plan and execute customer visits that recur periodically as part of the
logistics process.
______________________________________________________________
SAP AG 3
SAP System______________________________________________________________
7. You can create visit plans for long-term (strategic) planning. Visit plans describe which customers are
visited or supplied in which order, and how frequently they are visited. As well as validity period and
route, you can also maintain data on driver and means of transport. The same customer can feature in
multiple visit plans.
Based on the visit plans, you can generate visit lists for specific days. Each visit list is valid on a certain
day and describes which customers are visited in which order and with which means of transport. You
can edit visit lists manually if customer visits are cancelled at short notice, for example, more customers
have to be visited, or adjustments made due to public holidays.
You can develop visit plans and visit lists for the following roles:
o Delivery driver: only delivers goods that have been ordered in advance
o Van seller: visits customers according to the visit list and sells and delivers goods from the van
stock directly to the customer without an advance order.
o Advance seller: visits customer according to the visit list and only takes orders to be delivered later.
o You can display the assigned customers on a map when you maintain the visit plan or visit list. To
do this, you must connect a third-party map using the Internet Graphics Service (SAP Basis
interface).
On the Visit Information tab under DSD Additional Data in the customer master, you can color-highlight
the appointments that have been made for a specific customer using Visit Control.
Effects on Existing Data
Not relevant since the function is not part of the previous release.
Effects on Data Transfer
Not relevant since the function is not part of the previous release.
Effects on System Administration
If you use maps via the Internet Graphics Service, you must purchase, install, and administer third-party
map data.
Effects on Customizing
You can make the Customizing settings for Visit Control in the SAP Reference IMG under Logistics
Execution -> Direct Store Delivery Backend.
Using customizable calendar types, you can store appointments that are planned in Visit Control in
different calendars (for example, calendars with dates for goods deliveries and calendars for pre-sales
visits). You determine the calendar types using the Define Calendar Types function.
By defining visit groups in the Define Visit Groups activity, you can restrict the processing of visit plans
and visit lists to specific users.
You can assign materials to a DSD grouping in the material master. You create the DSD grouping in the
Define DSD Groupings activity, and link it to a calendar type.
Number ranges for visit plans and visit lists can be created in the Define Number Ranges for Visit Plans
and Define Number Ranges for Visit Lists activities.
The visit plan type is the central object in Visit Control and the basis for dynamic transportation planning;
______________________________________________________________
SAP AG 4
SAP System______________________________________________________________
8. your settings in the Define Visit Plan Type activity determine whether shipments orvisit lists are the
principal documents in Visit Control. You also decide on a calendar type and on the number range
interval for visit plans and visit lists.
You can use the Deliver Deliveries indicator to determine whether a van seller can make customer
deliveries that are already available. You can also choose whether you want the goods receiving timefor
the unloading point or the visit time (using the contact person function) to be displayed in Visit Control.
For dynamic transportation planning, you can determine how many deliveries should still be checked if a
delivery that is too large is rejected. You can also specify a default travel duration and length of stay. You
can determine a default value for the settlement office and settlement type for Route Accounting.
You use the Determine Allowed Sales Document Types activity to determine which sales document type is
relevant for Visit Control. This means that the requested delivery date and route are determined
according to the visit list and calendar type in order entry. You can also enter a minimum lead time for
each order type.
See also
For more information on DSD Backend, see the SAP Library.
10.1.4 LE-DSD-RP Transportation Planning
10.1.4.1 Direct Store Delivery Backend (DSD Backend) Transportation Planning
Use
As of SAP R/3 Enterprise 2.00 (EA-APPL 200) you can use Direct Store Delivery Backend (DSD
Backend) Transportation Planning. You use DSD Backend Transportation Planning to plan and organize
tours, with the aim of compiling all due deliveries into shipments.
Dynamic Transportation Planning has the following features:
o Using transportation planning you can compile shipments for transport-relevant deliveries with the
same transportation planning point, route, visit plan type, and so on.
o Dynamic transportation planning assigns vehicles, drivers, and alternate drivers to shipments on the
basis of visit lists or tours. Drivers, alternate drivers, vehicles, and trailers are managed in the
customer master or equipment master.
Using dynamic transportation planning you can select transport-relevant deliveries according to specific
criteria (selection variant for deliveries in initial screen). As well as deliveries, you also select visit lists
according to visit plan type, date of visit, and route.
The Dynamic Transportation Planning Process
1. The deliveries are selected and grouped by the system according to the specifications. All deliveries
for the same ship-to parties are treated by the system as a single delivery. The route contained in the
deliveries is an important control parameter. Sorting is done according to the itinerary from the
selected visit lists. The visit lists are the basis for the itinerary for outbound shipments or for van
______________________________________________________________
SAP AG 5
SAP System______________________________________________________________
9. sellers with their conventional sales tours.
2. The system determines vehicles and drivers from the visit lists or tours.
3. When the shipments are put together, the selected deliveries are assigned to one or more shipments
in the defined order. If you have maintained capacity criteria (weight, volume, variable capacity,
maximum duration, number of stops), it is taken into account for compiling the shipments.
Once the system has assigned the deliveries to the shipments and transferred the shipment document data,
it generates a log showing the following information:
o How many deliveries were selected
o Which deliveries were assigned to which shipments and how many shipments they were assigned to
(in a simulation run), or which deliveries were actually created (update run)
o Which visit lists were evaluated
Identification of Speculative Loads
Dynamic transportation planning can identify speculative loads (delivery to a driver). The log shows
whether or not there is a speculative load.
As soon as the first of the limits is reached, the system completes the shipment. Any deliveries not
assigned to the shipment are displayed in the log.
Dynamic transportation planning also only creates one shipment if:
o A driver or vehicle is entered in the header data of the relevant visit list
o It is a mixed case where the driver makes customer deliveries but also visits customers for whom
there are no deliveries.
Effects on Existing Data
Existing data is not affected.
Effects on Data Transfer
You do not have to transfer data from an earlier release.
Effects on System Administration
If you use geocoding at street level, you must purchase, install, and administer the relevant third-party
map data.
Effects on Customizing
The settings for transportation planning are in the SAP Reference IMG under the DSD Backend node:
Logistics Execution -> Direct Store Delivery Backend.
The existing Customizing settings are not affected.
See also
For more information, see the Release Notes on DSD Backend Route Accounting, DSD Backend Visit
Control, Master Data for DSD Backend, and the SAP Library.
______________________________________________________________
SAP AG 6
SAP System______________________________________________________________
10. 10.1.5 LE-DSD-VSO Vehicle Space Optimization
10.1.5.1 Direct Store Delivery Backend (DSD Backend) Vehicle Space
Optimization
Use
As of SAP R/3 Enterprise 2.00 (EA-APPL 200) you can use Direct Store Delivery Backend (DSD
Backend) Vehicle Space Optimization. DSD Backend Vehicle Space Optimization optimizes the
arrangement of delivery items in a shipment on packaging materials (such as palettes), and the
arrangement of the packaging materials in a means of transport. A third-party optimization algorithm
must be integrated using an interface.
The arrangement determined by vehicle space optimization depends on parameters from the following
areas:
o Optimization profile for plant and transportation type
o Customer master
o Material master for the material being delivered and for the packaging material.
You can load a means of transport according to a loading graphic that can be printed online in vehicle
space optimization.
The benefits of using Vehicle Space Optimization are as follows:
o You save time since the delivery items are arranged on the packaging materials automatically and
the packaging materials are arranged on the means of transport
o Customer-specific conditions are taken into account when the load is distributed
o Further processing of the results takes place in the warehouse process in vehicle space optimization.
If you cannot otherwise determine the result of vehicle space optimization with a justifiable amount of
effort, the following features are also beneficial:
o Loading and unloading times are minimized
o Optimum use of existing transport capacities
o Maximum weights are load distribution are taken into account
o Stacking rules are taken into account.
After vehicle space optimization, the MRP controller can use the shipment transactions Create and
Change to display a graphic showing the loading of the means of transport, check it and change it if
required.
You can also carry out vehicle space optimization in collective processing for dynamic transportation
planning (transaction /DSD/RP_DYNDISP), as well as for individual shipments.
Integration with the System
o In the Transport transactions VT01N (Create), VT02N (Change), and VT03N (Display)
______________________________________________________________
SAP AG 7
SAP System______________________________________________________________
11. - Call using a new pushbutton in the overview screen
- Display status in overview screen
o Automatic call upon saving an individual shipment, if required
o Automatic call when shipments are created using the collective processing for dynamic
transportation planning
o Display status of vehicle space optimization in the DSD Shipment List (/DSD/RP_VT11).
There is a new menu path: Logistics -> Logistics Execution -> Direct Store Delivery Backend -> Vehicle
Space Optimization.
Effects on Existing Data
To update the existing data after the release upgrade if you want to use vehicle space optimization, you
must make entries in the new vehicle space optimization fields in the VSO vehicle type master,
equipment master, customer master, and goods master. If you did not use vehicle space optimization up
to now, you do not have to make changes to existing data.
Existing data is not changed automatically.
Effects on System Administration
Required modifications:
o Set up a TCP/IP connection for the RFC server that links a third-party optimization algorithm
o Install and start the RFC server
o Install and register the third-party ActiveX control on the client on which the SAP front end is called
o Schedule the report that reorganizes the results data from vehicle space optimization as a periodic
batch job if you want the results to be reorganized regularly.
Effects on Customizing
The following new activity has been created for vehicle space optimization under the Customizing path
Logistics Execution -> Direct Store Delivery Backend -> Basic Functions:
o Activate vehicle space optimization
The following new activities have been created for vehicle space optimization under the Customizing
path Logistics Execution -> Direct Store Delivery Backend -> Vehicle Space Optimization:
o Define Process Type
o Find Process Type
o Determine Allowed Delivery Item Categories
o Assign Plant to a Transportation Planning Point
o Define Vehicle Space Optimization Profile
o Assign Vehicle Space Optimization Profile to Plant and Shipment Type
o Define Loading Bay Category
o Define VSO Vehicle Types and Loading Bays
______________________________________________________________
SAP AG 8
SAP System______________________________________________________________
12. o Define Packing Group
o Define Package Type
o Assign Package Type to a Packing Group
o Define Collective Unloading Point
o Determine HU Per Plant and Shipment Type
o Assign VSO Status to a Message
See also
For more information on DSD Backend, see the SAP Library.
10.1.5.2 Warehouse Process in Vehicle Space Optimization
Use
As of SAP R/3 Enterprise 2.00 (EA-APPL 200) you can use the warehouse process as part of Direct Store
Delivery Backend (DSD Backend) Vehicle Space Optimization. Using the warehouse process in vehicle
space optimization you can put together packaging materials (such as palettes) as they were planned in
vehicle space optimization (VSO). WM transport requests are created for picking for each VSO packing
proposal. When the WM transport requests are printed, additional information from vehicle space
optimization can also be printed.
The additional information includes the following data:
o At header level of a packaging material:
- Shipment number
- Number of the means of transport
- Number of the loading bay in the means of transport
- Number of the packaging material (different for each shipment)
- Type of packaging material (predefined, containing only one material and delivery / mixed /
closed packaging).
o At item level of a packaging material:
- Number of the layer (from bottom to top)
- Type of layer (containing only one material / mixed / remainder without layer structure).
The warehouse process can be divided into several process types. You can define the process types for
vehicle space optimization in Customizing. The stacking shipment of VSO packing proposals containing
only one material, the manual picking of mixed VSO packing proposals, the automatic picking of layers
containing only one material, or the picking of special materials in packaging materials with closed
packaging can all be defined as process types. A process type can be assigned to a packaging material
item in Customizing. The assignment depends on the type of packaging material and type of layers.
______________________________________________________________
SAP AG 9
SAP System______________________________________________________________
13. You can branch from displaying a shipment (transaction VT03N) to the overview of the packing
proposals in vehicle space optimization. The system displays the individual VSO packing proposals
grouped by process type. By selecting specific lines, you can generate, confirm, or print the relevant WM
transport requests for picking. The process types or individual VSO packing proposals can be selected to
generate the WM transport requests. If the process type is selected, all the corresponding packing
proposals also count as selected.
Generation of the WM transport requests can also be started in the shipment list (transaction
/DSD/RP_VT11). WM transport requests are generated for all packing proposals for the selected
shipments.
After the last WM transport request of a shipment has been confirmed and the picking of this shipment is
finished, handling units (HUs) can be generated for the packing proposals in vehicle space optimization.
A Customizing switch determines whether no HUs are generated at all, one HU is generated for each
packaging material, or if the HUs for the packaging material are also packed into an HU of the means of
transport. The system generates the HUs automatically in the background after the picking of the
shipment is entirely finished. The system takes the total value of the relevant WM transport requests as
the quantity of the material items of these HUs, not the planned quantity in vehicle space optimization,
since this is the actual quantity on the packaging material.
You can print your own load list in vehicle space optimization. The load list in vehicle space optimization
is the standard list for a shipment enhanced by the specific VSO fields.
Effects on System Administrationn
If you want handling units for the packing proposals in vehicle space optimization to be generated
automatically, you must schedule report /VSO/P_PROC_SYNC_HU as a periodic batch job.
Effects on Customizing
You must make the following Customizing settings for the warehouse process in vehicle space
optimization:
o Define and find process categories in Vehicle Space Optimization
(SAP Reference IMG: Logistics Execution -> Direct Store Delivery Backend -> Vehicle Space
Optimization)
You must define at least one process type. The system must find one process type for all items in vehicle
space optimization otherwise it cannot save the result of vehicle space optimization to the database.
Under the same path, you can also choose the automatic generation of handling units for the packing
proposals in vehicle space optimization.
If you want to print the special vehicle space optimization fields when you print WM transport requests,
you must make settings in Customizing for printing the WM transport request (SAP Reference IMG:
Logistics Execution -> Warehouse Management -> Activities -> Define Print Control).
See also
For more information on DSD Backend, see the SAP Library.
______________________________________________________________
SAP AG 10
SAP System______________________________________________________________
14. 10.1.6 LE-DSD-RA Route Accounting
10.1.6.1 Direct Store Delivery Backend (DSD Backend) Route Accounting
Use
As of SAP R/3 Enterprise 2.00 (EA-APPL 200) you can use Direct Store Delivery Backend (DSD
Backend) Route Accounting. DSD Backend Route Accounting supports the entire process of delivery or
route sales using a check-out, check-in, and a settlement transaction. Route Accounting begins once the
vehicle has been loaded, and ends when all the operations are posted. Route Accounting can include the
following activities:
o Check-out
o Check-in
o Settlement
Drivers who have returned from a tour hand in the documents and equipment belonging to their tour to
the settlement office. These include:
o Documents
o Sums of money
o Credit card documents
o New orders
o Tour data in a handheld device
You can also use Route Accounting without using handheld devices. Drivers record tour activities by
hand in the appropriate documents. You can subsequently enter the hand-written information in the
system.
The settlement cockpit is used to display and correct tour data, and enter additional data manually.
If the drivers do not use handheld devices, you can enter all required tour data manually in the settlement
cockpit. You can:
o Edit general tour data
o Enter check-out/check-in data
o Carry out difference determination
o Enter time data for a tour
o Enter distance data for a tour
o Enter collection data for a tour
o Edit visit data
o Edit delivery execution data
o Enter order
______________________________________________________________
SAP AG 11
SAP System______________________________________________________________
15. o Display invoices
o Enter time data on customer visits
o Enter distance data on customer visits
o Enter and assign collection data on customer visits
o Display the application log
o Display the settlement document
o Display the document flow
o Perform a DSD settlement run
o Scope of functionality
o Execute DSD collection clearing
o Execute DSD clearing in dialog or without dialog
o Display the clearing log
o Clear open items
DSD Backend Route Accounting is an offline solution, in other words, there is an exchange of data
between a handheld device and the SAP R/3 System at the start and end of a tour. There is no data
exchangeduring the tour.
Effects on Existing Data
Not relevant since the functions were not part of the last release.
Effects on Data Transfer
Not relevant since the functions were not part of the last release.
Effects on System Administration
Not relevant.
Effects on Customizing
The settings for Route Accounting are in the SAP Reference IMG under the DSD Backend node:
Logistics Execution -> Direct Store Delivery Backend.
Customizing for Dynamic Transportation Planning must be set up, including Visit Control.
See also
For more information, see the Release Notes on DSD Backend Visit Control, Transportation Planning,
Master Data for DSD Backend, and the SAP Library.
______________________________________________________________
SAP AG 12
SAP System______________________________________________________________
16. 10.2 LE-WM Warehouse Management
10.2.1 LE-WM-CD Cross-Docking
10.2.1.1 Cross-Docking (LE-WM-CD)
Use
In today's warehouse environment, customers aim to handle materials more efficiently and minimize
unnecessary material double-handling to reduce cycle times, inventory and handling costs. Maximizing
cross-docking utilization is one way of achieving this goal. Cross-Docking extends existing warehousing
functionality to the realm of cross-docking.
Cross-Docking provides the following features:
Planned and Opportunistic Cross-Docking
Cross-Docking enables you to create cross-docking decisions prior to the arrival of incoming stock and
release of the outgoing delivery or transfer requirement, as well as after goods have physically arrived at
the warehouse. These decisions can be created in contravention of strict FIFO according to a tolerance
duration determined in customization.
One-Step and Two-Step Cross-Docking Execution
Cross-Docking enables goods to be either be directly moved between the goods receipt and goods issue
areas, or first moved from goods receipt to a storage area specifically designated for cross-docking,
before being moved to the goods issue area.
Cross-Docking Decision Optimization
Cross-Docking determines the optimal cross-docking decisions and proposes these decisions. You can
either create these decisions in the background or view the decisions and decide whether or not to accept
them.
Monitoring and Response Tools - Cross-Docking Monitor
Cross-Docking enables you to monitor the cross-docking situation in the warehouse and invoke methods
to respond to this situation.
Cross-Dock Planning Tool
From the monitor, you can also invoke the cross-dock planning tool, a tool that enables you to analyze
inbound and outbound documents and manually create your own cross-docking decisions. The tool also
ensures that doors can be scheduled for the documents of any created decisions.
Alerts and Troubleshooting Tools - Cross-Docking Alert Monitor
Cross-Docking provides information on actual and arising problematic situations regarding cross-docking
in the warehouse, and enables you to handle exceptions.
Effects on Customizing
To use Cross-Docking, you must define the following in Customizing for Logistics Execution ->
______________________________________________________________
SAP AG 13
SAP System______________________________________________________________
17. Warehouse Management - Cross-Docking:
o General warehouse level settings, including the cross-docking storage type, outbound document
release and latest release times, and FIFO tolerance duration.
o The relevancy of cross-docking for warehouse movement types
You also have the option of personalizing the monitor and alert monitor, as well as implementing
project-specific logic via Business Add-Ins.
See also
o IMG for Logistics Execution -> Warehouse Management -> Cross-Docking
o SAP Library for Logistics Execution -> Warehouse Management -> Cross-Docking
10.2.2 LE-WM-VAS Value-Added Services
10.2.2.1 Value-Added Services (LE-WM-VAS)
Use
Value-Added Services (VAS) enables you to manage and control the execution of value-added services in
your warehouse.
Using VAS, you can perform and manage the following types of value-added services:
o VAS with handling unit (HU) changes, such as gift wrapping two materials
o VAS without HU changes, such as wrapping materials on the same pallet
VAS provides the following features:
Support of Simple (Supplementary) and Complex VAS
VAS supports value-added services that do not require special equipment or space, as well as those that
need to be executed in a work center. Simple VAS can be executed as part of transfer order (TO)
execution, while special desktop and radio frequency transactions are provided for executing VAS in
work centers.
VAS Templates
VAS allows you to create templates that form the basis of VAS orders, enabling the re-use of standard
instructions and other details for different document items. VAS automatically creates VAS orders based
on the predefined templates when reference documents meet predefined conditions.
Monitoring and Response Tools - VAS Monitor
VAS enables you to monitor value-added services in the warehouse, including the statuses of all
value-added services and the workload of work centers. You can also use the monitor to invoke methods
to respond to constantly changing circumstances in the warehouse.
Alerts and Troubleshooting Tools - VAS Alert Monitor
______________________________________________________________
SAP AG 14
SAP System______________________________________________________________
18. VAS provides information on actual and arising problematic situations in the warehouse with respect to
value-added services, and enables you to handle exceptions.
Mobile Presentation
VAS allows you to customize the presentation of data to a worker on a variety of presentation devices.
Integration with Task and Resource Management (TRM)
For warehouses in which TRM is implemented, VAS can be integrated with TRM to support movements
to and from work centers, as well as the execution of supplementary and complex value-added services.
Effects on Customizing
In order to use VAS, you must define the following in Customizing for Logistics Execution -> Warehouse
Management -> Value-Added Services:
o General settings, such as VAS warehouse settings, work centers and VAS order number ranges
o Settings for VAS template determination
o Presentation device settings, including the menu catalog and menu tree
You also have the option of doing the following:
o Personalizing the way in which data is presented on resource presentation devices, such as defining
function code profiles and pushbuttons
o Personalizing the monitor and alert monitor
o Implementing project-specific logic via Business Add-Ins
See also
o IMG for Logistics Execution -> Warehouse Management -> Value-Added Services
o SAP Library for Logistics Execution -> Warehouse Management -> Value-Added Services
10.2.2.2 Screen Conversion Tool
Use
In Task and Resource Management, Yard Management and Value-Added Services (VAS) Release 4.70,
Extension 2.0, you can effectively adjust the size and position of screen elements to fit the physical
dimensions of any presentation device (such as those with a screen size of 16x20).
The screen conversion tool enables you to do the following:
______________________________________________________________
SAP AG 15
SAP System______________________________________________________________
19. o Create new display profiles, including template screens, sub-screens and their respective
environments.
o Perform analyses regarding screen compression and overlapping of lines and columns before
creating new screens
o Delete fields from screens
o Generate all new screens at once
o Manually edit new screens individually
The tool significantly reduces the effort required for screen size adjustment.
Effects on Customizing
The screen conversion tool automatically updates the relevant presentation management customizing
views (IMG activity Define Display Profiles and Physical Screens).
See also
o SAP Library for Logistics Execution -> Task and Resource Management
o SAP Library for Logistics Execution -> Yard Management
o SAP Library for Logistics Execution -> Warehouse Management -> Value-Added Services
10.2.3 LE-WM-DCC Dynamic Cycle Counting
10.2.3.1 DCC (LE-WM-DCC)
Use
Dynamic Cycle Counting (DCC) enhances the previous RF inventory counting functionality by enabling
you to count physical inventory at storage bin and quant level during the performance of normal
warehouse operations, and allowing the creation of inventory documents when open transfer orders
(unconfirmed picks and putaways) exist for a bin. This ensures continued warehouse operations and
facilitates cycle counts during peak activity periods.
DCC provides the following features:
Inventory Counting Against Active and Inactive Inventory Documents
DCC enables inventory counting against both active and inactive inventory documents, allowing you to
count the physical inventory in a bin whether or not open transfer orders exist for the bin.
Inventory Counting at Both Bin and Quant Level
DCC supports inventory counting for a bin, as well as for a specific material in the bin.
Different Modes of Bin/Quant Selection
______________________________________________________________
SAP AG 16
SAP System______________________________________________________________
20. There are three main options for performing a dynamic inventory count using an RF device:
1. System-guided - The system proposes all of the bins/materials of an inventory document that was
assigned to the particular user. This assignment takes place during the creation of the document.
2. User-selected -The user selects the storage bin or material for the inventory count. Under this
option, you can select and scan storage bins or materials within a warehouse area that are assigned
from an organizational point of view.
3. User-initiated - In a case where an inventory document does not already exist in the system, the
system creates "on the fly" an inactive or active document for the selected storage bin or material in
the bin. The user can then start the inventory count.
Automatic Clearing of Inactive Inventory Documents
DCC supports the automatic clearing of an inventory count in Warehouse Management (WM) against
active documents, or inactive documents if the count results in no differences.
Effects on Existing Data
DCC involves minimal changes to the existing inventory counting transactions LM50 (user-selected
storage unit count) and LM51 (system-guided storage unit count). It uses similar RF screens with the
following changes:
o Addition of the Material field below the Storage Bin field in the initial selection screen
o The More pushbutton replaces the DISU pushbutton
o Addition of the DelDoc pushbutton
o Addition of various message screens
o Addition of new inventory count status D (dynamic cycle count)
Even though transactions LM50 and LM51 still exist in the system, you need only use the new DCC
transactions (LM58, LM59 and LM60).
Effects on Customizing
To use DCC, you must create at least one record for a specific storage type in Customizing for Logistics
Execution -> Warehouse Management -> Activities -> Physical Inventory -> Dynamic Cycle
Counting -> General Settings -> Define Storage Type Settings.
See also
IMG for Logistics Execution -> Warehouse Management -> Activities -> Physical Inventory ->
Dynamic Cycle Counting
______________________________________________________________
SAP AG 17
SAP System______________________________________________________________
21. 10.3 LE-YM Yard Management
10.3.1 Yard Management (LE-YM)
Use
Yard Management (LE-YM) extends warehouse management beyond the physical walls of the warehouse,
enabling management and control from the time that goods are planned to arrive at the warehouse. YM
provides the following features:
Management of Yard Processes
YM enables you to manage the following yard processes:
o Check-in and check-out of vehicles
o Scheduling of doors and staging areas for vehicles (manually or based on the system's automatic
scheduling mechanism)
o Creation and execution of movements in the yard (manually or based on the system's location
determination mechanism)
o Creation and execution of operations in the yard, such as weighing and sealing/un-sealing of
vehicles
o Registration of the start and finish of loading and unloading of vehicles
Provision of Information to Business Partners
YM provides business partners, such as freight forwarders, with information on their vehicles, including
time in yard, current location and processing status. This information may be provided either via the R/3
system or via the Web.
Monitoring and Response Tools - Yard Monitor
YM enables you to monitor all aspects of yard operations and invoke methods to respond to constantly
changing circumstances in the yard.
Alert and Troubleshooting Tools - Yard Alert Monitor
YM provides information on actual and arising problematic situations in the yard, and enables you to
handle exceptions.
Scheduling Chart
YM enables you to view, manually create and maintain scheduling activities via the yard scheduling chart,
a graphical representation of scheduling activities for the yard.
Mobile Presentation
YM allows you to customize the presentation of data to a resource on a variety of presentation devices.
______________________________________________________________
SAP AG 18
SAP System______________________________________________________________
22. Effects on Customizing
To use YM, you must define the following in Customizing for Logistics Execution -> Yard Management:
o General settings, such as the yard, activity number ranges and reason codes for exception situations
o The yard map, including doors, staging areas and yard locations
o Settings, such as scheduling profiles, to enable location determination and scheduling
o Presentation device settings, including the menu catalog and menu tree
You also have the option of doing the following:
o Refining scheduling and location determination by defining vehicle type groups, forwarding agent
vehicle types, location type-vehicle type group relationships, yard location groups, location group
relationships and location-time properties
o Personalizing the way in which data is presented on resource presentation devices, such as defining
function code profiles and pushbuttons
o Personalizing the monitor and alert monitor
o Implementing project-specific logic via Business Add-Ins
See also
o IMG for Logistics Execution -> Yard Management
o SAP Library for Logistics Execution -> Yard Management
10.3.2 Screen Conversion Tool
Use
In Task and Resource Management, Yard Management and Value-Added Services (VAS) Release 4.70,
Extension 2.0, you can effectively adjust the size and position of screen elements to fit the physical
dimensions of any presentation device (such as those with a screen size of 16x20).
The screen conversion tool enables you to do the following:
o Create new display profiles, including template screens, sub-screens and their respective
environments.
o Perform analyses regarding screen compression and overlapping of lines and columns before
creating new screens
o Delete fields from screens
o Generate all new screens at once
o Manually edit new screens individually
The tool significantly reduces the effort required for screen size adjustment.
______________________________________________________________
SAP AG 19
SAP System______________________________________________________________
23. Effects on Customizing
The screen conversion tool automatically updates the relevant presentation management customizing
views (IMG activity Define Display Profiles and Physical Screens).
See also
o SAP Library for Logistics Execution -> Task and Resource Management
o SAP Library for Logistics Execution -> Yard Management
o SAP Library for Logistics Execution -> Warehouse Management -> Value-Added Services
10.4 LE-TRM Task & Resource Management
10.4.1 Definition of Capacity Check for Nodes
Use
In Task & Resource Management (LE-TRM) Release 4.70, Extension 2.0, you can limit the number of
handling units, by type, physically occupying a node at any given time.
The node capacity check is implemented as part of the existing execution control mechanism. You define
a particular node as a static ECO, and then define its capacity in terms of handling units.
During task selection, the system determines whether the selection of a task (having the node as its
destination) will result in the node's capacity being exceeded. If so, the node ECO is unavailable, and no
resource will be able to select this task until the ECO is available again.
Effects on Customizing
The following has been added to IMG activity Execution Control:
o Node as an option in the ECO type field
o Handling Unit Type as an option in the Constraint field
o A list of handling unit types in the Constr.ob field
______________________________________________________________
SAP AG 20
SAP System______________________________________________________________
24. See also
IMG for Logistics Execution -> Task and Resource Management
10.4.2 Changes in Task & Resource Management (LE-TRM) Rel 4.7 Ext 2.0
Use
Task & Resource Management (LE-TRM) Release 4.70, Extension 2.0 has a number of new features:
Node capacity check
Task execution control has been enhanced through the introduction of capacity check for nodes.
For more information, see Definition of Capacity Check for Nodes.
Screen conversion tool
You can now effectively adjust the size and position of screen elements to fit the physical dimensions of
any presentation device.
For more information, see Screen Conversion Tool.
Log monitor
You can now display and track log data via the log monitor, increasing the transparency of warehouse
processes.
For more information, see Log Monitor.
See also
o IMG for Logistics Execution -> Task and Resource Management
o SAP Library for Logistics Execution -> Task and Resource Management
10.4.3 Log Monitor
Use
The log monitor is a tool that enables warehouse managers to view the data kept in log tables. The
information kept in the log tables may assist the manager in a number of ways, including:
o Planning the number and types of warehouse resources needed at any given time, based on expected
workload
o Assessing the performance of the warehouse as a whole
______________________________________________________________
SAP AG 21
SAP System______________________________________________________________
25. Effects on Customizing
The log monitor utilizes the same functionality as the TRM monitor, including a selection screen,
hierarchy tree with drag&drop functionality and ALV. The customizing activities are identical to that of
the monitor.
See also
o IMG for Logistics Execution -> Task and Resource Management
o SAP Library for Logistics Execution -> Task and Resource Management
10.4.4 Screen Conversion Tool
Use
In Task and Resource Management, Yard Management and Value-Added Services (VAS) Release 4.70,
Extension 2.0, you can effectively adjust the size and position of screen elements to fit the physical
dimensions of any presentation device (such as those with a screen size of 16x20).
The screen conversion tool enables you to do the following:
o Create new display profiles, including template screens, sub-screens and their respective
environments.
o Perform analyses regarding screen compression and overlapping of lines and columns before
creating new screens
o Delete fields from screens
o Generate all new screens at once
o Manually edit new screens individually
The tool significantly reduces the effort required for screen size adjustment.
Effects on Customizing
The screen conversion tool automatically updates the relevant presentation management customizing
views (IMG activity Define Display Profiles and Physical Screens).
See also
o SAP Library for Logistics Execution -> Task and Resource Management
o SAP Library for Logistics Execution -> Yard Management
o SAP Library for Logistics Execution -> Warehouse Management -> Value-Added Services
______________________________________________________________
SAP AG 22
SAP System______________________________________________________________
