LE Logistics Execution SAP R/3 Enterprise · PDF fileThe interface between the systems...

LE Logistics Execution

Release Notes

SAP R/3 EnterpriseRelease 4.70

© 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 permissionof 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 softwarevendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks ofMicrosoft Corporation.

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, andOS/400® are registered trademarks of IBM Corporation.

ORACLE® is a registered trademark of ORACLE Corporation.

INFORMIX®-OnLine for SAP and Informix® Dynamic ServerTM

are registered trademarks of Informix SoftwareIncorporated.

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 otherCitrix 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 andimplemented 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 AGin Germany and in several other countries all over the world. All other products mentioned are trademarks or registeredtrademarks of their respective companies.

Design: SAP Communications Media

14 LE Logistics Execution 114.1 LE-MOB Mobile Data Entry 114.1.1 Business Add-Ins for Logistics Execution (new) 114.2 LE-IDW Decentralized WMS Integration 214.2.1 LE-IDW-CEN Central Processing 214.2.1.1 Subsequent Changes to the Delivery (New)14.2.1.2 Delayed Distribution of Inbound and Outbound Deliveries to the 414.2.2 LE-IDW-DEC Local Operations14.2.2.1 Several ERP Systems to One Decentralized WMS 514.2.2.2 Subsequent Changes to the Delivery (New)14.3 LE-WM Warehouse Management 914.3.1 Business Add-Ins for Logistics Execution (new) 914.3.2 Changes to the Structure in the Logistics Execution IMG 1014.3.3 Delayed Update of Outbound Delivery (New) 1014.3.4 LE-WM-TFM Stock Movements14.3.4.1 Business Add-Ins for Logistics Execution (new) 1114.3.4.2 Transfer Order for Multiple Outbound Deliveries (New) 1214.3.4.3 Delayed Update of Outbound Delivery (New) 1314.3.5 LE-WM-BIN Inventory at the Storage Bin Level 1414.3.5.1 Business Add-Ins for Logistics Execution (new) 1414.3.6 LE-WM-STU Storage Unit Management 1514.3.6.1 Stock Overview for SU-Managed Bulk Storage (Changed) 1514.3.7 LE-WM-IFC Interfaces14.3.7.1 Links Between IDoc and Business Object

SAP System Table of Contents SAP AG______________________________________________________________

______________________________________________________________SAP AG

(New) 1514.3.7.2 Task and Resource Management (LE-TRM)14.3.8 LE-WM-GF Other Functions14.3.8.1 Delayed Update of Outbound Delivery (New) 1814.4 LE-TRM Task & Resource Management 1814.4.1 Task and Resource Management (LE-TRM)14.5 LE-SHP Shipping14.5.1 Changes to the Structure in the Logistics Execution IMG 2014.5.2 LE-SHP-DL Delivery Processing 2014.5.2.1 Business Add-Ins for Logistics Execution (new) 2014.5.2.2 Conversion of Matchcode Objects in Delivery Processing 2214.5.2.3 Partial Goods Receipt for Inbound Delivery (New) 2314.5.3 LE-SHP-GI Goods Issue14.5.3.1 Business Add-Ins for Logistics Execution (new) 2314.6 LE-TRA Transportation14.6.1 LE-TRA-FC Freight Processing 2514.6.1.1 Business Add-Ins for Logistics Execution (new) 2514.6.1.2 Direct Navigation from the Shipment Cost Document to the Reference 26

SAP System Table of Contents SAP AG______________________________________________________________

______________________________________________________________SAP AG

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 LogisticsExecution in the following areas:

o Warehouse Management

o Shipping

o Transportation

o 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

o 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

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

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

o Mobile Data Entry -> System Modifications -> Business Add-Ins in Mobile Data Entry

- Business Add-In for Queue Determination

14.2 LE-IDW Decentralized WMS Integration

14.2.1 LE-IDW-CEN 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 cansubsequently change certain data after it has been distributed by the central Enterprise Resource Planningsystem (ERP system) to the decentralized Warehouse Management System (WMS). You can make thesechanges in either the central or decentralized system. The interface between the systems performs asubsequent 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

o Changes to the inbound delivery item data


- Volume

- Expiration date

- Delivery quantity

- Delete delivery item (only using the interface)

o Changes to the outbound delivery header data

______________________________________________________________SAP AG 2

SAP System______________________________________________________________


- Volume

- Delivery date

- Door


- Incoterms

- Route

- Shipping condition

- Delivery priority

- Unloading point

- Picking date

- Loading date

- Shipment date

- Goods issue date

o Changes to the outbound delivery item data


- Volume

- Delivery quantity


o 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 thisdistribution model in Customizing under Logistics -> Logistics Execution -> Decentralized WMSIntegration -> Central Processing -> Distribution -> Generate Distribution Model. Here you set the Usechange management for inbound and outbound deliveries indicator.

If the distribution model for inbound and outbound deliveries already exists, enter the following methodsin the central system manually into the distribution model using ALE Customizing:

o InboundDelivery.DeliveryChange

o 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 thewarehouse number filter.

______________________________________________________________SAP AG 3

SAP System______________________________________________________________

o From the decentralized system to the central system, you can use the logical system filter forrecipient 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 theconnected decentralized WMS.

Within the decentralized WMS, a blocking concept must be introduced to ensure that you cannot processthe 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-ServerTechnology -> Cross-System Lock (CSL).

14.2.1.2 Delayed Distribution of Inbound and Outbound Deliveries to theDecentralized Warehouse Management System (New)

Use

As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can distribute inbound and outbounddeliveries to the decentralized Warehouse Management System (WMS) with a delay. Here, you candecide as of which point the inbound or outbound delivery is staged, and can therefore be transferred tothe 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 arecreated, or with a delay.For more information, see the Implementation Guide (IMG) under Logistics Execution -->Decentralized WMS Integration --> Central Processing --> Application --> Activiate DecentralizedWMS. This setting affects all inbound and outbound deliveries that are processed in the relevantwarehouse number.

2. For the corresponding delivery type, set the distribution mode for the deliveries. The permittedmodes 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 eachdelivery type independently of the warehouse number. Note, that any settings you make hereoverwrite 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 4

SAP System______________________________________________________________

time of your choosing, by selecting the function 'For Distribution' in the delivery monitor (transactionVL06).

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 ERPsystems to one decentralized WMS. This possibility also changes the filter criteria in particular, in as faras 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


o OutboundDelivery.ConfirmDecentral


o 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 adecentralized WMS must have unique and mutually exclusive plant-storage location combinations. Youshould manage inventory for the various ERP systems at plant-storage location level, in order thatinventory differences can be ascribed to one specific ERP system. When you clear inventorydifferences, always make an additional selection using the plant-storage location. These fields can betaken from the free selection.To clear inventory differences, from the SAP menu choose: Logistics --> Logistics Execution --> InternalWhse Processes --> Physical Inventory --> In Warehouse Management --> Clear Differences -->Inventory Management.

The following prerequisites must be fulfilled if you connect several ERP systems to one decentralizedWMS:

o Unique numbers for master data in the decentralized WMSThe different customer masters, vendor masters, creditor masters, and material masters from thevarious ERP systems must have unique numbers, so that a master record can always be readexclusively on the decentralized WMS.

o Unique numbers for organizational units in the decentralized WMSThe different plants and storage locations in the decentralized WMS must have unique numbers.

o Unique numbers for deliveries in the decentralized WMSDeliveries from different ERP systems must be unique in the decentralized WMS. When youreplicate the deliveries, ensure that the deliveries are unique in the decentralized system.

______________________________________________________________SAP AG 5

SAP System______________________________________________________________

Effects on System Administration

If several ERP systems are connected to a decentralized WMS, then existing distribution models must bechanged as described below. For the following methods, the filter criteria for recipient determination arechanged as follows:

o InboundDelivery.ConfirmDecentral


o OutboundDelivery.ConfirmDecentral


o OutboundDelivery.SplitDecentral

You must perform the following activities for changing the filter criteria once only:

1. Maintain the filter object typeTo do this, from the SAP menu choose: Tools -> ALE -> ALE Development -> RecipientDetermination -> 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 BAPITo do this, from the SAP menu choose: Tools -> ALE -> ALE Development -> RecipientDetermination -> 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 mentionedabove.

a) Maintain the distribution model and distribute the views (see also: Maintain DistributionModel and Distribute Views)

b) Create a new filter group containing the following values:Logical System = Enter the logical ERP systemWarehouse number = Do not enter a value

Because no distribution model exists yet, the distribution model can be generated automatically using theCustomizing activity Generate Distribution Model.

The filter for the above method are generated automatically, as described above.


______________________________________________________________SAP AG 6

SAP System______________________________________________________________

Maintain the distribution model in the Implementation Guide. To do this, from Customizing choose: SAPWeb Application Server --> Application Link Enabling (ALE) --> Modelling and Implementing BusinessProcesses --> 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 cansubsequently change certain data after it has been distributed by the central Enterprise Resource Planningsystem (ERP system) to the decentralized Warehouse Management System (WMS). You can make thesechanges in either the central or decentralized system. The interface between the systems performs asubsequent 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

o Changes to the inbound delivery item data


- Volume

- Expiration date

- Delivery quantity


o Changes to the outbound delivery header data


- Volume

- Delivery date

- Door


- Incoterms

- Route

- Shipping condition

- Delivery priority

______________________________________________________________SAP AG 7

SAP System______________________________________________________________

- Unloading point

- Picking date

- Loading date

- Shipment date

- Goods issue date

o Changes to the outbound delivery item data


- Volume

- Delivery quantity


o 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 thisdistribution model in Customizing under Logistics -> Logistics Execution -> Decentralized WMSIntegration -> Central Processing -> Distribution -> Generate Distribution Model. Here you set the Usechange management for inbound and outbound deliveries indicator.

If the distribution model for inbound and outbound deliveries already exists, enter the following methodsin the central system manually into the distribution model using ALE Customizing:



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 thewarehouse number filter.

o From the decentralized system to the central system, you can use the logical system filter forrecipient 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 theconnected decentralized WMS.

Within the decentralized WMS, a blocking concept must be introduced to ensure that you cannot processthe 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-ServerTechnology -> Cross-System Lock (CSL).

______________________________________________________________SAP AG 8

SAP System______________________________________________________________

14.3 LE-WM Warehouse Management

14.3.1 Business Add-Ins for Logistics Execution (new)

Use



o Shipping

o Transportation

o Mobile Data Entry






















______________________________________________________________SAP AG 9

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 LogisticsExecution no longer exists, because the system no longer supports migration from R/2 to SAP R/3Enterprise. The following activities have been removed from Logistics Information in the implementationguide (IMG):

Deleted nodes under Warehouse Management:

o Define Decentralized Link to R/2

Deleted nodes under Shipping:

o R/2-R/3 Link

o Define Indicator for Communication

o Define Mail Control

o Define Conversion of Customer Numbers R/2-R/3

o Define Number Ranges for Decentralized Deliveries

o Check Delivery Types and Item Categories

o Define Output for Communication

o Define Transfer of Texts

o 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 outbounddelivery following confirmation of transfer orders (TOs).

By using this function, you avoid lock problems when you confirm transfer orders for outbounddeliveries 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 youconfirm 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 timeyou confirm a transfer order item. In this case, the delayed update of the outbound delivery is notactive.

o The system transfers the confirmation data to the outbound delivery as soon as all of the items of atransfer order have been confirmed.

o The system transfers the confirmation data to the outbound delivery as soon as all of the transferorders 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 ofthe items of the TO have been confirmed.


You activate the delayed update of the outbound delivery in the Customizing for Warehouse Managementunder Interfaces -> Shipping -> Define Shipping Control -> Shipping Control per Warehouse Numberwith the indicator Late Delivery Update.

A Business Add-In for Influencing the Late Update of Deliveries is also available in the Customizing forWarehouse Management under System Modifications -> Business Add-Ins in WarehouseManagement. You can use this to specify exactly when you want to update an outbound delivery at a latertime.

14.3.4 LE-WM-TFM Stock Movements

14.3.4.1 Business Add-Ins for Logistics Execution (new)

Use



o Shipping

o Transportation

o Mobile Data Entry





______________________________________________________________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 multipleoutbound deliveries.

You use transfer orders for multiple deliveries in particular if you want to process a number of outbounddeliveries of the same material each with only one, or only a few outbound delivery items. The individualitems 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 groupingtogether material items from different outbound deliveries, which are stored close together.

You create a TO for multiple deliveries

______________________________________________________________SAP AG 12

SAP System______________________________________________________________

o With function module L_TO_CREATE_DN_MULTIPLEUsing this function module, you select the outbound deliveries and then create a cross-delivery TOdirectly for the selected outbound deliveries.

o 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 Issuefor 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 ordersaccording to certain criteria (for example, volume, weight, or TO items), so that these smaller transferorders 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 transferorders.

14.3.4.3 Delayed Update of Outbound Delivery (New)

Use


By using this function, you avoid lock problems when you confirm transfer orders for outbounddeliveries and update the outbound delivery data correspondingly. This function also improves systemperformance because the system does not process and lock the entire outbound delivery every time youconfirm a transfer order item.








______________________________________________________________SAP AG 13

SAP System______________________________________________________________

14.3.5 LE-WM-BIN Inventory at the Storage Bin Level


Use



o Shipping

o Transportation

o Mobile Data Entry






















______________________________________________________________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 systemreads all of the open transfer orders (TOs) for the corresponding bulk storage type. On the basis of theseTOs, the system balances out the stock level in the source storage type and the destination storage type attotals level. As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the system calculates the currentstock situation based on dummy quants, which are derived from the open transfer orders for the storagetype.

These dummy quants only exist for the purpose of correctly calculating the stock level in the particularstorage type. The system does not save dummy quants in the database; they are only available for a shorttime for internal system calculations.

For an overview of the material stocks, choose Logistics -> Logistics Execution -> Internal WarehouseProcesses -> 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 standardsystem because the system cannot assign a particular quant for removal from storage to the stock removalTO in advance in SU-managed bulk storage. However, you can display the stock overview per quantbased on a list variant. Make sure that in the system

o The available quantity per dummy quant corresponds to a negative quant

o The available quantity per quant corresponds to the current total quantity of this quant, inSU-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

o That the system displays the quantity to be removed in the destination quantity for SU-managedbulk 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 andcorresponding business object on receipt of the IDoc.

This makes it possible to display the corresponding business object from the IDoc with detailed data. Youcan also display the IDoc from the business object.

The following message types are linked with the following business objects:

Message Type Business Object

WMCATO Transfer order

WMTOCO Transfer order

WMTORD Transfer order

WMINVE Physical inventory document

WMPIHU Transfer order

WMSUMO Transfer order

WMTREQ Transfer requirement

Effects on Data Transfer

The links are only created for new IDocs. No links are made for IDocs that existed before the releaseupgrade, 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 thewarehouse. 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 tobe executed by warehouse resources.

Execution Control

TRM enables you to control the execution of tasks in predefined areas of your site, facilitatingtask-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 enablesyou to handle exceptions.

Mobile PresentationTRM 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 systemmaintains a separation and has clearly defined responsibilities. LES provides the details about whatactivity should be performed for which object, while TRM determines how and when the request isexecuted.


To integrate TRM with WMS, you must assign WM warehouses to TRM sites and control the WM-TRMlink 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.

o Logistics Execution -> Warehouse Management -> Interfaces -> Task and Resource Management-> Control WMS-TRM Interface for Transfer Orders.

There are also mandatory and optional settings in the IMG for Logistics Execution -> Task and ResourceManagement, where you do the following:

o Make general TRM settings, including defining the TRM sites, activities and exception reason codes

o Define number ranges for requests, tasks, resources and warehouse supervisor messages

o Make Resource Management settings, including defining resource types and resource element types

o Maintain task critical time windows, mechanisms that facilitate the synchronization of tasks

o Make Site Map Management settings, including defining TRM objects such as zones and workingareas , as well as enhancing WM objects such as storage bins, storage types and staging areas

o Make settings that affect the way in which data is presented on resource presentation devices, suchas defining menus and pushbuttons

o Make route-related settings

o Create execution control for your sites

o Make settings related to the TRM Monitor and Alert Monitor

o 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


By using this function, you avoid lock problems when you confirm transfer orders for outbounddeliveries and update the outbound delivery data correspondingly. This function also improves systemperformance because the system does not process and lock the entire outbound delivery every time youconfirm a transfer order item.








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 thewarehouse. 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 tobe executed by warehouse resources.

Execution Control

TRM enables you to control the execution of tasks in predefined areas of your site, facilitatingtask-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 toconstantly 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 enablesyou to handle exceptions.

Mobile PresentationTRM 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 systemmaintains a separation and has clearly defined responsibilities. LES provides the details about whatactivity should be performed for which object, while TRM determines how and when the request isexecuted.


To integrate TRM with WMS, you must assign WM warehouses to TRM sites and control the WM-TRMlink 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.

o Logistics Execution -> Warehouse Management -> Interfaces -> Task and Resource Management-> Control WMS-TRM Interface for Transfer Orders.

There are also mandatory and optional settings in the IMG for Logistics Execution -> Task and ResourceManagement, where you do the following:

o Make general TRM settings, including defining the TRM sites, activities and exception reason codes

o Define number ranges for requests, tasks, resources and warehouse supervisor messages

o Make Resource Management settings, including defining resource types and resource element types

o Maintain task critical time windows, mechanisms that facilitate the synchronization of tasks

o Make Site Map Management settings, including defining TRM objects such as zones and workingareas , as well as enhancing WM objects such as storage bins, storage types and staging areas

o Make settings that affect the way in which data is presented on resource presentation devices, suchas defining menus and pushbuttons

o Make route-related settings

______________________________________________________________SAP AG 19

SAP System______________________________________________________________

o Create execution control for your sites

o Make settings related to the TRM Monitor and Alert Monitor

o 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 LogisticsExecution no longer exists, because the system no longer supports migration from R/2 to SAP R/3Enterprise. The following activities have been removed from Logistics Information in the implementationguide (IMG):

Deleted nodes under Warehouse Management:

o Define Decentralized Link to R/2

Deleted nodes under Shipping:

o R/2-R/3 Link

o Define Indicator for Communication

o Define Mail Control

o Define Conversion of Customer Numbers R/2-R/3

o Define Number Ranges for Decentralized Deliveries

o Check Delivery Types and Item Categories

o Define Output for Communication

o Define Transfer of Texts

o 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

o Transportation

o Mobile Data Entry























______________________________________________________________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 foreffective access to deliveries in various stages of processing. Until now, the function of matchcodeobjects has been used for these tables. As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) , thisfunction is no longer available.

The previous tables for the matchcode pools for deliveries will be replaced by new transparent tables andviews. 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 Contents

Outbound Deliveries

M_VMVLASHP_IDX_GDSI Table Outbound deliveries: Not posted for GI

M_VMVLBSHP_IDX_PICK Table Outbound deliveries: Not picked

M_VMVLCSHP_IDX_GDSI Table Outbound deliveries: Not posted for GI

M_VMVLDSHP_IDX_CRED Table Outbound deliveries: After credit checks

M_VMVLI SHP_VIEW_EXTI View Outbound deliveries: Externalidentification

Inbound Deliveries

M_VMVMA (removed) - Inbound deliveries: Initiating document

M_VMVMB SHP_VIEW_TRAI View Inbound deliveries: Shipmentidentification

M_VMVMC SHP_VIEW_BOLN View Inbound deliveries: Tracking number

M_VMVMD SHP_VIEW_EXVE View Inbound deliveries: External identification

M_VMVME SHP_IDX_GDRC Table Inbound deliveries: Not posted for GR

M_VMVMF SHP_IDX_PUTA Table Inbound deliveries: Not putaway

Rough Goods Receipts

M_VMVG SHP_IDX_ROGR Table Rough goods receipts for vendor

Effects on Existing Data

The entries in the previous matchcode tables will be automatically copied into the new tables (indextables) when you upgrade to SAP R/3 Enterprise Core 4.70 (SAP_APPL 470). If, in your subsequentproductive system, you need to correct the entries in the index tables, you must use theRLE_SHP_IDX_TABLE_MAINTAIN reoprt.

______________________________________________________________SAP AG 22

SAP System______________________________________________________________

The matchcode objects VMVL (outbound deliveries), VMVM (inbound deliveries), and VMVG (roughgoods receipts) are deleted after the data transfer during the upgrade, along with the correspondingobjects (matchcode IDs, matchcode tables). You should therefore check your programs to see if any ofthese objects are used, and should replace these according to the above procedure. Because the new tablesand views contain at least the same fields as the previous tables, for programs, you normally only need toadjust the SELECT links to matchcode tables and the data definition of the target table or target structurefor 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 indextables, 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 goodsreceipts for inbound deliveries. For goods movement-relevant inbound deliveries, you can make goodsreceipt 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 orquantities.

You can display the individual partial goods receipts in the document flow of the inbound delivery usingthe relevant number of the existing material documents.

In addition, you can cancel partial goods receipts that have already been posted, at material documentlevel. You can cancel single material documents or all material documents. You cannot cancel partialquantities within the material document items. Instead you can only cancel the complete documentcreated and then return transfer the quantities again.

14.5.3 LE-SHP-GI Goods Issue


Use

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

______________________________________________________________SAP AG 23

SAP System______________________________________________________________

14.6 LE-TRA Transportation

14.6.1 LE-TRA-FC Freight Processing


Use



o Shipping

o Transportation

o Mobile Data Entry





















______________________________________________________________SAP AG 25

SAP System______________________________________________________________






14.6.1.2 Direct Navigation from the Shipment Cost Document to the ReferenceDocument.

Use

When you create, change, and display a shipment cost document (transactions VI01, VI02, VI03), youcan access the reference document directly by double-clicking on it.

______________________________________________________________SAP AG 26

SAP System______________________________________________________________

LE Logistics Execution SAP R/3 Enterprise · PDF fileThe interface between the systems...

Documents

Transcript of LE Logistics Execution SAP R/3 Enterprise · PDF fileThe interface between the systems...