Anda di halaman 1dari 51

LE Logistics Execution

SAP R/3 Enterprise


Release 470x200

Release Notes

Copyright 2003 SAP AG. 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 AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX, S/390, AS/400, OS/390, and OS/400 are registered trademarks of IBM Corporation. ORACLE is a registered trademark of ORACLE Corporation. INFORMIX-OnLine for SAP and Informix Dynamic Server Incorporated.
TM

are registered trademarks of Informix Software

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies. Design: SAP Communications Media

SAP System Table of Contents SAP AG ______________________________________________________________

17 17.1 17.1.1 17.1.2 17.1.2.1 17.1.3 17.1.3.1 17.1.4 17.1.4.1 17.1.5 17.1.5.1 17.1.5.2 17.1.6 17.1.6.1 17.2 17.2.1 17.3 17.3.1 17.3.1.1 17.3.1.2 17.3.2 17.3.2.1 17.3.2.2 17.4 17.4.1

LE Logistics Execution LE-DSD Direct Store Delivery Backend Direct Store Delivery Backend LE-DSD-MD Master Data Master Data for Direct Store Delivery Backend LE-DSD-VC Visit Control Visit Control in Direct Store Delivery Backend (DSD Backend) LE-DSD-RP Transportation Planning Direct Store Delivery Backend (DSD Backend) Transportation Planning LE-DSD-VSO Vehicle Space Optimization Direct Store Delivery Backend (DSD Backend) Vehicle Space Optimization Warehouse Process in Vehicle Space Optimization LE-DSD-RA Route Accounting Direct Store Delivery Backend (DSD Backend) Route Accounting LE-MOB Mobile Data Entry Business Add-Ins for Logistics Execution (new) LE-IDW Decentralized WMS Integration LE-IDW-CEN Central Processing Subsequent Changes to the Delivery (New) Delayed Distribution of Inbound and Outbound Deliveries to the LE-IDW-DEC Local Operations Several ERP Systems to One Decentralized WMS Subsequent Changes to the Delivery (New) LE-WM Warehouse Management Business Add-Ins for Logistics

1 1 1 2 2 3 3 5 5 7 7 9 11 11 13 13 14 14 14 16 17 17 19 21

______________________________________________________________
SAP AG iii

SAP System Table of Contents SAP AG ______________________________________________________________

17.4.2 17.4.3 17.4.4 17.4.4.1 17.4.4.2 17.4.4.3 17.4.5 17.4.5.1 17.4.6 17.4.6.1 17.4.7 17.4.7.1 17.4.8 17.4.8.1 17.4.9 17.4.9.1 17.4.10 17.4.10.1 17.4.10.2 17.4.11 17.4.11.1 17.5 17.5.1 17.5.2 17.6 17.6.1

Execution (new) Changes to the Structure in the Logistics Execution IMG Delayed Update of Outbound Delivery (New) LE-WM-TFM Stock Movements Business Add-Ins for Logistics Execution (new) Transfer Order for Multiple Outbound Deliveries (New) Delayed Update of Outbound Delivery (New) LE-WM-BIN Inventory at the Storage Bin Level Business Add-Ins for Logistics Execution (new) LE-WM-STU Storage Unit Management Stock Overview for SU-Managed Bulk Storage (Changed) LE-WM-IFC Interfaces Links Between IDoc and Business Object (New) LE-WM-GF Other Functions Delayed Update of Outbound Delivery (New) LE-WM-CD Cross-Docking Cross-Docking (LE-WM-CD) LE-WM-VAS Value-Added Services Value-Added Services (LE-WM-VAS) Screen Conversion Tool LE-WM-DCC Dynamic Cycle Counting DCC (LE-WM-DCC) LE-YM Yard Management Yard Management (LE-YM) Screen Conversion Tool LE-TRM Task & Resource Management Definition of Capacity Check for Nodes

21 22 23 23 24 25 25 26 26 27 27 28 28 29 29 29 29 31 31 32 33 33 34 34 36 37 37

______________________________________________________________
SAP AG iv

SAP System Table of Contents SAP AG ______________________________________________________________

17.6.2 17.6.3 17.6.4 17.7 17.7.1 17.7.2 17.7.2.1 17.7.2.2 17.7.2.3 17.7.3 17.7.3.1 17.8 17.8.1 17.8.1.1 17.8.1.2

Changes in Task & Resource Management (LE-TRM) Rel 4.7 Ext 2.0 Log Monitor Screen Conversion Tool LE-SHP Shipping Changes to the Structure in the Logistics Execution IMG LE-SHP-DL Delivery Processing Business Add-Ins for Logistics Execution (new) Conversion of Matchcode Objects in Delivery Processing Partial Goods Receipt for Inbound Delivery (New) LE-SHP-GI Goods Issue Business Add-Ins for Logistics Execution (new) LE-TRA Transportation LE-TRA-FC Freight Processing Business Add-Ins for Logistics Execution (new) Direct Navigation from the Shipment Cost Document to the Reference

38 38 39 39 40 40 40 41 43 43 43 44 44 44 45

______________________________________________________________
SAP AG v

SAP System ______________________________________________________________

17 LE 17.1 LE-DSD

Logistics Execution Direct Store Delivery Backend

17.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 o o Integration of a mobile solution to support the drivers activities Excellent coordination of the sales and distribution processes 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

______________________________________________________________
SAP AG 1

SAP System ______________________________________________________________

DSD Backend under Logistics Execution -> Direct Store Delivery Backend -> Basic Functions -> Activate 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.

17.1.2 LE-DSD-MD

Master Data

17.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:

______________________________________________________________
SAP AG 2

SAP System ______________________________________________________________

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: 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.

17.1.3 LE-DSD-VC

Visit Control

17.1.3.1 Visit Control in Direct Store Delivery Backend (DSD Backend)

______________________________________________________________
SAP AG 3

SAP System ______________________________________________________________

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. 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 o o o Delivery driver: only delivers goods that have been ordered in advance 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. Advance seller: visits customer according to the visit list and only takes orders to be delivered later. 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

______________________________________________________________
SAP AG 4

SAP System ______________________________________________________________

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 Visit Plans and Define Number Ranges for Visit Lists activities. Define Number Ranges for

The visit plan type is the central object in Visit Control and the basis for dynamic transportation planning; 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.

17.1.4 LE-DSD-RP

Transportation Planning

17.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 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. 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.

______________________________________________________________
SAP AG 5

SAP System ______________________________________________________________

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 sellers with their conventional sales tours. The system determines vehicles and drivers from the visit lists or tours. 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.

2. 3.

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 o o How many deliveries were selected 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) 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 o A driver or vehicle is entered in the header data of the relevant visit list 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

______________________________________________________________
SAP AG 6

SAP System ______________________________________________________________

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.

17.1.5 LE-DSD-VSO

Vehicle Space Optimization

17.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 o o Optimization profile for plant and transportation type Customer master 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 o 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 Customer-specific conditions are taken into account when the load is distributed 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

______________________________________________________________
SAP AG 7

SAP System ______________________________________________________________

o o o

Optimum use of existing transport capacities Maximum weights are load distribution are taken into account 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) o o o Call using a new pushbutton in the overview screen Display status in overview screen

Automatic call upon saving an individual shipment, if required Automatic call when shipments are created using the collective processing for dynamic transportation planning 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 o o o Set up a TCP/IP connection for the RFC server that links a third-party optimization algorithm Install and start the RFC server Install and register the third-party ActiveX control on the client on which the SAP front end is called 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

______________________________________________________________
SAP AG 8

SAP System ______________________________________________________________

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 o o o o o o o o o o o o o See also For more information on DSD Backend, see the SAP Library. Define Process Type Find Process Type Determine Allowed Delivery Item Categories Assign Plant to a Transportation Planning Point Define Vehicle Space Optimization Profile Assign Vehicle Space Optimization Profile to Plant and Shipment Type Define Loading Bay Category Define VSO Vehicle Types and Loading Bays Define Packing Group Define Package Type Assign Package Type to a Packing Group Define Collective Unloading Point Determine HU Per Plant and Shipment Type Assign VSO Status to a Message

17.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

______________________________________________________________
SAP AG 9

SAP System ______________________________________________________________

Number of the packaging material (different for each shipment) Type of packaging material (predefined, containing only one material and delivery / mixed / closed packaging).

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. 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:

______________________________________________________________
SAP AG 10

SAP System ______________________________________________________________

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.

17.1.6 LE-DSD-RA

Route Accounting

17.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 o o Check-out Check-in 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 o o o o Documents Sums of money Credit card documents New orders Tour data in a handheld device

______________________________________________________________
SAP AG 11

SAP System ______________________________________________________________

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 o o o o o o o o o o o o o o o o o o o o o Edit general tour data Enter check-out/check-in data Carry out difference determination Enter time data for a tour Enter distance data for a tour Enter collection data for a tour Edit visit data Edit delivery execution data Enter order Display invoices Enter time data on customer visits Enter distance data on customer visits Enter and assign collection data on customer visits Display the application log Display the settlement document Display the document flow Perform a DSD settlement run Scope of functionality Execute DSD collection clearing Execute DSD clearing in dialog or without dialog Display the clearing log 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

______________________________________________________________
SAP AG 12

SAP System ______________________________________________________________

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.

17.2 LE-MOB

Mobile Data Entry

17.2.1 Business Add-Ins for Logistics Execution (new)


Use As of SAP R/3 Enterprise 4.70 (SAP_APPL 470) Business Add-Ins (BAdIs) are available in Logistics Execution in the following areas: o o o o Warehouse Management Shipping Transportation Mobile Data Entry

Effects on Customizing To activate the Business Add-In, you have to create an active implementation. To do so, go to the Customizing for Logistics Execution, and choose o Warehouse Management -> System Modifications -> Business Add-Ins in Warehouse Management -> Business Add-In for Determining Quant Business Add-In for Determining Storage Type Business Add-In for Determining Storage Unit Type Business Add-In for Entering Inventory Data in Inventory Management

______________________________________________________________
SAP AG 13

SAP System ______________________________________________________________

Shipping -> System Modifications -> Business Add-Ins in Shipping Business Add-In for Delivery Processing Business Add-In for Price Determination in the Delivery Business Add-In for Subsequent Outbound Delivery Split Business Add-In for Posting Goods Movements Business Add-In for Additional Header Detail Screen in Delivery Transaction Business Add-In for Additional Item Detail Screen in Transaction Business Add-In for Additional Overview Screen in Delivery Transaction Business Add-Ins in Transportation

Transportation --> System Modifications --> -

Business Add-In for Checks when Creating a Shipment Cost Document Business Add-In for Creating a Shipment Cost Document Business Add-In for Shipment Cost Account Assignment Business Add-In for Checks During Shipment Cost Processing Business Add-In for Transferring Shipment Cost Items Business Add-In for Saving Shipment Cost Documents

Mobile Data Entry -> System Modifications -> Business Add-Ins in Mobile Data Entry Business Add-In for Queue Determination

17.3 LE-IDW
17.3.1 LE-IDW-CEN

Decentralized WMS Integration


Central Processing

17.3.1.1 Subsequent Changes to the Delivery (New)


Use As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), in inbound and outbound deliveries, you can subsequently change certain data after it has been distributed by the central Enterprise Resource Planning system (ERP system) to the decentralized Warehouse Management System (WMS). You can make these changes in either the central or decentralized system. The interface between the systems performs a subsequent change in the partner system for the following delivery data that is planned for a comparison: o Changes to the inbound delivery header data Gross and net weight

______________________________________________________________
SAP AG 14

SAP System ______________________________________________________________

Volume Delivery date Door Delete delivery (only using the interface) External identification

Changes to the inbound delivery item data Gross and net weight Volume Expiration date Delivery quantity Delete delivery item (only using the interface)

Changes to the outbound delivery header data Gross and net weight Volume Delivery date Door Delete delivery (only using the interface) Incoterms Route Shipping condition Delivery priority Unloading point Picking date Loading date Shipment date Goods issue date

Changes to the outbound delivery item data Gross and net weight Volume Delivery quantity Delete delivery item (only using the interface)

Changes to the partner data for inbound and outbound deliveries Delete or change a partner from a partner role

______________________________________________________________
SAP AG 15

SAP System ______________________________________________________________

Change a partner's address

Effects on Customizing If you have not yet generated a distribution model for inbound and outbound deliveries, you create this distribution model in Customizing under Logistics -> Logistics Execution -> Decentralized WMS Integration -> Central Processing -> Distribution -> Generate Distribution Model. Here you set the Use change management for inbound and outbound deliveries indicator. If the distribution model for inbound and outbound deliveries already exists, enter the following methods in the central system manually into the distribution model using ALE Customizing: o o InboundDelivery.DeliveryChange OutboundDelivery.DeliveryChange

You also set the filter for recipient determination for these methods: o o From the central system to the decentralized system, recipient determination takes place using the warehouse number filter. From the decentralized system to the central system, you can use the logical system filter for recipient determination if both systems have a release status of SAP R/3 Enterprise.

You then generate the partner profile for the new methods, and distribute the distribution model to the connected decentralized WMS. Within the decentralized WMS, a blocking concept must be introduced to ensure that you cannot process the delivery simultaneously in both systems. To implement this, choose in Customizing Logistics -> Logistics Execution -> Decentralized WMS Integration -> Central Processing -> Distribution Model -> Activate Cross-System Lock. See also For more information on the cross-system lock, see the SAP Library under Basis -> Client-Server Technology -> Cross-System Lock (CSL).

17.3.1.2 Delayed Distribution of Inbound and Outbound Deliveries to the Decentralized Warehouse Management System (New)
Use As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can distribute inbound and outbound deliveries to the decentralized Warehouse Management System (WMS) with a delay. Here, you can decide as of which point the inbound or outbound delivery is staged, and can therefore be transferred to the decentralized WMS. Effects on Customizing Make the following settings in Customizing for the warehouse number and the delivery type: 1. For the warehouse number, set whether deliveries should be distributed directly after they are created, or with a delay. For more information, see the Implementation Guide (IMG) under Logistics Execution -->

______________________________________________________________
SAP AG 16

SAP System ______________________________________________________________

Decentralized WMS Integration --> Central Processing --> Application --> Activiate Decentralized WMS. This setting affects all inbound and outbound deliveries that are processed in the relevant warehouse number. 2. For the corresponding delivery type, set the distribution mode for the deliveries. The permitted modes for distributing inbound and outbound deliveries are as follows: a) b) Distribution occurs according to your settings for the warehouse number. Distribution is suppressed.

c) Distribution occurs immediately after the delivery is created. For more information, see the Implementation Guide (IMG) under Logistics Execution --> Shipping --> Deliverie --> Define Delivery Types. You can use this activity to set the distribution for each delivery type independently of the warehouse number. Note, that any settings you make here overwrite the settings for the warehouse number. Note You can distribute suppressed inbound or outbound deliveries at a time to the decentralized WMS at a time of your choosing, by selecting the function 'For Distribution' in the delivery monitor (transaction VL06).

17.3.2 LE-IDW-DEC

Local Operations

17.3.2.1 Several ERP Systems to One Decentralized WMS


Use As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), it is technically possible to connect several ERP systems to one decentralized WMS. This possibility also changes the filter criteria in particular, in as far as the new filter criterion "logical system" is used to find the ERP system. For the following methods of the delivery, the central ERP system is determined using the filter criterion "logical system": o o o o o InboundDelivery.ConfirmDecentral InboundDelivery.DeliveryChange OutboundDelivery.ConfirmDecentral OutboundDelivery.DeliveryChange OutboundDelivery.SplitDecentral

Effects on Existing Data For the method GoodsMovement.CreateFromData, the ERP system is still found using the filter criteria "plant" and "storage location". For this to function correctly, all ERP systems that are connected to a decentralized WMS must have unique and mutually exclusive plant-storage location combinations. You should manage inventory for the various ERP systems at plant-storage location level, in order that inventory differences can be ascribed to one specific

______________________________________________________________
SAP AG 17

SAP System ______________________________________________________________

ERP system. When you clear inventory differences, always make an additional selection using the plant-storage location. These fields can be taken from the free selection. To clear inventory differences, from the SAP menu choose: Logistics --> Logistics Execution --> Internal Whse Processes --> Physical Inventory --> In Warehouse Management --> Clear Differences --> Inventory Management. The following prerequisites must be fulfilled if you connect several ERP systems to one decentralized WMS: o Unique numbers for master data in the decentralized WMS The different customer masters, vendor masters, creditor masters, and material masters from the various ERP systems must have unique numbers, so that a master record can always be read exclusively on the decentralized WMS. Unique numbers for organizational units in the decentralized WMS The different plants and storage locations in the decentralized WMS must have unique numbers. Unique numbers for deliveries in the decentralized WMS Deliveries from different ERP systems must be unique in the decentralized WMS. When you replicate the deliveries, ensure that the deliveries are unique in the decentralized system.

Effects on System Administration If several ERP systems are connected to a decentralized WMS, then existing distribution models must be changed as described below. For the following methods, the filter criteria for recipient determination are changed as follows: o o o o o InboundDelivery.ConfirmDecentral InboundDelivery.DeliveryChange OutboundDelivery.ConfirmDecentral OutboundDelivery.DeliveryChange OutboundDelivery.SplitDecentral

You must perform the following activities for changing the filter criteria once only: 1. Maintain the filter object type To do this, from the SAP menu choose: Recipient Determination -> Define Filter Add the following entry to the table ALE Object Type Table Name Field Name Tools -> ALE -> ALE Development Object Type. LOGSYS TBDLS LOGSYS ->

2.

Assign the filter object type to a BAPI To do this, from the SAP menu choose: Tools -> ALE -> ALE Development -> Recipient Determination -> Assign Filter Object Type to BAPI. Add the following entries to the table: Object Type Method Filter Object Type LIKP CONFIRMDECENTRAL LOGSYS

______________________________________________________________
SAP AG 18

SAP System ______________________________________________________________

LIKP LIKP BUS2015 BUS2015 3.

DELIVERYCHANGE SPLITDECENTRAL CONFIRMDECENTRAL DELIVERYCHANGE

LOGSYS LOGSYS LOGSYS LOGSYS

Change the filter criteria in the relevant distribution model for each of the methods mentioned above. a) b) Maintain the distribution model and distribute the views (see also: Maintain Distribution Model and Distribute Views) Create a new filter group containing the following values: Logical System = Enter the logical ERP system Warehouse number = Do not enter a value

Because no distribution model exists yet, the distribution model can be generated automatically using the Customizing activity Generate Distribution Model. The filter for the above method are generated automatically, as described above. Effects on Customizing Maintain the distribution model in the Implementation Guide. To do this, from Customizing choose: SAP Web Application Server --> Application Link Enabling (ALE) --> Modelling and Implementing Business Processes --> Maintain Distribution Model and Distribute Views.

17.3.2.2 Subsequent Changes to the Delivery (New)


Use As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), in inbound and outbound deliveries, you can subsequently change certain data after it has been distributed by the central Enterprise Resource Planning system (ERP system) to the decentralized Warehouse Management System (WMS). You can make these changes in either the central or decentralized system. The interface between the systems performs a subsequent change in the partner system for the following delivery data that is planned for a comparison: o Changes to the inbound delivery header data o Gross and net weight Volume Delivery date Door Delete delivery (only using the interface) External identification

Changes to the inbound delivery item data Gross and net weight

______________________________________________________________
SAP AG 19

SAP System ______________________________________________________________

Volume Expiration date Delivery quantity Delete delivery item (only using the interface)

Changes to the outbound delivery header data Gross and net weight Volume Delivery date Door Delete delivery (only using the interface) Incoterms Route Shipping condition Delivery priority Unloading point Picking date Loading date Shipment date Goods issue date

Changes to the outbound delivery item data Gross and net weight Volume Delivery quantity Delete delivery item (only using the interface)

Changes to the partner data for inbound and outbound deliveries Delete or change a partner from a partner role Change a partner's address

Effects on Customizing If you have not yet generated a distribution model for inbound and outbound deliveries, you create this distribution model in Customizing under Logistics -> Logistics Execution -> Decentralized WMS Integration -> Central Processing -> Distribution -> Generate Distribution Model. Here you set the Use change management for inbound and outbound deliveries indicator. If the distribution model for inbound and outbound deliveries already exists, enter the following methods in the central system manually into the distribution model using ALE Customizing:

______________________________________________________________
SAP AG 20

SAP System ______________________________________________________________

o o

InboundDelivery.DeliveryChange OutboundDelivery.DeliveryChange

You also set the filter for recipient determination for these methods: o o From the central system to the decentralized system, recipient determination takes place using the warehouse number filter. From the decentralized system to the central system, you can use the logical system filter for recipient determination if both systems have a release status of SAP R/3 Enterprise.

You then generate the partner profile for the new methods, and distribute the distribution model to the connected decentralized WMS. Within the decentralized WMS, a blocking concept must be introduced to ensure that you cannot process the delivery simultaneously in both systems. To implement this, choose in Customizing Logistics -> Logistics Execution -> Decentralized WMS Integration -> Central Processing -> Distribution Model -> Activate Cross-System Lock. See also For more information on the cross-system lock, see the SAP Library under Basis -> Client-Server Technology -> Cross-System Lock (CSL).

17.4 LE-WM

Warehouse Management

17.4.1 Business Add-Ins for Logistics Execution (new)


Use As of SAP R/3 Enterprise 4.70 (SAP_APPL 470) Business Add-Ins (BAdIs) are available in Logistics Execution in the following areas: o o o o Warehouse Management Shipping Transportation Mobile Data Entry

Effects on Customizing To activate the Business Add-In, you have to create an active implementation. To do so, go to the Customizing for Logistics Execution, and choose o Warehouse Management -> System Modifications -> Business Add-Ins in Warehouse Management -> Business Add-In for Determining Quant Business Add-In for Determining Storage Type

______________________________________________________________
SAP AG 21

SAP System ______________________________________________________________

Business Add-In for Determining Storage Unit Type Business Add-In for Entering Inventory Data in Inventory Management

Shipping -> System Modifications -> Business Add-Ins in Shipping Business Add-In for Delivery Processing Business Add-In for Price Determination in the Delivery Business Add-In for Subsequent Outbound Delivery Split Business Add-In for Posting Goods Movements Business Add-In for Additional Header Detail Screen in Delivery Transaction Business Add-In for Additional Item Detail Screen in Transaction Business Add-In for Additional Overview Screen in Delivery Transaction Business Add-Ins in Transportation

Transportation --> System Modifications --> -

Business Add-In for Checks when Creating a Shipment Cost Document Business Add-In for Creating a Shipment Cost Document Business Add-In for Shipment Cost Account Assignment Business Add-In for Checks During Shipment Cost Processing Business Add-In for Transferring Shipment Cost Items Business Add-In for Saving Shipment Cost Documents

Mobile Data Entry -> System Modifications -> Business Add-Ins in Mobile Data Entry Business Add-In for Queue Determination

17.4.2 Changes to the Structure in the Logistics Execution IMG


Use As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the R/2-R/3 link in the area of Logistics Execution no longer exists, because the system no longer supports migration from R/2 to SAP R/3 Enterprise. The following activities have been removed from Logistics Information in the implementation guide (IMG): Deleted nodes under Warehouse Management: o Define Decentralized Link to R/2

Deleted nodes under Shipping: o o o R/2-R/3 Link Define Indicator for Communication Define Mail Control

______________________________________________________________
SAP AG 22

SAP System ______________________________________________________________

o o o o o o

Define Conversion of Customer Numbers R/2-R/3 Define Number Ranges for Decentralized Deliveries Check Delivery Types and Item Categories Define Output for Communication Define Transfer of Texts Define Batch Check by Delivery Item

SAP recommend migrating from R/2 to R/3 release 4.6C.

17.4.3 Delayed Update of Outbound Delivery (New)


Use As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can delay updating the source outbound delivery following confirmation of transfer orders (TOs). By using this function, you avoid lock problems when you confirm transfer orders for outbound deliveries and update the outbound delivery data correspondingly. This function also improves system performance because the system does not process and lock the entire outbound delivery every time you confirm a transfer order item. You can update the outbound delivery at the following times: o The system transfers the confirmation data to the source outbound delivery immediately every time you confirm a transfer order item. In this case, the delayed update of the outbound delivery is not active. The system transfers the confirmation data to the outbound delivery as soon as all of the items of a transfer order have been confirmed. The system transfers the confirmation data to the outbound delivery as soon as all of the transfer orders that were created for one outbound delivery have been confirmed. This type of update is not designed for TOs for multiple deliveries. For TOs for multiple deliveries, make sure that the system transfers the confirmation data to the outbound delivery as soon as all of the items of the TO have been confirmed.

o o

Effects on Customizing You activate the delayed update of the outbound delivery in the Customizing for Warehouse Management under Interfaces -> Shipping -> Define Shipping Control -> Shipping Control per Warehouse Number with the indicator Late Delivery Update. A Business Add-In for Influencing the Late Update of Deliveries is also available in the Customizing for Warehouse Management under System Modifications -> Business Add-Ins in Warehouse Management. You can use this to specify exactly when you want to update an outbound delivery at a later time.

______________________________________________________________
SAP AG 23

SAP System ______________________________________________________________

17.4.4 LE-WM-TFM

Stock Movements

17.4.4.1 Business Add-Ins for Logistics Execution (new)


Use As of SAP R/3 Enterprise 4.70 (SAP_APPL 470) Business Add-Ins (BAdIs) are available in Logistics Execution in the following areas: o o o o Warehouse Management Shipping Transportation Mobile Data Entry

Effects on Customizing To activate the Business Add-In, you have to create an active implementation. To do so, go to the Customizing for Logistics Execution, and choose o Warehouse Management -> System Modifications -> Business Add-Ins in Warehouse Management -> o Business Add-In for Determining Quant Business Add-In for Determining Storage Type Business Add-In for Determining Storage Unit Type Business Add-In for Entering Inventory Data in Inventory Management

Shipping -> System Modifications -> Business Add-Ins in Shipping Business Add-In for Delivery Processing Business Add-In for Price Determination in the Delivery Business Add-In for Subsequent Outbound Delivery Split Business Add-In for Posting Goods Movements Business Add-In for Additional Header Detail Screen in Delivery Transaction Business Add-In for Additional Item Detail Screen in Transaction Business Add-In for Additional Overview Screen in Delivery Transaction Business Add-Ins in Transportation

Transportation --> System Modifications --> -

Business Add-In for Checks when Creating a Shipment Cost Document Business Add-In for Creating a Shipment Cost Document Business Add-In for Shipment Cost Account Assignment Business Add-In for Checks During Shipment Cost Processing Business Add-In for Transferring Shipment Cost Items

______________________________________________________________
SAP AG 24

SAP System ______________________________________________________________

Business Add-In for Saving Shipment Cost Documents

Mobile Data Entry -> System Modifications -> Business Add-Ins in Mobile Data Entry Business Add-In for Queue Determination

17.4.4.2 Transfer Order for Multiple Outbound Deliveries (New)


Use As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can create a transfer order (TO) for multiple outbound deliveries. You use transfer orders for multiple deliveries in particular if you want to process a number of outbound deliveries of the same material each with only one, or only a few outbound delivery items. The individual items in the transfer order are based on different outbound deliveries. You can also use a transfer order for multiple deliveries to optimize routes in the warehouse by grouping together material items from different outbound deliveries, which are stored close together. You create a TO for multiple deliveries o With function module L_TO_CREATE_DN_MULTIPLE Using this function module, you select the outbound deliveries and then create a cross-delivery TO directly for the selected outbound deliveries. For a group of outbound deliveries via the transaction Create Transfer Order for Multiple Orders (LT0S). To do this, choose Logistics -> Logistics Execution -> Outbound Process -> Goods Issue for Outbound Delivery -> Picking -> Create Transfer Order -> For multiple deliveries.

After you have created a transfer order for multiple deliveries, you can split it into smaller transfer orders according to certain criteria (for example, volume, weight, or TO items), so that these smaller transfer orders can be processed by several pickers. To do this, use user exit MWMTO012. The system supports the same functions for transfer orders for multiple deliveries as for regular transfer orders.

17.4.4.3 Delayed Update of Outbound Delivery (New)


Use As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can delay updating the source outbound delivery following confirmation of transfer orders (TOs). By using this function, you avoid lock problems when you confirm transfer orders for outbound deliveries and update the outbound delivery data correspondingly. This function also improves

______________________________________________________________
SAP AG 25

SAP System ______________________________________________________________

system performance because the system does not process and lock the entire outbound delivery every time you confirm a transfer order item. You can update the outbound delivery at the following times: o The system transfers the confirmation data to the source outbound delivery immediately every time you confirm a transfer order item. In this case, the delayed update of the outbound delivery is not active. The system transfers the confirmation data to the outbound delivery as soon as all of the items of a transfer order have been confirmed. The system transfers the confirmation data to the outbound delivery as soon as all of the transfer orders that were created for one outbound delivery have been confirmed. This type of update is not designed for TOs for multiple deliveries. For TOs for multiple deliveries, make sure that the system transfers the confirmation data to the outbound delivery as soon as all of the items of the TO have been confirmed.

o o

Effects on Customizing You activate the delayed update of the outbound delivery in the Customizing for Warehouse Management under Interfaces -> Shipping -> Define Shipping Control -> Shipping Control per Warehouse Number with the indicator Late Delivery Update. A Business Add-In for Influencing the Late Update of Deliveries is also available in the Customizing for Warehouse Management under System Modifications -> Business Add-Ins in Warehouse Management. You can use this to specify exactly when you want to update an outbound delivery at a later time.

17.4.5 LE-WM-BIN

Inventory at the Storage Bin Level

17.4.5.1 Business Add-Ins for Logistics Execution (new)


Use As of SAP R/3 Enterprise 4.70 (SAP_APPL 470) Business Add-Ins (BAdIs) are available in Logistics Execution in the following areas: o o o o Warehouse Management Shipping Transportation Mobile Data Entry

Effects on Customizing To activate the Business Add-In, you have to create an active implementation. To do so, go to the Customizing for Logistics Execution, and choose o Warehouse Management -> System Modifications -> Business Add-Ins in Warehouse Management ->

______________________________________________________________
SAP AG 26

SAP System ______________________________________________________________

Business Add-In for Determining Quant Business Add-In for Determining Storage Type Business Add-In for Determining Storage Unit Type Business Add-In for Entering Inventory Data in Inventory Management

Shipping -> System Modifications -> Business Add-Ins in Shipping Business Add-In for Delivery Processing Business Add-In for Price Determination in the Delivery Business Add-In for Subsequent Outbound Delivery Split Business Add-In for Posting Goods Movements Business Add-In for Additional Header Detail Screen in Delivery Transaction Business Add-In for Additional Item Detail Screen in Transaction Business Add-In for Additional Overview Screen in Delivery Transaction Business Add-Ins in Transportation

Transportation --> System Modifications --> -

Business Add-In for Checks when Creating a Shipment Cost Document Business Add-In for Creating a Shipment Cost Document Business Add-In for Shipment Cost Account Assignment Business Add-In for Checks During Shipment Cost Processing Business Add-In for Transferring Shipment Cost Items Business Add-In for Saving Shipment Cost Documents

Mobile Data Entry -> System Modifications -> Business Add-Ins in Mobile Data Entry Business Add-In for Queue Determination

17.4.6 LE-WM-STU

Storage Unit Management

17.4.6.1 Stock Overview for SU-Managed Bulk Storage (Changed)


Use To calculate the current stock overview in storage unit managed (SU-managed) bulk storage, the system reads all of the open transfer orders (TOs) for the corresponding bulk storage type. On the basis of these TOs, the system balances out the stock level in the source storage type and the destination storage type at totals level. As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the system calculates the current stock situation based on dummy quants, which are derived from the open transfer orders for the storage type. These dummy quants only exist for the purpose of correctly calculating the stock level in the

______________________________________________________________
SAP AG 27

SAP System ______________________________________________________________

particular storage type. The system does not save dummy quants in the database; they are only available for a short time for internal system calculations. For an overview of the material stocks, choose Logistics -> Logistics Execution -> Internal Warehouse Processes -> Bins and Stock -> Display -> Bin Stock per Material or Total Stock per Material (Warehouse Management) In the detail overview per storage type, the quantity available per quant is not shown in the standard system because the system cannot assign a particular quant for removal from storage to the stock removal TO in advance in SU-managed bulk storage. However, you can display the stock overview per quant based on a list variant. Make sure that in the system o o The available quantity per dummy quant corresponds to a negative quant The available quantity per quant corresponds to the current total quantity of this quant, in SU-managed bulk storage.

If you display the quant data from the stock overview, make sure o o That the system does not display dummy quants as these do not exist in the database That the system displays the quantity to be removed in the destination quantity for SU-managed bulk storage.

17.4.7 LE-WM-IFC

Interfaces

17.4.7.1 Links Between IDoc and Business Object (New)


Use As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the system stores the link between the IDoc and corresponding business object on receipt of the IDoc. This makes it possible to display the corresponding business object from the IDoc with detailed data. You can also display the IDoc from the business object. The following message types are linked with the following business objects: Message Type WMCATO WMTOCO WMTORD WMINVE WMPIHU WMSUMO WMTREQ Business Object Transfer order Transfer order Transfer order Physical inventory document Transfer order Transfer order Transfer requirement

Effects on Data Transfer

______________________________________________________________
SAP AG 28

SAP System ______________________________________________________________

The links are only created for new IDocs. No links are made for IDocs that existed before the release upgrade, nor can these be linked in retrospect.

17.4.8 LE-WM-GF

Other Functions

17.4.8.1 Delayed Update of Outbound Delivery (New)


Use As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can delay updating the source outbound delivery following confirmation of transfer orders (TOs). By using this function, you avoid lock problems when you confirm transfer orders for outbound deliveries and update the outbound delivery data correspondingly. This function also improves system performance because the system does not process and lock the entire outbound delivery every time you confirm a transfer order item. You can update the outbound delivery at the following times: o The system transfers the confirmation data to the source outbound delivery immediately every time you confirm a transfer order item. In this case, the delayed update of the outbound delivery is not active. The system transfers the confirmation data to the outbound delivery as soon as all of the items of a transfer order have been confirmed. The system transfers the confirmation data to the outbound delivery as soon as all of the transfer orders that were created for one outbound delivery have been confirmed. This type of update is not designed for TOs for multiple deliveries. For TOs for multiple deliveries, make sure that the system transfers the confirmation data to the outbound delivery as soon as all of the items of the TO have been confirmed.

o o

Effects on Customizing You activate the delayed update of the outbound delivery in the Customizing for Warehouse Management under Interfaces -> Shipping -> Define Shipping Control -> Shipping Control per Warehouse Number with the indicator Late Delivery Update. A Business Add-In for Influencing the Late Update of Deliveries is also available in the Customizing for Warehouse Management under System Modifications -> Business Add-Ins in Warehouse Management. You can use this to specify exactly when you want to update an outbound delivery at a later time.

17.4.9 LE-WM-CD

Cross-Docking

17.4.9.1 Cross-Docking (LE-WM-CD)

______________________________________________________________
SAP AG 29

SAP System ______________________________________________________________

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 -> Warehouse Management - Cross-Docking: o o General warehouse level settings, including the cross-docking storage type, outbound document release and latest release times, and FIFO tolerance duration. 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.

______________________________________________________________
SAP AG 30

SAP System ______________________________________________________________

See also o o IMG for Logistics Execution -> Warehouse Management -> Cross-Docking SAP Library for Logistics Execution -> Warehouse Management -> Cross-Docking

17.4.10 LE-WM-VAS

Value-Added Services

17.4.10.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 o VAS with handling unit (HU) changes, such as gift wrapping two materials 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 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.

______________________________________________________________
SAP AG 31

SAP System ______________________________________________________________

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 o o General settings, such as VAS warehouse settings, work centers and VAS order number ranges Settings for VAS template determination Presentation device settings, including the menu catalog and menu tree

You also have the option of doing the following: o o o Personalizing the way in which data is presented on resource presentation devices, such as defining function code profiles and pushbuttons Personalizing the monitor and alert monitor Implementing project-specific logic via Business Add-Ins

See also o o IMG for Logistics Execution -> Warehouse Management -> Value-Added Services SAP Library for Logistics Execution -> Warehouse Management -> Value-Added Services

17.4.10.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 o Create new display profiles, including template screens, sub-screens and their respective environments. Perform analyses regarding screen compression and overlapping of lines and columns before

______________________________________________________________
SAP AG 32

SAP System ______________________________________________________________

creating new screens o o o Delete fields from screens Generate all new screens at once 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 o o SAP Library for Logistics Execution -> Task and Resource Management SAP Library for Logistics Execution -> Yard Management SAP Library for Logistics Execution -> Warehouse Management -> Value-Added Services

17.4.11 LE-WM-DCC 17.4.11.1 DCC (LE-WM-DCC)


Use

Dynamic Cycle Counting

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 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

______________________________________________________________
SAP AG 33

SAP System ______________________________________________________________

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. 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.

3.

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 o o o o Addition of the Material field below the Storage Bin field in the initial selection screen The More pushbutton replaces the DISU pushbutton Addition of the DelDoc pushbutton Addition of various message screens 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

17.5 LE-YM
17.5.1 Yard Management (LE-YM)

Yard Management

______________________________________________________________
SAP AG 34

SAP System ______________________________________________________________

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 o o o o Check-in and check-out of vehicles Scheduling of doors and staging areas for vehicles (manually or based on the system's automatic scheduling mechanism) Creation and execution of movements in the yard (manually or based on the system's location determination mechanism) Creation and execution of operations in the yard, such as weighing and sealing/un-sealing of vehicles 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.

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

______________________________________________________________
SAP AG 35

SAP System ______________________________________________________________

situations o o o The yard map, including doors, staging areas and yard locations Settings, such as scheduling profiles, to enable location determination and scheduling 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 Personalizing the way in which data is presented on resource presentation devices, such as defining function code profiles and pushbuttons Personalizing the monitor and alert monitor Implementing project-specific logic via Business Add-Ins

o o o

See also o o IMG for Logistics Execution -> Yard Management SAP Library for Logistics Execution -> Yard Management

17.5.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 o o o o Create new display profiles, including template screens, sub-screens and their respective environments. Perform analyses regarding screen compression and overlapping of lines and columns before creating new screens Delete fields from screens Generate all new screens at once Manually edit new screens individually

The tool significantly reduces the effort required for screen size adjustment.

______________________________________________________________
SAP AG 36

SAP System ______________________________________________________________

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 o o SAP Library for Logistics Execution -> Task and Resource Management SAP Library for Logistics Execution -> Yard Management SAP Library for Logistics Execution -> Warehouse Management -> Value-Added Services

17.6 LE-TRM

Task & Resource Management

17.6.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 o o Node as an option in the ECO type field Handling Unit Type as an option in the Constraint field A list of handling unit types in the Constr.ob field

______________________________________________________________
SAP AG 37

SAP System ______________________________________________________________

See also IMG for Logistics Execution -> Task and Resource Management

17.6.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 o IMG for Logistics Execution -> Task and Resource Management SAP Library for Logistics Execution -> Task and Resource Management

17.6.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 o Planning the number and types of warehouse resources needed at any given time, based on expected workload Assessing the performance of the warehouse as a whole

______________________________________________________________
SAP AG 38

SAP System ______________________________________________________________

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 o IMG for Logistics Execution -> Task and Resource Management SAP Library for Logistics Execution -> Task and Resource Management

17.6.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 o o o o Create new display profiles, including template screens, sub-screens and their respective environments. Perform analyses regarding screen compression and overlapping of lines and columns before creating new screens Delete fields from screens Generate all new screens at once 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 o o SAP Library for Logistics Execution -> Task and Resource Management SAP Library for Logistics Execution -> Yard Management SAP Library for Logistics Execution -> Warehouse Management -> Value-Added Services

______________________________________________________________
SAP AG 39

SAP System ______________________________________________________________

17.7 LE-SHP

Shipping

17.7.1 Changes to the Structure in the Logistics Execution IMG


Use As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the R/2-R/3 link in the area of Logistics Execution no longer exists, because the system no longer supports migration from R/2 to SAP R/3 Enterprise. The following activities have been removed from Logistics Information in the implementation guide (IMG): Deleted nodes under Warehouse Management: o Define Decentralized Link to R/2

Deleted nodes under Shipping: o o o o o o o o o R/2-R/3 Link Define Indicator for Communication Define Mail Control Define Conversion of Customer Numbers R/2-R/3 Define Number Ranges for Decentralized Deliveries Check Delivery Types and Item Categories Define Output for Communication Define Transfer of Texts Define Batch Check by Delivery Item

SAP recommend migrating from R/2 to R/3 release 4.6C.

17.7.2 LE-SHP-DL

Delivery Processing

17.7.2.1 Business Add-Ins for Logistics Execution (new)


Use As of SAP R/3 Enterprise 4.70 (SAP_APPL 470) Business Add-Ins (BAdIs) are available in Logistics Execution in the following areas: o o o o Warehouse Management Shipping Transportation Mobile Data Entry

______________________________________________________________
SAP AG 40

SAP System ______________________________________________________________

Effects on Customizing To activate the Business Add-In, you have to create an active implementation. To do so, go to the Customizing for Logistics Execution, and choose o Warehouse Management -> System Modifications -> Business Add-Ins in Warehouse Management -> o Business Add-In for Determining Quant Business Add-In for Determining Storage Type Business Add-In for Determining Storage Unit Type Business Add-In for Entering Inventory Data in Inventory Management

Shipping -> System Modifications -> Business Add-Ins in Shipping Business Add-In for Delivery Processing Business Add-In for Price Determination in the Delivery Business Add-In for Subsequent Outbound Delivery Split Business Add-In for Posting Goods Movements Business Add-In for Additional Header Detail Screen in Delivery Transaction Business Add-In for Additional Item Detail Screen in Transaction Business Add-In for Additional Overview Screen in Delivery Transaction Business Add-Ins in Transportation

Transportation --> System Modifications --> -

Business Add-In for Checks when Creating a Shipment Cost Document Business Add-In for Creating a Shipment Cost Document Business Add-In for Shipment Cost Account Assignment Business Add-In for Checks During Shipment Cost Processing Business Add-In for Transferring Shipment Cost Items Business Add-In for Saving Shipment Cost Documents

Mobile Data Entry -> System Modifications -> Business Add-Ins in Mobile Data Entry Business Add-In for Queue Determination

17.7.2.2 Conversion of Matchcode Objects in Delivery Processing


Use For delivery documents, both document data and special database tables are updated, that allow for effective access to deliveries in various stages of processing. Until now, the function of matchcode objects has been used for these tables. As of SAP R/3 Enterprise Core 4.70

______________________________________________________________
SAP AG 41

SAP System ______________________________________________________________

(SAP_APPL 470) , this function is no longer available. The previous tables for the matchcode pools for deliveries will be replaced by new transparent tables and views. The transparent tables are automatically updated during normal delivery processing. The following relationship exists between matchcode tables and the new tables or views: Matchcode Tab. New Object Type Outbound Deliveries M_VMVLASHP_IDX_GDSI Table M_VMVLBSHP_IDX_PICK Table M_VMVLCSHP_IDX_GDSI Table M_VMVLD SHP_IDX_CREDTable checks M_VMVLI SHP_IDX_EXOB Table identification Inbound Deliveries M_VMVMA SHP_IDX_EXIB Table M_VMVMB SHP_VIEW_TRAI View identification M_VMVMC SHP_VIEW_BOLN View M_VMVMD SHP_IDX_EXIB Table identification M_VMVME SHP_IDX_GDRC Table M_VMVMF SHP_IDX_PUTATable Rough Goods Receipts M_VMVG SHP_IDX_ROGR Table Effects on Existing Data The entries in the previous matchcode tables will be automatically copied into the new tables (index tables) when you upgrade to SAP R/3 Enterprise Core 4.70 (SAP_APPL 470). If, in your subsequent productive system, you need to correct the entries in the index tables, you must use the RLE_SHP_IDX_TABLE_MAINTAIN reoprt. The matchcode objects VMVL (outbound deliveries), VMVM (inbound deliveries), and VMVG (rough goods receipts) are deleted after the data transfer during the upgrade, along with the corresponding objects (matchcode IDs, matchcode tables). You should therefore check your programs to see if any of these objects are used, and should replace these according to the above procedure. Because the new tables and views contain at least the same fields as the previous tables, for programs, you normally only need to adjust the SELECT links to matchcode tables and the data definition of the target table or target structure for these links. Any modifications to the matchcode objects are lost during the upgrade. Effects on System Administration You can use the RLE_SHP_IDX_TABLE_MAINTAIN report to analyze the data status in the index tables, and to correct it where necessary. Contents Outbound Outbound Outbound Outbound deliveries: deliveries: deliveries: deliveries: Not posted for GI Not picked Not posted for GI After credit

Outbound deliveries: External

Inbound deliveries: Initiating document Inbound deliveries: Shipment Inbound deliveries: Tracking number Inbound deliveries: External Inbound deliveries: Not posted for GR Inbound deliveries: Not putaway Rough goods receipts for vendor

______________________________________________________________
SAP AG 42

SAP System ______________________________________________________________

See also Release Note for matchcode conversion.

17.7.2.3 Partial Goods Receipt for Inbound Delivery (New)


Use As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you have the option of posting partial goods receipts for inbound deliveries. For goods movement-relevant inbound deliveries, you can make goods receipt postings using the confirmation of putaway from one or more transfer orders. You can perform a partial goods receipt posting for an inbound delivery using the following procedures: 1. 2. Creating and confirming several transfer orders Step-by-step confirmation of a transfer order, in other words, you only post a part of the items or quantities.

You can display the individual partial goods receipts in the document flow of the inbound delivery using the relevant number of the existing material documents. In addition, you can cancel partial goods receipts that have already been posted, at material document level. You can cancel single material documents or all material documents. You cannot cancel partial quantities within the material document items. Instead you can only cancel the complete document created and then return transfer the quantities again.

17.7.3 LE-SHP-GI

Goods Issue

17.7.3.1 Business Add-Ins for Logistics Execution (new)


Use As of SAP R/3 Enterprise 4.70 (SAP_APPL 470) Business Add-Ins (BAdIs) are available in Logistics Execution in the following areas: o o o o Warehouse Management Shipping Transportation Mobile Data Entry

Effects on Customizing To activate the Business Add-In, you have to create an active implementation. To do so, go to the Customizing for Logistics Execution, and choose

______________________________________________________________
SAP AG 43

SAP System ______________________________________________________________

Warehouse Management -> System Modifications -> Business Add-Ins in Warehouse Management -> Business Add-In for Determining Quant Business Add-In for Determining Storage Type Business Add-In for Determining Storage Unit Type Business Add-In for Entering Inventory Data in Inventory Management

Shipping -> System Modifications -> Business Add-Ins in Shipping Business Add-In for Delivery Processing Business Add-In for Price Determination in the Delivery Business Add-In for Subsequent Outbound Delivery Split Business Add-In for Posting Goods Movements Business Add-In for Additional Header Detail Screen in Delivery Transaction Business Add-In for Additional Item Detail Screen in Transaction Business Add-In for Additional Overview Screen in Delivery Transaction Business Add-Ins in Transportation

Transportation --> System Modifications --> -

Business Add-In for Checks when Creating a Shipment Cost Document Business Add-In for Creating a Shipment Cost Document Business Add-In for Shipment Cost Account Assignment Business Add-In for Checks During Shipment Cost Processing Business Add-In for Transferring Shipment Cost Items Business Add-In for Saving Shipment Cost Documents

Mobile Data Entry -> System Modifications -> Business Add-Ins in Mobile Data Entry Business Add-In for Queue Determination

17.8 LE-TRA
17.8.1 LE-TRA-FC

Transportation
Freight Processing

17.8.1.1 Business Add-Ins for Logistics Execution (new)


Use As of SAP R/3 Enterprise 4.70 (SAP_APPL 470) Business Add-Ins (BAdIs) are available in

______________________________________________________________
SAP AG 44

SAP System ______________________________________________________________

Logistics Execution in the following areas: o o o o Warehouse Management Shipping Transportation Mobile Data Entry

Effects on Customizing To activate the Business Add-In, you have to create an active implementation. To do so, go to the Customizing for Logistics Execution, and choose o Warehouse Management -> System Modifications -> Business Add-Ins in Warehouse Management -> o Business Add-In for Determining Quant Business Add-In for Determining Storage Type Business Add-In for Determining Storage Unit Type Business Add-In for Entering Inventory Data in Inventory Management

Shipping -> System Modifications -> Business Add-Ins in Shipping Business Add-In for Delivery Processing Business Add-In for Price Determination in the Delivery Business Add-In for Subsequent Outbound Delivery Split Business Add-In for Posting Goods Movements Business Add-In for Additional Header Detail Screen in Delivery Transaction Business Add-In for Additional Item Detail Screen in Transaction Business Add-In for Additional Overview Screen in Delivery Transaction Business Add-Ins in Transportation

Transportation --> System Modifications --> -

Business Add-In for Checks when Creating a Shipment Cost Document Business Add-In for Creating a Shipment Cost Document Business Add-In for Shipment Cost Account Assignment Business Add-In for Checks During Shipment Cost Processing Business Add-In for Transferring Shipment Cost Items Business Add-In for Saving Shipment Cost Documents

Mobile Data Entry -> System Modifications -> Business Add-Ins in Mobile Data Entry Business Add-In for Queue Determination

______________________________________________________________
SAP AG 45

SAP System ______________________________________________________________

17.8.1.2 Direct Navigation from the Shipment Cost Document to the Reference Document.
Use When you create, change, and display a shipment cost document (transactions VI01, VI02, VI03), you can access the reference document directly by double-clicking on it.

______________________________________________________________
SAP AG 46