LE Logistics Execution: SAP R/3 Enterprise

LE Logistics Execution
SAP R/3 Enterprise

Release 4.70
Release Notes
Copyright 2002 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
______________________________________________________________
14
14.1
14.1.1
14.2
14.2.1
14.2.1.1
14.2.1.2
14.2.2
14.2.2.1
14.2.2.2
14.3
14.3.1
14.3.2
14.3.3
14.3.4
14.3.4.1
14.3.4.2
14.3.4.3
14.3.5
14.3.5.1
14.3.6
14.3.6.1
14.3.7
14.3.7.1
LE Logistics
Execution
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
Execution (new)
Changes to the Structure in the
Logistics Execution IMG
Delayed Update of Outbound Delivery
(New)
LE-WM-TFM Stock Movements
Execution (new)
Transfer Order for Multiple Outbound
Deliveries (New)
(New)
LE-WM-BIN Inventory at the
Storage Bin Level
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
1
1
1
2
2
9
9
10
10
11
12
13
14
14
15
15
______________________________________________________________
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
14.3.7.2
14.3.8
14.3.8.1
14.4
14.4.1
14.5
14.5.1
14.5.2
14.5.2.1
14.5.2.2
14.5.2.3
14.5.3
14.5.3.1
14.6
14.6.1
14.6.1.1
14.6.1.2
(New)
Task and Resource Management (LE-TRM)
LE-WM-GF Other Functions
(New)
LE-TRM Task & Resource
Management
Task and Resource Management (LE-TRM)
LE-SHP Shipping
Changes to the Structure in the
Logistics Execution IMG
LE-SHP-DL Delivery
Processing
Execution (new)
Conversion of Matchcode Objects in
Delivery Processing
Partial Goods Receipt for Inbound
Delivery (New)
LE-SHP-GI Goods Issue
Execution (new)
LE-TRA Transportation
LE-TRA-FC Freight
Processing
Execution (new)
Direct Navigation from the Shipment Cost
Document to the Reference
15
18
18
20
20
20
22
23
23
25
25
26
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
14 LE
Logistics Execution
14.1 LE-MOB
Mobile Data Entry
14.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 Logistics
Execution in the following areas:
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
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
Transportation --> System Modifications --> Business Add-Ins in Transportation

-
Business Add-In for Checks when Creating a Shipment Cost Document
Business Add-In for Creating a Shipment Cost Document
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
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
14.2 LE-IDW
14.2.1 LE-IDW-CEN
Decentralized WMS Integration

Central Processing
14.2.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
Volume
Delivery date
Door
Delete delivery (only using the interface)
External identification
Changes to the inbound delivery item data

-
Volume
Expiration date
Delivery quantity
Delete delivery item (only using the interface)
Changes to the outbound delivery header data
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
Volume
Delivery date
Door
Incoterms
Route
Shipping condition
Delivery priority
Unloading point
Picking date
Loading date
Shipment date
Goods issue date
Changes to the outbound delivery item data

-
Volume
Delivery quantity
Changes to the partner data for inbound and outbound deliveries

-
Delete or change a partner from a partner role
Change a partner's address
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
InboundDelivery.DeliveryChange
OutboundDelivery.DeliveryChange
You also set the filter for recipient determination for these methods:
o
From the central system to the decentralized system, recipient determination takes place using the
warehouse number filter.
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
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).
14.2.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.
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 -->
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)
Distribution occurs according to your settings for the warehouse number.
b)
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
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
time of your choosing, by selecting the function 'For Distribution' in the delivery monitor (transaction
VL06).
14.2.2 LE-IDW-DEC
Local Operations
14.2.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
InboundDelivery.ConfirmDecentral
OutboundDelivery.ConfirmDecentral
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 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.
______________________________________________________________
SAP AG
SAP 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
InboundDelivery.ConfirmDecentral
OutboundDelivery.ConfirmDecentral
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: Tools -> ALE -> ALE Development -> Recipient
Determination -> Define Filter Object Type.
Add the following entry to the table
ALE Object Type
LOGSYS
Table Name
TBDLS
Field Name
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
LIKP
DELIVERYCHANGE
LOGSYS
LIKP
SPLITDECENTRAL
LOGSYS
BUS2015
CONFIRMDECENTRAL
LOGSYS
BUS2015
DELIVERYCHANGE
LOGSYS
3.
Change the filter criteria in the relevant distribution model for each of the methods mentioned
above.
a)
Maintain the distribution model and distribute the views (see also: Maintain Distribution
Model and Distribute Views)
b)
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.
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
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.
14.2.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

-
Volume
Delivery date
Door
External identification
Changes to the inbound delivery item data

-
Volume
Expiration date
Delivery quantity
Changes to the outbound delivery header data

-
Volume
Delivery date
Door
Incoterms
Route
Shipping condition
Delivery priority
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
Unloading point
Picking date
Loading date
Shipment date
Goods issue date
Changes to the outbound delivery item data

-
Volume
Delivery quantity
Changes to the partner data for inbound and outbound deliveries

-
Delete or change a partner from a partner role
Change a partner's address
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
You also set the filter for recipient determination for these methods:
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).
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
14.3 LE-WM
14.3.1 Business Add-Ins for Logistics Execution (new)

Use
o
Shipping
Transportation
Mobile Data Entry
o
->
-

-

-
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
-
14.3.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
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.
14.3.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
______________________________________________________________
SAP AG
10
SAP 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.
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.
14.3.4 LE-WM-TFM
Stock Movements
14.3.4.1 Business Add-Ins for Logistics Execution (new)

Use
o
Shipping
Transportation
Mobile Data Entry
o
->
______________________________________________________________
SAP AG
11
SAP System
______________________________________________________________

-

-
-
14.3.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
______________________________________________________________
SAP AG
12
SAP System
______________________________________________________________
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.
14.3.4.3 Delayed Update of Outbound Delivery (New)

Use
o
active.
time.
______________________________________________________________
SAP AG
13
SAP System
______________________________________________________________
14.3.5 LE-WM-BIN
Inventory at the Storage Bin Level

Use
o
Shipping
Transportation
Mobile Data Entry
o
->
-

-

-
______________________________________________________________
SAP AG
14
SAP System
______________________________________________________________
-
14.3.6 LE-WM-STU
Storage Unit Management
14.3.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 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
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
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.
______________________________________________________________
SAP AG
15
SAP System
______________________________________________________________
14.3.7 LE-WM-IFC
Interfaces
14.3.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

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.
14.3.7.2 Task and Resource Management (LE-TRM)

Use
You can use Task and Resource Management (TRM) to control and optimize the processes in the
warehouse. TRM provides the following features that supports this optimization:
Task-Resource Optimization
TRM optimizes warehouse processes by determining optimal routes and creating and prioritizing tasks to
be executed by warehouse resources.
Execution Control
TRM enables you to control the execution of tasks in predefined areas of your site, facilitating
task-resource optimization by preventing the crowding of resources.
Monitoring and Response Tools - TRM Monitor
TRM enables you to monitor all aspects of warehouse operations and invoke methods to respond to
______________________________________________________________
SAP AG
16
SAP System
______________________________________________________________
constantly changing circumstances in the warehouse.

Alerts and Exception Handling Tools - TRM Alert Monitor
TRM provides information on actual and arising problematic situations in the warehouse, and enables
you to handle exceptions.
Mobile Presentation
TRM allows you to customize the presentation of data to a resource on a variety of presentation devices.
LES and TRM work together to manage and maintain warehouse operations. However, each system
maintains a separation and has clearly defined responsibilities. LES provides the details about what
activity should be performed for which object, while TRM determines how and when the request is
executed.
To integrate TRM with WMS, you must assign WM warehouses to TRM sites and control the WM-TRM
link for transfer orders. For more information, see the following Implementation Guide (IMG) activities:
o
Logistics Execution -> Warehouse Management -> Interfaces -> Task and Resource Management
-> Assign Site.
-> Control WMS-TRM Interface for Transfer Orders.
There are also mandatory and optional settings in the IMG for Logistics Execution -> Task and Resource
Management, where you do the following:
o
Make general TRM settings, including defining the TRM sites, activities and exception reason codes
Define number ranges for requests, tasks, resources and warehouse supervisor messages
Make Resource Management settings, including defining resource types and resource element types
Maintain task critical time windows, mechanisms that facilitate the synchronization of tasks
Make Site Map Management settings, including defining TRM objects such as zones and working
areas , as well as enhancing WM objects such as storage bins, storage types and staging areas
Make settings that affect the way in which data is presented on resource presentation devices, such
as defining menus and pushbuttons
Make route-related settings
Create execution control for your sites
Make settings related to the TRM Monitor and Alert Monitor
Create user exits if desired
See also
For more information on TRM, see the SAP Library for Task & Resource Management.
______________________________________________________________
SAP AG
17
SAP System
______________________________________________________________
14.3.8 LE-WM-GF
Other Functions
14.3.8.1 Delayed Update of Outbound Delivery (New)

Use
o
active.
time.
14.4 LE-TRM
Task & Resource Management
14.4.1 Task and Resource Management (LE-TRM)

Use
You can use Task and Resource Management (TRM) to control and optimize the processes in the
warehouse. TRM provides the following features that supports this optimization:
______________________________________________________________
SAP AG
18
SAP System
______________________________________________________________
Task-Resource Optimization
TRM optimizes warehouse processes by determining optimal routes and creating and prioritizing tasks to
be executed by warehouse resources.
Execution Control
TRM enables you to control the execution of tasks in predefined areas of your site, facilitating
task-resource optimization by preventing the crowding of resources.
Monitoring and Response Tools - TRM Monitor
TRM enables you to monitor all aspects of warehouse operations and invoke methods to respond to
constantly changing circumstances in the warehouse.
Alerts and Exception Handling Tools - TRM Alert Monitor
TRM provides information on actual and arising problematic situations in the warehouse, and enables
you to handle exceptions.
Mobile Presentation
TRM allows you to customize the presentation of data to a resource on a variety of presentation devices.
LES and TRM work together to manage and maintain warehouse operations. However, each system
maintains a separation and has clearly defined responsibilities. LES provides the details about what
activity should be performed for which object, while TRM determines how and when the request is
executed.
To integrate TRM with WMS, you must assign WM warehouses to TRM sites and control the WM-TRM
link for transfer orders. For more information, see the following Implementation Guide (IMG) activities:
o
-> Assign Site.
-> Control WMS-TRM Interface for Transfer Orders.
There are also mandatory and optional settings in the IMG for Logistics Execution -> Task and Resource
Management, where you do the following:
o
Make general TRM settings, including defining the TRM sites, activities and exception reason codes
Define number ranges for requests, tasks, resources and warehouse supervisor messages
Make Resource Management settings, including defining resource types and resource element types
Maintain task critical time windows, mechanisms that facilitate the synchronization of tasks
Make Site Map Management settings, including defining TRM objects such as zones and working
areas , as well as enhancing WM objects such as storage bins, storage types and staging areas
Make settings that affect the way in which data is presented on resource presentation devices, such
as defining menus and pushbuttons
Make route-related settings
______________________________________________________________
SAP AG
19
SAP System
______________________________________________________________
Create execution control for your sites
Make settings related to the TRM Monitor and Alert Monitor
Create user exits if desired
See also
For more information on TRM, see the SAP Library for Task & Resource Management.
14.5 LE-SHP
Shipping
14.5.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
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.
______________________________________________________________
SAP AG
20
SAP System
______________________________________________________________
14.5.2 LE-SHP-DL
Delivery Processing

Use
o
Shipping
Transportation
Mobile Data Entry
o
->
-

-

-
______________________________________________________________
SAP AG
21
SAP System
______________________________________________________________
-
14.5.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_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_VMVLB SHP_IDX_PICK
Table
M_VMVLC SHP_IDX_GDSI
Table
M_VMVLDSHP_IDX_CRED
Table
M_VMVLI SHP_VIEW_EXTI
View
identification
Inbound Deliveries
M_VMVMA
(removed)
M_VMVMB
SHP_VIEW_TRAI View
identification
M_VMVMC
SHP_VIEW_BOLN View
M_VMVMD
SHP_VIEW_EXVE View
M_VMVME
SHP_IDX_GDRC Table
M_VMVMF
SHP_IDX_PUTA Table
Rough Goods Receipts
M_VMVG SHP_IDX_ROGR
Table
Contents
Outbound deliveries: Not posted for GI
Outbound deliveries: Not picked
Outbound deliveries: Not posted for GI
Outbound deliveries: After credit checks
Outbound deliveries: External
Inbound deliveries: Initiating document

Inbound deliveries: Shipment
Inbound deliveries: Tracking number
Inbound deliveries: External identification
Inbound deliveries: Not posted for GR
Inbound deliveries: Not putaway
Rough goods receipts for vendor
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.
______________________________________________________________
SAP AG
22
SAP System
______________________________________________________________
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.
See also
Release Note for matchcode conversion.
14.5.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.
Creating and confirming several transfer orders
2.
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.
14.5.3 LE-SHP-GI
Goods Issue

Use
______________________________________________________________
SAP AG
23
SAP System
______________________________________________________________
14.6 LE-TRA
Transportation
14.6.1 LE-TRA-FC
Freight Processing

Use
o
Shipping
Transportation
Mobile Data Entry
o
->
-

-

-
______________________________________________________________
SAP AG
25
SAP System
______________________________________________________________
-
14.6.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
26

LE Logistics Execution: SAP R/3 Enterprise

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LE Logistics Execution: SAP R/3 Enterprise

Uploaded by

Copyright:

Available Formats

LE Logistics Execution

SAP R/3 Enterprise

Copyright 2002 SAP AG. All rights reserved.

are registered trademarks of Informix Software

Mobile Data Entry

14.1.1 Business Add-Ins for Logistics Execution (new)

Mobile Data Entry

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

Transportation --> System Modifications --> Business Add-Ins in Transportation

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

Business Add-In for Queue Determination

Decentralized WMS Integration

14.2.1.1 Subsequent Changes to the Delivery (New)

Changes to the inbound delivery header data

Gross and net weight

Delete delivery (only using the interface)

Changes to the inbound delivery item data

Gross and net weight

Delete delivery item (only using the interface)

Changes to the outbound delivery header data

Gross and net weight

Delete delivery (only using the interface)

Goods issue date

Changes to the outbound delivery item data

Gross and net weight

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

14.2.1.2 Delayed Distribution of Inbound and Outbound Deliveries to the

Distribution occurs according to your settings for the warehouse number.

c) Distribution occurs immediately after the delivery is created.

14.2.2.1 Several ERP Systems to One Decentralized WMS

Effects on Existing Data

Unique numbers for master data in the decentralized WMS

Unique numbers for organizational units in the decentralized WMS

Unique numbers for deliveries in the decentralized WMS

Effects on System Administration

Maintain the filter object type

Assign the filter object type to a BAPI

Create a new filter group containing the following values:

14.2.2.2 Subsequent Changes to the Delivery (New)

Changes to the inbound delivery header data

Gross and net weight

Delete delivery (only using the interface)

Changes to the inbound delivery item data

Gross and net weight