cg sap dsd 100 final

8/10/2019 Cg Sap Dsd 100 Final

http://slidepdf.com/reader/full/cg-sap-dsd-100-final 1/554

SAP Direct Store Delivery 1.0 Configuration Guide

PUBLICDocument Version: 1.0 – 03/13/2014



(C) SAP AG 2

Copyright© Copyright 2013 SAP AG. All rights reserved.

SAP Library document classification: PUBLIC

No part of this publication may be reproduced or transmitted in any form or for any purposewithout 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. National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for

informational purposes only, without representation or warranty of any kind, and SAP Group

shall not be liable for errors or omissions with respect to the materials. The only warranties for

SAP Group products and services are those that are set forth in the express warranty statements

accompanying such products and services, if any. Nothing herein should be construed as

constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in Germany and other countries.

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for

additional trademark information and notices.

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark






(C) SAP AG 3

Icons in Body TextIcon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of

information at a glance. For more information, see Help on Help General InformationClasses and Information Classes for Business Information Warehouse on the first page of anyversion of SAP Library .

Typographic ConventionsType Style Description

Example text Words or characters quoted from the screen. These include field names, screen

titles, pushbuttons labels, menu names, menu paths, and menu options.Cross-references to other documentation.

Example text Emphasized words or phrases in body text, graphic titles, and table titles.EXAMPLE TEXT Technical names of system objects. These include report names, program

names, transaction codes, table names, and key concepts of a programminglanguage when they are surrounded by body text, for example, SELECT andINCLUDE.

Example text Output on the screen. This includes file and directory names and their paths,messages, names of variables and parameters, source text, and names ofinstallation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the systemexactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace these words andcharacters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.



(C) SAP AG 4

Table of ContentsSAP Direct Store Delivery: Configuration ................................................................................ 11

SAP Notes ............................................................................................................................ 12 System Connections ............................................................................................................ 14

Connection of DSD Back End System to DSD Connector ............................................... 16

Define Logical Systems ................................................................................................ 17 Assign Client to Logical System ................................................................................... 18 Define RFC Destination for Back End/DSD Connector ................................................ 19 Define Port in Back End/DSD Connector ..................................................................... 21 Set Cross-System Company Codes for Global Organizational Units .......................... 24 Define ISO Codes for Currencies ................................................................................. 25 Define ISO Codes for Units of Measurement ............................................................... 26 Maintain Distribution Models and Distributing Views .................................................... 28 Define Inbound Process Code ...................................................................................... 31 Define Outbound Process Code ................................................................................... 34 Maintain Partner Profiles in Back End/DSD Connector ................................................ 36

Assign IDoc Type and Message Type .......................................................................... 43 Connection of DSD Connector to SAP Mobile Platform .................................................. 45

Define RFC Destination on DSD Connector ................................................................. 46 Maintain SAP Mobile Platform Data Connectivity......................................................... 48

Connection of SAP Mobile Platform to DSD Connector .................................................. 49 Define RFC Destination in SAP ERP for bgRFC .......................................................... 50 Define RFC Destination for Supervisor ........................................................................ 52 Maintain Inbound Destination for bgRFC ..................................................................... 54

Activate Internet Communication Services ................................................................... 55 General Parameter Value Maintenance ....................................................................... 56

Define Parameter Subjects ....................................................................................... 58 Define Parameter Keys ............................................................................................. 59

Configuration of Basic Functions ..................................................................................... 60 Activate Direct Store Delivery ....................................................................................... 61 Manage Multiple Sales Areas Processes ..................................................................... 62

Activate Vehicle Space Optimization ............................................................................ 63 Activate CRM Scenario ................................................................................................. 64

Configuration of DSD Connector Cockpit ......................................................................... 65 Link Mobile Device to Driver and Vehicle ..................................................................... 66 Display Driver Master Data ........................................................................................... 68 Display Vehicle Master Data ......................................................................................... 69

Pricing on Mobile Devices ................................................................................................ 70 Define Block Condition Types for Mobile Pricing.......................................................... 71

Configuration of Pricing Data Extractor ............................................................................ 73 Define General Settings for Pricing Data Extractor ...................................................... 74 Enhance Pricing Selection Criteria for Pricing BAdI ..................................................... 75

Handheld Connectivity ......................................................................................................... 78 SAP CRM Integration ....................................................................................................... 79

SAP ERP Settings ........................................................................................................ 80 Define RFC Destination for SAP CRM ...................................................................... 81 Maintain General Parameter Values ......................................................................... 83 Maintain Download Setting for CRM Activities.......................................................... 85

SAP CRM Settings ....................................................................................................... 86 Define RFC Destination for SAP ERP ...................................................................... 87 Maintain General Parameter Key Values .................................................................. 89 Maintain General Parameter Subject Values ............................................................ 90 Maintain General Parameter Values ......................................................................... 91 Define Transaction Types ......................................................................................... 93 Define CRM Activity Authorization ............................................................................ 95 Define CRM Activity Mass Generation Depending on Tour Scenario ...................... 97 Define Attachment Types .......................................................................................... 99 Define Activity Status of Past Activities ................................................................... 100 Define Attribute Sets ............................................................................................... 101



(C) SAP AG 5

Define Currencies ................................................................................................... 102 CRM Business Add-lns (BAdIs) .............................................................................. 103

Electronic Signature ....................................................................................................... 105 Maintain Signature Repository ................................................................................... 107 Maintain Signature Text IDs ....................................................................................... 108

Assign Signer Roles to Documents ............................................................................ 110

Define Settings for Canceling or Changing Signed Documents ................................. 116 Additional Data Download .............................................................................................. 117

Assign Rule per Tour Scenario for Additional Customers .......................................... 118 Define Route Properties for Additional Customers ..................................................... 119

General Settings ............................................................................................................. 121 Maintain Filter for Mobile Business Objects ............................................................... 122 Define Supported Processes for Download and Upload ............................................ 123 Set Up Download Process Activation ......................................................................... 124

Upload ............................................................................................................................ 126 Set Up Upload Process Sequence ............................................................................. 127 Define Allowed Route Transaction Types .................................................................. 128

Occasionally Connected Scenarios ............................................................................... 129 Define Document Settings for ATP Check and Price Determination.......................... 131

Activate Reload Proposals .......................................................................................... 133 Allow Deliveries with Different Route .......................................................................... 134 Maintain Condition Types for Online Pricing .............................................................. 135 Define Follow-up Documents for Shipments .............................................................. 136 Define Follow-up Documents for Visit Lists ................................................................ 138

Document Numbering .................................................................................................... 139 Assign Delivery Document Types to DSD Delivery Scenarios ................................... 140 Assign Sales Document Types to DSD Order Scenarios ........................................... 142 Assign Document Prefix to Collection Document Number Types .............................. 144 Assign Document Prefix to Sales Document Number Types ..................................... 145 Define Criteria for Unique Number Creation ............................................................... 147

Assign Series to Criteria for Unique Number Creation ............................................... 148 Define Last No. for Document Number Types and Criteria for Unique No. Creation . 149

Application Log Monitoring ............................................................................................. 150 Activate HTTP Service for Web Dynpro ..................................................................... 151 Define Connector Tables to Be Monitored ................................................................. 152 Define Objects for Message Log Monitoring .............................................................. 153 Define Subobjects for Message Log Monitoring ......................................................... 154

Assign Message Log Objects and Subobjects to Messages...................................... 156 Define Error Subjects and Map to SAP CRM Messages/Status ................................ 158

Vehicle Checks ............................................................................................................... 160 Maintain Catalog ID and Related Questions .............................................................. 161 Maintain Catalog Determination ................................................................................. 163

DSD Connector Settings ................................................................................................ 166 Logical System Connectivity ....................................................................................... 167

Define Mobile Engine Servers ................................................................................ 168

Maintain Destinations of Mobile Engine Server ...................................................... 169 Set Up SAP Mobile Platform or Middleware Server SAP mDSD ............................ 170 Maintain EDI Port Definitions .................................................................................. 171

Connectivity Objects ................................................................................................... 173 Define Connectivity Objects .................................................................................... 174

Assign Function Modules to Connectivity Objects .................................................. 176 Assign Message Types to Connectivity Objects ..................................................... 177

Mapping Rules ............................................................................................................ 179 Define Function Modules for Mapping .................................................................... 180 Define Mapping Rules ............................................................................................. 181

Types Assignments .................................................................................................... 187 Assign Material Types to DSD Connectivity Material Types ................................... 188 Assign Document Types to DSD Connectivity Document Types ........................... 189

Assign Invoice Document Types as Criteria for Open Items .................................. 190 Definitions of Reasons ................................................................................................ 192



(C) SAP AG 6

Define Reasons for Differences for Check-In and Check-Out ................................ 193 Define Reasons for Changing Deliveries and Orders on the DSD Connector ....... 194 Define Customer Visit Reasons .............................................................................. 196 Create Reason Types and Characteristics ............................................................. 197

Assign Reason Codes to Reason Types ................................................................ 198 Assign Tour Scenario to Reason Types ................................................................. 199

Administration of Mobile Devices ............................................................................... 200 Define Mobile Device Groups ................................................................................. 201 Define Group-Specific Roles ................................................................................... 202

Assign Group-Specific Roles to Mobile Device Groups .......................................... 204 Mobile Device Settings ............................................................................................... 205

Define Global Mobile Device Settings ..................................................................... 210 Define Group-Specific Mobile Device Settings ....................................................... 211 Define Tour Scenario Settings ................................................................................ 213 Definition of General Settings ................................................................................. 226

Define Payment Methods .................................................................................... 227 Define Expense Types ........................................................................................ 229 Define Allowed Payment/Credit Card Types ....................................................... 230

Assign Shipment/Visit Plan Types to DSD Tour Scenarios ................................ 231

Assign Delivery Document Types to DSD Delivery Scenarios............................ 232 Assign Sales Document Types to DSD Order Scenarios ................................... 234 Manual Discounts ................................................................................................ 236

Assign Condition Types for Manual Discounts ................................................ 237 Barcode Support for Recording Visit Times on Mobile Device ...................................... 239

Enable Barcode Support in Tour Scenarios ............................................................... 241 Invoice Reprint as Copy ................................................................................................. 243 Listing and Exclusion ...................................................................................................... 244

Maintain Condition Tables for Material Listing/Exclusion ........................................... 247 Maintain Access Sequences for Material Listing/Exclusion ....................................... 248 Maintain Condition Types for Material Listing/Exclusion ............................................ 250 Maintain Procedures for Material Listing/Exclusion .................................................... 251

Assign Procedures for Material Listing/Exclusion to Sales Doc. Types ..................... 253

Deal Conditions .............................................................................................................. 254 Define Deal Condition Types ...................................................................................... 256 Define Number Ranges for Deal Conditions .............................................................. 257 Define Field Selection for Deal Conditions ................................................................. 258 Define Customer Hierarchy Types for each Sales Area ............................................. 259 Define Condition Types for Deal Condition Discounts ............................................... 260

Master Data Configuration ................................................................................................. 262 Driver Master Data Configuration ................................................................................... 263

Define Driver's License Categories ............................................................................ 264 Create Number Ranges for Customer Accounts ........................................................ 265 Define Account Groups and Field Selection for Customers ....................................... 266

Assign Number Ranges to Customer Account Groups .............................................. 270 Specify Allowed Account Group for Drivers ................................................................ 271

Set Up Partner Determination for Customer Master................................................... 272 Vehicle Master Data/Fleet Objects Configuration .......................................................... 274

Define Technical Objects Types ................................................................................. 275 Define Usage Types for Fleet Objects ........................................................................ 276 Set View Profiles for Technical Objects ...................................................................... 277 Maintain Equipment Category .................................................................................... 279 Define Number Ranges .............................................................................................. 281

Assign View Profile and Equipment Categories to Fleet Object Types ...................... 282 Assign Means-of-Transportation Types to Equipment Category/Vehicle Types ........ 284

Material Master Data Configuration ............................................................................... 285 Determine Categories for Totals Fields ...................................................................... 286 Define Counting Groups ............................................................................................. 287 Define UoM Levels for Counting with Counting Groups ............................................. 288

Assign Screen Sequences.......................................................................................... 290 Visit Control Configuration ................................................................................................. 293



(C) SAP AG 7

Define Calendar Types ................................................................................................... 294 Define Visit Groups ........................................................................................................ 295 Define DSD Groupings ................................................................................................... 296 Maintain Number Ranges for Visit Plans ....................................................................... 297 Maintain Number Ranges for Visit Lists ......................................................................... 298 Define Visit Plan Types .................................................................................................. 299

Specify Allowed Sales Document Types ........................................................................ 303 Specify Allowed Transaction Types ............................................................................... 304

Assign Sales Activity Types/Outcome to Customer Visit Status .................................... 305 DSD Messaging - Text Control within Visit Control ........................................................ 307

Define Text Types for Visit Control ............................................................................. 309 Maintain Text Control for Visit Control ........................................................................ 310 Define Driver Messages ............................................................................................. 314

Transportation Planning Configuration .............................................................................. 316 Route Definition .............................................................................................................. 317

Define Modes of Transport ......................................................................................... 318 Define Shipping Types ................................................................................................ 319 Define Routes and Stages .......................................................................................... 320

Route Determination Definition ...................................................................................... 323

Define Transportation Zones ...................................................................................... 324 Maintain Country and Transportation Zones for Shipping Point................................. 325 Define Transportation Groups .................................................................................... 327 Define Weight Groups ................................................................................................ 328 Define Shipping Conditions ........................................................................................ 330 Maintain Route Determination .................................................................................... 331 Define Loading Groups ............................................................................................... 334 Maintain Transportation Relevance ............................................................................ 335 Define Shipment Types .............................................................................................. 336 Define Transportation Planning Point ......................................................................... 337 Determine Allowed Delivery Types for Dynamic Transportation Planning ................. 339 Determine Capacity Limits for Dynamic Transportation Planning .............................. 340

Loading Unit Configuration ............................................................................................. 342

Check Units of Measurement ..................................................................................... 344 Define Permissible Document Types for Order .......................................................... 346 Define Permissible Document Types for Delivery ...................................................... 347 Define Units of Measure and Tolerances ................................................................... 348 Set Unit of Measure Divisor for Loading Units............................................................ 349 Define Table for LU Groups for Material Master......................................................... 351

Download/Data Replication Configuration ......................................................................... 352 Send Customer Master Data .......................................................................................... 353 Send Material Master Data ............................................................................................. 355 Distribute Material BOM Information .............................................................................. 357 Send Credit Data (Open Items) ...................................................................................... 359 Send Driver Text Settings .............................................................................................. 361

Data Replication and Modification ..................................................................................... 363

Activate Change Pointers - Generally ............................................................................ 364 Activate Change Pointers for Message Types ............................................................... 365 Generate IDocs from Change Pointers: Defining Variants ............................................ 366 Generate IDocs from Change Pointers: Scheduling Jobs ............................................. 367 Schedule Jobs for Collected IDocs ................................................................................ 369

DSD Tour Status ................................................................................................................ 371 Define Tour Status ID ..................................................................................................... 373 Specify Function Modules Available for Tour Status Profiles ........................................ 376 Define Tour Scenarios and Tour Status Profiles ............................................................ 377 Delivery Process: Assign Shipment to the Connected Medium ..................................... 383 Delivery Process: Assign Shipment to Tour Scenario ................................................... 384 Sales Process: Assign Visit List to Connected Medium ................................................. 386 Sales Process: Assign Visit List to Tour Scenario ......................................................... 387

Route Accounting ............................................................................................................... 389 Basic Function Configuration ......................................................................................... 390



(C) SAP AG 8

Application Log Configuration ..................................................................................... 391 Maintain General Settings ....................................................................................... 392 Maintain Treatment of Message per Object ............................................................ 393

Define Route Transaction Types ................................................................................ 394 Define Distance Types ................................................................................................ 395 Define Time Types ...................................................................................................... 396

Define Payment Methods ........................................................................................... 397 Define Reasons for Differences for Check-out and Check-in ..................................... 398 Define Reasons for Changing Deliveries and Orders ................................................ 399 Define Customer Visit Reasons .................................................................................. 400

Number Range Interval Maintenance ............................................................................ 401 Assign Number Range Interval ................................................................................... 403

Route Settlement ............................................................................................................... 404 Settlement Office ............................................................................................................ 406

Define Settlement Office ............................................................................................. 407 Set Determination of Settlement Office ...................................................................... 409

Settlement Type Configuration ....................................................................................... 411 Define Settlement Types ............................................................................................ 412 Set Determination of Settlement Types ...................................................................... 415

Assign Allowed Settlement Types to Settlement Office ............................................. 416 Collection Processing ..................................................................................................... 417

Maintain Settings for Automatic Clearing ................................................................... 418 Maintain Settings for Manual Clearing ........................................................................ 420 Post Control of Driver Receipts and Expenditures ..................................................... 421

Final Settlement/Document Control ............................................................................... 423 Define Customer Sales Transaction Types ................................................................ 424 Document Controls for Each Customer Sales Transaction Type ............................... 426 Set Up Customer Sales Transaction Types Determination ........................................ 428 Set Up Customer Sales Transaction Types Determination for Check-In/-Out Reasons .................................................................................................................................... 429 Define Customer-Specific Customer Sales Transaction Types ................................. 430

Settlement Cockpit ......................................................................................................... 431

Maintain Transaction Screens .................................................................................... 432 Activate Transaction Types ........................................................................................ 433

Automatic Route Settlement ........................................................................................... 434 Maintain Exclusions for Automatic Route Settlement ................................................. 435

Route Settlement: Tolerances ........................................................................................ 437 Define Tolerance Types.............................................................................................. 438 Define Tolerance Groups ............................................................................................ 439 Maintain Search Criteria for Tolerance Groups .......................................................... 442 Maintain Tolerance Group Determination ................................................................... 443

Route Settlement: Interim Accounting ............................................................................ 445 Maintain Special Driver and Customer Accounts (Collection) .................................... 448 Maintain Generic Driver and Customer Accounts (Collection) ................................... 450 Maintain Interim Accounts with +/- Differences .......................................................... 451

Maintain Interim Accounts for Final Differences ......................................................... 454 Copy Control Enablement from Handheld Invoice to R/3 Billing.................................... 456

Activate Copying Routines .......................................................................................... 457 Assign Copying Routine to Item Categories ............................................................... 458

Vehicle Space Optimization ............................................................................................... 459 Configure Material Master .............................................................................................. 460 Configure Customer Master ........................................................................................... 461 Configure Equipment/Fleet Master ................................................................................ 463 Define Process Types .................................................................................................... 464 Define Process Type Determination .............................................................................. 465 Determine Allowed Delivery Item Categories ................................................................. 466

Assign Plant to Transportation Planning Point ............................................................... 467 Define Vehicle Space Optimization Profile ..................................................................... 468

Assign VSO Profile to Plant and Shipment Type ........................................................... 469 Define Loading Bay Categories...................................................................................... 470



(C) SAP AG 9

Define VSO Vehicle Types and Loading Bays ............................................................... 471 Define Packing Groups .................................................................................................. 472 Define Package Types ................................................................................................... 473

Assign Package Types to Packing Group ...................................................................... 474 Define Collective Unloading Points ................................................................................ 475 Determine HU per Plant and Shipment Type ................................................................. 476

Assign VSO Status to Message ..................................................................................... 477 Loading Confirmation ......................................................................................................... 478

Configure Loading Confirmation Dialogs ....................................................................... 480 Configure Display of Detail Screens .............................................................................. 482 Define Reasons for Differences for Check-in and Check-out ........................................ 483

Output Control Configuration ............................................................................................. 484 Output Control for Visit Lists........................................................................................... 486

Output Determination .................................................................................................. 487 Maintain Condition Tables....................................................................................... 488 Maintain Access Sequences ................................................................................... 489

Message Type Maintenance....................................................................................... 490 Maintain Message Types for EDI ............................................................................ 492 Maintain Message Types Used for ALE Distribution .............................................. 494

Maintain Message Types for Collective Print Output .............................................. 496 Maintain Message Types for Visit List .................................................................... 498 Maintain Output Determination Procedure .............................................................. 500

Assign Output Determination Procedures ............................................................... 503 Print Output and Download from Visit List ..................................................................... 504

Define Message Types ............................................................................................... 505 Download: Define Scope of Data Transfer ................................................................. 506 Print Output: Determine Messages for Processing .................................................... 508

Output Control for Shipments ......................................................................................... 510 Output Determination .................................................................................................. 511

Maintain Condition Tables....................................................................................... 512 Maintain Access Sequences ................................................................................... 513

Output Type Maintenance .......................................................................................... 514

Maintain Output Types for EDI ................................................................................ 516 Maintain Output Types Used for ALE Distribution .................................................. 519 Maintain Output Types for Collective Print Output .................................................. 521

Assign Output Types to Partner Functions ............................................................. 523 Maintain Output Determination Procedure .............................................................. 524

Assign Output Determination Procedure ................................................................ 527 Print Output and Download from Shipment .................................................................... 528

Define Message Types ............................................................................................... 529 Specify Volume of Transmitted Shipping Data ........................................................... 530 Print Output: Determine Individual Messages for Processing .................................... 532

Valuated Delivery Note ................................................................................................... 534 Assign Shipping Messages and Billing Types ............................................................ 535

DSD Reload ....................................................................................................................... 536

Maintain Destination of DSD Connector ........................................................................ 538 Define Activity Types and their Assignment to Order Types .......................................... 539 Configure Order Type Determination ............................................................................. 540

Inventory View (Stock Visibility) ......................................................................................... 541 Activate Stock Visibility ................................................................................................... 544 Maintain Stock Visibility Scenario Settings .................................................................... 545 Maintain Storage Locations per Plant ............................................................................ 548 Maintain Recipient for Express Mail ............................................................................... 549

Business Add-lns (BAdIs) for Direct Store Delivery (Background) .................................... 551



(C) SAP AG 10

About This Document

This document only provides the download of configuration descriptions that are to form partof the Solution Manager Content for SAP Direct Store Delivery 1.0, which is planned to bedelivered by means of the next available patch in the Solution Manager Content supportpackage cycle. Other content, for example, links to IMG activities, transactions, andprograms, is not included and, therefore, this document should not be considered as thecomplete Solution Manager Content for SAP Direct Store Delivery 1.0.

The Solution Manager Content for SAP Direct Store Delivery 1.0 is delivered by means of thestandard Solution Manager Content support package cycle ST-ICO 150_700 which isavailable from the SAP Software Download Centre at http://service.sap.com/swdc. You canobtain the entire content by downloading the relevant patch from there.

The following table lists the document versions of this Configuration Guide, as well as thecorresponding patch numbers for patches in which the content that is relevant for SAP DirectStore Delivery 1.0 is included:

Document Versionof ThisConfigurationGuide

CorrespondingPatch Number

Release toCustomer Date

Description

1.00 Patch 41 June 3, 2014Initial delivery ofSolution ManagerContent for SAPDirect StoreDelivery 1.0

Patch 42 Sept. 2, 2014

For more information about SAP Solution Manager, see SAP Service Marketplace athttp://service.sap.com/solutionmanager .

http://service.sap.com/swdc



http://service.sap.com/solutionmanager






(C) SAP AG 11

SAP Direct Store Delivery: Configuration

This business scenario configuration guide applies to the SAP Direct Store Delivery business

scenario with the corresponding releases of SAP application components.

Business Scenario and Application Components

Business Scenario Application Component with Minimum Release

SAP Direct StoreDelivery

SAP ERP Central Component (SAP ECC) 6.0 EhP 6

SAP Direct Store Delivery 1.0

SAP Mobile Platform 2.3 SP 03

SAP Customer Relationship Management (SAP CRM) 7.0 EhP 2

(optional)

For more information about the necessary components and releases, see the mySAP ERPMaster Guide in the SAP Service Marketplace at http://service.sap.com/instguides under

Installation & Upgrade Guides SAP Business Suite SAP ERP ERP 6.0 .

Contents

The business scenario configuration guide contains all steps required to implement SAPDirect Store Delivery . The guide specifies the sequence of the configuration activities and

their dependencies.

It includes information about the following topics:

System connections

Business Customizing (including master data settings)

Target Group

Technical consultants

Application consultants

Project team members during the implementation of an SAP mobile app

SAP customer IT department

The sections are aimed at both technical and application consultants. Other target groupsmay find certain sections important as well.

http://service.sap.com/instguides






(C) SAP AG 12

SAP Notes

Before you start to configure this business scenario, consult the following SAP notes. Thissummary only contains major SAP notes to give you an initial overview. Make sure that youhave the up-to-date version of each SAP note, which you can find on SAP ServiceMarketplace at http://service.sap.com/notes.

Central SAP Notes for the Business Scenario

SAPNote

Title of SAP Note

1977104 Release restrictions/information for SAP Direct Store Delivery 1.0

1977108

Restrictions/Features of SAP Direct Store Delivery related to mobile offline

pricing

1935880 Installation information for SAP Direct Store Delivery 1.0

1928776 Release Strategy for Mobile Direct Store Delivery

1935880 Installation Information for SAP Direct Store Delivery 1.0

659222 ED: Performance Index for MSEG and VBFA

1873573 Enhancements for SAP Direct Store Delivery in SAP_APPL

1899013 Enhancements for SAP Direct Store Delivery in EA-APPL

1914486 Tour Will not Be Displayed in Transaction /DSD/SL_COCKPIT

1917902 Enhancements for AddOn SAP Direct Store Delivery in EA_APPL

1873455 Error /DSD/VC_MESSAGE 106: Visit list header locked

1894324Error /DSD/VC_MESSAGE 106: Visit list header locked (fixes error in note

1873455)

1927541 Odometer reading of visit is not settled

1926776 Incorrect assignment of reference documents during upload

1929019 Upload: Handheld activity type is not mapped to time type

1929301 Enhancements for SAP Direct Store Delivery in EA_APPL

1955922 Corrections to SAP Direct Store Delivery 606 SP 00

1955420 EA-APPL corrections necessary for SAP Direct Store Delivery (MOBDSDEI)

1637451 Encryption of credit card data in DSD

http://service.sap.com/notes



http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1873455&_NLANG=en&_NVERS=0






(C) SAP AG 13

SAPNote

Title of SAP Note

1645629 Route settlement: New orders are incomplete



(C) SAP AG 14

System Connections

System Landscape

The SAP Direct Store Delivery system consists of the following components:

DSD Back End

The DSD back end maintains the master data records (customer master, material master,bills of material). It contains the Data Extractor Core (or Pricing Engine), which handles DSDRoute Planning, Route Accounting, and the standard Sales and Distribution (SD) functions. Itcreates tours and shipments by consolidating deliveries. It also initiates the download of data.

DSD Connector

The DSD Connector parses the IDocs sent from the back end and stores the parsed data inits database. It also provides the interface to SAP Mobile Platform for transmitting tour-relateddata as well as master data to the mobile client. In addition, it provides the interface for SAPMobile Platform to upload the data collected on the mobile client to the DSD Connectordatabase. It also provides the transfer of the data collected on the mobile client to the DSDback end.

SAP Mobile Platform

SAP Mobile Platform is placed on a server and stores all tour data sent from the DSD backend system via the DSD Connector. It also handles the data transfer between the mobileclient and the DSD Connector in both directions (download and upload) by Mobile BusinessObjects (MBOs).

SAP Mobile Platform stores the data on a separate database (CDB). It also contains tools forsynchronization and data replication for administrative and controlling purposes. Thedownload and upload process are asynchronous.

Mobile Client

The mobile client contains the mobile app, the mobile Pricing Engine, and the MobileInfrastructure Client component.

CRM System (Optional)

SAP CRM is used for activity management processed and used during DSD tours. Thesystem needs to be connected to SAP ERP for master data exchange of customer and

materials and for download and upload of activity management data. All data downloaded foractivities goes through the DSD Connector.

Data Flow

On the DSD back end, deliveries are consolidated into shipments. The DSD back end canalso create visit lists. When saving the shipment or visit list, the system creates IDocsaccording to the customized settings and the data is transferred (downloaded) via IDocs fromthe DSD back end to the DSD Connector. The transfer of shipment and visit list-related datais performed by the DSD Output Control component in the DSD back end.

The DSD Connector parses the incoming IDocs and retrieves the necessary fields for themobile client application. As soon as all relevant shipment and pricing data is received by the

DSD Connector, the shipment status is set to Ready. The data is then transferred to the SAPMobile Platform.



(C) SAP AG 15

The mobile client synchronizes on request via the SAP Mobile Platform and checks if the tourdata is ready. When it is ready, the tour data is transferred to a specific mobile deviceaccording to the truck/driver assignment maintained in the DSD Connector Cockpit.

On the mobile client, data is entered or changed depending on the actual tour activities. Uponcompletion of the tour, tour data is uploaded into the Route Accounting Database and

subsequently settled. CRM activities are uploaded directly back to the CRM system whereactivities are updated accordingly; they are not settled through SAP ERP.

Furthermore, the mobile client supports a range of so called online scenarios like onlinepricing, online ATP, online credit check, and online open item check. An additional downloadduring the tour, for example, a new customer from the back end or an additional delivery, iscovered by the Occasionally Connected Scenario.

The following documentation describes all the configuration steps that enable the variouscomponents to communicate and to correctly transfer the data.

These steps are:

1. Connection of DSD Back End System to DSD Connector [Page 16]

2. Connection of DSD Connector to SAP Mobile Platform [Page 45]

3. Connection of SAP Mobile Platform to DSD Connector [Page 49]

4. Application Log Monitoring [0]

5. Optional: SAP CRM Integration [Page 79]



(C) SAP AG 16

Connection of DSD Back End System to DSDConnector

This process allows communication between the DSD back end and the DSD Connector.

The majority of the configuration paths mentioned is found in Customizing. However, a fewpaths are on the SAP Easy Access menu.

Prerequisites

The following should be noted before connecting the DSD back end to the DSD Connector:

The DSD back end must be on the same client system as the DSD Connector.

In this documentation, this system is called the DSD back end/DSD Connector.

The Data Extractor component (also called the Pricing Engine) should also be on thesame system as the DSD back end and DSD Connector.

The Data Extractor is part of the plug-in. A plug-in is an additional component (similar to theadd-on of an Industry Solution), which is located above the level of SAP_APPL. The plug-inconnects the extension objects (EA-APPL) to the SAP_APPL level.

Process

The following steps need to be performed to enable communication between the DSD back

end and the DSD Connector:

1. Define Logical Systems [Page 17]

2. Assign Client to Logical System [Page 18]

3. Define RFC Destination for Back End/DSD Connector [Page 19]

4. Define Port in Back End/DSD Connector [Page 21]

5. Set Cross-System Company Codes for Global Organizational Units [Page 24]

6. Define ISO Codes for Currencies [Page 25]

7. Define ISO Codes for Units of Measurement [Page 26]

8. Maintain Distribution Models and Distributing Views [Page 28]

9. Define Inbound Process Code [Page 31]

10. Define Outbound Process Code [Page 34]

11. Maintain Partner Profiles in Back End/DSD Connector [Page 36]

12. Assign IDoc Type and Message Type [Page 43]

Result

You have established a connection between the DSD back end and the DSD Connector.



(C) SAP AG 17

Define Logical Systems

The distribution of data between the DSD back end and the DSD Connector makes it

necessary to identify each system as a unique logical system.

The Customizing table Define Logical System is cross-client. Therefore, we recommend thatyou define both logical systems for the DSD back end and the DSD Connector from onesystem.

Procedure

1. To define logical systems, in Customizing for SAP NetWeaver under Application

Server IDoc Interface / Application Link Enabling (ALE) Basic Settings Logical

Systems , choose Define Logical System.

2. Choose New Entries.

3. Enter the following data:

Field Name User Action and Default Values

Log.System Enter a name for the logical system that you want to create.

Example: Q3ACLNT004

Name Enter a free text description for the logical system.

Example: DSD Back End

The table is cross-client. This means that changes made here apply to all clients inthe system.

To designate logical systems, we recommend the following naming convention:

<XXX >CLNT<NNN > (where XXX is the system name and NNN is the client).

Since you need to maintain two logical systems on the same client (one for the DSDback end and another for the DSD Connector), you have to deviate from this format.However, we recommend following the naming convention as closely as possible tosimplify identification.

4. Save your entries.

Result

You have now defined two logical systems to establish data distribution from the DSD backend to the DSD Connector.



(C) SAP AG 18

Assign Client to Logical System

You assign the appropriate client to the logical system for the DSD back end that you have

defined in Define Logical Systems [Page 17].

This step is needed to enable data distribution from the DSD back end to the DSD Connector.

The Customizing table Assign Client to Logical System is cross-client.

Procedure

1. To assign a client to a logical system, in Customizing for SAP NetWeaver under

Application Server IDoc Interface / Application Link Enabling (ALE) Basic

Settings Logical Systems , choose Assign Logical System to Client .




Client Select the appropriate client of the DSD back end and enter adescription.

City Enter the appropriate name.

Logical system

Select the logical system created in the previous step from the inputhelp to assign the client to the logical system.

Example: Q3ACLNT004

Std currency (Standard Currency)

Enter the standard currency used in the client.

Client role Select the appropriate client role from the list.

Example: T Test


Result

You have now assigned the logical system for processing outgoing and incoming IDocsbetween the DSD back end and the DSD Connector.



(C) SAP AG 19

Define RFC Destination for Back End/DSDConnector

You have to enable data distribution from the DSD back end to the DSD Connector, which areon the same client. In Customizing, you define the technical parameters for the RemoteFunction Call (RFC) destinations. The RFC is controlled by the RFC destination parameters.

RFC destinations must be assigned to RFC ports during the creation of ports (see Define Portin Back End/DSD Connector [Page 21]).

We recommend giving the RFC destination the same name as the logical system.

This naming convention allows you to identify easily which logical system and RFC

destinations are connected later.

Procedure

1. To define an RFC destination, in Customizing for SAP NetWeaver under

Application Server IDoc Interface / Application Link Enabling (ALE)

Communication , choose Create RFC Connections.

2. Choose Create.



RFCDestination

We recommend you use the same naming format as the one used toidentify the logical system of the DSD Connector.

ConnectionType

3 (Connection to R/3 System)

Description

Description Enter a description (this is not stored with the Description ID).

4. Choose Enter to enable data entry on the tab fields.

5. On the individual tabs, enter the following data:


TechnicalSettings

Balance Load Selected

Target Host Enter the host name of the DSD back end/DSD Connector.

System Number Enter the system number of the DSD back end/DSD Connector.



(C) SAP AG 20


Save as Select IP-address.

Logon/Security

Language Enter the abbreviation of the desired language.

Client

Enter the client number of the DSD back end/DSD Connector.

Although both systems are on the same client, you have to define

separate logical systems for the DSD Connector. In the Client field,

enter the DSD back end. This enables communication between the DSDback end and the DSD Connector within one SAP R/3 system.

User If you do not select the option Current User , enter the Logon/User ID ofthe DSD back end.

Current User Selected.

SpecialOptions

Trace ExportMethods

Default Gateway Value selected.

Keep-AliveTimeout

Default Gateway Value selected.

Select TransferProtocol

2 – Classic with tRFC.


Result

You have now defined an RFC destination to establish communication between the DSDback end and the DSD Connector.



(C) SAP AG 21

Define Port in Back End/DSD Connector

You have to enable communication between the DSD back end and the DSD Connector.

A port definition is required for dispatching messages to logical systems. The port is assignedto a partner system in the partner profile.

Prerequisites

RFC destinations are defined.

The number range for ports is defined.

Procedure

1. To define the port in the DSD back end/DSD Connector, in Customizing for SAP

NetWeaver under Application Server IDoc Interface / Application Link Enabling

(ALE) Modelling and Implementing Business Processes Configure Predefined ALE

Business Processes Logistics Logistics-External Systems External Transportation

Planning Systems , choose Maintain ALE Port Definition.

On the Ports in IDoc Processing screen, choose Transactional RFC .

2. Choose Create.

In the dialog box, choose an option as follows:

o If you want the system to generate a port name, choose Generate port name.

o If you wish to define the port name yourself, select own port name and entera name in the Name field.

3. Choose Continue (Enter).

On the Creating a tRFC Port screen, enter the following data:


Port Depending on the previously selected option, the port ID was eithergenerated automatically – allocating a number to the new port from the rangeof ports – or the port name provided was used.

Description Enter a description for the port.

RFC Enter the name of the RFC destination that was created in Define RFCDestination for Back End/DSD Connector [Page 19].

4. Save the port definition.

On the Ports in IDOC Processing screen, choose File and Create.

On the Creating a file port screen, enter the following data:


Port Enter a name.



(C) SAP AG 22


Example: DSD_PORT

Description

Enter a description for the port.

Example: DSD Port for download

Version

IDOC record typesSAP release 2.0/2.1

Not selected.

IDOC record typesSAP release 3.0/3.1

Not selected.

IDOC record typesSAP release 4.x

Selected.

System Setting

Unicode Format Selected.

Continue despiteconversion error

Not selected.

Replacement char. No entry.

Outbound File

physical directory Selected.

Directory

Enter a directory that can be accessed from another system, such asthe DSD Connector (use the Uniform Naming Convention-UNC).

Contact your system administrator for the name of the directory.

Entering an invalid directory produces an error (transaction code

BD87) during processing of the Inbound IDOC /DSD/HH_CONTROL.

Function module EDI_PATH_CREATE_CLIENT_DOCNUM

Outbound Trigger

Start Shell Scriptwith Idoc File Name

Selected.

Physical directory Selected.

Directory Enter a directory that can be accessed from another system.

Inbound File

physical directory

Selected.

In the field below, enter the directory where the DSD back end storesthe IDoc files.



(C) SAP AG 23


Function module No entry.

Inbound file

Depends on the function module entered on the Outbound File tab in

the Function Module field.

Example: O_<client number of DSD Backend System>


In the section Partner Profiles: Outbound Parameters, a file port must be labeled as areceiver port.

The receiver port is used for the following message types, which representtransactional data:

o /DSD/HH_ROUTE_ITINERARY

o DESADV

o ORDRSP

o SHPMNT

Result

The necessary ports have been defined to establish communication between the DSD back

end and the DSD Connector.



(C) SAP AG 24

Set Cross-System Company Codes for GlobalOrganizational Units

To distribute open items (in the Financial Accounting (FI) component) of customers via Application Link Enabling (ALE), you have to assign the local company code unit to a globalcompany code in the DSD back end. This ensures that they are used consistently in thedistributed environment.

Prerequisites

A company code is defined in FI.

Credit master data is defined for those customers whose open items are to be madeavailable on the mobile device.

Procedure

1. To set cross-system company codes, in Customizing for SAP NetWeaver under

Application Server IDoc Interface / Application Link Enabling (ALE) Modelling

and Implementing Business Processes Global Organizational Units , chooseCross-System Company Codes.

In the Choose Activity dialog box, choose Cross-System Company Codes entry.


Specify an alphanumeric key with up to six characters for the company code, forexample ALE001.

3. Save your entries and go back.

Choose Assign Company Code to Cross-System Company Code.

4. Assign the global company code to your local company code.


Result

You have now defined a new organizational unit as a prerequisite for the data distribution ofcustomer open items.



(C) SAP AG 25

Define ISO Codes for Currencies

You need to define ISO currency codes in your SAP system to allow communication with

external systems.

The ISO code is used to convert the internal SAP units of measurement into standardmeasurement units. Data exchange via Electronic Data Interchange (EDI) requires internalmeasurement units to be converted into standard measurement units. For this reason, ISOcodes must be assigned to SAP internal units.

The Customizing table for currency codes must contain entries for all currencies that occur inyour business transactions. All currencies need to be defined according to the internationalISO standard for currencies. Otherwise, the system is not able to use data exchange ininternational communication (for example, for bank clearing transactions).

Procedure

1. To define ISO codes, in Customizing for SAP NetWeaver under General Settings

Currencies , choose Check Currency Codes.


3. On the New Entries: Details of Added Entries screen, enter the following data:


Currency Enter a key for the currency in which monetary amounts are being managedwithin your system.

Long Text Enter a description for your new entry (long form).

Short text Enter a description for your new entry (short form).

ISO code Enter the appropriate currency key (standard worldwide).

Alternativekey

To ensure a unique assignment of the ISO code to an SAP currency key, oneof the SAP currency keys must be selected as the primary currency key forthe ISO code.

Valid until Enter an expiration date for the currency.


Result

The system is now set up to use currencies for EDI data exchange.



(C) SAP AG 26

Define ISO Codes for Units of Measurement

SAP uses internal units for measurement. To communicate with external systems, these

internal units must be converted into the Electronic Data Interchange (EDI) standard. ISOcodes exist for standard measurement units and are used for data exchange via EDI withexternal systems. To implement communication with external systems, ISO codes must beassigned to SAP internal units.

Procedure

Defining ISO Codes

1. To define ISO codes, in Customizing for SAP NetWeaver under General Settings,choose Check Units of Measurements.

2. Choose ISO Codes and New Entries.



ISO code Specify an alphanumeric key with up to three characters for the ISO code.

ISO code text Enter a description for the new ISO code.

4. Save your entries and choose Back twice to return to the initial screen.

Defining Units of Measurement

1. Choose Units of Measurement .

2. Choose Create and enter the following data:

Field Name User Action and Default Actions

Int. meas unit Enter a description for the new unit of measurement.

Display

Commercial Enter a description for the new unit of measurement.

Technical Enter a description for the new unit of measurement.

Decimal places Enter the number of decimal places with which this unit ofmeasurement is displayed.

float. point exp. No entry.

Conversion

Numerator 1

Denominator 1

Exponent No entry.



(C) SAP AG 27


Additive constant No entry.

Decimal pl. rounding No entry.

Unit of meas. family No entry.

Measurement UnitText

Measurement unittext

Optional: Enter a description for the unit.

ALE/EDI

ISO code Enter the current ISO code for your unit of measurement.

Primary code Select this checkbox if this unit should be a primary unit for an ISOcode.

ApplicationParameters

Commercial meas.unit

Selected.

Value-based commt Not selected.


Result

The system can use the new units of measurements for EDI.



(C) SAP AG 28

Maintain Distribution Models and DistributingViews

A distribution model must be maintained if data transfer is performed via Application LinkEnabling (ALE). ALE must be used in cases where one DSD back end communicates withmore than one DSD Connector. This Customizing is not necessary for communication viaIntercompany Data Exchange (IDE).

To process the credit status data, it is necessary to use the ALE distribution model (via BAPI).

Applications that communicate with each other within an ALE business process are specifiedwhen modeling the message flow. The message flow can be defined in a distribution model.

The distribution model consists of separate model views in which all associated cross-systemmessage flows between the DSD back end and the DSD Connector can be defined. These

views must be distributed to the receiving systems.

Procedure

1. To maintain distribution models and distribute views, in Customizing for SAP

NetWeaver under Application Server IDoc Interface / Application Link Enabling

(ALE) Modeling and Implementing Business Processes , choose MaintainDistribution Model and Distribute Views.

2. Ensure that you are in Change mode.

3. Choose Create Model View .



Short text Enter a description of the new model view to be created.

Example: DSD Data Distribution to Connector

Technicalname

Enter a description.

Example: DSD_Data

Start Date Enter the start of a validity period (by default, the system date is

displayed).

End Date Enter the end of a valid period.


The newly created model view appears on the Distribution Model Overview screen.

Adding Message Types

1. Select the new model view and choose Add message type.




(C) SAP AG 29


Model view By default, the technical name of the selected model view is displayed.

Sender Enter the name of the logical system of the DSD back end.

Receiver Enter the name of the logical system of the DSD Connector.

MessageType

From the input list, select one of the message types for which data should betransferred via ALE.

Example: /DSD/HH_CONTROL

3. You have to add the following message types to the distribution model for the DSDprocess:

o DEBMAS

o MATMAS

o BOMMAT

o /DSD/HH_CONTROL

o /DSD/HH_CUSTMASTEXT

o /DSD/HH_CREDITDATA

o /DSD/HH_MATMASTEXT

o /DSD/HH_PAYMMASTEXT

o /DSD/HH_DRIVERMAST

o /DSD/HH_TXTDRV

o /DSD/HH_VEHICMAST

Repeat steps 1. and 2. for each message type.


They appear on the Distribution Model Overview screen.

Adding BAPIs

1. Select the model view and choose Add BAPI .

This is mandatory for processing credit status data (for which you need to add themessage type CRESTA).



Model view By default, the technical name of the selected model view is displayed.



(C) SAP AG 30


Sender/client Enter the name of the logical system of the DSD back end.

Receiver/Server Enter the name of the logical system of the DSD Connector.

Obj.name/interface

From the input help, select the entry DebtorCreditAccount .

Method From the input help, select the entry ReplicateStatus.


They appear in the Display Distribution Model screen.



(C) SAP AG 31

Define Inbound Process Code

You enable the DSD Connector to process IDocs that are received from the DSD back end.

You define a code that identifies a process type. The process type determines which processis being used to convert an incoming IDoc into an SAP document.

Procedure

1. To define inbound process codes, on the SAP Easy Access screen in SAP ERP,

choose Tools ALE ALE Development IDoc Inbound Processing Define

Process Code.

2. In Change mode, choose New Entries.



Process code Enter an alphanumeric code with up to 30 characters.

For example: DSD-INBOUND

Description Enter a description for the process code.

Identification Leave this field blank.

Option ALE Select the appropriate option.

Processing Type

Processing by task Not selected.

Processing by function module Selected.

Processing by process Not selected.

4. Choose Save and confirm the message in the dialog box.



Process code The field contains the selected process code.

Function module Enter /DSD/ME_IDOC_INPUT_CONNECTOR . This is the name of the

function module responsible for inbound processing.

Maximum numberof repeats

Specify the number of attempts to post an IDoc in an application.

Example: 0

IDoc Packet



(C) SAP AG 32


Object Type Enter IDOCPACKET

End event Enter MASSINPUTFINISHED

IDoc

Object Type Enter IDOCAPPL

Start event Enter INPUTERROROCCURRED

End event Enter INPUTFINISHED

Success Event Enter INPUTSUCCESS

Application

Object

Object Type No entry.

Start event No entry.


7. Choose Back and confirm the message in the dialog box.

8. On the New Entries: Details of Added Entries screen, select the newly-definedprocess code DSD-INBOUND and double-click Logical Message.

9. On the Logical Message: Overview screen, choose New Entries.



Process code The field contains the selected process code.

Assignment toLogical Message

Message type

Select this radio button. In the adjacent field, enter an appropriate

message type as indicated in step 12.


All Types Not selected.

Message code Select this radio button, but leave the adjacent field blank.

All Codes Not selected.

Message function Select this radio button, but leave the adjacent field blank.

All functions Not selected.




(C) SAP AG 33

12. Repeat steps 9 through 11 for the following message types:

o /DSD/HH_CONTROL



o /DSD/HH_PAYMASTEXT

o /DSD/HH_TXTDRV

o BOMMAT

o DEBMAS

o MATMAS

o SYNCH

ResultYou have now defined an inbound process code that is used during the processing ofincoming IDocs from the DSD back end.

This inbound process code is assigned to each message type that you maintain in MaintainPartner Profiles in Back End/DSD Connector [Page 36] for inbound parameter settings.



(C) SAP AG 34

Define Outbound Process Code

You define an outbound process code that the system uses during the processing of

outbound IDocs being sent from the DSD back end to the DSD Connector.

The outbound process code /DSD/HHDL is shipped with client 100 and should be transported

into the copy client. If you want to define your own outbound process code, follow theprocedure below.

Procedure

1. On the SAP Easy Access screen, choose Tools ALE ALE Development IDoc

Outbound Processing Define Process Code .




Process code

Enter an alphanumeric code with up to 30 characters using thecustomer namespace (either Y* or Z*).

Example: <YDSD-OUTBOUND >

Description Enter a description for the process code.

Function module Enter the function module/DSD/HH_IDOC_OUTPUT_CONTROL.

Option ALE/inb.procg. Select Processing with ALE service

Version of FunctionModule

Processing with functionmodule version 3.0

Selected.

Processing with functionmodule version 2.2

Not selected.

4. Choose Save and confirm the message in the dialog box.

5. Choose the Logical Message entry.



Process Code The field contains the selected process code.

Assignment to Logical



(C) SAP AG 35


Message

Message Type Select this radio button. In the adjacent field enter/DSD/HH_CONTROL .

All Types Not selected.

Message Code Select this radio button, but leave the adjacent field blank.

All Codes Not selected.

Message function Select this radio button, but leave the adjacent field blank.

All functions Not selected.


Result

You have defined a process code that is ready to be used during the processing of outboundIDocs being sent from the DSD back end to the DSD Connector.

The outbound process code is assigned in the Partner Profiles, table control OutboundParameter for the message type /DSD/HH_CONTROL on the Message Control tab.



(C) SAP AG 36

Maintain Partner Profiles in Back End/DSDConnector

You use partner profiles to ensure proper IDoc processing. Partner profiles maintain thecorrect message types as inbound or outbound parameters. For Application Link Enabling(ALE) communication to take place, partners must have been defined with inbound oroutbound parameters. This way, incoming or outgoing IDocs can be channeled correctly.

You must specify a partner profile on the sending side (DSD back end) by defining inboundparameters as well as on the receiving side (DSD Connector) by defining outboundparameters.

Prerequisites

One logical system is defined for the DSD back end and another for the DSD Connector.

The receiving ports are assigned.

Output types exist. Either use the SAP standard functionality of output control for shipments(in Customizing for Logistics Execution, choose Transportation Basic Transportation

Functions Output Control. ) or use the DSD functions of output control for shipments (in

Customizing for Logistics Execution, choose SAP Direct Store Delivery Output Control ):

Message type Download – EDI (for example, DSD1) with the following parameters:

o Transmission medium 6 = EDI

o Application V7 = Shipment

For the output types, output condition records are defined on the SAP Easy Access

screen, choose Logistics Sales and Distribution Master Data Output Shipment

.

Message types must have been created for visit lists (in Customizing, chooseLogistics Execution Direct Store Delivery Output Control ).

o Message type Download – EDI (for example, DSD1) with followingparameters:

Transmission medium 6 = EDI; Application VL = Visit List

For the message types, message condition records must have been defined on the

SAP Easy Access screen under Logistics Logistics Execution Direct StoreDelivery Output Control Message Condition Records Visit List .

The message types are assigned to a processing program, /DSD/HH_NASTED that creates

the relevant IDocs for all data belonging to the shipment or DSD visit list environment(deliveries, orders, and so on). See also the section Download , topic Specify Volume of

Transmitted Shipping Data [Page 530].

The transfer of transactional data to the DSD Connector system is performed as shipment-oriented or DSD visit list-oriented. This means that all data belonging to a shipment or DSD

visit list is bundled and transmitted to the DSD Connector system. The bracket over the entiredata transmission forms the IDoc /DSD/HH_CONTROL02 IDOC.



(C) SAP AG 37

Procedure

1. In Customizing for SAP NetWeaver under Application Server IDoc

Interface/Application Link Enabling (ALE) Modelling and Implementing Business

Processes Configure Predefined ALE Business Processes Logistics Logistics <

External Systems External Transportation Planning Systems , choose Maintain

ALE Partner Profiles.

2. In the Partner column, select Partner Type LS and choose Create.

3. On the Partner Profiles screen, enter the following data:


Partner no.

Enter the name of the logical system of the DSD Connector asdefined in Define Logical Systems [Page 17].

Example: Q3ACLNT004

Partn. Type This field should automatically be filled with the partner functionLS (must always be LS).

Post Processing:Permitted Agent

Type Choose US (User)

Agent Enter a User ID.

Lang. Enter the language abbreviation.

Example: EN

Classification

Partner class No entry.

Partn. status Choose A (must be always set to A = active)

Arch. indicator Not selected.

Telephony

Telephone No. Optional: Enter a number.

Country Indic. Optional: Enter the language abbreviation.

Name Optional: Enter a name.

Company Optional: Enter a name.


The icons below the table control get activated.

Below the Outbound paramtr. table, choose Create outbound parameter .

5. In the Partner Profiles: Outbound Parameters screen, enter the following data:



(C) SAP AG 38


PartnerNumber

This field is automatically filled with the value maintained in the entryscreen.

Partn. Type This field is automatically filled with the value maintained in the entryscreen.

Partner Role For EDI processing, choose partner function LS. For ALE processing,

leave the field blank

Message type Enter a message type listed below this table.

Example: /DSD/HH_ROUTE_ITINERARY

Message Code Leave blank .

MessageFunction Leave blank .

Tab OutboundOptions

Receiver Port

Enter receiver port as defined in step Define Port in Back End/DSDConnector [Page 21].

See the list of message types that follows this table that needs to bemaintained. It contains information about which port to use for each

message type and partner role.

Choose Enter to open allfields.

Packet Size Enter the desired number of IDocs sent per RFC.

Example: 10

Output Mode

Transfer IDocimmed.

Recommended and required for at least the DEBMAS, MATMAS,BOMMAT , and CRESTA message types.

In case data is transferred using the file port, also recommended andrequired for the ORDRSP, DESADV, SHPMNT and INVOIC messagetypes.

Collect IDocs

Required for the /DSD/HH_CONTROL message type.

Recommended and required for the ORDRSP, DESADV, SHPMNT,INVOIC message types in cases where they are to be transferred via RFCport instead of file port.

For the /DSD/HH_CONTROL message type, a job needs to be scheduledto get the collected IDocs dispatched later (see also Download/Data



(C) SAP AG 39


Replication Configuration [Page 352]).

IDoc Type

Basic Type

Use input help to select the appropriate message type (the last entry onthe list with the highest number).

When maintaining the /DSD/HH_ROUTE_ITINERARY message type, you

must ensure that you have selected the correct basic type (ending with03). Only this version contains the segments required to downloadcustomer and/or visit texts to the mobile device and make them visible asdriver messages.

Tab MessageControl (seealso Note

below)

Application

Enter the application for which you maintain the message type.

For Shipments: enter V7

For Visit Lists: enter VL

Message Type

Enter the name of the message type, which is defined in SAP StandardOutput Control or in DSD Backend Output Control (see “Prerequisites”).

For EDI processing, choose the message type that has been customizedfor EDI.

Example: DSD1

For ALE processing, choose the message type that has been customizedfor ALE.

Example: DSD2

Process Code

Use input help to select the outbound process code as defined in DefiningOutbound Process Code [Page 34].

Example: YDSD-OUTBOUND

The data on the Message Control ( Application, Message Type, Process Code fields)

must be maintained only for message type /DSD/HH_CONTROL.

The following list contains all message types that must be maintained in the tablecontrol Outbound Parameters. To do this, follow step 5 for each of the message typeslisted. Depending on the type of Data Distribution being used (ALE or EDI), you needto maintain the message types with or without the Partner Role LS.

The partner role LS should not to be confused with the partner function LS. Allmessage types maintained must have the partner function LS.

IDOCs with transactional data should be sent by File Port (not by tRFC) and shouldhave the radio button Transfer Immediately and Do not start subsystem selected.



(C) SAP AG 40

Message Type W/o LS With LS Use Port

/DSD/HH_CONTROL X X tRFC Port

/DSD/HH_CREDITDATA X - tRFC Port

/DSD/HH_CUSTMASTEXT X - tRFC Port

/DSD/HH_DRIVERMAST X - tRFC Port

/DSD/HH_MATMASTEXT X - tRFC Port

/DSD/HH_PAYMMASTEXT X - tRFC Port

/DSD/HH_ROUTE_ITINERARY X X File Port

/DSD/HH_TXTDRV X - tRFC Port

/DSDHH_VEHICMAST X - tRFC Port

BOMMAT X - tRFC Port

DEBMAS X - tRFC Port

MATMAS X - tRFC Port

DESADV - X File Port

ORDRSP - X File Port

SHPMNT - X File Port

SYNCH - X tRFC Port


7. In the left window under the heading Partner , select partner type LS.

8. Choose Create.

9. On the Partner Profiles screen, enter the following data:


Partner Number Enter the name of the logical system of the DSD back end asdefined in Define Logical Systems [Page 17].

Partner Type This field should be filled with the Partner Function LS automatically (must always be LS).

Post Processing:Permitted Agent

Type Choose US (User).

Agent Enter the User ID.



(C) SAP AG 41


Language Enter the language abbreviation.

Example: EN

Classification

Partner class No entry.

Partner status Choose A (must be always set to A = active).

Archive Checkbox Not selected.

Telephony

Telephone No. Optional: Enter a number.

Country Key Optional: Enter the language abbreviation.

Name Optional: Enter a name.

Company Optional: Enter a name.


Saving activates the icons below the table control.

11. Below the table control Inbound Parameters, choose Create Inbound Parameter .

12. In the Partner Profiles: Inbound Parameters screen, enter the following data:


Partner Number This field is automatically filled with the value maintained in theentry screen.

Partn.Type This field is automatically filled with the value maintained in theentry screen.

Partner Role

For EDI processing, choose partner function LS. For ALEprocessing, leave the field blank.

For all message types listed below it is recommended to leave thisfield blank.

Message type Enter a message type listed below this table.

Example: BOMMAT

Process Code Enter the Inbound Process Code, as defined in Define InboundProcess Code [Page 31].

Syntax Check Checked.

Processing byFunction Module



(C) SAP AG 42


Trigger by background program

No entry.

Trigger immediately Recommended and required for all Master Data IDocs and theControl IDoc (see the list below this table).

The following list contains all message types that must be maintained in the InboundParameters table control. All message types listed below should be maintainedwithout partner role LS. To do this, repeat step 8 for each of the following messagetypes:

o /DSD/HH_CONTROL





o /DSD/HH_TXTDRV

o /DSD/HH_VEHICMAST

o BOMMAT

o MATMAS

o DEBMAS

o SYNCH

Inbound processing does not exist for transactional IDocs. Therefore, they donot need to be maintained in the Inbound Parameters table control.

13. Save your settings.

Result

You have now defined a partner profile that contains the necessary settings to handle theprocessing of outgoing IDocs from the DSD back end and incoming IDocs to the DSDConnector.



(C) SAP AG 43

Assign IDoc Type and Message Type

All message types necessary to handle incoming IDocs based on an SAP ERP shipment

must be entered in this table with the appropriate function module assigned to each type.

Prerequisites

The Inbound Process Code is defined.

The Logical System LS is defined.

The Partner Profile is defined.

Procedure

1. To assign IDoc and message types, on the SAP Easy Access screen, choose

Tools ALE ALE Development IDocs Inbound Processing Function Module Assign IDoc Type and Message Type .




Processing By

Module

/DSD/ME_IDOC_INPUT_CONNECTOR (that is the name of the

function module for inbound processing of incoming IDocs for theDSD-Connector).

Type F (Function Module)

IDoc Type

Basic Type

Enter the name of the basic IDoc type of the incoming IDocconcerned.

Example: /DSD/HH_CONTROL02

Extension No entry.

Message

Message Type

Enter the name of the message of the incoming IDoc concerned.This field is mandatory.


Message Variant No entry.

Mess. Function No entry.

Object Type No entry.



(C) SAP AG 44


IDoc: Assignment ofFM to Log, Message,and IDoc Type

Direction Select option 2 (for Inbound).

Description Is entered automatically.

Name No entry.


5. Repeat step 3 and 4 for each message type (except message type SYNCH ) that youhave entered in the Inbound Parameters table control in the corresponding partnerprofile. This means that you must maintain an entry for the following message types:

o /DSD/HH_CONTROL





o /DSD/HH_TXTDRV

o BOMMAT

o MATMAS

o DEBMAS

Result

You created an entry for each message type and IDoc type for which a function module hasbeen assigned. Together with the completion of the three preceding activities, the system nowhas all the necessary settings to receive incoming IDocs from the back end system.



(C) SAP AG 45

Connection of DSD Connector to SAP MobilePlatform

In the DSD Connector system, you have to enable communication between the DSDConnector and SAP Mobile Platform.

These steps are linked closely to SAP Mobile Platform. We recommend that you set up bothsystems together; therefore, see the Master Guide for appropriate actions in SAP MobilePlatform.

Process

You have to define an RFC destination on the DSD Connector to enable communicationbetween the DSD Connector and SAP Mobile Platform:

1. Defining RFC Destination on DSD Connector [Page 46]

2. Maintain SAP Mobile Platform Data Connectivity [Page 48]



(C) SAP AG 46

Define RFC Destination on DSD Connector

Perform this step to establish communications between the DSD Connector and the SAP

Mobile Platform Component.

Procedure

1. In Customizing for SAP NetWeaver under SAP Web Application Server IDoc

Interface/ Application Link Enabling (ALE) Communication , choose Create RFCConnections.

2. Choose Create.



RFC Destination

Enter the name for the RFC destination.

The name should be identical to the name that is being usedto identify SAP Mobile Platform, for example, ZSMP_DCN.

Connection Type G (HTTP Connection to External Server).

Description

Description 1-3 Enter a description (not stored with a description ID).

Technical Settings

Target Host Enter the host name (IP) of SAP Mobile Platform.

Service No. Enter the system ID.

Logon/Security

Basic Authentication

Enter user name that is valid on SAP Mobile Platform.

Example: supAdmin@YKB

“@YKB” depends on your settings for the security user onSAP Mobile Platform; for more information, see the MasterGuide.

Send logon Ticket WithoutRef. to a target System

Select the radio button.

SSL Select the radio button for Inactive.

SSL Certificate Select DFAULT SSL Client (Standard).



(C) SAP AG 47


Special Options

ICM Default Time out Selected.

HTTP Version Select HTTP 1.0 .

Compression Select Inactive.

Compressed Response Select Yes.

Accept Cookies Select No.


Result

An RFC destination is defined to establish communication between the DSD Connector andSAP Mobile Platform.



(C) SAP AG 48

Maintain SAP Mobile Platform Data Connectivity

You can define different SAP Mobile Platform connections. These connections can be used,

for example, for testing or support. If you define an active RFC connection, SAP MobilePlatform domain, and SAP Mobile Platform package for your user, these values are used forthe download process (from the back end to SAP Mobile Platform). For all other users, theentries with the empty user name are used as default.

For this table, two fields are necessary and need to be defined first in SAP Mobile Platform (SMP Domain and SMP Package). For more information, see the Master Guide.

Procedure

1. In Customizing for Logistic Execution under SAP Direct Store Delivery HandheldConnectivity General Settings , choose Maintain SAP Mobile Platform DataConnectivity .




User Name Optional entry.

Counter Optional entry.

Active Select the checkbox to activate the connection.

RFCDestination

Enter the name for the RFC destination of SAP Mobile Platform.

SMP Domain Enter here the domain of SAP Mobile Platform.

SMPPackage

Enter here the name and the version for the SAP Mobile Platform package.The format should be <package name>:<package version>.

Can be entered later as well.


Result

You have set up the connection from SAP ERP to SAP Mobile Platform. Informationregarding the SAP Mobile Platform settings is part of the Master Guide for SAP Direct StoreDelivery .



(C) SAP AG 49

Connection of SAP Mobile Platform to DSDConnector

The data transfer from SAP Mobile Platform to SAP ERP (upload) is based on a backgroundremote function call (bgRFC). This ensures that the data is transferred exactly once and inorder. The bgRFC uses queues for communication handling between the systems.

These steps are typically SAP Basis related. Therefore, you might not have the appropriateauthorization to perform the actions.

For more information, see the Master Guide for SAP Direct Store Delivery where additionalsettings are described regarding the setup of SAP Mobile Platform (the middleware system).

Process

The following steps need to be performed to enable communication between SAP MobilePlatform and the DSD Connector:

1. Define RFC Destination in SAP ERP for bgRFC [Page 50]

2. Define RFC Destination for Supervisor [Page 52]

3. Maintain Inbound Destination for bgRFC [Page 54]

4. Activate Internet Communication Services [Page 55]

5. General Parameter Value Maintenance [Page 56]

Result

Once all the process steps have been performed, the connection between SAP MobilePlatform and the DSD Connector is established.



(C) SAP AG 50

Define RFC Destination in SAP ERP for bgRFC

You have to establish the communication between SAP Mobile Platform and the DSD

Connector by configuring a background remote function call (bgRFC).

Procedure

1. In Customizing for SAP NetWeaver under Application Server IDoc Interface /

Application Link Enabling (ALE) Communication , choose Create RFCConnections.

2. Choose Create.



RFC Destination


The name should identify the connection to SAP Mobile Platform.

Example: HTTP_UPLOAD_INFORMATION

Connection Type 3 (connection to SAP ERP).

Description

Description Enter a description (not stored with a description ID).

TechnicalSettings

Balance Load Not Selected.

Target Host Enter the host name of the DSD Connector.

System number Enter the system number of the DSD Connector.

Save as “Hostname” selected.

Logon/Security

Language No entry.

Client No entry.

User No entry.

Current User Not Selected.

Special Options



(C) SAP AG 51


Transfer Protocol Select 1 – Classic with bgRFC.


Result

You have now defined a bgRFC destination to establish communication between SAP MobilePlatform and the DSD Connector.



(C) SAP AG 52

Define RFC Destination for Supervisor

The supervisor destination gets the configuration settings for the bgRFC scheduler and starts

or stops the scheduler as required on each application server. This technical setting isneeded for the queues to work correctly.

This destination must be defined as either an ABAP connection or a logical connection.

Procedure

1. In Customizing for SAP NetWeaver under Application Server IDoc Interface /

Application Link Enabling (ALE) Communication , choose Create RFCConnections.

2. Choose Create.

3. Enter the following data (for an ABAP Connection here):


RFC Destination


The name should identify the bgRFC Supervisor.

Example: BGRFC_SUPERVISOR

Connection Type 3 (connection to SAP ERP).

Description

Description Enter a description (not stored with a description ID).

TechnicalSettings

Balance Load Not Selected.

Target Host No entry.

System number No entry.

Save as “IP” selected but no entry maintained.

Logon/Security

Language Enter desired log on language.

Example: EN

Client Enter the client of the back end system.

Example: 100



(C) SAP AG 53


User

Enter the user name.

The user needs the authorizations in the SAP_BC_BGRFC_SUPERVISOR

role.

PW status Enter the password of the user.

Current User Not selected.

Special Options

Transfer Protocol Select 2 – Classic with tRFC.


Result

You have now defined an RFC destination for your supervisor.



(C) SAP AG 54

Maintain Inbound Destination for bgRFC

The two newly created destinations need to be maintained as inbound destinations in the

bgRFC configuration using the SBGRFCCONF transaction. Within the inbound destination, a

new prefix should also be maintained. The prefix is used later on during queue processing.

You should maintain the entries in:

Define Inbound Destination

Define Supervisor Destination

Procedure

1. Launch the SBGRFCCONF transaction.

2. Choose the Define Inbound Dest. tab.

3. Choose Create and enter your previously created bgRFC destination.

4. Enter a Logon/Server group.

5. Enter a prefix for the upload queue.

HTTP_UPLOAD


7. Choose the Define Supervisor Dest. tab.

8. Choose Create.

9. Populate your previously maintained RFC connection for Supervisor under DefinedSupervisor Destination in the Destination field.


Result

You have maintained the RFC connection to handle tour uploads. If there are errors during

upload, the corresponding bgRFC queue is put on hold. The error can be analyzed and thequeue can be processed after a solution is found. Administration of the bgRFC queue can be

done using the SBGRFCCONF and SBGRFCMON transactions.



(C) SAP AG 55

Activate Internet Communication Services

SAP Direct Store Delivery provides a set of services that must be activated after installation of

the mobile app. Such services are required to support, for example, authorization requestsfrom SAP Mobile Platform or managing online requests from the mobile client to the back endSAP ERP.

Procedure

1. In SAP ERP, in the SAP Easy Access menu, choose Tools Administration

Administration Network HTTP Service Hierarchy Maintenance .

2. On the selection screen, choose hierarchy type SERVICE as filter criteria and execute

the selection.

3. On the next screen, choose the following Virtuelle Hosts / Services:

1. Go to default_host sap bc zcheck_user .

This service is used to authenticate the mobile users.

2. Go to default_host sap bc DSDng online .

This service is used for the synchronous online connection, for example,

online pricing.

3. Go to default_host sap bc DSDng upload_inform .

This service is used for data upload notification, sent by SAP MobilePlatform.

4. Go to default_host sap bc DSDng version .

This service is used to check the compliance of the data model used on themobile device with the one at SAP ERP.

Result

You have activated all the services needed for proper communication between SAP ERP andSAP Mobile Platform.



(C) SAP AG 56

General Parameter Value Maintenance

A set of different technical application parameters can be defined in order to configure SAP

Direct Store Delivery . These parameters are used to control, for example, the communicationto other systems or logging. The configuration of each setting can be done for a specificsubject and you can have certain keys and values per subject.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery General

Parameters , choose Maintain General Parameters Value.

2. Choose New entries


ParameterSubject

Parameter Key Description

CRM CRM_RFC_DEST RFC Destination which points to SAP CRM.

CRMDEFAULT_CRMACT_SEQ

Default sequence ID of newly created CRMactivities in list of activities for visits.

OCS CRT_DLT_POLL_SECS

Time for which the system tries to push a deltapackage (tour) to SAP Mobile Platform whentriggered by the front end. The number enteredrepresents seconds.

SUP COMM_BLOCKED

A checkbox that indicates whether or not thecommunication between the SAP ERP back endand SAP Mobile Platform should be blocked, forexample, due to maintenance reasons, in order toavoid inconsistencies

SUP HTTP_COMM_LOG

This checkbox is obsolete and not used.

HTTP communication can be monitored via the

Internet Communication Manager (see the SAPHelp Portal at http://help.sap.com SAP

NetWeaver Platform 7.3 Including Enhancement

Package 1 Internet Communication Manager ).

SUP PERF_MEASURE

This checkbox indicates whether or not theperformance of downloading and uploading datafrom/to the SAP ERP back end from/to SAP MobilePlatform should be tracked. The results can bemonitored via the

/EMSE/PERFORMANCE_ANALYSIS program.

SUP STRUST_APPLIC

This value represents the key maintained for

encryption in the SSFAPPLIC table.

http://help.sap.com/






(C) SAP AG 57

ParameterSubject

Parameter Key Description

Refer to the Master Guide for SAP Direct StoreDelivery .

SUP UPLD_BGRFC_DEST RFC destination of the inbound queue of thebgRFC.

SUP UPLD_BGRFC_QUEUE Name of the bgRFC queues to be created (onlyprefix).

SUP UPLD_PACKSIZE

This parameter represents the number of uploadoperations that are to be read in one session by theSAP ERP back end from SAP Mobile Platform.

Example: 10000


Result

The technical parameters are maintained.



(C) SAP AG 58

Define Parameter Subjects

You maintain parameter subjects for general parameter Customizing of SAP Direct Store

Delivery . A parameter subject restricts the parameter for a single system, for example, forSAP Mobile Platform.

Procedure

In the case of customer coding enhancements, it might be necessary to define your ownparameter subjects. You can do this in the following steps:


Parameters , choose Define Parameter Subjects.

2. Choose New entries and enter the following data (if required):


Parameter Subject

Specifies a parameter subject.

SAP delivers the following subjects:

o CRM (SAP Customer Relationship Management )

o OCS (Occasionally Connected Scenario)

o SUP (SAP Mobile Platform)


Result

You have defined your own parameter subject for customer enhancements.



(C) SAP AG 59

Define Parameter Keys

A parameter key is used in the program code as a condition for the current process. A

process key has a parameter value and this value controls the running process. This value isdelivered by SAP. For customer enhancement, it might by necessary to define your ownparameter key additionally.

Procedure


Parameters , choose Define Parameter Keys.

2. Choose New entries and enter the following data (if required):


Parameter Key

Specifies the parameter key.

Keys delivered by SAP are named in General Parameter ValueMaintenance [Page 56].

ParameterDescription

Contains a description of your parameter key.


Result

You have defined your own parameter key to be used in your program.



(C) SAP AG 60

Configuration of Basic Functions

To use the SAP Direct Store Delivery and Vehicle Space Optimization (VSO) functions in the

DSD back end, you must activate the DSD application component as well as the VSOapplication component. In addition, if you want to implement a mobile DSD scenario, youneed to decide whether or not you want to use multiple sales area processing. If you want todownload CRM activities to the mobile client, you need to activate it as well.

Process

You can find the steps for this process in Customizing for Logistics Execution under SAP

Direct Store Delivery Basic Functions . This section covers the following steps:

1. Activate Direct Store Delivery [Page 61]

2. Manage Multiple Sales Areas Processes [Page 62]

3. Activate Vehicle Space Optimization [Page 63]

4. Activate CRM Scenario [Page 64]



(C) SAP AG 61

Activate Direct Store Delivery

In this IMG activity, you enable the Direct Store Delivery (DSD) application component. If you

want to use DSD in your system, you must first activate this checkbox.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Basic

Functions , choose Activate Direct Store Delivery .

2. Select the DSD Active checkbox.

3. Save your entry.

Result

Once the DSD Component has been activated, you are able to access all the functions in thisapplication.



(C) SAP AG 62

Manage Multiple Sales Areas Processes

In this IMG activity, you specify that you want DSD-specific processes to be carried out for

one or more sales areas. This allows you to maintain and enable the DSD scenario fordifferent sales areas and serves as an additional key for assigning deliveries to visit lists andshipments.

If you want to use the mobile DSD process just with one sales area, you must select theSingle-SA Processes checkbox in this activity.

Procedure


Functions , choose Manage Multiple Sales Areas Processes.

2. Select the Single SA-Procs (Single Sales Area Processes) checkbox if you want to

use just one sales area.


Result

Once you have activated the Single-SA Procs checkbox, the system activates appropriatechecks in DSD-relevant applications, for example, Visit Control. These checks prevent youfrom being able to enter cross-sales area objects. In other words, it is not possible to assigncustomers from different sales areas to the same visit plan or to create a driver for differentsales areas.



(C) SAP AG 63

Activate Vehicle Space Optimization

In this IMG activity, you enable the Vehicle Space Optimization (VSO) application component.

You must activate this component (incurring extra licence costs) to call the optimizationalgorithm of a third-party provider via an interface.

Prerequisites

The optimization algorithm (OCX file) of the third-party provider needs to be installed in theoperative system. You must activate and register the OCX file of the third-party provider. Thealgorithm also must be accessible through a Remote Function Call (RFC) connection. Thisprerequisite is not checked during activation but VSO does not work without it.

Procedure


Functions , choose Activate Vehicle Space Optimization.

2. Select the VSO Active checkbox.

3. Save your entry.

Result

Once the VSO component has been activated, you are able to access all the functions in thisapplication.



(C) SAP AG 64

Activate CRM Scenario

In this IMG activity, you indicate whether or not the CRM scenario is active on the SAP Direct

Store Delivery mobile app. If you want to download CRM activities to the client, you must firstselect the checkbox to activate the CRM scenario.

Procedure

1. In SAP ERP Customizing for Logistics Execution under SAP Direct Store Delivery

Basic Functions , choose Activate CRM Scenario.

2. Select the CRM Scenario Active checkbox.

3. Save your entry.

ResultOnce SAP CRM has been activated, you are able to use CRM activities on the client.



(C) SAP AG 65

Configuration of DSD Connector Cockpit

The DSD Connector Cockpit is located on the DSD Connector. It serves to link mobile

devices to drivers and vehicles in order to transfer tour data to the mobile devices concerned.The DSD Connector Cockpit is called on the SAP application menu by the /DSD/ME_CPT transaction code.

Prerequisites

You have defined an bgRFC destination pointing to SAP Mobile Platform and the MobileInfrastructure Server Component if you run the SAP mDSD solution and SAP Direct StoreDelivery in parallel.

Process

1. On the Assign Driver/Vehicle tab, you maintain the driver/vehicle assignment to amobile device.

2. On the Driver Master tab, you display driver master data.

3. On the Vehicle Master tab, you display vehicle master data.



(C) SAP AG 66

Link Mobile Device to Driver and Vehicle

On this screen, you establish the link between individual mobile devices and drivers and

vehicles. You link each driver and vehicle to a specific middleware system if you run bothsolutions in parallel.

Every shipment or visit list that is being downloaded to the middleware contains informationabout the driver and the vehicle assigned to this shipment or visit list. The DSD Connectortakes this information and identifies the correct middleware based on entries in this table andthus determines to which driver and vehicle the tour data should be distributed.

In SAP Direct Store Delivery , the driver can pick up any mobile device and perform thedownload to the mobile client for one tour.

Prerequisites

System connections between the DSD Connector and the DSD back end (includingthe Pricing Engine Component) are established.

System connections between the DSD Connector and SAP Mobile Platform (and theMobile Engine Server if you run SAP mDSD in parallel) are established.

Mobile engine IDs are maintained for the middleware system.

Mobile device groups are defined.

The SAP ERP user for the driver is maintained and the password is set up.

Procedure

1. Enter the /n/DSD/ME_CPT transaction code.

2. On the Assign Driver/Vehicle tab, choose Insert Row .


FieldName

User Action and Default Values

Mobile ID

<Mobile ID >

Select the ID for your mobile device from the input help. For easier

processing, you can use the filter function from the input help.

The user here represents the SAP ERP user of your driver.

MobileEngine ID

<MEID >

Select the ID of the Mobile Engine Server on which the mobile device isrunning from the input help.

The system can use this ME ID to distinguish which DSD solution is used for



(C) SAP AG 67

FieldName


your driver if you run SAP mDSD and SAP Direct Store Delivery 1.0 inparallel.

Driver

<driverID >

Select the ID of the driver to whom the device should be assigned from theinput help.

Vehicle

<vehicleID >

Select the ID of the vehicle to which the device should be assigned from theinput help.

Group

<group name>

Select the name of the group to which the device will be assigned from the

input help.

MiniAppName

The value for this field is entered automatically by the system.

Version The value for this field is entered automatically by the system.


Result

Shipments/visit lists created in the DSD back end contain information about the driver and

vehicle. Whenever the DSD Connector receives such shipments/visit lists, the systemforwards the data to the corresponding driver/user depending on the driver/vehicleassignment maintained on this Assign Driver/Vehicle tab of the DSD Connector Cockpit .



(C) SAP AG 68

Display Driver Master Data

On the Driver Master tab, the system displays data records for all available drivers that are

currently maintained in the DSD back end. When calling the transaction for the DSDConnector Cockpit , these data records are pulled from the tables of the driver master data inthe DSD back end and are displayed in the DSD Connector Cockpit for informationalpurposes.

Prerequisites

System Connections between the DSD Connector and the DSD back end (includingthe Pricing Engine Component) are established.

System Connections between the DSD Connector and SAP Mobile Platform (and theMobile Engine Server if you run SAP mDSD in parallel) are established.

Procedure

1. Enter the transaction code /n/DSD/ME_CPT.

2. Choose the Driver Master tab.

Result

The system displays the data records for drivers. When you choose a record, the systemopens a three-window screen with information about the transportation planning point,license, and lock times.



(C) SAP AG 69

Display Vehicle Master Data

On the Vehicle Master tab, the system displays data records for all available vehicles that are

currently maintained in the DSD back end. When calling the transaction for the DSDConnector Cockpit , these data records are pulled from the tables of the vehicle master data inthe DSD back end and are displayed in the DSD Connector Cockpit for informationalpurposes.

Prerequisites

System connections between DSD Connector and the DSD back end (including thePricing Engine Component) are established.

System connections between DSD Connector and the Mobile Engine Server (if yourun SAP mDSD in parallel) are established.

Procedure

1. Enter the /n/DSD/ME_CPT transaction code.

2. Choose the Vehicle Master tab.

Result

The system displays the data records of vehicles. When you choose a record, the systemopens a three-window screen with information about the transportation planning point,license, and lock times.



(C) SAP AG 70

Pricing on Mobile Devices

In this menu option, you implement steps required for enabling the pricing retrieval process.

This process is handled by the component called the Pricing Data Extractor (also knowntechnically as the Pricing Data Extractor Core). It must always reside on the same system asthe DSD back end.

The Pricing Data Extractor is designed as a component that is independent from DSD, whichmeans that it can potentially be triggered by other solutions. The logic inside the DSDConnector that communicates with the Pricing Data Extractor is the Pricing Data Extractor

Add-on. The Pricing Data Extractor Add-on is a group of function modules that is included inthe DSD Connector and that always resides on the DSD Connector.

For retrieving the pricing condition records, the DSD Connector (Pricing Data Extractor Add-

on) calls the /EMSE/ME_DE_TRIGGER function module on the DSD Connector. This function

module submits the selection criteria to the Pricing Data Extractor on the DSD back end

which, in turn, retrieves the relevant condition records and places them into the localdatabase of the DSD back end. As soon as the retrieval process is completed, the PricingData Extractor informs the DSD Connector about the readiness status of the pricing data for aspecific shipment.

Process

For the pricing retrieval process to function correctly, it is necessary to perform the followingsteps:

1. Define Block Condition Types for Mobile Pricing [Page 71]

2. Configuration of Pricing Data Extractor [Page 73]

1. Define General Settings for Pricing Data Extractor [Page 74]

2. Enhance Pricing Selection Criteria for Pricing BAdI [Page 75]



(C) SAP AG 71

Define Block Condition Types for Mobile Pricing

In this IMG activity, you can control for which condition types used in a mobile scenario a

check is performed. The check is carried out during the following:

Creation of new condition records

Changes to existing condition records

You can further define a safety period (number of days before the validity start of a conditionrecord) in which the following types of messages occur when mobile users try to changecondition records:

Error messages

Users are blocked by error messages and the transaction is left.

Warning messages

Users are asked to continue saving or to cancel the transaction.

Error messages are evaluated prior to warning messages. This means that you can set uperror and message types for the same condition type.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Handheld

Connectivity General Settings , choose Block Condition Types Changes for MobilePricing.

2. Switch to change mode and choose New Entries.

3. Maintain the table as follows:


App

Select an application type and desired condition type from the input help.

Example: V PR00

The application type depends on the condition type. Make sure that yourcondition type belongs to the application area “V”.

CnTyPrepopulated based on selection for previous field.

Example: PR00

Message Type Select message type from input help.

Safety Period(Days) Define a safety period in days.



(C) SAP AG 72


Result

Depending on your settings, a check is carried out during condition record maintenance.



(C) SAP AG 73

Configuration of Pricing Data Extractor

With the Pricing Data Extractor, you retrieve the correct pricing condition records for a given

shipment from the DSD back end and place them in the local database of the DSD back end.The Pricing Data Extractor considers whether or not the multiple sales area modes are activeto determine the correct pricing condition records.

Process

The following IMG activities for this process are found in Customizing for Sales and

Distribution under Basic Functions Pricing :

1. Define General Settings for Pricing Data Extractor [Page 74]

2. Enhancing Pricing Selection Criteria for Pricing BAdI [Page 75]



(C) SAP AG 74

Define General Settings for Pricing Data Extractor

In this IMG activity, you maintain general settings for the Pricing Data Extractor.

Prerequisites

You have defined an RFC Destination for the communication between the DSD back end andthe DSD Connector.

Procedure

1. In the DSD back end, in Customizing for Sales and Distribution under Basic

Functions Pricing Pricing Data Extractor for Mobile Device , choose DefineGeneral Settings.




ConfigureKey

ADDON_RFC

ConfigureValue

Enter the RFC destination pointing from the Pricing Data Extractor (DSDback end) to the calling system (DSD Connector).

4. Select Enter.

5. Select the next line.

Repeat step 3. and 4. to define a second entry with the following data:


ConfigureKey

LOCAL_CURRENCY

Configure

Value

Enter the currency you want to use in the Pricing Data Extractor. The PricingData Extractor is a standard application that therefore requires its owncurrency field.

Example: EUR




(C) SAP AG 75

Enhance Pricing Selection Criteria for Pricing BAdI

To enhance the pricing selection criteria, a BAdI was created in the Data Extractor Trigger

(the /EMSE/ME_DE_TRIGGER function module). It is called after the trigger has finished

preparing the selection criteria and before the Pricing Data Extractor is called.

The implementation of this BAdI is particularly important for the preseller scenario as, byimplementing this BAdI, materials are made available for a preseller scenario on the mobiledevice.

Procedure

1. To enhance your customer-specific business logic, use the SE19 transaction to

implement the /DSD/ME_DE_TRIGGER_E definition.

2. You need to add codes to the SEL_CRI_EXTRA_PROCESS method.

The SEL_CRI_EXTRA_PROCESS method is also necessary to select pricing

conditions for materials that are not included in an order or a delivery or in areference sales document of a visit list.

Definition: /DSD/ME_DE_TRIGGER_E

Interface: /DSD/IF_EX_ME_DE_TRIGGER_E

Method: SEL_CRI_EXTRA_PROCESS (Extra Process for Selection Criteria)

Parameters

MEUSER Importing Type /DSD/ME_MEUSER

MEMBLID Importing Type /DSD/ME_MBLID

TOURID Importing Type /DSD/ME_TOURID

T_CUSTOMER Changing Type /DSD/ME_PE_CUST_LT_T

T_MATERIAL Changing Type /DSD/ME_PE_MAT_LT_T

T_DATE Changing Type /DSD/ME_PE_DATE_LT_CV_T

T_UOM Changing Type /DSD/ME_PE_UOM_LT_T

T_ENHANCEMENT001 Changing Type /DSD/ME_ENHANCEMENT_T

USERKEY Changing Type /DSD/ME_PE_KEY

VISITDATE Changing Type SY-DATUM



(C) SAP AG 76

MEUSER Importing Type /DSD/ME_MEUSER

LANGUAGE Changing Type SY-LANGU

DELETE Changing Type /DSD/ME_PE_ACTION

UOM_TYPE Changing Type C

INTERVAL Changing Type I

MEUSER Changing Type /DSD/ME_MEUSER

Result

Once the BAdI is implemented, the Pricing Engine (Data Extractor Core) is able to extractpricing data for criteria that are not necessarily bound to a specific shipment.

ExampleThe following is an example for a customer-specific download of conditions that are related toone specific material 0000000022 and are not bound to the shipment:

1. method /DSD/IF_EX_ME_DE_TRIGGER_E~SEL_CRI_EXTRA_PROCESS.2. 3. data:4. 5. ls_mat type /DSD/ME_PE_MAT_LT.6.

7. ls_mat-MATNR = '0000000022'.8. 9. append ls_mat to t_material.10. 11. endmethod.

The following is an example that is used to customize the valid date period of conditions (fromtoday to 4 days in the future) which needs to be downloaded. The default logic is used todownload the condition which is available today:

1. method /DSD/IF_EX_ME_DE_TRIGGER_E~SEL_CRI_EXTRA_PROCESS.2.

3. interval = 4.4. 5. endmethod.

The T_ENHANCEMENT001 table is used to transfer customer-specific information that is

unique to DSD, for example, tour information, to the Pricing Data Extractor as it is not set upfor the tour concept. In the Pricing Data Extractor, customers can add their own logic in the

BADI implementation of /DSD/PE_SET_DRSTAT with the information in

T_ENHANCEMENT001 .

The following is an example of this type of usage:

1. method /DSD/IF_EX_ME_DE_TRIGGER_E~SEL_CRI_EXTRA_PROCESS.2.



(C) SAP AG 77

3. lds_enhancement001-objectkey_id = '0001'.4. 5. lds_enhancement001-field_value = tourid.6. 7. append lds_enhancement001 to T_ENHANCEMENT001.8. endmethod.



(C) SAP AG 78

Handheld Connectivity

Mobile clients constitute the front end of the DSD process. Usually, they take the form ofhandheld devices.

This section deals with all the Customizing settings that the system needs for handling theprocess of mapping and forwarding data correctly during the data download. It also includesthe settings that are necessary for the upload process at the end of a tour.

Prerequisites

An RFC Destination pointing to the DSD Connector is defined.

Business Functions /DSD/BF, /DSD/ARC, /DSD/OCS, and

/EMSE/ACITVATE_FIELDS are activated.

Process

The Customizing tables for maintaining DSD handheld connectivity are located in the DSD

Connector under Logistics Execution SAP Direct Store Delivery Handheld Connectivity .

Set Up the Connections Between the Back End and the Handheld

To set up the connections between the back end and the handheld, you need to maintain thefollowing Customizing activities:

1. General Settings [Page 121]

2. Upload [Page 126]

3. DSD Connector Settings [Page 166]

Use Front End Functions

To use front end functions, you need to maintain the following Customizing activities:

1. Electronic Signature [Page 105]

2. Barcode Support for Recording Visit Times on Mobile Device [Page 239]

3. Invoice Reprint as Copy [Page 243]

4. Listing and Exclusion [Page 244]

5. Deal Conditions [Page 254]

6. Manual Discounts [Page 236]



(C) SAP AG 79

SAP CRM Integration

In SAP Direct Store Delivery, you can download CRM activities to a tour created in SAP ERP.

For this purpose, you need to make settings in Customizing in both the SAP ERP and SAPCustomer Relationship Management (SAP CRM) systems. Furthermore, some master dataneeds to be linked to allow the selection of CRM activities.

This chapter describes the steps that are necessary to allow you use CRM activities for SAPDirect Store Delivery .

These Customizing settings need to be done in addition to the mandatory settings for DSDCustomizing. Firstly, the settings for SAP ERP are described and then the settings for SAPCRM.

SAP Direct Store Delivery 1.0 supports the following CRM activity items:

Attachments

Surveys

Notes

Activity journals

Partners

Marketing attribute sets

There are the following two ways of downloading CRM activities:

If you create CRM activities in SAP CRM, then these CRM activities are read during aDSD download.

CRM activities can be created based on certain settings when a download istriggered.

Both ways are valid for occasional connected scenarios (OCS).

In addition, you can download marketing attributes for customers and contact persons.Contact persons are downloaded from SAP CRM as soon as the CRM scenario is activated inSAP ERP.

Furthermore, a preseller or delivery driver can create new CRM activities on the mobile client.

Such activities are uploaded with the final tour upload.

Process

1. Make settings in Customizing in SAP ERP (see SAP ERP Settings [Page 80]).

2. Make settings in Customizing in SAP CRM (see SAP CRM Settings [Page 86]).



(C) SAP AG 80

SAP ERP Settings

To enable the use of CRM activities on the client, you need to make settings in Customizing

in SAP ERP.

Prerequisites

The CRM scenario has been activated. For more information, see Activate CRM Scenario[Page 64].

Process

1. Define RFC Destination for SAP CRM [Page 81]

Make settings in SAP ERP Customizing for SAP NetWeaver under Application

Server IDoc Interface / Application Link Enabling (ALE) Communication Create

RFC Connections .

2. Maintain General Parameter Values [Page 83]

Make settings in SAP ERP Customizing for Logistics Execution under SAP Direct

Store Delivery General Parameters Maintain General Parameter Values .

3. Maintain Download Setting for CRM Activities [Page 85]

Make settings in SAP ERP Customizing for Logistics Execution under SAP Direct

Store Delivery Handheld Connectivity Additional Data Download Maintain

Download Setting for CRM Activities .



(C) SAP AG 81

Define RFC Destination for SAP CRM

You have to enable data distribution from SAP CRM to the DSD Connector in SAP ERP. In

this IMG activity, you define the technical parameters for the Remote Function Call (RFC)destinations. The RFC is controlled by the RFC destination parameters.

RFC destinations must be assigned to general parameters (see Maintain General ParameterValues [Page 83]).

We recommend giving the RFC destination the same name as the SAP CRM client. Thisnaming convention allows you to easily identify which system and RFC destinations areconnected later.

Procedure1. In SAP ERP Customizing for SAP NetWeaver, define an RFC destination by

choosing Application Server IDoc Interface / Application Link Enabling (ALE)

Communication Create RFC Connections .

2. Choose Create.



RFC

Destination

We recommend you use the same naming format as the one used to

identify the SAP CRM system.

ConnectionType

3 (Connection to ABAP System)

Description

Description Enter a description (this is not stored with the description ID).




Technical Settings

Balance Load Selected No.

Target Host Enter the host name of the SAP CRM system.

System Number Enter the system number of the SAP CRM system.

Save as Select IP Address.

Logon & Security



(C) SAP AG 82


Language Enter the abbreviation for the desired language.

Client Enter the client number of the SAP CRM system.

User If you do not select the Current User option, enter the logon/user ID

of the SAP CRM system.


Trust Relationship Select No.

Status of SecureProtocol

Select Inactive.


Result

You have defined an RFC destination to establish communication between SAP ERP andSAP CRM.



(C) SAP AG 83

Maintain General Parameter Values

In this IMG activity, you maintain general parameter values that are used during DSD

processing.

The following parameters are delivered by SAP:

Parameter Description Example

DEFAULT_CRMACT_SE Q

Defines the activitysequence on the client if nospecial activity sequence ismaintained.

999, see note below.

CRM_RFC_DEST

Defines the SAP Direct

Store Delivery to SAP CRMconnection for RFC.

Enter the RFC connection you

have defined here (see DefineRFC Destination for SAP CRM[Page 81]).

The DEFAULT_CRMACT_SEQ parameter influences the sequence of CRM activities on the

client. In SAP ERP Customizing for Logistics Execution under SAP Direct Store Delivery

Handheld Connectivity DSD Connector Settings Mobile Device Settings Define Tour

Scenario Settings , you can define activity sequences for tour scenarios. If no sequence ismaintained for CRM activities in Customizing, the system uses this entry and, as a result,CRM activities are listed at the end of the activity list in the visit overview on the client.

Procedure

Check if the table already contains the values, otherwise, maintain them as follows:


General Parameters , choose Maintain General Parameter Values.




Parameter Subject Select CRM from the input help.

Parameter Key Enter your parameter key used for SAP CRM.

Optional Parameter Key Empty



Parameter Value Check/Enter proposed values as described in the table above.




(C) SAP AG 84

Result

The required parameters are now maintained.



(C) SAP AG 85

Maintain Download Setting for CRM Activities

In this IMG activity, you set defaults for SAP CRM handling of the following:

Shipments

The default values are automatically taken during the download from SAP CRM. Thesystem considers this time setting (per visit) when selecting activities from SAP CRM.

Visit plan types

The default values are taken during the creation of a visit plan. This is a proposal thatcan be changed in the visit plan.

If you want to enable the collection of CRM activities for certain shipment types or visit plans,select the CRM Act. (Collect CRM Activities) checkbox.

Procedure


Handheld Connectivity Additional Data Download , choose Maintain DownloadSetting for CRM Activities.




Shp/VP Type Enter a shipment or visit plan type from input help.

Example: MPS

CRM Act. Select the checkbox when you want to download CRM activities.

CRM Act. Max. Mins Enter the time in minutes per activities per visit.

Example: 10

4. Save your entries

Result

You have now defined all shipments/visit plans that are relevant for downloading CRM Activities.



(C) SAP AG 86

SAP CRM Settings

To enable the use of CRM activities on the client, you need to make settings in Customizing

in SAP CRM.

Process

1. Define RFC Destination for SAP ERP [Page 87]

Make settings in SAP CRM Customizing for SAP NetWeaver under Application

Server IDoc Interface / Application Link Enabling (ALE) Communication Create

RFC Connections .

2. Maintain the following cross-application general parameter values:

o Maintain General Parameter Key Values [Page 89]

o Maintain General Parameter Subject Values [Page 90]

o Maintain General Parameter Values [Page 91]

Make settings in SAP CRM Customizing for Customer Relationship Management

under SAP Direct Store Delivery General Parameters Cross Application

Parameters .

3. Maintain the following general parameters:

o Define Transaction Types [Page 93]

o Define CRM Activity Authorization [Page 95]

o Define CRM Activity Mass Generation Depending on Tour Scenario [Page97]

o Define Attachment Types [Page 99]

o Define Activity Status of Past Activities [Page 100]

o Define Attribute Sets [Page 101]

o Define Currencies [Page 102]


under SAP Direct Store Delivery General Parameters .

4. CRM Business Add-lns (BAdIs) [Page 103]


under SAP Direct Store Delivery Business Add-Ins .



(C) SAP AG 87

Define RFC Destination for SAP ERP

You have to enable data distribution from SAP CRM to the DSD Connector in SAP ERP. In

this IMG activity, you define the technical parameters for the Remote Function Call (RFC)destinations. The RFC is controlled by the RFC destination parameters.

RFC destinations must be assigned to the general parameters (see Maintain GeneralParameter Values [Page 91]).

We recommend giving the RFC destination the same name as the SAP ERP client. Thisnaming convention allows you to easily identify which system and RFC destinations areconnected later.

Procedure1. In SAP CRM Customizing for SAP NetWeaver, define an RFC destination by

choosing Application Server IDoc Interface / Application Link Enabling (ALE)

Communication Create RFC Connections .

2. Choose Create.



RFC

Destination

We recommend you use the same naming format as the one used to

identify the DSD SAP ERP system.

ConnectionType

3 (Connection to ABAP System)

Description

Description Enter a description (this is not stored with the description ID).




Technical Settings

Balance Load Select No.

Target Host Enter the host name of the DSD SAP ERP system.

System Number Enter the system number of the DSD SAP ERP system.

Save as Select IP Address.

Logon & Security



(C) SAP AG 88


Language Enter the abbreviation for the desired language.

Client Enter the client number of the DSD SAP ERP system.

User If you do not select the Current User option, enter the logon/user ID

of the DSD SAP ERP system.


Trust Relationship Select No.

Status of SecureProtocol

Select Inactive.


Result

You have defined an RFC destination to establish communication between SAP CRM andSAP ERP.



(C) SAP AG 89

Maintain General Parameter Key Values

A parameter key is used in the program code as a condition for the current process. A

process key has a process value and this value controls the running process.

The following parameter keys are delivered by SAP:

Key Description

ACT_MASS_GEN_BREAK Mass gen.: Break between two activities in minutes

ACT_MASS_GEN_DESCR Default description for a DSD-driven activity

ACT_MASS_GEN_START_ T

Start time for mass activity generation

DRIVER_EXT_NUM_TYPEMapping ID type for DSD driver to a SAP CRM businesspartner (BP)

DSD_RFC_DEST RFC destination to DSD for F4 help shipment types

EMP_MD_CALCULATION Calculation of relevant master data for partners

Customers can define their own parameter key values if they enhance the process of SAPDirect Store Delivery . This requires coding enhancements as well.

Procedure

1. In SAP CRM Customizing for Customer Relationship Management under SAP

Direct Store Delivery General Parameters Cross Application Parameters , chooseGeneral Parameter Key Values.




Parameter Subject Enter your used parameter subject.




(C) SAP AG 90

Maintain General Parameter Subject Values

A parameter subject restricts the parameter for a single system, for example, for SAP Direct

Store Delivery (DSD) or SAP CRM.

The following parameter subjects are delivered by SAP:

Parameter Subject

CRM

DSD

Procedure

1. In SAP CRM Customizing for Customer Relationship Management under SAPDirect Store Delivery General Parameters Cross Application Parameters , chooseGeneral Parameter Subject Values.




Parameter Subject Enter a parameter subject.




(C) SAP AG 91

Maintain General Parameter Values

In this IMG activity, you maintain general parameter values for parameter subjects and

parameter keys.

The following parameters are used:

Parameter Description Example Value

ACT_MASS_GEN_START_T

Defines the start of theworking day.

Time format.

Example: 08:00

DRIVER_EXT_NUM_TYPE Defines the externalmapping key for ERP

driver to CRM employee.

See note below.

ACT_MASS_GEN_DESCR Defines the defaultdescription for thegenerated activities.

Example:

DSD Driven Act.

DSD_RFC_DEST

Defines the SAP CRM toSAP Direct StoreDelivery connection forRFC.

Enter the RFC connection youhave defined here (see DefineRFC Destination for SAP ERP)[Page 87]]

EMP_MD_CALCULATION Defines how to find theemployees for the tour

download.

See note below.

ACT_MASS_GEN_BREAK Defines the breakbetween each CRMactivity in minutes.

Example: 10

DRIVER_EXT_NUM_TYPE

There are two scenarios as follows:

o SAP HR is in place

Your driver has the same personal number in SAP ERP and in SAP CRM. Inthat case, you do not need to maintain this entry.

o SAP HR is not in place

You need to map your driver from SAP ERP (customer number) to a CRMemployee number. This can be done by maintaining the driver as anemployee in SAP CRM using an external number. In that case, enterCRM001 as the value here. This is required because an employee ismandatory for CRM activities.

EMP_MD_CALCULATION

Defines how to find the employees for the tour download using one of the following:



(C) SAP AG 92

o Territory

Enter value 1

o Sales organization

Enter value 2

Procedure


Direct Store Delivery General Parameters Cross Application Parameters , chooseGeneral Parameters.




Parameter Subject

Select a parameter subject from the input help.

Example: CRM

DSD is just needed for the DSD_RFC_DEST parameter.

Parameter Key Select a parameter key from the input help.

Parameter Value Enter the parameter value as described above.


Result

The control parameters have been set up.



(C) SAP AG 93

Define Transaction Types

In this IMG activity, you make settings for downloading activities from SAP CRM to the DSD

Connector in SAP ERP.

Usually, a transaction type for CRM activities has a date on which it should be executed. Inthis Customizing table, you can control which date range and/or what amount of createdactivity types you want to download for a specific tour.

Furthermore, you can control which offline-created activity types should be mandatory oncecreated on the client. This has an impact on the visit status calculation on the client side.

Procedure


Direct Store Delivery General Parameters , choose Define Transaction Types.



FieldName


Trans.Type

Select a transaction type from the input help.

Example: 2020

Transaction types need to be defined in SAP CRM standard Customizing.

Category

Select a category from the input help.

A category is a more specific grouping within the activity type that controlswhich functions are available for each activity type.

Categories need to be defined in SAP CRM standard Customizing.

Days Past Enter the days for past activities to be downloaded.

Example: 10

Days Ahead

Enter the days for future activities to be downloaded.

Example: 10

Max. Past

Enter the maximum number of activities from the past that should bedownloaded.

Example: 5

Max. Enter the maximum number of activities for the future that should be



(C) SAP AG 94

FieldName


Ahead downloaded.

Example: 5

Mandatory Select the checkbox to define all offline-created activities on the client asmandatory.


Result

The entries are saved and are considered for the download of activities.



(C) SAP AG 95

Define CRM Activity Authorization

In this IMG activity, you can define authorization rights per tour scenario. Authorization rights

can be given for the following two authorization subjects:

Activities

Attachments

Procedure


Direct Store Delivery General Parameters , choose Define CRM Activity Authorization




Tour Scenario Select tour scenario from input help.

Example: 01 Pre-Sales Scenario

S/VP

Select a shipment or visit plan type from the input help.

Example: MPS

You can leave it blank and this entry is then valid for all shipment or visitplan types.

Trans.Type Select a transaction type from the input help.

Example: 2020

AuthorizationSubject

Enter an authorization subject from input help.

Example: Attachment

Only Activity and Attachment are supported.

Read Controls whether or not this process type and all dependent objects willbe downloaded.

New Controls whether or not the mobile user can select this process type fornew activities on the mobile device.

Edit

Controls whether or not the mobile user can edit the activity on the

mobile device



(C) SAP AG 96


Delete

Controls whether or not the mobile user can delete attachments on themobile device.

This process type is only relevant for Attachment authorization subjects.


Result

You have defined the CRM activity authorizations.



(C) SAP AG 97

Define CRM Activity Mass Generation Dependingon Tour Scenario

In this IMG activity, you can make settings for the mass generation of activities in SAP CRMdepending on the following:

Occasionally connected scenario (OCS)

Tour scenario

Customer sales area

Target group assignment

You can define mass generation based on the certain parameters.

Procedure


Direct Store Delivery General Parameters , choose Define CRM Activity MassGeneration Depending on Tour Scenario




OC Rel. If you select the OC Rel.(Occasionally Connected Relevant) checkbox,CRM activities are also created in an occasionally connected scenario.

Tour Scen. Select tour scenario from input help.

Example: 01 Pre-Seller

S/VP Enter shipment or visit plan type from input help.

Example: MPS

SalesOrganization ID

Enter the sales organization, for which activities should be created, frominput help.

Dis. Chan. Enter the distribution channel from input help.

Division Enter the division from input help.

Target Group Enter the desired target group from input help.

Trans. Type Select transaction type from input help.

Category Will be filled depending on entered transaction type above.

Valid From

Sets date from which an activity is active.

Example: 01.02.2013



(C) SAP AG 98


Valid To Sets Valid To date for activity creation.

Example: 28.06.2013

Priority

Defines the priority of an activity.

All activities with priority 1 are mandatory on the client.

Activity Reason Select an appropriate reason code for your activity from the input help.

Act. Dur. Specifies the duration in minutes of activities created by mass generation.

Transaction

Desc.

Short description for an activity.


Result

Based on your entries, the system creates new activities based on your shipment or visit plantype.



(C) SAP AG 99

Define Attachment Types

You can download attachments to the device for use while performing CRM activities. Due to

security reasons and to control the transfer volume, you need to limit the size of suchattachments.

Procedure


Direct Store Delivery General Parameters , choose Define Attachment Types




Attach. Type

Enter the attachment type image/jpeg .

Currently, only image/jpeg is supported.

Attach. Size (in Bytes) Enter the desired size in bytes.

Example: 1000000 for 1 Mbyte


Result

You have now defined the attachment type allowed.



(C) SAP AG 100

Define Activity Status of Past Activities

In this IMG activity, you can control the download for past activities depending on their status.

Here, you can set up all statuses that should be considered during download.

Depending on the maintained status profile in the CRM activity, the following status valuesare used for the CRMACTIV profile (default):

I1002 – Open

I1003 – In Process

I1005 – Completed

I1032 – Canceled

Procedure


Direct Store Delivery General Parameters , choose Define Activity Status of Past Activities.




Trans. Type

Select transaction type from input help.

Example: 2020

Category Will be filled depending on entered transaction type above.

Back De St Enter a back end device status that should be considered for download.

Example: I1032


Result

You have defined the status for past activities that are considered for download from SAPCRM to the DSD Connector in SAP ERP.



(C) SAP AG 101

Define Attribute Sets

In this IMG activity, you can assign CRM marketing attribute sets to business partner

categories for downloading from SAP CRM to the DSD Connector in SAP ERP.

Procedure


Direct Store Delivery General Parameters , choose Define Marketing AttributeSets.




Attribute Set Select attribute set from input help.

Example: CPPPRO

BPC Select one of the business partner category for your attribute set.

Example: 1 Person


Result

You have defined the marketing attributes that are downloaded to the client.



(C) SAP AG 102

Define Currencies

In this IMG activity, you can define currencies for downloading from SAP CRM to the DSD

Connector in SAP ERP. These currencies are used on the client for CRM activity items suchas audits, survey, and journals.

If direct store delivery-relevant currencies are not maintained, all available currenciesare downloaded from SAP CRM to the DSD Connector.

These currencies have no impact on the mobile pricing engine. For the mobile pricingengine, the currency is maintained in SAP ERP.

Procedure


Direct Store Delivery General Parameters , choose Define Currencies.



FieldName


Crcy

Maintain at least the currency that you are using in SAP CRM for your mobileDSD process.

Example: EUR


Result

You have defined the currencies used for your activities.



(C) SAP AG 103

CRM Business Add-lns (BAdIs)

In the SAP CRM component of SAP Direct Store Delivery , a number of Business Add-In

(BAdIs) are available that allow you to individualize the standard DSD process according tocustomer-specific needs by influencing this standard process without making modifications.

Procedure

1. In SAP CRM in Customizing for Customer Relationship Management choose SAP

Direct Store Delivery Business Add-Ins .

2. Choose from the following BAdIs, listed in the table below alongside a briefdescription of their potential effects, which can be used within the DSD component:

BAdI Description

/CMSE/BADI_MAP_STATUS

Mapping of CRM Activity Status and Device Activity Status

With this BAdI, you can change the mapping between theCRM activity status and the device activity status during thedownload and upload of activities.

The following two methods are available:

o SET_DEVICE_ACT_STATUS for mappingCRM activity status and the device status duringdownload. The method is called from the /CMSE/READ_ACTIVITIES and /CMSE/READ_SURVEY function modules (FM).

o SET_CRM_ACT_STATUS for mapping the

device status and the CRM activity status duringupload. The method is called from the /CMSE/UPDATE_ACTIVITIES FM.

/CMSE/BADI_SALES_ORG

Sales Area Determination

With this BAdI, you can influence the determination of thesales area during upload of activities.

If the determination of sales organization unit, sales group,and sales office should be extended using activity data

and/or activity-related data, the following methods areavailable:

o SELECT_SALES_GROUP

o SELECT_SALES_OFFICE

o SELECT_SALES_ORG_UNIT

These methods are called from the /CMSE/UPDATE_SALES_AREA FM.

/CMSE/BADI_ACT_PRIORIT

Y

Determination of Mandatory Activities

In the standard, an activity is defined as mandatory if its



(C) SAP AG 104

BAdI Description

priority is 1. If the determination should be extended using

activity data and/or activity-related data, theSET_MANDATORY method is available.

This method is called from the /CMSE/READ_ACTIVITIES FM .



(C) SAP AG 105

Electronic Signature

Electronic signatures are commonly used in mobile business processes to verify activities and

can be important proof in case of complaints. By signing a document, for example, an invoice,a delivery note, an order, or a check-out/check-in document, the signer confirms that thesigned activity has taken place. For DSD scenarios, possible signers are drivers, checkers,and customers.

You can control the signature process on the mobile device by making Customizing settings,which are transferred to mobile devices, in the DSD Connector as follows:

In Customizing, you must activate every document type that you want to haveelectronically signed on the mobile device. Once activated, the signature of thatdocument is mandatory and cannot be refused.

If a signature is required for a document, in Customizing, you can configure as follows

which signer is allowed to sign for the respective document:

o Customers and/or drivers can sign the following:

Invoices

Orders

Deliveries

o Drivers and/or checkers can sign the following:

Check-out/check-in documents

Reload check-out/check-in documents

In the case of check-out/check-in and reload check-out/check-in, you can define inCustomizing whether or not the electronic signature replaces the manual input of thepassword. If electronic signature recording is enabled for check-out/check-in andreload check-out/check-in, the dialog box for manually entering a password does notappear and the signature screen is displayed instead.

Based on Customizing, it is possible to cancel or modify the document that has beensigned and/or printed. If a signed/printed document is canceled on the mobile device,then any signatures attached to this document are deleted as well.

Once a signature is captured on the mobile device, the device assigns it to the respective

mobile document and stores it as an image on the mobile device. At the end of the tour, themobile device signatures, as well as their assignment to mobile documents, are uploaded tothe back end system as part of the overall tour data.

During the Final Settlement Run (FSR), the back end documents (order, delivery, and invoice)are created or changed, depending on the tour activities and the related FSR Customizing.The linkage between mobile document, signature, and back end document is stored in theRoute Accounting Database (RAD) signature tables. The uploaded electronic signatures aretransferred to an HTTP-Content Server where they are stored as an image. In return, theHTTP-Content Server provides each signature with an archive document ID (= signature ID),

which assigns each signature to the back end document that corresponds to the mobiledevice document. This signature ID is stored in the relevant back end signature table (that is,order, delivery, or invoice signature table), together with the back end document number, the

signer name, the signer role, a time stamp, and a checksum. Once a signature is successfully



(C) SAP AG 106

stored in the folder system of the HTTP-Content Server , the related signature data in the RADsignature tables is deleted.

You can print the signed documents (orders, deliveries, invoices), including the signatures,from the back end as well as from mobile devices. The signatures are embedded (as GIFfiles) in selected forms of the documents that must be suitable for the corresponding mobile

device documents. As no forms exist for the documents for check-out/check-in and reloadcheck-out/check-in, you can display the signatures for these documents in the Check-out/Check-in Header Control and the Tour Data Entry respectively in the Settlement Cockpit .You can view all other signatures related to orders, deliveries, and invoices in the standard

transactions (VA03, VL03N, VF03) with the standard function Services for Object . For

collection, you can use the FB03 transaction.

Electronic signatures are not legally binding. This is because, within the DSD mobile process,no 1:1 relation exists between the documents created or changed on the mobile device andthe documents created or changed in the back end after the FSR. If a delivery is changed onthe mobile device, then an additional delivery is created in the back end. In this case, asigned delivery is related to two back end deliveries and two forms, all of which areinterpreted as one package conforming to the related mobile device delivery. The same isvalid for orders, invoices, and collections.

Process

To use the electronic signature function, you must make settings in Customizing in the boththe back end system and in the DSD Connector.

1. Make settings for the following activities in back end Customizing for LogisticsExecution:

o Under SAP Direct Store Delivery Electronic Signature for the following:

Signature Repository

Signature Text ID

For more information, see Maintain Signature Repository [Page 107] andMaintain Signature Text IDs [Page 108].

o Under SAP Direct Store Delivery Handheld Connectivity DSD Connector

Settings Mobile Device Settings Define Tour Scenario Settings , chooseSigner Roles Settings for the definition of signer roles settings.

For more information, see Assign Signer Roles to Documents [Page 110].

2. You can find the DSD Connector Customizing tables for this function underLogistics Execution SAP Direct Store Delivery Handheld Connectivity DSD

Connector Settings Mobile Device Settings Define General Settings Defining

Settings for Canceling/Changing Signed Documents .

For more information, see Define Settings for Canceling or Changing SignedDocuments [Page 116].



(C) SAP AG 107

Maintain Signature Repository

In this IMG activity, you need to maintain an archive document type to which you assign an

HTTP-Content Server as the content repository. This data record is used when storingsignatures that are assigned to Sales and Distribution (SD) documents in the back endsystem. The two fields of the data record (the archive document type and the contentrepository) can be compared with a pointer to a file that is saved in the folder system of theHTTP-Content Server . Together, they form the key for reading the signatures from the foldersystem.

Prerequisites

The following must be defined in Customizing for SAP NetWeaver under Application Server

Basis Services Archive Link Basic Customizing :

Under Edit Document Types

An archive document type (global document type) for DSD electronic signatures

Under Define Content Repositories

An external folder system with storage type HTTP-Content Server as the contentrepository for storing the DSD electronic signatures

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Electronic

Signature , choose Signature Repository .


3. On the screen that appears, enter the following data:

FieldName


Doc.Type Enter the global document type that is to be used for signature storage.

Example: ZSIGARC

Cont.Rep.

Choose the content repository (defined with storage type HTTP-ContentServer ) from the input help.

Example: A2


Result

During the Final Settlement Run, the system checks the entries made in this table and storesthe signatures, assigned to one or more documents during a tour, in the content repositoryyou maintained.



(C) SAP AG 108

Maintain Signature Text IDs

When a customer signs a document (order, delivery, invoice, or collection) on a mobile

device, it is possible to enter a signer name in block letters as well. The content of the signer’sname is uploaded to the back end where it is stored in signature tables.

In the standard maintenance applications for order, delivery, invoice, and collection, thissigner name is inserted into the customized header text ID of the respective back enddocument and thus becomes directly visible and readable at the header level of thedocument.

In order for the system to know which text ID should be used for signed orders, deliveries,invoices, and collection, in this IMG activity, you need to maintain the relevant text ID for eachtext object.

Prerequisites

New text IDs (text types) must be defined in standard text control Customizing (oneeach for order, delivery, and invoice) using the customer namespace (Y*, Z*). As allsales documents use the same text object for standard text processing, each text IDmust be defined for the VBBK text object. These are VBBK (for header) and VBBP (for items).

The text IDs must be assigned to the corresponding text procedures of the salesdocument header, delivery header, and billing document header. You do this in

Customizing for Logistics Execution under Shipping Basic Shipping Functions

Text Control Define Text Types .

For collection, you need to set up text ID for object “BELEG”. You do this in

Customizing, for example, under Financial Accounting (New) AccountsReceivable and Accounts Payable Business Transactions Incoming Invoices/Credit

Memos Make and Check Document Settings Define Text IDs for Documents .

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Electronic

Signature , choose Signature Text ID.



FieldName


For

Enter a text object from the dropdown list.

Example: A-Sales Document Header

For the mobile DSD scenario, only the following options are allowed for electronicsignatures:

o A (Sales Document Header)



(C) SAP AG 109

FieldName


o B (Delivery Header)

o C (Billing Document Header)

o W (Documentary Payments)

ID

Enter the customer-specific text ID, which you have created in standardCustomizing for Text Control (see “Prerequisites” above), to be used by thesystem for displaying the signer name.

Example: SIGN


ResultBased on entries made for orders, deliveries, and invoices, the system displays the signername on the header text ID on the maintenance screen of the corresponding application.



(C) SAP AG 110

Assign Signer Roles to Documents

You define the Customizing settings described here in the DSD Connector. The settings are

downloaded to mobile devices to control the signature process on the mobile devices.

In this IMG activity, for each relevant combination of document type and signer role, youdefine whether or not an electronic signature is mandatory on the mobile device. If electronicsignature recording is activated, you maintain the signing sequence of the signer roles thatare allowed for each combination of document type and role.

Prerequisites

The following relevant types must be assigned to DSD tour scenarios:

Shipment types

Visit plan types

Procedure


Connectivity DSD Connector Settings Mobile Device Settings , choose DefineTour Scenario Settings.

2. Go to Signer Roles Settings and choose New Entries.



TourScenario

Choose a tour scenario from the dropdown list provided. The tour scenariois indicated by the 2 digit ID at the beginning of each record.

Example: 02 (Van Sales Scenario)

Make sure that shipment type and/or visit plan type are assigned to DSDtour scenarios. Otherwise, the dropdown list is empty.

Shp/ VP Type

Choose a shipment type or visit plan type from the dropdown list.

Example: ZRH1

Type and number of entries displayed in the list depend on the selectionmade in the TS field.

If you have several shipment or visit plan types, you can also maintain anentry without shipment or visit plan type. During download, the DSDConnector takes the values from this entry if no other shipment or visit plantype matches.

Inv.sig.by Cu From the dropdown list, select one of the following:

o 0-disabled to disable customer signature on invoice



(C) SAP AG 111


o 1-enabled, first signer to request mandatory

customer signature on invoice

o 2-enabled, second signer to request mandatorycustomer signature on invoice after the driver has signed the invoicefirst

Inv.sig.by Drv

From the dropdown list, select one of the following:

o 0-disabled to disable driver signature on invoice

o 1-enabled, first signer to request mandatory driver

signature on invoice

o 2-enabled, second signer to request mandatory

driver signature on invoice after the customer has signed the invoice

first

Ensure consistent entries between the Inv.sig.by Cu field and the Inv.sig.byDrv field.

Ord.sig.by Cu


o 0-disabled to disable customer signature on order


customer signature on order


customer signature on order after the driver has signed the orderfirst

Ord.sig.by

Drv


o 0-disabled to disable driver signature on order


signature on order


driver signature on order after customer has signed the order first

Ensure consistent entries between the Ord.sig.by Cu field and theOrd.sig.by Drv field.

Del.sig.by Cu


o 0-disabled to disable customer signature on delivery


customer signature on delivery



(C) SAP AG 112



customer signature on delivery after driver has signed the deliveryfirst

Del.sig.by Drv


o 0-disabled to disable driver signature on delivery


signature on delivery


driver signature on delivery after customer has signed the deliveryfirst

Ensure consistent entries between the Del.sig.by Cu field and the Del.sig.byDrv field.

CI.sig.by Drv


o 0-disabled to disable driver signature on check-in

document


signature on check-in document


driver signature on check-in document after checker has signed thecheck-in document first

CO.sig.by Drv


o 0-disabled to disable driver signature on check-out

document


signature on check-out document


driver signature on check-out document after checker has signedthe check-out document first

CI.sig.by ChK


o 0-disabled to disable checker signature on check-in

document


checker signature on check-in document


checker signature on check-in document after driver has signed thecheck-in document first



(C) SAP AG 113


Ensure consistent entries between the CI.sig.by Drv field and the CI.sig.by

ChK field.

CO.sig.byChK


o 0-disabled to disable checker signature on check-out

document


checker signature on check-out document


checker signature on check-out document after driver has signedthe check-out document first

Ensure consistent entries between the CO.sig.by Drv field and theCO.sig.by ChK field.

ReCI.sig byDrv


o 0-disabled to disable driver signature on reload check-in

document


signature on reload check-in document


driver signature on reload check-in document after checker hassigned the reload check-in document first

ReCO.sig.byDrv


o 0-disabled to disable driver signature on reload check-

out document


signature on reload check-out document


driver signature on reload check-out document after checker hassigned the reload check-out document first

ReCI.sig.byChK


o 0-disabled to disable checker signature on reload check-

in document


checker signature on reload check-in document

o 2-enabled, second signer to request mandatorychecker signature on reload check-in document after driver has



(C) SAP AG 114


signed the reload check-in document first

Ensure consistent entries between the ReCI.sig.by Drv field and theReCI.sig.by ChK field.

ReCO/ChK


o 0-disabled to disable checker signature on reload check-

out document


checker signature on reload check-out document


checker signature on reload check-out document after driver hassigned the reload check-out document first

Ensure consistent entries between the ReCO.sig.by Drv field and theReCO.sig.by ChK field.

Flag Select Enabled or Disabled to control whether or not a password must be

entered for regular and reload check-out/check-in documents instead of asignature.

Collc. Sig. byCust.


o 0-disabled to disable customer signature on collection

document


customer signature on collection document


customer signature on collection document after driver has signedthe collection document first

Collc. Sig. byDrv.


o 0-disabled to disable driver signature on collection

document


signature on collection document


driver signature on collection document after customer has signedthe collection document first




(C) SAP AG 115

Result

For each activated combination of document type and signer role, electronic signaturerecording is now supported on the mobile device and the respective mobile screen isdisplayed for recording signatures. If the functionality is disabled, the appropriate field isgreyed out on the mobile device and input is not possible.



(C) SAP AG 116

Define Settings for Canceling or Changing SignedDocuments

You define the Customizing settings described here in the DSD Connector. The content isthen downloaded to mobile devices for controlling the process of changing and cancelingorders, deliveries, invoices, and collections on the mobile devices.

These Customizing settings allow you to define whether or not a document that has beenprinted and/or signed on the mobile device can be changed or canceled.

Procedure


Connectivity DSD Connector Settings Mobile Device Settings Define General

Settings , choose Define Settings for Canceling/Changing Signed Documents.



FieldName


DocType Choose a document type from the dropdown list provided.

Example: 20 Order

Printed

Select this checkbox to indicate that changing and canceling a printed

document is allowed (in this example, the printed order).

Signed Select this checkbox to indicate that changing and canceling a signeddocument is allowed (in this example, the signed order).


Result

Based on the entries you have made, the driver may be allowed to change and/or cancel adocument (order, delivery, invoice, or collection) that has been signed and/or printed.



(C) SAP AG 117

Additional Data Download

In some process scenarios, on the tour, you need to have additional customers who are not

part of the current visit list or shipment. In SAP Direct Store Delivery , you can manage thisrequirement in the following 2 ways:

Use additional data download together with occasionally connected scenario (OCS)

Use a BAdI during regular download

Downloading customer data by additional data download only downloads a subset ofcustomer master data. If you require the full data set, you need to trigger data synchronizationfrom the mobile client, for example, after adding a new customer to your visit list.

The functionality does not require you to make any program changes; you only need tomaintain some Customizing settings. For simple requirements, this approach is sufficient; for

more complex requirements, you should use a BAdI implementation within the downloadprocess.

Prerequisites

If you want to use this functionality, you need to maintain Customizing for follow-updocuments in OCS. For more information, see the following:

Define Follow-up Documents for Shipments [Page 136]

Define Follow-up Documents for Visit Lists [Page 138]

You need to have an online connection during tour/visit processing

Process

In Customizing for Logistics Execution under SAP Direct Store Delivery Handheld

Connectivity Additional Data Download , choose the following:

1. Assign Rule per Tour Scenario for Additional Customers [Page 118]

2. Define Route Properties for Additional Customers [Page 119]



(C) SAP AG 118

Assign Rule per Tour Scenario for AdditionalCustomers

In this IMG activity, you can specify, per tour scenario, the rule that defines how the systemdetermines additional customers. The determination can be based on the following:

Visit information

Additional customers are selected by checking visit lists for the following days. Nofurther selection criterion is considered. This is the recommended setting for apreseller scenario.

Master data

Additional customers are selected based on master data fields, for example, sales

area, sales office, and transportation zone.

Procedure


Connectivity Additional Data Download , choose Assign Rule per Tour Scenario for Additional Customers.




Tour Scenario Select a tour scenario from the input help.


Cust.Rule Select a rule from the input help.

Example: 01 - Visit Driven


Result

You have defined the rule for additional customer master data download.



(C) SAP AG 119

Define Route Properties for Additional Customers

In this IMG activity, you can define selection criteria for your additional customer master data.

Each entry in the properties field is used as an “and” statement in the database selectstatement.

Procedure


Connectivity Additional Data Download , choose Define Route Properties for Additional Customers.




Route Select a route from the input help.

Example: 000001

Sorg. Select a sales organization from the input help.

Example: 0001

DChl Select a distribution channel from the input help.

Example: 01

Dv Select a division from the input help.

Example: 01

SOff. Select a sales office from the input help.

Example: 0001

Group Select a customer account group from the input help.

Example: 0001

Plnt Select a delivery plant from the input help.

Example: 0001

Country Select a country from the input help.

Example: DE

Transport.Zone Enter a transportation zone.

Example: 0000000001



(C) SAP AG 120

The selection criteria are only used if you set up the tour scenario rule as 02-MasterData driven. You have to maintain at least one property for a route.


Result

The route properties have been defined.



(C) SAP AG 121

General Settings

In the following IMG activities, you can influence the data transfer between SAP ERP via SAP

Mobile Platform to the client. These tables are delivered by SAP and already populated withthe correct content. Typically, you only need to change or add some entries if you developsome additional functionality.

Changing the existing entries may result in download or upload issues

Process

Proceed as follows:

1. Maintain Filter for Mobile Business Objects [Page 122]

2. Define Supported Processes for Download and Upload [Page 123]

3. Set Up Download Process Activation [Page 124]



(C) SAP AG 122

Maintain Filter for Mobile Business Objects

Mobile Business Objects (MBO) are used to transfer data between SAP ERP, SAP Mobile

Platform, and mobile devices. These MBOs are based on structures of the SAP ERP backend. If certain fields of an MBO should not be used for data transfer, for example, in order toreduce data volume, these fields can be deactivated. If you change a parameter withoutadapting the MBO model on SAP Mobile Platform, it leads to runtime errors.

The table content is delivered by SAP and should only be adjusted while doing a customerenhancement/development.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery HandheldConnectivity General Settings , choose Maintain Filter for Mobile Business Objects.

2. Choose New Entries


FieldName

User Action

MBOName

The name of the MBO.

MBO Field The field name of the corresponding MBO.

InactiveSelect the checkbox to set the MBO field inactive. This means that the field isnot transferred.

Cont Inact Select the checkbox to ignore this field when generating MBO structures.

By default, certain fields are inactive. Activating them without regenerating the MBOdata model in SAP Mobile Platform would lead to runtime errors.



(C) SAP AG 123

Define Supported Processes for Download andUpload

MBOs are grouped into processes. The sequence of MBO processing after data upload canbe managed via the corresponding processes. All processes listed in this table are deliveredand used by SAP for SAP Direct Store Delivery . If you do customer enhancements, it may benecessary to define new processes.

Removing processes leads to data loss during download and/or upload.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery HandheldConnectivity General Settings , choose Define Supported Processes for Downloadand Upload .



FieldName

User Action

Process

The name of your new process for your custom enhancement.

The entries shown are used by SAP Direct Store Delivery . This includes the first“empty” line which should not be removed.


Result

A new process is defined.



(C) SAP AG 124

Set Up Download Process Activation

You can control which processes are active for certain synchronization types or scenarios.

You can also control if a customer function, done by your own BAdI Implementation, is usedfor some processes.

The content of this table is delivered by SAP and is used for SAP Direct Store Delivery .

Do not change the default settings as this might cause inconsistencies on the mobile devices.

Procedure


Connectivity General Settings , choose Set Up Download Process Activation.



Field Name User Action

Process Name of the process.

Std ActiveSelect the checkbox to activate the standard data extraction for downloadfor this process.

CustActive Select the checkbox to activate the custom-specific data extraction fordownload for this process (only used in the case of enhancements).

DeltActive

Select the checkbox to set this process active for delta downloads.

Do not change the default settings as this might cause inconsistencies onthe mobile devices.

RelActive

Select the checkbox to set this process active for reload download.


OCSRemAct

Select the checkbox to set this process active for delta deletes.


Error Stop Select the checkbox to cause the entire download to stop in case this



(C) SAP AG 125

Field Name User Action

process raises an error.


Result

You have activated each process for download.



(C) SAP AG 126

Upload

You use the upload functions once the mobile user returns to the depot or plant from a tour. In

a mobile scenario, the mobile user places the mobile device in its cradle and the tour data isautomatically uploaded to the Route Accounting Database (RAD). In a non-mobile scenario,you enter the tour data manually.

In contrast to the download process, SAP ERP does not control the upload process of tourdata. For Route Accounting [Page 389] in SAP Direct Store Delivery , SAP ERP uses aseparate database called the Route Accounting Database (RAD). When you transfer tourdata from a mobile device to SAP ERP at the end of a tour, the mobile device synchronizesand uploads the tour data to the DSD Connector. As soon as the synchronization and uploadprocesses are complete, the DSD Connector calls the relevant BAPIs in the DSD back end toupload the data to the DSD back end. The BAPIs transfer the tour data from the DSDConnector to the RAD. Once the data is successfully uploaded, the tour-related data isdeleted from the DSD Connector. SAP ERP retrieves the tour data from the RAD and

displays it in the Settlement Cockpit. You can further process the tour data within RouteSettlement [Page 404].

For this process, the /EMSE/UPLOAD_BADI BAdI is available. The methods of this BAdI offer

more flexibility during the upload process. This BAdI enables customers to set up their ownspecific mapping between the interface data and the RAD tables.

Process

This section covers the following steps:

1. Set up Upload Process Sequence [Page 127]

2. Define Allowed Route Transaction Types [Page 128]



(C) SAP AG 127

Set Up Upload Process Sequence

SAP Mobile Platform sends an HTTP as information to the back end. The

/EMSE/CL_HTTP_UPLOAD_INFORM HTTP handler class reads the user and the number of

operation records and calls a queued bgRFC to ensure data consistency. The handler classreturns a 200 OK code to SAP Mobile Platform to confirm the received information. Then, the

/EMSE/UPL_PROC upload processes Customizing is read and, in a loop, all processes are

triggered. A default implementation is delivered, which can be replaced by a customer-specific implementation. The complete upload is handled through the new

/EMSE/UPLOAD_BADI BAdI enhancement implementation. SAP delivers the table content

and it may be necessary to change the sequence for customer enhancements.

Procedure


Connectivity Upload , choose Set up Upload Process Sequence.



FieldName


Sequence

Enter a sequence number.

Example: 300

It is mandatory that, at first sequence, the UPLOAD_TYPE process appears.

Process

Select a process from the input help.

Example: COCI

You can select all processes that are available in Define Supported Processesfor Download and Upload [Page 123].


Result

The sequence of the upload is defined.



(C) SAP AG 128

Define Allowed Route Transaction Types

In this IMG activity, you define allowed route transaction types for the upload depending on

the Settlement Type [Page 411] and the Settlement Office [Page 406]. Several settlementtypes are allowed for the same settlement office.

You create customer-specific extensions for the relevant route transactions in the namesspaces reserved for this purpose in the chapter Basic functions in the IMG activity Define Allowed Route Transaction Types. The corresponding flow logic for further processing mustbe reprogrammed.

Prerequisites

You have defined at least one settlement type.

You have defined at least one settlement office.

You have defined route transaction types.

Procedure


Connectivity Upload , choose Define allowed Route Transaction Types.




Sett.Type Select a settlement type from the input help.

Example: M001

Sett.Off. Select a settlement office from the input help.

Example: M001

Trans.Type Select a route transaction type (01 – 09) from the input help.

Example: 01

Repeat the entries in the table for each required route transaction type.


Result

The data of the excluded tour transaction types that have been entered in the Define allowedRoute Transaction Types Customizing table are transferred even if an error message occursduring the automatic settlement run. The transaction then requires manual touch-up work.

For example, a delivery driver may not be allowed to accept customer orders. Should he doso, the data of the customer order is transferred and edited manually by the settlement officelater.



(C) SAP AG 129

Occasionally Connected Scenarios

SAP Direct Store Delivery supports occasionally connected scenarios (OCS). In previous

DSD solutions, it was only possible to synchronize data during tour start (download) and tourend (upload), and reload (if a truck returns to the distribution center during the day). SAPDirect Store Delivery also supports the download of some additional data during tourprocessing. The following scenarios are also covered:

1. Online pricing

2. Online credit check

3. Online ATP check

4. Online open item check

1. to 4. can be switched on/off in Customizing for Logistics Execution under SAP

Direct Store Delivery Handheld Connectivity DSD Connector Settings Mobile

Device Settings Define Tour Scenario Settings (see Define Tour Scenario Settings

[Page 213]).

5. Download additional delivery, activity, or customer master data during the tour

The online scenarios 1.- 4. are triggered automatically from the mobile client while the OCSdownload, scenario 5., is initiated by the back end user in the OCS Cockpit

(/EMSE/OC_ONTOUR transaction). Only the ATP check can be triggered manually by the

mobile user on the mobile client.

The online scenarios 1.- 4. use the Lean Order API in the back end to retrieve the results. The

Lean Order API simulates an order creation (similar to the back end VA01 transaction).

For scenario 5, you can download “delta data” like an additional customer or an additionaldelivery. Depending on the tour status (default tour status is 308000 – Available on mobile)[see Delivery Process: Assign Shipment to Tour Scenario [Page 384] or Sales Process:

Assigning Visit List to Tour Scenario [Page 387]], the system does not need to create a “deltashipment/visit list”; it can use the originally edited shipment/visit list instead. This is referred toas the “Keep” scenario because the sequences of the original shipments/visit lists remain inthe DSD Connector.

Depending on the tour scenario, you can add different objects, for example, a delivery, to your

original downloaded tour.

For the preseller scenario, it is not possible to assign deliveries for downloading. For themixed driver scenario, you can download additional customers, deliveries, and activities (ifCRM is used).

In the OCS Cockpit , you manually trigger the download by selecting Output when all yourchanges have been done. On the mobile client, the mobile user also needs to send a requestto receive the data on the mobile device.



(C) SAP AG 130

Process

In Customizing for Logistics Execution under SAP Direct Store Delivery Handheld

Connectivity , choose Occasionally Connected Scenarios, you have to maintain the followingIMG activities, depending on which online scenario you want to use:

1. Define Document Settings for ATP Check and Price Determination [Page 131]

2. Activate Reload Proposals [Page 133]

3. Allow Deliveries with Different Route [Page 134]

4. Maintain Condition Types for Online Pricing [Page 135]

5. Define Follow-up Documents for Shipments [Page 136]

6. Define Follow-up Documents for Visit Lists [Page 138]



(C) SAP AG 131

Define Document Settings for ATP Check and PriceDetermination

You define the document settings for pricing in a DSD scenario with occasional datasynchronization between the mobile device and the back end system. The system uses theLean Order API and requires a sales order type and, optionally, some item usages to usedifferent item categories if required.

You can make different settings for the various combinations of shipment types andtransportation planning points. You can also make settings for visit plan types.

If you indicate that a defined item usage in the document settings is the default setting, thesystem uses this item usage for pricing. This default setting is valid as long as no otherdocument settings are transmitted from the mobile device to the back end system.

Procedure1. In Customizing for Logistics Execution under SAP Direct Store Delivery Handheld

Connectivity Occasionally Connected Scenarios , choose Define DocumentSettings for ATP Check and Price Determination.




ShTy

Optional – Select shipment type from the input help.

Example: ZMDD

TPPt Optional – Enter desired transportation planning point.

Example: ZMDD

VPT Optional – Select visit plan type from the input help.

Example: ZPS

SaTy Mandatory – Select sales document type from the input help.

Example: ZTA

Usg. Item usage for material items (price determination).

Usg. Item usage for free of charge material items (price determination).

Usg. Item usage for free of charge material items with free empties.

Usg. Item usage of return items (price determination).

Usg. Item usage of free of charge return items (price determination).

Usg. Item usage of free of charge return items with free empties.



(C) SAP AG 132


Def. Default checkbox.


Result

You have defined the settings for online ATP checks and pricing determination.



(C) SAP AG 133

Activate Reload Proposals

In this IMG activity, you can connect the reload process to the occasionally connected

scenario (OCS) process. The reload proposal uses the delta documents created in the OCSprocess.

Reload is the process of loading or unloading a truck during a tour by making an intermediatestop at the distribution center.

If you select this checkbox, a corresponding pushbutton appears in the reload

/DSD/SV_RELOAD transaction.

You can also decide for which combination of shipment type and transportation planning pointthis function is active. If you leave both key fields blank, the function is active for allcombinations.

Procedure


Connectivity Occasionally Connected Scenarios , choose Activate ReloadProposals.




ShTy

Optional – Select shipment type from input help.

Example: ZMDD

TPPt Optional – Enter desired transportation planning point.

Example: ZMDD

Proposals Select the checkbox to activate.


Result

You have defined and activated for which shipment type/transportation planning point areload proposal can be used.



(C) SAP AG 134

Allow Deliveries with Different Route

In the OCS Cockpit , you can add new deliveries to existing tours. In this IMG activity, you

allow that new deliveries can be added to shipments that have different original routes.

Procedure


Connectivity Occasionally Connected Scenarios , choose Allow Deliveries withDifferent Routes.




Flag Select the checkbox to activate adding allowed.


Result

By selecting this checkbox, you can add any delivery with route to any shipment in the OCSCockpit.



(C) SAP AG 135

Maintain Condition Types for Online Pricing

During online pricing, the mobile client sends a request to the back end for pricing. The back

end then sends the used condition types and values back to the mobile client. This allows youto print specific condition types, for example, on the customer invoice on the mobile client.However, the invoice layout on the client still needs to be adjusted.

Procedure


Connectivity Occasionally Connected Scenarios , choose Maintain ConditionTypes for Online Pricing .




CnTy Select condition type from the input help.

Example: PR00

Name Populated automatically depending on the selected condition type.

No return If you select this checkbox, the condition type is not sent to the mobile client.

4. Repeat step 3. for all desired condition types. Usually, these are all the condition

types of the back end pricing procedure you use with the exception of, for example,statistical condition types.


Result

You save set all required condition types for online pricing process that are used during LeanOrder API .



(C) SAP AG 136

Define Follow-up Documents for Shipments

The OCS Cockpit uses a shipment for delta document creation. Therefore, you need to

maintain a follow-up shipment type that is used accordingly based on your original shipment.Independent of how many follow-up documents the system has created, during settlement,you only have to work with the original shipment or visit list

This setting has to be done for scenarios where your leading document is a shipment, forexample, for delivery driver scenarios. In a mixed role scenario (consisting of a visit list andshipment), you have to select the multiday tour (MDT) checkbox if the visit plan type of theoriginal visit list is MDT enabled. You can only create MDT enabled deltas for a multiday tourenabled visit list.

Procedure


Connectivity Occasionally Connected Scenarios , choose Follow-up Documents forShipments.



FieldName


ShTy Select shipment type from the input help.

Example: ZMDD

TPPt Select transportation planning point from the input help.

Example: ZMDD

MDT

Select this checkbox to indicate an MDT.

If your original visit list is MDT enabled, you have to select this checkbox if youwant to do delta data creation.

Shpt Ty. Follow-up shipment type to be used during delta data creation

Example: ZMDD

FL-upTPPt

Follow-up transportation planning point to be used during delta creation

Example: ZMDD

FL-upVPT

Follow-up visit plan type to be used during delta data creation

Example: MDD




(C) SAP AG 137

Result

You have defined the follow-up documents for delta data creation.



(C) SAP AG 138

Define Follow-up Documents for Visit Lists

You make settings for scenarios where your leading document is a visit plan, for example, for

a preseller scenario.

Procedure


Connectivity Occasionally Connected Scenarios , choose Follow-up Documents forVisit Lists.




Visit Plan Type Select visit plan type from the input help.

Example: MPS

Follow-up VisitPlnTy Select follow-up visit plan type from the input help.

Example: MPS


Result

You have defined the follow-up document for delta data creation for the preseller scenario.



(C) SAP AG 139

Document Numbering

In SAP Direct Store Delivery , an algorithm for document number generation guarantees that

all documents from the same source class (order, delivery, invoice, credit note, and collection)have a unique number for a specific tour. To avoid the need for custom developments in thefront end and back end, the document number string is customizable and supportsrequirements for centralized/decentralized approaches, for example, per distribution center.

Process

1. You have to define the delivery number type or invoice number type first. Makesettings for the following activities in Customizing for Logistics Execution under

SAP Direct Store Delivery Handheld Connectivity DSD Connector Settings

Mobile Device Settings Define General Settings :

o Assign Delivery Document Types to DSD Delivery Scenarios [Page 140]

o Assign Sales Document Types to DSD Order Scenarios [Page 142]

2. Make settings for the following activities in Customizing for Logistics Execution under

SAP Direct Store Delivery Handheld Connectivity Document Numbering :

o Assign Document Prefix to Collection Document Number Types [Page 144]

o Assign Document Prefix to Sales Document Number Types [Page 145]

o Define Criteria for Unique Number Creation [Page 147]

o Assign Series to Criteria for Unique Number Creation [Page 148]

o Define Last No. for Document No. Types and Criteria for Unique No. Creation[Page 149]



(C) SAP AG 140

Assign Delivery Document Types to DSD DeliveryScenarios

In this IMG activity, you maintain which delivery document types are allowed and can be usedon the mobile device for each DSD delivery scenario. Only delivery document typesmaintained in this Customizing table are relevant for download. In addition to the existingCustomizing table, you assign parameters here for the following:

Document numbering

Listing/Exclusion

Additional sales documents

Default checkbox

Procedure



Settings , choose Assign Delivery Document Types to DSD Delivery Scenarios.



FieldName


DeliveryScenario

Select the desired delivery scenario from the input help.

Example: Presold Delivery Scenario

DeliveryType

Specify a relevant delivery document type, as maintained in the DSD backend, which is allowed on the mobile device in the DSD delivery scenarioselected.

Example: ZLF

Sales Type

Specify a relevant sales document type, as maintained in the DSD back end,which is allowed on the mobile device for the DSD delivery scenario selected.

Example: ZTA

DeliveryNo. Type

Defines the delivery number type that controls the rules of document numbergeneration for delivery.

Invoice No.Type

Defines the invoice number type that controls the rules of document numbergeneration for invoices.

Default

Select the checkbox.

In back end Customizing, multiple document types can be maintained for each



(C) SAP AG 141

FieldName


of the order/delivery scenarios. To ensure that Listing/Exclusion is workingproperly, you need to default one document type per scenario.


Result

From the settings made in this table, the system can now determine the following:

Which delivery scenario is on the mobile device

Which unique number will be created

Which documents are considered for Listing/Exclusion



(C) SAP AG 142

Assign Sales Document Types to DSD OrderScenarios

In this IMG activity, you maintain sales document types that are allowed on the mobile devicefor each DSD order scenario. In addition to the existing Customizing table, you assignparameters here for the following:

Document numbering

Listing/Exclusion

Default checkbox

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery HandheldConnectivity DSD Connector Settings Mobile Device Settings Define General

Settings , choose Assign Sales Document Types to DSD Order Scenarios.




OrderScenario

Select the desired order scenario from the input help.

Example: Take Order Scenario

SalesDocumentType

Specify a relevant sales document type, as maintained in the DSD back end,that is allowed on the mobile device for the DSD delivery scenario selected.

Example: ZTA

Order No.Type

Defines the order number type.

It is used to associate various orders for document number generation.

Example: O

Default


In back end Customizing, multiple document types can be maintained foreach of the order/delivery scenarios. To ensure that Listing/Exclusion isworking properly, you need to default one document type per scenario.


Result

From the settings made in this table, the system can now determine the following:

Which order scenario is on the mobile device



(C) SAP AG 143

Which unique number will be created

Which documents are considered for Listing/Exclusion.



(C) SAP AG 144

Assign Document Prefix to Collection DocumentNumber Types

In this IMG activity, you define a prefix value to represent collection type documents.

Procedure


Connectivity Document Numbering , choose Assign Document Prefix to CollectionDoc. Number Types.

2. On the screen that opens, switch to change mode and choose New Entries.



CompanyCode

Select a company code from the input help.

Example: 0001

Collctn. No.Ty.

Enter the collection number type for collection documents.

Example: P

You can only select the collection type document P, which representspayments.

Prefix

Enter a value (2 characters) that is used in document number generation ondocument type.

Example:

CO for collection


Result

Based on the entries in this table, the client generates the document number for collectiontype documents.



(C) SAP AG 145

Assign Document Prefix to Sales DocumentNumber Types

In this IMG activity, you define a prefix value to represent the document type for salesdocument number type in number generation.

Based on the document type you choose, the respective document number types ispopulated from the following settings, which you define in Customizing for Logistics Execution

under SAP Direct Store Delivery Handheld Connectivity DSD Connector Settings

Mobile Device Settings Define General Settings :

Assign Delivery Document Types to DSD Delivery Scenarios

Assign Sales Document Types to DSD Order Scenarios


Connectivity Document Numbering , choose Assign Document Prefix to Sales Doc.Number Types.




SalesOrganization

Select a sales organization from the input help.

Example: 0001

DistributionChannel

Enter the collection number type for collection documents.

Example: P

You can only select the collection type document P, which representspayments.

Division

Enter a value (2 characters) that is used in document numbergeneration on document type.

Example:

CO for collection

Doc. Type

Enter the document type from the input help.

Example: OR

You can choose from the following values:

o OR



(C) SAP AG 146


Sales order document

o DL

Delivery document

o IN

Invoice/Credit note document

Doc No. Type Enter the document number type from the input help.

Example: O

Prefix

Enter a value (2 characters) that is used in document numbergeneration on document type.

Example:

o SO

Sales order

o RO

Return order


Result

Based on the entries in this table, the client generates the document number for salesdocuments.



(C) SAP AG 147

Define Criteria for Unique Number Creation

In this IMG activity, you define which of the following criteria is used for unique number

creation in document numbering:

Customer-Specific

Driver

MEUser

Route

Vehicle

If you specify Customer-Specific , you need to implement the

/EMSE/BADI_UNIQUE_CONCEPT Business Add-In (BAdI) to determine unique numbercreation.

Procedure


Connectivity Document Numbering , choose Define Criteria for Unique NumberCreation.

2. On the screen that opens, switch to change mode.



Unique No. Crit. Select one criterion from the input help.

Example: MEUser


Result

Depending on this entry, the system uses this criterion to ensure a unique document number.



(C) SAP AG 148

Assign Series to Criteria for Unique NumberCreation

In this IMG activity, you define a sequence number for each unique number criterion. You canonly define a unique series value for each unique number criterion.

Procedure


Connectivity Document Numbering , choose Assign Series to Unique NumberCreation.

2. On the screen that opens, switch to change mode.



Unique No. Criter. Select one criterion from the input help.

Example: MEUser

Series Enter a value up to 6 characters.

Example: A00001


Result

The entry for Series here is used in association with the unique number criterion in thegeneration of a unique document number.



(C) SAP AG 149

Define Last No. for Document Number Types andCriteria for Unique No. Creation

In this IMG activity, you define the last number used for each of the following:

Unique number criterion

Delivery type

Order type

Delivery/Invoice number type

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery HandheldConnectivity Document Numbering , choose Define Last No. for Doc. No. Typesand Criteria for Unique No. Creation.




Unique No.Criter.

Select one criterion from the input help.

Doc. Type Select a value from the input help.

Example: Delivery Document

Doc. No. Type

Select a value from the input help.

Example: R

Depending on the document type, different document type indicators areselectable.

Last No. Enter a numeric value of up to 8 digits.


5. Repeat these entries for all document type and document number type used.

Result

You have now set the last number, which will be the starting point for new documentnumbers.



(C) SAP AG 150

Application Log Monitoring

The SAP Direct Store Delivery Application Log Monitor enables monitoring and control of the

synchronization status of a shipment or visit list from the back end DSD Connector. You canuse the Application Log Monitor to track all messages that occur during all mobile scenarios.

The main capabilities support the following:

You can see all relevant statuses of tours

You can see all relevant application log messages from the back end for the selectedtour

You can see all relevant connector data for a selected tour

You can see tour dependent JSON data that are used for download and upload

Administration functions like resend, remove, or force tour uploads

Prerequisites

Before using the Application Log Monitor , you need to activate a HTTP for the Webdynpro service (see Activate HTTP Service for Web Dynpro) [Page 151].

Process

You can use the following two ways to start the Application Log Monitor :

1. Launch the monitor using the /EMSE/APPLOG_MONITOR transaction. In the SAP

Easy Access menu, choose Logistics Execution Direct Store Delivery ApplicationLog Monitor .

On the log on screen, enter your SAP ERP user and password.

2. Log on in a web browser as follows using the web dynpro link Error! Hyperlinkreference not valid.:

o <Server>: Enter your system server name here

o <Port> : Enter the port here

o Sap-client : Client of the DSD SAP ERP system

o Sap-language : User-specific logon language



(C) SAP AG 151

Activate HTTP Service for Web Dynpro

For the web dynpro component, we deliver the required HTTP service with SAP Direct Store

Delivery . To be able to use the Application Log Monitor , you first need to activate the HTTPservice in SAP ERP.

Procedure

1. In SAP ERP, in the SAP Easy Access menu, choose Tools Administration

Administration Network HTTP Service Hierarchy Maintenance .

2. On the selection screen, select hierarchy type SERVICE as filter and execute.

3. On the next screen, in Virtuelle Hosts / Services, choose default_host sap bc

webdynpro emse and do the following:

o Select fpm_appl_log_monitor , right click, and select Activate Service

o Select wd _appl_log_monitor , right click, and select Activate Service

Result

The service is now active and ready to use.



(C) SAP AG 152

Define Connector Tables to Be Monitored

In the Application Log Monitor , you can choose to see the database tables of the DSD

Connector. The tables are displayed in the Connector Data assignment block.

Tables with the following prefixes can be displayed:

/DSD/ME

Y

Z

Tables outside of customer name space starting with “/”

ProcedureWe deliver a set of DSD Connector tables by BC set. If you want to add additional tables,proceed as follows:


Connectivity Monitoring , choose Define Connector Tables to Be Monitored .



FieldName


TableName

Select a table from the input help.

Example: /EMSE/ME_CNDLE

Object Select the authorization object from the input help. For this Customizing, onlythe object /EMSE/CDAT is valid.


Result

You can now access the maintained tables in the Application Log Monitor .



(C) SAP AG 153

Define Objects for Message Log Monitoring

In this IMG activity, you maintain all possible values for SAP Direct Store Delivery application

log objects. These values are needed to maintain the assignment of system messages to theapplication log handling.

As default, there are the following 3 objects (delivered by BC set):

/EMSE/PROCESS_DWNLD

DSD: Process for Download

/EMSE/PROCESS_UPLD

DSD: Process for Upload

/EMSE/PROCESS_ONLINE

DSD: Process for Online

Procedure

If you require additional objects, you can maintain them here.

To use your new custom maintained objects, coding enhancement is required in SAP ERP.


Connectivity Monitoring , choose Define Objects for Message Log Monitoring .




Object

Enter the object of your choice.

Y* and Z* are reserved as customer names.


Result

You have created your own object.



(C) SAP AG 154

Define Subobjects for Message Log Monitoring

In this IMG activity, you maintain all possible values for SAP Direct Store Delivery application

log subobjects. These values are needed to maintain the assignment of the system messagesto the application log handling.

The subobject sets the location where the original message is written (back end or front end)and for which technical part of the process (business or system). In the SAP Direct StoreDelivery Application Log Monitor , you can select messages by these subobjects.

As default, there are the following 6 subobjects (delivered by BC set):

/EMSE/SYSTEM_BE

DSD: System Logs for Back End Activities

/EMSE/SYSTEM_FE

DSD: System Logs for Front End Activities

/EMSE/BUSINESS_BE

DSD: Business Logs for Back End Activities

/EMSE/BUSINESS_FE

DSD: Business Logs for Front End Activities

/EMSE/OTHERS

DSD: Logs for all other Activities

/EMSE/OCS_BE

DSD: OCS Monitor Messages Filter

Procedure

If you require additional subobjects, you can maintain them here.

To use your new custom maintained subobjects, coding enhancement is required in SAPERP.


Connectivity Monitoring , choose Define Subobjects for Message Log Monitoring .




Object Enter the object of your choice.



(C) SAP AG 155


Y* and Z* are reserved as customer names.


Result

You have created your own subobject.



(C) SAP AG 156

Assign Message Log Objects and Subobjects toMessages

In this IMG activity, you maintain the association between the process message and theapplication log. You can assign the following to a process message:

Message ID

Message number

Relevant application log information object

Relevant application log information subobject

You can control every message in different ways, for example, by suppressing the message

or by defining a different message type. Additionally, you have the option to connect to SAP Alert Management by linking the message to an alert category.

Procedure

A set of necessary entries are delivered by BC set. If you need to change/add somemessages, proceed as follows:


Connectivity Monitoring , choose Assign Message Log Objects and Subobjects toMessages.


Enter the following data:

FieldName


MainProcess

Select the main process from the input help

Example: /EMSE/PROCESS_DWNLD

Process

You can select a process to define for which sub process the application loghandling should be used.

If you select “blank”, application log handling is valid for all process steps.

If you select a specific process, the application log handling is only done for thisstep.

Prerequisite:

All processes that need to be maintained are delivered by BC set (in

Customizing for Logistic Execution under SAP Direct Store Delivery

Handheld Connectivity General Settings Define Supported Processes for

Download and Upload ).

Message Enter the message class.



(C) SAP AG 157

FieldName


Class Example: /DSD/ME

Msg. No. Enter the message number.

Example: 61

Object

Select object from the input help. The object must be the same as the mainprocess.

Example:/EMSE/PROCESS_DWNLD

Subobject Select a subobject from the input help.

Example: /EMSE/BUSINESS_BE

Suppress Select this checkbox to suppress the message in the application log monitor.

Msg. Typ

Select a value from the input help. If the message type of the original messageshould be changed, enter the new value here.

Example: E (Error) to put an initial warning message to error.

AlertCategory

Enter the alert category to use Alert Management functionality.


ResultThe process messages are now assigned to the SAP Direct Store Delivery Application LogMonitor .



(C) SAP AG 158

Define Error Subjects and Map to SAP CRMMessages/Status

In this IMG activity, you define the status of messages from SAP CRM by using errorsubjects, which classify similar CRM messages that can occur during the upload or downloadprocess. For each tour scenario, you can determine if a specific error subject should have animpact on the CRM status.

Procedure

As default, we deliver all necessary entries in the system by BC set. If you need to changesome settings, proceed as follows:


Connectivity Monitoring , choose Define Error Subjects and Map to CRM

Messages/Status.




Definition ofError Subjects

Error Subject Select one line with related error subject.

Description Description

Mapping ofError Subjectsto CRMMessage IDs

Message Class

Enter the message class.

Example: /CMSE/DL_MESSAGES

The message classes are from SAP CRM. All start with the /CMSE/

prefix.

Msg.No Enter the message number.

Mapping ofError Subjectto CRM Status

TS Select a tour scenario from the input help.

Example:01 Pre-Sales Scenario



(C) SAP AG 159


CRM Status

Enter CRM status from input help.

Example: Error

Map the error status to a CRM status to determine how the CRM status ischanged for tour scenarios. That is, if a specific CRM message occurs inthe course of the upload or download process, this CRM message has itsCRM status (for example, warning or error) set through its affiliation to aspecific error subject for the current tour scenario.


Result

You have defined the status of CRM messages.



(C) SAP AG 160

Vehicle Checks

During the check-out process, you can carry out a vehicle check. You can maintain questions

in a catalog and define how the back end determines the catalog.

If a catalog is determined, the appropriate screen with the questions is displayed on themobile client during the check-out process. The mobile user has to confirm each questionbefore being allowed to proceed. The questions are not displayed on the mobile client if nocatalog has been determined or the catalog is deactivated.

The results of the vehicle check are not stored on the mobile client and are not uploaded attour end.

Process

To use the vehicle check, you need to make settings in the following IMG activities in

Customizing for Logistics Execution under SAP Direct Store Delivery HandheldConnectivity Vehicle Check :

1. Maintain Catalog ID and Related Questions [Page 161]

2. Maintain Catalog Determination [Page 163]



(C) SAP AG 161

Maintain Catalog ID and Related Questions

In this IMG activity, you define a catalog ID and assign vehicle check questions to it. The

questions can be maintained in different languages for the same catalog.

Procedure


Connectivity Vehicle Check , choose Maintain Catalog ID and Related Questions.




Catalog ID

Enter a unique ID for your catalog.

Example: A000

You can use up to four characters or digits.

Catalog Description Enter a description.

Example: Vehicle Check

Use Catalog Select the checkbox to use the catalog (default setting).


5. Select your previously saved catalog ID and select Questions in the structure on the left.




Catalog ID

Select your previously created catalog ID.

Example: A000

Question ID

Enter a question ID.

Example: 1

This ID represents the sequence of the questions on the mobile client.

Language

Select the language key from the input help.

Example: EN



(C) SAP AG 162


QuestionText

Enter your question.

Example: Is the tire pressure OK?

The field length is limited to 33 characters because that is the space availableon the mobile client.

8. Repeat step 7. if required.


Result

You have defined your catalog and the related questions.



(C) SAP AG 163

Maintain Catalog Determination

Once you have maintained the catalog and its questions, you need to define the catalog

determination. The determination can be set up with the following fields:

Tour scenario

Route

Shipping point

Plant

Shipment type

Visit plan type

Transportation planning point

Vehicle

Vehicle type

Country

The order of the fields already contains a form of “access sequence”, an example of which isdescribed below. Not every field needs to be populated and this allows you to reduce yourmaintenance effort.


Connectivity Vehicle Check , choose Maintain Catalog Determination.




TS Optional – Select a tour scenario from the input help.

Example: 01 Preseller

Route Optional – Enter a route from the input help.

Example: 000001

ShPt Optional – Select a shipping point from the input help.

Example: 0001

Plnt Optional – Select a plant from the input help.

Example: 0001

ShTy Optional – Select a shipment type from the input help.



(C) SAP AG 164


Example: ZMDD

VPT

Optional – Select a visit plan type from the input help.

Example:

TPPt Optional – Select a transportation planning point from the input help.

Example: ZMDD

Vehicle Optional – Select a truck from the input help.

Example: Truck_020

Vehicle Type Optional – Select a vehicle type from the input help.

Example: DSD FLEET

Cty Optional – Select a country from the input help.

Example: EN

Catalog ID Select a catalog ID from the input help.

Example: CHK4


ResultYou have defined your catalog determination.

Example

It contains a type of “access sequence”: tour scenario, route, shipping point, plant, shipmenttype, visit plan type, transportation planning point, vehicle, vehicle type, and country.

S.No.

Scenario

Vehicle

TypeVehicle Tpp

Shipment Pt

ShipmentType

VPType

Route

Plant

Country

Catalog ID

1

Deliver

ydriver

DSDFleet ZMDD

000001

0002 DE CHK1

2Deliver ydriver

DSDFleet

TRUCK001

000001

0002

DE CHK2

3Deliver ydriver

DSDFleet

TRUCK001

ZMDD

0002

DE CHK3

4Deliver ydriver

DSDFleet

TRUCK001

001000001

DE CHK4

5 Deliver y

DSDFleet

TRUCK001

ZMDD

001000001

CHK5



(C) SAP AG 165

S.No.

Scenario

Vehicle

TypeVehicle Tpp

Shipment Pt

ShipmentType

VPType

Route

Plant

Country

Catalog ID

driver

6Deliver ydriver

DSDFleet

TRUCK001

ZMDD 000001

0002

CHK6

7Deliver ydriver

DSDFleet

TRUCK001

ZMDD000001

0002

DE CHK7

8Deliver ydriver

000001

0002

DE CHK8

9Mixeddriver

DSDFleet

TRUCK001

ZMDD

001 ZMDD000001

0002

DE CHK9

The determination is as follows (scenario used: Delivery driver with shipment type ZMDD,route 000001, from shipping point 0001)

Scenario: Delivery driver -> possible catalogs CHK1 to CHK8

Route: 000001 -> CHK1, CHK2, CHK4, CHK5, CHK6, CHK7, CHK8

Shipping point 0001 -> CHK4, CHK5

Shipment type/VP type -> CHK4, CHK5

Transportation planning point: ZMDD -> CHK5 (result)



(C) SAP AG 166

DSD Connector Settings

In the DSD back end system, shipments or DSD visit lists are created and relevant

customized shipment or DSD visit list data is downloaded to the DSD connector in the form ofIDocs. Since the middleware system is unable to read these IDocs, the DSD connector mustconvert the data contained in the IDoc fields to a form that is readable by the middlewaresystem. This conversion process is called mapping. Depending on the message type of theinbound IDoc received, the system determines the corresponding connector object. Theconverted IDoc data is written (mapped) to the corresponding DSD connector table, fromwhich the system can extract the tour data and forward it to the mobile device. The linkbetween driver and vehicle is maintained in the DSD Connector Cockpit .

This section deals with all the general Customizing settings that the system needs forhandling the process of mapping and forwarding data correctly during the data download,such as maintaining the logical system or defining mapping rules.

Prerequisites

An RFC Destination pointing to the DSD Connector is defined.

Process

The Customizing tables for maintaining the DSD Connector settings are located in the

Customizing for the DSD Connector under Logistics Execution SAP Direct Store Delivery

Handheld Connectivity DSD Connector Settings .

The procedures for this process include the following:

1. Logical System Connectivity [Page 167]

2. Connectivity Objects [Page 173]

3. Mapping Rules [Page 179]

4. Types Assignments [Page 187]

5. Definitions of Reasons [Page 192]

6. Administration of Mobile Devices [Page 200]

7. Mobile Device Settings [Page 205]



(C) SAP AG 167

Logical System Connectivity

This section combines all steps that set up system connections between the middleware

system and the mobile device. For the SAP Direct Store Delivery mobile app, the middlewareis SAP Mobile Platform.

Process

The Customizing tables for Logical System Connectivity are located in Customizing for the

DSD Connector under Logistics Execution SAP Direct Store Delivery Handheld

Connectivity DSD Connector Settings Logical System Connectivity .

Setting up Logical System Connectivity consists of the following steps:

1. Define Mobile Engine Servers [Page 168]

2. Maintain Destinations of Mobile Engine Server [Page 169]

3. Set Up SAP Mobile Platform or Middleware Server SAP mDSD [Page 170]

4. Maintain EDI Port Definitions [Page 171]



(C) SAP AG 168

Define Mobile Engine Servers

You define the ID for each individual mobile engine server. Multiple mobile engine servers

can use the same DSD Connector. On each mobile engine server, you can list an unlimitednumber of mobile devices. This table is also used if you run SAP mDSD 3.0 in parallel withSAP Direct Store Delivery . In this case, you have to maintain two different IDs for eachmiddleware.

Procedure

1. In Customizing for the DSD Connector under Logistics Execution SAP Direct

Store Delivery Handheld Connectivity DSD Connector Settings Logical System

Connectivity , choose Define Mobile Engine Server.




Mobile Engine ID

Enter a numeric key with up to 2 digits for the new mobile engine to bedefined.

Example: 1

Mobile EngineServer

Enter a description for the new mobile engine server.

Example: DSD-ME01


Result

Mobile engine servers can now be identified by a numeric key and are ready to have an RFCdestination assigned.



(C) SAP AG 169

Maintain Destinations of Mobile Engine Server

You assign RFC destinations to mobile engine servers that have been created previously. By

means of this assignment, the DSD Connector can determine the target host of the mobileengine server for future identification.

Prerequisites

An RFC destination pointing to the DSD Connector is defined.

Procedure


Connectivity DSD Connector Settings Logical System Connectivity , chooseMaintain Destination of Mobile Engine Server .




MobileEngine ID

Select a Mobile Engine ID from the input help.

Example: 1

MobileEngine

Server

The mobile engine server name is automatically entered depending on thechosen Mobile Engine ID.

Example: DSD-ME01

MobileEngine Dest

Enter the RFC destination of the DSD Connector that points to themiddleware system (as created in Defining RFC Destination for BackEnd/DSD Connector [Page 19]).


Result

With the RFC destination assigned to the mobile engine server, the DSD Connector can nowidentify the target host where the mobile engine server is installed.



(C) SAP AG 170

Set Up SAP Mobile Platform or Middleware ServerSAP mDSD

SAP Direct Store Delivery supports running the SAP Mobile Direct Store Delivery (SAPmDSD 3.0) solution in parallel. The concept is based on the main restriction of assigning eachmobile user uniquely to one solution or the other. The assignment can be changed if the

mobile user is not executing a tour. In the DSD Connector Cockpit (the /DSD/ME_CPT

transaction), the mobile user can be assigned to a middleware system (MEID field) which is

used either for SAP Direct Store Delivery or SAP mDSD.

However, you need to maintain an entry here even if you just run only SAP Direct StoreDelivery .

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery HandheldConnectivity DSD Connector Settings Logical System Connectivity , choose Setup SAP Mobile Platform or Middleware Server SAP MDSD .




Mobile EngineID

Select a Mobile Engine ID from the input help.

Example: 1

Mobile EngineServer Name

The mobile engine server name is automatically entered depending on thechosen Mobile Engine ID.

Example: DSD-ME01

MDSD 3.0 Select the checkbox to activate this middleware system for SAP mDSD. Ifthis check box is not selected, this system (must be SAP Mobile Platform) isused for SAP Direct Store Delivery .


ResultYou have defined the middleware you want to use.



(C) SAP AG 171

Maintain EDI Port Definitions

You maintain actions performed during the DSD process and assign the appropriate port to

each action to enable the corresponding communication.

The following actions have been implemented and are available for use on the selection list:

Action 01 = Read DSD Transactional Data

Using the port specified in the adjacent Port field, this action reads the DSD

transactional data recorded on a specified file in the DSD back end as soon as the

DSD Connector has received the /DSD/HH_CONTROL IDoc during the download

process.

Action 03 = Send DSD Route Accounting Data

Using the port specified in the adjacent Port field, this action calls the upload BAPIsduring the upload process.

Action 12 = Call Pricing Data Extractor

Using the port specified in the adjacent Port field, this action triggers the Pricing DataExtractor on the DSD back end when the shipment IDocs have been parsed duringthe download process.

Action 01 uses a file port while actions 03 and 12 use the same transactional port.

Prerequisites

A file port and a tRFC port have been defined.

Procedure


Connectivity DSD Connector Settings Logical System Connectivity, , chooseMaintain EDI Port Definition.



Field

Name


Action Select 01 = Read DSD Transactional Data from the input help.

PORT Enter name of the File Port (as created in Define Port in Back End/DSDConnector [Page 21]).

Description The description is entered automatically depending on the selected port.

FieldName


Action Select 03 = Send DSD Route Accounting Data from the input help.



(C) SAP AG 172

FieldName


PORT Enter name of the Transactional Port (as created in Define Port in BackEnd/DSD Connector [Page 21]).


FieldName


Action Select 12 = Call Pricing Data Extractor from the input help.

PORT Enter the name of the Transactional Port (as created in Define Port in BackEnd/DSD Connector [Page 21]).



Result

You have now created the EDI port definitions on the DSD Connector.



(C) SAP AG 173

Connectivity Objects

DSD connectivity objects identify master data as well as transactional data. Message types

from the DSD back end are mapped to DSD connectivity objects. You can map more thanone message type from the DSD back end to a DSD connectivity object.

Process

The tables for the DSD connectivity objects are located in Customizing for Logistics Execution


Connectivity Objects .

Setting up connectivity objects consists of the following steps:

1. Define Connectivity Objects [Page 174]

2. Assign Function Modules to Connectivity Objects [Page 176]

3. Assign Message Types to Connectivity Objects [Page 177]



(C) SAP AG 174

Define Connectivity Objects

Connectivity objects identify master data and transactional data that are relevant within the

DSD process.

The list below contains all the connectivity objects that have been implemented. They areincluded in the shipment. The numbers are fixed and are connected with programming codefor specific processes.

001 = Shipment

002 = Route itinerary

003 = Customer delivery

005 = Material master

006 = Customer master

007 = Credit status (still needed)?

008 = Driver text

009 = Customer order

010 = Customer invoice

013 = Bill of material

You can define customer-specific objects using the customer name spaces 8* and 9* andadding them to the list.

Procedure

Make sure that all the connectivity objects are maintained in this Customizing table. In caseswhere one or more of the objects are missing or when a connectivity object is to be added tothe list, use this procedure.


Connectivity DSD Connector Settings Connectivity Objects , choose Define

Connectivity Objects.



FieldName


HH Object

Enter a numeric key with up to three digits using the customer name space forthe new connectivity object.

Example: 901



(C) SAP AG 175

FieldName


Description Enter description for the new connectivity object.


The corresponding flow logic for further processing must be reprogrammed.

Result

Only connectivity objects that are maintained in this table can be used by the system for theDSD process on the mobile device.



(C) SAP AG 176

Assign Function Modules to Connectivity Objects

The mapping of message types of the DSD back end to DSD connectivity objects also

includes how the data in the IDocs must be converted and stored in database tablescorresponding to the DSD connectivity objects. This is achieved by assigning a functionmodule to the DSD connectivity object.

When maintaining a new entry, you cannot select this function module from the input help.

Prerequisites

Connectivity objects (HH objects) must be maintained.

Procedure


Connectivity DSD Connector Settings Connectivity Objects , choose AssignFunction Modules to Connectivity Objects.




Conn. Object Select a connectivity object from input help.

Example: 003 (Customer Delivery)

Seq. No (SequenceNumber)

Enter a number that is sequential within the same HH object.

FunctionModule

Enter the /DSD/ME_MAINTAIN_DATA function module. This is the function

module for the default behavior of the mobile DSD solution. You can developfunction modules for your own purposes to realize new or changedfunctionality. The interface of the user-defined function module must be the

same as the interface of /DSD/HH_MAINTAIN_DATA .

Actv. (Activate)

Activate the entry by selecting the checkbox.


Result

You have now assigned the function module to the DSD connectivity object that converts thedata in the IDoc structures to the database tables of the DSD Connector corresponding to theDSD connectivity object.



(C) SAP AG 177

Assign Message Types to Connectivity Objects

You assign to each DSD connectivity object one or more message types of the DSD back

end. The data from incoming IDocs is converted and stored in database tables according tothe underlying message type assigned to the DSD connectivity object.

Prerequisites

Connectivity objects are maintained.

Message types are defined.

Procedure


Connectivity DSD Connector Settings Connectivity Objects , choose AssignMessage Types to Connectivity Objects.




Conn. Object Select an HH object (connectivity object) from the input help.

Example: 001 (Shipment)

Message Type Select a message type from the input help.


4. Repeat step 3. for all message types related to a specific HH object as listed in thefollowing table.

HH Object Message Type

001 Shipment /DSD/HH_CONTROL

SHPMNT

002 Route Itinerary /DSD/HH_ROUTE_ITINERARY

003 Customer Delivery DESADV

005 Material Master MATMAS

/DSD/HH_MATMASTEXT

006 Customer Master DEBMAS

/DSD/HH_CUSTMASTEXT

/DSD/HH_PAYMMASTEXT



(C) SAP AG 178

HH Object Message Type

007 Credit status CRESTA

008 Driver Text /DSD/HH_TXTDRV

009 Customer order ORDRSP

010 Customer Invoice

INVOIC

Only for use together with SAP mDSD 3.0.

013 Bill of Material BOMMAT


Result

When you have made these settings, the system is able to convert the data from incomingIDocs for all message types that are assigned to the corresponding connectivity object in thisCustomizing table.



(C) SAP AG 179

Mapping Rules

The DSD Connector receives IDocs from the back end containing the data for a specific tour.

Since the mobile engine cannot process IDocs, it is necessary to map the field values of theincoming IDocs to the DSD Connector tables. This mapping process is performed on the DSDConnector system. For this purpose, a set of mapping rules (data records) must bemaintained in the DSD Connector.

Process

The tables to maintain the mapping rules are located in Customizing for Logistics Execution


Mapping Rules.

To set up mapping rules, proceed as follows:

1. Define Function Modules for Mapping [Page 180]

2. Define Mapping Rules [Page 181]



(C) SAP AG 180

Define Function Modules for Mapping

During the mapping process, function modules use the same interface. Using the interface,

the system imports the current mapping rule entry as well as the field value from a specificIDoc segment and exports the converted value. Therefore, you can share the same functionmodule to convert multiple fields. The function modules are called dynamically during IDocparsing. Whenever a function module is defined for a given IDoc field, the IDoc parser in theDSD Connector triggers this specified function module when parsing a certain IDoc field.

If one of the mapping rules that you have defined requires special handling, you need todefine a corresponding function module where the interface must be the same as thosefunction modules delivered and listed below. This new function module must then be insertedin this Customizing table. In case you have also defined mapping rules, you can assign thenew function module to your new mapping rules.

The list below contains all the function modules for mapping that have been implemented.

They are included in the shipment.

/DSD/ME_CONVERT_ME_ACTION

/DSD/ME_MAP_RULE01

/DSD/ME_MAP_RULE02

/DSD/ME_MAP_RULE03

/DSD/ME_MAP_RULE04

/DSD/ME_MSG_HD_DSDC

/DSD/ME_MSG_HD_LINE_RESET

/DSD/ME_SET_RETURN_FLAG

/EMSE/ME_SET_SALESAREA_ORDERS

You can define customer-specific function modules using the customer name spaces Y* andZ* and adding them to the list.

Procedure


Connectivity DSD Connector Settings Mapping Rules , choose Define FunctionModules for Mapping .


3. On the screen that appears, enter the name of the new function module to be used bythe system for the mapping process in the Conversion field.


Result

All function modules maintained in this table are now available for the system to be usedduring the mapping process.



(C) SAP AG 181

Define Mapping Rules

In this IMG activity, you make entries in the table to control how incoming IDoc fields for each

message type are mapped to DSD Connector table fields.

Mapping rules are shipped with client 000 and need to be transported to the copy client.

Prerequisites

Connectivity objects exist.

Message types are defined.


Connectivity DSD Connector Settings Mapping Rules , choose Define MappingRules.




Conn. Object

Select the HH (handheld) object (connectivity object), for which you

want to maintain an entry, from the input help.

Example: 001 (Shipment)

Issue Enter the next sequential number that is within the same HH object.

Example: 23

DSD Connector:Define MappingRules

Message Type

Enter the name of the message type of the incoming IDoc dependingon the HH object selected.

Example: SHPMNT

Segment Enter the name of a segment contained in the selected message type.

Example: E1EDT20

Source Field

Enter the name of a field contained in the segment selected. It is thesame name that the field is given in the SAP back end system.

Example: SHTYP (Shipment Type)

Quality Field Optional: Enter the name of the field that should be used as a filter, if



(C) SAP AG 182


desired.

Qualifier Optional: Enter the value of the filter, if desired.

Table Name

Enter the name of the DSD Connector table in which the correspondingfield is located and to which the IDoc field should be mapped.

Example: /DSD/ME_TOUR_HD

Target Field

Enter the name of the corresponding field in the DSD Connector tablesto which the IDoc field should be mapped.

Example: SHIP_TYPE

Group Change

Each mapping rule entry is mapped to a DSD Connector table (see theTable Name field). If the mapping rule entry constitutes the last field

within the same DSD Connector table, enter the value X here.

Conversion If an extra conversion of the field value is needed, enter the appropriatefunction module.

Actv. (Activate) Activate the entry by selecting the checkbox.

Repeat step 3. for the IDoc field of each segment of each message type related to aspecific DSD Connector type. For more information, see the following table:

You should maintain entries for the fields and segments of the following messagetypes related to the connectivity type indicated:

Connectivity Type Message Type

001 Shipment /DSD/HH_CONTROL

SHPMNT

002 Route Itinerary /DSD/HH_ROUTE_ITINERARY

003 Customer Delivery DESADV

005 Material Master MATMAS

/DSD/HH_MATMASTEXT

006 Customer Master DEBMAS

/DSD/HH_CUSTMASTEXT

/DSD/HH_PAYMMASTEXT

007 Credit status CRESTA

008 Driver Text /DSD/HH_TXTDRV



(C) SAP AG 183

Connectivity Type Message Type

009 Customer order ORDRSP

010 Customer invoice INVOIC

013 Bill of Material BOMMAT

If you wish to use a customer-specific return item category instead of the standard,you must adjust the corresponding mapping rule as follows:

1. Locate the following entry on the mapping rule table:

Connectivity Object 3

Issue 31

Message Type DESADV

Segment E1EDL26

Source Field PSTYV

Quality Field PSTYV

Qualifier REN

Table Name /DSD/ME_DEL_ITM

Target Field RTN_FLAG

Conversion /DSD/ME_SET_RETURN_FLAG

2. Replace the existing value in the Qualifier field with your own customer-

specific return item category.

3. Save your entry.

The entry made in the Qualifier field triggers the system to interpret the item categoryas returns.

If you use more than one return item category or if you use return item categories forEMPTIES, then you need to maintain a separate entry for each individual (empty)return item category. In such cases, proceed as follows:

1. Copy the adjusted mapping rule for return item category (describedpreviously).

2. Change the value in the Issue field. Enter the next open sequential numberfor the Connectivity Object .

3. Change the value in the Qualifier field. Enter one of the additional return itemcategories to be maintained.



(C) SAP AG 184

4. Save your entry.


With SAP Direct Store Delivery , some new features are implemented, for example, Multiple

Sales Area support and suggested order process, and some new /EMSE/ fields (for example,

for tax information) have been appended to existing /DSD/ME tables or newly created tables(for example, /EMSE/ME). Therefore, check if the following mapping rules have been

maintained in your system:

DESADV:

ConnectivityObject

3 3 3

Issue For example, 48 For example, 49 For example, 50

Message Type DESADV DESADV DESADV

Segment E1EDL20 E1EDL24 E1EDL24

Source Field VKORG VTWEG SPART

Quality Field

Qualifier

Table Name /DSD/ME_DEL_HD /DSD/ME_DEL_ITM /DSD/ME_DEL_ITM

Target Field

/EMSE/SALES_OR

G

/EMSE/DIST_CHANNE

L /EMSE/DIVISION

Conversion

MATMAS:

ConnectivityObject

5 5 5


Message Type MATMAS MATMAS MATMAS

Segment E1MLANM E1MLANM E1MVKEM

Source Field TATY1* TATY2* MVGR1

Quality Field

Qualifier

Table Name /EMSE/TAX_CAT1 /EMSE/TAX_CAT2 /DSD/ME_MAT_SOR

Target Field /EMSE/SALES_ORG /EMSE/DIST_CHANNEL /EMSE/SEQU_ID



(C) SAP AG 185

Conversion

* For taxes, SAP Direct Store Delivery supports up to four tax categories.

DEBMAS:

Connectivity Object 6 6 6


Message Type DEBMAS DEBMAS DEBMAS

Segment E1KNVVM E1KNVVM E1KNVIM

Source Field KALKS VSORT TATYP*

Quality Field TATYP

Qualifier MWST

Table Name /DSD/ME_CUST_SA /DSD/ME_CUST_SA /DSD/ME_CUST_TAX

Target Field /EMSE/KALKS /EMSE/VSORT /EMSE/TAX_CAT1

Conversion

* For taxes, SAP Direct Store Delivery supports up to four tax categories. For each qualifier,you need an entry.

ORDRSP:

Connectivit y Object

9 9

Issue For example, 30 For example, 31

MessageType

ORDRSP ORDRSP

Segment E1EDK01 E1EDK01

Source

Field BELNR BELNR

QualityField

Qualifier

TableName

/DSD/ME_ORD_HD /DSD/ME_ORD_HD

TargetField

/EMSE/SALES_ORG /EMSE/DIST_CHANNEL

Conversion /EMSE/ME_SET_SALESAREA_ORDE /EMSE/ME_SET_SALESAREA_ORDE



(C) SAP AG 186

RS RS

Connectivity Object 9

Issue For example, 32

Message Type ORDRSP

Segment E1EDK01

Source Field BELNR

Quality Field

Qualifier

Table Name /DSD/ME_ORD_HD

Target Field /EMSE/DIVISION

Conversion /EMSE/ME_SET_SALESAREA_ORDERS

Result

With all the entries maintained in this table, the system is now able to map the incoming IDocfields to the correct fields in the DSD Connector.



(C) SAP AG 187

Types Assignments

In this section, you maintain settings that help you control mobile devices with regards to type

allowance and type meaning. You use types to control which aspects of selected back endobjects (for example, invoice document types, material types, and item categories) should beallowed on mobile devices and which meaning these aspects have in the mobile app.

Process

The tables for assigning various document types are located in Customizing for Logistics

Execution under SAP Direct Store Delivery Handheld Connectivity DSD Connector

Settings Types Assignments .

To set up types assignments, proceed as follows:

1. Assign Material Types to DSD Connectivity Material Types [Page 188]

2. Assign Document Types to DSD Connectivity Document Types [Page 189]

3. Assign Invoice Document Types as Criteria for Open Items [Page 190]



(C) SAP AG 188

Assign Material Types to DSD ConnectivityMaterial Types

You assign material types, maintained in the DSD back end, to DSD Connectivity materialtypes that need to be distinguished on the mobile device.

For the DSD Connectivity material type EMPTIES, you define which material types on theDSD back end identifies a material on the mobile device as an EMPTY .

The mobile device can display untied empties (empties returned from a customer) separatelyin the inventory. Tied empties, however, can only be displayed in connection with the fullproducts to which they are connected. The mobile device needs to be able to distinguishwhether a downloaded material is a full product or whether it belongs to empties. This isespecially important for pricing determination.

Prerequisites

Material types are available for selection.

Item categories for a given material type (for example, empties) have been defined.

Procedure


Connectivity DSD Connector Settings Types Assignments , choose Assign

Material Types to DSD Connectivity Material Types.



FieldName


MaterialType

Select a DSD Connectivity material type from the input help provided.

Example: EMPTIES

MaterialType

Enter the material type customized in the DSD back end that identifies amaterial as belonging to the selected DSD Connectivity material type.

Example: LEER


Result

When receiving a downloaded order or delivery, the system checks the entries made in thistable and recognizes from the settings whether or not an order item or delivery item is to beconsidered as an empty material; in other words, the system determines to which materialtype a specific material belongs.



(C) SAP AG 189

Assign Document Types to DSD ConnectivityDocument Types

In this IMG activity, you control which open items are downloaded to the mobile device. Openitems for a customer can result from invoices that occurred in the Sales and Distribution (SD)component, however, other Financial Accounting (FI) documents may lead to the creation ofan open item (for example, payment of rental fees).

You maintain the document types that the system uses as a filter when selecting existingopen items for a given customer that should be downloaded to the mobile device. The systemdoes not download any open items for a specified customer in the DSD back end that useddocument types not maintained in this table.

If you omit the optional procedure, the system selects all open items related to thedownloaded customers and makes them available on the mobile device.

Procedure


Connectivity DSD Connector Settings Types Assignments , choose AssignDocument Types to DSD Connectivity Types.




AllowedDocumentType

Select DOC_TYPE Document Type as Type for Open Items from the inputhelp.

DocumentType

Enter an accounting document type that is customized and used in theDSD back end for creating open items, for example, during the standardSD billing procedure.

Example: RV


ResultFrom the entries maintained in this table, the system determines which open items should bedownloaded to the mobile device for a given customer. Only those open items created withdocument types maintained in this table are downloaded.



(C) SAP AG 190

Assign Invoice Document Types as Criteria forOpen Items

In this IMG activity, you maintain the document types that had open items resulting from aback end Sales and Distribution (SD) invoice. By maintaining them in this table, the mobiledevice is able to recognize the correct origin of an open item (the SD invoice) after it isdownloaded to the mobile device.

Whenever open items are downloaded at the beginning of a tour and are uploaded again atthe end of the tour, the DSD back end must know the origin of the document that caused theopen item to be created. This is due to the fact that after the upload, open items aredistinguished in the Settlement Cockpit of the DSD back end by various types of documentorigins.

Currently, the following four types of document origins for open items are implemented in the

Settlement Cockpit :

10 for R/3-Invoice (if the open item resulted from a SD invoice created in the backend)

20 for External Invoice (if the open item resulted from an invoice that was created onthe mobile device)

30 for External Delivery (if the open item resulted from a delivery that was created onthe mobile device)

40 for Open Items that have no relation to an SD invoice.

The origin provides important information for the clearing process. Open items with origin 40are processed differently than open items with origin 10.

Entries maintained in this Customizing table do not influence the download of open items butthey do control which clearing type is set to an open item on the mobile device. If you do notmaintain any entries in this table, then all downloaded open items receive the clearing type 10after the upload.

Prerequisites

You have defined invoice document types representing open items, for example, RV.

Procedure


Connectivity DSD Connector Settings Types Assignment , choose Assign InvoiceDocument Types as Selection Criteria for Open Items.




InvoiceType

Choose the entry INV_TYPE Invoice Type as Selection Criteria for OpenItems from the input help.

Document Enter an accounting document type that is customized and used in the DSD



(C) SAP AG 191


Type back end system for creating open items, for example during standard SD

billing process.

Example: RV


Result

The document types maintained in this procedure are recognized on the mobile device asback end downloaded invoices. As a result of this, the document type in the upload clearing isfilled with 10 , which means a back end downloaded invoice.



(C) SAP AG 192

Definitions of Reasons

In mobile DSD scenarios, reasons are used for informational purposes. At various points

throughout the DSD process, it is useful and sometimes required to record the reason for aspecific entry to keep information about why a certain action produced a result at variancefrom that expected or initially planned. This may be the case if, for example, deliverieschange, a customer declines to make a payment, or a visit needs to be canceled.

In the back end, reasons are maintained in Route Accounting . These reasons are alsoneeded on the mobile device. As the DSD mobile app is a stand alone application, it is notpossible to make references to the standard tables. Therefore, manual double maintenance isnecessary for the reasons tables.

Only enter reasons that are also maintained in the corresponding table in Route Accounting .

Process

The following steps for maintaining various types of reasons are located in Customizing forLogistics Execution under SAP Direct Store Delivery Handheld Connectivity DSD

Connector Settings Reasons :

1. Defining Reasons for Differences for Check-In and Check-Out [Page 193]

2. Defining Reasons for Changing Deliveries and Orders on DSD Connector [Page 194]

3. Defining Customer Visit Reasons [Page 196]

4. Create Reason Types and Characteristics [Page 197]

5. Assign Reason Codes to Reason Types [Page 198]

6. Assign Tour Scenario to Reason Types [Page 199]



(C) SAP AG 193

Define Reasons for Differences for Check-In andCheck-Out

In this IMG activity, you define the reasons for differences determined during check-out orcheck-in procedures. These reasons can be used to classify the check-out/check-indifferences of the stock on trucks.

Possible reasons for differences are as follows:

Product damaged in transit

Mistakes (for example, the wrong freight list)

Theft of product

Only reasons that are maintained here are allowed on the mobile device. They can be few in

number but those entered should be identical to those in the /DSD/HH_RACKD_V

Customizing table in Route Accounting .

Prerequisites

Reasons for differences for check-in and check-out are defined in the corresponding

/DSD/HH_RACKD_V Customizing table in Route Accounting .

Process


Connectivity DSD Connector Settings Reasons , choose Define Reasons for

Differences for Check-in and Check-out .




COCI Reason Enter a two-digit key for the difference reason to be defined.

Example: M1

Description


Example: DAMAGED IN TRANSIT


Result

Only those reasons that are maintained in this /DSD/ME_COCI_RST Customizing table are

available for use on the mobile device during check-out and check-in procedures.



(C) SAP AG 194

Define Reasons for Changing Deliveries andOrders on the DSD Connector

In this IMG activity, you maintain reasons that define why the outbound delivery quantitydiffers from the original planned delivery quantity. In other words, these reasons classifydeviations from the original planned delivery quantity. All reason codes maintained in thistable are downloaded to the mobile device.

The following are examples of possible reasons:

A customer orders more or less than originally planned.

A store is closed.

There is less stock available on truck than required and, therefore, the delivered

quantity has to be changed.

Only the reasons that are maintained here are allowed on the mobile device. A few reasons

are sufficient, however, they should be the same as the reasons in the /DSD/HH_RAREAS_V


Prerequisites

Reasons for changing deliveries are defined in the corresponding /DSD/HH_RAREAS_V


Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery HandheldConnectivity DSD Connector Settings Reasons , choose Define Reasons forChanging Deliveries and Orders.




ChangeReason

Enter a two-digit key for the change reason to be defined.

Example: M1

Description Enter an appropriate description.

Example: INCORRECT ORDER

Chg. ReasonBehavior

Select a behavior code from the selection list provided.

Example: Damaged Goods Return

With the entry made in this field, it is possible to control into which type of

stock the returned material should be moved (for example, with the entryDAMAGE RETURN, the material that has been recorded with this reason code



(C) SAP AG 195


will be moved into the BLOCKED STOCK stock type).

The Change Reason Behavior codes are hard-coded. They are downloadedto the device and cannot be changed on the device.

When using the functionality DSD Deal Condition-Free Goods, two reason codes arerequired for proper processing. Free goods may or may not contain a tied empty;thus, it is possible to distinguish whether the whole material (including the tied empty)is free-of-charge or whether only the main item remains free-of-charge while the tiedempty is chargeable. In each of these two cases, a separate reason code is required.

For proper processing, the following Customizing is needed:

o Definition of two reason codes in the /DSD/ME_CHG_RSN DSD Connector

table.

o Assignment of the two reason codes to a specific Change Reason Behavior

in the /DSD/ME_CHG_RSN DSD Connector table, depending on whether or

not the tied empty should be charged.

Change Reason Behavior A

Indicates that only the main item is free-of-charge, but the tied emptyis charged, for example, reason code 11 with behavior A

Change Reason Behavior B

Indicates that the complete item, that is main item plus tied empty, isfree-of-charge, for example, reason code 12 with behavior B

o Maintenance of the Customer Sales Transaction Type Determination with

reason code assignment in the /DSD/SL_TC_CTRL back end table.

If you do not wish to maintain this determination configuration for the DSDDeal Condition-Free Goods, you must implement the

BADI_ORDITM_CHANGE method of the /DSD/SL_FSR_DEFFMT_P BAdI

(implementation in customer name space). For the BAdI implementation, it isnecessary to change the item category of the material items with reason

codes 11 and 12 (or other reason codes assigned to behavior A or B). The

item categories need to be maintained to cover complete free good

processing and main item free but subitems with deposit (full product free,empty charged) processing.


Result

Only the reasons that are maintained in this /DSD/ME_CHG_RSN Customizing table areavailable for use on the mobile device during tour execution.



(C) SAP AG 196

Define Customer Visit Reasons

In this IMG activity, you can define customer visit reasons to describe a visit to a customer in

detail. The classification itself does not initiate any operative activities.

Cancellation of a customer visit requires a reason code to be entered.

Only those reasons that are maintained here are allowed on the mobile device. They can be

few in number but those entered should be identical with those in the /DSD/HH_RAVISC_V


Prerequisites

Reasons for customer visit reasons are defined in the corresponding /DSD/HH_RAVISC_V


Procedure


Connectivity DSD Connector Settings Reasons , choose Define Customer VisitReasons.




Visit Reason Enter a two digit key for the visit reason to be defined.

Example: M1

Description Enter a description.

Example: PRESALES VISIT


Result

Only those reasons that are maintained in this /DSD/ME_VISIT_RT Customizing table are

available for use on the mobile device during the tour.



(C) SAP AG 197

Create Reason Types and Characteristics

In this IMG activity, you can control in detail where a reason code is used on the mobile cl ient.

Depending on the settings here, you can define in which mobile activity the reason is shownand can be used.

Procedure


Connectivity DSD Connector Settings Reasons , choose Create Reason Typesand Characteristics.




Reason Type Enter a two digit key for the visit type to be defined.

Example: 01


Example: No sales reasons

Ord Hd Defines the behavior of a reason for order header activity

Delv Hd Defines the behavior of a reason for delivery header activity

Order item Defines the behavior of a reason for order item activity

Delv Itm Defines the behavior of a reason for delivery item activity

Return Ord Defines the behavior of a reason for return order activity

Return Delv Defines the behavior of a reason for return delivery activity

Normal Order Defines the behavior of a reason for normal order activity

Normal Delv Defines the behavior of a reason for normal delivery activity

Free Ord Defines the behavior of a reason for free order activity

Free Delv Defines the behavior of a reason for free delivery activity

Return Ind. Defines the behavior of a reason for return delivery/order activity

CollcRvk Defines the behavior of a reason for collection revoking activity


ResultYou have defined the characteristics per reason type.



(C) SAP AG 198

Assign Reason Codes to Reason Types

In this IMG activity, you can assign your reason codes to various reason types. You can only

use reason types that have been defined in the previous step.

The reason codes that are considered in this table can be maintained in Customizing for

Logistics Execution under SAP Direct Store Delivery Route Accounting Basic Functions

Define Reasons for Changing Deliveries.

Procedure


Connectivity DSD Connector Settings Reasons , choose Assign Reason Codes toReason Types.




Reason Select a reason code from the input help.

Example: 01

Description Description is automatically populated from the reason code.

Example: Incorrect order

Reason Type Select a reason type from the input help.

Example: 01 No Sales Reasons

Description Description is automatically populated from the selected reason type.


Result

You have now assigned all possible reason codes to a reason type.



(C) SAP AG 199

Assign Tour Scenario to Reason Types

In this IMG activity, you assign your previously defined reason types to a tour scenario. Only

those reason types with properly assigned reason codes are then available on the mobileclient.

Procedure

1. in Customizing for Logistics Execution under SAP Direct Store Delivery Handheld

Connectivity DSD Connector Settings Reasons , choose Assign Tour Scenariosto Reason Types.




Tour Scenario Select a tour scenario from the input help.


Shp/VP Type Select appropriate shipment or visit plan type from the input help.

Example: MPS

Reason Type Select a reason type from the input help.

Example: 01 No Sales Reasons

Description Description is automatically populated from the selected reason type.


5. Repeat step 3. as often as required.

Result

You have assigned the reason types to a tour scenario thus ensuring that the reason codescan be used on the mobile client.



(C) SAP AG 200

Administration of Mobile Devices

In this section, you maintain Customizing settings that enable an administrator to control the

accessibility of specified transactions on the mobile device by mobile users. Groups andgroup-specific roles are linked and can be given a password. In this way, security measureson mobile devices can easily be administered.

Process

The tables for settings for the administration of mobile devices are located in Customizing for

Logistics Execution under SAP Direct Store Delivery Handheld Connectivity DSD

Connector Settings Administration of Mobile Devices .

Setting up the administration of mobile devices consists of the following steps:

1. Define Mobile Device Groups [Page 201]

2. Define Group-Specific Roles [Page 202]

3. Assign Group-Specific Roles to Mobile Device Groups [Page 204]



(C) SAP AG 201

Define Mobile Device Groups

In this IMG activity, you can define mobile device groups as needed or wanted. Mobile device

groups may consist of an unlimited number of roles that have passwords assigned to them;however, a group can also exist without any roles assigned to it. The mobile device group islinked to a driver through the DSD Connector cockpit and ensures that all roles andpasswords are downloaded to the mobile device.

Procedure


Connectivity DSD Connector Settings Administration of Mobile Devices , chooseDefine Mobile Device Groups.



FieldName


Group

Specify an alphanumeric key with up to 20 characters for the new mobiledevice group.

Example: CHECKER

Description Enter a description of the group being defined.

Example: CHECKER


Result

Mobile device groups have been defined and are ready to be used for linkage with group-specific roles.



(C) SAP AG 202

Define Group-Specific Roles

In this IMG activity, you define group-specific DSD roles as needed or wanted.

The roles defined here are only relevant on the mobile device and not in the DSD back end.

The following roles are used and required on the mobile device by SAP Direct Store Delivery ,for example, for canceling visits during a tour (if that functionality is active):

Role ID Use of Password

ACCOUNTANT

For payments confirmation during check-out/check-in

You can define several accountant roles and assign them differentpasswords. The prerequisite is that all role names start with“Accountant”, for example, Accountant01 and Accountant02. The clientchecks if the password entered fits to one of the two roles during theprocess.

CHECKER

For Check-out/Check-in Materials/Counting Groups

You can define several checker roles and assign them differentpasswords. The prerequisite is that all role names start with “Checker”,

for example, Checker01 and Checker02. The client checks if thepassword entered fits to one of the two roles during the process.

DRIVER Cancel visit step in visit or visit list

ADMINISTRATOR

Client reset on the main menu

SUPERVISOR Inventory adjustments

Procedure


Connectivity DSD Connector Settings Administration of Mobile Devices , chooseDefine Group-Specific Roles.



FieldName


Role ID

Specify an alphanumeric key with up to 20 characters for the new DSD cockpitrole.

Example: CHECKER



(C) SAP AG 203

FieldName


Description Enter a description of the role being defined.

Example: CHECKER FOR CHECK-OUT/IN


Result

Group-specific DSD cockpit roles have been defined and are ready to be used for linkage withmobile device groups.



(C) SAP AG 204

Assign Group-Specific Roles to Mobile DeviceGroups

In this IMG activity, you assign roles to mobile device groups. You can assign several roles toone group. Likewise, the same role can be assigned to more than one group.

You also assign a password to each combination of group and role. You maintain a set ofpasswords here. The role-dependent password allows the control of the access to a specifiedset of functions or transactions on the device. Passwords are downloaded to the mobile client.

Prerequisites

Mobile device groups are defined.

Group-specific roles are defined.

Procedure


Connectivity DSD Connector Settings Administration of Mobile Devices , choose Assign Group-Specific Roles to Mobile Device Groups.




Group Specify a mobile device group as previously defined.

Role ID Specify a role as previously defined.

Password Enter a password for the new combination of group/role.


Result

Users who are assigned a role and a mobile device group are now authorized for certainfunctions on the mobile device.



(C) SAP AG 205

Mobile Device Settings

In this section, you maintain Customizing settings that enable an administrator to control the

mobile app on mobile devices. You can define the settings so that this control takes effect asfollows:

At a global level

Global settings have an influence on all mobile devices used within the system.

For specific groups

Group-specific settings concern all devices that belong to the specified group.

This section also deals with those Customizing tables where the entries made take a process-oriented control on the mobile app itself. These settings define which tour scenario (for

example, presales or van sales) the mobile app is dealing with during a given tour.

Mobile device settings use pre-defined parameters for which customer-specific values aremaintained during configuration. Each parameter consists of the combination Source andCustomizing Key whereby the Source identifies the basic meaning of the parameter (forexample, FORMAT ) and the Customizing Key identifies a certain aspect of that source (forexample, CURRENCY_DISP ). Values can be numeric or alphanumeric, depending on thecombination of Source and Customizing Key .

The following table contains all mobile device parameters that are implemented and areincluded in the shipment.

Source Customizing Key Possible Values

Account Group

ACCOUNT_GRP CPD CPD = Account group of one-time (CPD)customer

Signature Size

SIGNATURE_SIZE VGA

Specifies the size for signature if you areusing a device with VGA resolution.

Values are in kilobytes.

Recommended value is 2600

SIGNATURE_SIZE QVGA

Specifies the size for signature if you areusing device with QVGA resolution.

Values are in kilobytes.




(C) SAP AG 206


Loading Confirmation

COCI_METHOD CO_CG

X = Counting default level is CG

blank = Counting default level is materialin case of check-out

COCI_METHOD CI_CG

X = Counting default level is CG

blank = Counting default level is materialin case of check-in

COCI_METHOD RLD_COCI_CG X = Counting default level is CG

blank = Counting default level is material

Check-out / Check-in

COCI_METHOD CO_BLIND blank or X.

X = Blind check-out

COCI_METHOD CI_BLIND blank or X .

X = Blind check-in

COCI_METHOD RLD_COCI

COCI_METHOD RLD_COCI_BLIND

blank or X .

X = Blind reload check-in and blind check-

out

Country

COUNTRY CPD Default country for one-time customer

Currency

CURRENCY CURR EUR = Currency used on device is EURO

Driver Language

DRIVER_LANG DLANG EN = Language driver uses on device isEnglish

DRIVER_COUNTRY DCOUNTRY US = Country where the tour is performed;this entry identifies the culture informationon the device.

Currency and QuantityFormat

FORMAT CURRENCY_DISP ###,##0.00



(C) SAP AG 207


Display format of currency

FORMAT QUANTITY_DISP

###,##0

Display format of quantities

Language

LANGUAGE LANG1

Optional

If parameter is maintained, then it must befilled with a language ID, for example, E for English (only one digit).

Use the same language as the driverlanguage.

LANGUAGE LANG2

Optional

If parameter is maintained, then it must befilled with a language ID, for example, E for English (only one digit).

Use the same language as the driver

language.

Capture on Hand

COH COH_DAYS

While using the capture on-hand process,this parameter controls after how manydifferent entries for one customer persales area the data will be deleted duringupload.


Customer Hierarchy

Cust_Hier HIER_TYPE This specifies used customer hierarchytype on the device.

Pricing – Valid No. ofDays

PRICING VALID_DAYS Determines number of valid days forpricing (1, 2, and so on)

Product Security



(C) SAP AG 208


Standard

INPUT_MAX_FILE_SIZE MAX_FILE_SIZE

Specifies the file size for report templates,log file, and config. file. The entry ismaintained in Kilobyte. The recommendedsize is a value 3 - 5 Megabyte.


Time Zone

TIME_ZONE TZONE Time zone

Unit of Measure of

Distance

TOUR_DIST DIST KM = Unit of measure for distance iskilometers

Untied Empties

UNTIED_EMPTIES IS_ENABLED blank or X .

X = Add Untied Empty button is enabled

ISOCODE Setting

USE_ISOCODE CURRENCY blank or X .

Use ISO Code for currency

USE_ISOCODE UOM blank or X .

Unit of measurement

CRM Settings

CRM_ACTIVITY

TIME_CAPTURIN

G

Blank or Auto

Auto = Automatic recording of start/endtime for CRM activities

You can define your own customer-specific parameter to be used by the DSD Connector orthe mobile app on the mobile device.

The corresponding flow logic for further processing of the new parameter has to beprogramed.

You can maintain the same parameters on more than one level, namely on a global

level and on a group-specific level. This is needed in cases where selected groups ofmobile devices should use different values of the same parameter.



(C) SAP AG 209

Settings made on the lower level always overwrite corresponding settings on thehigher level. In other words: Group-Specific Settings have priority over GlobalSettings.

Process

The tables for mobile device settings are located in Customizing for Logistics Execution under

SAP Direct Store Delivery Handheld Connectivity DSD Connector Settings Mobile

Device Settings .

In order to setup the necessary Customizing for the mobile devices, you need to perform thefollowing steps:

1. Define Global Mobile Device Settings [Page 210]

2. Define Group-Specific Mobile Device Settings [Page 211]

3. Define Tour Scenario Settings [Page 213]

4. Define General Settings [Page 226]



(C) SAP AG 210

Define Global Mobile Device Settings

In this IMG activity, you can define settings that allow you to control the mobile app on mobile

devices on a global level. This means that settings made in the global section of this IMGactivity are valid for all mobile devices concerned.

In order to view the list of all parameters available, together with their possible values andvalue meanings, see the section Mobile Device Settings [Page 205].

Procedure

1. In Customizing for Logistics Execution on the DSD Connector under SAP Direct

Store Delivery Handheld Connectivity DSD Connector Settings Mobile Device

Settings , choose Define Mobile Device Settings.

2. Choose Global Settings.



Source Select a source from the input help.

Example: CURRENCY

Customizing Key

The value is automatically entered depending on the

source chosen.

In the given example: CURR

Description The description is automatically entered if it ismaintained in the definition table.

Shrt Dscrp (Short Description)The description is automatically entered if it ismaintained in the definition table.

DSD CN: Global Customizing forMobile Devices

Cust. Value Enter the desired value for the new setting.

Example: EUR




(C) SAP AG 211

Define Group-Specific Mobile Device Settings

In this IMG activity, you can define settings that allow you to control the mobile app on a

specified group of mobile devices. This means that settings made in the group-specificsection of this IMG activity are valid for all mobile devices that are assigned to the group forwhich the settings are maintained.

Procedure


Connectivity DSD Connector Settings Mobile Device Settings , choose DefineMobile Device Settings.

2. In the selection dialog box, choose Group-specific Settings.



Group Select a valid group.

Source

Select an origin using the input help.

The input help for the Origin contains a list of all allowed entriesthat we deliver. You cannot make any additional entries in thislist.

Example: DRIVER_LANG

Customizing Key

The Customizing key is automatically entered depending on theorigin chosen. If there are more entries available, you have toselect the appropriate one from the input help.

The input help for the Customizing Key contains a list of allallowed entries that are we deliver. You cannot make anyadditional entries in this list.

In this example: DLANG

Description The description is automatically entered if it is maintained in thedefinition table.

Shrt Dscrp (ShortDescription)

The description is automatically entered if it is maintained in thedefinition table.

DSD CN: Group-SpecificCustomizing for MobileDevices

Cust. Value Enter the desired value for the new setting.



(C) SAP AG 212


Example: EN


Result

Entries made in Global Settings or Group-Specific Settings take effect on the individualdevices for which the settings are maintained.



(C) SAP AG 213

Define Tour Scenario Settings

In this IMG activity, you need to enable the functions you want to use on the mobile device for

each relevant scenario. In addition, you can setup different settings for the same tourscenario, depending on shipment type or visit plan type. The table controls general processavailability and/or specific functions in processes.

You can turn on/off the reload process completely.

This setting then enables or disables all related screens and menu items.

You can adjust the delivery process, for example, to increase product quantity.

Procedure1. In Customizing for Logistics Execution on the DSD Connector under SAP Direct

Store Delivery Handheld Connectivity DSD Connector Settings Mobile Device

Settings , choose Define Tour Scenario Settings.




Tour Scenario

Select a scenario from the input provided.

Example: 02 Van Sales Scenario

Shp/VP Type Optional: Enter a shipment type or visit plan type.

Description Enter a description for your settings.


5. Select your previously saved entry and step through the different structures shown onthe left tree.


Dialog Structure: General

For each function, select thedesired option

(disabled/enabled) from thedrop-down list.


Reload Enable/Disable

Visit Time Capture 0 – No time capturing



(C) SAP AG 214





1 – Manual

2 – Automatic

3 – Barcode

For more information about this setting, see BarcodeSupport for Recording Visit Times on Mobile Device[Page 239].

Capture Odom. Visit Enable/Disable

Partner Roles

0 – Sold-to

1 – Ship-to

2 – Both

Download P Role Data Enable/Disable

Filter Prd Hier Lev1

Enable/Disable

On the client we support a filter up to 4 product hierarchylevels. Here, you can select which levels should beconsidered. If you enable more then 4 levels, the systemconsiders the first 4 levels starting from the first enabledlevel.

Filter Prd Hier Lev2 Enable/Disable








Empties Qty Field 1 Select field from the input help.



(C) SAP AG 215





Defines which fields from the /BEV1/EMLGBSD table are

relevant for downloading the initial empties balance.

If you mark more than one field for downloading, thesystem adds the quantities of the fields.




Material Short Desc Select field from the input help.

Empties Management

Enable/Disable

If you enable this button, the system downloads the initialbalance, prints an empty block on the documents, andempties reporting is available on the device.

About Screen Enable/Disable

Dialog Structure: Check-out/In

For each function, select thedesired option(disabled/enabled) from thedrop-down list.


CO Material Enable/Disable

CI Material Enable/Disable

CO Payment Enable/Disable

CI Payment Enable/Disable

Expense Enable/Disable

Final Odometer 0 – No capturing



(C) SAP AG 216





1 – First step

2 – Second step

Determines when the odometer recording appears in thescreen flow.

1 – First step

The odometer recording is before the differencedetermination of the check-in.

2 – Second step

The odometer recording is after the differencedetermination of the check-in.

Initial Odometer

0 – No capturing

1 – First step

2 – Second step

Determines when the odometer recording appears in thescreen flow.

1 – First step

The odometer recording is before the differencedetermination of the check-out.

2 – Second step

The odometer recording is after the differencedetermination of the check-out.

C-Out in Sales UOM Enable/Disable if Check-Out shows quantity in SalesUOM

Reason Mndt CI Diff. Enable/Disable if reason is mandatory for Check-Indifferences

Reason Mndt CO Diff. Enable/Disable if reason is mandatory for Check-Outdifferences

Reload CI Enable/Disable



(C) SAP AG 217





Reload CO Enable/Disable

Dialog Structure: Order andDelivery


Credit Check Offline Enable/Disable

Due Op. Itms Offline Enable/Disable

Credit Check Online Enable/Disable

Due Op. Itms Online Enable/Disable

Online Pricing Enable/Disable

Online ATP Enable/Disable

Pricing Date

0 – Delivery date

1 – Sales order date

2 – Shipment date

Change Payment Terms

Enable/Disable

Payment terms can be changed to those maintained incustomer master data in SAP Direct Store Delivery

during order/delivery processing.

Deal Condition Enable/Disable

Manual discounts Enable/Disable

Capture on Hand

Enable/Disable

This functionality enables you to capture inventory atPOS. The functionality can be used together with item

proposals to create, for example, a suggested order.



(C) SAP AG 218





The capture on hand data is uploaded at tour end and

stored in /EMSE/HH_COH_HD and /EMSE/HH_COH_ITM .

From there, it can be used according to customer needs.

Downld Item Proposal

Enable/Disable

Downloads an item proposal from /DSD/ME_CUST_SA.

Item proposals are created by the standard transaction

VA51/52/53 and assigned in customer master data.

Increase Qty p. Scan

Enable/Disable

Enable = Determines that each time a product isscanned, the quantity field is displayed and the quantityof the product is increased incrementally by 1 unit.

This functionality is available in material lists on the

mobile client.

Filter Itm Prop w/LE

Enable/Disable

Filters the item proposal based on listing/exclusionbefore sending it to SAP Mobile Platform.

Add Items for Return 0 – Sales unit

1 – Base unit

Dialog Structure: Order andDelivery -> Order


Sales Order Enable/Disable

Return Order Enable/Disable

Free Order Enable/Disable



(C) SAP AG 219





Order Summary&Detail

Enable/Disable

This activates related functionality on the orderconfirmation screen.

Order Preview

Enable/Disable

Enable – Order preview screen is accessible on the orderconfirmation screen.

Print Order Enable/Disable

Enable – Print button is active in order preview.

Rush Order

Enable/Disable

Rush order process requires OCS scenario.

Display Returns

Enable/Disable

Enable – Return item screen is shown every time.

Disable – you can reach the return screen by selectingthe menu item.

Reason Mandatory FG

Enable/Disable

Reason code mandatory for free good order/delivery.

Reason Mandatory RT

Enable/Disable

Reason code mandatory for return order/delivery.

Reason Mandatory NO

Enable/Disable

Reason code mandatory for normal order/delivery.



(C) SAP AG 220





Price Free Good Ord.

Enable/Disable

Enable – Order prices are shown on item level andprinted; over all amount remains zero.

Change Delivery Date Enable/Disable

Dialog Structure: Order andDelivery -> Delivery


Delivery Enable/Disable

Return Delivery Enable/Disable

Free Delivery Enable/Disable

Inc. PlnFPrdND

Enable/Disable

Increase Planned Finished Products Quantities in NormalDel.

Inc. PlnRetEmp Enable/Disable

Increase Planned Return Empties Quantities

Inc. PlnRetFPrd Enable/Disable

Increase Planned Return Finished Products Quantities

Inc. PlnFPrdFG

Enable/Disable

Increase Planned Finished Products in Free GoodsDelivery

Dec. PlnFPrdND

Enable/Disable

Decrease Planned Finished Products Quantities inNormal Del.

Dec. PlnRetEmp Enable/Disable

Decrease Planned Return Empties Quantities

Dec. PlnRetFPrd Enable/Disable



(C) SAP AG 221





Decrease Planned Return Finished Products Quantities

Dec. PlnFPrdFG

Enable/Disable

Decrease Planned Finished Product in Free GoodsDelivery

Del. Summary&Detail

Enable/Disable

This activates related functionality on the deliveryconfirmation screen.

Delivery Preview

Enable/Disable

Enable – Delivery preview screen is accessible on thedelivery confirmation screen.

Print Delivery Enable/Disable

Enable – Print button is active in delivery preview.

Display Returns

Enable/Disable

Enable – Return item screen is shown every time

Disable – you can reach the return screen by selectingthe menu item.

Add AFPrdND

Enable/Disable

Add Additional Finished Products to Existing PlannedNormal Del.

Add AFPrdRD

Enable/Disable

Add Additional Finished Products to Existing PlannedReturn Del.

Add AEmpREmp

Enable/Disable

Add Additional Empties to Existing Planned ReturnEmpties Del.

Add AFPrdFG

Enable/Disable

Add Additional Finished Prods to Existing Planned FreeGoods Del.



(C) SAP AG 222





Add AEmpND

Enable/Disable

Add Additional Empties to Existing Planned NormalDelivery

Reason Code Part Del

Enable/Disable

Reason Code Mandatory if Quantities Decreased inNormal Del.

Reason Mandatory FG

Enable/Disable

Reason code mandatory for free good delivery.

Reason Mandatory RT

Enable/Disable

Reason code mandatory for return delivery.

Reason Mandatory NO

Enable/Disable

Reason code mandatory for normal delivery.

Price Free Goods Del

Enable/Disable

Enable – Prices are shown on item level and printed;over all amount remains zero.

Ref Deals Pres. Del.

Enable/Disable

Enable – Deal conditions that are already applied duringsales order taking (preseller) will be checked/appliedagain if a delivery driver performs the delivery of goods.

Dialog Structure: Invoice


Invoice Reprint Enable/Disable



(C) SAP AG 223





Dialog Structure: Collection


Collection Enable/Disable

Coll. Item Def. Payt Enable/Disable

Allow Overpayments Enable/Disable

Allow Part. Payments Enable/Disable

Dialog Structure: Inventory


Inventory Adj. Enable/Disable

Stock to Stock Tran. Enable/Disable

Dialog Structure: Visit ListItems Row Information

For each function, select thedesired option (field 1 to field 8)from the drop-down list.

2nd Row List Field 1

Select desired field from input help.

In the visit list on the mobile client, you can define thecontent that is shown on the second line for a customerentry. The information will be shown inline starting from“2nd row list field 1”. All information can be shown byoverlay as well.

2nd Row List Field 2 Select desired field from the input help.





(C) SAP AG 224









Dialog Structure: Signer Roles

Settings

For each function, select thedesired option.

For a description of all settings, see Assign Signer Rolesto Documents [Page 110].

Dialog Structure: RiskCategories and Credit ControlArea settings

Field Name


TS Select your tour scenario from the input help.

Example: 01-Pre-Sales Scenario

S/VP Select a shipment/visit plan from the input help.

Example: 01-Pre-Sales Scenario

Risk cat. Select a risk category from the input help.

Example: 101

CCAr Select a credit control area from the input help.

Example: 0001

Msg Typ.

Select message type Warning or Error .

Error stops the delivery/order process on the mobileclient if credit data for a customer is insufficient.Furthermore, it has an impact on collection. If a customer

has due open items and the message is on warning, thedriver is forced to collect open items first.



(C) SAP AG 225





Dialog Structure: TourScenario of SAP DSD andCRM Activities

You need to create/select anentry first for your tour scenarioand, if required, for yourshipment/visit plan type


OS Select source system of the activity.

Example: 0 - DSD

Acitvity Type

Select an activity type (dependent on previously selectedsource system).

Example: 4 - Collection

Sequence Number

Enter a number to sequence the activity.

This setting lists activities on the mobile client in visitoverview, for example, collection first and takes ordersecond.

ActivityType Name Will be populated automatically.

7. Save your entries. Repeat the steps for additional tour scenarios.

Result

Once you have enabled a function in this Customizing table, its functions/screens areavailable on the mobile client.



(C) SAP AG 226

Definition of General Settings

This section describes where to find the Customizing tables for defining settings that allow

you to control the mobile app with regards to the various existing tour scenarios. Thesesettings are more process-oriented than device-oriented. They are valid at a general level forall mobile devices.

Process

The tables for general mobile settings are located in Customizing for Logistics Execution


Mobile Device Settings Define General Settings .

To set up general settings for mobile devices, you need to perform the following Customizingactivities:

1. Define Payment Methods [Page 227]

2. Define Expense Types [Page 229]

3. Define Allowed Payment/Credit Card Types [Page 230]

4. Assign Shipment/Visit Plan Types to DSD Tour Scenarios [Page 231]

5. Assign Delivery Document Types to DSD Delivery Scenarios [Page 232]

6. Assign Sales Document Types to DSD Order Scenarios [Page 234]

In addition, the Customizing activities listed below refer to general settings that are needed for

specific SAP Direct Store Delivery functions, which are Manual Discounts, Deal ConditionDiscounts, or Electronic Signature. The purpose and procedure of each activity is explained inthe corresponding functional section.

Assign Condition Types for Manual Discounts [Page 237]

Defining Condition Types for Deal Condition Discounts [Page 260]

Defining Settings for Canceling or Changing Signed Documents [Page 116]



(C) SAP AG 227

Define Payment Methods

In this IMG activity, you maintain the payment methods that are allowed for making payments

during the course of a tour and that are available for use on the mobile device.

In a non-mobile business scenario, the payment methods can be selected during therecording process in the Settlement Cockpit .

The following payment methods are supported and implemented in SAP Direct StoreDelivery :

CA

Cash

CH

Check

CC

Credit card

BT

Bank transfer

Beside these default payment methods, maintaining a custom-specific payment method issupported. This method is derived from an ABAP structure. The following fields of thestructure definition are taken into account:

TABNAME

Name of the structure

FILDNAME

Name of the structure field

POSITION

Position of the field on the screen

DATATYPE

Data type of the field

LENG

Maximum length of the field

SCRTEXT_M

Text of the input field label



(C) SAP AG 228

The structure is dynamically rendered on the front end and some basic validations areperformed based on the length and data type of the field. The following data types aresupported:

CHAR (default)

DATS

INT1

INT2

INT3

INT4

CUKY

Such custom-specific payment methods are treated like cash payments.

Procedure



Settings , choose Define Payment Methods.



FieldName


Paym.Meth.

Enter a two digit key for the payment method to be defined.

Example: CA

Description Enter a description for the new entry (long version).

Example: CASH

TableName

Enter an ABAP structure on which this payment method is based. This entry is just required for newly defined payment methods besides the delivered ones.

Example: ZPMTerm


Result

Only those payment methods you maintain in this table are available on the mobile deviceand can be used by the driver during payments/collections.



(C) SAP AG 229

Define Expense Types

In this IMG activity, you maintain the expense types that may occur during the course of a

tour and which should be available for use on the mobile device.

Procedure



Settings , choose Define Expense Types.




Expense Type Enter a one digit key for the expense type to be defined.

Example: G

Description Enter a description for the new entry (long version).

Example: GASOLINE

Short Description Enter a description for the new entry (short version).

Example: GAS


Result

Only those expense types you maintain in this table are available on the mobile device andcan be used by the driver when recording tour-related expenses.



(C) SAP AG 230

Define Allowed Payment/Credit Card Types

In this IMG activity, you maintain the credit card types that your business accepts for

payments on the mobile device.

The keys of the payment/credit card types you maintain in this Customizing table need to be

identical to those maintained in the TVCIN table. For more information, see Customizing for

Sales and Distribution under Billing Payment Cards Maintain Card Types .

Procedure



Settings , choose Define Allowed Payment / Credit Card Type.




Pay Card Enter an alphanumeric key for the credit card to be allowed for payment.

Example: VISA

Description

Enter a description for the new entry (long version).

Example: VISACARD

Short Description Enter a description for the new entry (short version).

Example: VISA


Result

Once you have made the settings, the system accepts only those credit cards for payments

that are maintained in this table on the mobile device.



(C) SAP AG 231

Assign Shipment/Visit Plan Types to DSD TourScenarios

In this IMG activity, you maintain allowed shipment types or visit plan types that can be usedon the mobile device for a given DSD tour scenario.

The following tour scenarios are available on the mobile device:

Presales

Van sales

Delivery driver

Mixed driver

The presales scenario does not have a shipment, instead it uses a visit list that wasgenerated from a visit plan type. For the mobile device, the visit plan type functions like ashipment type when it is mapped to the above scenario.

Procedure


Connectivity DSD Connector Settings Define General Settings , choose AssignShipment / Visit Plan Types to Tour Scenarios.




DSD TourScenario

Select the desired tour scenario from the input help.

02 VAN SALES SCENARIO

Shipm/Visit PlanType

Enter the relevant shipment type, as maintained in the DSD back end,that represents the selected DSD tour scenario.

Example: Y002


Result

From the settings you have made in this table, the system can determine which type of DSDtour scenario is on the mobile device.



(C) SAP AG 232

Assign Delivery Document Types to DSD DeliveryScenarios

In this IMG activity, you maintain which delivery document types are allowed and can be usedon the mobile device for each DSD delivery scenario. Only those delivery document typesmaintained in this Customizing table are relevant for download.

The following delivery scenarios are available on the mobile device:

Presold delivery

Delivery types maintained for this scenario are downloaded to the Presold DeliveryScenario activity on the mobile device.

Delivery without presold

Delivery types maintained for this scenario are downloaded to the Delivery withoutPresold Scenario activity on the mobile device.

Return delivery

Delivery types maintained for this scenario are downloaded to the Return Delivery

activity on the mobile device. The special functionality of this activity type is that allitems are indicated as returns.

Free goods

Delivery types maintained for this scenario are downloaded to the Free GoodsDelivery activity on the mobile device. The special functionality of this activity type is

that it does not have pricing or invoicing on the mobile device since the Free GoodsDelivery is not billing-relevant. Even though you can set a parameter in Customizingfor the tour scenario (see Define Tour Scenario Settings [Page 213]) to show priceditems, the amount of the invoice is still zero. Additionally, Free Goods Delivery automatically has a reason code assigned to it according to Customizing settings inthe /DSD/ME_CHG_RSN table (see Define Reasons for Changing Deliveries andOrders on DSD Connector [Page 194]).

Procedure



Settings , choose Assign Delivery Document Types to Delivery Scenarios.




DSDDeliveryScenario

Select the desired delivery scenario from the input help.

Example: 01 PRESOLD DELIVERY SCENARIO

Delivery

Type

Specify a relevant delivery document type as maintained in the DSD back

end that is allowed on the mobile device in the DSD delivery scenarioselected.



(C) SAP AG 233


Example: ZLF

SaTy

Specify a relevant sales document type as maintained in the DSD back end

that is allowed on the mobile device for the DSD delivery scenario selected.

Example: ZTA

DeliveryNo.Ty

Defines the delivery number type that controls the rules of document numbergeneration for delivery.

Invoice No.Ty

Defines the invoice number type that controls the rules of document numbergeneration for invoices.

Def

Select checkbox.

Multiple document types can be maintained in the back end Customizing foreach of the order/delivery scenarios. To ensure that listing/exclusion isworking properly, you need to default one document type per scenario.


Result

From the settings you have made in this table, the system can determine which deliveryscenario is on the mobile device.



(C) SAP AG 234

Assign Sales Document Types to DSD OrderScenarios

In this IMG activity, you maintain allowed sales document types on the mobile device for eachDSD order scenario.

The following order scenarios are available on the mobile device:

Take order

Sales document types maintained for this scenario are downloaded to the Take Order activity on the mobile device.

Return order

Sales document types maintained for this scenario are downloaded to the ReturnOrder activity on the mobile device. All items of this activity type are flagged asreturns.

Free goods order

Sales document types maintained for this scenario are downloaded to the FreeGoods Order activity on the mobile device.

Procedure



Settings , choose Assign Sales Document Types to Order Scenarios.




DSD OrderScenario

Select the desired order scenario from the input help.

Example: 01 TAKE ORDER SCENARIO

Sales

DocumentType

Specify a relevant sales document type as maintained in the DSD back end

that is allowed on the mobile device for the DSD delivery scenario selected.

Example: ZTA

Order No.Type

Defines the order number type.

It is used to associate various orders for document number generation.

Example: O

Default

Select checkbox.

Multiple document types can be maintained in the back-end Customizing for



(C) SAP AG 235


each of the order/delivery scenarios. To ensure that listing/exclusion isworking properly you need to default one document type per scenario.


Result

From the settings you have made in this table, the system can determine which orderscenario it is dealing with on the mobile device, which unique number will be created, andwhich documents are considered for listing/exclusion.



(C) SAP AG 236

Manual Discounts

In the DSD process, drivers sometimes need to grant a customer an additional manual

discount on their mobile device. Manual discounts can be given on header level as well as onitem level of orders and deliveries and they are treated as pricing conditions. Once the datahas been uploaded to the DSD back end system, the Final Settlement Run program uses themanual discount during invoice generation.

Process

To have the manual discount pushbutton available on mobile devices, you must activate theManual Discounts functionality in Customizing for the Tour Scenario [Page 213].

For more information, see Mobile Device Settings [Page 205].



(C) SAP AG 237

Assign Condition Types for Manual Discounts

In this IMG activity, condition types are assigned to be used as manual discounts at header

and/or item level. It is necessary to differentiate between percentage and value discounts. Ifthe driver applies a manual discount on a mobile device, this discount is transferred to theRoute Accounting Database (RAD) during upload. The Final Settlement Run program thenapplies it as a discount in the related documents, such as orders and invoices.

Prerequisites

The condition types used for manual discounts must be defined in Customizing forstandard Sales and Distribution (SD).

The condition types must be maintained with a minus sign so that the conditionamount is displayed as minus (for example, – 1000 USD).

The calculation type of the condition types must be maintained as A (percentage) orB (fixed amount).

The setting for manual entries of the condition types must be different than D (notpossible to process manually).

The condition types must be maintained as manual condition types in your pricingprocedures.

Procedure



Settings , choose Define Condition Types for Manual Discounts.



FieldName


SOrg. Choose a sales organization from the input help.

Example: 1000

DChl Choose a distribution channel from the input help.

Example: 01

Dv Choose a division from the input help.

Example: 01

CTyp Enter a condition type that should be used as a manual discount.

Example: HA00

Percentage Select the checkbox if you want the condition type in the previous field to beapplied as a percentage discount.



(C) SAP AG 238

FieldName


Apply on

Choose from the drop-down list whether the discount should be applied atheader level or item level or both.

Example: 1-Header Condition

Description Enter a description for the condition type maintained.

Example: Discount(percentage)-Header

4. Repeat steps 2. and 3. depending on how many sales areas and condition types persales area are required. You can assign a maximum of four condition types per salesarea.


The settings for the manual discounts must correspond to the settings made for the conditiontype in Customizing for standard SD Pricing. If you have maintained the condition type as avalue discount in Customizing for standard Sales and Distribution, you cannot select thepercentage checkbox in the DSD Customizing table for manual discounts.

Result

On mobile devices, drivers can choose from the list of manual discounts (as maintained) thatcan be granted to customers.



(C) SAP AG 239

Barcode Support for Recording Visit Times onMobile Device

The time spent at the customer site for delivery execution is an important figure that can beused to evaluate historic tour information and improve future transport scheduling. To be ableto derive this figure, the mobile user must capture the visit start time and date (arrival at thecustomer site) and the visit end time and date (departure from the customer site). This activityneeds to be customized so that it is simple and automated for the mobile user.

With SAP Direct Store Delivery , you have the following options for facilitating visit time

recording on the mobile device:

Barcode scanning

Automatic system time entry

Manual time entry

All three options are controlled by Customizing settings made on the DSD Connector that arethen transferred to the mobile device.

Visit times are recorded by scanning the customer barcode identifier. This barcode identifier ismaintained in the customer master data and is downloaded to the mobile device with the restof the master data. Preferably, the Global Location Number (GLN) should be used as thebarcode identifier. However, since GLN number ranges need to be purchased from GS1 (theissuing and controlling organization), other unique numbers (such as the SAP customernumber) may be used for this purpose as well. The mapping rules in the DSD Connector for

Connectivity Object 6 (Customer Master) are enhanced with three GLN fields (BBBNR, BBSNR,

and BUBKZ) to supply the /DSD/ME_CUST_HD DSD Connector table with the required data.The concatenation of the three new fields is equal to the GLN. These new mapping recordsare delivered as switchable BC Sets.

The default barcode identifier is the GLN but customers can define their own barcode

identifier using the existing /DSD/BADI_HH_CUST_BARCODE BAdI in the DSD Connector.

The customer-specific barcodes may be printed out in the back end in barcode format. If the

BAdI is implemented, it is called in the /DSD/HH_PRINT_BARCODE printing report.

If the /DSD/BADI_HH_CUST_BARCODE BAdI method is implemented, then this

implementation must be aligned with the corresponding implementation of the

KUNNR_ADDITIONAL_HANDLING_POST method (/DSD/ME_CUSTOMER_HEADER ,

BARCODE_IDENTIFIER field) of the /DSD/ME_BADI BAdI.

It is possible to differentiate between visit times that were recorded on the mobile device andthen uploaded to the back end and visit times that were recorded after the upload in theSettlement Cockpit . This requires maintaining a special time type in Customizing for DSDRoute Accounting to enable the identification of new visit time entries made in the back end.

This special time type must be derived in the TIMETYP_ADDITIONAL HANDLING method of

the /DSD/ME_BAPI BAdI. An example implementation is delivered to explain the possible

transformation in detail.

Prerequisites

Business Function /DSD/BF must be activated.



(C) SAP AG 240

Process

Customizing for Visit Time Capture involves the following activity in the DSD Connector:

1. Enable Barcode Support in Tour Scenarios [Page 241]



(C) SAP AG 241

Enable Barcode Support in Tour Scenarios

If you want to use the Barcode Support on Mobile Device function, you must enable the

barcode option in each relevant scenario under the dialog structure “General”.

The following values are possible:

0 – No time capturing

1 – Manual for start and end time

The mobile user can change the recorded time as often as required by clicking on thetime stamp link button.

2 – Automatic for start and end time

The mobile user cannot make changes.

3 – Barcode scans for start and end time

If there is a failure of the scanner, the mobile user can set the start/end times oncemanually by clicking on the link button. This is recorded in the client database in theBarcode_Error field with an “X” and is uploaded as well.

Barcode Mode

If the scenario is barcode mode is on and you have just one visit for your customer in the visitlist, the start time is recorded automatically and the screen switches to the visit overviewdirectly.

If you have more than one visit to a single customer, for example, in a multiple sales areaprocess, then an overlay opens and the appropriate visit is requested.

If you access the visit overview manually and barcode mode is on, then the link button showsScan failed to indicate that you have to scan the start time.

Automat ic Mode

If you change from the visit list to the visit overview, the link button shows the initial or apreviously persisted start time. The client persists the time automatically if you start anactivity, for example, a collection, and the activity status is different to “NP” (Not Processed). Ifthe activity remains in “NP” status, for example, step-in and immediately step-out fromcollection, no visit start time is persisted.

Manual Mod e

If you change from the visit list to the visit overview, the link button shows the initial or apreviously persisted start time. If it is initial, you can click on it, the time is saved, and it can nolonger be changed. If you want to change to an activity and no time has been recorded so far,the mobile client opens an info message to capture the time and denies a change to theselected activity.

Prerequisites

The Business Function /DSD/BF must be switched on to make the barcode support

option available within the Define Tour Scenario Settings view.

Tour scenarios must have been maintained.



(C) SAP AG 242

Procedure


Connectivity DSD Connector Settings Mobile Device Settings , choose DefineTour Scenario Settings.

2. Highlight the tour scenario for which you want to enable barcode support and chooseChange.



Visit Time Capture

Set the desired value:

o 0 – No Time Capturing

o 1 – Manual

o 2 –

Automatic

o 3 – Barcode


Result

The visit time capturing relevant settings in the Tour Scenario Settings determine exactly howthe mobile client can support visit time capturing.



(C) SAP AG 243

Invoice Reprint as Copy

During delivery execution at the customer site, the delivery driver may print an invoice from

the mobile device to give to the customer. The information that the invoice has been printedand the time at which it was printed is uploaded to the DSD back end.

During the Final Settlement Run, billing documents are generated for the customer in theback end system taking into account the delivery data and invoice data that has been sentfrom the mobile device. If output determination has been customized for this respective billingtype, message controls can be found during the invoice generation. The invoice printed fromthe mobile device is the original and any further printouts of the same invoice must contain areprint label, which clearly indicates that the printout is a copy of the original invoice.

Prerequisites

Business Function /DSD/BF must be activated.

Process

1. Make settings for the Invoice Reprint as Copy function in Customizing for Logistics

Execution under SAP Direct Store Delivery Handheld Connectivity DSD

Connector Settings Mobile Device Settings Define Tour Scenario Settings .

2. For more information about how to proceed with this IMG activity, see Define TourScenario Settings [Page 213].



(C) SAP AG 244

Listing and Exclusion

Material Listing and Material Exclusion are standard back end functions in Sales and

Distribution (SD) that allow users to control which materials are permitted (listed) or prohibited(excluded) to be sold to a specific customer or to a group of customers.

The limitation for this function in existing solutions has been solved in SAP Direct StoreDelivery , where you can now use almost the same fields for listing and exclusion as in theback end. A list with featured fields is listed in this chapter. For this purpose, listing andexclusion data is extracted from the back end and transferred to the DSD Connector to beforwarded to the respective mobile device. The DSD Connector triggers the extraction of thelisting/exclusion data as soon as a mobile user is assigned to a downloaded tour and beforethe pricing data is extracted. A result of this extraction is a customer/material relation that is

stored in the /EMSE/ME_CNDLE DSD Connector table. On the mobile client, the listing and

exclusion function enables the driver to perform the following additional functions:

The driver can display a list of materials that are allowed (inclusion list) or not allowed(exclusion list) for a customer. This information can be accessed via customer masterdata screens.

The driver can search for materials during the creation/modification of a new/existingorder/delivery, based on customer listings. If the driver wants to add an item by usingthe Add Item button on the Delivery screen, the mobile app behaves as follows:

o If an inclusion list exists for the customer

The Add item Screen only displays materials that are allowed for thecustomer.

o If only an exclusion list exists and no inclusion list is maintained

The Add item Screen displays all materials except the excluded ones.

o If neither an inclusion nor an exclusion list exists

All materials are displayed and can be added to the document.

The driver can validate materials during order or delivery entry without searching forthe material.

The driver wants to add an item by using the Add Item button on the Delivery screen.The mobile app compares the entered material number with the list of excludedmaterials and if it finds a match, the mobile app returns an appropriate error messageindicating that it was unable to add the material to the delivery/order. If no match isfound, the material is added to the document.

While determining whether a material is contained in an inclusion or an exclusion list, themobile app also considers the order type/delivery type to which the material should be added.The document type for the order/delivery is determined based on the activity type for theorder/delivery. In back end Customizing, document types are maintained for the variousorder/delivery scenarios of which each scenario corresponds to an activity type on the mobiledevice. This relationship is used to determine the document type for each activity. Currently,multiple document types can be maintained for each of the order/delivery scenarios in back

end Customizing. For this purpose, you need to set one order/delivery type as default. For



(C) SAP AG 245

more information, see Assign Delivery Document Types to DSD Delivery Scenarios [Page140] and Assign Sales Document Types to DSD Order Scenarios [Page 142].

The Listing and Exclusion function also applies during the Final Settlement Run in the backend by checking whether a material is listed or excluded for the customer. If the material isnot allowed for the customer, then the material is removed from the order item list and an

appropriate message is created in the application log.

The DSD-related Material Listing and Exclusion function is limited in that SAP does notsupport all the fields from the catalog for table creation in the back end. The following are thefields that are supported:

Field Description

ALAND Country

BUKRS Company Code

CITYC City code

COUNC County code

EAN11 EAN/UPC

KDGRP Customer group

KNRZE Payer

KONDM Material pricing grp

KUNAG Sold-to party

KUNNR Customer

KUNWE Ship-to party

MATKL Material Group

MATNR Material

MTART Material Type

PLTYP Price list type

PMATN Pricing Ref. Matl

PRODH Product hierarchy

WERKS Plant

REGIO Region

SPART Division



(C) SAP AG 246

Field Description

VKORG Sales Organization

VTWEG Distribution Channel

KONDA Price Group

Prerequisites

Business Function for DSD, for example, /EMSE/Activate_Fields , must be activated.

Process

In SAP Direct Store Delivery , the Listing and Exclusion function only requires Customizingactivities in the back end. Once this has been assigned to the appropriate order type, theextraction happens during a normal tour download.

The back end Customizing tables for material listing/exclusion are part of SD standardCustomizing for Sales and Distribution under Basic Functions Listing/Exclusion . It uses

the condition technique and involves the following activities:

1. Maintain Condition Tables for Material Listing/Exclusion [Page 247]

2. Maintain Access Sequences for Material Listing/Exclusion [Page 248]

3. Maintain Condition Types for Material Listing/Exclusion [Page 250]

4. Maintain Procedures for Material Listing/Exclusion [Page 251]

5. Assign Procedures for Material Listing/Exclusion to Sales Document Types [Page

253]



(C) SAP AG 247

Maintain Condition Tables for MaterialListing/Exclusion

In this IMG activity, you define the condition tables for material listing and material exclusionby defining the appropriate field combination required in a condition record. Not all fields fromthe catalog are supported by SAP Direct Store Delivery .

Procedure

1. To create a new condition table for material listing/exclusion, in Customizing for Sales

and Distribution, choose Basic Functions Listing/Exclusion . From the optionsprovided, choose Maintain Condition Tables for Listing/Exclusion.

2. To change to create mode, go to the Condition menu and choose Create.



Table Enter an ID for the new condition table.

Example: 501

Copy from Condition

Table Leave blank.

4. Choose Enter . Enter a description for the new condition table (for example,Cust/Mat.Group).

From the list of allowed fields, select the supported fields to build your requiredcondition table.

5. Generate the new condition table.

Result

You have defined a condition table with key fields for which you can maintain conditionrecords.



(C) SAP AG 248

Maintain Access Sequences for MaterialListing/Exclusion

In this IMG activity, you define access sequences for material listing and material exclusion.

The access sequence is a search strategy with which the system searches for valid conditionrecords for each condition type. The access sequence refers to the fields for material listing ormaterial exclusion with the condition tables contained in the access sequence.

Procedure

1. In Customizing for Sales and Distribution, choose Basic Functions

Listing/Exclusion and from the options provided, choose Maintain AccessSequences for Listing/Exclusion.



FieldName


AS

Enter an ID (up to 4 digits) for the new access sequence; we recommend using

the prefix A for listing and B for exclusion.

Example: A501

Description

Enter a description for the new access sequence, as appropriate.

Example: AS-DSD Listing

4. Choose Enter . Highlight your entry, choose Accesses in the left window, and chooseNew Entries.



No. Enter a sequential number for the access within the access sequence.

Example: 10

Tab Select the condition table from the input help.

Example: 501

Description This is automatically entered depending on the entry made in the Tab field.

Requirement Leave blank .

6. Choose Enter . Highlight your entry and choose Fields in the left window.

7. On the screen that appears, maintain entries for each field as follows:




(C) SAP AG 249


Condition Name of the field of the condition record.

Example: VKORG

Docmt Structure

Specifies an internal table in which condition information aboutdocuments is stored.

Example: KOMKG for header structure field

Doc.field Determines the data dictionary characteristics for new fields in datadictionary structures.

Long field label This is automatically entered depending on the entry made in theDoc.field field.

Spec.Val.Sourc

e Leave blank .

Init Leave blank .


Result

You have defined access sequences for DSD material listing and exclusion that are nowready to be assigned to condition types.



(C) SAP AG 250

Maintain Condition Types for MaterialListing/Exclusion

In this IMG activity, you define condition types for material listing and material exclusion andassign an access sequence to each condition type. In addition, you can also maintain avalidity period per condition type. Condition types help you to control how material listing andexclusion is carried out.

Procedure


Listing/Exclusion and from the options provided, choose Maintain Listing/ExclusionTypes.



FieldName


CTyp

Enter an ID (up to 4 digits) for the condition type. We recommend using theprefix A for listing and B for exclusion.

Example: A501

Name Enter a description for the new access sequence, as appropriate.

Example: CT-DSD Listing

AS Assign an access sequence by selecting it from the input help.

Example: A501

Description This is automatically entered, depending on the entry in the AS field.

Valid From Optional – Leave blank or select an appropriate entry from the input help, ifdesired.

Valid To Optional – Leave blank or select an appropriate entry from the input help, if

desired.


Result

You have defined condition types for DSD material listing and exclusion that are now ready tobe assigned to material listing/exclusion procedures.



(C) SAP AG 251

Maintain Procedures for Material Listing/Exclusion

In this IMG activity, you define procedures for material listing and material exclusion and

assign the condition types that you want the system to consider when executing thelisting/exclusion function.

Procedure


Listing/Exclusion and from the options provided, choose Procedures formaintaining Listing/Exclusion.




Usage Value G (for Listing and Exclusion) is automatically set.

Application Value V (for Sales and Distribution) is automatically set.

Procedure Enter an ID (up to six digits) to identify the new procedure.

Example: A50001

Description Enter a description for the new procedure.

Example: PC-DSD Listing

4. Choose Enter . Highlight your entry and choose Control data in the left window.



Step Enter a number to determine the sequence of the step within the procedure.

Example: 10

Counter Leave blank .

CTyp Enter a condition type by selecting it from the input help.

Example: A501

Description That is automatically entered depending on the entry made in field CTyp.

Requirement Leave blank .




(C) SAP AG 252

Result

You have defined procedures for DSD material listing and exclusion that are ready to beassigned to sales document types.



(C) SAP AG 253

Assign Procedures for Material Listing/Exclusionto Sales Doc. Types

In this IMG activity, you assign the material listing/exclusion procedures to all the salesdocument types that are relevant for your DSD mobile business processes.

During the download process, the system retrieves the relevant order and delivery types (as

customized for DSD order scenarios and DSD delivery scenarios in the /DSD/ME_ORD_AUT

and /EMSE/DELV_LFT DSD Connector tables). The system then determines the listing and

exclusion data that needs to be extracted and transferred. For each delivery that has beencreated with reference to a sales order, material listing and exclusion is carried out on thebasis of the underlying sales document type. This means that material listing and/or exclusionis only carried out when the underlying sales document type has a procedure assigned in thistable for the relevant function. Material listing and exclusion is not carried out for deliveryitems that have been copied from the sales order.

In addition to your specific DSD-relevant sales document types, you must also assign anappropriate procedure to the “DL” sales document type to ensure that material listing and/orexclusion is carried out in deliveries that have been created without reference to a salesorder.

Prerequisites

The relevant sales document types must be defined.

Procedure1. In Customizing for Sales and Distribution, choose Basic Functions

Listing/Exclusion and from the options provided, choose Activate Listing/Exclusionby sales document type.

2. On the screen that appears, chose the desired sales document type.

3. In the Listing field, maintain a procedure that is defined for DSD material listing.

4. In the Exclusion field, maintain a procedure that is defined for DSD materialexclusion.

5. In the Pro (Procedure) field, select an appropriate entry from the input help.

Procedure “B” is not supported by SAP Direct Store Delivery on the mobile client.

6. Repeat the steps for each relevant sales document type.


Result

Based on the assignments made in this table, the system is able to determine whether

material listing and/or exclusion needs to be executed.



(C) SAP AG 254

Deal Conditions

As part of marketing strategies, consumer product industries offer discounts and free goods

for limited periods of time based on the quantity of other products that have been ordered andpurchased by customers. This means that a customer can purchase occasional volumes ofgoods at a reduced cost or they can receive new or additional items at no extra cost.

DSD deal conditions and discounts are only valid for the specific customer visit during the tourexecution and do not consider any previous purchases made by the same customer. Dealconditions are not taken into account during creation of the sales order and delivery in theSAP ERP back end.

In SAP Direct Store Delivery, there is the following additionally supported process:

1. In a preseller scenario, the sales representative grants some deal condition(s) in thecustomer order on the mobile device.

2. The order is uploaded and the agreed deal condition is saved in the order and routedthrough to delivery document for next delivery day.

3. The delivery driver delivers the goods and deal conditions are already applied.

DSD deal conditions are not linked to the standard Sales and Distribution promotions in theSAP ERP back end.

Prerequisites

You must activate deal condition functionality in Customizing for the Tour Scenario[Page 213] to have the deal condition available on mobile devices.

For more information, see Mobile Device Settings [Page 205].

You must create two reason codes to be used for the deal condition of free goods. Assign the change reason behavior A (Tied Empty Charged) to one reason code andthe behavior B (Deal Condition Free of Charge) to the other reason code.

For more information, see Define Reasons for Changing Deliveries and Orders onDSD Connector [Page 194].

Process

The DSD Deal Condition functionality requires back end as well as DSD ConnectorCustomizing.

Back End Customizing

The back end tables for this function are located in Customizing for Logistics Execution under

SAP Direct Store Delivery Deal Condition and comprise the following activities:

1. Define Deal Condition Types [Page 256]

2. Define Number Ranges for Deal Conditions [Page 257]

3. Define Field Selection for Deal Conditions [Page 258]

4. Define Customer Hierarchy Types for each Sales Area [Page 259]



(C) SAP AG 255

DSD Connector Customizing

The DSD Connector table for this function is located in Customizing for Logistics Execution


Mobile Device Settings Define General Settings and comprises the following activities:

1. Define Condition Types for Deal Condition Discounts. [Page 260]

2. Activate deal condition in the activity Define Tour Scenario Settings. [Page 213]



(C) SAP AG 256

Define Deal Condition Types

In this IMG activity, you define different types of DSD deal conditions that allow you to

differentiate between deal conditions for specific scenarios or between deal conditions forspecific material and customer types.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Deal

Condition , choose Define Deal Condition Types.




DCond.Type Define a deal condition type.

Example: Z001

Description Enter a description for the deal condition type.

Example: Standard Deal Condition


Result

You have defined DSD deal condition types.



(C) SAP AG 257

Define Number Ranges for Deal Conditions

You must assign a number range for DSD deal condition.

Procedure

1. In the SAP Easy Access menu, enter the SNRO transaction code.

2. Enter the /DSD/PR_NR object and choose Ranges.

3. Choose Change Intervals.

4. Select Insert Intervals define the number range for interval “01”.


Result

You have defined a number range for DSD deal condition.



(C) SAP AG 258

Define Field Selection for Deal Conditions

In this IMG activity, you define per deal condition type the fields that should be displayed and

available for maintaining the different DSD deal conditions on the DSD deal conditionmaintenance screens in the back end (for example, in the/DSD/PR_PRO_CH transaction).

Prerequisites

Deal condition types must be defined.

Procedure


Condition , choose Define Field Selection.




Deal cond.Type Choose a deal condition type from the input help.

Example: Z001

MDSD Promotions

Material De-/Activate, as required.

Material group De-/Activate, as required.

Mat.pricing grp De-/Activate, as required.

Sales org. De-/Activate, as required.

Distr.channel De-/Activate, as required.

Division De-/Activate, as required.

Deliver.Plant De-/Activate, as required.

Customer De-/Activate, as required.

Customer Group De-/Activate, as required.

HgLvCust. De-/Activate, as required.


Result

Only the activated fields are displayed in the DSD deal condition maintenance transactions

Create Deal Condition (/DSD/PR_PRO_CR), Change Deal Condition (/DSD/PR_PRO_CH),

and Display Deal Condition (/DSD/PR_PRO_DP).



(C) SAP AG 259

Define Customer Hierarchy Types for each SalesArea

In this IMG activity, you need to maintain a customer hierarchy type for each sales area that isto be used for the DSD deal condition.

Prerequisites

At least one sales area must be defined.

At least one customer hierarchy must be defined.

Procedure


Condition , choose Define Customer Hierarchy Type for each sales area.




Sales Org. Choose a sales organization from the input help.

Example: 0001

Distr.channel

Choose a distribution channel from the input help.

Example: 01

Division Choose a division from the input help.

Example: 01

MDSD Promotions – General

Hierarchy type Choose a hierarchy type from the input help.

Example: A


Result

You have maintained customer hierarchy types for each sales area.



(C) SAP AG 260

Define Condition Types for Deal ConditionDiscounts

The condition types that you want to use as DSD deal condition discounts are assigned atheader and item level. You need to differentiate between percentage and value discounts. If aDSD deal condition is granted on a mobile device, the discounts are transferred to the Route Accounting Database (RAD) during upload. During the Final Settlement Run, the discounts

are transferred to the related documents, such as orders or invoices.

Prerequisites

The condition types used for DSD deal conditions must be defined in Customizing forstandard Sales and Distribution.

The condition types must be maintained with a minus sign, so that the condition

amount is displayed as minus (for example, -1000 USD).

The calculation type of the condition types must be maintained as A (percentage) orB (fixed amount).

The setting for manual entries of the condition types must be different than D (notpossible to process manually).

The condition types must be maintained as manual condition types in your pricingprocedure.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery HandheldConnectivity DSD Connector Settings Mobile Device Settings Define General

Settings , choose Define Condition Types for Deal Condition Discounts .




Sales Org. Choose a sales organization from the input help.

Example: 1000

Distr.channel Choose a distribution channel from the input help.

Example: 01

Division Choose a division from the input help.

Example: 01

MDSD Promotions – Conditions

Cond.Type Head Perc Enter a condition type to grant a percentage discount onheader level.



(C) SAP AG 261


Example: RA01

Cond.Type Item Perc

Enter a condition type to grant a percentage discount on item

level.

Example: K007

Cond.Type Head Amnt

Enter a condition type to grant a value discount on headerlevel.

Example: HM00

Cond.Type Item Amnt

Enter a condition type to grant a value discount on headerlevel.

Example: KP00


Result

You have defined the condition types to be used for DSD deal conditions.



(C) SAP AG 262

Master Data Configuration

The DSD scenario involves the following groups of master data:

Customer master

Driver master

Vehicle master/ fleet objects

Tour master

Material master

The SAP Direst Store Delivery components influenced by these master data groupings are:

Visit Control

Transportation Planning

Vehicle Space Optimization

Route Accounting

Process


1. Driver Master Data Configuration [Page 263]

2. Vehicle Master Data/Fleet Objects Configuration [Page 274]

3. Material Master Data Configuration [Page 285]



(C) SAP AG 263

Driver Master Data Configuration

Companies in the consumer products industry often run their own fleet of vehicles that are

driven by their own employees. You maintain drivers and vehicles as master data in thesystem. Various SAP Direct Store Delivery components (for example, Visit Control ,Transportation Planning , Vehicle Space Optimization, and Route Accounting ) use this masterdata throughout the DSD scenario.

Process

This section contains the Customizing settings that are relevant to driver master data:

1. Create Number Ranges for Customer Accounts [Page 265]

2. Define Account Groups and Field Selection for Customers [Page 266]

3. Define Driver's License Categories [Page 264]

4. Assign Number Ranges to Customer Account Groups [Page 270]

5. Specify Allowed Account Group for Drivers [Page 271]

6. Set Up Partner Determination for Customer Master [Page 272]



(C) SAP AG 264

Define Driver's License Categories

In this IMG activity, you define customer-specific driver’s license categories. Customer -

specific driver’s license categories can be, for example, licenses for special vehicles,transporters of dangerous goods, fork-lift trucks, or passenger transporters.

Driver’s license categories are assigned to driver master data (Driver tab) and vehicle masterdata (DSD Vehicle Data tab) in the respective master data applications.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Master

Data , choose Define Driver's License Categories.




DLC Enter an alphanumeric key with up to 2 characters for the license category.



Result

The driver’s license categories can now be assigned to drivers within the driver master data.



(C) SAP AG 265

Create Number Ranges for Customer Accounts

The system maintains drivers just like normal customers. To distinguish drivers from normal

customers, you maintain and use specific Customizing settings. In this IMG activity, youdefine specific number ranges for customer accounts (drivers).

You define the type of number assignment and the number range intervals for customeraccounts that you use for drivers.

Procedure

1. In Customizing for Financial Accounting (New) under Accounts Receivable and

Accounts Payable Customer Accounts Master Data Preparations for Creating

Customer Master Data , choose Create Number Ranges for Customer Accounts.

2. Choose Intervals (with the Pencil).

3. Choose Insert Row .

4. Maintain a number range interval by indicating the limits of the number range interval.The limits of the number range intervals are not allowed to overlap. Each number isallowed to exist just once.


No Enter a two digit value.

Example: DR.

Fromnumber

Enter the first number of the number range interval.

Example: 300000

To number Enter the last number of the number range interval.

Example: 300999

Ext (External)

If you choose internal number assignment (recommended), do not select thecheckbox.


Result

You have defined the number ranges for your drivers.



(C) SAP AG 266

Define Account Groups and Field Selection forCustomers

In this IMG activity, you define account groups to which you assign customer master recordswith the same features (for example, a group of ship-to-parties, groups of one-timecustomers).

Prerequisites

Number ranges for account groups are defined.

Partner determination procedures are defined.

Procedure

1. In Customizing for Logistics General under Business Partner Customers Control , choose Define Account Groups and Field Selection for Customers.




Account Group

Enter a code for your account group.

Example: DSD1


Example: DSD Driver

General Data

Number Range Enter the number of the number range intervaldefined in the menu item Create NumberRanges for Customer Accounts [Page 265].

One-time acct. Do not select this checkbox as, in general,drivers are not one-time accounts.

Field Status

With the field status you determine thefollowing:

o Mandatory fields wheredata needs to be entered duringthe creation of the customermaster record of an accountgroup (Req. Entry );

o Optional fields where youmay or may not enter data (Opt.

Entry )



(C) SAP AG 267


o Fields that should not bedisplayed by the SAP system(Suppress).

General data

Double-click General Data and then double-clickeach sub-field to set the following data:

o Address: Req. Entry (Lastname, Search term A, Postal Code,Transportation Zone); Opt. Entry (allremaining fields).

o Communication: Opt. Entry (allfields).

o Control: Suppress (Referenceaccount group, Business place, Taxtype, CFOP category, Tax number 3,tax number 4, Brazilian taxes, taxcategories); Opt. Entry (all remainingfields).

o Marketing: Suppress (Hierarchy Assignment); Opt. Entry (all remainingfields).

o Payment transactions: Suppress (DME Details); Opt. Entry (allremaining fields).

o Unloading Points: Opt. Entry (allfields).

o Contact Person: Opt. Entry (all

fields)

o Foreign Trade: Opt. Entry (all

fields)

Company Code Data

Double-click Company Code Data and thendouble-click each sub-field to set the followingdata:

o Account Management: Suppress (Preference Indicator,Release Group, Gross Income Tax);Req. Entry (Reconciliation Account);Opt. Entry (all remaining fields).

o Payment Transactions: Suppress (Credit memo terms ofpayment, Diff. payer in document); Opt.Entry (all remaining fields).

o Correspondence: Opt. Entry (allfields).

o Insurance: Opt. Entry (all fields).



(C) SAP AG 268


o Withholding tax data: Opt. Entry(all fields).

Sales data

Double-click Sales Data and then double-clickeach sub-field to set the following data:

o Sales: Suppress (DocumentIndex active); Req. Entry (PricingProcedure, Currency); Opt. Entry (allremaining fields).

o Shipping: Suppress (Railspecifications); Req. Entry (ShippingConditions/POD relevance); Display(Transportation Zone); Opt. Entry (allremaining fields).

o Billing: Req. Entry (Taxes andLicenses); Opt. Entry (all remainingfields).

o Partner Usage: Opt. Entry (allfields).

o Documents: Opt. Entry (allfields).

Text Procd.

CentrTextDetPrc No entry.

TextDetProc SD No entry.

Sales and Distribution Data

You do not have to make entries for textdetermination, partner determination, orother sales data at this point. Youmaintain these fields later when you setthe defaults for the individual functions.

Cust.Pric.Proc. No entry.

Partn.Det.Proc. Choose AG (= Sold-to-Party) from the inputhelp.

OutputDet.Proc. No entry.

Competitors Do not select this checkbox.

Sales Partner Do not select this checkbox.

Prospect Do not select this checkbox.

Default SP Do not select this checkbox.



(C) SAP AG 269


Consumer Do not select this checkbox.


Result

You have set up the account group and its fields for master data creation.



(C) SAP AG 270

Assign Number Ranges to Customer AccountGroups

In this IMG activity, you assign number ranges, which you created for customer accounts (seeCreate Number Ranges for Customer Accounts [Page 265]), to account groups forcustomers. You can use one number range for several account groups.

Prerequisites

Number ranges are defined.

Account groups for customer accounts are defined.

Procedure

1. In Customizing for Financial Accounting under Accounts Receivable and AccountsPayable Customer Accounts Master Data Preparation for Creating Customer

Master Data , choose Assign Number Ranges to Customer Account Groups.

2. Select the entry for the Customer Account Group that was created in the previousstep.

3. In the Number Range field, assign the number of the number range interval created

for customer accounts that are considered to be drivers (for example, DR).

4. Save your entry.



(C) SAP AG 271

Specify Allowed Account Group for Drivers

In this IMG activity, you determine which account groups are valid for a driver.

The account group determines:

To which number range the account number of the driver corresponds

Whether the number is assigned by the user or by the system

Which data entries are necessary or possible

The driver-specific fields in the customer master are only displayed if the selected accountgroup is assigned in this Customizing table for account groups.

Procedure


Data , choose Specify Allowed Account Group for Drivers.




AccountGroup

Choose the account group from the input help that is to be used and allowedfor driver master records.

Name Description is added automatically when you choose Enter .


Result

If you choose a customer number for which the account group is defined as a permittedaccount group for drivers, the system recognizes that this customer master record containsdriver master data.

To display the extra Driver page, choose Additional Data, DSD in the driver master datarecord. You can enter the following information:

The transportation planning points for which the driver is permitted

The driver’s available driver’s license categories

The lock times during which the driver cannot carry out a shipment



(C) SAP AG 272

Set Up Partner Determination for Customer Master

Since drivers are maintained like customers, standard partner determination needs to be set

up and applied to drivers.

In this IMG activity, you define the rules that should be used to perform automatic partnerdetermination. When creating a customer master record, the SAP system proposes theallowed partner functions for maintenance. The partners are copied from the sold-to party’scustomer master records into the sales documents, according to the rules you have defined.

For partner determination, you must edit the following points:

Partner function

Partner functions can be used to define which roles exist in the system for partners.For drivers you maintain the four partner functions SP (Sold-to-party), SH (Ship-to-

Party), BP (Bill-to-Party), and PY (Payer).

Allowed partners for each account group

For each account group you assign the allowed partner functions. In the case ofdrivers, you assign the three partner functions to the account group to be used fordrivers (which was created in previous steps).

Function key conversion

It is possible to define language-dependent keys for the partner functions.

Partner object

Partner objects exist in both the customer master records and the sales documents(orders, deliveries, shipment, billing documents, and contacts). You define partnerdetermination separately for each of these objects.

Partner determination procedures

For each partner object, partner determination procedures are defined. Theseprocedures contain the allowed partner functions.

Assignment of procedures

A key is used to assign each partner determination procedure to a fixed partnerobject.

Procedure

1. In Customizing for Sales and Distribution under Basics Functions Partner

Determination , choose Setup Partner Determination.

2. Choose Setup Partner Determination for Customer Master from the list.

In the following screen, select the Partner Determination Procedures entry in the leftwindow and highlight the entry AG = Sold-to-Party in the right window. Choose Account Groups-Function Assignment in the left window.





(C) SAP AG 273


Partn.Funct .

Choose a partner function (for example, SP ) from the input help.

For drivers, the following four partner functions are relevant: SP (Sold-to-

Party), SH (Ship-to-Party), BP (Bill-to-Party) and PY (Payer).

AccountGrp

Choose the account group (for example, DSD1) from the input help. It shouldbe the account group that is to be used for drivers.

5. Choose Enter to save your entries.

6. Maintain step 3. through step 5. for each of the four partner functions (Sold-to-Party,Ship-to-Party, Bill-to-Party and Payer).

7. Repeat step 2. through step 5. for each of the four partner determination procedures(Sold-to-Party, Ship-to-Party, Bill-to-Party and Payer).

ResultYou have set up partner determination for your driver account group.



(C) SAP AG 274

Vehicle Master Data/Fleet Objects Configuration

Vehicle master data is a master data grouping that is needed and used by various SAP Direct

Store Delivery components (for example, Visit Control , Transportation Planning , VehicleSpace Optimization, and Route Accounting ) throughout the DSD scenario.

Process

This section contains the following Customizing settings that are relevant to vehicle masterdata:

1. Define Technical Objects Types [Page 275]

2. Define Usage Types for Fleet Objects [Page 276]

3. Set View Profiles for Technical Objects [Page 277]

4. Maintain Equipment Category [Page 279]

5. Define Number Ranges [Page 281]

6. Assign View Profile and Equipment Categories to Fleet Object Type [Page 282]

7. Assign Means-of-Transportation Types to Equipment Category/Vehicle [Page 284]



(C) SAP AG 275

Define Technical Objects Types

In this IMG activity, you define types of technical objects.

Each piece of equipment or each functional location can be assigned to a technical objecttype. In this way, you can combine several pieces of equipment, for example, into groups ofall equipment that are used for the same purpose. The grouping can then be used to evaluatemaster data or maintenance data.

These technical object types can also be used as a grouping instrument in fleet management.

Procedure

1. In Customizing for Plant Maintenance and Customer Service under Master Data in

Plant Maintenance and Customer Service Technical Objects General Data ,choose Define Types of Technical Objects.



FieldName


ObjectType

Enter an alphanumeric key (up to 10 characters) to identify the type oftechnical object defined.

Example: DSD_FLEET


Example: DSD Vehicle


Result

Technical object types can be used for the creation of a new vehicle master data record.



(C) SAP AG 276

Define Usage Types for Fleet Objects

In this IMG activity, you define different usage types for fleet objects. You can define a usage

type as a criterion for usage-related categorization.

Possible definitions for usage types are, for example, as follows:

Use fleet object exclusively for business

Use fleet object only as company transport

Use fleet object only for executive board purposes

Use fleet object for business as well as privately

These settings serve solely to check permitted values and for reporting functions. The usage

indicators defined in this table are selected in the vehicle master data records on the VehicleTechnology tab.

Procedure


Plant Maintenance and Customer Service Technical Objects Settings for Fleet

Management , choose Define Usage Types for Fleet Objects.




Usage Indicator Enter a 1 digit character to identify fleet usage.

Example: D

Text Enter a short text for the usage indicator.

Example: DSD Process


ResultTechnical object types can be used for the creation of a new vehicle master data record.



(C) SAP AG 277

Set View Profiles for Technical Objects

In this IMG activity, you can create individual screens for technical objects.

The data fields for the technical objects are sorted by contents into screen groups. You candefine one or more view profiles for each screen group, for example, equipment. Each viewprofile enables you to assign pre-grouped and accompanying fields to individual screentemplates. These screen templates can be labeled individually using tab pages.

To make the tab pages visible in the maintenance transactions, they must be labeled asactive. You can assign a view profile to each equipment category or functional locationcategory and to each fleet object type.

Prerequisites

Number IDs of technical object views are available.

List of sub-screens of technical object views are available.

Procedure


Plant Maintenance and Customer Service Technical Objects General Data ,choose Set View Profiles for Technical Objects.



FieldName


ScreenGrp

Choose the appropriate entry (H4 Screen group fleet object data) from the inputhelp.

Profile

Enter a code (up to 8 characters) for the profile to be defined. This entry controlswhich (fleet-specific) views for a fleet object should be displayed on the screen.

Example: DSD

Profile

Enter a description for the view profile defined.

Example: DSD Profile

4. Choose Enter .

Highlight the newly created entry and choose Activity and Layout of Views in the left

window.





(C) SAP AG 278

FieldName


Number Choose the number ID (130) for the Technical Object View VehicleID/Measmnts.

Tab active Select the checkbox in order to make the screen visible in data maintenancetransactions.

Seq. no. Choose Identification (200) from the input help.



7. Choose Enter .

Repeat step 7 by making a second set of entries in the Activity and Layout of Views screen according to the following table:

FieldName


Number Choose the number ID (140) for the Technical Object View VehicleTechnology.

Tab active Select the checkbox in order to make the screen visible in data maintenancetransactions.

Seq. no. Choose Additional Data (220) from the input help.


9. Choose Back and save your entries.



(C) SAP AG 279

Maintain Equipment Category

In this IMG activity, you define the description for an equipment category. This allows you to

control which basic characteristics an equipment master record such as a vehicle masterrecord should have. Using these control characteristics, you can decide how many and whichequipment categories you require.

Prerequisites

A view profile for technical objects is defined.

Procedure


Plant Maintenance and Customer Service Technical Objects Equipment

Equipment Categories , choose Maintain Equipment Category .




Category

Enter a one digit character to distinguish individual technical objectsaccording to their use.

Example: D

ReferenceCategory

M = Machines

P = Production Resources/Tools

S = Customer equipment, defines history-relevant fields of an equipment

master record.

Equip. Cat.

Enter a description indicating the meaning of the specific equipmentcategory.

Example: DSD Vehicle

Checkbox A

Select this checkbox to prohibit alphanumeric equipment numbers for this

equipment category, for example, when external number assignment isallowed.

X = Alphanumeric equipment numbers are prohibited

<Blank> = Alphanumeric equipment numbers are allowed

Checkbox C

Select this checkbox to define whether change documents should be writtenin order to trace changes made to the master data. There are two options:

X = Change documents should be written

<Blank> = No change documents required.

Checkbox W Specifies whether one of the following workflow events is generated when



(C) SAP AG 280


maintaining equipment master data:

o PieceOfEquipment.Created

o PieceOfEquipment.Changed

o PieceOfEquipment.LocationChanged

Object Info No entry.

View Profile

Assign a view profile for the master data maintenance from the input help.

This entry controls which (fleet-specific) views for a fleet object should bedisplayed on the screen.

Ctyp/MatNo

Ensures that the construction type and material number are keptsynchronous in the master record for serialized equipment.

Choose default indicator settings from the input help (there is no check ifconstruction type and material number are synchronous).




(C) SAP AG 281

Define Number Ranges

In this IMG activity, you maintain number range groups and allocate equipment categories to

those groups. The same number ranges can be shared by several equipment categories.

Prerequisites

Equipment categories are defined.

Procedure


Plant Maintenance and Customer Service Technical Objects Equipment

Equipment Categories , choose Define Number Ranges.

2. Choose Groups (designated by the pencil icon).

The system displays newly created equipment categories that have not yet beenassigned to a group.

3. Select a group from the list by selecting the respective checkbox (we recommendusing the Standard Number Range group).

4. Select the letter of the non-assigned equipment category and choose Select Element (F2).

5. Choose Element/Group.

Result

The equipment category is allotted to the selected number range group. The underlyingnumber ranges of that group are used when creating an equipment master data record of thatequipment category.



(C) SAP AG 282

Assign View Profile and Equipment Categories toFleet Object Types

In this IMG activity, you define different types of fleet objects. You assign a view profile toeach of these fleet object types that defines the screen template layout for the fleet object-specific data. You also determine in this table which equipment categories are allowed forfleet objects of a fleet object type.

The fleet object type is a technical object type to which fleet object-specific attributes areassigned.

The fleet object type (Vehicle Type) is a mandatory field when creating a new vehicle masterdata record.

Prerequisites

Fleet object types are defined as types of technical objects.

View profiles for the technical objects concerned are defined.

Equipment categories are defined.

Procedure


Plant Maintenance and Customer Service Technical Objects Settings for Fleet

Management , choose Assign View Profile and Equipment Categories to FleetObject Type.




Veh. Type Select an object type from the input help.

Text Is entered automatically by choosing Enter .

Profile Select a view profile from the input help.

4. Choose Enter .

Highlight the new entry and choose Definition of Default Equipment Category in theleft window.

If only one equipment category is defined for each fleet object type, then this isproposed automatically in this screen when a new fleet object is created. Move on tostep 9.

If more than one equipment categories exist for the selected fleet object type, thencontinue with Step 7.





(C) SAP AG 283


Equi Cat (Equipment Category) Select an equipment category from the input help.

Long name equi cat Is entered automatically by choosing Enter .




(C) SAP AG 284

Assign Means-of-Transportation Types toEquipment Category/Vehicle Types

In this IMG activity, you define whether the respective equipment category or vehicle typeinvolves a trailer or a tractor vehicle.

Procedure


Data , choose Assign Means-of-Transport Type to Equipment Category and VehicleType.




Equip Category Select an equipment category from the input help.

Vehicle Type Select a vehicle type from the input help.

Means-of-Trans. Type Select a means-of-transportation type from the input help.




(C) SAP AG 285

Material Master Data Configuration

With regards to material master data, the standard material master data records are

enhanced to fully utilize them within the DSD process. These settings are used by variousSAP Direct Store Delivery components (for example, Visit Control , Transportation Planning ,Vehicle Space Optimization, and Route Accounting ) throughout the DSD scenario.

Process

This section deals with the following customizing steps that are relevant to material masterdata:

1. Determine Categories for Totals Fields [Page 286]

2. Define Counting Groups [Page 287]

3. Define UoM Levels for Counting with Counting Groups [Page 288]

4. Assign Screen Sequences [Page 290]



(C) SAP AG 286

Determine Categories for Totals Fields

In Customizing, up to four totals categories are available. In this IMG activity, you define the

names of these totals categories (customer-specific).

For each document (order, delivery, or shipment), the system dynamically determinesmaterial quantities that correspond to the same totals category being assigned in the materialmaster. The system adds up the relevant material quantities and displays the result for eachtotals category in a dialog box, for example, when choosing Save to save a delivery. Youdefine the conversion factor in the material master with which the system determines thematerial quantities for each document.

Procedure


Data , choose Determine Categories for Totals Fields.

2. Enter your customer-specific names for one to four category fields.


Result

The four totals categories are displayed in the material master on the DSD – Totals tab withtheir given names. You can assign one of these totals categories as well as a unit of measureto the respective material.



(C) SAP AG 287

Define Counting Groups

In this IMG activity, you define counting groups. Within each counting group, you can define

multiple levels with different units of measurement (UoMs). These UoMs have to bemaintained as alternative UoMs for each material that belongs to a counting group. Whileeach counting group can be assigned to multiple materials, each material can only beassigned to one counting group. The conversion factors of these UoMs do not need to be thesame for all materials of a counting group but they do need to be defined.

Counting groups are used to group different materials with similar characteristics. This makesit easier for checkers to count the truck load in the warehouse right after the loading hasfinished or at the gate of the distribution center when the truck leaves the depot.

Remember to assign the counting groups to materials in the material master, once they aredefined.

Once you have assigned the counting group to the material master, you need to download

this counting group assignment to the connector with the /DSD/HH_MAT transaction code

(send DSD-specific material data).

If you wish to use counting groups during the check-out and check-in process on the mobile

device, you must activate the CO_CG and CI_CG parameters (for Regular Check-out/Check-

in) and the RLD_COCI_CG parameter (for Reload Check-out/Check-in) in Global Device

Customizing.

Procedure


Data , choose Define Counting Groups.



Counting Group Define a counting group (free text).

Example: 1L-6PACK

Description

Enter a description for the counting group.

Example: All 6-Packs with 1L-Bottles


Result

You have defined counting groups. These counting groups are available for assignment inmaterial master records on the respective subscreen of the DSD-Data tab.



(C) SAP AG 288

Define UoM Levels for Counting with CountingGroups

In this IMG activity, you define the hierarchy of units of measurement (UoMs) for eachcounting group.

This UoM hierarchy is used for the following:

In the mobile scenario for regular and reload loading confirmation (on the back end)and the check-out/ check-in on the mobile client

In the paper-based scenario for regular and reload loading confirmation(/DSD/SV_LC_COUNT transaction) as well as for check-out (Settlement Cockpit )

Prerequisites

Counting groups have been maintained.

Procedure


Data , choose Define UoM-Hierarchy for counting with counting groups.


FieldName


CountingGroup

Choose a counting group from the input help.

Example: 1L-6PACK

UoM-Level

Enter a level number for the assigned UoM. If more than one level ismaintained for the same counting group, you must use sequential numbering.

Example: 1

Every level represents another UoM within the same counting group. Foreasier readability, it is recommended to set level 1 to the smallest UoM level inwhich materials can be counted.

UoM Assign a UoM from the input help.

The UoM assigned in the UoM field must be maintained as an alternative UoM in thematerial records that belong to the respective counting group. You can check thecorrect and complete assignment of alternative UoMs by using the/DSD/SV_CHECK_CG program.




(C) SAP AG 289

Result

You have defined UoM levels for counting groups. These UoM levels are available in specificsteps throughout the DSD process, for example, for loading confirmation and regular andreload check-out/check-in.



(C) SAP AG 290

Assign Screen Sequences

In material master records, two specific DSD tabs are available. They are named DSD –

Totals and DSD –

Data. In order to make these tabs visible and accessible, you need to usethis Customizing table to maintain the necessary settings.

In this table, you assign a screen sequence to a combination of one or more transactions,users, material types, or industry sectors. The standard screen sequence carries the screensequence number 21. This screen sequence number (SSq) is valid for all users, materialtypes, and industry sectors.

For the DSD process, the following screen sequence numbers have been implemented andare included in the shipment:

BC = pre-defined screen sequence number for the DSD tabs, including countinggroup

BD = pre-defined screen sequence number for the DSD tabs, without counting group

BE = pre-defined screen sequence number for the empties tabs

BV = pre-defined screen sequence number for the DSD tabs, including the VSO tabs

In this Customizing table, you may either replace the standard screen sequence number (21)by one of the DSD-relevant screen sequence numbers (BC, BD, BE, or BV), or you create anew combination of user/transaction/material type/industry sector and thereafter assign aDSD-relevant screen sequence number to make the DSD or VSO tabs in the material masterrecords visible.

For more information, refer to Customizing for this menu option.

Prerequisites

You have activated DSD.

You have defined the Screen Sequences BC (for DSD including Counting Group), BD(for DSD), BE (for Empties) or BV (for VSO).

Procedure

1. In Customizing for Logistics General under Material Master Configuring the

Material Master , choose Assign Screen Sequences to User/Material

Type/Transaction/Industry Sector .

The Screen Sequence Control screen is displayed.

You have a variety of Customizing options depending on your specific needs byentering your customer-specific names for from one to four category fields. Asexamples, this procedure describes two possible settings.

Example 1 – DSD and/or VSO tabs should be visible for all materials, independent ofuser, material type, or industry sector. In the Sequence Control : Overview screen,locate the entry with the following settings:



(C) SAP AG 291


SRef:Trans Select the standard pre-defined entry (standard number is 01).

SRef:user

For the standard entry 01, the value should read *

( = valid for all users).

SRef:Matl Type For the standard entry 01, the value should read *

( = valid for all material types).

SRef:industry For the standard entry 01, the value should read *

( = valid for all industry sectors).

SSq

For the standard entry 01, the value should read 21

(21 = valid for all users, all material types, all industry sectors). Replacethis screen sequence number (21) with one of the DSD-relevant screensequence numbers.

Example: BV

Screen seq.description

The description for the screen sequence number selected willautomatically be entered here.

Example 2 – DSD or VSO tabs – should be visible for all materials to selected users

only, independent of material type or industry sector: in the screen Screen SequenceControl: Overview , locate entry 01 with the pre-defined settings (01, *, *, *, 21).

Select this entry and choose Copy .

Enter the following data:


SRef:Trans Leave the entry 01 unchanged.

SRef:user Enter the DSD-relevant screen sequence number.

Example: BV

SRef:Matl Type Leave the value * (valid for all material types) unchanged.

SRef:industry Leave the value * (valid for all industry sectors) unchanged.

SSq Select one of the DSD-relevant screen sequence numbers.

Example: BV

Screen seq.description

The description for the screen sequence number selected isautomatically entered here.




(C) SAP AG 292

On the left window, choose User Screen Reference.



FieldName User Action and Default Values

Name Enter the logon name of the user for which the visibility of the DSD or VSOtabs should be allowed.

SRef:user Enter the DSD-relevant screen sequence number.

Example: BV


Result

The screen sequence maintained in this table appears automatically for the respective user(s)when the transaction, material type, or industry sector is chosen.



(C) SAP AG 293

Visit Control Configuration

The mobile Order-to-Cash DSD scenario integrates the mobile DSD solution for the mobileroles preseller and delivery driver into the DSD back end processes. The orders taken on themobile device by the preseller are uploaded into the back end for further processing. Thedelivery driver fulfills these orders during the next planned delivery cycle of the customers.

It is important to visit neighboring customers together and to contact them according to theircalling, visiting, and delivery restrictions. Visit Control is a tool that helps manufacturers planand schedule their sales and distribution operations based upon allowed times for sales,calling, and delivery visits as negotiated and agreed upon with the customers.

For customer enhancements in DSD visit control, the /DSD/BADI_VC_BAPI BAdI is

available for enhancing visit plans and visit lists with values from customer-specific fields.

ProcessTo use the DSD Visit Control functionality to its fullest scope, perform the followingCustomizing steps:

1. Define Calendar Types [Page 294]

2. Define Visit Groups [Page 295]

3. Define DSD Groupings [Page 296]

4. Maintain Number Ranges for Visit Plans [Page 297]

5. Maintain Number Ranges for Visit Lists [Page 298]

6. Define Visit Plan Types [Page 299]

7. Specify Allowed Sales Document Types [Page 303]

8. Specify Allowed Transaction Types [Page 304]

9. Assign Sales Activity Types/Outcome to Customer Visit Status [Page 305]



(C) SAP AG 294

Define Calendar Types

In this IMG activity, you define your own customer-specific calendar types. The calendar type

is used to determine how the dates for customer visits planned in visit control should begrouped together.

Calendar types are assigned to visit plan types (see Define Visit Plan Types [Page 299]).During the creation of a visit plan, a calendar is created for each customer that was assignedto this visit plan according to the calendar type of the visit plan type.

As soon as the customer was assigned a visit plan, the respective calendar can be displayedin the customer master data record on the Visit Information tab.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Visit

Control , choose Define Calendar Types.




Calendar Type Specify an alphanumeric key with up to 3 characters.

Name of

Calendar Type

Enter a description of the calendar type being defined. We recommendusing descriptions that provide information about the types of datesgrouped into this calendar.

Two examples are: <PRESALES> and <DELIVERY TO CUSTOMERS>.


Result

Calendar types have been defined and are now available to be used in visit plans andcustomer master data.



(C) SAP AG 295

Define Visit Groups

In this IMG activity, you define your own visit groups. The visit group is a new organizational

unit to be used in visit control. Using visit groups enables you to restrict the processing of visitplans and visit lists to specific users.

Procedure


Control , choose Define Visit Groups..




Visit Group Specify an alphanumeric key with up to 10 characters.

Name of Visit Group Enter a name as a description of the visit group being defined.


Result

Visit groups have been defined and are now available for use in visit plans.



(C) SAP AG 296

Define DSD Groupings

In this IMG activity, you define your own customer-specific DSD groupings and assign a

calendar type to them. The DSD grouping is a grouping element for existing materials. Youassign the DSD grouping in the material master on the DSD-Data tab.

Assigning a calendar type to a DSD grouping as well as to a visit plan type enables you toschedule customer visits depending on specific materials.

An example of material-dependent visit control is newspapers being delivered daily (DSDgrouping: D1) while magazines are only being delivered weekly (DSD grouping: D2 ).

Procedure


Control , chose Define DSD Grouping .




DSD Grouping Specify an alphanumeric key with up to 6 characters.

Name of DSD Grouping Enter a description for the DSD grouping.

Calendar Type Select the calendar to assign from the input help.


Result

DSD groupings are defined and available for use in visit plans.



(C) SAP AG 297

Maintain Number Ranges for Visit Plans

In this IMG activity, you define the type of number assignment and the number range intervals

for visit plans. Visit plan number range intervals are assigned to visit plan types (see DefineVisit Plan Types [Page 299]). Each time you create a visit plan, the system must generate aunique number. This number is taken from the visit plan number range interval assigned tothe visit plan type concerned.

Procedure


Control , choose Define Number Ranges for Visit Plans.

2. Choose Intervals (with the Pencil icon).

Choose Interval+.

Maintain a number range interval by indicating the limits of the number range interval.The limits of the number range intervals are not allowed to overlap. Each number isallowed to exist just once.

3. Choose Insert (Enter) to add the entry to the table.

Repeat steps 2. and 3. to maintain more than one number range interval.


Result

Number ranges for visit plans have been maintained and are now available to be assigned tovisit plan types.



(C) SAP AG 298

Maintain Number Ranges for Visit Lists

In this IMG activity, you define the type of number assignment and the number range intervals

for visit lists. Visit list number range intervals are assigned to visit plan types (see Define VisitPlan Types [Page 299]). Each time you generate a visit list, the system must assign a uniquenumber. This number is taken from the visit list number range interval assigned to the visitplan type concerned.

Procedure


Control , choose Define Number Ranges for Visit Lists.

2. Choose Intervals (with the Pencil icon).

Choose Interval+.

Maintain a number range interval by indicating the limits of the number range interval.The limits of the number range intervals are not allowed to overlap. Each number isallowed to exist just once.

3. Choose Insert (Enter) to add the entry to the table.

Repeat steps 2. and 3. to maintain more than one number range interval.


Result

Number ranges for visit lists are maintained and are now available to be assigned to visit plantypes.



(C) SAP AG 299

Define Visit Plan Types

The visit plan type is the central object in visit control and the basis for dynamic transportation

planning. The visit plan type defines the roles and uses of visit plans and visit lists (forexample, visit plans/visit lists for delivery drivers, visit plan/visit lists for presellers). Youspecify the characteristics of the visit plans and visit lists for the visit plan type and use this tocontrol how they are processed.

In this Customizing table, you define your own visit plan types. The preseller primarily usesvisit lists without deliveries. Therefore, the visit list is the primary document for presellers. Incontrast, the delivery driver needs shipments containing pre-sold deliveries. Therefore, theshipment is the primary document for the driver. For each of these different requirements, youcan create different visit plan types.

In addition, you determine which visit plan type is to be used for manual shipment creationfrom the tour master. It is also possible to enter default values for driving time and waiting

times.

SAP Direct Store Delivery supports multi-day tours. You need to set up your visit plan typeaccordingly if it is used for this scenario.

Prerequisites

Number range intervals for visit plans and visit lists are defined.

Calendar types are defined.

Settlement office is available.

Settlement type is available.

Procedure


Control , choose Define Visit Plan Types.




Visit Plan Type

Specify an alphanumeric key with up to 3 characters. Enter also adescription for the visit plan type.

Example: PRESELLER

Visit Control

Visit Plan No.Range No.

Select a number range no. from the input help.

Visit plans are assigned numbers from this number range when beingcreated.

Visit List No.Range No.

Select a number range no. from the input help

Visit lists are assigned numbers from this number range when being



(C) SAP AG 300


created.

Calendar Type

Select a calendar type from the input help. Choose the calendar typethat corresponds to your driver role.

Example: PRESALES

RelevantDocuments

Within this block, you define whether a visit list or a shipment is theleading document. Set the 3 options as follows according to therequested driver role:

o For delivery drivers (Shipping Document and ShipDelivery option)

o For van sellers (Visit List Document and ShippingDocument option)

o For mixed role drivers (select the checkboxes for allthree options)

o For presellers (Visit List Document option)

Visit ListDocument

Set this option depending on the requested driver role.

ShippingDocument

Set this option depending on the requested driver role.

Ship Delivery Set this option depending on the requested driver role.

Visiting Times

Goods ReceivingHrs

Select this checkbox if you wish to display goods receiving hours percustomer in the visit plan.

Visiting Hoursfrom CP

Select this checkbox if you wish to display visiting hours of the customercontact person in the visit plan.

Function If you set the option Visiting Hours from CP , you need to enter the codeof the Customer Contact Person concerned.

Multiday Tour

Select this checkbox if your visit plan is used for tours more than one

day.

Duration ofMultiday Tour

Specify the least number of days a multiday tour can have.

A tour cannot last longer than the number of days specified, forexample, a tour is not extended if there are non-working days within thetour.

Multiday TourSetting

Select a value from input help.

Example: NP



(C) SAP AG 301


Driving Times – Default Values

Default valuesentered here

Waiting Timehh:mm

Enter a default time (hh:mm). The waiting time describes the averagetime the driver requires to perform tour activities per customer.

Example: 00:30

Dir.Driv.Timehh:mm

Enter a default time (hh:mm). The direct driving time describes theaverage time the driver needs to drive from the depot to the firstcustomer on the itinerary.

Example: 00:30

Driving Timehh:mm

Enter a default time (hh:mm). The driving time describes the averagetime the driver requires to drive from one customer to the next.

Example: 00:30

TransportationPlanning

Max. LoadingTries

Enter the maximum number of attempts to load a truck. This criterion istaken into account during dynamic transportation planning.

Example: 6

Manual Shipment

In general, do not select this checkbox. If you maintain more visit plantypes, you can set this option only once. The system uses the optionvisit plan type when creating a shipment manually to gain access to the

tour master.

RouteAccounting – Default Values

Settlement Office

Assign a settlement office from the input help. If the settlement office isnot yet defined, you may assign it later. The settlement office assigned

to the visit plan type is taken as default settlement office whenperforming the final settlement run. However, you may overwrite it.

Settlement Type

Assign a settlement type from the input help, depending on thesettlement office chosen. If the settlement type is not yet defined, youmay assign it later. The settlement type assigned to the visit plan type istaken as default settlement type during the final settlement run.However, you may overwrite it.

MessageControl

Output Determ.Proc.

No active entry possible. A passive entry is displayed once an output

determination procedure has been maintained within output control andassigned to the visit plan type.



(C) SAP AG 302


Output Type No active entry possible. A passive entry is displayed once an outputtype has been assigned to the visit plan type within output determinationprocedure.


Result

It is now possible to create visit plans and, subsequently, generate visit lists.



(C) SAP AG 303

Specify Allowed Sales Document Types

In this IMG activity, you define the allowed sales document types. You can also assign a

calendar type and the minimum lead time to these types.

The sales document types maintained in this table are used for order entry and to determinethe requested delivery date and route based on visit plans and visit lists, provided a calendartype has been assigned.

When creating an order (for example, with order type ZTA), the system checks whether theorder type is maintained in this Customizing table with a calendar type assigned. Without thisassignment, the system uses standard settings to determine the requested delivery date androute and leaves visit control settings aside. If you have maintained a calendar type for the

order type and it matches the calendar type valid for the customer concerned, the systemuses the visit plan/visit list that customer is assigned to. It uses the system date and adds theminimum lead time maintained to calculate the next requested delivery date.

Procedure


Control , choose Specify Allowed Sales Document Types.




Sales Doc.Type Choose a sales document type from the input help.

Example: ZTA

Calendar Type Choose a calendar type from the input help.

Example: DELIVERY TO CUSTOMERS

Min. Lead Time Enter a time duration formatted hh:mm.

Example: 10:00


Result

Visit plans and visit lists are considered during order creation to determine the next planneddelivery date for a given customer.



(C) SAP AG 304

Specify Allowed Transaction Types

Visit Control allows users to maintain customer contact appointments, which are used during

order maintenance in SAP ERP to align requested delivery dates. Visit Control is part of DSDand as such is only available in SAP ERP systems. If users opt to create sales orders in theSAP CRM Customer Interaction Center (CIC), they need access to the contact appointmentsmaintained in Visit Control.

This type of access can be provided. In this IMG activity, you must maintain additionaltransaction types for the DSD process. You must assign a calendar type and a minimum leadtime to each transaction type.

You must also implement the /DSD/VC_REQDATES_GET function module with the

CRM_SALES_MERGE method of the CRM_SALES_BADI BAdI. With this function module

implemented and based on the entries maintained in this Customizing activity, the systemdetermines the contact appointments maintained in Visit Control for a customer and returns

the data to the target system using an RFC connection.

Prerequisites

The Business Function /DSD/BF must be activated.

Procedure


Control , choose Specify Allowed Transaction Types.



FieldName


Trans.Type

Enter a transaction type (with up to four digits). You can either define the typeyourself (free text definition), or use the exact name of the sales document asdefined in the target system (for example, SAP CRM).

Example: CRM1

Calendar

Type

Choose a calendar type from the input help.

Example: DELIVERY TO CUSTOMERS

Min. LeadTime

Enter time duration in the format hh:mm.

Example: 10:00


Result

Based on the entries made in this table, DSD Visit Control contact appointments for a specificcustomer can be requested during order maintenance, for example, in an external system

such as SAP CRM.



(C) SAP AG 305

Assign Sales Activity Types/Outcome to CustomerVisit Status

In this IMG activity, you assign a contact type and a contact outcome to a status of a salesactivity type. Depending on the contact outcome, you also assign an outcome analysis. Thesales activity types equal the customer visit reasons maintained in Route Accounting .

This table is used whenever the system detects an unsuccessful customer visit during theFinal Settlement Run; provided a status (giving a reason for the failure) had been assigned tothe customer visit. An unsuccessful customer visit is a visit that did not yield either orders ordeliveries and for which customer data only exists in the Route Accounting Database.

According to the settings made for a specific reason in this Customizing table, the systemcreates a contact using the parameters maintained in this table.

A sales activity type represents various business transactions in sales support in your

company.

Prerequisites

You have defined customer visit reasons.

Refer to Route Accounting , menu Define Customer Visit Reasons [Page 196].

You have defined sales activity types.

In Customizing for SAP ERP under Sales and Distribution Sales Support (CAS)

Sales Activities , choose Define Sales Activity Types.

You have defined sales activity outcomes and sales activity outcome analyses.


Sales Activities , choose Define Sales Activity Outcomes and Sales OutcomeReasons.

You have assigned sales activity outcomes analyses to sales activity outcomes.


Sales Activities , choose Define Sales Activity Outcomes and Sales OutcomeReasons..

Procedure


Control , choose Assign Sales Activity Types and Outcome to Customer VisitStatus.




CVStatus Select the appropriate customer visit reason from the input help.




(C) SAP AG 306


SalesActTy Select the appropriate sales activity type from the input help.

Example: SALES CALL

Outcome Select the appropriate sales activity outcome from the input help.

Example: UNSUCCESSFUL

Analysis Select the appropriate sales activity analysis from the input help.

Example: NO INTEREST


Result

If unsuccessful customer visits have an appropriate status assigned, the system can respondcorrectly during the Final Settlement Run.



(C) SAP AG 307

DSD Messaging - Text Control within Visit Control

Throughout the logistical process, business partners need to be able to exchange information.

In Sales and Distribution, this type of exchange is supported by messages (or texts) that aremaintained in master records (customer) and in documents (order, delivery, and shipment).

The Text Control within Visit Control function can be used to maintain specific visit texts onthe header and item level of visit plans or visit lists. Customer master texts can also be usedin customer visits of a given visit plan or visit list and downloaded to the DSD Connector to beforwarded to the mobile client. There are two basic options for downloading visit texts andcustomer texts:

Customer master texts are downloaded together with the customer master data (by

using the BD12 transaction), and the visit texts are downloaded with the relevant visit

list.

Customer master texts are considered during text determination of visit texts byassigning customer master texts (via copy or reference) to each visit for thatcustomer. In this way, customer master texts can be downloaded for each relevantcustomer visit together with the download of the visit list.

The Text Control within Visit Control function enables the following processing and controlfunctions:

Texts from the customer master records are proposed in visit plan items and visit listitems, if the appropriate Customizing settings are made.

All texts found via text determination are either copies or references. If a text wascopied (from a visit plan to the generated visit list, for example), it remains the same

even if the original text changes. If a text is referenced, changes in the original textare immediately reflected in the referenced text. However, if the referenced text itselfis changed, the text is duplicated and becomes an independent text.

When a new visit plan is created using the copy function, texts are copied from theoriginal visit plan to the new visit plan. Only text IDs are copied that are valid for thevisit plan type on which the new visit plan is based.

Texts are identified by text object, text name, and text ID. The text name is derived from theobject ID (such as visit plan ID) to which the text belongs. Since visit plans and visit lists areassigned to different number ranges, there could be a visit plan and a visit list with the samenumber. For unique identification, the following four text objects are defined:

/DSD/VCVPH

Text object for Visit Plan Header texts

/DSD/VCVPP

Text object for Visit Plan Item texts

/DSD/VCVLH

Text object for Visit List Header texts

/DSD/VCVLP

Text object for Visit List Item texts



(C) SAP AG 308

In the back end, customer master texts and visit texts (for visit plans and visit lists) are saved

in the standard STXH and STXL tables for text control. To make these texts available to the

driver on the mobile device during tour execution, they must be defined as driver messages.The same is true for the paper-based scenario when a visit list needs to be printed. On theprintout, only visit list texts are printed for which the corresponding text types are maintainedas driver messages in the /DSD/HH_DRVTXT back end table.

Downloading texts to the DSD Connector is done using the DEBMAS IDoc (for customermaster texts) and the /DSD/HH_ROUTE_ITINERARY IDoc (for visit texts). They are stored inthe DSD Connector /DSD/ME_MSG_HD table. On the mobile device, visit texts are displayedas tour messages (visit list header texts) or visit messages (visit list item texts), and customermaster texts are displayed as customer messages.

On the mobile device, messages are only displayed if the language key of the original text(text in a delivery, for example) is identical to the language key maintained for the driver in themobile device settings.

Process

This section contains the following Customizing settings that are relevant for using TextControl within the Visit Control function:

1. Define Text Types for Visit Control [Page 309]

2. Maintain Text Control for Visit Control [Page 310]

3. Define Driver Messages [Page 314]



(C) SAP AG 309

Define Text Types for Visit Control

In this IMG activity, you define new text types for the new text objects. Text types are

identified by their unique combination of text object and text ID.

Procedure


Control , choose Text Control within Visit Control .

On the screen that appears, select the radio button (Item, for example) of the desiredtext object (such as Visit List ) and choose Text Types.




Text object Select the desired text object.

Example: /DSD/VCVLP

Maintain Text ID for Object

Text ID Enter a text ID.

Example: 4010

ID Description Enter a description for the new text ID.

Example: Text ID VLP 4010


Result

Text IDs are defined for the relevant text object and are ready for assignment to thecorresponding text procedures in subsequent Customizing activities.



(C) SAP AG 310

Maintain Text Control for Visit Control

In this IMG activity, you set up text determination for each text object in visit control, including

visit plan header texts, visit plan item texts, visit list header texts, and visit list item texts. Textdetermination for visit control requires the following settings:

Define a text procedure

Assign one or more text IDs to the text procedure

Define an access sequence

Assign one or more text IDs to the access sequence

Assign the text procedure to the visit plan type

Visit plan headers do not contain any references to other objects. Therefore, it is not possibleto copy texts from other applications to the visit plan header, which means that no accesssequence is required.

Prerequisites

The relevant text IDs have been defined for each text object.

Procedure


Control , choose Text Control within Visit Control .

On the screen that appears, select the desired radio button (Item, for example) of thedesired text object (such as Visit List ) and choose Change.




TxPrc

Enter a key with up to two digits for the text procedure you wish todefine.

Example: Z1

DescriptionTxtDetProc

Enter a description for the new text procedure.

Example: TextProc VLP Z1

4. Choose Enter .

Highlight the new entry and double-click Text IDs in Text Procedure in the left

window.

5. Choose New Entries. In the screen that appears, enter the following data:

Field

Name User Action and Default Values



(C) SAP AG 311

FieldName


ID

Choose a text ID from the input help. The list displays all text IDs that belong tothe relevant visit control text object (such as Visit List Item).

Example: 4010

Seq Enter a sequential number for the text ID.

Example: 401

Meaning Entered automatically when you choose ENTER (if maintained for the text ID).

RefDp

Select the reference/duplication checkbox if you want the system to create areference of the text maintained with this text ID.

If a text is maintained in the visit plan and the checkbox is selected, the text isreferenced in the visit list item when the visit list is generated. Whenever the visitplan text is changed, the visit list text is automatically changed as well.

If the checkbox is not selected, the text is copied from the visit plan to the visitlist, for example. Any text update in the visit plan does not change the visit listtext.

Acc.

Enter an access sequence that the system can use to determine the text IDs thatshould be referenced or copied into the visit list header or item.

If the access sequence is not yet defined, skip the field for the moment andmaintain the entry later once the relevant access sequence has been created.


For the /DSD/VCVPH text object (Visit Plan Header Texts), an access sequence is

not required. In this case, skip the respective steps and continue with Text Procedure Assignment (step 8).

Choose Access Sequences in the left window, and choose New Entries.


Accesssequence

Enter a numerical key with up to four digits for the access sequence youwish to define using the customer namespace (starting with 9*).

Example: 9000

Description Enter a description for the new access sequence.

Example: Access Seq VLP 9000

7. Choose Enter .

Highlight your entry and choose Access sequence for text IDs in the left window.Choose New Entries.



(C) SAP AG 313


Example: RH02

Visit Plan

Type

Description is entered automatically depending on entry made in the VPT

field.

TxPrc Choose the text procedure that you wish to assign to the visit plan type.

Example: 40

9. Save your entry.

Result

Based on the settings made in this table for customer texts and visit texts, the system is ableto determine the permitted text IDs for a given text object to be considered during textprocessing in visit control.



(C) SAP AG 314

Define Driver Messages

In the /DSD/HH_DRVTXT back end Customizing table, you must maintain all text IDs that you

want to have displayed on the driver’s mobile device (mobile scenario) or show on the printoutof the visit list (paper-based scenario). In this table, only text objects are allowed that are usedin the applications for customer master, visit list, shipment, delivery, and order. The text

objects are predefined by SAP and are contained in the TTXOB table.

For the mobile scenario only: Once maintained, you must download your entries to the DSDConnector (/DSD/ME_MSG_CUST table) using the /DSD/HH_DRVTXT transaction.

The system transfers the messages from the back end to the DSD Connector but onlymessages that correspond to message types maintained in this table are transferred to the

driver’s mobile device. On the mobile device, messages are displayed as follows:

Tour messages

Maintained in visit list header and shipment

Visit messages

Maintained in visit list items

Customer messages

Maintained in customer master data as general customer texts or sales area-dependent customer texts

Activity messages

Maintained in order or delivery

When a visit list is printed, only visit list texts that are defined as driver messages in this table

are considered for printing on the new PDF form for visit lists (/DSD/VC_VLIST_PDF). This

PDF form is only available if the Business Function /DSD/BF is active.

If the Business Function /DSD/BF has not been activated, the table for driver messages is

located in Customizing for Logistics Execution under SAP Direct Store Delivery OutputControl Output Control for Shipments Print Output and Download from Shipment Define

Driver Messages . In this case, the table entries maintained are valid only for the deliveryprocess (not for the sales process). The shipment type and transportation planning type mustalso be maintained.

Make sure that you have maintained /DSD/HH_ROUTE_ITINERARY03 (with ending 03) as

the basic type for your /DSD/HH_ROUTE_ITINERARY . Only this version contains the

segments required to download visit texts to the mobile device and make them visible asdriver messages. For more information, see Download: Defining Scope of Data Transfer

[Page 506] or Specify Volume of Transmitted Shipping Data [Page 530].



(C) SAP AG 315

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Output

Control , choose Define Driver Messages.




MessageType

Enter the name of a message type relevant for the transmitted shippingdata.

For visit texts, use /DSD/HH_ROUTE_ITINERARY.

For customer texts, use DEBMAS.

For sales document texts, use the following:

o SHPMNT

o DESADV

o ORDRSP

Text Object

Select the appropriate text object.

For visit texts, use the following:

o /DSD/VCVLH – Visit List Header

o /DSD/VCVLP – Visit List Item

For customer texts, use the following:

o KNA1 – General Customer texts

o KNVV – Sales area-dependent texts

For sales document texts, use the following:

o VTTK – Shipment Header

o VBBK – Order/Delivery Header

o VBBP – Order/Delivery Item

Text ID Select the appropriate text ID.

Example: 3010


Result

Based on the entries in this table, texts are transmitted to the mobile device and displayedupon request by the driver.



(C) SAP AG 316

Transportation Planning Configuration

The transportation planning component of SAP Direct Store Delivery schedules tours that runon predefined routes to organize all planned deliveries into shipments.

In the DSD mobile scenario Order-to-Cash, orders are taken by the preseller on the mobiledevice, uploaded into the back end, and converted into SAP ERP sales documents during theFinal Settlement Run. Depending on the Customizing settings for the order type used, thesystem may immediately create deliveries as well. For these deliveries, the system uses thenext possible delivery date according to the visit plan and valid visit list for the customer inquestion. Furthermore, the system also determines the route when creating the delivery sincethis is one of the criteria for organizing deliveries into shipments later on.

Dynamic transportation planning is an important feature of the transportation planningcomponent. Its functions enable you to create shipments with shipping-relevant deliveries that

have the same delivery date, the same visit plan type, the same route, and the sametransportation planning point. Additionally, vehicles and drivers are assigned automatically tothe shipment.

Process

To use the SAP Direct Store Delivery transportation planning functions, you must perform thefollowing steps:

1. Route Definition [Page 317]

2. Route Determination Definition [Page 323]

3. Maintain Transportation Relevance [Page 335]

4. Define Shipment Types [Page 336]

5. Define Transportation Planning Point [Page 337]

6. Determine Allowed Delivery Types for Dynamic Transportation Plan [Page 339]

7. Determine Capacity Limits for Dynamic Transportation Planning [Page 340]

8. Loading Unit Configuration [Page 342]



(C) SAP AG 317

Route Definition

A route is a link between the departure point and the destination point. It describes the path

from the depot (point of departure) via all ship-to parties of the specific tour back to the depot(point of destination). It comprises the maximum distance that a shipment covers during thetour.

The route is used as a criterion to select deliveries for a shipment and is a control parameterfor shipments.

A route may consist of several stages and it may also consist of several tours. The routecontains numerous details that are of relevance to the shipment (for example, assignedshipping type, mode-of-transport regarding foreign trade, or route-specific restrictions such asallowed total weight for a shipment).

Each shipment always has only one route that is contained as information in the shipment

header. The route can be copied from the deliveries selected for the shipment or can beentered manually.

Process

This process contains the following Customizing settings:

1. Define Modes of Transport [Page 318]

2. Define Shipping Types [Page 319]

3. Define Routes and Stages [Page 320]



(C) SAP AG 318

Define Modes of Transport

In this IMG activity, you define modes of transport that are relevant for your business (for

example, by road, by air, or by sea).

Procedure

1. In Customizing for Logistics Execution under Transportation Basic Transportation

Functions Routes Define Routes , choose Define Modes of Transport .



FieldName


ShTy Enter an alphanumeric key up to two digits.

Example: M1

Description Enter a text description for the mode of transport being defined.

Example: ROAD

SType

Entry is optional.

You may choose a mode of transport type from the input help (if defined). Themode of transport type serves for classifying modes of transport in dangerousgoods management.

Description This will be entered automatically by choosing Enter , depending upon the entryin the Stype field.

4. Choose Enter .

Repeat step 3. and 4. to maintain additional types of modes of transport.


Result

Modes of transport have been defined and are now available for use in defining shippingtypes.



(C) SAP AG 319

Define Shipping Types

In this IMG activity, you define the type of shipping (for example, truck or freight train) that is

used to transport the goods on a particular leg of a route.

Prerequisites

Modes of transport are defined.

Procedure


Functions Routes Define Routes , choose Define Shipping Types.



FieldName


PT Specify a two digit key.

Example: M1

Description Enter a text description for the shipping type being defined.

Example: TRUCK

MdTr Assign an appropriate mode-of-transport from the input help.

Example: M1

Description

This will be displayed automatically depending on the mode-of-transportchosen.

Example: ROAD

STPG No entry.

4. Choose Enter .

Repeat step 3. and 4. to maintain additional shipping types.


Result

Shipping types have been defined and are now available for use in route definition.



(C) SAP AG 320

Define Routes and Stages

In this IMG activity, you define the routes relevant for your business.

Procedure


Functions Routes Define Routes , choose Define Routes and Stages.




Route Enter an alphanumeric key of maximum 6 characters.

Example: DSD001

Identification

Description Enter a text description for the route to be defined.

Example: COASTAL ROUTE 01

Route ID

No entry (optional).

This additional route ID can be used, for example, to specify the routing

number for a railway route.

Processing

Service Agent


If the shipment is to be carried out by a transportation service agent,you may specify it here.

ModeofTr-Border


Entries in this field identify the mode of transport (for example, rail) bywhich the goods cross a border during export or import. This

information is required for the declaration of foreign trade data.

Shipping Type Select a shipping type from the input help.

Example: TRUCK

Distance


The distance of a leg in a shipment can be maintained here togetherwith the unit of measure for the distance.

ShTypePrelLeg


It is possible to maintain a shipping type used for transporting goods ina preliminary leg of a route.



(C) SAP AG 321


ShTypeSublLeg


It is possible to maintain a shipping type used for transporting goods in

a subsequent leg of a route.

Rel. Tranport


By selecting the transportation relevance checkbox, the route can beused for creating shipments. If you use routes in delivery documentsfor which transportation relevance is not maintained, these deliveriescannot be planned in shipments.

Scheduling

TransitTime

Enter a number of calendar days (with 2 decimal places) required todeliver an item from your company to the customer via a given route.

Example: 3.00

The system uses the transit time from delivery scheduling as well asother time estimates (for example, the loading time) to determine thedates by which the goods must be available for picking, packing, andloading.

Factory cal. No entry (optional).

Trav. Dur.

Enter a number of <hours:minutes> of actual travel duration

required to deliver an item from your company to the customer via agiven route.

Example: 10:30

The actual travel duration is a subset of the transit time in calendardays. The actual travel duration in hours/minutes is not used in deliveryscheduling. For delivery scheduling, the system uses only the transittime.

TransLdTm.


The system uses the transportation lead time to calculate thetransportation planning date. On the basis of this date as well as othertime estimates (for example, the time needed to deliver the goods) the

system determines the dates by which the goods must be available forpicking, packing, and loading.

Depending on the shipping point, the system uses the transportationlead time either in calendar days or in hours/minutes (if the workinghours have been maintained in the referring shipping point).

TrLeadTimeHrs No entry (optional).

Same as field TransLdTm

AlwdTotWgt No entry (optional).

DangerousGoods



(C) SAP AG 322


Take transitcountry table intoacc.



Result

Routes have been defined and are now available for use in various sales and distributiontransactions.



(C) SAP AG 323

Route Determination Definition

Route determination is part of transportation planning and optimizes the transportation

processing. During the route determination process, the system determines the mostappropriate tour for the shipment.

The process starts during order entry. Based on the order type used (for which shippingconditions must have been customized) and the materials ordered (which provide the loadinggroup and the plant from the respective material master data), the system is able to determinethe shipping point. With the ship-to party entered in the order, the system knows thetransportation zone from the respective customer master. This transportation zone, togetherwith the shipping conditions and the transportation group of the materials concerned, help thesystem to find the route according to the Customizing settings made.

Once the route is known, the system can also locate the tours that are maintained for eachroute in the tour master records. Based on the settings for the visit plan type involved and the

transportation planning point to be used, the system chooses a tour according to the toursequence maintained.

Prerequisites

To determine the route correctly, the system requires details about the following criteria:

Shipping conditions

Loading group

Plant

Transportation zone

Transportation group

Process

This process contains the following procedures:

1. Define Transportation Zones [Page 324]

2. Maintain Country and Transportation Zones for Shipping Point [Page 325]

3. Define Transportation Groups [Page 327]

4. Define Weight Groups [Page 328]

5. Define Shipping Conditions [Page 330]

6. Maintain Route Determination [Page 331]

7. Define Loading Groups [Page 334]



(C) SAP AG 324

Define Transportation Zones

In this IMG activity, you can define transportation zones according to each country depending

upon your company’s needs. Transportation zones represent regions of ship-to parties(recipients of deliveries) or regions of vendors (shippers of deliveries). You can define yourtransportation zones according, for example, to a country’s zip code system.

Procedure


Functions Routes Route Determination , choose Define Transportation Zones.




Ctry (Country)Select the country code from the input help.

Example: DE

TranspZone Enter a key with up to ten characters for the transportation zone.

Example: DSD0000001

Description Enter a description for the new transportation zone.

Example: COASTAL REGION

4. Choose Enter .

Repeat steps 3. and 4. to maintain additional transportation zones.


Ensure that the respective transportation zone is entered in customer master records.

Result

Transportation zones are now defined and are available for use in the master data records ofship-to parties and vendors.

Using the transportation zone of the ship-to party as well as the shipping conditions and thetransportation group of the materials, the system automatically suggests a suitable routeduring sales order and outbound delivery processing.



(C) SAP AG 325

Maintain Country and Transportation Zones forShipping Point

In this IMG activity, you assign countries and transportation zones that you defined in aprevious step for each shipping point. It is essential to assign a shipping point to a departurecountry and departure zone, since this information is critical for selecting deliveries. Theshipping point is located in the departure country.

You only can assign one transportation zone per shipping point. However, you can assign thesame transportation zone to more than one shipping point.

Prerequisites

Shipping points are defined (example: Z001).

Transportation zones are defined.

Procedure


Functions Routes Route Determination , choose Maintain Country andTransportation Zone for Shipping Point .

2. In the Customizing table that appears, select Change mode, if necessary.



ShPt Locate the shipping point you wish to assign a transportation zone to.

Example: Z001

Description Is automatically displayed.

Ctry Enter the desired country code.

Example: DE

Name Is automatically displayed depending on the chosen country code.

Example: GERMANY

Zone Enter a description for the new transportation zone.

Example: DSD0000001

Description Is automatically displayed depending on the transportation zone chosen.





(C) SAP AG 326

Result

The transportation zone is a criterion in customer master data records. During transportationplanning, the system needs to know which shipping point to use when selecting customerdeliveries to create a shipment. This aspect of the route determination process is supportedby having linked transportation zone and shipping points.



(C) SAP AG 328

Define Weight Groups

Route determination is carried out in the sales order. When creating the delivery, you can

have the system carry out route determination again. In addition to the criteria for routedetermination contained in the order item (destination country, departure country,transportation zone, shipping conditions, and transportation group), the system also takes theweight of the delivery items into account.

In this Customizing table, you can predefine weight groups to suit your own business. Youspecify the maximum weight allowed for each group (for example, up to 10 tons). Duringdelivery processing, the system uses the weight group as additional information for automaticroute determination. If a route was proposed during sales order processing, weightinformation available at shipping time may result in the system proposing a new, moresuitable route.

Procedure1. In Customizing for Logistics Execution under Transportation Basic Transportation

Functions Routes Route Determination , choose Define Weight Groups.

On the screen that appears, select the option Maintain Weight Groups in the leftscreen window.



FieldName


WeightGroup

Enter a key with up to four characters for each weight group to be defined.Since this key specifies a group according to weight, you should use keys thatindicate up to what weight this weight group should apply.

Example: 0200 (for weight groups up to 200 kg)

Description Enter a description for the new weight group.

Example: UP TO 200 KG

4. Choose Enter .

Repeat steps 3. and 4. to maintain additional weight groups.

Highlight one of the new entries and choose Maintain Details for Weight Groups inthe left window.


6. Enter the following data in the right window:

FieldName


Totalweight

Enter a number for the total gross weight of all items in the delivery.

The system calculates the gross weight for each item by multiplying the



(C) SAP AG 329

FieldName


delivery quantity by the gross weight per sales unit from the sales order. Ifthere is no related sales order, the system uses the gross weight from thematerial master record.

Example: 500

Unit Enter the unit of measure defined for the weight group.

Example: KG

Seq

Enter a sequential number with up to three digits.

When maintaining weight groups, the sequential number is used to identify thedata record uniquely in the database. You always maintain this field manually.It is irrelevant whether or not the content of the field is given in ascending orderfor each weight unit. You should simply ensure that you enter a value wherethere was previously no entry for the relevant weight unit.

Example: 4

WgtGr Select the respective weight group from the input help.

Example: 0200

Description

Is automatically displayed depending on the weight group chosen.



Result

Weight groups are now defined and can be used within Customizing settings regarding routedetermination.



(C) SAP AG 330

Define Shipping Conditions

In this IMG activity, you define shipping conditions. Shipping conditions are entered in each

customer master record on the Shipping tab in the sales area data for each sales area. Thesystem copies the shipping conditions into the sales document header.

Without shipping conditions, the system cannot carry out the determination of the shippingpoint. The shipping point, however, is a requirement for creating a delivery.

If your company does not distinguish between different shipping conditions, then it is sufficientto work with just one shipping condition, for example, 01 = Standard, which then is specifiedin all customer master records.

Prerequisites

Customer master records contain shipping conditions.

Procedure

1. In Customizing for Logistics Execution under Shipping Basic Shipping Functions

Shipping Point and Goods Receiving Point Determination , choose Define ShippingConditions.



FieldName


SC

Enter an alphanumeric, two digit key for each data record of shippingconditions.

Example: M1

Description Enter a description for the new shipping conditions.

Example: STANDARD

Choose Enter .

Repeat steps 3. and 4. to maintain additional shipping conditions, if needed.


Ensure that the shipping conditions are entered in the customer master records.

Result

Shipping conditions are now defined and are available for use in master data records of ship-to parties and vendors.



(C) SAP AG 331

Maintain Route Determination

In this IMG activity, you control the route determination per country of departure/departure

zone and country of destination/receiving zone in the sales order or in the outbound delivery.Departure zone and receiving zone are transportation zones defined for specified countries.

In the sales order, the route determination depends on the following factors:

Country of departure/departure zone

Country of destination/receiving zone

Shipping conditions

Transportation group.

You can maintain a proposed route to enable route determination with every combination ofthe above criteria. These criteria and the weight group are relevant for the delivery routedetermination.

Prerequisites

You have defined the following:

Transportation zones for selected countries

Routes

Shipping conditions

Transportation groups

Weight groups

Procedure


Functions Routes Route Determination , choose Maintain Route Determination.



FieldName


CDep Select the desired country code from the input help.

Example: DE

Name Is entered automatically depending on the country code chosen.

Example: GERMANY

DepZ

Select the desired departure zone (= transportation zone) from the input help.

Example: DSD0000001



(C) SAP AG 332

FieldName


Description Is entered automatically depending on the departure zone chosen.


DstC Select the desired country code from the input help.

Example: DE

Name Is entered automatically depending on the country code chosen.

Example: GERMANY

RecZ Select the desired destination zone (= transportation zone) from the input help.

Example: DSD0000001

Description Is entered automatically depending on the destination zone chosen.


4. Select Enter .


To set the route determination in the order, select your new entry and choose RouteDetermination without Weight Group (Order).




SC Select the desired shipping conditions from the input help.

Example: M1

Description Is entered automatically depending on the country code chosen.

Example: STANDARD

TGroup Select the desired transportation group from the input help.

Example: M001

Description Is entered automatically depending on the transportation group chosen.

Example: ON PALLETS

Proposed route Select the desired route from the input help.

Example: DSD001

Description

Is entered automatically depending on the route chosen.




(C) SAP AG 333


To set the route determination in the delivery, select the new entry and choose RouteDetermination with Weight Group (Delivery).




SC Select the desired shipping conditions from the input help.

Example: M1

Description Entered automatically depending on the country code chosen.

Example: STANDARD

TGroup Select the desired transportation group from the input help.

Example: M001

Description Entered automatically depending on the transportation selected group.

Example: ON PALLETS

WgtGr Select the desired weight group from the input help.

Example: 0200

Description

Entered automatically depending on the weight group chosen.


Actual route Select the desired route from the input help.

Example: DSD001

Description Entered automatically depending on the route chosen.



Repeat steps 3. to 11. for each combination of departure country/departure zone anddestination country/receiving zone.

Result

Route Determination is maintained and takes effect during sales order and outbound deliveryprocessing.



(C) SAP AG 334

Define Loading Groups

In this IMG activity, you define the loading groups that must be entered in each material

master record on the Sales: General/Plant tab for each plant.

The system can carry out the shipping point determination only when a loading group isdefined in the material master record. The system determines the shipping point based on thefollowing criteria:

Shipping conditions of the customer

Loading group of the materials

Plant of the materials

Procedure

1. In Customizing for Logistics Execution under Shipping Basic Shipping Functions

Shipping Point and Goods Receiving Point Determination , choose Define LoadingGroups.



FieldName


LGrp

Enter an alphanumeric key with up to 4 digits for each loading group to be

defined.

Example: FORK

Description Enter a description for the new loading group.

Example: FORK-LIFT

4. Select Enter .

Repeat steps 3. and 4. to maintain additional loading groups.


Ensure that the loading group is entered in the material master records.

Result

Loading groups are defined and available for use in master data records.



(C) SAP AG 335

Maintain Transportation Relevance

In this IMG activity, you define the transportation relevance of delivery types, delivery item

categories, and routes.

Delivery types and delivery item categories for which transportation processing is to becarried out must be characterized as relevant for transportation. All routes that are to be usedfor the shipment must also be set as relevant for transportation.

Prerequisites

Delivery types (including delivery item categories) are defined.

Routes are defined.

Procedure1. In Customizing for Logistics Execution under Transportation Shipments , choose

Maintain Transportation Relevance.

2. In the dialog box, choose Maintain Transportation Relevance for Delivery Types.

On the screen that appears, locate all delivery types that are relevant fortransportation and select the checkbox in the Rel. Transport column.


4. Choose Back .

In the dialog box, choose Maintain Transportation Relevance for Delivery Item Types. In the screen that appears, locate all delivery item categories that are relevant fortransportation and select the respective checkbox in the Rel. Transport column.


Choose Back .

In the dialog box, choose Maintain Transportation Relevance for Routes.

In the screen that appears, locate all routes that are relevant for transportation andselect the respective checkbox in the Rel. Transport column.


Result

All delivery types, delivery item categories, and routes that are indicated as relevant fortransportation can now be considered during transportation planning.



(C) SAP AG 336

Define Shipment Types

In this IMG activity, you define the shipment types that contain all essential control features

for the shipment document. Examples of essential control elements of the shipment type areas follows:

Number ranges

Partner, output, and text determination procedures

Various default values

The shipment types represent the various forms of transportation processing in sales anddistribution.

The shipment type is a mandatory input when creating shipments (either manually or via

dynamic transportation planning).

The following forms of transportation processing exist:

In an individual shipment, one or more deliveries are transported by a single transportmode from one point of departure to another final destination.

In a collective shipment, one or more deliveries are transported by a single transportmode from one or more points of departure to one or more final destinations.

In a multimodal shipment, deliveries are transported by several transport modesbetween one or more points of departure and one or more final destinations.

Procedure1. In Customizing for Logistics Execution under Transportation Shipments , choose

Define Shipment Types.

In the table that appears, select the entry with the key 0001 Indiv.Shipmt-Road .

2. Choose Copy as (F6).

On the detail screen that appears, replace the alphanumeric key 0001 with your own

key with up to four digits (an example is M001). You may also adjust the text

description or leave the description as it is.

Leave all the default values from the copied data record unchanged.

3. Choose Enter .


Result

With the shipment types maintained, one important input is now available for creatingshipments. Another necessary input to enable shipment creation is the transportationplanning point (see Define Transportation Planning Point [Page 337]).



(C) SAP AG 337

Define Transportation Planning Point

In this IMG activity, you define transportation planning points. A transportation planning point

represents a group of people responsible for handling transportation activities such asorganizing shipments with special features, for example, by train or by ship. A company codeis assigned to every transportation planning point. This is used to calculate and bill shippingcosts. Otherwise, the transportation planning point is independent of other organizationalunits.

The transportation planning point is a mandatory input when creating shipments (eithermanually or via the dynamic transportation planning). Every shipment has exactly onetransportation planning point responsible for it.

Prerequisites

A company code is defined.

Procedure

1. In Customizing for Enterprise Structure under Definition Logistics Execution ,choose Maintain Transportation Planning Point .



FieldName


TPPt

Enter an alphanumeric key with up to 4 characters for each transportationplanning point to be defined.

Example: M001

Description Enter a description for the new transportation planning point.

Example: TPP-COASTAL 01

CoCd Select a company code from the input help.

Example: 0001

4. Choose Enter .

In the dialog box, maintain the mandatory fields as well as the additional fields suchas title, name, street, and address of the transportation planning point.

If the screen does not open automatically, you can also choose Address to maintainthe settings.

5. Choose Enter .

Repeat steps 3. through 5. to maintain additional transportation planning points.




(C) SAP AG 338

Result

With the transportation planning point maintained, an important input is now available tocreate shipments. Another input necessary to enable shipment creation is the shipment type(see Define Shipment Types [Page 336]).



(C) SAP AG 339

Determine Allowed Delivery Types for DynamicTransportation Planning

In this IMG activity, you indicate which delivery types are permitted for the system to useduring dynamic transportation planning. If you have defined delivery types, you need to enterthem here in order for the system to take them into account for the dynamic transportationplanning.

Additionally, you specify the transportation planning points allowed for dynamic transportationplanning.

Prerequisites

You have defined transportation planning points.

You have defined delivery types.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery

Transportation Planning , choose Determine Allowed Delivery Types.




TrspPlanPt Select a transportation planning point from the input help.

Example: M001

Deliv. Type Select a delivery type from the input help.

Example: ZLF

Combi Flag

Do not select the checkbox (recommended).

If you select the Combi Flag checkbox, deliveries are only executed duringdynamic transportation planning if at least one other shipment is pending forthe same ship-to party. The Combi Flag must not be selected for this

additional delivery type, but it must also be allowed for dynamic transportationplanning.

4. Choose Enter .

Repeat steps 3. and 4. to maintain additional delivery types for the same or othertransportation planning points.


Result

The delivery types maintained in this table can now be used by the transportation planning

component for the dynamic transportation planning.



(C) SAP AG 340

Determine Capacity Limits for DynamicTransportation Planning

In this IMG activity, you can activate different capacity criteria and specify a percentagetolerance for each capacity limit. It is necessary to maintain this information for eachtransportation planning point. The settings made here are used during dynamic transportationplanning.

Capacity limits that can be configured comprise the following points:

Usable load of the vehicle

Volume of the vehicle

Number of stops allowed (as maintained in the tour header)

Duration of tour in terms of time (as maintained in the tour header)

Capacity limit of the vehicle

Loading units limit

Procedure


Transportation Planning , choose Determine Capacity Limits.




TransportPlanPt Select a transportation planning point from the input help.

Example: M001

Capacity Limits: DynamicTransportation Planning

You must select at least

one checkbox to maintainthe entry.

Load Limit

Select this checkbox if you want the system to consider thePAYLOAD LIMIT of the vehicle used during the dynamicdisposition run (maintained in the vehicle master).

If you select this checkbox, you may also enter a tolerancethreshold up to which the system may exceed the given limit.

Volume Limit

Select this checkbox if you want the system to consider theVOLUME LIMIT of the vehicle used during the dynamicdisposition run (maintained in the vehicle master).

If you select this checkbox, you may also enter a tolerancethreshold up to which the system may exceed the entered



(C) SAP AG 341


limit.

Stop Limit

Select this checkbox if you want the system to consider theMAXIMUM NUMBER OF STOPS for a specific tour during thedynamic disposition run (maintained in the tour header of tourmaster data).

If you select this checkbox, you may also enter a tolerancethreshold up to which the system may exceed the enteredlimit.

Cap. Limit

Select this checkbox if you want the system to consider duringthe dynamic disposition run the CAPACITY LIMIT of thevehicle used (maintained in the vehicle master).

If you select this checkbox, you may also enter a tolerancethreshold up to which the system may exceed the entered

limit.

Time Limit

Select this checkbox if you want the system to consider duringthe dynamic disposition run the MAXIMUM DURATION OFTIME a specific tour may last (maintained in the tour header oftour master data).


Load.Unit Limit

Select this checkbox if you want the system to consider duringthe dynamic disposition run the MAXIMUM NUMBER OFLOADING UNITS allowed for a specific vehicle.


4. Choose Enter and save your entries.

5. Choose Back and repeat steps 3. and 4. to maintain capacity limits for additionaltransportation planning points.


Result

The activated capacity criteria are taken into account during dynamic transportation planningfor all those transportation planning points that are maintained in this table.



(C) SAP AG 342

Loading Unit Configuration

Loading units can be used in connection with the DSD Transportation Planning component.

During the order-delivery-shipment processing, the system provides an estimate of the loadspace required on a truck based on the orders/deliveries for a specific shipment. The systemthus helps the dispatcher to optimize shipment loading. Loading units can also be used as acapacity criterion for dynamic transportation planning.

The loading unit (LDU) is a non-dimensional unit. The following are some examples of loadingunits:

Fork lift load

The quantity of material that a fork lift can pick up and load on the truck in one lift.This one-lift load can be defined as 1 LDU.

Container capacity

A loading unit can be defined for a specific quantity of material that can be loaded intoone container (for example, 1000 cans form 1 LDU which equals 1 container).

Pallet slots on the truck

A specific quantity of kegs equal 1 LDU.

In order to use loading units, you need to maintain the necessary Customizing settings (asdescribed in this section) and to maintain the application settings in the material master andthe vehicle master data records. In the material master, you maintain the alternative units ofmeasure Additional Data, Units of Measure tab and the loading unit group using the DSD-

Totals tab. In the vehicle master, you maintain the maximum number of loading units allowedfor the specified truck using the DSD Vehicle Data tab.

Once all the Customizing settings and application entries for loading units have beenmaintained, a dialog box can be induced during the order and delivery processing to displaythe calculated loading units. In the order entry screen, you may either use the Loading Unitsand Aggregated Quantities button or choose from a menu selection. During delivery, theloading units are displayed automatically after saving. The loading unit quantity is then copiedinto the shipment document. In the shipment document, you can display the maximumnumber of loading units in a separate window (maintained in the vehicle master) compared tothe calculated loading units.

Process

The steps for this process are located in Customizing for Logistics Execution under SAP

Direct Store Delivery Transportation Planning Loading Units.

This section deals with the following Customizing settings:

1. Check Units of Measurement [Page 344]

2. Define Permissible Document Types for Order [Page 346]

3. Define Permissible Document Types for Delivery [Page 347]

4. Define Units of Measure and Tolerances [Page 348]

5. Set Unit of Measure Divisor for Loading Units [Page 349]

6. Define Table for LU Groups for Material Master [Page 351]



(C) SAP AG 343

If you wish to use the loading unit capacity as a criterion in dynamic transportation planning,make sure that you select the Loading Unit checkbox in the /DSD/RP_LMT_V table (seeDetermine Capacity Limits for Dynamic Transportation Planning [Page 340]) after you havecompleted all the configuration details for loading unit calculation.



(C) SAP AG 344

Check Units of Measurement

In this IMG activity, you can define a unit of measurement that you wish to use for the loading

units (for example, LDU). However, it may be sufficient to use an already existing unit ofmeasurement if this fits your business. For example, there might already be a standardsetting that can be used as a unit of measure for loading units such as PAL (for pallets).

If you need to create a new unit of measurement, follow the procedure below. The loadingunit needs to be created as a non-dimensional unit of measure.

Procedure


Transportation Planning Loading Units , choose Check Units of Measurements.

2. Choose Units of Measurements.

Make sure that the adjacent field contains the non-dimensional entry.

3. Choose Create.



Int.Meas.unit

Enter an alphanumeric key with up to 3 characters as a unit ofmeasure for the loading units.

Example: LDU

Display

Commercial

Enter a 3 character key as a commercial measurement unit format forthe loading units.

Example: LDU

Technical

Enter a 3 character key as a technical measurement unit format forthe loading units.

Example: LDU

Measurement UnitText

Long text Enter a description for the loading unit (long version).

Example: LOADING UNIT

Short text Enter a description for the loading unit (short form).

Example: LOAD U

Leave all the remaining fields at default values.




(C) SAP AG 345

Result

With the unit of measure for the loading unit maintained (newly created or chosen from the listof standard units of measurements), a basic input is available to be used in furtherCustomizing settings (see Define Units of Measure and Tolerances [Page 348]).



(C) SAP AG 346

Define Permissible Document Types for Order

In this IMG activity, you enter the combinations of sales area or sales document types for

which you want to enable loading unit determination.

Prerequisites

Sales area data (sales organization, distribution channel, division) is defined.

Sales document types are defined.

Procedure


Transportation Planning Loading Units , choose Permissible Document Types –

Order .




SOrg Select a sales organization from the input help.

Example: 0001

DChl

Select a distribution channel from the input help.

Example: 01

Dv Select a division from the input help.

Example: 01

SaTy Select a sales document type from the input help.

Example: ZTA

Repeat step 3. if you want to maintain additional sales area or sales document typecombinations.


Result

When using one of the sales document types maintained in this table for order entry, thesystem can calculate loading units. In the order entry screen, you may either use the LoadingUnits and Aggregated Quantities button or choose from the corresponding menu option onthe GoTo – Loading Units and Aggregated Quantities menu path to have the system displaythe calculated loading units.



(C) SAP AG 347

Define Permissible Document Types for Delivery

In this IMG activity, you enter the combinations for sales organizations, shipping points, and

delivery types for which you want to enable the calculation of loading units.

Prerequisites

At least one sales organization is defined.

At least one shipping point is defined.

Delivery types are defined.

Procedure


Transportation Planning Loading Units , choose Permissible Document Types – Delivery .




SOrg Select a sales organization from the input help.

Example: 0001

ShPt Select a shipping point from the input help.

Example: Z001

DlvTy Select a delivery type from the input help.

Example: ZLF

Repeat step 3. if you want to maintain additional combinations of sales area, shippingpoint, and delivery types.


Result

After saving, the system automatically displays a dialog box that shows the calculated loadingunits when using one of the delivery types maintained in this table.



(C) SAP AG 348

Define Units of Measure and Tolerances

In this IMG activity, you enter a unit of measure in this Customizing table that defines the unit

of measurement that is used for the loading unit calculation per specified sales organization.The tolerance limit as a percentage indicates by how much the loading capacity of theassigned vehicles for a shipment can be exceeded.

Prerequisites


A unit of measurement for the loading unit is defined.

Procedure


Transportation Planning Loading Units , choose Units of Measure andTolerances.



FieldName


SalesOrg

Select a sales organization from input help.

Example: 0001

LU Select a unit of measure for the loading unit from the input help.

Example: LDU

Tol.Limit

Enter a number up to two digits for the tolerance limit (in percentage). Thetolerance limit indicates by how much the loading capacity of the assignedvehicles for a shipment may be exceeded.

Repeat step 3. if you wish to maintain entries for additional sales organizations.


Make sure that the unit of measure for the loading unit as defined in this table is maintainedas alternative unit of measure in the material master data records concerned ( Additional Data button, Units of Measure tab).

Result

A unit of measure for the loading unit has now been assigned to a sales organization. Assoon as this unit of measure is entered in the material master as an alternative unit ofmeasure, the respective material can be converted into the loading unit. Alternatively, it canbe converted directly using the sales unit of measure in the document.



(C) SAP AG 349

Set Unit of Measure Divisor for Loading Units

The unit of measure of each document item is compared with the entries made in the UoM

column in this Customizing table. If the system finds a matching unit of measurement, thenthe quantity entered in the document represents an item loading unit. If the divisor maintainedin this Customizing table for that item is greater than 1, then the unit of measure represents afraction of an item loading unit.

When finding item loading units in a document, the system calculates the number of loadingunits per item by dividing each relevant item quantity in the document with the number(divisor) entered here in this Customizing table for the respective unit of measure.

If a conversion factor has additionally been maintained in the material master ( Additional Data button, Units of Measure tab), then this conversion factor is taken as divisor and takes priorityover the loading unit divisor. If no conversion factor is maintained, then the loading unit divisoris used for the loading unit calculation.

Prerequisites


Units of measurement are defined.

Procedure


Transportation Planning Loading Units , choose Unit of Measure Divisor forLoading Units.




Sales Org. Select a sales organization from the input help.

Example: 0001

Uom Select a unit of measurement from the input help.

Example: CRT

LU Div. Select a divisor from the input help.

Example: 10

Choose Enter .

Repeat step 3. if you want to maintain divisors for additional units of measurement.


Result

Whenever a unit of measure maintained in this table is encountered in an order/delivery itemfor which the respective order type connected to a delivery type is permitted for loading unit



(C) SAP AG 350

calculation, the system uses the respective divisor to divide the item quantity and to obtain thetotal loading units of each item.



(C) SAP AG 351

Define Table for LU Groups for Material Master

In this IMG activity, you define loading unit groups before you can use them in the material

master. Materials are assigned to loading unit groups (LU-Group) in the material master onthe DSD-Totals tab under LU-Grouping .

Materials that are assigned to the same loading unit group can be loaded by the system ontothe same pallet.

Procedure


Transportation Planning Loading Units , choose Check Table for LU Groups forMaterial Master .




LU Group

Enter an alphanumeric key with up to 3 characters for each loading unitgroup to be defined.

Example: M01

LU GroupDescription

Enter a description for the new loading unit group.

Example: MIXED PALLETT (JUICE)

Choose Enter .

IDocs from Change Pointers: Scheduling Jobs Repeat step 3. if you wish to maintainadditional loading unit groups.


Result

Loading unit groups have been defined and are now available to be assigned within materialmaster data records.



(C) SAP AG 352

Download/Data Replication Configuration

During the download process, the system transfers master data as well as transactional datafor a specific tour via Intermediate Documents (IDocs) to a middleware server. Themiddleware server then transfers this data to the individual mobile devices. The data is thenaccessible by mobile users during their tours.

The download of master data is accomplished via SAP Integration Technology ALE(Application Link Enabling). The system uses standard IDocs to download the data of thecustomer master, material master, bill of materials, open customers’ items, and driver textsettings.

The download of transactional data is managed by using SAP R/3 Standard Output Control

Process

1. Send Customer Master Data [Page 353]

2. Send Material Master Data [Page 355]

3. Distribute Material BOM Information [Page 357]

4. Send Credit Data (Open Items) [Page 359]

5. Send Driver Text Settings [Page 361]

6. Data Replication and Modification [Page 363]



(C) SAP AG 353

Send Customer Master Data

This section describes how customer master data is distributed from the DSD back end to the

DSD Connector, independent of the system structure.

Prerequisites

All settings regarding the system connections between the DSD back end and the DSDConnector are completed.

Customer master data records exist.

Procedure

1. On the SAP Easy Access screen, choose Tools ALE Master Data Distribution

Cross-Application Customer Send .



Customer In order to send one or a range of customers, enter the appropriatenumber(s) in this field. If all customers should be sent in one step, leavethe field empty.

Class No entry.

Output type DEBMAS

Logical system Logical system name of the target system, in this case, the DSDConnector.

ParallelProcessing

Server group No entry.

No. of customers per process

Choose the default value: 20

3. Execute the program.

After sending the customer master data to the DSD Connector, we recommend checking thesuccess of the data transfer. To do this, on the SAP Easy Access screen, choose Tools

ALE ALE Administration Monitoring IDoc Display Status Monitor .

Select the current date and execute the program.

Depending on settings in the outbound parameters for the message type DEBMAS in thepartner profiles (output parameters/output mode), the status should be Data passed to portOK (green light) or IDOC ready to be transferred to application (yellow light). In the latter

case, it is necessary to trigger the data transfer in another step. To do this, mark the statusline and choose Process.



(C) SAP AG 354

Result

Once this activity has been finished, the customer master data should be available in the DSDConnector database tables.



(C) SAP AG 355

Send Material Master Data

This section describes how material master data is distributed from the DSD back end to the

DSD Connector independent of the system structure.

Prerequisites


Material master data records exist.

Procedure


Cross-Application Material Send .



Material In order to send one or a range of materials, enter the appropriatenumber(s) in this field. If all materials should be sent in one step, leavethe field empty.

Class No entry.

Message type (R/3

Standard) MATMAS

Logical system Logical system name of the target system, in this case the DSDConnector.

Send material infull

No entry.

ParallelProcessing

Server Group No entry.

No. of Customers per Process

Choose the default value: 20.


After sending the material master data to the DSD Connector, we recommend checking thesuccess of the data transfer. On the SAP Easy Access screen, choose Tools ALE ALE

Administration Monitoring IDoc Display Status Monitor.


Depending upon the settings in the outbound parameters for the message type MATMAS inthe partner profiles (output parameters/output mode), the status should either be Data passedto port OK (green light) or IDoc ready to be transferred to application (yellow light). In the



(C) SAP AG 356

latter case, it is necessary to trigger the data transfer in another step. To do this, mark thestatus line and choose Process.

Result

Once this activity has been finished, the material master data should be available in the DSD

Connector database tables.



(C) SAP AG 357

Distribute Material BOM Information

This section describes how bill of material (BOM) master data is distributed from the DSD

back end to the DSD Connector, regardless of the system structure.

Prerequisites


A bill of materials is set up for the relevant materials.

Procedure


Logistics Bill of Material Material BOM Send.


Field name User Action and Default Actions

Material Enter one or a range of materials, for which a BOM should betransferred. This field is mandatory.

Plant Select a plant (optional).

BOM usage Choose BOM usage 5.

Alternative BOM Leave this field blank.

Valid from Select an appropriate validity date.

Ignore distributionlock

Leave this field blank.

Distribution

Message Type BOMMAT (this entry cannot be changed)

Output Variant CRE

Logical system Logical name of the target system, in this case, the DSD Connector.


After sending the BOM master data to the DSD Connector, we recommend checking thesuccess of the data transfer. To do so, on the SAP Easy Access screen, choose Tools

ALE ALE Administration Monitoring IDoc Display Status Monitor .


Depending on the settings in the outbound parameters for the message type BOMMAT in thepartner profiles (output parameters/output mode), the status should either be Data passed to

port OK (green light) or IDOC ready to be transferred to application (yellow light). If thesecond status applies, you must trigger the data transfer in another step. To do this, selectthe status line and choose Process.



(C) SAP AG 358

Result

Once this activity has been finished, the BOM master data should be available in the DSDConnector database tables.



(C) SAP AG 359

Send Credit Data (Open Items)

This section describes how credit data (open items) is distributed from the DSD back end to

the DSD Connector. By executing this program, Accounts Receivable (A/R) summary data iscreated within a control area per credit account.

For a given customer, this A/R summary data can be created and is transferred via ALEDistribution (IDoc CRESTA) from central Financial Accounting (FI) to decentralized Sales andDistribution (SD), provided all the prerequisites have been met.

Prerequisites

All settings regarding the system connections between the DSD back end and theDSD Connector are completed.

Preparatory settings for credit management must have been maintained in

Customizing. For example, credit control area(s) and risk categories must have beendefined.

The customer has been created in at least one company of the corresponding creditcontrol area.

The credit management customer master table contains credit control area data forthe customer.

Procedure

1. On the SAP Easy Access screen, choose Logistics Logistics Execution Direct

Store Delivery Handheld Connection Download Send Credit Data (Open Items).



Customer In order to send one or a range of credit data, enter the appropriate numberof customer(s) in this field. If all credit data should be sent in one step, leavethe field empty.

Credit controlarea

Select the corresponding credit control area from the input help.

Creationparameters

Current payeronly

If you select this checkbox, the A/R summary data is created from the dataof the current payer only.

All payers If you select this checkbox, the A/R summary data is created for everypayer.

All (expectcurrent payers)

If you select this checkbox, the A/R summary data is created for everypayer (except the current payer).

Permitted ageThe program compares the current date and time with the timing of the last

A/R summary. If the time elapsed since then is greater (in days and hours)



(C) SAP AG 360


in days than the permitted aging in days and hours, the program generates a new A/R summary. If you do not specify a permitted aging in days and hours, thesystem determines a new A/R summary anyway.

Permitted agein hours

The program compares the current date and time with the timing of the last A/R summary. If the time elapsed since then is greater (in days and hours)than the permitted aging in days and hours, the program generates a new

A/R summary. If you do not specify a permitted aging in days and hours, thesystem determines a new A/R summary anyway.

ALEDistributionParameters

Current payeronly

If you select this checkbox, only the results arrived at during the creation ofthe A/R summary together with the data from the current payers in the

credit customer are sent via ALE.

All payers If you select this checkbox, only the results arrived at during the creation ofthe A/R summary together with the data from all the payers in the creditcustomer are sent via ALE.

All (expectcurrent payers)

If you select this checkbox, only the results arrived at during creation of the A/R summary with the data from all the payers (except the current payer) inthe credit customer are sent via ALE.

No ALEdistribution

If you select this checkbox, only those results arising from the A/R summarydata created from the data relating to all payers of the credit customer(except the current payer) are sent by ALE.

Number ofcustomers

This parameter indicates the maximum number of A/R summaries to betransferred per call.


After sending the credit data to the DSD Connector, we recommend checking the success ofthe data transfer. To do this, on the SAP Easy Access screen, choose Tools ALE ALE

Administration Monitoring IDoc Display Status Monitor .

Select for the current date and the message type CRESTA.

Execute the program.

Depending on settings in the outbound parameters for the message type CRESTA in thepartner profiles (output parameters/output mode), the status should either be Data passed to port OK (green light) or IDOC ready to be transferred to application (yellow light). In the lattercase, it is necessary to trigger the data transfer in another step. To do this, mark the statusline and choose Process.

Result

Once this activity has been finished, the credit data (open items) is available in the DSDConnector database tables.



(C) SAP AG 361

Send Driver Text Settings

This section describes how driver text settings are distributed from the DSD back end to the

DSD Connector. The driver text settings are maintained in Customizing table /DSD/HH_DRVTXT . The texts are distributed by message type DESADV , ORDERSP orSHPMNT .

Prerequisites


Procedure

1. On the SAP Easy Access screen, choose Logistics Logistics Execution Direct

Store Delivery Handheld Connection Download Send Driver Text Settings .



Shipment type Depends on the settings in table /DSD/HH_DRVTXT .

Transportation planning point

Depends on the settings in table /DSD/HH_DRVTXT .

Message Type Depends on the settings in table /DSD/HH_DRVTXT .

Example: DESADV

Text object Depends on the settings in table /DSD/HH_DRVTXT .

Example: VTTK

Text ID Depends on the settings in table /DSD/HH_DRVTXT .

Message type /DSD/HH_TXTDRV

Logical system The logical name of the target system, in this case, the DSDConnector.

Processing Size

Number of objects perIDoc

Choose the default value: 200


After sending the data to the DSD Connector, we recommend checking the successof the data transfer. On the SAP Easy Access screen, choose Tools ALE ALE

Administration Monitoring IDoc Display Status Monitor.


Depending on settings in the outbound parameters for the message type /DSD/HH_TXTDRV in the partner profiles (output parameters/output mode), the



(C) SAP AG 362

status should either be Data passed to port OK (green light) or IDoc ready to betransferred to application (yellow light). In the latter case, it is necessary to trigger thedata transfer in another step. To do this, select the status line and choose Process.

Result

The system transfers the selected driver texts to the individual mobile devices.



(C) SAP AG 363

Data Replication and Modification

Downloaded data consists of master data and transactional data. Transactional data such asvisit list and shipment data is downloaded each time a visit list is generated or a shipment issaved. Master data, however, is initially sent to the middleware and remains unchangedunless you activate the change pointers for selected message types.

With activated change pointers, any changes made to master data (customer master, materialmaster, or bills of material) are recorded in change documents. Depending on the parametersof scheduled jobs for specified variants of message types, the system generates IDocs inbackground processing from these change documents and downloads the changed masterdata to the middleware.

To do this, you must define number range intervals and activate the change pointer creation.

Process1. Activate Change Pointers - Generally [Page 364]

2. Activate Change Pointers for Message Types [Page 365]

3. Generate IDocs from Change Pointers: Defining Variants [Page 366]

4. Generate IDocs from Change Pointers: Scheduling Jobs [Page 367]

5. Schedule Jobs for Collected IDocs [Page 369]

Result

Once all the steps of the above process have been completed, newly created master dataand changes to master data are recorded in change documents, which are read by a report togenerate new IDocs.



(C) SAP AG 364

Activate Change Pointers - Generally

If you want to use the change pointer functionality, you need activate the writing of change

pointers in the Activate Change Pointers Generally Customizing table.

Procedure


Interface / Application Link Enabling (ALE) Modeling and Implementing Business

Processes Master Data Distribution Replication of Modified Data , choose Activate Change Pointers – Generally .

2. Select the checkbox for Change pointers activated – Generally .




(C) SAP AG 365

Activate Change Pointers for Message Types

In this IMG activity, writing change pointers can be activated or deactivated for each message

type, in addition to the Change Pointers Activation in Activate Change Pointers - Generally[Page 364].

We recommend activating change pointers for the following message types:

BOMMAT

DEBMAS

MATMAS

Prerequisites

The general writing of the change pointers is activated.

Procedure


Interface / Application Link Enabling (ALE) Modelling and Implementing Business

Processes Master Data Distribution Replication of Modified Data , choose Activate Change Pointers for Message Types.

2. Choose the message types to activate (for example, BOMMAT , DEBMAS,MATMAS), and set to active.




(C) SAP AG 366

Generate IDocs from Change Pointers: DefiningVariants

In this IMG activity, you define variants for each message type that should be run by theRBDMIDOC program. This program is responsible for generating IDocs from change pointers.

The message types relevant for the DSD process are MATMAS (changes in material master),DEBMAS (changes in customer master), and BOMMAT (changes made to bills of material).

Procedure

1. In Customizing for SAP NetWeaver under Web Application Server IDoc Interface /

Application Link Enabling (ALE) Modelling and Implementing Business Processes

Master Data Distribution Replication of Modified Data Create IDocs from Change

Pointers , choose Define Variants.

2. Enter the RBDMIDOC program.

In the Sub-objects block, select the Variants radio button.

3. Choose Change.

On the screen that follows, enter a name for the variant (for example,MaterialMaster ).

4. Choose Create.

On the screen that follows, select a message type for which a variant should bemaintained (for example, MATMAS).

5. Choose Attributes.

Enter a description and save the variant.

Choose Back and repeat steps 2. through 9. for each relevant message type (forexample, MATMAS, DEBMAS, and BOMMAT ) for which a variant needs to bemaintained.



(C) SAP AG 367

Generate IDocs from Change Pointers: SchedulingJobs

In this IMG activity, you schedule jobs for each variant that has been defined (hence, for eachmessage type). The scheduled jobs trigger the system to periodically run the RBDMIDOC program. The program generates IDocs for modified master data contained in the changedocuments. In this way, master data records on the DSD Connector are updated periodically.

Procedure

1. In Customizing for Integration with other SAP Components under Advanced

Planning and Optimization Basic Settings for the Data Transfer Change Transfer

Change Transfer for Master Data Reorganize ALE Change Pointers , chooseSchedule Job.



Job name Enter a name for the job to be maintained.

Example: Update Material Master

Job class Job class refers to the priority of the job. Choose one from the input help.

Exec.server Enter the name of an SAP R/3 instance on which the background job shouldrun.

Confirm your entries. A new screen should appear, otherwise choose Steps.

On the screen that appears, choose ABAP Program.


FieldName


Name Enter the name of the program: RBDMIDOC

Variant

From the input help, choose the variant for which this current job is scheduled.

Example: MATMAS

Language Enter the desired language abbreviation.

Example: EN

Choose Check to check your input and then save your entries.

You should now be on the Define Background Job starting screen .

Choose Start Condition to define the starting time.

Choose one of the buttons (for example, Date/Time).



(C) SAP AG 368

Enter the date and time to schedule the start of job (for example, System-Date and

12:00:00 as Time).

To have this job run periodically, select the Periodic job checkbox. Choose Periodicvalues and choose one of the options offered (for example, Daily ).

Choose Check to check your input and then save your entries.

Repeat steps 2. through 3. to schedule jobs for all relevant variants.


Result

For the above mentioned example entries, the system runs the RBDMIDOC program everyday at noon for the maintained variants to generate IDocs from the change documents. TheIDocs are sent to the DSD Connector and master data records are updated.



(C) SAP AG 369

Schedule Jobs for Collected IDocs

When you download transactional data (for example, a visit list or shipment), the system

creates various IDocs, one of which is the /DSD/HH_CONTROL control IDoc . This IDoc is

always created first and contains a list of all IDoc numbers that belong to the relevant

shipment (for example, DESADV, SHPMNT, or /DSD/HH_ROUTE_ITINERARY ). The

Customizing settings for the control IDoc determine when the /DSD/HH_RSEOUT00_DELAY

program triggers the control IDoc.

The control IDoc is the only IDoc that the system sends to the receiving system. The system

does not send IDocs that contain data, such as SHPMNT, DESADV, or ORDRSP to the receiving

system. Instead, the system places these IDocs in a physical file, which you determine inCustomizing. The system receives the data from this file collectively, as determined by thecontent of the control IDoc. The system sends the control IDoc to the receiving system onlyafter all corresponding IDocs are placed in the file and are ready to be retrieved.

Prerequisites

The output mode for /DSD/HH_CONTROL is defined as Collect IDocs.

For more information, see Maintain Partner Profiles in Back End/DSD Connector [Page 36].

Procedure

1. On the SAP Easy Access screen, choose Tools CCMS Background Processing

Define Job (transaction code SM36).



Job name <Your job name>

Example: Process collected IDocs

Job class <Select a job class>

Exec.target <Leave blank>

1. To confirm your entries, choose Enter .

2. Choose ABAP program and enter the following data:


Name /DSD/HH_RSEOUT00_DELAY

Variant <Leave blank>

Language Example: EN

3. Choose Check and then save your entries.

To define the starting time, on the Define Background Job screen, choose Start Condition.



(C) SAP AG 370

To schedule the start of the job, choose Date/Time and enter the date and time (for example,

<system date> and 12:00:00).

To run this job periodically, select the Periodic job checkbox.

Choose Periodic values and then choose Other period .

In the Explicit Period Value dialog box that appears, enter the number of minutes for whichthe batch job is to run.

Choose Check and then save your entries.

Result

Once you have scheduled a job for the /DSD/HH_RSEOUT00_DELAY program, the system

identifies all control IDocs that are ready to be sent and checks whether all the correspondingtransactional IDocs are ready to be retrieved from the respective file.



(C) SAP AG 371

DSD Tour Status

The DSD business process involves multiple SAP application components. Severalcomponents are located in the back end, one in the middleware, and the DSD client is locatedon the front end. While each of these components tracks its own status, no overall tour statushas been visible in the back end until now.

The DSD tour status functions are implemented to provide this overall tour status. The DSDtour status allows the tracking of all DSD tours across all relevant applications. In this way,the system can control the behavior of an application on the basis of the status of anotherapplication or it can trigger an action when a defined status is reached. The DSD tour statusalso helps to provide an overview of DSD tours and displays the past process of selected

DSD tours (the /DSD/ST_TOUR transaction code).

All existing DSD-relevant applications are enhanced with the DSD tour status. Steps, which

are executed in the different applications and which are considered important in controllingoverall tour processing, are defined as the DSD tour status. The DSD tour status is the finalprocess step within an application, such as the “visit list created” step in the Visit Control component or the “shipment completed” step in the Transportation Planning component.Likewise, if new interfaces or new standard applications are added to the DSD process, themain status of the new application is added to the list of DSD tour statuses.

The DSD-relevance is maintained in tour status Customizing, as well as their assignment toeither a mobile or paper-based scenario. For each tour scenario, a tour profile is definedcontaining the list of tour status IDs that are considered relevant for the scenario concerned.

A tour profile can contain optional steps such as the steps for the loading confirmation orreload. A tour status ID can be attained in one of the following ways:

By a user action within the application involved

For example, by saving a shipment

By the application involved setting it automatically

For example, during the download of tour data to the mobile device

By being triggered by a function module that is assigned in the tour profile to thecorresponding tour status ID

For example, “release tour for presales processing”

DSD differentiates between delivery tours and sales tours. Each DSD tour has a unique DSD

tour ID. The DSD tour ID concatenates the document type (10 for shipment, 20 for visit list)with the number of the leading document of the respective business process.

Delivery process where the shipment is the leading document

The DSD tour ID reads 10+shipment number

Sales process where the visit list is the leading document

The DSD tour ID reads 20+visit list ID



(C) SAP AG 372

On saving a shipment or visit list, the system determines the appropriate scenario based onCustomizing settings, derives the tour execution date from the relevant shipment or visit list,and creates the corresponding DSD tour ID.

For customer enhancements within the DSD tour status function, the BAdI /DSD/BADI_ST

can be used to change tour status data in paper-based or mobile DSD scenarios.

Prerequisites

Business Function /DSD/BF must be activated to enable access to all transactions and

Customizing activities related to the tour status function.

Process Flow

The tables for this section are located in Customizing for Logistics Execution under SAP

Direct Store Delivery Tour Status and comprise the following IMG activities:

1. Define Tour Status ID [Page 373]

2. Specify Function Modules Available for Tour Status Profiles [Page 376]

3. Define Tour Scenarios and Tour Status Profiles [Page 377]

4. Delivery Process: Assign Shipment to Connected Medium [Page 383]

5. Delivery Process: Assign Shipment to Tour Scenario [Page 384]

6. Sales Process: Assigning Visit List to Connected Medium [Page 386]

7. Sales Process: Assign Visit List to Tour Scenario [Page 387]



(C) SAP AG 373

Define Tour Status ID

In this IMG activity, you maintain the DSD tour status IDs deriving from the different

applications involved in the DSD process.

The following table lists all the DSD tour status IDs that we implement and deliver:

Status ID Description No activ. W/o Cont.

101000 Visit List created

201000 Shipment – Created

202000 Shipment – Planning completed

203000 Shipment – Check-in

204000 Shipment – Loading started

205000 Loading confirmation – Initial started

205090 Loading confirmation – Initial confirmed

206000 Shipment – Loading completed

207000 Shipment – Completed

208000 Shipment – Started

301050 Connector – Download failed

301090 Connector – Download success; not assigned

302000 Connector – Download success; assigned

303000 Connector – Statistical Data Started

303050 Connector – Statistical Data Failed

303090 Connector – Statistical Data Successful

304000 Connector – Pricing waiting

304050 Connector – Pricing failed

305000 Connector – Ready for download to MW

306000 Connector – Triggered to MW

307000 Connector – Download to mobile failed

308000 Connector – Available on mobile



(C) SAP AG 374

Status ID Description No activ. W/o Cont.

401000 Reload – Started

405000 Reload – Loading confirmation started

405090 Reload – Loading confirmation confirmed

406050 Reload – Creation of Deliveries failed

406090 Reload – Creation of Deliveries success

501000 Upload started

600550 Delta Upload failed X

600590 Delta Upload successful X

601050 Upload failed

601090 Upload successful

602030 RADB partially filled X

602090 RADB filled

701000 Shipment – Finished

801000 FSR – Released for Presales Processing X

801050 FSR – Presales Processing Incomplete X

801090 FSR – Presales Processing Complete X

802000 FSR – Released for Settlement

803000 FSR – Balancing ended

804000 FSR – Settlement started

804090 FSR – Settlement completed

Each DSD tour status can trigger actions. Due to technical reasons, however, it must beavoided that certain statuses trigger an action. This is achieved by selecting the NO ACTIVITY checkbox for the respective DSD tour status, which subsequently deactivates theTriggered activity field in the tour status profile for that particular tour status ID.

Procedure

Customers may define their own tour status IDs within the restricted customer number rangeof 80000000 – 99999999. For defining a customer-specific tour status, proceed as follows:

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Tour

Status , choose Define Tour Status ID.




(C) SAP AG 375



Status ID Enter the name of the tour status ID using the customer number ranges.

Description

Enter a description for the tour status ID. The description should conform to astandard naming convention to make it easier to identify subprocesses (suchas reload). All step descriptions should begin with a subprocess or objectdescription.

Example:

o Reload – Started

The starting step for the reload subprocess

o Reload – Creation of Deliveries successful

The final step of the reload subprocess

No activ. Optional – Select the checkbox if you want to deactivate the Triggered activity field in the tour status profile.

W/o Cont. Optional - Indicates that the corresponding status has no presequence orsequence, which are used to control the strict order of the steps in the tourstatus cycle.

Table /DSD/ST_CSTATUS is cross-client.


Result

The DSD tour status IDs are maintained and ready for use during the maintenance of the tourstatus profiles. For status IDs where the No activ. checkbox is selected, the Triggered activity field in the tour status profile maintenance screen is not active.



(C) SAP AG 376

Specify Function Modules Available for TourStatus Profiles

In this IMG activity, you specify the function modules you want to allow for entry in a tourstatus profile as follow-up activities.

In the standard, we deliver the following function modules for optional maintenance in the tourstatus profile:

DSD/SV_SET_LC_EXECUTION

/DSD/SL_ASL_ACT_PRES_RELEASE

/DSD/SL_ASL_ACT_PRES_PROCESS

/DSD/SL_ASL_ACT_FSR_RELEASE

/DSD/SL_ASL_ACT_DIFF_DET

/DSD/SL_ASL_ACT_FSR_PROCESS

These function modules must be listed in this Customizing table.

Any customer-specific function modules that are developed for use with the tour status profilesettings must be maintained in this table.

Procedure

1. In Customizing for Logistics Execution under Direct Store Delivery Tour Status ,choose Function Modules available for Tour Status Profiles.




Triggered activity Enter the function module.

Short text Entered automatically depending on the function module.

Ensure that the standard function modules listed above are entered in thisCustomizing table.

Result

The function modules maintained in this Customizing table can be entered in a tour statusprofile.



(C) SAP AG 377

Define Tour Scenarios and Tour Status Profiles

In this IMG activity, you define tour scenarios and assign the required tour status IDs to them,

thus forming the tour status profile of a specific tour scenario. The tour status module alsoallows the assignment of function modules on tour status level, containing actions to beexecuted once the respective DSD tour has attained the desired tour status value.

Based on the different applications and steps that need to be processed, at least four differentstandard DSD scenarios are distinguished. SAP delivers them as standard and they comprisethe following:

MDELIV00 (Mobile – Delivery scenario)

MSALES00 (Mobile – Preseller scenario)

PDELIV00 (Paperbased – Delivery scenario)

PSALES00 (Paperbased – Preseller scenario)

Customers can define their own scenarios using the customer namespace (Y and Z ).Customers may also insert custom-defined process steps in predefined status profiles;however, it is the responsibility of the customer to adjust the dependencies inside the statusprofile.

Prerequisites

Tour status IDs must be maintained.

Procedure


Status , choose Define Tour Scenarios and Tour Status Profiles.



FieldName


Scenario

Enter a name for the customer-specific DSD tour scenario that should beprocessed.

Example: ZMDELVLC

Description Enter a description for the scenario.

Example: Mobile - Delivery w/Load.Confirm

4. Choose Enter , select the entry, and choose View for Status Profile in the left window. A table control appears in the right window.


6. In this step, you assign single status IDs to the tour scenario defined in step 3.

together with some specific attributes by entering the following data:



(C) SAP AG 378


Scenario Enter the scenario defined in step 3.

Sequence

Mandatory – Enter an ascending sequence ID (2 to 3 digits) for the scenario

step.

Example: 500

View forStatusProfile

Presequence

Optional – Enter the sequence ID of a previous status ID that must becompleted before the tour status, maintained in the current sequence, canbe set.

Example: 400

The example given (seq 400 and pre-seq 500) means that the tour musthave reached at least status 400 before status 500 can be executed.

Status ID

Enter the status ID for the current sequence. Once the tour has reached thisstatus, it is logged in the tour status log for the shipment.

Example: 205000 (= Loading Confirmation – Initial started )

Description Entered automatically depending on the status ID selected, provided it wasmaintained when defining the status ID.

History

Select this checkbox if you wish to make the status ID visible in the tour

status overview (transaction /DSD/ST_TOUR) for a DSD tour.

Regardless of whether or not this checkbox is selected, the current tourstatus is always stored in the tour status table.

No return

Some steps in the DSD process cannot be canceled automatically butrequire manual action in the relevant application.

For example, if a tour has reached tour status 801090 (FSR PresalesProcessing Complete), this means that a presales order was alreadysuccessfully created. This order creation step cannot be taken back bysimply changing the tour status but requires manual cancellation of theorder as well.

Therefore, you should select this checkbox to prevent that tour processingis rolled back beyond the status ID flagged with No Return.

Max. Seq

This field only requires an entry if the status ID of the current record is theSTARTING step of a subprocess that involves one or more subsequent tourstatus sequences. In this case, the entry required is the sequence numberof the sequence record within the given scenario that constitutes thecorresponding ENDING step of the given subprocess.

Within the DSD process, the Reload , Loading Confirmation, and PresalesProcessing functions are examples of subprocesses.

Example Loading Confirmation: The starting step is status ID 205000(Loading Confirmation – Initial started ) and the ending step is status ID



(C) SAP AG 379


205090 (Loading Confirmation – Initial confirmed ). If tour status 205000 hassequence number 500 and tour status 205090 has sequence number 600 ,the sequence number 600 must be entered in the Max Seq field to ensurethat the ending status ID of the subprocess is reached first before any

higher tour status ID can be set by the system.

Triggered Activity

In this field, a relevant function module can be maintained in all caseswhere an action should be triggered to update the database upon reachingthe relevant tour status (for example, to perform database commits or makechanges to values of objects).

The field is inactive for tour status IDs where the NO ACTIVITY checkbox is

selected in the/DSD/ST_CSTATUS table.

The Triggered Activity field exists in two views:

The first view is View for Status Profile: Only function modules that perform databaseactivities are allowed in this view. SAP delivers the following function modules foroptional maintenance in this view, depending on customer-specific requirements:

o DSD/SV_SET_LC_EXECUTION

o /DSD/SL_ASL_ACT_PRES_RELEASE

o /DSD/SL_ASL_ACT_PRES_PROCESS

o /DSD/SL_ASL_ACT_FSR_RELEASE

o /DSD/SL_ASL_ACT_DIFF_DET

o /DSD/SL_ASL_ACT_FSR_PROCESS

The second view is View for Activities in UPDATE TASK : In this view, function

modules can be entered that trigger non-database activities.

The following table lists the function modules SAP delivers for optional maintenancewithin the tour profile and provides a brief description of the action triggered by eachindividual function module as well as the recommended tour status ID at which the

function module may be entered. This list of function modules is found in Customizingfor Logistics Execution under SAP Direct Store Delivery Tour Status Function

Modules available for Tour Profiles .

TourStatus

IDFunction Module Triggered Activity

601090

/DSD/GS_DEL_STATISTICAL_DATA

Only required in processes that use the SalesHistory function.

This function module deletes theextracted statistical data fromthe back end tables, once therelevant tour has beensuccessfully uploaded into theRAD.



(C) SAP AG 380

TourStatus

IDFunction Module Triggered Activity

This is not supported for SAPDirect Store Delivery 1.0 .

204000

/DSD/SV_SET_LC_EXECUTION

Mandatory if tour status IDs for loadingconfirmation are maintained in the tour profile.

This function module checkswhether or not loadingconfirmation should beperformed in the given shipment.

A scenario must include tourstatus IDs 205000 and 205090 to allow Loading Confirmation tobe executed.

602090

/DSD/SL_ASL_ACT_PRES_RELEASE

For use in mobile scenarios only. In a paper-based scenario, the user needs to manuallyconfirm that all the tour data is entered.

This function moduleautomatically releases the tourfor presales processing, as soonas the tour data has beensuccessfully uploaded into RAD.

801000 /DSD/SL_ASL_ACT_PRES_PROCESS

This function module triggersautomatic presales processingto be executed without thenecessity to run difference

determination.

For use in all scenarios.

801090 /DSD/SL_ASL_ACT_FSR_RELEASE

This function moduleautomatically releases the tourfor settlement.


802000 /DSD/SL_ASL_ACT_DIFF_DET

This function module triggersdifference determination to startautomatically.


803000 /DSD/SL_ASL_ACT_FSR_PROCESS

This function module triggers thefinal settlement run to startautomatically.


7. Choose Enter .



(C) SAP AG 381

The following two steps are optional and only required if you wish to maintain a

function module that triggers non-database activities. If this is the case, execute steps8. through 10. Otherwise, proceed with step 11.

8. Highlight the sequence for which you want to maintain an entry and choose View to Activities in UPDATE TASK in the left window. A table control appears in the rightwindow.



FieldName


Scenario Select the scenario defined in step 3.

Example: ZMDELVLC

Status ID

Select the status ID for which you wish to maintain function module(s) thattrigger the execution of additional activities.

Example: 208000

Sequence Enter a sequential number.

Triggeredactivity

In this field, enter a function module responsible for triggering required

activities. The function module(s) entered should not contain any commands tothe database, that is, should not influence the database such as commits. Youmay maintain more than one function module for each status and scenario.

Example: DSD/SV_SET_LC_EXECUTION


12. Repeat this procedure to maintain a record for each status ID that is considered anessential part of the relevant scenario.

If you maintain status IDs that belong to a subprocess within the DSD process (suchas the reload process), you must include all optional tour status IDs for reload in thetour status profile. The following five reload tour status IDs are implemented:

o 401000 (Reload – Started)

o 405000 (Reload – Loading Confirmation Started)

o 405090 (Reload – Loading Confirmation Confirmed)

o 406050 (Reload – Creation of Deliveries failed)

o 406090 (Reload – Creation of Deliveries successful)



(C) SAP AG 382

The same is valid for all occasionally connected scenarios where some new tourstatuses have been introduced:

o 600550 (Delta Upload failed)

o 600590 (Delta Upload successful)

o 602030 (RADB partially filled)

Result

You have defined tour scenarios with assigned tour status IDs (tour status profile).



(C) SAP AG 383

Delivery Process: Assign Shipment to theConnected Medium

As soon as a shipment is saved, the system needs to decide whether the shipment is relevantfor the DSD process and if so, which DSD process should be executed – mobile or paper-based.

In this IMG activity, you maintain all valid combinations of shipment type and transportationplanning point that are relevant for a DSD process. Additionally, it is necessary to define theconnected medium (mobile or paper-based) for each combination.

Prerequisites

Shipment types must be maintained

Transportation planning point must be maintained

Procedure

1. In Customizing for Logistics Execution SAP Direct Store Delivery Tour Status ,choose Delivery Process: Assign Shipment to the Connected Medium.




ShTy Choose a shipment type from the input help.

Example: ZNEW

TPPt Choose a transportation planning point from the input help.

Example: ZNEW

Medium Choose a medium from the input help.

Example: M - Mobile


Result

Once the relevant combinations of shipment type and transportation planning point aremaintained in this Customizing table, the system can determine the DSD-relevance of theshipment and create the correct DSD tour ID for the shipment.



(C) SAP AG 384

Delivery Process: Assign Shipment to TourScenario

The shipment is the leading document for the delivery scenario (logistics-oriented businessprocess). Due to the fact that the delivery scenario can either run as a mobile or paper-basedscenario, the system needs to determine which of these two scenarios is applicable for agiven shipment. Each shipment can be assigned to only one scenario, either mobile or paper-based.

In this IMG activity, you maintain all relevant combinations between connected medium(mobile or paper-based), shipment type, and transportation planning point, and assign a DSDscenario to each of these combinations. In this way, the system can determine the exact DSDscenario to be used for a given shipment. The shipment type and transportation planningpoint can be used generically.

On saving a shipment, the system first determines the connected medium and, if successful,identifies the DSD scenario in the following order:

Select with connected medium, shipment type, and transportation planning point

Select only with connected medium and shipment type (transportation planning pointis blank)

Select only with connected medium and transportation planning point (shipment typeis blank)

Select only with connected medium (shipment type and transportation planning pointare blank)

The first successful selection determines the DSD scenario.

There should be one generic entry for each connected medium. This ensures that a shipmentwith a new shipment type or transportation planning point immediately works in the DSDprocess in a proper scenario. SAP delivers a generic entry for each of the two predefineddelivery scenarios MDELIV00 (mobile) and PDELIV00 (paper-based) with blank fields forshipment type and transportation planning point in both records.

Prerequisites

Shipment types must be defined.

Transportation planning points must be defined.

Tour scenarios with tour status profiles must be defined.

Procedure


Status , choose Delivery Process: Assign Shipment to Tour Scenario.





(C) SAP AG 385

FieldName


Medium Choose the desired medium from the input help.

Example: M - Mobile

ShTy Choose a shipment type from the input help.

Example: ZNEW


Example: ZNEW

Scenario

Choose a scenario from the input help.

Example: ZMDELVLC

Status ID

Select a tour status from the input help.

Example: 30600

The entry in the Status ID field is used by occasionally connected scenario(OCS) to determine from which status on a delta document is required.


Result

On successful determination that a shipment is relevant for DSD, the system uses the entriesmade in this table to determine which DSD scenario should be applied to the shipment. Theentry in the Status ID field is used by OCS to determine the point in time for creating deltadocuments.



(C) SAP AG 386

Sales Process: Assign Visit List to ConnectedMedium

As soon as a visit list is saved, the system needs to decide whether this visit list is relevant forthe DSD process and if so, which DSD process should be executed – mobile or paper-based.

In this IMG activity, you maintain all visit plan types that are relevant for a DSD process andassign the connected medium (mobile or paper-based) to each visit plan type.

Prerequisites

Visit plan types must be defined.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery TourStatus , choose Sales Process: Assign Visit List to the Connected Medium.




VPT Choose a preseller visit plan type from the input help.

Example: YRH


Example: M - Mobile


Result

Once the relevant visit plan type is maintained in this Customizing table, the system cancheck the DSD-relevance of the visit list and determine which medium to use for creating theDSD tour ID.



(C) SAP AG 387

Sales Process: Assign Visit List to Tour Scenario

The visit list is the leading document for the sales scenario (sales-oriented business process).

Due to the fact that the sales scenario can either run as a mobile or paper-based scenario,the system needs to determine which of these two scenarios is applicable for a given visit list.Each visit list can be assigned to only one scenario, either mobile or paper-based.

In this IMG activity, you maintain all relevant combinations between connected medium(mobile or paper-based) and visit plan type and assign a DSD scenario to each combination.In this way, the system can determine the exact DSD scenario to be used for a given visit list.The visit plan type can be used generically.

On saving a visit list, the system first determines the connected medium and, if successful,identifies the DSD scenario in the following order:

Select with connected medium and visit plan type

Select only with connected medium (visit plan type is blank)

The first successful selection determines the scenario of the tour.

There should be one generic entry for each connected medium. This ensures that a new visitlist with a new visit plan type immediately works in the DSD process in a proper scenario.SAP delivers a generic entry for each of the two predefined sales scenarios MSALES00 (mobile) and PSALES00 (paper-based), that is, the field of the visit plan type is blank in bothrecords.

Prerequisites

Visit plan types must be defined.

Tour scenarios with tour status profiles must be defined.

Procedure


Status , choose Sales Process: Assign Visit List to Tour Scenario.



FieldName



Example: M - Mobile

VPT Choose a visit plan type from the input help.

Example: YRH

Scenario Choose a scenario from the input help.

Example: ZMSALES1



(C) SAP AG 388

FieldName


Status ID

Choose a tour status from the input help.

Example: 30600

The entry in the Status ID field is used by occasionally connected scenario(OCS) to determine from which status on a delta document is required.


Result

On successful determination that a visit list is relevant for DSD, the system uses the entriesmade in this table to determine which DSD scenario should be applied to the visit list. Theentry in the Status ID field is used by OCS to determine the point in time for creating deltadocuments in a preseller scenario.



(C) SAP AG 389

Route Accounting

DSD Route Accounting is the final component within the DSD process. DSD Route Accounting starts as soon as the truck is loaded and ends with the posting of all tour-relevantactivities. During a tour, various activities can take place such as checking-out goods from thedepot, creating new orders, changing deliveries, collecting payments from customers,recording times and distances, collecting empties or sales returns, and checking-in returnedgoods to the plant. DSD route accounting handles the post-tour processing of all theseactivities including difference determination of materials or collections as well as finalsettlement.

Route Accounting is able to handle the Reload/Unload of the truck during the tour and canalso support the provision of promotions and manual discounts on the mobile device. Thereloaded/unloaded quantities, as well as the promotional deals and discounts, are consideredaccordingly during Route Settlement .

Route Accounting makes it possible to settle a tour automatically within defined tolerancesand to post differences to defined interim accounts based on difference reasons in all thosecases where differences could not be resolved before final settlement.

DSD Route Accounting may be used in mobile and non-mobile scenarios. In the case of anon-mobile scenario (also referred to as paper-based scenario), drivers record their touractivities in documents manually. This data is then manually transferred into the system.

DSD Route Accounting is an offline solution. This means that the data transfer between amobile device and the SAP ERP system takes place in the beginning and at the end of a tour.Even if there is data transferred during a tour, for example, during an Occasionally ConnectedScenario, Route Accounting is performed at the end of a tour.

Integration

Process

The Customizing tables for DSD Route Accounting are located in Customizing for Logistics

Execution under SAP Direct Store Delivery Route Accounting .

To use DSD Route Accounting, Customizing activities settings are required in the followingareas:

1. Basic Function Configuration [Page 390]

2. Route Settlement [Page 404]

3. Copying Control Enablement from Handheld Invoice to R/3 Billing [Page 456]

In addition to the Customizing activities, some master data maintenance is required in SAPEasy Access menu to enable the use of specific functionalities within Route Settlement. The

corresponding tables are located in the SAP Easy Access menu under Logistics Logistics

Execution Direct Store Delivery Route Accounting .



(C) SAP AG 390

Basic Function Configuration

The Basic Function Configuration IMG activities are located in Customizing for Logistics

Execution under SAP Direct Store Delivery Route Accounting Basic Functions .

Process


1. Application Log Configuration [Page 391]

2. Define Route Transaction Types [Page 394]

3. Define Distance Types [Page 395]

4. Define Time Types [Page 396]

5. Define Payment Methods [Page 397]

6. Define Reasons for Differences for Check-out and Check-in [Page 398]

7. Define Reasons for Changing Deliveries and Orders [Page 399]

8. Define Customer Visit Reasons [Page 400]

9. Maintain Number Range Intervals [Page 401]

10. Assign Number Range Interval [Page 403]



(C) SAP AG 391

Application Log Configuration

The settings in this section only influence the application log for the UPLOAD. The application

log of the final settlement run is not influenced.

The application log allows an object-oriented recording of events. In the current case, theapplication log provides information about the status and success of the data transfer flowingfrom the device to the DSD back end.

Process

The procedures for this process are found in Customizing for Logistics Execution under

SAP Direct Store Delivery Route Accounting Basic Functions Application Log.

To use this function, it is necessary to maintain the following Customizing tables:

1. Maintain General Settings [Page 392]

2. Maintain Treatment of Message per Object [Page 393]



(C) SAP AG 392

Maintain General Settings

In this IMG activity, you control whether or not an application log is written. You also control

the general actions of the application log (queues, waiting time, and action).

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Route

Accounting Basic Functions Application Log , choose Maintain General Settings.

2. If you want to create a new entry for a new object, choose New Entries.

3. Enter the following data for each object:

FieldName


Object Application log object name (for the DSD Route Accounting application, choosethe /DSD/RTACC object from the input help.)

WriteLog

X = application log is written

blank = application log is not written

Queues

Enter the number of attempts (for example, 5) the system has for starting a new

mode.

If errors occur during the upload of handheld data, the system may terminate the

program prematurely. In such a case, the system attempts to process theapplication log in a new mode.

WaitTime

Enter the waiting time (in seconds) between two attempts.

Action 1 (Processing Terminated)

2 (Do not write Application Log)




(C) SAP AG 393

Maintain Treatment of Message per Object

In this IMG activity, you define how the application log treats the respective message type for

each object, for example, whether or not the different message types (error message,warning, information message, and success message) are saved in the application log.

Procedure


Accounting Basic Functions Application Log , choose Maintain Treatment ofMessage per Object .

2. If you want to create a new entry for a new object, choose New Entries.



Object Application log object name (for DSD Route Accounting application, chooseobject /DSD/RTACC from the input help).

Subobject Enter the name of a subobject of the chosen application log object (choosethe subobject from the input help. For the object /DSD/RTACC, the followingfive sub-objects exist: BALANCE, CLEARING, FSR, POSTING, UPLOAD).

TerminateMessage

Blank = No / X = Yes

ErrorMessage


Warning Blank = No / X = Yes

Inf.Message


Scr.Message





(C) SAP AG 394

Define Route Transaction Types

In this IMG activity, you define the various route transaction types. The route transaction

types classify the activities that can be performed in the course of a tour.

The following transaction types have been implemented:

01 = Check-out/Check-in

02 = Tour – Distances

03 = Tour – Times

04 = Customer sales call

05 = Delivery execution

06 = Invoice printout transmission

07 = External invoice

08 = Payment handling

09 = Sales order

Procedure

The areas 9*, X*, Y*, and Z* are designed for customer-specific extensions. Customer-specific sales transaction types can be defined in these names spaces.


Accounting Basic Functions , choose Define Route Transaction Types.




Transact. Type Enter a double digit key for the transaction type to be maintained.

Example: 05

Transaction Descript. Enter the appropriate description.

Example: DELIVERY EXECUTION


The corresponding flow logic for further processing must be reprogrammed.



(C) SAP AG 395

Define Distance Types

In this IMG activity, you maintain different categories for the distance data collected in the

course of a tour.

Additionally, you can maintain whether it is a service tour is being dealt with or a customerdebit memo is created for each entry.

Distances types can be used for analysis in the SAP ERP back end.

Procedure


Accounting Basic Functions , choose Define Distance Types.




Leg Type

Specify an alphanumeric key with up to two characters for the distance typeto be defined.

Example: M1

No ServiceTour

If the trip is not an official service tour, you need to select the no service tour checkbox. The default setting for this checkbox is blank = No; this means thatas a rule every tour is considered to be a service tour.

CustomerDebit

If the customer shall be charged with debit, you need to select the CustomerDebit checkbox.

Description Enter an appropriate description.

Example: SHIP-TO-PARTY




(C) SAP AG 396

Define Time Types

In this IMG activity, you maintain various categories for the time information collected in the

course of a tour. You can later use the time categories for statistical evaluations.

Additionally, you can maintain whether the recorded time is considered as working time andwhether a customer debit memo shall be created for each of the entries made.

Procedure


Accounting Basic Functions , choose Define Time Types.




Time Type

Specify an alphanumeric key with up to two characters for the time type to bedefined.

Example: M1

No WorkingTime

If the entered time is considered as working time, you must set the option noworking time. The default setting is blank = No. This means that, as a rule,the recorded time is considered as working time.

CustomerDebit If the customer shall be charged with debit, you need to select the CustomerDebit checkbox.


Example: BREAK TIME




(C) SAP AG 397

Define Payment Methods

In this IMG activity, you can define payment methods. The payment method describes the

procedure of the currency transfer using different means of payments. The following paymentmethods have been implemented by SAP:

CA = Cash payment

CC = Credit card

CH = Check

If you have maintained your own defined payment methods for the mobile scenario (DefinePayment Methods [Page 227]), you need to enter them in this table as well.

In a non-mobile business scenario, the payment methods can be selected during the

recording process in the Settlement Cockpit.

Procedure


Accounting Basic Functions , choose Define Payment Methods.




Payment Met Enter one of the keys from the List of Payment Methods.

Example: CA


Example: CASH PAYMENT


If new payment methods have been created, it is necessary to make additional Customizingsettings in the /DSD/SL_POSTSET Customizing table (posting control for driver receipts andexpenditures).



(C) SAP AG 398

Define Reasons for Differences for Check-out andCheck-in

In this IMG activity, you define the reasons for determined differences during the check-outand check-in procedure. These reasons may be used to classify the check-out/check-indifferences of the stock on the truck.

Possible reasons for determined differences could be: product damaged in transit, mistakes(for example, wrong freight list), or product theft.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Backend

Route Accounting Basic Functions , choose Define Reasons for Differences forCheck-in and Check-out.




Reason Code Enter a two digit key for the difference reason to be defined.

Example: M1


Example: DAMAGED IN TRANSIT


Result

Only reasons maintained in the /DSD/HH_RACKD_V Customizing table are available on theCheck-out/Check-in screen in the Settlement Cockpit in the DSD back end.



(C) SAP AG 399

Define Reasons for Changing Deliveries andOrders

In this IMG activity, you define reasons for deviations from the planned outbound deliveryquantity. These reasons are used to classify deviations from the delivery quantity.

Examples for possible reasons are: customer orders more/less, store closed, or lower stock-on-truck quantity than required.

The reasons can be used to evaluate delivery changes.

Procedure


Accounting Basic Functions , choose Define Reasons for Changing Deliveries.





Example: M1


Example: INCORRECT ORDER


Result

Only reasons that are maintained in the /DSD/HH_RAREAS_V Customizing table areavailable for use on the Delivery Execution screen in the Settlement Cockpit on the DSD backend.



(C) SAP AG 400

Define Customer Visit Reasons

In this IMG activity, you define customer visit reasons to describe a visit to a customer in

detail. The classification itself does not initiate any operative activities.

In the /DSD/HH_RTACC_CHECK delivery BAdI, customer-specific extensions can beimplemented. This makes it possible for businesses to create their own classifications forcustomer visit reasons and to store the relevant flow logic in this BAdI.

Integrating BAdIs into the check modules enables them to be called during uploading.

The BAdI has an error table that can also be filled by the BAdI. For example, adding a recordwith an error message of type A (premature termination) prevents writing into the Route

Accounting Database in the BAPI. An entry is written in the application log.

Procedure


Accounting Basic Functions , choose Define Customer Visit Reasons.




Visit Reason Enter a two digit key for the difference reason to be defined.

Example: M1




Result

Only reasons maintained in this Customizing table are available for use on the Customer Visit screen in the Settlement Cockpit on the DSD back end.



(C) SAP AG 401

Number Range Interval Maintenance

In this IMG activity, you define the number intervals of the number ranges for route

accounting documents. When creating a document, a unique number is assigned to identifythe document. The number comes from the number range, which is provided for thedocument type. There are the following two possible types:

Internal number assignment

The SAP system automatically assigns a consecutive number from the definednumber range.

External number assignment

You specify a number from the external number range.

Process


Accounting Basic Functions , choose Number Ranges:

o Maintain Number Range for Check-out Documents

o Maintain Number Range for Check-in Documents

o Maintain Number Range for External Delivery Documents

o Maintain Number Range for External Order Documents

o Maintain Number Range for External Invoice Documents

o Maintain Number Range for Settlement Documents

o Maintain Number Range for the Final Settlement Run

2. Choose Intervals (with the pencil).

3. Choose Interval+.

Define the following number range intervals for the respective route accountingdocuments:

Number Range

Interval Route Accounting Document

01 Check-out documents validate outgoing activities when the vehicleleaves the plant premises with goods.

02 Check-in documents validate inbound activities when the vehiclereturns to the plant premises from its tour.

03 SAP R/3 document duplicating external deliveries documents createdon the handheld.

04 SAP R/3 document duplicating external orders documents created on

the handheld.



(C) SAP AG 402

Number RangeInterval

Route Accounting Document

05 SAP R/3 document duplicating external invoice documents created onthe handheld.

06 Settlement documents.

07 Documents of the final settlement run.

The limits of the number range interval are not allowed to overlap. Each vale may exist onlyonce.

The number range may not overlap the number range of the handheld. An overlap of thenumber range interval prevents unambiguous assignment of numbers. Double table entries in

the database result in premature termination of the program.



(C) SAP AG 403

Assign Number Range Interval

In this IMG activity, you assign a number range interval number (01 to 07) to a usage of the

number range interval. The system checks whether the corresponding number range numberis assigned to the respective number range object.

Number range interval 01 applies to check-out documents.

Number range interval 02 applies to check-in documents.

Number range interval 03 applies to external delivery numbers.

Number range interval 04 applies to external order numbers.

Number range interval 05 applies to external Invoice numbers.

Number range interval 06 applies to settlement documents.

Number range interval 07 applies to final settlement run.

Procedure


Accounting Basic Functions Number Ranges , choose Assign Number RangeInterval .

2. In the Number Range Interval Purpose field, choose one from the input help.

In No. Range No. field, assign the appropriate number range digits. For example,

assign the number range interval 01 to Check-out Control Document Number .

Repeat step 2. and 3. for each number range interval defined in the previous activityMaintain Number Range Intervals [Page 401].




(C) SAP AG 404

Route Settlement

Route settlement is the final step within DSD route accounting. During the settlement process,materials and payments are balanced, differences are reconciled and charged to theappropriate account, and goods movements (goods issue, goods receipt) are posted. Finally,customer and driver accounts are credited and debited based on the tour activities.

DSD Route Settlement offers a wide range of options on how to settle a tour, particularly withregards to automatic route settlement as well as the difference processing during routesettlement. It is possible to:

Automatically release the tour for presales processing only

Automatically generate presales orders without settling the whole tour

Automatically release the tour for final settlement

Automatically run difference determination

Involve tolerance limits during difference determination (for material and/or moneyitems) thus allowing tour settlement to proceed in case of tolerated differences

Exclude specific tours from being settled automatically based on selectable criteriasuch as driver, sales area or shipment type

Automatically start the Final Settlement Run

Post differences on defined interim accounts

Manually execute all steps involved in the route settlement process (that is, releasetour, run difference determination, trigger final settlement) not only from withinsettlement cockpit, but also from within the tour data entry screen

Integration

Process

In order to have all the functionalities listed above available for Route Settlement, thefollowing Customizing activities as well as control table maintenance are required.

You make these settings in Customizing for Logistics Execution under SAP Direct Store

Delivery Route Accounting Route Settlement .

The process route settlement includes the following steps:

1. Settlement Office [Page 406]

2. Settlement Type Configuration [Page 411]

3. Collection Processing [Page 417]

4. Final Settlement/Document Control [Page 423]

5. Settlement Cockpit [Page 431]

6. Route Settlement: Tolerances [Page 437]



(C) SAP AG 405

With regards to control tables maintenance in the SAP Easy Access menu, navigate to

Logistics Logistics Execution SAP Direct Store Delivery Route Accounting andmaintain the appropriate settings for the following functions:

1. Automatic Route Settlement [Page 434]

2. Route Settlement: Interim Accounting [Page 445]



(C) SAP AG 406

Settlement Office

You make settings for Settlement Office in Customizing for Logistics Execution under SAP

Direct Store Delivery Route Accounting Route Settlement , choose Settlement Office.

Process

Settlement Office comprises the following steps:

1. Define Settlement Office [Page 407]

2. Set Determination of Settlement Office [Page 409]



(C) SAP AG 407

Define Settlement Office

The DSD Route Settlement creates up a new organizational unit called a settlement office.

From the technical point of view, the settlement office represents an organizational unit withcontrol functions.

The work area of a settlement office consists of the following:

Determining differences that occurred during the tour

Deciding whether a difference is posted to the debit or credit side

Deciding on releasing for further processing

Clearing errors and inconsistencies that occurred during the tour

In this IMG activity, you define the settlement office and assign sales area data to the newlycreated settlement office. Each settlement office is assigned to exactly one sales area.

Prerequisites

You have defined at least one sales organization.

You have defined a distribution channel.

You have defined a division.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Route Accounting Route Settlement Settlement Office , choose Define SettlementOffice.




Settlement Office

Specify an alphanumeric key with up to 4 characters for eachsettlement office.

Example: M001

Sales Organization Select a sales organization from the input help.

Example: 0001

Distribution Channel Select a distribution channel from the input help.

Example: 01

Division Select a division from the input help.

Example: 01



(C) SAP AG 408


Description of SettlementOffice

Enter a description for the new settlement office.

Example: MAIN OFFICE




(C) SAP AG 409

Set Determination of Settlement Office

In this IMG activity, you determine a standard settlement office for each transportation

planning point. If no entry is maintained in this table, the route settlement cannot be startedautomatically (by a background job), but the relevant settlement office needs to be enteredmanually each time before the final settlement run can be executed.

When trying to settle a tour, the entries in this table provide default values about whichsettlement office should be used for settling the tour, depending upon the transportationplanning point. The default values can be overwritten.

Prerequisites

You have defined a transportation planning point.

You have defined a settlement office in the /DSD/SL_TBSO transaction.

Procedure


Accounting Route Settlement Settlement Office , choose Set Determination ofSettlement Office.


3. Assign a settlement office to a transportation planning point with the following values:


TrspPlanPtSelect a transportation planning point from the input help.

Example: M001

Description

Automatically displayed depending on chosen transportationplanning point

Example: TTP-COASTAL 01

Settlem.Office Select a settlement office from the input help.

Example: M1


Automatically displayed depending on selected settlementoffice

Example: MAIN OFFICE


You cannot assign more than one settlement office to the same transportation planning point.But you can assign one settlement office to more transportation planning points.



(C) SAP AG 410

Result

After this Customizing, route settlement starts automatically - you do not have to entersettlement office manually before the settlement run.



(C) SAP AG 411

Settlement Type Configuration

To simplify the route settlement process, you can run specific processes in background.

Therefore, the system has various predefined settlement types that you can assign to ashipment type.

Process

In Customizing for Logistics Execution under SAP Direct Store Delivery Route Accounting

Route Settlement , choose Settlement Type.

Settlement Type configuration includes the following steps:

1. Define Settlement Types [Page 412]

2. Set Determination of Settlement Types [Page 415]



(C) SAP AG 412

Define Settlement Types

In this IMG activity, you pre-define settlement types that will be used by the system to

facilitate background processing of specific processes during the Final Settlement Run (FSR).For different business processes (for example, presales process, van sales process), differentsettlement types are defined. Subsequently, every settlement type is assigned to a shipmenttype. For more information, see Set Determination of Settlement Types [Page 415].

In this IMG activity, you control which SAP ERP documents are created during processing, forexample, whether difference documents are created and/or goods movements are postedand/or incoming payments are posted.

Procedure


Accounting Route Settlement Settlement Type , choose Define Settlement Types.




Settlement Type

Specify an alphanumeric key with up to 2characters for each settlement type.

Example: M1

Description

Enter a description for the new settlementtype.

Example: DELIVERY and CASH PAYMENTSw/ NEW ORDER

DSD Route Settlement: Settlement Types

The data elements of this sub-screenrepresent follow-up activities performedduring the FSR. You may or may not selecteach checkbox according to your businessrequirements. For performance reasons,

only activate those data elements (persettlement type) that are required for yourbusiness processes.

Balancing dnkl st

(dnkl st = start dark)

Select an option from the drop-down list tocontrol the background processing of thedifference determination (balancing).

0 = Do not release tour for settlement

1 = Release tour for settlement, Do not start

balancing

2 = Release tour for settlement, Startbalancing



(C) SAP AG 413


Start Blind FinSettm If activated, FSR is enabled to start inbackground processing.

Create COCI DiffDoc.

If activated, Check-out and Check-indifferences become relevant for posting anddifference documents are created for Check-out and/or Check-in differences, dependingon settings of applicable tolerance groupsand settings within interim accounting.

Example: during difference determination,differences are detected for Check-out andCheck-in that fall outside of tolerated limits.Due to this selected checkbox, they aredetermined as relevant. Based on separateinterim accounts that are setup for CO-

differences and CI-differences, FSR willcreate two difference document (one for CO-differences, one for CI-differences) taking theinterim account maintained for thecorresponding inside tolerance setting assold-to party.

Create Returns Load. If activated, FSR creates a Return LoadingNote taking the driver as sold-to party and thechecked-in materials and quantities as items.

Process Time Date

If activated, time data entered on the timescreen of the settlement cockpit/tour data

entry can be processed provided acorresponding customer development hasbeen implemented.

Time processing does not exist in Standard.

Process Tour Distance

If activated, distance data entered on thedistance information screen of the settlementcockpit/tour data entry can be processedprovided a corresponding customer

development has been implemented.

Distance processing does not exist inStandard.

Create New Orders If activated, FSR creates new orders.

Process Order/Del. If activated, FSR processes any order ordelivery-related changes for the deliveriescontained in a given tour.

Create DiffDocs Fin. If activated, final differences become relevant



(C) SAP AG 414


and a difference document is created,depending on settings of applicable tolerancegroups and settings within interim accounting.

Example: during difference determination, CI-differences are detected as being outside oftolerated limits and determined relevant duethis selected checkbox. Based on interimaccounts that are setup for CI-differences aswell as final differences, FSR will create adifference document taking the interimaccount maintained for final differences assold-to party.

With regards to difference documents, thefollowing cases need to be distinguished:

If checkbox Create DiffDocs Fin is selectedand checkbox Create COCI DiffDoc is notselected, the system creates only one addeddifference document.

If checkbox Create COCI DiffDocs is selectedand checkbox Create DiffDoc Fin is notselected, then system creates two separatedifference documents.

If both checkboxes are selected (CreateDiffDocs Fin and Create COCI DiffDoc ), thesystem creates only one added differencedocument because the selection of theCreate DiffDocs Fin checkbox overrules theselection of the Create COCI DiffDoc checkbox).

Post Goods Movement If activated, FSR posts goods movements fororiginal and/or newly created deliveries.

Process Bill. Doc. If activated, FSR creates a billing document,based on input provided in the invoice screen

of the settlement cockpit/tour data entry.

Post IncomingPayment

If activated, FSR posts customer payments tothe customer account, provided no specialand no generic interim account is applicablefor the customer concerned.

Process Collect.Clrg If activated, FSR clears specified open itemsof the customer accounts.




(C) SAP AG 415

Set Determination of Settlement Types

In this IMG activity, you determine a standard settlement type for each shipment type. Without

an entry in the Customizing table, the route settlement cannot be started automatically (by abackground job). You must enter it manually before each final settlement run.

Prerequisites

You have defined shipment types.

You have defined settlement types in the /DSD/SL_TSLTYP transaction.

Procedure


Accounting Route Settlement Settlement Type , choose Set Determination ofSettlement Types.




Shipment type Select a shipment type from the input help.

Example: M001

Description Automatically displayed depending on the shipment typechosen.

Example: INDIV.SHPMT.-ROAD

Sett.Type Select a settlement type from the input help.

Example: M1

Description Settlementtype

Automatically displayed depending on the settlement typechosen.

Example: DELIVERY and CASH PAYMENT w/ NEW ORDER


Result

After this IMG activity, route settlement may be started automatically. You do not have toenter it manually before each settlement run.



(C) SAP AG 416

Assign Allowed Settlement Types to SettlementOffice

To enable a given settlement office to perform route settlement, you must enter the settlementtype for which a settlement office can perform route settlement.

You can do this in two ways:

Enter a combination of settlement office and settlement type: The settlement officecan perform route settlement for only one settlement type.

Enter a settlement office without a settlement type: The settlement office can performroute settlement for any settlement type.

Prerequisites

You have defined settlement offices in Customizing for Logistics Execution, under

SAP Direct Store Delivery Route Accounting Route Settlement Settlement

Office Define Settlement Office .

You have defined settlement types in Customizing for Logistics Execution, under

SAP Direct Store Delivery Route Accounting Route Settlement Settlement Type

Define Settlement Types .

Procedure


Accounting Route Settlement , choose Assign Allowed Settlement Types to

Settlement Office.

2. Choose New entries and enter the following data:


Sett.Off Select a settlement office.

Example: M001

Sett.Type Select a settlement type.

Example: M1


When you select a settlement office, the description appearsautomatically.

Example: INDIV.SHPMT.-ROAD

Description SettlementType

When you select a settlement type, the description appearsautomatically.

Example: DELIVERY and CASH PAYMENT w/ NEW ORDER




(C) SAP AG 417

Collection Processing


Route Settlement , choose Collection Processing.

Process

Collection processing includes the following steps:

1. Maintain Settings for Automatic Clearing [Page 418]

2. Maintain Settings for Manual Clearing [Page 420]

3. Post Control of Driver Receipts and Expenditures [Page 421]



(C) SAP AG 418

Maintain Settings for Automatic Clearing

In this IMG activity, you enable the system to automatically clear assignments (open items) in

Financial Accounting (FI).

Prerequisites

For this IMG activity, the following settings are required in the FI module:

You have defined a company code.

You have set up a clearing procedure.

You have defined document types that classify accounting documents.

Procedure1. In Customizing for Logistics Execution under SAP Direct Store Delivery Route

Accounting Route Settlement Collection Processing , choose Maintain settings for Automatic Clearing.




Company Code Choose an existing company code.

Clearing OK

blank = No

X = Yes

Permission of financial accounting is required for automatic clearing.

User StatusMandatory

blank = No

X = Yes

Status assigned by the user needs to be entered.

ClearingProcedure Choose an existing clearing procedure for transfer posting in financialaccounting.

Document Type Choose an existing document type which is used for clearing in financialaccounting.

Partial Payt OK

blank = No

X = Yes

Status code allows clearing of partial payments with debits.

Posting key If the clearing of partial payments is allowed, choose an existing posting

key from FI for payment differences with a debit indicator.



(C) SAP AG 419

To perform clearing automatically during the final settlement run, select the ClearingOK option and deselect the User Status Mandatory option.




(C) SAP AG 420

Maintain Settings for Manual Clearing

In this IMG activity, you define the status assigned by the user.

Procedure


Accounting Route Settlement Collection Processing , choose Maintain Settingsfor Manual Clearing.




Manually AssignedStatus

Specify an alphanumeric key with up to 2 characters to classifystatuses that can be manually assigned by the user.

Automatic Clearing Allowed

blank = No

X = Yes

Status code allows clearing.





(C) SAP AG 421

Post Control of Driver Receipts and Expenditures

In this IMG activity, you customize automatic posting of driver receipts and payments. They

are performed during the final settlement run.

Prerequisites

For this activity, you have defined the following in the Financial Accounting module:

A company code

A clearing procedure

Document types that classify accounting documents

A posting key driver account

A posting key customer account

Procedure


Accounting Route Settlement Collection Processing , choose Posting control ofDriver Receipts and Expenditures.




Company Code Select a company code from the input help.

Example: 0001

Currency Enter a currency to be used for the postings.

Example: EUR

Payment Method Choose one of the payment methods defined in Define PaymentMethods [Page 397].

Receipt/Expenditure 1 = Receipts

2 = Expenditures

Document Type Choose an existing document type that is used for the posting inFinancial Accounting.

Driver Posting Key Choose an existing posting key from Financial Accounting. Thisdata element is used for selecting the relevant posting key to debitor credit the driver account during collection assignment.

Customer Account

Posting Key Choose an existing posting key from Financial Accounting.



(C) SAP AG 422


Material Alphanumeric key uniquely identifying the material.




(C) SAP AG 423

Final Settlement/Document Control

In this IMG activity, you define SAP ERP documents created during final settlement. They

depend on the settlement types and the various customer sales transactions types.

Process


Route Settlement , choose Final Settlement/Document Control.

Final settlement/document control includes the following steps:

1. Define Customer Sales Transaction Types [Page 424]

2. Document Controls for Each Customer Sales Transaction Type [Page 426]

3. Set Up Customer Sales Transaction Types Determination [Page 428]

4. Set Up Customer Sales Transaction Types Determination for Check-in/-out Reasons[Page 429]

5. Define Customer-Specific Customer Sales Transaction Types [Page 430]



(C) SAP AG 424

Define Customer Sales Transaction Types

In this IMG activity, you define customer sales transaction types to classify the customer sales

transactions in regard to their business processes. You define an activity on the basis of touractivities, such as delivery execution and order with reference to the final settlement in detail.

Customer sales transactions are tour activities connected to sales or physical deliveryexecution.

The following customer sales transaction types are implemented:

Customers may define their own specific customer sales transaction types, as required, usingthe usual customer naming space ( X , Y , Z ).

ID Customer Sales Transaction Type

01 Out.Dely Existing Orders w/o Changes

02 Out.Dely Exist. Orders Reduction/Deletion

03 Out.Dely Exist.Orders Addit. Sales

04 Truck Sales

05 Taking Back Empties

06 Customer Sales Returns

07 Order Acceptance

10 Check-out Driver Debit from Difference

11 Check-out Driver Credit from Difference

12 Returns Loading Note

13 Check-in Driver Debit from Difference

14 Check-in Driver Credit from Difference

15 Check-in Driver Breakage Debit

16 Check-in Driver Breakage Credit

17 Check-out Driver Breakage Debit

18 Check-out Driver Breakage Credit

20 Sales to Customer (Free of Charge)



(C) SAP AG 425

ID Customer Sales Transaction Type

21 Taking Back Empties (Free of Charge)

22 Customer Sales Returns (Free of Charge)

23 Order Acceptance (Free of Charge)

24 Free Delivery without Change

25 Free Delivery Quantity Reduction

26 Free Delivery Quantity Increase

27 Loading Conf. Broken in Transit Credit

28 Loading Conf. Broken in Tansit Charge

29 Loading Confirmation Driver Credit

30 Loading Confirmation Driver Charge

Procedure


Accounting Route Settlement Final Settlement/Document Control , choose DefineCustomer Sales Transaction Types.

2. The table includes a two digit key for the customer sales transaction type and adescription.

If you create a new customer sales transaction type, the relevant flow logic for furtherprocessing must be reprogrammed.



(C) SAP AG 426

Document Controls for Each Customer SalesTransaction Type

In this IMG activity, you define which SAP ERP documents are generated during the finalsettlement run. The relevant SAP ERP documents are maintained for each customer salestransaction type depending on the settlement type. For more information, refer to DefineSettlement Types [Page 412].

For a settlement type with the option Create Difference Documents Driver selected, thesystem generates check-out/check-in difference documents. The system uses thecorresponding document type defined in this activity.

Prerequisites

You have defined the following settings for follow-up activities in standard SAP :

Sales document types

Delivery types

Item usages

Procedure


Accounting Route Settlement Final Settlement/Document Control , chooseDocument Control for each Customer Sales Transaction Type.




Settlement Type Choose an existing settlement type.

Customer SalesTransaction Type

Choose one of the customer sales transaction types.

Extend ExistingDocument

Indicates whether documents are extended:

<blank> = No

X= Yes

Reset Billing Block

Billing block is undone.

<blank> = No

X= Yes

QuantityDetermination

Input/Output field to define quantity:

0 = Difference between delivered and confirmed quantity



(C) SAP AG 427


1 = Confirmed quantity

BOM Explosion

Method of bill of material (BOM) explosion for a new document:

<blank> = Break down BOMs in one step according to master data.

1 = Do not break down BOMs.

This setting is just required if your adding BOM materials directly to adelivery type. Otherwise, the item category defines the BOMexplosion.

Mapping Type

Determine if the delivery execution (order entry, driver document) isconverted to a:

01 = Delivery

02 = Customer order

03 = Delivery receipt confirmation

Delivery Type Enter the delivery type to convert the delivery execution from thehandheld into a delivery.

Item usage

Enter the appropriate item usage to:

o Convert delivery execution from the handheld into an

order

o Perform item category determination with an itemusage

Sales DocumentType

Enter the appropriate sales document type to convert a deliveryexecution from the handheld into an order.

BOM Application Enter the application to convert the handheld data into a delivery.


Repeat steps 2. to 4. for each customer sales transaction type.



(C) SAP AG 428

Set Up Customer Sales Transaction TypesDetermination

In this IMG activity, a more precise customer sales transaction type determination is enabled.The determination is based on the entry in the Reason field (header or item) within theSettlement Cockpit. These settings allow the assignment of customer-specific customer salestransaction types to standard DSD customer sales transaction types, meaning that no extracoding is necessary.

Prerequisites

Settlement types are maintained in the IMG activity /DSD/SL_TSLTYP .

Reason codes are maintained in the IMG activity /DSD/HH_RAREASON .

Customer sales transaction types are maintained in the IMG activity/DSD/SL_TCSTATYP .

Procedure


Accounting Route Settlement Final Settlement/Document Control , choose Set UpCustomer Sales Transaction Types Determination.




Settlement Type Choose a settlement type from the input help.

Reason Choose a reason from the input help.

Customer Sales TransactionType

Choose a customer sales transaction type from the inputhelp.


Result

During the final settlement run, the system determines the correct customer sales transactiontype (customer-specific or standard), based on the reason code that was entered in therespective field within the Settlement Cockpit and/or the Fast Tour Data Entry screen.



(C) SAP AG 429

Set Up Customer Sales Transaction TypesDetermination for Check-In/-Out Reasons

In this IMG activity, a more precise customer sales transaction type determination is enabled.The determination is based on the entry in the Reason field within the Settlement Cockpit onCheckIn/Out screens. These settings allow the assignment of customer-specific customersales transaction types to Standard DSD customer sales transaction types, meaning that noextra coding is necessary.

Prerequisites

Settlement types are maintained in the IMG activity /DSD/SL_TSLTYP .

Reason codes are maintained in the table /DSD/HH_RACKDRS.

Customer sales transaction types are maintained in the IMG activity /DSD/SL_TCSTATYP .

Procedure


Accounting Route Settlement Final Settlement/Document Control , choose Set UpCustomer Sales Trans. Types Determination for CheckIn/Out Reasons.




Settlement Type Choose a settlement type from the input help.



Reason Choose a reason from the input help.




Result

During the final settlement run, the system determines the correct customer sales transactiontype (customer-specific or standard), based on the reason code that was entered in therespective field on the Settlement Cockpit screen.



(C) SAP AG 430

Define Customer-Specific Customer SalesTransaction Types

In this IMG activity, you can assign customer-specific customer sales transaction types tostandard DSD customer sales transaction types without the need for extra coding. This allowscustomer-specific customer sales transaction types to be processed in the same way asstandard ones assigned to them, but different document control can be set up.

Prerequisites

Standard and customer-specific customer sales transaction types are maintained in the/DSD/SL_TCSTATYP IMG activity.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Route Accounting Route Settlement Final Settlement/Document Control , choose DefineCustomer-specific Customer Sales Transaction Types.




Cust.Sls.Trans.Type

(Key field)

Enter the desired customer-specific customer sales transaction typefrom the input help.

Example: Y1

Cust.Sls.Trans.Type

Enter the appropriate standard customer sales transaction type whoseprocessing logic is required.

Example: 01


Result

During the final settlement run, the system applies the processing logic of the assigned

standard customer sales transaction type (here: 01) to the customer-specific customer salestransaction type (here: Y1), based on the settings maintained for the standard customer salestransaction type (here: 01).



(C) SAP AG 431

Settlement Cockpit

The Settlement Cockpit prepares the uploaded and subsequently entered data for route

accounting. At the end of a tour, the relevant tour data is entered into the Route AccountingDatabase (RAD). Within the RAD, the data is available for retrieval and display in theSettlement Cockpit for further processing. There are the following two ways to enter tour datainto the route accounting database and show it in the Settlement Cockpit:

Upload the tour data using a mobile device.

Copy the original tour data with the application copy shipment data into routeaccounting and subsequently adjust the entries with the actual data.

Process

Configuring the Settlement Cockpit comprises the following steps:

1. Maintain Transaction Screens [Page 432]

2. Activate Transaction Types [Page 433]



(C) SAP AG 432

Maintain Transaction Screens

In this IMG activity, you define identifiers (IDs) for transaction screens to make them available

in the Settlement Cockpit, either on a shipment level or on a customer visit level. Theidentifiers for the transaction screens determine the layout and the contents of the respectiveinterfaces.

The following IDs for transaction screens have been implemented:

ID Transaction Screen

SELECTION Entry: Selection Criteria

BALANCE Difference determination

COCI Entry: Check-in and Check-out Data

DELIVERY Entry: Outbound Delivery Data

DISTANCE Entry: Distance Data

TIME Entry: Time Recording

ENCASHMENT Entry: Receipts/Expenditure

GENTOUR Display: General Tour Data

INVOICE Entry: Invoice Data

ORDER Entry: Sales Order

VISIT Entry: Customer Visit

APPLLOG Display: Application Log

SETTLEDOC Display: Settlement Document

DOCFLOW Display: Document Flow

All transaction screens maintained in this table are visible in the Settlement Cockpit – as long

as they are not explicitly set inactive in the /DSD/SL_ACTIVETA Customizing table. For more

information, refer to Activate Transaction Types [Page 433].

Procedure


Accounting Route Settlement Settlement Cockpit , choose Maintain Transaction Screens.

If you create new transaction screens, relevant flow logic for further processing must bereprogrammed.



(C) SAP AG 433

Activate Transaction Types

In this IMG activity, you de-activate certain transaction types. This might be relevant, for

example, when processes require no check-out/check-in data or when the user is not allowedto handle new order entries. These transaction screens are disabled for display in theSettlement Cockpit.

Procedure


Accounting Route Settlement Settlement Cockpit , choose Activate TransactionTypes.




ID TA-Screen Select the identifier to be deactivated

Inactive Select the checkbox to deactivate the selected ID Transaction screen.




(C) SAP AG 434

Automatic Route Settlement

Whenever a tour is ready for settlement (that is, whenever tour data entry is completed), it is

necessary to execute a sequence of settlement steps in order to settle the tour. The RouteSettlement process involves the following settlement steps:

1. Release the tour for presales processing

2. Generate presales orders

3. Release the tour for settlement

4. Trigger the difference determination

5. Start the final settlement run

The first two steps are optional and depend on whether a presales order is present in a giventour and, if so, whether the user wishes to create the presales orders before the FinalSettlement.

All these settlement steps can be automated by maintaining the relevant standard functionmodules at the correct tour status IDs within the tour profiles to trigger the next settlementstep.

In cases where tour status is used for the Automatic Tour Settlement (via function modules tobe triggered at a specific tour status), tours can only be differentiated according to tourscenarios. All tours that belong to the same tour scenario containing function modules for

Automatic Tour Settlement are settled the same way. Although automating the RouteSettlement process is desirable due to its higher efficiency, there may sometimes becustomer-specific reasons that warrant an exclusion of certain tours from this automaticfeature. In such cases, it is possible to maintain exclusion rules that exclude defined toursfrom the triggered automatic process.

Prerequisites

You must have Business Function /DSD/BF switched on to be able to access all transactions

and Customizing activities related to Automatic Route Settlement.

Process

To exclude tours from Automatic Tour Settlement, you need to define corresponding rules inthe following activity:

1. Maintain Exclusions for Automatic Route Settlement [Page 435]



(C) SAP AG 435

Maintain Exclusions for Automatic RouteSettlement

In this transaction in the application menu (/DSD/SL_AUTOFSR_EXCL ), you define rules with

which you can exclude specific tours from being automatically settled. The records can bemaintained depending on several parameters, for example, scenario, shipment, or visit plandata.

The exclusion rules maintained in this control table can be further modified or enhanced by

implementing the /DSD/BADI_SL_ASL_EXCL BAdI, where additional conditions can be

defined to determine tours to be excluded from the automated process.

Procedure

1. In the SAP Easy Access menu, choose Logistics Logistics Execution Direct

Store Delivery Route Accounting Automatic Route Settlement Edit Exclusions .

On the screen that opens, switch to change mode and choose New Entries. On theupper portion of the screen, a set of entry fields appears (for scenario, settlementoffice, settlement type, and so on).

Maintain the appropriate combination of field values for which you want to maintainan exclusion rule.

You just want to exclude a specific driver from automatic route settlement. You onlyneed to maintain the Scenario field and the Driver field.

In the Control of Automatic Settlement, subscreen, select the checkbox for thosesettlement steps that should not be automatically performed for the field combinationmaintained.

The access to this table is processed by the system in the following sequence: driver-> user who created RAD -> visit plan type -> shipment type and transportationplanning point -> settlement office and settlement type. According to the sequencedescribed, the systems searches for a specific entry and then for a more general oneif no valid specific entry is found.


Result

Based on the entries made in this transaction, the Route Settlement process does notproceed automatically but waits for manual intervention to move on to the next settlementstep.

The defined exclusions are considered in the following:

All tour status function modules for settlement (see Specify Function Modules Available for Tour Status Profiles [Page 376])

Transaction /DSD/SL_MS_PRESALES – Carry Out Presales Processing

Transaction /DSD/SL_FSR – Start Final Settlement Run (unless the settlement run isrestarted)



(C) SAP AG 436

Transaction /DSD/SL_MS_SETTLE – Perform Final Settlement (unless the settlement

run is restarted)

The exclusions are skipped when starting the individual settlement steps manually in the

Settlement Cockpit ( /DSD/SL_COCKPIT transaction ).



(C) SAP AG 437

Route Settlement: Tolerances

In a delivery scenario (mobile or paper-based), the driver delivers materials to the customer

and collects returnable goods to be taken back to the depot. The driver may also collectmoney items from the customers as payments for deliveries. Upon return to the depot,returnable material items and the payments collected are checked-in by the driver. Duringdifference determination, the check-in quantities are compared with the total of all customerdeliveries and the total of all customer collections.

Up to Release SAP xMDSD2.1, messages are created and displayed on the differencescreen whenever differences are detected for either materials or money items. During theFinal Settlement Run (FSR), all differences that are found for materials are charged to thedriver’s account; even the smallest discrepancy is taken into account. While the customer’sencashment is automatically accounted on the customer’s Financial Accounting (FI) accountduring Route Settlement, the checked-in money is not forwarded automatically to the driver’saccount.

In SAP Direct Store Delivery , tolerance groups are implemented that allow you to distinguishbetween tolerated and non-tolerated differences and to suppress a determined discrepancy,based on defined upper and lower tolerance limits. Upper and/or lower tolerance limits can besetup as a combination of percentage and quantity for materials and percentage and amountfor money. The implementation of tolerance groups helps to minimize differences and givescustomers the opportunity to tolerate small discrepancies related to rounding or countingproblems. Tolerance groups also facilitate Automatic Route Settlement because smalldiscrepancies that fall within tolerated limits no longer stop the settlement process; instead,route settlement can proceed without manual intervention.

In order for tolerance groups to take effect during difference determination, each materialmust be assigned to a specific tolerance type in the material master record (DSD Data tab,

Tolerance Type field). This leads to the correct tolerance group, based on Customizingsettings.

Prerequisites

You must have the Business Function /DSD/BF switched on to be able to access all

transactions and Customizing activities related to the Tolerance Groups in DSD RouteSettlement functionality.

Process

To be able to apply tolerance groups during the Route Settlement process, the followingcontrol tables need to be maintained:

1. Define Tolerance Types [Page 438]

2. Define Tolerance Groups [Page 439]

3. Maintain Search Criteria for Tolerance Groups [Page 442]

4. Maintain Tolerance Group Determination [Page 443]



(C) SAP AG 438

Define Tolerance Types

In the /DSD/SL_TGTYP transaction, you define tolerance types that subsequently need to be

assigned in the material master records of the relevant materials.

Procedure

1. In the SAP Easy Access menu, choose Logistics Logistics Execution SAP Direct

Store Delivery Route Accounting Route Settlement Settlement Process

Tolerances Tolerance Types .




Tol.Type Maintain an ID (up to four digits) for the new tolerance type.

Example: TT01

Description Enter a description for the new tolerance type.


Result

You have defined tolerance types. These tolerance types are available for assignment in

material master records ( DSD –

Data tab, Tolerance Type field).



(C) SAP AG 439

Define Tolerance Groups

In the /DSD/SL_TGGRP transaction, you define tolerance groups and maintain their upper

and lower limits in terms of value and/or percentage. Tolerances below the desired valueneed to be maintained as negative amounts within the lower limit subscreens. Tolerancesabove the desired value need to be maintained as positive amounts within the upper limitsubscreens. The absolute limit is valid for all values of those materials that are assigned tothe tolerance group concerned. The small difference is valid for each material position on itsown. The Check limit checkboxes define which level should be considered. Any discrepancydetected in one of the checked limits avoids an automated tour settlement.

A tolerance group can be maintained either for a currency unit or for a unit of measurement(UoM). Groups are necessary to build frames to allow that equal types of materials can behandled in the same way.

Procedure1. In the SAP Easy Access menu, choose Logistics Logistics Execution SAP Direct


Tolerances Tolerance Groups .


3. Maintain the following data:


Tol.Group Maintain an ID for the new tolerance group.

Example: TG01

Description Enter a description for the new tolerance group.

Currency or Unit of Measure

Currency or Alternative Unit : select one of the twoavailable radio buttons and maintain the appropriate unitin the corresponding entry field.

Example: EUR (for currency), ST (for alternative unit)

Automatic Acceptance ofNegative Differences

Absolute Lower Limit

Check Limit Select this checkbox if you want the system to check thelimit maintained for this subscreen (absolute lower limit).

NegAccept.Limit

Enter a negative value for the accepted negative lowerlimit. If relevant, the system checks whether the shipmentas a whole exceeds this limit during differencedetermination (meaning that more units are missing thanallowed by this setting).

Example: 5 (units)



(C) SAP AG 440


Make sure that you have entered a NEGATIVE value

(with negative sign).

Percentage Lower Limit

Check Limit Select this checkbox if you want the system to check thelimit maintained for this subscreen (percentage lowerlimit).

PercLowerAccLim

Enter a percentage x as the accepted lower limit. Ifrelevant, the system checks whether the shipment as awhole exceeds this percentage during differencedetermination (meaning that more than x% of the load is

lacking) and if so, automatic acceptance of the differenceis prohibited).

Example: 30 (%)

Negative Small Difference

Check limit Select this checkbox if you want the system to check thelimit maintained for this subscreen (negative small limit).

Minor Diff.

Enter a negative value for minor differences, in anegative direction; meaning that the system detects lessunits of a material than required. If relevant, the system

checks whether an individual material level is exceededduring difference determination and, if so, displays adialog box.

Example: 5 (units)

Make sure that you have entered a NEGATIVE value(with negative sign).

Automatic Acceptance of

Positive Differences

Positive Small Difference

Check Limit Select this checkbox if you want the system to check thelimit maintained for this subscreen (positive small limit).

Minor Diff.

Enter a value for minor differences, in a positive direction;meaning that the system detects more units of a materialthan expected. If relevant, the system checks whether anindividual material level tolerance threshold is exceededduring difference determination. If so, automaticacceptance of the difference is not possible.



(C) SAP AG 441


Example: 0 (units)

Absolute Upper Limit

Check limit : select this checkboxif you want the system to checkthe limit maintained for thissubscreen (absolute upper limit)

PosAccUpperLimt

Enter a value for the accepted positive upper limit. Ifrelevant, the system checks whether the shipment as awhole exceeds this limit during difference determination(meaning more units are returned than allowed by thissetting to be automatically accepted).

Example: 2 (units)

Percentage Upper Limit

Check limit Select this checkbox if you want the system to check thelimit maintained for this subscreen (percentage upperlimit).

PercUpperAccLim

Enter a percentage x as the accepted upper limit. Ifrelevant, the system checks whether the shipment as awhole exceeds this percentage during differencedetermination; meaning that more units than the definedpercentage have been detected. In this case, automaticacceptance of the difference is prohibited.

Example: 10 (%)


Result

You have defined tolerance groups. These tolerance groups are available for assignment intolerance group determination.



(C) SAP AG 442

Maintain Search Criteria for Tolerance Groups

In the /DSD/SL_TGSEARCH transaction, you define access sequences. Each access

sequence contains a set of search criteria selected from seven available criteria: salesorganization, distribution channel, division, shipment type, settlement office, settlement type,and tolerance type. The access sequences should be setup in such a way that the systemsearches from specific to general.

Procedure



Tolerances Search Criteria for Tolerance Groups .




AccessNumber

Maintain an access sequence ID (up to two digits).

Example: 10

Sales OrgSearch

D.Channel

Search

Div.Search

ShipTypeSearch

RSOSearch

Settl.TypeSearch

Tol.Type

Search

Select the checkboxes of those criteria that you want the system to considerduring the search for a valid tolerance group record.

1. Example: 10 + all checkboxes selected

2. Example: 20 + all checkboxes selected, but not the Ship

Type Search field

In the first access sequence (ID 10 ), the system tries to find a valid tolerancegroup where ALL criteria match. In the second access sequence (ID 20 ), thesystem tries to match a valid tolerance group record without consideringshipment.

All key fields are optional and can be left blank.

4. Save your entries

Result

Based on the entries made, the system uses the specified criteria to determine valid tolerancegroup records.



(C) SAP AG 443

Maintain Tolerance Group Determination

In the /DSD/SL_TGFIND transaction, you maintain the tolerance group determination. You do

this by assigning a tolerance group to a set of tour- and settlement-related data (such assales area data, shipment type, or visit plan type) including the tolerance type. This links eachtolerance type to a tolerance group.

Procedure



Tolerances Determination of Tolerance Groups .



FieldName

User Action and Default Actions

Sales Org

D.Channel

Div.

S/VP

RSO

Settl.Type

Optional – Maintain a value for each relevant field. A field is relevant if youwant the system to consider this field value during its search for a validtolerance group.

ToleranceType

Maintain a tolerance type if you intend to assign a UoM-based tolerance group(the Tol.Group field). Tolerance types are assigned to materials in the materialmaster; therefore an entry is only required for UoM-based tolerance groups.

Leave this field blank , if you intend to assign a currency-based tolerance group(Tol.Group field).

Tol.Group

Maintain the tolerance group that the system should determine duringdifference determination for the given settings in order to apply the settingsmaintained therein.

If the previous Tolerance type field contains an entry, then you may enter aUoM-based tolerance group.

If the previous Tolerance type field is blank , then you must maintain acurrency-based tolerance group.




(C) SAP AG 444

Result

Based on the entries made, the system determines a tolerance group and applies the settingsmaintained in the respective tolerance group to the data concerned.



(C) SAP AG 445

Route Settlement: Interim Accounting

In prior releases, differences that were detected during difference determination were fully

charged to the driver’s account. Likewise, the posting of customer payments during FinalSettlement Run (FSR) depended completely on the setting of the Post Incoming Payment field within the settlement type used. This field is a global switch that does not allow adifferent processing of payment postings to be triggered.

In SAP Direct Store Delivery , interim accounts are implemented that support a flexiblehandling of difference processing and customer payment postings, depending on the specificbusiness requirements.

Interim Accounts are customer master records for the Financial Accounting (FI) accountrepresenting a non-existing person, for example, a dummy driver. An interim account is usedto replace the real sold-to party in certain circumstances, particularly when a driver debitshould be posted, which may be legally prohibited in some countries. It is possible to maintain

special interim accounts and generic interim accounts. While the special interim accounts areused for postings of an individual driver or customer only, the generic interim accounts areused for postings of all drivers or all customers, or for a group of drivers or a group ofcustomers.

In the DSD process, differences can occur during Loading Confirmation (LC), Check-out(CO), and Check-in (CI). Additionally, final differences (check-out plus check-in) may alsooccur. For each of these four potential difference events, an interim account can be assignedto trigger a specific posting of the respective differences. The following rules apply to themaintenance of the interim account control tables and their effect on difference processing:

LC

If an interim account is maintained for Loading Confirmation, the LC differences arecharged to the warehouse checker using the interim account maintained for LCdifferences. If no LC interim account is maintained, then the LC differences arecharged to the driver.

COCI

If different interim accounts are maintained for check-out and check-in, thedifferences are posted separately for check-out and check-in; that is, a separatedocument is created for each difference with the respective driver interim account assold-to party.

COCI

If the same interim accounts are maintained for check-out and check-in, only onedocument is created with two items (one item for the check-out differences and onefor the check-in differences) using the respective driver interim account as sold-toparty.

COCI & Final

If no interim accounts are maintained (neither for check-out nor for check-in), then the

system posts the COCI differences as total using the driver interim accountmaintained for the final differences.

COCI & Final

If an interim account is maintained only for check-in, but not for check-out, the sameapplies as if no COCI interim accounts are assigned: the system posts the COCI



(C) SAP AG 446

differences as total using the driver interim account maintained for the finaldifferences.

COCI & Final

If neither COCI nor Final Difference have an interim account assignment, the

differences are charged to the driver’s real account using the real driver as sold-toparty in the document created.

The handling of differences can be differentiated even further by using tolerance groups andby setting up different interim accounts depending on whether the differences are within oroutside of the tolerated limits. Such inside/outside interim accounting can be maintained foreach type of difference (Loading Confirmation, Check-out, Check-in, or Final Differences).The difference posting is always done completely, meaning that it is either completelycharged to an account for outside of the tolerance group or completely charged to an accountwithin the tolerance group.

Sometimes differences may occur for which neither warehouse checker nor driver can beheld responsible. In such cases, a different Customizing can be set up that is determinedusing the reason code. A field for entering a reason code is available on all check-out/check-in directions within the COCI header data in the Settlement Cockpit or Tour Data Entry. Thefollowing COCI directions exist:

1-Check-out

2-Check-in

3-Reload Check-out

4-Reload Check-in

5-Loading Confirmation Initial

6-Loading Confirmation Confirmed

It is important to note that differences must be relevant in order to be posted. The relevanceof differences is determined by the settings within the settlement type used:

COCI differences are relevant if the Create Check-out and Check-in Difference

Documents field (CRT_CHKO_DIFF) is switched on in the settlement type concerned.

Final Differences are relevant if the Create Difference Documents for Final Difference

field (CRT_DRV_DIFF) is switched on in the settlement type concerned.

Besides advanced difference handling, the Interim Accounting functionality is also used tosupport a different processing of customer payment postings during the payment posting step

within the FSR. In detail, it is possible to direct the booking of payments to special interimaccounts (for both customer and driver) depending on the payment type used. During theFSR, the driver is debited with the collected payments, depending on the payment type andits Customizing. If the Customizing refers to an interim account (such as for credit cardpayments), this account is debited instead of the driver’s account. This allows credit cardpayments to remain as open items for the clearing process. It is possible to maintain interimaccounts for individual sold-to parties (driver/customer) or to maintain generic interimaccounts for all drivers/all customers or a group of drivers/a group of customers.

Prerequisites

You must have the Business Function /DSD/BF switched on to be able to access all

transactions and Customizing activities related to the Interim Accounting functionality in DSD

Route Settlement .



(C) SAP AG 447

Process

To be able to use Interim Accounting during Route Settlement, the following maintenance ofall control tables is required.

For control table maintenance in the SAP Easy Access menu, choose Logistics Logistics

Execution Direct Store Delivery Route Accounting Settlement Process AccountDetermination :

1. Maintain Special Driver and Customer Accounts (Collection) [Page 448]

2. Maintain Generic Driver and Customer Accounts (Collection) [Page 450]

3. Maintain Interim Accounts with +/- Differences [Page 451]

4. Maintain Interim Accounts for Final Differences [Page 454]



(C) SAP AG 448

Maintain Special Driver and Customer Accounts(Collection)

The control table in the /DSD/SL_PMSIAC transaction is relevant for drivers and customers.

In this table, you maintain an interim account per payment method for specific sold-to parties.

Whenever a customer has made a payment during a tour, the system checks the entries inthis table during the Final Settlement Run to see whether an interim account has beenmaintained for the customer concerned and the payment method used. If a valid entry exists,the system posts the revenue to the interim account found. If no valid record applies, thesystem checks whether a generic customer account is maintained and, if so, uses this genericaccount to post the payments.

The process is the same for drivers where collections are posted to the special interimaccount for the payment method used or, if not available, to the generic interim account for

drivers.

Procedure


Store Delivery Route Accounting Settlement Process Account Determination

Special Driver and Customer Account (Collection):



Field

NameUser Action and Default Actions

PM

Select a payment method from the input help.

Example: CC (credit card)

Entries should be restricted to cashless payment methods such as credit card orcheck.

Sold-to-Party

Enter the customer number for which a special interim account should be

maintained.

Example: CP_KON1300

Account

Maintain the special interim account number to be used for payment postings forcustomer/driver entered in the Sold-to-Party field and with payment methodentered in the PM field .

Example: 303




(C) SAP AG 449

Result

Based on the entries in this table, the system is able to determine whether a special interimaccount exists for a given payment method and a given customer/driver.



(C) SAP AG 450

Maintain Generic Driver and Customer Accounts(Collection)

The control table in the /DSD/SL_PMGIAC transaction is relevant for drivers and customers.In this table, you maintain generic interim accounts per payment method for alldrivers/customers or a group of drivers/a group of customers. It is useful for businesses thatdo not want to keep an individual interim account for each customer or each driver (or groupsof them), but want to post only one interim account for all drivers and one for all customers.

The entries maintained in this table are used if no special interim account was found for thedriver or customer concerned.

Procedure


Store Delivery Route Accounting Settlement Process Account Determination Generic Driver and Customer Account (Collection) .




PM

Select a payment method from the input help.

Example: CH (Check)

Entries should be restricted to cashless payment methods such as creditcard or check.

Cust.Account Optional – Maintain the generic interim account number for customerpayment postings with payment method entered in the PM field.

Driver Account

Optional – Maintain the generic interim account number for driverencashment collections with payment method entered in the PM field.


Result

Based on the entries in this table, the system is able to determine whether a generic interimaccount exists for a given payment method at the customer or driver level..



(C) SAP AG 451

Maintain Interim Accounts with +/- Differences

The control table in the /EMSE/SL_DIFIAC transaction is only relevant for drivers. In this

table, you maintain settings per individual driver by specifying interim accounts for postings ofdifferences that may have occurred during Loading Confirmation, Check-out, or Check-in. Foreach difference event (LC/CO/CI), you can maintain a separate interim account fordifferences that fall within a tolerated limit and for differences that are outside the tolerancelimit. Optionally, a reason code may also be maintained, which enables the user to set updifferent interim account settings for the same driver leading to different sales document typesto be used, based on different reason codes.

During Route Settlement, if the system detects a difference (either for Loading Confirmation,for Check-out, or for Check-in), it first determines whether the respective difference falls withinor outside a defined tolerance limit. It then determines the relevance of the difference asindicated in the settlement type used and, if relevant, checks this table for a valid entry bysearching for driver and reason code. If a valid entry is found, the system creates a difference

document using the sales document type with the corresponding interim account as sold-toparty, as customized in this table.

It is now also possible to create a sales document type for “negative” differences based onthe reason code. This allows you to handle, for example, the following scenario:

Check out of Material A was for 10 cases.

Check in of Material A is for 9 cases but in 2 lines, 7 cases of good quality and 1 case of poorquality.

There were 2 deliveries for the route. The first delivery was for 2 cases and the second wasfor 8 cases. The first customer also returned 2 cases of poor quality and the second customerwas closed. So, in the truck there should be 8 cases of good quality and 2 cases of poorquality. But for some reason, one of the cases of good quality and also one case of poorquality got lost, so you need two different document types for that.

One document posts from the block stock and the other one from the unrestricted stock.

.

This new transaction is used instead of /DSD/SL_DIFIAC for the existing MDSD3.0 solution.

Procedure

1. In the SAP Easy Access menu, choose Logistics Logistics Execution DirectStore Delivery Route Accounting Settlement Process Account Determination

Interim Accounts with +/- Differences .



FieldName


Driver Enter a driver ID.

Reason Optional – Enter a reason code.



(C) SAP AG 452

FieldName


Code

LC out Optional – Maintain the interim account number for LC differences that areoutside a defined and applicable tolerance limit.

CO out Optional – Maintain the interim account number for CO differences that areoutside a defined and applicable tolerance limit.

CO in Optional – Maintain the interim account number for CO differences that are withina defined and applicable tolerance limit.

CI out Optional – Maintain the interim account number for CI differences that areoutside a defined and applicable tolerance limit.

CI in Optional – Maintain the interim account number for CI differences that are within

a defined and applicable tolerance limit.

SaTy

Optional – Maintain a sales document type to be used by the system for creatingthe driver difference document.

If this field is left blank, the system determines the sales document type from thesettings made in the relevant customer sales transaction types (CSTT), based onthe settlement type used.

o No Control Parameter 2

LC differences: CSTT 30 and 29

CO differences: CSTT 10 and 11

CI differences: CSTT 13 and 14

o With Control Parameter 2

LC differences: CSTT 26 and 27

CO differences: CSTT 17 and 18

CI differences: CSTT 15 and 16

Usg Optional – Maintain an item usage for specific item category determination.

DlvTy Optional – Maintain a delivery type to be used by the system when differencesshould be mapped directly into a delivery (instead of an order).

SaTy - Optional – Maintain a sales document type to be used by the system for creatingthe driver difference document.

Usg. - Optional – Maintain an item usage for specific item category determination.

DlvTy - Optional – Maintain a delivery type to be used by the system when differencesshould be mapped directly into a delivery (instead of an order).




(C) SAP AG 453

Result

If differences are determined for a tour at Loading Confirmation, Check-out, or Check-in, andthe settings in the settlement type used considers them as relevant, the system creates driverdifference documents for each of these differences during the Final Settlement Run, based onthe settings made in this table.



(C) SAP AG 454

Maintain Interim Accounts for Final Differences

The control table in the DSD/SL_IACFIN transaction is only relevant for drivers. In this table,

you maintain settings per individual driver by specifying an interim accounts for finaldifferences. Final differences are calculated as the addition of check-out differences andcheck-in differences.

It is possible to maintain separate interim accounts for differences that are within anddifferences that fall outside of defined upper or lower tolerance limits. Different salesdocument types, item usages, and delivery types can be specified for either positivedifferences (that is, actual quantity is higher than target quantity) or negative differences (thatis, actual quantity is lower than target quantity).

Procedure


Store Delivery Route Accounting Settlement Process Account Determination

Interim Accounts Final Difference .



FieldName


Driver Enter a driver ID.

Final out Optional – Maintain the interim account number for final differences that areoutside a defined and applicable tolerance limit.

Final in Optional – Maintain the interim account number for final differences that areinside a defined and applicable tolerance limit.

Styp +

Optional – Maintain a sales document type for the system to use when creatingthe driver difference document for positive differences (meaning that the actualquantity is higher than the target quantity).


o CSTT 14 (no control parameter 2)

o CSTT 16 (with control parameter 2)

SDType

Optional – Maintain a sales document type for the system to use when creatingthe driver difference document for negative differences (meaning that the actualquantity is lower than the target quantity).


o CSTT 13 (no control parameter 2)



(C) SAP AG 455

FieldName


o CSTT 15 (with control parameter 2)

Use + Optional – Maintain an item usage for specific item category determination(positive differences)

Use - Optional – Maintain an item usage for specific item category determination(negative differences)

DType + Optional – Maintain a delivery type for the system to use when final positivedifferences should be mapped directly into a delivery (instead of an order).

Dtype - Optional – Maintain a delivery type for the system to use when final negativedifferences should be mapped directly into a delivery (instead of an order).


Result

If final differences are determined for a tour and the settings in the settlement type usedconsiders them as relevant, the system creates driver difference documents for thesedifferences during the Final Settlement Run, based on the settings made in this table.



(C) SAP AG 456

Copy Control Enablement from Handheld Invoiceto R/3 Billing

With Copying Control, you can transfer the handheld-generated invoice number in the FinalSettlement Run (external invoice number) from the Route Accounting Database (RAD) intothe reference field of the SAP ERP invoice and from there into a Sales and Distribution (SD)document. Without copying control, the only handheld-generated invoice on the SAP ERP

back end system would exist in the RAD. However, it is very important to keep a record of thisexternal invoice number since many customers refer to it with a related payment. Keeping thisrecord attached to the SAP R/3 billing document enables Financial Accounting (FI) to clear

open items.

Process

Copying Control is shipped with an inactive status. You enable it with the following activities:

1. Activate Copying Routines [Page 457]

2. Assign Copying Routine to Item Categories [Page 458]

Result

With Copying Control activated and assigned to the respective item categories, the systemtransfers the handheld-generated invoice number to the reference field of the SAP ERP billingdocument.



(C) SAP AG 457

Activate Copying Routines

In this activity, you activate the copying routine (403) that is responsible for the Copying

Control of the external invoice number to the SAP ERP invoice during the Final SettlementRun.

Procedure

1. To activate the copying routine, in the SAP Easy Access menu, enter the VOFM

transaction.

2. Choose Data Transfer Billing Documents .

3. Select routine 403.

4. Choose Edit Activate .

5. Save your entry.

Return to the SAP Easy Access menu and enter transaction SE 38.

Enter the rv80hgen report ( Activation of Routines).

Choose Execute.

Result

The All routines have been successfully activated message indicates that the routine isavailable for assignment to item categories.



(C) SAP AG 458

Assign Copying Routine to Item Categories

In this IMG activity, you assign the copying control 403 to all item categories used by the

system in deliveries for which invoices are created.

Procedure

1. In Customizing for Sales and Distribution under Billing Billing Documents ,choose Maintain Copying Control for Billing Documents.

2. Choose the Copying Control: Delivery Document to Billing Document activity.

3. Choose Change mode.

From the list in the right window, select the entry containing your target billing typeand source delivery type for which you want to maintain Copying Control.

4. Select Details.

Check that the Reference number field is blank.

Select the Item menu option in the left window.

Locate the item category for which you want to maintain the Copying Control.

Mark the entry and choose Details.

In the Data VBRK/VBRP field, assign the copying control 403 by selecting it from theinput help.

Select your entry.

5. Choose Back.

Repeat steps 2. to 5. for each item category you want to maintain the copying control403 for.

Result

With Copying Control assigned to the relevant item categories, the handheld-generatedinvoice number is transferred to the SAP ERP billing document during the Final SettlementRun and facilitates the clearing of open items.



(C) SAP AG 459

Vehicle Space Optimization

Vehicle Space Optimization (VSO) is an optional feature within the DSD process that assiststhe dispatcher by setting up shipments.

For a given shipment, VSO calculates the optimum arrangement of delivery items requiringpackaging materials (such as pallets), as well as the optimum arrangement of packagingmaterials (PKM) for a particular vehicle. These optimizations use material-specific, customer-specific, and tour-sequence-dependent information. The results of these calculations are VSO packing proposals.

The system displays the VSO packing proposals graphically in a loading chart . Here, you canchange the composition of packing proposals, as well as choose a different position for apacking proposal on the vehicle. The system can also consider requirements such asoverhang, preferred loading position, and loading direction in the calculations. You can print

the VSO loading chart and the VSO loading list and use them as templates for loading.

VSO is integrated into the standard SAP dialogs for shipments as well as in the DynamicTransportation Planning part of the DSD process. The external optimizer is a third partyproduct and needs extended information of materials, such as stacking and packaginginformation.

By using the follow-on processes of VSO, the dispatcher can control warehouse functionssuch as generating transfer orders for VSO packing proposals.

Integration

Prerequisites

You have installed an external third-party optimizer.

Extra license fee.

You have activated VSO (see Activate Vehicle Space Optimization [Page 63]).

Activation of VSO is only possible when DSD is already activated (see Activate DirectStore Delivery [Page 61]).



(C) SAP AG 460

Configure Material Master

In this IMG activity, you can assign the screen sequence BV (VSO Std. Tabs) to a

combination of one or more transactions, users, material types, or industry sectors. Thisscreen sequence includes DSD- and Vehicle Space Optimizer (VSO)-specific tabs.

Procedure

1. In Customizing for Logistics – General under Material Master Configuring the

Material Master , choose Assign Screen Sequences to User/MaterialType/Transaction/Industry Sector .

2. Assign the screen sequence BV (VSO Std. Tabs) to a combination of one or moretransactions, users, material types, or industry sectors.


Result

The following DSD- and VSO-specific tabs are visible in the Material Master:

● VSO – Data

● DSD – Totals

● VSO – Plant Data

● DSD – Data

You can maintain additional material and packaging material information on the VSO –

Data tab. This information is needed for VSO calculations.

The Packaging Material Type (MARA-VHART) field determines whether the additional fieldsfor materials or packaging materials are shown on the VSO – Data tab. If the PackagingMaterial Type field is initial, the additional information for materials (but not for packagingmaterials) displays.

You maintain the additional plant-specific information for materials and packaging materialson the VSO – Plant Data tab.



(C) SAP AG 461

Configure Customer Master

Vehicle Space Optimization (VSO) is integrated in the Customer Master . In this activity, you

can maintain customer-specific information, which is then taken into account duringoptimization.

Procedure


Store Delivery Master Data Customer Create .

2. On the Customer Create: Initial Screen, enter data as required.

3. Choose Additional Data: DSD.

4. Choose the Vehicle Space Optimization tab, and enter the following data:


Max. StackingHeight

Enter the maximum height permitted for loaded packaging material forthis customer.

PackMat.Customer

Enter or choose a packaging material for this customer.

Coll. Unload.Point

Choose a Collective Unloading Point if applicable. By choosing thesame Collective Unloading Point for several customers (ship-to parties),VSO packs those customers’ deliveries together/nearby, when they are

loaded on the same truck.

PackCustomerRelated

Activate this option if the materials should be packed using a certainpackaging material for this customer.

Material-Spec.Pack.

Activate this option if materials with the same material number shouldbe packed using a certain packaging material.

Pack PckTypePacking

Activate this option if materials with the same package type should bepacked using a certain packaging material.

Side Preference

This parameter defines the preferred side of the truck for arrangingmaterials for loading and unloading.

You can configure the following values:

o No side preference

o Left side preferred for loading/unloading

o Right side preferred for loading/unloading

F/B Preference

This parameter defines the preferred loading position of the materials inthe vehicle’s dir ection of motion (in the front or in the rear).

You can configure the following values:

o No front/rear preference



(C) SAP AG 462


o Front preference for loading/unloading

o Rear preference for loading/unloading




(C) SAP AG 463

Configure Equipment/Fleet Master

In this activity, you define the basic dimensions of your loading space(s) as well as additional

information such as axle positions, axle weights, and loading directions.

Prerequisites

You have defined Vehicle Space Optimization (VSO) vehicle types in Customizing for

Logistics Execution under Direct Store Delivery Vehicle Space Optimization Define VSO

Vehicle Types and Loading Bays .

For more information, see Define VSO Vehicle Types and Loading Bays [Page 471].

Procedure

1. On the SAP Easy Access screen, choose Logistics Logistics Execution SAP

Direct Store Delivery Master Data Vehicle Create .

2. On the Create Fleet Object: Initial Screen, choose DSD Vehicle Data.

3. Select a VSO Vehicle Type and save your entries.



(C) SAP AG 464

Define Process Types

In this IMG activity, you need to define process types for Vehicle Space Optimization (VSO).

These process types control the process flow of picking and packing by grouping the items ofa VSO packing proposal.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Vehicle

Space Optimization , choose Define Process Types.

2. Enter data as required.


More InformationFor more information, see Define Process Type Determination [Page 465].



(C) SAP AG 465

Define Process Type Determination

You need to define the process type determination for the Vehicle Space Optimization (VSO)

plants. The process types are found depending on the type of the VSO packing proposal andthe layer type.

Prerequisites

You have defined process types.

Procedure


Space Optimization , choose Find Process Types.

2. Assign a process type to a plant and a layer of a VSO packing proposal :




(C) SAP AG 466

Determine Allowed Delivery Item Categories

The system only considers delivery item categories that are indicated as relevant for Vehicle

Space Optimization (VSO) during VSO processing. This allows you to exclude, for example,sub materials like empty materials (bottles of a crate) or additional advertising materials.

Procedure


Space Optimization , choose Determine Allowed Delivery Item Categories.

2. Enter Delivery Item Categories that are allowed for VSO processing and select theVSO-Relevant Item Category checkbox:


Item cat. Select a delivery item category allowed for VSO processing.

Description Filled automatically.

VSO-RelevantICat

Select the checkbox if this item category is relevant for VSO.

Other necessary settings for VSO must also exist (for example, theshipment type must be tagged as relevant for VSO).


Result

Only materials with allowed delivery item categories are transferred to the optimizer and areconsidered during VSO.



(C) SAP AG 467

Assign Plant to Transportation Planning Point

In this IMG activity, you need to assign a plant to a transportation planning point.

Procedure


Space Optimization , choose Assign Plant to a Transportation Planning Point .

2. Enter a transportation planning point and assign a plant .




(C) SAP AG 468

Define Vehicle Space Optimization Profile

Vehicle Space Optimization (VSO) parameters can be preset with specific values in a Vehicle

Space Optimization Profile. These values are then considered in the VSO run.

Procedure


Space Optimization , choose Define a Vehicle Space Optimization Profile.

2. Create a new VSO Profile.


Result

You can assign the profile to a plant and a shipment type.



(C) SAP AG 469

Assign VSO Profile to Plant and Shipment Type

In this IMG activity, you need to assign a vehicle space optimization profile to a plant and a

shipment type.

Prerequisites

You have defined VSO profiles.

Procedure


Space Optimization , choose Assign Vehicle Space Optimization Profile to Plant andShipment Type.

2. Enter a plant and a shipment type and assign a VSO Profile.


Result

You have assigned a VSO profile to a plant and a shipment type. The system automaticallyuses the parameter settings of this profile for shipments and shipment type. You can manuallyoverride these parameter settings.



(C) SAP AG 470

Define Loading Bay Categories

The loading bay category determines the loading bays for a means of transportation preferred

for loading the material.

Procedure


Space Optimization , choose Define Loading Bay Categories.

2. Define a Loading Bay and enter a Description.


Result

You can assign loading bay categories to loading bays of VSO vehicle types. You can alsoassign packing groups to loading bay categories. Packing groups are preferred packed intoloading bays with the same category.



(C) SAP AG 471

Define VSO Vehicle Types and Loading Bays

You need to define your own VSO-specific vehicle types, for which you can then also define

loading bays. You assign the VSO vehicle type to a specific vehicle.

Procedure


Space Optimization , choose Define VSO Vehicle Types and Loading Bays.

2. In Dialog Structure, choose Vehicle Type for Vehicle Space Optimization.

3. Choose New Entries and define a VSO vehicle type.


The following steps are optional and only necessary when the VSO vehicle type hasloading bays:

5. In the Dialog Structure, choose Define Loading Bays for Vehicle Type.

6. Choose New Entries and define loading bays for the VSO vehicle type.


Repeat steps 5. to 7. for each loading bay of the VSO vehicle type.

Result

You have defined the VSO-specific parameters of a vehicle in the VSO vehicle type.Optionally, you have defined loading bays for the VSO vehicle type. You can assign the VSOvehicle type to specific vehicles in the Equipment/Fleet Master .



(C) SAP AG 472

Define Packing Groups

Packing groups allow you to group materials together. A packing group is used to determine

the layer pattern of a packaging material.

Procedure


Space Optimization , choose Define Packing Groups.

2. Define a packing group for a plant.


Result

You have defined packing groups that aggregate materials. You can assign packing groups toloading bays with specific loading bay categories (you can also assign materials directly toloading bays). Furthermore, you can group several packing groups into package types.



(C) SAP AG 473

Define Package Types

A package type groups several packing groups. Furthermore, the overstackability matrix is

built using package types.

Procedure


Space Optimization , choose Define Package Types.

2. Define a packing type and assign it to a plant.


Result

You have defined package types that allow you to group several packing groups together andto build the overstackability matrix.



(C) SAP AG 474

Assign Package Types to Packing Group

In this IMG activity, you need to determine which package types to assign a specific packing

group.

Prerequisites

You have defined packing groups and packing types.

Procedure


Space Optimization , choose Assigning Package Type to a Packing Group.

2. Assign a package type to a packing group for a plant.


Result

You have assigned package types to packing groups. You have grouped materials intopacking groups and then grouped packing groups by package type. By maintaining theoverstackability matrix for the package types, you indirectly define the overstackability for allmaterials that are grouped together in one package type.



(C) SAP AG 475

Define Collective Unloading Points

If different ship-to parties share one unloading point, Vehicle Space Optimization (VSO)

ensures that their materials are loaded as close together as possible during transportation.

Procedure


Space Optimization , choose Define Collective Unloading Points.

2. Define a Collective Unloading Point and a Description.


Result

You have defined collective unloading points that you can assign, for example, to customersin the same shopping mall.

To assign a collective unloading point to a customer, you need to maintain their customermaster (see Configure Customer Master [Page 461]).



(C) SAP AG 476

Determine HU per Plant and Shipment Type

You determine whether and how handling units (HUs) are created in Vehicle Space

Optimization (VSO) when picking is finished.

Keep in mind that SAP does not support HU on the mobile client.

Procedure


Space Optimization , choose Determine HU per Plant and Shipment Type.

2. Enter a plant and shipment type and assign a predefined HU creation determination.


Result

You have defined how handling units are created for VSO when picking is completed.



(C) SAP AG 477

Assign VSO Status to Message

You can assign a status to the messages in Vehicle Space Optimization (VSO). The status of

VSO is set automatically during the VSO run but can also be changed manually.

Procedure


Space Optimization , choose Assign VSO Status to a Message.

2. Assign a VSO Status to a message.


Result

You have assigned a VSO status to a message for a plant.



(C) SAP AG 478

Loading Confirmation

Within the SAP Direct Store Delivery process, the loading confirmation function is an optionalstep that starts during shipment preparation as soon as physical loading of the truck iscompleted. Based on Customizing settings, the goods loaded onto the truck are counted andthe results are recorded on counting group level or material level. Any differences that occurare maintained on material level, unless they can be resolved by adding or removingmaterials or by adjusting deliveries. The truck can then be sealed (optional) and the sealnumbers are entered in the loading confirmation screen as part of the tour data. The step ofsaving (confirming) the loaded quantities of a new shipment is referred to as “Initial LoadingConfirmation”. Once the initial loading confirmation is completed (status confirmed), it ispossible by Customizing of loading confirmation to automatically switch the tour status, forexample, 206000 (Shipment – Loading completed ).

Depending on other Customizing settings (output control) it may be necessary to manually

trigger the download of tour data by setting the approached shipment status as customizedwithin output control. After synchronization with the mobile device, a handheld inventory iscalculated on the handheld based on the downloaded information.

The quantities of the handheld inventory are taken from the confirmed quantities of theloading confirmation and not of the planned quantities of the delivers contained in theshipments.

In consequence, the target quantities of the check-out on the mobile device are also based onthe quantities as confirmed by the loading confirmation.

In order to proceed with the process, the shipment status Shipment – Completed (shipmentstatus 5) can be set manually in the shipment header (depending on the Customizing). Thisaction can trigger the tour status to be changed to 207000 (Shipment – Completed). At thesame time, the download of tour data can be started and a stock-on-truck inventory can becalculated on the handheld based on the downloaded information.

For the loading confirmation function, two new roles called warehouse clerk and warehousechecker are implemented. Together, they are responsible for the execution of the loadingconfirmation process. The warehouse clerk is usually responsible for loading the truck whilethe warehouse checker counts and confirms the loaded quantities. Counting can be facilitatedby using counting groups. The loading confirmation function is controlled partly by tour statusCustomizing and partly by specific loading confirmation Customizing. The decision as towhether or not loading confirmation is executed for a specific shipment depends on theCustomizing settings maintained in the tour status module. The shipment type andtransportation planning point must be assigned to a scenario that contains the tour status IDs

relevant for loading confirmation. The /DSD/SV_SET LC_EXECUTION function module must

also be maintained at the respective status to trigger execution of the loading confirmation.How the loading confirmation is executed depends on the Customizing settings made in theloading confirmation module.

For customer enhancements within the DSD loading confirmation function, the

/DSD/BADI_SV_LOAD_CONF BAdI is available. It can be used to define customer-specific

changes to the loading confirmation process.

Prerequisites

You must have the Business Function /DSD/BF switched on to have access to all

transactions and Customizing activities related to the loading confirmation function.



(C) SAP AG 479

Integration

To make full use of the loading confirmation function, you need to perform the followingCustomizing activities:

1. Settings for Loading Confirmation Dialog [Page 480]

2. Settings for Display of Detail Screen [Page 482]

3. Define Reasons for Differences for Check-in and Check-out [Page 483]

4. Define Counting Groups [Page 287]

5. Define UoM Levels for Counting with Counting Groups [Page 288]



(C) SAP AG 480

Configure Loading Confirmation Dialogs

The loading confirmation is executed by the warehouse checker using the loading

confirmation maintenance screen (/DSD/SV_LC_COUNT transaction) and by the warehouse

clerk (/DSD/SV_LC_ADJUST transaction).

In this Customizing activity, you define settings that control the display and availability ofloading information and loading confirmation functions on the loading confirmationmaintenance screen.

Prerequisites

Transportation planning points must be maintained.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Loading

Confirmation , choose Settings for Loading Confirmation Dialog .



FieldName



Example: ZMDD

Blind LC

On the loading maintenance screen:

o Select the checkbox if you want to hide the target quantity of theload.

o Do not select the checkbox if you want to display the targetquantity of the load.

UCGrp

On the loading maintenance screen:

o Select the checkbox to display the load on counting group level

and material level.

o Do not select the checkbox to display the load on material levelonly.

FolOvSta

From the dropdown list, select the appropriate shipment status that the systemsets automatically in the shipment header as soon as the initial loadingconfirmation is saved.

Example: 4 - Loading End

Batch

Select this checkbox if you want to display the Batch column in the loadingconfirmation maintenance screen. If the deliveries of the processed shipment

contain batches, the system displays the summarized quantities of same batchnumbers on material level in the batch column.



(C) SAP AG 481


Result

The loading confirmation maintenance screen displays or hides information according to thesettings made in this table.



(C) SAP AG 482

Configure Display of Detail Screens

Whenever warehouse checkers detect differences during load counting on counting group

level or material level, they can either enter a reason code on material level for the changesand then confirm the shipment with differences, or change the loading confirmation status ofthe shipment to Deferred . The deferred shipment is visible on the warehouse clerk’s loading

confirmation workload screen (the /DSD/SV_LC_ADJUST transaction). The warehouse clerk

adjusts the load according to the differences and changes the loading confirmation status ofthe shipment to Recount . This status change triggers the shipment to be listed again on theloading confirmation screen of the warehouse checker, who can proceed with recounting andconfirming the load.

By selecting a single checkbox in this Customizing activity, the warehouse clerk is enabled toview the load differences on material level. Otherwise, the warehouse clerk can only accessthe working list with the deferred shipments.

The Target Quantity and Differences fields are displayed even if Blind LC was switched on,since the detail screen is intended to be a help for the warehouse clerk by showing how thetruck load needs to be adjusted.

Procedure


Confirmation , choose Settings for Display of Detail Screen.

2. Select the Detail screen checkbox.


Result

If the checkbox is selected, the warehouse clerk sees the Detail button on the loading

confirmation workload screen (/DSD/SV_LC_ADJUST), which enables them to view the

loading confirmation and the differences on material level in display mode only.



(C) SAP AG 483

Define Reasons for Differences for Check-in andCheck-out

During the counting of a load, warehouse checkers may detect load differences. In mostcases, they can defer the tour to the warehouse clerk who can make loading adjustments bychanging the loading confirmation (LC) status of the tour to “Deferred”. If they want to confirmthe tour with differences, they need to enter a reason code for the differences in therespective field. The Reason Code field is available during counting only on material level.

In this Customizing activity (the /DSD/HH_RACKD_V table), the reasons for loading

confirmation differences are defined.

Procedure


Confirmation , choose Define Reasons for Differences for Check-in and Check-out .





Example: L1

Description


Example: LC-Out of stock


Result

LC-specific reason codes are defined and can be used in the /DSD/SV_LC_COUNT

transaction to confirm shipments with load differences.



(C) SAP AG 484

Output Control Configuration

Within the SAP Direct Store Delivery process, the DSD back end Output Control is used insuch way that the system automatically produces all documents and messages, at the correcttime, that are relevant and needed for a specific shipment or visit list.

DSD back end Output Control has the following target groups:

Dispatchers (within logistics/sales and distribution) who wish to check on messages

Drivers/presellers who need to take the documents produced by the output control(visit lists, delivery notes, and order confirmations) on their tours

The messages are made available either on paper as a physical printout or are put into IDocsfor further data transfer to the mobile devices of mobile users. In both cases, the termDownload , which refers equally to both types of data transfer (printout on a printer or IDoccreation) depending on the method chosen, is used.

DSD back end Output Control distinguishes between two different business processes,namely, the sales-oriented business process and the logistic-oriented business process.Consequently, the DSD Output Control distinguishes between Customizing settings for visitlists and Customizing settings for shipments. Furthermore, each business processes output iscontrolled by its own application:

The application VL controls the sales-oriented business process where the visit list isthe leading document. This visit list contains the sequence of customers that are tobe visited without delivering products to them. Therefore, such visit lists have noconnection to shipments. Usually, the data download is performed by the systemdepending on the execution day of the visit list. Relevant data to be downloaded isthe visit list and eventually also reference documents (for example, reference orders).

The application V7 controls the logistics-oriented business process where theshipment is the leading document. This means that the visit plan type behind the visitlist on which that shipment is being based, must have the Shipping Documentcheckbox selected. As soon as a shipment reaches a certain status (for example,“planned”), the system performs the download. The system then transfers allshipment-relevant data (deliveries of the shipment or the visit list with the sequence ofthe customers) to a printer or to IDocs.

In the Customizing table for the visit plan type (see Visit Control Configuration [Page 293]), itis necessary to determine whether the visit list or the shipment is the leading document. Thesystem uses the Visit Plan Type Customizing table to determine which application within

output control is responsible for the data download.

The prerequisites for the output control to function are the existing shipments or visit lists.Shipments may be created manually or by using Dynamic Transportation Planning . Thesystem triggers the output determination when saving shipments or visit lists. If the shipmentis the leading document (according to the visit plan type used), then the system executes thedata download via the output control of the shipping application (V7). If the visit list is theleading document and does not result in a shipment, then the download of data is executedfrom within the application for the visit list (VL). In this case, only the Visit List checkboxshould be selected in the respective visit plan type.

Integration

The Customizing tables for DSD back end Output Control are located under LogisticsExecution SAP Direct Store Delivery Output Control .



(C) SAP AG 485

In order to be able to use the functions of the DSD Output Control, customer-specific settingsneed to be maintained in the following areas:

1. Output Control for Visit Lists [Page 486]

2. Output Determination for Visit Lists [Page 487]

3. Print Output and Download from Visit List [Page 504]

4. Output Control for Shipments [Page 510]

5. Output Determination for Shipments [Page 511]

6. Print Output and Download from Shipment [Page 528]

7. Valuated Delivery Note [Page 534]

8. Define Driver Messages [Page 314]

The Defining Driver Messages IMG activity is closely linked to the Text Control within VisitControl function; therefore, its purpose and procedure is explained in detail as part of thatfunction.



(C) SAP AG 486

Output Control for Visit Lists

The Output Control for visit lists is used within the sales-oriented business process to provide

the preseller with all the documents that are needed on the tour.

The preseller only needs the visit list for a specific day. In the visit list, the preseller can findsthe customers to be visited in order to receive new orders or to acquire new customers. Thepreseller does not deliver products to customers and, therefore, no delivery or shipment datais required.

The data download (printed or per IDoc) for such type of visit lists is controlled by the Visit List(VL) application.

Prerequisites

The visit plan type used must have been set so that the visit list is the leading document. In

Relevant Documents, select only the Visit List Document option.

Process

This process is found in Customizing for Logistics Execution under SAP Direct Store

Delivery Output Control Output Control for Visit Lists.


1. Output Determination for Visit Lists [Page 487]

2. Print Output and Download from Visit List [Page 504]



(C) SAP AG 487

Output Determination

The DSD back end output control uses the condition technique of the SAP ERP system.

This section deals with all those Customizing settings that are necessary for the system tofind the correct output types and messages connected with a specific visit list. Outputdetermination for visit lists determines which conditions need to be met and, if they are met,which message type(s) should be created for a given visit list, at what time, and in which form(printed or IDoc).

Generating or saving a visit list triggers this process of finding the correct output types.

Process

The steps for this process are found in Customizing for Logistics Execution under SAP

Direct Store Delivery Output Control Output Control for Visit Lists Maintain Output

Determination for Visit Lists.


1. Maintain Condition Tables [Page 488]

2. Maintain Access Sequences [Page 489]

3. Maintain Message Types [Page 490]

4. Maintain Output Determination Procedure [Page 500]

5. Assign Output Determination Procedures [Page 503]



(C) SAP AG 488

Maintain Condition Tables

In this IMG activity, you define the condition tables for output condition records. To do so, you

define the combination of fields for which you want to create output condition records in acondition table. In this way, you can control output determination depending on your specificfield combination.

The DSD back end Output Control Component already contains one condition table (390)with a unique index (Visit Plan Type). This table is used by the DSD process and should notbe changed. If you want to make changes, you should create new condition tables by copyingsimilar, already existing condition tables and making the necessary changes.

Procedure

1. To create a new condition table for DSD output control (visit list), in Customizing forLogistics Execution under SAP Direct Store Delivery Output Control Output

Control for Visit Lists Maintain Output Determination for Visit Lists , chooseMaintain Condition Tables.

2. Choose Create Condition Tables.



Table

Enter a name (3 digit number) for the new condition table to becreated.

You may only choose between 900 and 999.

Example: 900

Copy fromCondition

Table Leave blank.

4. Choose Enter.

Enter a description for the new condition table.

Select the desired fields for the condition table from the list of allowed fields, forexample, VISIT PLAN TYPE and ROUTE .

5. Generate the new condition table.

Result

You have now defined a new condition table for which you can maintain condition records.



(C) SAP AG 489

Maintain Access Sequences

In this IMG activity, you define the access sequences. The access sequence controls the

sequence of condition tables in which the system accesses those condition tables to find validcondition records.

The DSD back end Output Control Component already contains a pre-customized accesssequence (0001) specifying only one condition table (390 ) to be accessed (Visit Plan Type).This table is ready to be used for the DSD process and should remain unchanged. If you havecreated new condition tables during the previous step, you may need to establish a newaccess sequence.

Procedure

1. Find the procedure for creating an access sequence for output determination for visitlists in Customizing for Logistics Execution under SAP Direct Store Delivery

Output Control Output Control for visit lists Maintain Output Determination for visit

lists Maintain Access Sequences.

2. See the IMG activity documentation.



(C) SAP AG 490

Message Type Maintenance

In this IMG activity, you define the message types that are to be used by the DSD back end

Output Control Component for visit lists. A message might be either printed on paper or sentto an IDoc, likewise, a message might be downloaded separately as a single document orcollectively together with other documents.

The DSD back end Output control for visit lists already contains pre-customized messagetypes that are ready to be used for the DSD process. Each message type has an accesssequence assigned to it. The following message types are available:

DSD1

Message type for EDI

DSD2

Message type used for ALE distribution

DSDP

Message type for collective print output

VL01

Message type for the visit list

The message types mentioned above are delivered with client 000 and should be transportedinto copy clients.

Prerequisites

At least one condition table is defined.

The access sequence is maintained.

Process

This process consists of the following steps:

1. Maintain Message Types for EDI [Page 492]

2. Maintain Message Types Used for ALE Distribution [Page 494]

3. Maintain Message Types for Collective Print Output [Page 496]

4. Maintain Message Types for Visit List [Page 498]

Maintain condition records for each message type maintained in the output determinationprocedure for the visit list.



(C) SAP AG 491

Condition records for visit lists are maintained in the SAP Easy Access screen under

Logistics Logistics Execution Direct Store Delivery Output Control Message Condition

Records Visit List .

If a message can be printed, you also must specify the communication data, that is, theoutput device (use the Communication button during the condition record creation), for each

printout condition record. If a printer is not specified, the system does not create the messagein spite of the maintained condition record.

Result

After message types are defined, condition records can be maintained on the SAP Easy Access screen.



(C) SAP AG 492

Maintain Message Types for EDI

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery OutputControl Output Control for Visit Lists Maintain Output Determination for Visit Lists

, choose Maintain Message Types.



General Data

Access Sequence Choose <Access Sequence>.

Example: 0001 (Visit Plan Type)

Access to Conditions

Mandatory: This checkbox must be selected for the system toknow that the output should be determined using the conditiontechnique. If this checkbox is not selected, the system finds theoutput by using the proposal in the customer master record. Insuch a case, you would need to set the corresponding defaultsfor output determination from the customer master record.

Multiple Issuing

Optional: This checkbox should be selected only in cases wherethe system is required to create a change message for shipmentchanges that occurred after the download had already beenexecuted.

Other CheckboxesThe CannotBeChanged , Partner-indep.output , and Do not write processing log checkboxes remain not selected.

Default Values

Dispatch Time

Choose the desired value (one digit, numeric key). It defines thetime of output processing (example: immediately when saving adocument or during the next selection run).

4 Send immediately (when saving the application)

Transmission Medium Choose 6 (EDI).

Partner function Choose partner function LS (Logical System). The entry definesthe recipient of an output in the SD document.

Communication Strategy Leave blank.

Time/StorageSystem/Print/Mail/SortOrder

Leave all fields blank for these tabs.



(C) SAP AG 493

Values entered for output type, time, and partner function for detail data areautomatically transferred as default values when creating a condition record by outputcondition.

4. Choose Enter , then choose Processing Routines in the left window and choose NewEntries.



Transmed.Medium Choose medium 6 (EDI) from the input help.

Processing1

Program Enter the /DSD/HH_NASTED program name.

FORM Routine Enter the name of the EDI_PROCESSING_DS FORM Routine.

6. Choose Enter , then choose Partner Functions in the left window and choose NewEntries.



Medium Choose medium 6 (EDI) from the input help.

Function Choose partner function LS (Logical System) from the input help.

Name The name is automatically entered depending on the entry for the function.

8. Save your entries and return to the initial screen.



(C) SAP AG 494

Maintain Message Types Used for ALE Distribution

Procedure


, choose Maintain Message Types.




Output Type

Enter an alphanumeric key with up to four digits and adescription to identify the output type.

Example-key: DSD2

Example-description: DSD DOWNLOAD-ALE

General Data

Access Sequence Choose the access sequence from the input help.


Access to Conditions Checkbox must be selected (see comments in MaintainMessage Types for EDI [Page 492]).

Multiple Issuing Checkbox should be selected (see comments in MaintainMessage Types for EDI [Page 492]).

Other CheckboxesCheckboxes remain not selected (see comments inMaintain Message Types for EDI [Page 492]).

Default Values

Dispatch Time

Choose a desired value (one digit, numeric key) from theinput help.


Transmission Medium Choose medium A (ALE) from the input help.

Partner function No entry.

Communication Strategy No entry.

Time / StorageSystem / Print / Mail / SortOrder




(C) SAP AG 495

4. Choose Enter , choose Processing Routines in the left window, and choose NewEntries.



Transm.Medium Choose medium A (ALE) from the input help.

Processing1


FORM Routine Enter the name of the ALE_PROCESSING_DSD FORM routine.

6. Choose Enter, choose Partner Functions in the left window, and choose New Entries.



Medium Choose medium A (ALE) from the input help.


Name The name is automatically entered depending on entry for the function.




(C) SAP AG 496

Maintain Message Types for Collective Print Output

Procedure

1. To create a new message type, in Customizing for Logistics Execution under DirectStore Delivery Output Control Output Control for Visit Lists Maintain Output

Determination for Visit Lists , choose Maintain Message Types.




Output Type

Enter an alphanumeric key with up to four digits and a

description to identify the output type.

Example key: DSDP

Example description: DSD Collected Docs

General Data

Access Sequence Choose an access sequence from the input help.

Example: 0001(Visit Plan Type)

Access to Conditions Checkbox must be selected (see comment in Maintain

Message Types for EDI [Page 492]).

Multiple Issuing Checkbox should be selected (see comment in MaintainMessage Types for EDI [Page 492]).

Partner-indep.output Checkbox should be selected. This means that duringoutput processing, the system allows all partners.

Other checkboxesCheckboxes may remain not selected (see comment inMaintain Message Types for EDI [Page 492]).

Default Values

Dispatch Time

Choose desired value (one digit, numeric key) from the listprovided.

1 Send with periodically scheduled job

Transmission Medium Choose value 1 (Print output) from the input help.





(C) SAP AG 497


Time / StorageSystem / Print / Mail / SortOrder –





Transm. Medium Choose medium for 1 (Print output) from the input help.

Processing1

Program Enter the /DSD/VC_NAST_PRINT program name.

FORM Routine Enter the name of the DSD_PRINT_VL FORM routine.

6. Choose Enter , choose Partner Functions in the left window, and choose New Entries.



Medium Choose medium for 1(Print output) from the input help.

Function Choose partner function SH (Ship-to-Party) from the input help.





(C) SAP AG 498

Maintain Message Types for Visit List

Procedure

1. To create a new message type, in Customizing for Logistics Execution under SAPDirect Store Delivery Output Control Output Control for Visit Lists Maintain Output

Determination for Visit Lists , choose Maintain Message Types.




Output Type

Enter an alphanumeric key with up to four digits and a description toidentify the output type.

Example key: VL01

Example description: DSD Visit List

General Data

Access Sequence Choose an access sequence from the input help.


Access to

Conditions

Mandatory: A checkbox must be selected for the system to knowwhether the output should be determined using the conditiontechnique. If this checkbox is not selected, the system finds the

output by using the proposal in the customer master record. In thiscase, you need to set the corresponding defaults for outputdetermination from the customer master record.

Multiple Issuing

Optional: The checkbox should be selected only in cases where thesystem is required to create a change message for shipmentchanges that occurred after the download had already beenexecuted.

Other CheckboxesThe CannotBeChanged , Partner-indep.output , and Do not write processing log checkboxes are not selected.

Default Values

Dispatch Time

Choose desired value (one digit, numeric key) from the input help. Itdefines the time of output processing (for example, immediately uponsaving a document or during the next selection run).


TransmissionMedium

Choose value 6 (EDI) from the list provided.

Partner function Choose partner function LS (Logical System) from the input help. The



(C) SAP AG 499


entry defines the recipient of an output in the SD document.

CommunicationStrategy

No entry.

Time/StorageSystem/Print /Mail /Sort Order


4. Choose Enter, choose Processing Routines in the left window, and choose NewEntries.



Transm..Medium Choose medium for 1 (Print output) from the input help.

Processing1


FORM Routine Enter the name of the DSD_PRINT_VL FORM routine.




Medium Choose medium for 1 (Print output) from the input help.

Function Choose partner function SH (Ship-to-Party) from the input help.



The message type VL01 is the form for the visit list and must always be maintained within theVL application whenever a visit list should be downloaded as a print output.

Maintain condition records for each message type maintained in the output determinationprocedure for the visit list.

Condition records for visit lists are maintained using the following menu path on the SAP Easy

Access screen: Logistics Logistics Execution Direct Store Delivery Output Control

Message Condition Records Visit List.



(C) SAP AG 500

Maintain Output Determination Procedure

In this IMG activity, you define the procedures for various tour scenarios that the system uses

to determine which output types are allowed for a specific document.

In a sales-oriented process, for example, in a preseller scenario, no shipment is involved.Whenever this is the case, then you need to make sure that the message types for thedownload (for example, DSD1, DSD2 , DSDP , as described in this section) are onlymaintained for the preseller visit plan type in the output determination procedure for visit listsbecause the visit list is the document that triggers this process.

You also need to take care that these message types for the download (DSD1, DSD2, DSDP )are not maintained for the other visit plan types (such as delivery driver, van seller, or mixed

driver) in the output determination procedure for visit lists because for these other visit plantypes (for example, delivery driver, van seller, and mixed driver), the download of the visit listis triggered from the shipment.

ScenarioForm of

Download

ApplicationTriggering

the Process

MessageTypes to

BeProcessed

Scope of Download

Preseller IDocs VL

DSD1 (EDI)

or

DSD2 (ALE)

IDocs according to CustomizingOutput Control for Visit Lists:Define Scope of Data Transfer .

Examples:

/DSD/HH_ITINERARY

ORDRSP

Printoutput

VL DSDP

Individual messages according toCustomizing Output Control forVisit Lists: Determine IndividualMessages to be processed .

Examples:

VL-VL01 (Visit List)

V1-BA00 (OrderConfirmation)

All IDocs must be defined as outbound parameters for the corresponding partner.

Output determination must be set up for all individual messages that are printed out in order

for them to be created within the application (for example, V1 –

an order confirmation wascreated when saving the order ) and to be ready in the system for further processing (time 3).



(C) SAP AG 501

Prerequisites

Output types are defined.

Procedure


, choose Maintain Output Determination Procedure.



FieldName


Procedure

Enter an alphanumeric key with up to six characters to identify the newprocedure.

Example: PRE001

Descript. Enter a description for the new procedure.

Example: Procedure for Preseller

4. Choose Enter, select the entry and choose Control in the left window. A table controlappears in the right window.

5. Choose New Entries and enter the following data:


Step Enter a two digit number for each output type that you are going to maintainin the table. Start with the number ten and continue in increments of ten.This number determines the sequence of the conditions within a procedure.

Cntr Enter a two digit access number of the conditions within a step. Start withnumber ten with increments of ten.

CTyp

From the input help, choose an appropriate output type that the systemshould consider within the new procedure.

Example: VL01 DSD Visit List

Description Is entered automatically depending on the chosen output type.

Requirement No entry.

Manual Only

No entry.

Conditions with this checkbox selected are only included in outputdetermination if they are entered manually or if they are transferred from anexternal process.

Repeat step 5. and enter all output types that you wish to be considered within theprocedure concerned (such as output types DSD1, DSD2 , DSDP , and VL01).




(C) SAP AG 502

Repeat steps 2. through 6. for additional procedures. We recommend maintaining aseparate procedure for each different tour scenario, that is, for the preseller scenario,delivery driver scenario, and van seller scenario with the corresponding output types.

Result

You have defined various output determination procedures ready to be assigned to visit plantypes.



(C) SAP AG 503

Assign Output Determination Procedures

In this IMG activity, you assign output determination procedures to specific visit plan types.

Visit list are based on visit plan types and visit plan types are specifically customized fordifferent tour scenarios, for example, preseller, delivery driver, van seller, and mixed driver(see Visit Control Configuration [Page 293], menu option Define Visit Plan Types [Page 299]).

In this assignment table, scenario-specific visit plan types are linked to scenario-specificoutput determination procedures and thus can determine which output types for whichmedium should be downloaded at what time.

Prerequisites

Visit plan types are defined.

Output determination procedures are defined.


Procedure


Control Output Control for Visit Lists Maintain Output Determination for Visit Lists

, choose Assign Output Determination Procedure.

2. On the screen that appears, locate the entry that shows the visit plan type that youwant to assign an output determination procedure to (for example, PRESELLER ).

3. In the OutDetProc field for that visit plan type, select an output determination

procedure from the input help (for example, PRE001).

This step is optional: in the OutputType field for that visit plan type, specify an outputtype that is displayed in a dialog box whenever you have more than one document toprint and want to preview them. The system takes the output type, entered here asdefault, to be displayed first.

If you have more than one visit plan type, repeat steps 2. through 4. for each visitplan type.


Result

Maintenance of condition tables, access sequences, message types, and outputdetermination procedures as well as the assignment of output determination procedures tovisit plan types comprise the general Customizing settings for the output determination forvisit lists.

With the assignment of the output determination procedures to visit plan types maintained,the system is now set up to determine the appropriate output types for each visit list.



(C) SAP AG 504

Print Output and Download from Visit List

In this section, you maintain the necessary Customizing settings that enable the system to

handle specific output determination situations. The settings also define the scope of datatransfer, thus informing the system in more detail about the extent of the data to bedownloaded.

Process

These settings are available in Customizing for Logistics Execution under SAP Direct Store

Delivery Output Control Output Control for Visit Lists Print Output and Download from Visit

Lists.

To use this function, it is necessary to maintain the following customizing tables:

1. Define Message Types [Page 505]

2. Download: Define Scope of Data Transfer [Page 506]

3. Print Output: Determine Messages for Processing [Page 508]



(C) SAP AG 505

Define Message Types

If you want to change a previously downloaded or printed (collective printout) visit list, you are

informed about the status before making any changes. Only messages entered in thisCustomizing table are checked for successful processing while checking the visit lists,whether they have already been downloaded or printed out.

In addition, this table is required in the transaction for message processing( /DSD/VC_MESSAGES) to trigger listing of individual messages. If the message type for thecollective printout is not entered in this table, it is not possible to add the correspondingindividual messages to the message display.

Prerequisites

You have defined message types (for EDI, for ALE, for collective printout).

Procedure


Control Output Control for Visit Lists Print Output and Download from Visit Lists ,choose Define Message Types.



FieldName


OutputType

Enter all message types that are setup for the EDI download (medium 6 ), for the ALE download (medium A), and for the printout (medium 1).

Descript. Entered automatically depending on output type chosen.


For printout message types (medium 1), only maintain the message type for collectiveprintouts.

Result

All message types entered are considered by the system when checking for a successfuldownload or printout prior to making changes to an already downloaded visit list.



(C) SAP AG 506

Download: Define Scope of Data Transfer

In this IMG activity, you are allowed to control which data (message types, IDocs) is

transferred. In order for the system to be able to do this, you must enter all data that shouldbe processed further in this Customizing table. The download program reads the Customizingtable and calls the relevant function module (FUNCMOD field) for all entries (message types)that are maintained for the visit plan type.

In this table, you need to maintain entries only in those cases where IDocs should be created.This means, that concerns all those cases where messages should be created for visit lists ofa given visit plan type that are to be sent by medium 6 (EDI) or A (ALE). For printoutmessages, no entries are needed in this table.

PrerequisitesYou have defined visit plan types.

Procedure


Control Output Control for Visit Lists Print Output and Download from Visit Lists ,choose Download: Define Scope of Data Transfer.




Visit Plan Type Enter the name of a visit plan type.

Example: PRE

Message Type

Enter the name of a message type for the transmitted shippingdata (see the list below step 4. of this procedure).

Example: /DSD/HH_ROUTE_ITINERARY

DSD: Extent of Data toTransfer from VisitList

Basic Type Select the basic type for the selected message type (see the listbelow step 4. of this procedure).

FM name Select the function module for the selected message type/basictype (see the list below step 4. of this procedure).


For the relevant visit plan types, maintain the following message types (steps 2. through 4.)

with:



(C) SAP AG 507

Message Type

/DSD/HH_ROUTE_ITINERARY

DESADV

ORDRSP

SHPMNT

The corresponding basic type and function modules for the listed message types are asfollows:

Basic Type Function Module

/DSD/HH_ROUTE_ITINERARY03

Make sure that you have selected the correctbasic type (with ending 03). Only this versioncontains the segments required to downloadcustomer or visit texts to the mobile device andmake them visible as driver messages.

/DSD/VC_HH_DL_ROUTE_ITINERAR Y

DELVRY03 /DSD/VC_HH_DL_DELIVERY

ORDERS05 /DSD/VC_HH_DL_SALES_ORDER

SHPMNT05 /DSD/VC_HH_DL_SHIPMENT

The /DSD/HH_CONTROL control IDoc is always sent. Therefore, you do not need to enter itin the table.

Result

For the message types maintained for a given visit plan type, the download program nowknows which function module to call for the data transfer.



(C) SAP AG 508

Print Output: Determine Messages for Processing

In this IMG activity, you define which documents should be created for each visit plan type for

the print output when processing the collective message. In this Customizing table, youmaintain entries for all message types of DSD relevant applications that have individualmessages that are printed during the processing of the collective print output.

In this table, you need to maintain entries only in those cases where a collective print outputshould be created. In other words: entries are needed only in cases where messages shouldbe created for visit lists of a given visit plan type that are to be created according to messagetype DSDP . If only IDocs should be created, then you do not need to maintain entries in thistable.

Prerequisites You have defined visit plan types.

SAP standard output determination for sales documents (V1) must have beenconfigured with all the message types that should be created (for example, orderconfirmation). The processing time of these individual messages must have been setto 3 (Send using application-specific transaction).

You have defined condition records for output types for sales documents.

You have setup the SAP standard output determination for outbound deliveries (V2 )

with all message types that should be created (for example, delivery note). You have

set the processing time of these messages to 3 (Send using application-specifictransaction).

You have defined condition records for output types for outbound deliveries.

You have setup the SAP standard output determination for billing documents (V3)with all message types that should be created (for example, invoice). You have setthe processing time of these messages to 3 (Send using application-specifictransaction).

You have defined condition records for output types for billing documents.

SAP Standard Output Determination for Visit List (VL) are set up with all the message

types that should be created (for example, message type VL01). The processing timeof these individual messages must have been set to 3 (send using application-specific transaction).

Condition records for output types for the visit list (for example, VL01) are defined.

Procedure


Control Output Control for Visit Lists Print Output and Download from Visit Lists ,choose Print Output: Determine Individual Messages to Be Processed.





(C) SAP AG 509


Visit Plan Type

Enter the name of the visit plan type to setup the individualmessage determination.

Example: PRE

Sequence Number

Enter a sequential number. The sequence number is allocated toeach message type to control the sequence in which thedocuments for each customer will be printed.

Example: 1

Application Select an application from the input help.

Example: VL

Output Type

Select an output type from the input help.

Example: VL01

DSD: Message Typefor Print Output forEach Visit List

Different Printer

Not selected.

This checkbox is selected only when a document needs to beprinted on a specific printer.

If this checkbox is not selected, then print parameters for the

collective message are adopted for each individual message thatare to be processed; in this way, all documents can be assigned toone spool request.


Result

If a collective print output message has been created during visit list creation, you canprocess this collective printout message by running the /DSD/VC_RSNAST00 report. Thesystem looks into this Customizing table and collects all messages it finds for a given visitplan type to have them processed collectively. The system triggers printing the documents ina logical preset sequence on the printer maintained in the condition record of the collective

output type.



(C) SAP AG 510

Output Control for Shipments

The output control for shipments is used within the logistics-oriented business process to

provide the driver with all the documents that are needed on the tour.

The driver may function in different roles: either as pure delivery driver (only deliveringproducts to customers based upon pre-sold orders), as a van seller (selling products from thevehicle without pre-sold orders existing), or as a mixed role driver (delivering pre-orderedproducts and selling products to customers from the vehicle without an existing order).Depending on the role, the driver needs various documents (for example, delivery notes,shipping documents, or freight list for export) for the tour. The output control for shipmentsmakes sure that the whole set of documents is being produced at the right time in the rightform (printed or per IDoc).

In the case of shipments, only the data download is controlled by the V7 application.

Prerequisites

The visit plan type used is set in such way that the shipment is the leading document. Thismeans that under Relevant Documents, the three checkboxes must be selected in one of thefollowing combinations depending on the driver role:

Delivery driver

Select the Shipping Document and Ship Delivery checkboxes.

Van seller

Select the Flag Visit List Document and Shipping Document checkboxes.

Mixed role

Select all three checkboxes.

Process

The procedures for this process are in Customizing for Logistics Execution under SAP

Direct Store Delivery Output Control Output Control for Shipments .


1. Output Determination for Shipments [Page 511]

2. Print Output and Download from Shipment [Page 528]



(C) SAP AG 511

Output Determination

The DSD back end Output Control uses the condition technique of the SAP ERP system.

This section deals with all those Customizing settings that are necessary for the system tofind the correct output types and messages connected with a specific shipment. The outputdetermination for shipments determines which conditions need to be met and if they are met,which message type(s) should be created for a given shipment, at what time, and in whichform (printed or IDoc).

Saving a shipment triggers this process of finding the correct message types.

Process

The Customizing tables for this process are located in Customizing for Logistics Execution

under SAP Direct Store Delivery Output Control Output Control for Shipments Maintain

Output Determination for Shipments.

Customizing this function consists of the following steps:

1. Maintain Condition Tables [Page 512]

2. Maintain Access Sequences [Page 513]

3. Output Types Maintenance [Page 514]

4. Assign Output Types to Partner Functions [Page 523]

5. Maintain Output Determination Procedure [Page 524]

6. Assign Output Determination Procedure [Page 527]



(C) SAP AG 512

Maintain Condition Tables

In this IMG activity, you define the condition tables for output condition records. Here, you

define the combination of fields for which you want to create output condition records in acondition table. In this way, you can control output determination depending on your specificcombination of fields.

The DSD back end output control component already contains the condition tables (017 , 022 ,023, and 045 ) to be used for the DSD process. These should not be changed. If you want tomake changes, you should create new condition tables by copying similar, already existingcondition tables and making the necessary changes.

Procedure

1. To create a new condition table for DSD output control (shipments), in Customizingfor Logistics Execution under SAP Direct Store Delivery Output Control Output

Control for Shipments Maintain Output Determination for Shipments , chooseMaintain Condition Tables.

2. Choose Maintain Output Condition Table for Shipments.



Table

Enter a name (3 digit number) for the new condition table to be created.Remember that you may only choose names between 900 and 999.

Example: 900

Copy fromCondition

Table Leave blank.

4. Choose Enter .

Enter a description for the new condition table.

Select the desired fields for the condition table from the list of allowed fields.

Example: TRANSPORTATION PLANNING POINT and ROUTE .

5. Generate the new condition table

Result

You have now defined a new condition table for which you can maintain condition records.



(C) SAP AG 513

Maintain Access Sequences

In this IMG activity, you define the access sequences. The access sequence controls the

sequence of condition tables in which the system accesses those condition tables in order tofind valid condition records.

The DSD back end output control component already contains pre-customized accesssequences (0001 – Shipment Type, 0002 – Transportation Planning Point and ShipmentType, 0003 – Transportation Planning Point/Transportation Processing Type/Forwarding

Agent, 0004 – Shipment Type and Forwarding Agent) that are ready to be used for the DSDprocess. These should remain unchanged. If you have created new condition tables duringthe previous step, you may need to establish a new access sequence.

Procedure

1. To create an access sequence for output determination for shipments, in Customizing

for Logistics Execution: SAP Direct Store Delivery Output Control Output Control

for Shipments Maintain Output Determination for Shipments , choose Maintain Access Sequences.

2. See the IMG activity documentation.



(C) SAP AG 514

Output Type Maintenance

In this IMG activity, you define the output types that are to be used by the DSD back end

Output Control component for shipments. A message might be either printed on paper or sentto an IDoc; likewise, a message might be downloaded separately as a single document orcollectively together with other documents.

The DSD back end output control for shipments already contains pre-customized output typesthat are ready to be used for the DSD process. Each output type has an access sequenceassigned to it. The following output types are available:

DSD1

Output type for EDI

DSD2

Output type used for ALE Distribution

DSDP

Output type for collective print output

The message types mentioned above are delivered with client 000 and should be transportedin copy clients..

Prerequisites At least one condition table is defined.

The access sequence is maintained.

Process

The Customizing tables for this process are found in Customizing for Logistics Execution

under SAP Direct Store Delivery Output Control Output Control for Shipments Maintain

Output Determination for Shipments Maintain Output Types.

This process consists of the following steps:

1. Maintain Output Types for EDI [Page 516]

2. Maintain Output Types Used for ALE Distribution [Page 519]

3. Maintain Output Types for Collective Print Output [Page 521]

Maintain condition records for each message type maintained in the output determinationprocedure for the shipment.

Condition records for shipments are maintained using the SAP Easy Access menu under

Logistics Logistics Execution SAP Direct Store Delivery Output Control Message

Condition Records Shipment .



(C) SAP AG 515

If a message is to be printed, you must specify the communication data, that is, the outputdevice (use the Communication button during the condition record creation), for each printoutcondition record. If a printer is not specified, the system does not create the message despitethe maintained condition record.

Result

With the output types defined, the condition records can now be maintained on the SAP Easy Access screen.



(C) SAP AG 516

Maintain Output Types for EDI

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery OutputControl Output Control for Shipments Maintain Output Determination for Shipments

, choose Maintain Output Types.




Output Type


Example key: DSD1

Example description: DSD DOWNLOAD-EDI

General Data

AccessSequence

Choose the access sequence from the input help.

Example: 0002 (Transportation Planning Point and Shipment Type)

Access to

Conditions

Mandatory: The checkbox must be selected for the system to knowwhether the output should be determined using the condition technique. Ifthis checkbox is not selected, the system finds the output by using the

proposal in the customer master record. In such cases, you need to setthe corresponding defaults for output determination from the customermaster record.

Multiple Issuing

Optional: The checkbox should be selected. This enables the system tocreate a change message for shipment changes that occurred after thedownload had already been executed. It is then possible to process thechanged message again with the same report.

OtherCheckboxes

The CannotBeChanged , Partner-indep.output , and Do not write processing log checkboxes remain not selected.

Default Values

Dispatch Time

Choose the desired value (one digit, numeric key) from the list provided.It defines the time of output processing (for example, immediately whensaving a document or during the next selection run).


TransmissionMedium

Choose 6 (EDI) from the input help.

Partner function Choose partner function LS (Logical System) from the input help. The



(C) SAP AG 517


entry defines the recipient of an output in the SD document.


No entry.

Time Leave all fields blank.

StorageSystem

Storage Mode Choose value 1 (Print only) from the input help.

Document Type No entry.

Print

Print param. Choose print parameter 8 (Transportation Planning Point) from the inputhelp.

Mail / SortOrder

Leave all fields blank.

Values entered for output type, time, and partner function for detail data areautomatically transferred as default values when creating a condition record by outputcondition.




Transmed.Medium Choose medium 6 (EDI) from the input help.

Processing1


FORM Routine Enter the name of the EDI_PROCESSING_DSDFORM routine.



FieldName


Medium Choose medium 6 (EDI) from the input help.




(C) SAP AG 518

FieldName


Name The name is automatically been entered depending on the entry for thefunction.




(C) SAP AG 519

Maintain Output Types Used for ALE Distribution

Procedure






Output Type


Example key: DSD2

Example description: DSD DOWNLOAD-ALE

General Data

Access Sequence Select the access sequence from the input help.

Example: 0002 (Transportation Planning Point and Shipment Type)

Access to Conditions This checkbox must be selected (see Maintain Output Types for EDI[Page 516]).

Multiple Issuing This checkbox must be selected (see Maintain Output Types for EDI[Page 516]).

Other CheckboxesThese checkboxes remain not selected (see Maintain Output Typesfor EDI [Page 516]).

Default Values

Dispatch Time

Choose a desired value (one digit, numeric key) from the input help.


TransmissionMedium

Choose the medium A (ALE) from the list provided.



No entry.

Time Leave all fields blank.

Storage System



(C) SAP AG 520


Storage Mode Choose 1 (Print only) from the input help.

Document Type No entry.

Print

Print param. Choose the print parameter 8 (Transportation Planning Point) fromthe input help.

Mail / Sort Order Leave all fields blank for these tabs.




Transm. Medium Choose the medium A (ALE) from the input help.

Processing1


FORM Routine Enter the name of the ALE_PROCESSING_DSD FORM routine.




Medium Choose medium A (ALE) from the input help.






(C) SAP AG 521

Maintain Output Types for Collective Print Output

Procedure






Output Type

Enter an alphanumeric key with up to four digits and a

description to identify the output type.

Example key: DSDP

Example description: DSD Collected Docs

Tab General Data

Access Sequence Choose the access sequence from the input help.

Example: 0001 (Shipment Type)

Access to Conditions Checkbox must be selected (see Maintaining Output Types

for EDI [Page 516]).

Multiple Issuing Checkbox must be selected (see Maintaining Output Typesfor EDI [Page 516]).

Partner-indep.output Checkbox must be selected. This means that during outputprocessing, the system allows all partners.

Other CheckboxesCheckboxes may remain not selected (see MaintainingOutput Types for EDI [Page 516]).

Default values

Dispatch Time

Choose desired value (one digit, numeric key) from the listprovided.

1 Send with periodically scheduled job

Transmission Medium Choose 1 (Print output) from the input help.





(C) SAP AG 522


Time / StorageSystem / Print / Mail / SortOrder





Transm. Medium Choose medium 1 (Print output) from the input help.

Processing1


FORM Routine Enter the name of the DSD_PRINT_V7 FORM routine.

6. Chose Enter , choose Partner Functions in the left window, and choose New Entries.



Medium Choose the medium for 1 (Print output) from the input help.

Function Choose the partner function CR (Forwarding Agent) from the input help.



Result

With the output types defined, the condition records can now be maintained in the SAP Easy Access screen.



(C) SAP AG 523

Assign Output Types to Partner Functions

In this IMG activity, you define the allowed output types to partner functions. In addition, you

can also specify which type of processing is allowed for the combination of output types andpartner functions.

Prerequisites


Procedure

1. To maintain a new procedure for output determination, in Customizing for Logistics

Execution under SAP Direct Store Delivery Output Control Output Control for

Shipments Maintain Output Determination for Shipments , choose Assign Output

Types to Partner Functions.




Out. Choose a previously defined output type from the input help.

Example: DSD1 (DSD Download – EDI)

Med

Choose the allowed partner function from the input help.

Example: LS Logical System

Funct Specify an output medium (printout, fax, EDI).

Example: 6 (EDI)

4. Choose Enter and repeat step 3. for each output type you want to assign to a partner

function.


Result

Once all the necessary output types are assigned, the table provides an overview of whichoutput types are allowed for which partner functions.



(C) SAP AG 524

Maintain Output Determination Procedure

In this IMG activity, you define the procedures for different tour scenarios that the system

utilizes to determine which output types are allowed for a specific document.

In a logistics-oriented process, there is always a shipment involved. Whenever this is thecase, you need to make sure that the message types for the download (for example DSD1,DSD2, DSDP – described in this section) are maintained in the output determinationprocedure for shipments. This is because the shipment is the document that triggers thisprocess.

At the same time, you also need to make sure that these message types for the download(DSD1, DSD2, DSDP ) are not maintained in the output determination procedure of the

corresponding visit plan type.

ScenarioForm of

Download

Application

triggering the

process

MessageTypes to

beprocessed

Scope of Download

Vanseller,DeliveryDriver,MixedRoleDriver

IDOCs V7

DSD1

(EDI) or

DSD2

(ALE)

IDocs according to CustomizingOutput Control for Shipments:Specify Volume of TransmittedData.

Examples:

/DSD/HH_ITINERARY

ORDRSP

DESADV

Print output V7 DSDP

Individual messages according toCustomizing Output Control forShipments: Determine IndividualMessages to be processed .

Examples:

VL-VL01 (Visit List)

V1-BA00 (Orderconfirmation)

V2-LD00 (Delivery Note)

.

All IDocs must be defined as outbound parameters for the corresponding partner.



(C) SAP AG 525

The output determination must have been correctly set up for individual messages that areprinted out, in order for the message to be created successfully within its own application (forexample, V1 – an order confirmation was created when saving the order ) and to be ready inthe system for further processing (time 3).

Prerequisites


Procedure


Control Output Control for Shipments Maintain Output Determination for Shipments

, choose Maintain Output Determination Procedure.



FieldName


Procedure

Enter an alphanumeric key with up to 6 characters to identify the newprocedure.

Example: V7SHIP

Descript. Enter a description for the new procedure.

Example: Transportation Output

4. Choose Enter , select the entry, and choose Control in the left window. A table control

appears in the right window.

5. Choose New Entries and enter the following data:


Step Enter a two digit number for each output type that you are going to maintainin the table; start with number 10 with increments of 10. This number

determines the sequence of the conditions within a procedure.

Cntr Enter a two digit access number of the conditions within a step; start withnumber 10 with increments of 10.

CTyp

From the input help, choose an appropriate output type that the systemshould consider within the new procedure.

Example: DSDP DSD collected DOCs

Description Is entered automatically depending on the output type chosen.

Requirement No entry.



(C) SAP AG 526


Manual Only

No entry.

Conditions with this checkbox selected are only included in output

determination if they are entered manually or if they are transferred from anexternal process.

Repeat step 5. and enter all output types that you wish to be considered within theprocedure concerned (such as output types DSD1, DSD2 , DSDP ).


Repeat steps 2. through 5. for additional procedures. It is recommended that youmaintain a separate procedure for each tour scenario, that is, for the presellerscenario, the delivery driver scenario, and the van seller scenario with the outputtypes.

ResultYou have defined various output determination procedures ready to be assigned to shipmenttypes.



(C) SAP AG 527

Assign Output Determination Procedure

In this IMG activity, you assign output determination procedures to specific shipment types.

Shipments are created with a specific shipment type and shipment types are specificallycustomized for different tour scenarios (preseller, delivery driver, van seller, and mixed roledriver).

In this assignment table, shipment types are linked to scenario-specific output determinationprocedures. Thus, the system can determine which output types in which medium should bedownloaded at what time.

Prerequisites

Shipment types are defined.

Output determination procedures are defined.


Procedure


Control Output Control for Shipments Maintain Output Determination for Shipments

, choose Assign Output Determination Procedure.

2. On the screen that appears, locate the entry that shows the shipment type to whichyou want to assign an output determination procedure (for example, M001).

3. In the OutDetProc field for that shipment, select the output determination procedure

from the input help that you wish to assign (for example, V7SHIP ).

This step is optional: in the OutputType field for that shipment type, specify an outputtype that will be displayed in the dialog box whenever you have more than onedocument to print and want to preview them. The system will take the output typeentered here as default, to be displayed first.

If you have more than one shipment type, repeat steps 2. through 4. for eachshipment type.


Result

Maintenance of condition tables, access sequences, message types, and outputdetermination procedures as well as the assignment of output determination procedures toshipment types comprise the general Customizing settings for the output determination forshipments.

With the assignment of the output determination procedures to shipment types maintained,the system is now set up to determine the appropriate output types for each shipmentconcerned.



(C) SAP AG 528

Print Output and Download from Shipment

In this section, you maintain the necessary Customizing settings that enable the system to

handle specific output determination situations. The settings also define the scope of datatransfer, thus informing the system in more detail about the extent of the data to bedownloaded.

Process

You can find the procedures for this process in Customizing for Logistics Execution under

SAP Direct Store Delivery Output Control Output Control for Shipments Print Output

and Download from Shipment .


1. Define Message Types [Page 529]

2. Specify Volume of Transmitted Shipping Data [Page 530]

3. Print Output: Determining Individual Messages for Processing [Page 532]



(C) SAP AG 529

Define Message Types

If a shipment was already downloaded or printed (collective printout) but needs to be

changed, then you are informed of its status before making the change. During checkingwhether or not download or printout of the shipment has already been performed, only thosemessages that are entered in this Customizing table are checked for successful processing.

Messages are only processed (that is, IDocs and printouts are only created) if the shippingstatus entered in this table has been reached. If this is not the case when the messages areto be processed, then processing is terminated with a message in the processing log.

In addition, this table is also used in the transaction for message processing( /DSD/VC_MESSAGES) to trigger listing of individual messages. If the message type for thecollective printout is not entered in this table, it is not possible to add the correspondingindividual messages to the message display.

Prerequisites

Message types (for EDI, for ALE, for collective printout) are defined.

Procedure


Control Output Control for Shipments Print Output and Download from Shipments

, choose Define Message Types.




Output Type Enter all message types that are set up for the EDI download(medium 6 ), for the ALE download (medium A), and for the printout(medium 1).

Descript. Entered automatically depending on output type chosen.

OverallTransportationStatus

Determine the minimum shipment status that must be reached forIDOCs or a collective printout to be created.


For printout message types (medium 1), maintain only the message type for collectiveprintouts.

Result

All message types entered are considered by the system when checking a successfuldownload or printout prior to making changes to a previously downloaded shipment.



(C) SAP AG 530

Specify Volume of Transmitted Shipping Data

In this IMG activity, you maintain all message types that are necessary for the download of

transactional data (messages types and IDocs) in a shipment. In other words: transactionaldata is transferred to the handheld middleware server only if the respective message type hasbeen entered in this Customizing table. The download of the shipment is controlled by theOutput Determination function.

The various message types are maintained depending on shipment types and transportationplanning types.

The /DSD/HH_IDOC_OUTPUT_CONTROL program reads this Customizing table and callsthe respective function module (funcmode field) for all entries (messages types) that havebeen maintained for the shipment type and the transportation planning point.

In this table, you need to maintain entries only in those cases where IDocs are created. Inother words, only in cases where output types should be created for shipments of a givenshipment type to be sent by medium 6 (EDI) or A (ALE). If you only wish to create printoutput, then you do not need to maintain entries here.

Prerequisites


Transportation planning points are defined.

Procedure1. In Customizing for Logistics Execution under SAP Direct Store Delivery Output

Control Output Control for Shipments Print Output and Download from Shipment ,choose Specify Volume of Transmitted Shipping Data.




Shipment type

Enter the name of a shipment type.

Example: 0001

TransportationPlanning Point

Enter the name of a transportation planning point.

Example: 1001

Message Type

Enter the name of a message type relevant for the transmittedshipping data.

Example: /DSD/HH ROUTE ITINERARY

Basic Type

Select the appropriate basic type to the selected message type (list

below step 4. of this procedure).



(C) SAP AG 531


Function modulename

Select the appropriate function module for the selected messagetype/basic type (list below step 4. of this procedure).


For the relevant combinations of shipment types and transportation planning points,maintain the following message types (steps 2. through 4.):

o /DSD/HH_ROUTE_ITINERARY

o DESADV

o ORDRSP

o SHPMNT

The basic type and function modules for these message types are:

Basic Type Function Module

/DSD/HH_ROUTE_ITINERARY03

Make sure that you have selected the correctbasic type (with ending 03). Only this versioncontains the segments required to downloadcustomer or visit texts to the mobile device andmake them visible as driver messages.

/DSD/HH_DL_FM_ROUTE_ITINERAR Y

DELVRY03 /DSD/HH_DL_FM_DELIVERY

ORDERS05 /DSD/HH_DL_FM_SALES_ORDER

SHPMNT05 /DSD/HH_DL_FM_SHIPMENT

The /DSD/ HH_CONTROL control IDoc is always sent. Therefore, you need not enterit in the table.

Result

For the message types that have been entered in the /DSD/HH_TRADAT Customizing table,the /DSD/HH_IDOC_OUTPUT_CONTROL download program creates the IDocs. If there are

no entries (for the transportation planning point and the shipment type), optional data is nottransferred.



(C) SAP AG 532

Print Output: Determine Individual Messages forProcessing

This menu item concerns the collective print output. In this IMG activity, for each combinationof shipment type and transportation planning point, you define which documents the systemshould create, that is, print collectively, when processing the collective message. In otherwords, in this Customizing table you maintain all message types of DSD-relevant applications(V1-Sales and Distribution, V2-Shipping , V3-Billing , V7-Transportation, VL-Visit List ) for theindividual messages you want to print during the processing of the collective print output.

In this table, you need to maintain entries only in those cases where a collective print outputshould be created. In other words: entries are needed only in cases where messages shouldbe created for shipments of a given shipment type that are be created according to message

type DSDP. If only IDocs are created, then you do not need to maintain entries in this table.

Prerequisites


Transportation planning points are defined.

SAP standard output determination for sales documents (V1) is set up with allmessage types that should be created (for example, order confirmation). Theprocessing time of these individual messages is set to 3 (Send using application-specific transaction).

Condition records for output types for sales documents are defined.

SAP standard output determination for outbound deliveries (V2 ) is set up with all themessage types that should be created (for example, delivery note). The processingtime of these individual messages is set to 3 (Send using application-specifictransaction).

Condition records for output types for outbound deliveries are defined.

SAP standard output determination for Visit List (VL) is set up with all the messagetypes that should be created (for example, message type VL01). The processing timeof these individual messages is set to 3 (Send using application-specific transaction).

Condition records for output types for the visit list (for example, VL01) are defined.

Procedure


Control Output Control for Shipments Print Output and Download from Shipments

, choose Print Output: Determine Individual Messages to Be Processed.





(C) SAP AG 533


Shipment Type

Enter the name of the shipment type that you want to set up forindividual message determination.

Example: 0001

Transportation PlanningPoint

Enter the name of the transportation planning point that you wantto set up for individual message determination.

Example: 0001

Sequence Number

Enter a sequential (consecutive) number. The sequence numberis allocated to each message type in order to control thesequence in which the documents for each customer are printed.

Example: 1

Application Select application V1 from the input help.

Output Type Select an output type from the input help.

Example: BA00

DSD: Message Typefor Print Output forEach Visit List

Different Printer

Not selected.

This checkbox is selected only when a document needs to be

printed by a particular printer.

If this checkbox is not selected, then print parameters for thecollective message are adopted for each individual message thatis to be processed. In this way, all documents can be assigned toone spool request.


Result

If a collective print output message has been created during shipment creation, you canprocess this collective printout message by running the /DSD/VC_RSNAST00 report. The

system looks into this Customizing table and collects all messages it finds for a givencombination of shipment type and transportation planning point to have them processedcollectively. This means that the system triggers the printing of the documents in a logicalpreset sequence on the printer maintained in the condition record of the collective output type.



(C) SAP AG 534

Valuated Delivery Note

The valuated delivery note is a printed delivery note that also contains up-to-date product

prices and an empties block for the customer. The data is being determined within a specificprinting program by means of a pro-forma invoice. This means that the printing program waitsuntil the system has determined the data and subsequently prints the valuated delivery note.This process takes place at the time of delivery creation.

The functionality valuated delivery note is integrated into the SAP standard output control forshipping.

Process

1. The Customizing tables for this process are located in Customizing for Logistics

Execution under SAP Direct Store Delivery Output Control Valuated Delivery

Note .

2. To use this function, it is necessary to configure Assign Shipping Messages andBilling Types [Page 535].



(C) SAP AG 535

Assign Shipping Messages and Billing Types

In this IMG activity, you assign a pro-forma billing document type to a specific output type for

the valuated delivery note. Due to the assignment, a specific printing program to a specificform, the system triggers the creation of a pro-forma invoice when the delivery is saved. Thepricing data, as well as the information regarding empties on the pro-forma invoice, is addedto the valuated delivery note.

Prerequisites

SAP standard output determination for outbound deliveries (V2 ) is maintained with allthe message types that must be created, including the output type for the valuateddelivery note. The processing time of these individual messages is set to 3 (Send

using application-specific transaction).

Condition records for the output type of valuated delivery notes is defined.

Billing types for pro-forma invoices is defined.

Copy control delivery for pro-forma invoices is maintained.

Procedure

1. In Customizing for Logistics Execution SAP Direct Store Delivery Output Control

Valuated Delivery Note , choose Assign Shipping Messages/Billing Type.




Cond. Type Enter the name of the output type for the valuated delivery note.

Bill. Type Enter the name of a pro-forma billing document.

Name Is entered automatically depending on the selected output type.

Description Is entered automatically depending on the selected billing type.

The assigned pro-forma billing document type must be delivery-related.


Result

For all output types maintained in this table with a pro-forma billing document assigned tothem, the system creates a pro-forma billing document in the background from where itobtains the up-to-date pricing data for the valuated delivery note before printing the valuateddelivery note.



(C) SAP AG 536

DSD Reload

The DSD Reload/Unload function is used to load additional materials, as well as to unloadmaterials that are no longer needed, to and from the truck during a tour. The reload/unloadquantities are transferred to the device via the reload synchronization. This updates thematerial inventory without sending the complete tour data. If the reload synchronization doesnot return any discrepancies, a reload sales order and a reload delivery are createdautomatically for each reload activity in the back end (with the driver as customer) for allloaded and unloaded materials.

If the Stock Visibility function has been activated and configured for the respective scenario,all unloaded quantities of the reload delivery are transferred from the truck stock storagelocation to the regular storage location defined in the reload delivery. At the same time, allquantities that are reloaded are transferred from the regular storage locations defined in thedelivery to the truck stock storage location.

Optionally, the DSD reload/unload process may include the Loading Confirmation function,depending on the Customizing settings in the tour status profile. In this case, a dialog boxappears during the reload as soon as the reload status is R . The user can then decidewhether or not loading confirmation should take place for this reload sequence. If so, thereload status L (loading confirmation to be executed) is set and the respective loadingconfirmation header dataset is created.

Furthermore, the reload functionality can be used together with Occasionally ConnectedScenario. If you want to assign new deliveries to an already downloaded tour, such quantitiescan be used as a reload proposal.

In the reload function, only the materials that were in the shipment are allowed to be entered.

It is possible to change the list of allowed materials by implementing theGET_ALLOWED_MATERIALS method of the /DSD/SV_RELOAD BAdI .

Integration

Prerequisites

You need to enable the reload function for each tour scenario if you want to have thereload menu available on a mobile device.

You need to maintain correct tour status profiles if you want to use the loadingconfirmation function within the reload process.

You need to ensure that all Stock Visibility (SV) prerequisites for Reload are met, ifyou want to use the stock visibility function within the reload process.

You must activate the parameter RLD_COCI and RLD_COCI_CG in Customizing forGlobal Device to enable reload check-out and reload check-in on the mobile device,with or without using counting groups.

You must create specific sales order types to be used for the reload.

The sales order types used for reload cannot be maintained for immediate deliveries.



(C) SAP AG 537

Process

The Customizing tables for this process are located in Customizing for Logistics Execution

under SAP Direct Store Delivery Reload and comprise the following activities:

1. Maintain Destination of DSD Connector [Page 538]

2. Define Activity Types and their Assignment to Order Types [Page 539]

3. Configure Order Type Determination [Page 540]



(C) SAP AG 538

Maintain Destination of DSD Connector

Reload data is transferred via an RFC destination. During the reload transaction, the system

must check the tour status in the DSD Connector and must know the correct RFC destination.

In this IMG activity, you therefore maintain the logical system of the DSD Connector to beused for the DSD process.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Reload ,choose Maintain Destination of DSD Connector .




ItemNo Maintain an item number.

Example: 1

DSD Conn.Destination Choose an RFC Destination from the input help.

Example: DSD_CON203


Result

Once you have maintained the destination, the system can establish the correct RFCconnection to the DSD Connector, when a reload needs to be performed.



(C) SAP AG 539

Define Activity Types and their Assignment toOrder Types

In this IMG activity, you define whether you want materials to be reloaded onto or unloadedfrom the truck.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Reload ,choose Define Activity Types and Their Assignment to Order Types.




Reload Act Maintain a reload activity type.

Example: R

Description Maintain a description for the reload activity type.

Example: RELOAD

Loading Direction Assign the loading direction Reload or Unload.


Result

You have defined reload activity types with the corresponding loading direction.



(C) SAP AG 540

Configure Order Type Determination

In this IMG activity, you maintain the SD sales order types to be used for creating the reload

documents in the back end system. For each reload activity type created, you can assign onesales order type together with a special item usage.

With the combination of sales order type and item usage, you can determine a special itemcategory.

We strongly recommend that you use a standard SD sales item category.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Reload ,choose Configure Order Type Determination.




Reload Act Choose a reload activity type from the input help.

Example: R

Sales Doc Type Assign a sales order type.

Example: RELOAD

Item Usage Choose an item usage from the input help.

If you need a specific determination of a sales order item category, you candetermine it with a specific item usage.


Result

You can now create reload activities with the back end /DSD/SV_RELOAD reload transaction. After saving, the system creates sales orders with your assigned sales order type in thebackground.



(C) SAP AG 541

Inventory View (Stock Visibility)

The Stock Visibility (SV) function allows you to track truck stock during a tour and ensuresthat the back end system knows the load status throughout the DSD process. This isachieved by executing material movements during loading, re-loading, and unloading as wellas by providing an SV status management tool for loaded goods. There are the following fourpossible SV statuses:

1-Loaded (loading of the truck is completed)

2-On Route (truck has left the depot to execute its tour)

3-Back (truck has returned from its tour to the depot)

4-Unloaded (unloading of the truck is completed).

During shipment preparation (including the optional step of loading confirmation), once thetruck loading is completed and the tour has reached the tour status as defined in SVCustomizing, all materials included in the deliveries of the tour are transferred from thestorage location maintained in the delivery to the designated truck stock storage location. Atthe same time, the SV status for all materials of the tour is set to 1-Loaded and the downloadof the tour data can be started.

During check-out, the checker or driver counts all materials loaded on the truck and eitherconfirms the results on the handheld (if they match the stock-on-truck information displayedby the device) or corrects the handheld inventory (in case of discrepancies). Once check-outis completed, the check-out data can be synchronized with the back end before the truckleaves the depot, which changes the tour status of the tour. Having attained the required tourstatus, the system then automatically changes the SV status of the tour to 2-On Route basedon the corresponding SV Customizing settings. If no synchronization is performed, forexample, in a paper-based scenario, the shipment status must be changed manually in orderto reach the customized tour status.

During physical tour execution, the local stock-on-truck status is changed by all issued orreturned goods on the handheld. In the back end system, however, the status for the stock-on-truck of the particular vehicle remains unchanged (On-Route).

If reload/unload activities need to be performed (including the optional step of reload loadingconfirmation), the stock-on-truck inventory of the individual truck gets updated aftersuccessful reload synchronization, that is, material levels that were unloaded are decreasedand material levels that were reloaded are increased. If applicable, stock adjustments arerecorded on the device during reload check-in and reload check-out and are – optionally –

synchronized with the back end. For the already loaded and unloaded materials, the SVstatus in the back end remains unchanged (On-Route). The newly loaded materials (Reload)will be changed to the On-Route SV status.

During check-in, all materials remaining on the truck are counted and the results areconfirmed by driver and/or checker on the device. Once check-in is completed and the finalupload is successfully performed, the system changes the tour status of the tour according tothe Customizing settings made in the Tour Status Profile. Consequently, now that therequired tour status has been attained, the SV status of the truck is also changed, this time tostatus 3-Back . Furthermore, a Final Unloading Document is created if you have selected thisin SV Customizing. This is a sales document with the driver as the customer and withmaterials and quantities taken from the check-in data.

As soon as the physical unloading of the truck is finished, the final unloading document isreleased. Based on this document, goods movements are posted for the unloaded materials



(C) SAP AG 542

by executing a stock transfer from the designated truck-stock storage location to the standardwarehouse storage location. Additionally, the SV status of the tour changes to 4-Unloaded .

After difference determination and difference balancing, the Final Settlement Run (FSR) isexecuted. During this FSR, all prior stock movement postings are reversed based on thecustomized movement type (for example, from blocked stock to free stock). To reverse all

postings does not mean that all individual postings are cancelled. Instead, a reversalmovement record is created based on the aggregated data of all prior postings for a tour thuscounterbalancing all prior movements. Posting this reversal aggregated movement recordensures that, once the tour is settled, the stocks in all locations will be the same as if no stockvisibility transfers had been made at all.

The only exception to this is when stock remaining on the truck prior to the tour is different tothe stock remaining on the truck after the tour. This change must be reflected by the stockvisibility transfers for a tour and is therefore added to the aggregated data. This can only beachieved with BAdI implementation.

However, SAP Standard assumes that every truck will be completely unloaded within an FSR.

A movement record is similar to a movement document except that it does not have adocument number of its own. Movement records can be displayed using the transactionDisplay SV Material Movements ( /DSD/SV_STOCK_AD_DP ).

Every movement record is written to the DSD Document Flow (document type 018 in the /DSD/SL_SLD_FLOW table, PRE_DOC_TYPE field).

For customer enhancements within the DSD Stock Visibility function, the /DSD/BADI_SV_POSTINGS BAdI is available. This BAdI allows you to define customer-specific tracking of truck material movements during loading, reloading, and unloadingprocess steps.

Integration

Prerequisites

You need to ensure that material master records are available for the truck stockstorage location when materials are transferred to that storage location. This isachieved by setting up Materials Management (MM) Customizing so that the masterrecord is automatically created at the time of first goods receipt for the storagelocation. Maintain this Customizing setting for the plants and movement types used

for stock visibility in Customizing for Materials Management under Inventory

Management and Physical Inventory Goods Issue/Transfer Postings Create

Storage Location Automatically .

Master records are only created at first goods receipt, and not at goods issue. If empties areunloaded from the vehicle during reload, and stock transfer from truck stock storage locationto regular storage location takes place, it is required to manually maintain the master recordsfor the empties even if the checkbox for automatic record creation is selected.

When using stock visibility within the reload process, unloading of empties duringreload may result in negative stocks on the truck storage location. Therefore, youneed to allow negative stocks for all relevant materials in all truck stock storagelocations, which you can maintain in Customizing for Materials Management under

Inventory Management and Physical Inventory Goods Issue/Transfer Postings Allow Negative Stocks .



(C) SAP AG 543

Process Flow

The Customizing Tables for this process are located in Customizing for Logistics Execution

under SAP Direct Store Delivery Stock Visibility comprising the following activities:

1. Activate Stock Visibility [Page 544]

2. Maintain Stock Visibility Scenario Settings [Page 545]

3. Maintain Storage Locations per Plant [Page 548]

4. Maintain Recipient for Express Mail [Page 549]



(C) SAP AG 544

Activate Stock Visibility

If you want to use the DSD functionality Stock Visibility (SV), you must select the checkbox in

this IMG activity. This activation table is needed in order to start the stock visibility at adefined moment.

Stock Visibility should only be activated if there is no active tour (that is, tour within asettlement process), because the Initial Load cannot be created retroactively causing SV datafor the tour and vehicle to be incorrect. When activating the SV function, all vehiclesconcerned should be empty, that is, no stock should remain on the truck because the SVfunction would not be aware of this stock. If any stock remains on the truck, the stock needsto be adjusted by creating a movement record in the /DSD/SV_STOCK_AD_CR transaction.

De-activation of SV while tours are active could cause inconsistencies in both the SV data as

well as in standard Materials Management (MM) because there may still be stock on the truckstock storage location.

Procedure

1. In Customizing for Logistics Execution under SAP Direct Store Delivery Stock

Visibility , choose Activate Stock Visibility .

2. Set the DSD SV active option.

3. Save your entry.

Result

With the checkbox selected to active, the system is able to use existing SV Customizingduring the DSD process and to display selected DSD tours in SV-relevant transactions forfurther processing.



(C) SAP AG 545

Maintain Stock Visibility Scenario Settings

Within the new tour status module, as standard, every shipment status is directly related to a

tour status. Whenever a shipment status is set in the shipment, the connected tour status isautomatically assigned to the corresponding tour. Due to this close connection between tourstatus and shipment status, the tour status can be changed indirectly by setting the shipmentstatus. However, the tour status for check-out and check-in can also be changed directlybased on Customizing settings made in this table.

In this IMG activity, you define for each scenario which tour status must have been reached inorder for the system to set a new Stock Visibility (SV) status for the respective tour.

Prerequisites

Tour status IDs must be maintained.

Tour status scenarios and tour status profiles must be defined.

Movement types must be maintained.

Procedure


Visibility , choose Stock Visibility Scenario Settings.

2. Choose New entries.

3. On the screen that opens, enter the following data:


Scenario

Enter the scenario for which you want to maintain the Stock Visibilityscenario settings.

Example: ZMDELVLC

DSD SVScenarioSettings

MvT Vehicleto Wareh

Enter the movement type which the system should use to transfer materials

from the truck stock storage location back to the standard warehousestorage location.

Example: 343

TS Loaded

Enter the tour status ID which the tour must have reached for triggering thesystem to perform a stock transfer for all materials contained in theshipment from the WH-storage location specified in the delivery to the truckstorage location customized for the given plant. When this tour status ID isreached, the SV status is set to Loaded and a movement record is createdto document the status change.

Example: 206000 (Shipment – Loading completed)

This transfer will only be done for materials that are not yet goods issued



(C) SAP AG 546


and that are not marked for returns, because planned returns are not loadedonto the vehicle at the depot but at the customer’s site.

TS On Route

Enter the tour status ID which the tour must have reached for triggering thesystem to change the SV status to On Route and to create a corresponding

movement record.

Example: 208000 (Shipment – Started)

In a mobile scenario, this tour status is set automatically when check-outdata is synchronized before leaving the plant; subsequently, the DSD SVstatus is set automatically as well.

Alternatively, in a paper-based scenario, this tour status can be reached bymanually setting the corresponding shipment status in the shipmentdocument triggering the setting of the DSD SV status in consequence.

TS Back

Enter the tour status ID which the tour must have reached for triggering thesystem to change the SV status to Back and to create a correspondingmovement record.

Example: 701000 (Shipment – Finished)

TS set atCheck-out

Enter the tour status ID which the system should set in a tour as soon ascheck-out synchronization has been performed. The new tour status of theshipment will trigger the SV status to change from Loaded to On Route forthe vehicle stock of the tour.

Example: 208000 (Shipment – Started)

TS set atCheck-In

Enter the tour status ID which the system should set in a tour as soon as thevehicle checks-in, that is, the upload has been executed successfully. Thenew tour status of the shipment will trigger the SV status to change from OnRoute to Back for the vehicle stock of the tour.

Example: 701000 (Shipment – Finished)

RL Mobile

Choose an option from the drop-down menu (listed below) to indicatewhether and, if yes, when the system should create a Final UnloadingDocument (RL = Return Loading Note), given a mobile scenario:

o 0 Never automatically, placed in customer development

o 1 Within Upload

o 2 At released for settlement, before FSR

The document type for creating the RL-Document is taken from the Route Accounting Customizing for the customer sales transaction type 12 of thesettlement type that is relevant for the tour concerned.

RLPaperbased

Choose an option from the drop-down menu (listed below) to indicatewhether and, if yes, when the system should create a Final UnloadingDocument (RL = Return Loading Note), given a paper-based scenario.

The three options to choose from include the following:

o 0 Never automatically, placed in customer development



(C) SAP AG 547


o 1 Within copy functionality ( /DSD/SL_RADB)

o 2 At released for settlement, before FSR

The document type for creating the RL-Document is taken from the Route Accounting Customizing for the customer sales transaction type 12 of thesettlement type that is relevant for the tour concerned.


Result

Based on the entries made in this table, the system changes the SV status of a tour when thecorresponding tour status is reached. Likewise, check-out/check-in tour statuses are set andthe Final Unloading Document is created, if applicable.



(C) SAP AG 548

Maintain Storage Locations per Plant

In this IMG activity, you define a truck stock storage location for each relevant plant. The truck

stock storage location is used for all vehicles loading or unloading at that plant. Additionalrecords are kept that connect the truck stock material to each individual vehicle, this wayproviding information on the material quantities that are assigned to each individual truck.

Prerequisites

Plants must be maintained.

Storage locations must be maintained.

Procedure


Visibility , choose Storage Locations per Plant .

2. Choose New entries.



Plnt Choose a plant from the input help.

Example: 1000

SLoc Choose a truck storage location from the input help.

Example: TRCK

4. Save your entry.

Result

When executing a stock transfer between warehouse stock and vehicle stock for a specifictour, the system checks the entries made in this table and uses the truck stock storagelocation that is the plant that matches the plant maintained in the deliveries of the tour.



(C) SAP AG 549

Maintain Recipient for Express Mail

In this IMG activity, for selected scenarios and Stock Visibility (SV) events, you specify one or

more users who should receive an express mail if errors occur during a stock transfer posting.

During the DSD process, stock transfer postings may happen at various points, each of whichconstitutes an SV event. As standard, the following SV events are defined and implemented:

Initial Load

Check-out

Reload

Check-in

Final Unload (RL)

FSR

Manual

This event applies to those cases where the SV movement record (for the stock transfer) iscreated manually using the /DSD/SV_STOCK_AD_CR transaction.

Initial Un-load

When an error occurs in stock transfer postings, the DSD application log is updated with anerror message and an express mail is sent to the relevant user, if customized in this table forthe triggering SV event.

Prerequisites

Recipient must be maintained as user in the system.

Procedure

1. In Customizing for Logistics Execution under Direct Store Delivery Stock Visibility

, choose Recipient for Express Mail .




Scenario Choose a scenario from the input help.

Example: MSALES00

SV Event Choose an SV event from the drop-down list.

Example: 3 Reload



(C) SAP AG 550


User Name Enter the user name of the recipient (log on user name) of the express mail.

4. Save your entry.

Result

Based on the entries made, the user(s) maintained receive an express mail as soon as anerror has occurred during the stock transfer posting of the SV event maintained.



(C) SAP AG 551

Business Add-lns (BAdIs) for Direct Store Delivery(Background)

In SAP Direct Store Delivery , a number of BAdIs are available that allow you to individualizethe standard DSD Process according to customer-specific needs by influencing this standardprocess without making modifications.

The BAdIs that can be used within the SAP Direct Store Delivery component are listed belowwith a brief description of their potential effects. With SAP Direct Store Delivery , there is a setof new BAdIs and some existing ones remain active as well.

The existing BAdIs from mDSD 3.0 (can still be used with SAP Direct Store Delivery ) can be

accessed in Customizing for Logistics Execution under SAP Direct Store Delivery

Business Add-Ins (BAdIs) Business Add-ins in DSD .

BAdI Description

/DSD/BADI_VC_BAPI

Customer Enhancements Visit Control

The BAdI is used in the Visit Control component toenhance BAPIs for visit plans and visit lists so thatvalues from customer-specific fields can be processedand returned to the BAPIs. Customers may use theirown BAdI methods to enhance the individual BAPIfunction module for selecting and retrievinginformation.

/DSD/BADI_HH_CUST_BARCODE

Creation of Customer Barcode Identifier

A customer can use this BAdI to define their ownbarcode identifier instead of the GLN. The customerneeds to implement their own coding with the CREATE method within the /DSD/BADI_HH_CUST_BARCODE BAdI definition at the /DSD/ES_HH_CUST_BARCODE enhancement spot. The individual barcode identifiercan be derived from different combinations of the fields

of KNA1 structure (General Data in the Customer

Master). If this BAdI is implemented, it must be alignedwith the implementation ofKUNNR_ADDITIONAL_HANDLING_POST method (

/DSD/ME_CUSTOMER_HEADER table,BARCODE_IDENTIFIER field) in the /DSD/ME_BADI

BAdI.

/DSD/BADI_GS_EXTV_COMPILE

Implementation of Data Compilation for ExtractionVariants

Not supported in SAP Direct Store Delivery 1.0

/DSD/BADI_GS_EXT_METHOD Implementation of Extraction Methods


/DSD/BADI_GS_EXT_VARIANT Implementation of Extraction Variants



(C) SAP AG 552

BAdI Description


/DSD/BADI_ST

Customer Enhancements Tour Status

The BAdI allows you to change the tour status data inpaper-based or mobile DSD scenarios. Prerequisites:The tour must be DSD-relevant, that is, the shipmentand/or visit list must be assigned to the connectedmedium.

/DSD/BADI_SV_LOAD_CONF

Customer Enhancements Loading Confirmation

The BAdI allows you to define customer-specificchanges to the Loading Confirmation process. Whenimplemented, the system uses this BAdI during theloading confirmation dialog and processes the loading

confirmation difference with its different reasons justbefore the final status of loading confirmation is set toconfirmed.

/DSD/BADI_SV_POSTINGS

Customer Enhancements Stock Visibility

The BAdI allows you to define customer-specifictracking of truck material movements during loading,reloading, and unloading in paper-based or mobilescenarios.

Example:

With the STOCK TRANSFER method, the customercan control (change) all input data of the stocktransfers.

/DSD/BADI_MF_UPLOAD

More Flexibility in Upload

The BAdI provides methods that offer more flexibilityduring the Upload process. Before EnhancementPackage 3 (Business Function /DSD/BF ), tour datacould be transferred to the Route AccountingDatabase (RAD) via BAPIs only in those cases wherethe related function modules mapped the interfacedata from the RAD to the same naming convention.

The /DSD/BADI_MF_UPLOAD BAdI enables thecustomer to set up their own specific mapping betweenthe interface data and the RAD tables. For each RADtable, a separate method exists in this BAdI, forexample, DELHD method for the /DSD/HH_RADELHD table to control changes within the delivery header.

/DSD/BADI_SL_ASL_EXCL

Exclude Tour from Automatic Settlement:

The BAdI is used in the Route Accounting componentto exclude individual tours from subsequent processeswithin an Automatic Route Settlement. The system firstchecks the entries in the /DSD/SL_ASL_EXCL control

table before automatically starting a subsequentprocess. The exclusions determined during this check



(C) SAP AG 553

BAdI Description

can be further modified or enhanced by implementingthis BAdI.

The following list shows the newly added BAdIs for SAP Direct Store Delivery .

They can be accessed in the Customizing for Logistics Execution under SAP Direct Store

Delivery Business Add-Ins (BAdIs) .

BAdI Description

/EMSE/BADI_LISTEXCL_ENH

Enhance Material Listing/Exclusion List forDownload

This BAdI enables the enhancement of thedocument types used for materiallisting/exclusion extraction. It is possible to addfurther delivery/order types, which are used todetermine a listing/exclusion material list foreach tour customer.

/EMSE/DOWNLOAD_BADI

Process Mobile Business Object for Download

As part of the enhancement framework, you candefine a BAdI for every mobile business object(MBO).

Note that the filter of the BAdI has to be theMBO name.

In this implementation, an import parameter of

the result table content is given. The data canbe manipulated or additional data can beenhanced with the MSE_MBO_EXT MBO. ThisMBO is similar to the BAPIEXT logic often usedin standard Business Application ProgrammingInterfaces (BAPIs) based on key/value pairs.

To add data to MBO_EXT , the following 2 ABAPDictionary objects are already defined:

/EMSE/ /EMSE/MBO_EXT structure

/EMSE/TT_MBO_EXT table type

To add MBO_EXT data to the JSON downloadpayload, it is necessary to call a method in thehelper class with an internal MBO_EXT table(for example, ir_download_helper ->append_mbo_ext (lt_mbo_ext )).

/EMSE/DWNL_PROC_PRE_SEND_BADI

Add Activities in Download Before Transfer tothe Mobile Engine

This BAdI enables the enhancement of thestandard download process. It is possible to addfurther data after the normal download process.

Example:



BAdI Description

The /EMSE/EHI_PROC_PRE_SEND_BADI example implementation enhances the standarddownload process via the

/EMSE/CL_DWNL_PROC_PRE_SEND implementation class. This class implements the /EMSE/IF_DWNL_PR_PRE_SEND_BADI interface.

/EMSE/PE_DOWNLOAD_DATA

Enhance Pricing Data for Download

The BAdI implementation is to enhance the