Download pdf - G62 BB InstallGuide en De

V2.470

July 2004

English

Direct Store Delivery (G62)

SAP AG Neurottstr. 16 69190 Walldorf Germany

Building Block Installation Guide

SAP Best Practices Direct Store Delivery (G62): Installation Guide

© SAP AG Page 2 of 18

Copyright

© Copyright 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without

the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

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

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic Server™ are trademarks of IBM Corporation in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, 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 in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves information purposes only. National product specifications may vary.



Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the

ENTER key.

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

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Content

1 Purpose ................................................................................................................................. 5

2 Preparation ........................................................................................................................... 5

2.1 Prerequisites .................................................................................................................. 5

2.2 Uploading the Installation Role ...................................................................................... 5

3 Requesting the Installation Status ........................................................................................ 5

4 Configuration ........................................................................................................................ 6

4.1 SD Standard Configuration ............................................................................................ 6

4.1.1 Maintaining Standard Settings for SD ................................................................... 6

4.2 DSD General Configuration ........................................................................................... 7

4.2.1 Activating Direct Store Delivery ............................................................................. 7

4.3 DSD Process Configuration ........................................................................................... 7

4.3.1 Maintaining Basic Settings for Direct Store Delivery ............................................. 7

4.3.2 Assigning Number Range Intervals ....................................................................... 9

4.3.3 Maintaining Route Settlement for Direct Store Delivery ...................................... 10

4.3.3.1 Assigning Allowed Settlement Types to Settlement Offices ....................... 11

4.3.3.2 Maintaining Settings for Manual Clearing ................................................... 11

4.3.4 Maintaining Visit Control ...................................................................................... 12

4.3.5 Maintaining Transportation Planning ................................................................... 12

4.4 DSD Master Data Configuration .................................................................................. 13

4.4.1 Maintaining the DSD Master Data Settings ......................................................... 13

5 Master Data ........................................................................................................................ 14

5.1 Creating DSD Master Data .......................................................................................... 14

5.1.1 Creating Drivers (C6610, C6611, C6612) with eCATT/LSMW ........................... 14

5.1.1.1 Creating Additional Data for DSD ............................................................... 14

5.1.2 Creating Vehicles (F6009, F6010, F6011) .......................................................... 15

5.1.3 Creating Tours ..................................................................................................... 15

5.1.4 Creating Visit Plans - Header Data ..................................................................... 16

5.1.5 Adding Customers to Visit Plans ......................................................................... 17

6 Setting the Installation Status ............................................................................................. 17



1 Purpose

This installation guide provides the information you need to set up the configuration of this building block using automated configuration tools, such as BC Sets. If you are not familiar with working with the automated configuration tools, refer to the document Essential Information.

If you do not want to use the automated installation process and prefer to configure this building block manually, refer to the configuration guide of this building block.

2 Preparation

2.1 Prerequisites

If you want to use this building block, you must first install the following building blocks:

Building Block G62 Description

G80 Basic Settings

2.2 Uploading the Installation Role

Use

Before you start with the installation using the automated procedures described in this installation guide, upload the installation role and assign it to your user. If you prefer to carry out some of the steps manually, refer to the configuration guide of this building block.

This building block provides one or more installation roles, which enable you to access all the transactions required for the installation from the relevant system. The following roles are available for this building block:

Technical name Description File name for upload

_SMB26_G62_01I.SAP Installation Role for Direct Store Delivery _SMB26_G62_01I.SAP

Procedure

For details on how to upload the installation roles to the system and how to work with the roles, refer to the document Essential Information.

3 Requesting the Installation Status

Use

The purpose of this activity is to check whether the current building block has already been installed. This enables you to keep track of the installation process.



Procedure

1. Access the activity using one of the following navigation options:

SAP R/3 Role Menu G62: Installation Role Direct Store Delivery Requesting the Installation Status

Transaction Code /SMB26/T001_J01_G62

2. Choose Execute to start the eCATT procedure.

The installation status information is displayed (incomplete, successfully installed (complete), or reset to incomplete).

3. If the installation of the current building block is incomplete and you want to complete it now, go back to the installation role and proceed with the next step.

If the installation of the current building block is complete, you can proceed to the next building block. If, for some reason, you want to redo some or all of the completed installation of the current building block, first go to the activity Setting the Installation Status to reset the status to incomplete. Then make your changes before returning to the activity Setting the Installation Status to set the status to complete again.

Result

You have confirmed the installation status of the current building block, which either enables you to safely proceed with the installation process or proceed to the next building block.

4 Configuration

4.1 SD Standard Configuration

4.1.1 Maintaining Standard Settings for SD

Use

The purpose of this activity is to define new sales document types for DSD, maintain the appropriate number ranges, assign the new created sales document types to existing item categories and maintain the copy control between debit/credit-requests to billing documents.

Procedure


SAP R/3 Role Menu G62: Installation Role Direct Store Delivery Customizing SD Standard Settings

Transaction Code /SMB26/S000_G62_01

2. Activate the BC Set /SMB26/SD_CONFIG_S000_G62.

From number (CO/CI-Diff.Driver Cred)

0160000000 0160000000

From number (CO/CI- 0170000000 0170000000



Diff.Driver Deb)

From number (DSD ReturnLoadingNote)

0150000000 0150000000

Number Range Nr (CO/CI-Diff.Driver Cred)

30 30

Number Range Nr (CO/CI-Diff.Driver Deb)

31 31

Number Range Nr (DSD ReturnLoadingNote)

29 29

To number (CO/CI-Diff.Driver Cred)

0169999999 0169999999

To number (CO/CI-Diff.Driver Deb)

0179999999 0179999999

To number (DSD ReturnLoadingNote)

0159999999 0159999999

4.2 DSD General Configuration

4.2.1 Activating Direct Store Delivery

Use

This BC Set sets the indicator to control whether the Direct Store Delivery (DSD) backend is active or not.

Procedure


SAP R/3 Role Menu G62: Installation Role Direct Store Delivery Customizing Activate Direct Store Delivery

Transaction Code /SMB26/B015_G62_02

2. Activate the BC Set /SMB26//DSD/RP_SETUP_B015_G62.

3. Complete the activation of the BC Set and go back to the installation role.

4.3 DSD Process Configuration

4.3.1 Maintaining Basic Settings for Direct Store Delivery

Use

With this BC Set you maintain reasons for classifying the differences in the check-in and check-out of the stocks on truck and reasons to classify deviations from the delivery quantity.

You also define the customer sales calls reasons to describe a visit to a customer in detail.



With the rest of the BC Sets in this hierarchy you define number ranges for all DSD specific documents, for example: Check-Out and check-In documents, settlement document, final settlement run.

Procedure


SAP R/3 Role Menu G62: Installation Role Direct Store Delivery Customizing Direct Store Delivery - Basic Settings


2. Activate the BC Set /SMB26/DSD_BASIC_S001_G62

3. In the Enter Variable Field Values screen, change the values of the following fields:

Field Lang BC Set Conts Value

From number (Check-In Documents)

200000 200000

From number (Check-Out Documents)

100000 100000

From number (External Delivery )

0300000000 0300000000

From number (External Invoice)

0500000000 0500000000

From number (External Order )

0400000000 0400000000

From number (Final Settlement Run)

0700000000 0700000000

From number (Settlement Document)

0600000000 0600000000

Number Range Number (Check-In Documents

02 02

Number Range Number (Check-Out Documents

01 01

Number Range Number (External Delivery )

03 03

Number Range Number (External Invoice)

05 05

Number Range Number (External Order )

04 04



Field Lang BC Set Conts Value

Number Range Number (FinalSettlementRun)

07 07

Number Range Number (Settlement Document

06 06

To number (Check-In Documents)

299999 299999

To number (Check-Out Documents)

199999 199999

To number (External Delivery )

0399999999 0399999999

To number (External Invoice)

0599999999 0599999999

To number (External Order)

0499999999 0499999999

To number (Final Settlement Run)

0799999999 0799999999

To number (Settlement Document)

0699999999 0699999999


4.3.2 Assigning Number Range Intervals

Use

The purpose of this activity is to assign the previously created number ranges to DSD-specific Number Range Interval Purposes.

Procedure


SAP R/3 Role Menu G62: Installation Role Direct Store Delivery Customizing Assign Number Range Interval

Transaction Code /SMB26/B028_G62_04

2. Activate the BC Set /SMB26//DSD/SL_NRZUORD_B028_G62.


Field Lang BCSet Conts Value

Number Range Number (Check-In Docum.)

02 02



Number Range Number (Check-Out Docum.)

01 01

Number Range Number (External Delivery)

03 03

Number Range Number (External Invoice)

05 05

Number Range Number (External Order)

04 04

Number Range Number (FinalSettlementRun)

07 07

Number Range Number (Settlement Document)

06 06


4.3.3 Maintaining Route Settlement for Direct Store Delivery

Use

The purpose of this activity is to make the customizing setup for the DSD-relevant part of route settlement. This includes the creation of a new organizational unit called the settlement office. The settlement office is dependent on the transportation planning point. Furthermore, a settlement type with dependence on the shipment type will be defined. Another step of the installation part is to maintain the mapping of tour activities such as outbound deliveries and the check-out for the tour for the corresponding R/3 documents. You also maintain the settings for automatic and manual clearing of FI documents in the financial accounting, set the automatic posting of driver receipts and payments, and define customer sales transactions (tour activities that are related to sales and/or the physical delivery execution).

Procedure


SAP R/3 Role Menu G62: Installation Role Direct Store Delivery Customizing Route Settlement


2. Activate the BC Set /SMB26/DSD_ROUTESET_S002_G62.


Field Lang BCSetConts Value

Company Code BP01 BP01

Distribution Channel 01 01



Division 01 01

Sales Organization BP01 BP01

Settlement Office YG01 YG01

TransportPlanningPt BP01 BP01


4.3.3.1 Assigning Allowed Settlement Types to Settlement Offices

Use

In this customizing table you can assign allowed settlement types to a settlement office.

If the customizing table contains an entry with the required settlement type / settlement office combination, the route settlement can be executed.

Procedure


SAP R/3 Role Menu IMG Logistics Execution Direct Store Delivery Backend

Route Accounting Route Settlement Assign Allowed Settlement Types to Settlement Office

Transaction Code SPRO

2. On the Change view “DSD Route Settlement : Settlement Types per Settlement Office“ screen, choose New Entries.

3. On the New Entries: Overview of Added Entries screen, make the following entries:

Field Description Value/User action

Set.Off YG01

Sett. type YG

4. Save your entries.

4.3.3.2 Maintaining Settings for Manual Clearing

Use

Direct store delivery provides the functionality to perform the manual clearing process of incoming payments against open items. The following procedure describes how to make the appropriate customizing setup.

Procedure

1. Access the activity using the following navigation options:



SAP R/3 Role Menu Logistics execution Direct Store Delivery Backend Route

Accounting Route Settlement Collection Processing Maintain Settings for Manual Clearing

Transaction Code SPRO

2. On the Change view: DSD Clearing: Manual control of clearing: Overview screen, choose New Entries and make the following entries.

Man Assign Stat. Auto Clear All Description

Y0 x Clearing allowed

Y1 Clearing not allowed

3. Save your entries.

4.3.4 Maintaining Visit Control

Use

The purpose of this activity is to define the customizing setup, which is relevant for using the DSD component visit control. Within this installation step you create your own calendar types. The calendar type is used to determine how one customer's dates, which are planned in visit control, are grouped together. You restrict the processing of visit plans and visit lists to specific users, and you define various number ranges. The visit plan type determines which parameters are used for dynamic transportation planning and which visit plan type is used for manual shipment creation from the tour master. You can also enter default values for driving time and waiting times. Furthermore, you can define the allowed sales document types that can be used while using visit control.

Procedure


SAP R/3 Role Menu G62: Installation Role Direct Store Delivery Customizing Visit Control


2. Activate the BC Set /SMB26/DSD_VISITCONTROL_S003_G62.


4.3.5 Maintaining Transportation Planning

Use

With the delivery type you determine how the system processes a delivery. For example, depending on the delivery type, the system determines which screens to present and which data to request from the user. Here you define your own capacity limits and a possible tolerance in percentage (such as usable load, volume, number of stops, capacity field variables, and time).

SAPEVENT:DOCU_LINK/DS:DE.KUNNR

SAPEVENT:DOCU_LINK/DS:GLOS.4D543F599D548B4782B12126F488056E



Procedure


2. Activate the

BC Set /SMB26/DSD_TRANSPORT_S004_G62.


Field Lang. BCSET Conts Value

Delivery Type LF LF

TransportPlanningPt BP01 BP01


4.4 DSD Master Data Configuration

4.4.1 Maintaining the DSD Master Data Settings

Use

For the DSD component, specific master data is required. As a prerequisite for the master data maintenance you have to maintain some customizing settings. These customizing settings will be implemented within this installation step.

Procedure


SAP R/3 Role Menu G62: Installation Role Direct Store Delivery Customizing DSD Master Data Configuration


2. Activate the BC Set /SMB26/DSD_MASTERDATA_S005_G62.


Field Lang BCSET CONTS Value

Account group Driver

YG05 YG05

From number (Vehicle)

A A

Number range (Driver DSD)

XX XX

To number (Vehicle)

ZZZZZZZZZZ ZZZZZZZZZZ


SAP R/3 Role Menu G62: Installation Role Direct Store Delivery Customizing Transportation Planning




5 Master Data

5.1 Creating DSD Master Data

5.1.1 Creating Drivers (C6610, C6611, C6612) with eCATT/LSMW

Use

The purpose of this activity is to create master data using LSMW in an automated process supported by eCATT.

For more information about using the LSMW with or without the eCATT tool, see the section Legacy System Migration Workbench in Essential Information.

Procedure


SAP R/3 Role Menu G62: Installation Role Direct Store Delivery Master Data Driver

Transaction Code /SMB26/L001_G62_01

2. On the /SMB99/START_ECATT screen, ensure that the Test Configuration field contains the value /SMB26/LSMW_FRAME_T001_G80, and the Variant field contains the variant for the relevant master data file, in this case G31.


The eCATT processes various steps automatically. Do not interrupt this process.

4. For further information, refer to the Legacy System Migration Workbench section in Essential Information.

5.1.1.1 Creating Additional Data for DSD

Use

The drivers you created before in step 5.1 have to be enhanced by additional DSD data. This will be done via eCATT within this implementation step.

Procedure


SAP R/3 Role Menu G62: Installation Role Direct Store Delivery Master Data Additional DSD Data for Drivers

Transaction Code /SMB26/O002_G62_02

2. On the /SMB99/START_ECATT screen, ensure that the Test Configuration field contains the value /SMB26/XD02_O311_G62, and the Variant field contains the value C*.



3. Choose Execute to start the eCATT procedure /SMB26/XD02_O311_G62.

4. Check the eCATT log (optional) and go back to the installation role.

Result

The drivers and special DSD data have been created.

5.1.2 Creating Vehicles (F6009, F6010, F6011)

Use

The purpose of this activity is to create the necessary vehicles/trucks for the DSD processes. If you want to personalize the eCATT, refer to the Essential Information documentation.

Procedure


SAP R/3 Role Menu G62: Installation Role Direct Store Delivery Master Data Vehicle


2. On the /SMB99/START_ECATT screen, ensure that the Test Configuration field contains the value /SMB26/IE31_O312_G62, and the Variant field contains the value F*.

3. Choose Execute to start the eCATT procedure /SMB26/IE31_O312_G62.


Result

You have created three vehicles.

5.1.3 Creating Tours

Use

Another type of DSD-specific master data is the tour master. Within this activity you maintain tour master data, which combines the driver, vehicle, and the visit plan types, and assign the combinations to routes. This step has to be done manually.

Prerequisites

The driver and vehicle master data are required.

Procedure


SAP R/3 Role Menu G62: Installation Role Direct Store Delivery Master Data Maintain Tours

Transaction Code /N/DSD/RP_TOUR



2. On the Maintain Tours screen, leave the selection fields blank and choose Execute.

3. On the Change Tours screen, choose Create Tour Headers.

4. In the Create New Tour Headers dialog box, enter the following values:

Field name Description User action and values Notes

Shipment route Southern Route 000002

Visit Plan Type YG1

TransportPlanPt BP01

No. of Stops e.g. 10

Max Duration 08:00

5. Choose OK.

6. On the Change Tours screen, select the tour header you have created and choose Create Tours.

7. In the Create New Tours dialog box, enter the following values:

Field name Description User action and values Notes

Driver 1 C6612

Tractor Vehicle F6012

8. Choose OK and repeat the procedure from step 7 onwards to create two more tours with the other two drivers (C6610, C6611) and the other two vehicles in the system (F6009, F6011).

9. Save and go back.

Result

You have created a tour header with three tours using the southern route.

5.1.4 Creating Visit Plans - Header Data

Use

The purpose of this activity is to create this visit plan header data using eCATT. If you want to personalize the eCATT, refer to the Essential Information documentation.

Procedure


SAP R/3 Role Menu G62: Installation Role Direct Store Delivery Master Data Creating Visit Plan Header


2. On the /SMB99/START_ECATT screen, ensure that the Test Configuration field contains the value /SMB26/DSD_VC_VP_O320_G62, and the Variant field contains the value V*.

3. Choose Execute to start the eCATT procedure /SMB26/DSD_VC_VP_O320_G62.




5.1.5 Adding Customers to Visit Plans

Use

The purpose of this activity is to assign a range of customers to the visit plan you created with installation step 5.1.4 in order to make the visit plan complete. This step must be done manually.

Procedure


SAP R/3 Role Menu G62: Installation Role Direct Store Delivery Master Data Add customer to visit plan

Transaction Code /N/DSD/VC_VP

2. On the Visit Control: Visit Plans screen, leave all selection fields blank and choose Execute.

3. On the Maintain Visit Plans screen, select the first visit plan (Visit Plan 1) you created with installation step 5.1.4.

4. Choose More Customers.

5. In the dialog box Select More Customers, choose Multiple selection on the customer level.

6. Enter the following customer numbers: C6111, C6113

7. Choose Execute (two times). The selected customers appear on the lower area of the Maintain Visit Plans screen.

8. Assign the selected customers from the lower area with drag and drop to the visit plan in the upper area.

9. Choose Save.

10. Repeat steps 3 to 9 for the remaining visit plans. The following customers should be assigned to the following visit plans:

Visit Plan 2 – Customer: C6100



11. Go back to the installation role.

6 Setting the Installation Status

Use

The purpose of this activity is to set the installation status for the current building block to complete. This status is then used when building block installation status requests are made, and therefore enables you to keep track of the installation process.



Procedure


SAP R/3 Role Menu G62: Installation Role Direct Store Delivery Setting the Installation Status Installation

Transaction Code /SMB26/T002_J01_G62


3. Choose Complete if all steps in the installation role for this building block have been completed successfully.

Note that if the installation status is already complete, you have the option of resetting it to incomplete if you want to redo part or all of the installation of the building block for some reason.

Result

The installation status is now set to complete.