SAP Dealer Business Management: Business Scenario and Busine

SAP Dealer Business Management: Business Scenario and Business Process Configuration

Release DBM 8.1 SP01

CUSTOMER Document Version 1.0

SAP Dealer Business Management: Business Scenario and Business Process Configuration 2

SAP Copyright and Disclaimers

Copyright

© 2016 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.

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

are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in

Germany and other countries. All other product and service names mentioned are the

trademarks of their respective companies. Please see http://www.sap.com/corporate-

en/legal/copyright/index.epx#trademark for additional trademark information and notices.

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.sap.com%2Fcorporate-en%2Flegal%2Fcopyright%2Findex.epx%23trademark

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.sap.com%2Fcorporate-en%2Flegal%2Fcopyright%2Findex.epx%23trademark


Important Disclaimers on Legal Aspects

SAP Library document classification: PUBLIC

This document is for informational purposes only. Its content is subject to change without notice, and SAP does not warrant that it is error-free. SAP MAKES NO WARRANTIES, EXPRESS OR IMPLIED, OR OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

Coding Samples

Any software coding and/or code lines / strings (“Code”) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

Internet Hyperlinks

The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint where to find supplementary documentation. SAP does not warrant the availability and correctness of such supplementary documentation or the ability to serve for a particular purpose. SAP shall not be liable for any damages caused by the use of such documentation unless such damages have been caused by SAP’s gross negligence or willful misconduct.

Accessibility

The information contained in the SAP Library documentation represents SAP’s current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP specifically disclaims any liability with respect to this document and no contractual obligations or commitments are formed either directly or indirectly by this document.

Gender-Neutral Language As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with “you”, or a gender-neutral noun (such as “sales person” or “working days”) is used. If when referring to members of both sexes, however, the third person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.


Document History The following table provides an overview of the most important document changes:

Version Date Status/Change

1.0 2016–02–05 Initial


Icons in Body Text Icon 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 Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Typographic Conventions Type 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 programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

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 of installation, upgrade and database tools.

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. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

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


Table of Contents

1 General Information ................................................................................................... 17

2 Generic Settings for Searches ................................................................................ 20 2.1 Generic Settings for Searches Based on TREX ........................................................ 20 2.1.1 Setting Up the RFC Connection .............................................................................. 20 2.1.2 Transaction COM_SE_ADMIN ................................................................................ 20 2.1.3 Delta Indexing of TREX Objects ............................................................................. 21

2.2 Generic Settings for SAP HANA-based Searches (Without TREX) .............................. 21 2.2.1 Set up Connection to SAP HANA Database Using DBCO ..................................... 21 2.2.2 Define Destination for Search ................................................................................. 21

3 Configuring a Client ................................................................................................ 22

4 Defining Field Control for the Loading Group and Transportation Group (HAWA) . 23

5 Enterprise Structure ................................................................................................ 24

5.1 Defining the Credit Control Area ......................................................................... 25

5.2 Assigning Organizational Elements .................................................................... 26

5.3 Integrating Warehouse Management .................................................................. 27

6 Logistics General .................................................................................................... 28

6.1 Setting Up Conversion Exit for Material Numbers .............................................. 29

6.2 Defining the Batch Level ..................................................................................... 30

6.3 Activating Internal Batch Number Assignment .................................................... 31

6.4 Processing Number Ranges for Internal Batch Number Assignment ................. 32

6.5 Maintaining Company Codes for Materials Management ................................... 33

6.6 No Update of MOFF/MSTA Data with Separate Evaluation ............................... 34

7 Sales and Distribution ............................................................................................ 35

7.1 Defining Common Distribution Channels and Divisions...................................... 36

7.2 Defining Conditions for Value-Added Tax ........................................................... 37

8 Materials Management ........................................................................................... 38

8.1 Adjusting Movement Types ................................................................................. 39

9 Dealer Business Management (DBM) .................................................................... 40

9.1 Defining an External Manufacturer ...................................................................... 41


9.2 Assigning an External Manufacturer ................................................................... 42

9.3 Maintaining Number Ranges for the DBM Order ................................................ 43

10 Business Partner Configuration ........................................................................... 44

10.1 Prerequisite Settings ......................................................................................... 45

10.1.1 Synchronization from Business Partner to Customer .................................... 47

10.1.2 Synchronization from Business Partner to Vendor ........................................ 48

10.1.3 Synchronization from Customer to Business Partner .................................... 49

10.1.4 Synchronization from Vendor to Business Partner ........................................ 50

10.1.5 Define Number Assignment for Direction BP to Customer ............................ 51

10.1.6 Define Number Assignment for Direction BP to Vendor ................................ 52

10.1.7 Define Number Assignment for Direction Customer to BP ............................ 53

10.1.8 Define Number Assignment for Direction Vendor to BP ................................ 54

10.1.9 Business Add-Ins (BAdIs) .............................................................................. 55

10.1.10 Synchronize Contact Person between Business Partner and Customer..... 56

10.1.11 Maintain Collective Billing Field in the BP Transaction ................................ 57

10.2 Synchronization Cockpit .................................................................................... 58

10.3 Upgrade Report ................................................................................................. 59

10.4 Quick Creation of Business Partner .................................................................. 60

11 Accounting (Financials, Controlling) ..................................................................... 62

11.1 Processing the Controlling Area ........................................................................ 63

11.2 Chart of Accounts .............................................................................................. 64

11.3 Creating Accounts ............................................................................................. 65

11.4 Creating Cost Elements .................................................................................... 66

11.5 Copying the Cost Element Group ..................................................................... 67

11.6 Creating a Profit Center .................................................................................... 68

11.7 Creating Cost Centers ....................................................................................... 69


11.8 Creating and Assigning an Activity Type and a Price ....................................... 70

11.9 Defining Number Ranges for Internal Order Types .......................................... 71

11.10 Create Account Assignment Groups for Internal Business Partners .............. 72

11.11 Assign Account Assignment Group to Business Partner ................................ 73

11.12 Assign Account Assignment Group to Material ............................................... 74

11.13 Revenue Account Determination .................................................................... 75

11.14 Processing and Activating the Results Area ................................................... 76

11.15 Assigning SD Condition Types to Value Fields ............................................... 77

11.16 Defining Account Assignment for Cost Posting in Order ................................ 78

11.17 Defining Internal Order Type for Bill-To Party ................................................. 79

11.18 Defining Parameters for Settlement Rule ....................................................... 80

11.19 Collective Order Control .................................................................................. 82

11.20 Defining Internal Order Account Assignment .................................................. 84

11.21 Internal Order Account Revaluation ................................................................ 88

11.22 Release Production Order Immediately .......................................................... 89

11.23 Automatic Postings.......................................................................................... 90

11.24 Defining Default Values for Cost Object Controlling ....................................... 91

11.25 Defining Valuation of Goods Received ........................................................... 92

11.26 Defining Profit Center Control ......................................................................... 93

11.27 Defining Reports in the Information System ................................................... 94

11.28 Field Control Movement Type 261 Account 410000 ....................................... 95

11.29 Defining Document Type for Customer Advance Payment (Deposits) ........... 96

11.30 Defining External Service ................................................................................ 97

11.31 Setting Up Profitability Analysis (CO-PA) ........................................................ 98

12 Parts ..................................................................................................................... 99

12.1 Creating Spare Parts ....................................................................................... 100


12.2 Creating a Sales Price for Spare Parts ........................................................... 102

12.3 Search Help for Spare Parts ........................................................................... 103

12.4 Exchange Parts ............................................................................................... 104

12.4.1 Setting Up Customizing ................................................................................ 105

12.4.2 Setting Up the Material Master ..................................................................... 106

12.4.3 Restricting Material Group for Material Search ............................................ 107

12.4.4 Assignment of SD Conditions to Value Fields ............................................. 108

13 Service ............................................................................................................... 109

13.1 Defining a Labor Value Catalog ...................................................................... 110

13.2 Defining a Hierarchy Level .............................................................................. 111

13.3 Determining a Catalog .................................................................................... 112

13.4 Creating a Labor Value Group ........................................................................ 113

13.5 Creating a Dummy Material for Labor Value ................................................... 114

13.6 Creating Labor Values .................................................................................... 115

13.7 Creating a Sales Price for Labor Values ......................................................... 117

13.8 Defining a Service Package ............................................................................ 118

13.9 Creating Customer Advisers ........................................................................... 119

13.10 Appointment Scheduling ............................................................................... 120

13.10.1 Defining a Job Catalog ............................................................................... 121

13.10.2 Defining a Hierarchy Level ......................................................................... 122

13.10.3 Determining a Job Catalog ......................................................................... 123

13.10.4 Defining a Workshop Department .............................................................. 124

13.10.5 Creating Job IDs......................................................................................... 125

14 Quality Inspection of Vehicle Service ................................................................. 126

14.1 Setting Up Quality Inspection of Vehicle Service ............................................ 127

15 Service Contracts ............................................................................................... 128


15.1 Assigning a Service Item Group ...................................................................... 129

15.2 Determining Contract Split Indicator ............................................................... 130

16 Vehicle ................................................................................................................ 131

16.1 Assigning an Internal Order Type in the Control Table ................................... 132

16.2 Enhancement Concept (Vehicle) .................................................................... 133

16.3 Vehicle Search ................................................................................................ 135 16.3.1 Vehicle Search with Search Engine TREX ......................................................... 135

16.3.1.2 Transaction COM_SE_ADMIN .............................................................. 135 16.3.2 Vehicle Search using SAP HANA ....................................................................... 135

16.4 Creating a Dummy Material for the Vehicle Model ......................................... 136

16.5 Creating a Dummy Material for Vehicle Features ........................................... 138

16.6 Creating Search-Relevant Customizing .......................................................... 140

16.7 Determining the Navigation Profile .................................................................. 141

16.8 Maintaining the Model Catalog ........................................................................ 142

16.9 Model Catalog Determination .......................................................................... 143

16.10 Creating a Vehicle Model .............................................................................. 144

16.11 Assigning Vehicle Model and Users to VMS Roles ...................................... 145

16.12 Action Control ................................................................................................ 146

16.13 Defining Number Ranges for Internal Vehicle Number ................................. 147

16.14 Maintaining Number Ranges for Vehicle Chain Order Group ....................... 148

16.15 Creating a Customer ..................................................................................... 149

16.16 Creating a Vehicle and Assigning a Customer ............................................. 150

16.17 Mass Vehicle Processing .............................................................................. 151

16.17.1 Enhance the Action Control ....................................................................... 152

16.17.2 Enhance VMS Action Technical Details ..................................................... 153

16.17.3 Define Bulk Actions .................................................................................... 154

16.17.4 Define Vehicle Creation Control Value ...................................................... 155


16.17.5 Determine Vehicle Stock Age .................................................................... 156

16.18 Additional Costs ............................................................................................ 157

16.18.1 Define Categories for Additional Costs ...................................................... 158

16.18.2 Create Dummy Material for Additional Cost Category ............................... 159

16.18.3 Assign Material to Additional Cost Category .............................................. 160

17 Vehicle Sales Assistant ...................................................................................... 161

17.1 Maintaining Number Ranges for the DBM Deal .............................................. 162

17.2 Assign Notification Types ................................................................................ 163

17.3 Define Alias for VSA Events ............................................................................. 164 Procedure ....................................................................................................................... 164

17.4 Define Hierarchy Mapping ............................................................................... 165

17.5 CRM-DBM Integration ..................................................................................... 166

17.5.1 Map CRM Product Category to DBM Technical Item Category ................... 167

17.5.2 Map CRM Lead Partner to DBM Deal Partner ............................................. 168

17.5.3 Map CRM Lead Source to DBM Notification Source ................................... 169

17.5.4 Assign Default Task Code For Notification Type ......................................... 170

17.6 Define Object Control Framework - Event Schema ........................................ 171

17.7 Define Automatic Rejection Reason for Quotations ........................................ 172

17.8 Assign Rejection Reason ................................................................................ 173

17.9 Define Calculation Sheet .................................................................................. 174

17.10 Deal Search ..................................................................................................... 175 17.10.1 Deal Search with Search Engine TREX ............................................................ 175 17.10.1.1 Setting Up the RFC Connection ..................................................................... 175 17.10.1.2 Transaction COM_SE_ADMIN for Deal Search ............................................ 175 17.10.2 Deal Search using HANA .................................................................................. 175

17.11 Activity Search ......................................................................................................... 176 17.11.1 Activity Search Using TREX .............................................................................. 176 17.11.2 Activity Search using SAP HANA ...................................................................... 176

17.12 Model Search ........................................................................................................... 177 17.12.1 Model Search Using TREX ............................................................................... 177 17.12.2 Model Search using SAP HANA ....................................................................... 177

17.13 Business Partner Search ......................................................................................... 177 17.13.1 Business Partner Search Using TREX.............................................................. 177 17.13.2 Business Partner Search using SAP HANA ..................................................... 178


17.14 SAP Business Warehouse Management Integration in DBM ........................ 179

17.15 Activity Printing ................................................................................................ 181

18 Warranty Processing .......................................................................................... 182

18.1 Warranty Customizing ..................................................................................... 183

18.2 Assigning Warranty Claim Item Type – Order Item Category ......................... 184

18.3 Editing Warranty Data ..................................................................................... 185

18.4 Defining Catalog Code .................................................................................... 187

18.5 Defining Automatic CO Account Assignment Determination .......................... 188

18.6 Allowing Change of CO Account Assignments for Condition ......................... 189

18.7 Defining Warranty Number Range .................................................................. 190

18.8 WTYRCL Customizing .................................................................................... 191

18.9 Defining Recall Priority .................................................................................... 192

18.10 Defining Order Type and Warranty Category for Recalls ............................. 193

18.11 Assigning Item Type and Item Category to OEM .......................................... 194

19 Cash Desk .......................................................................................................... 195

19.1 Setting Characteristics of Document Type SK ................................................ 196

19.2 Defining Business Transactions ...................................................................... 197

19.3 Assigning a Number Range to Cash Desk Document Types ......................... 198

19.4 Setting Up a Cash Desk Work Center............................................................. 199

20 Dynamic Sheet ................................................................................................... 200

20.1 Define Style ..................................................................................................... 201

20.2 Define Content Object ..................................................................................... 202

20.3 Define Content Object Parameters .................................................................. 203

21 Notification .......................................................................................................... 204

21.1 Maintaining Enhancements and BAdI Implementations ................................. 205

21.2 Defining Notification Types for DBM ............................................................... 206


21.3 Defining Outcome Type and Outcome Code .................................................. 207

21.4 Assigning Outcome Type to Task Code.......................................................... 208

21.5 Assigning Task Code to Order Type ............................................................... 209

21.6 Defining Follow-Up Task Code ....................................................................... 210

21.7 Setting BAdI: Input Help for Outcome Type .................................................... 211

21.8 Setting BAdI: Input Help for Outcome Code ................................................... 212

21.9 Setting BAdI: Input Help for Outcome Code Value ......................................... 213

21.10 Setting BAdI: Filter Text of Outcome Code ................................................... 214

21.11 Configuring E-Mail for Notification................................................................. 215

22 Order .................................................................................................................. 216

22.1 Order Search ................................................................................................... 217 22.1.1 Order Search with Search Engine TREX ............................................................ 217

22.1.1.2 Transaction COM_SE_ADMIN for Order .............................................. 217 22.1.2 Order Search using HANA ................................................................................. 218

22.3 Defining Order Search..................................................................................... 219

22.4 Defining Enhanced Order Search ................................................................... 220

22.4.1 Defining BAdI: Enhanced Order Search - UI Enhancement ........................ 223

22.4.2 Defining BAdI: Enhanced Order Search - Criteria Enhancement ................ 224

22.4.3 Defining BAdI: Enhanced Order Search - Result Enhancement ................. 225

22.5 Up-selling and Cross-selling ........................................................................... 226

22.5.1 Define Proposal Type ................................................................................... 227

22.5.2 Define Replacement Procedure ................................................................... 228

22.6 Defining a Reason for Rejection ..................................................................... 229

22.7 Working with Suborders .................................................................................. 230

22.8 Defining Copying of Order Items ..................................................................... 232

22.9 Define Order Type Schema ............................................................................. 233

23 Archiving ............................................................................................................. 234


23.1 Maintaining Enhancements and BAdI Implementations ................................. 235

23.2 Archiving Control for DBM Order .................................................................... 236

24 Time Recording .................................................................................................. 237

24.1 Creating Customer Include Fields for Table CATSDB .................................... 238

24.2 Transferring DBM Data to CATS ..................................................................... 239

24.3 Setting Up Data Entry Profiles ........................................................................ 243

24.4 Maintaining HR Master Data ........................................................................... 244

24.5 Additional Information...................................................................................... 245

25 Integration with SAP Credit Management .......................................................... 246

25.1 Setting Up the Credit Limit Check ................................................................... 247

25.2 Setting Up the Documented Credit Decision .................................................. 249

26 Storage Goods Manager .................................................................................... 250

26.1 Creating Required Master Data ...................................................................... 251

26.2 Integrating Storage Goods into Memo Pad ..................................................... 253

26.3 Defining Number Range for Storage Goods ................................................... 254

26.4 Defining Storage Type for Putaway ................................................................ 255

26.5 Defining Putaway Location .............................................................................. 256

26.6 Defining Putaway Bin ...................................................................................... 257

26.7 Defining Permitted Storage Type for Putaway for Each Warehouse .............. 258

26.8 Defining Wheel Rim Size ................................................................................ 259

26.9 Defining Wheel Rim Type ............................................................................... 260

26.10 Defining Wheel Rim Manufacturer ................................................................ 261

26.11 Defining Tire Size .......................................................................................... 262

26.12 Defining Tire Manufacturer ............................................................................ 263

26.13 Defining Standard Position of Storage Goods .............................................. 264

26.14 Defining Reminder / Expediting Data ............................................................ 265


26.15 Defining Status .............................................................................................. 266

26.16 Defining Actions ............................................................................................ 267

26.17 Defining Action Matrix ................................................................................... 268

26.18 Defining Printout Forms ................................................................................ 269

26.19 Defining Condition Tables ............................................................................. 270

26.20 Defining Access Sequence ........................................................................... 271

26.21 Defining Message Types ............................................................................... 272

26.22 Defining Message Schema ........................................................................... 273

27 Text Handling ..................................................................................................... 274

27.1 Defining Criteria Table..................................................................................... 275

27.2 Defining Access Sequences ........................................................................... 276

27.3 Defining Control Model Master ........................................................................ 277

27.4 Defining Control Vehicle Master ...................................................................... 278

27.5 Defining Control Labor Value Master .............................................................. 279

27.6 Defining Control Package Master ................................................................... 280

27.7 Defining Control Memo Pad ............................................................................ 281

27.8 Defining DBM Order Control ........................................................................... 282

27.9 Defining Storage Goods Control ..................................................................... 283

27.10 Defining Rule Key.......................................................................................... 284

27.11 Defining BAdI: Definition of Rule ................................................................... 285

27.12 Defining Text Determination Logic Key ......................................................... 286

27.13 Defining BAdI: Definition of Text Determination Logic .................................. 287

27.14 Defining Text Handling for Purchase Requisition ......................................... 288

28 Sundry Items in a Fleet Order ............................................................................ 289

28.1 Creating Activity Type for Sundry Items .......................................................... 290

29 Optional Components......................................................................................... 291


29.1 SAP Incentive and Commission Management Integration ............................. 292

29.2 SAP Multi Resource Scheduling Integration ................................................... 293


1 General Information

Customizing

All Customizing (table contents of DBM and ERP tables) which is changed in DBM 810 with respect to DBM 810 is part of the object list of the DBM 810 installation. All customizing entries delivered with DBM 810 are included in the BC Sets listed in the following table. The

BC Set /DBM/DBM800_BASIS contains basic settings for all DBM processes. Its activation is

mandatory. All other BC Sets only need to be activated if the corresponding process will be used in your system.

Note: You must activate the BC sets with Expert Mode and Deletion Functionality – Enable for Classical BC Sets indicators selected.

Function BC Set Description

Basic Settings /DBM/DBM800_BASIS Basic Settings for DBM 800; activation of this BC Set is mandatory

Calculation Sheet /DBM/DBM800_CALC_SHEET Settings for DBM Calculation Sheet

Cash Desk /DBM/DBM800_CASHDESK Settings for DBM Cash Desk

Credit Limit Check /DBM/DBM800_CLC Settings for DBM Credit Limit Check

Profitability Analysis (CO-PA)

/DBM/DBM800_COPA Settings for CO-PA Integration

Enhanced Order Search

/DBM/DBM800_EOS Settings for DBM Enhanced Order Search

Exchange Part Process

/DBM/DBM800_EXP Settings for DBM Exchange Part Process

Fleet Order Process

/DBM/DBM800_FLEET Settings for DBM Fleet Order Process

Notification /DBM/DBM800_NTF Settings for DBM Notification

Order Mass Processing

/DBM/DBM800_OMP Settings for DBM Order Mass Processing

Price Limit Check /DBM/DBM800_PRICE_LIMT_CHECK Settings DBM Price Limit Check

Quality Inspection /DBM/DBM800_QUAL_CHECK Settings for DBM Quality Inspection

Vehicle Service History

/DBM/DBM800_SERV_HIST Settings for DBM Vehicle Service History

Up-selling and Cross-selling

/DBM/DBM800_UPS_CRS Settings for DBM Up-selling and Cross-selling

Vehicle Mass Transaction

/DBM/DBM800_VEH_MASS Settings for DBM Vehicle Mass Transaction


Vehicle Sales Assistant

/DBM/DBM800_VSA Settings for DBM Vehicle Sales Assistant

Workshop Controller’s Cockpit

/DBM/DBM800_WCC Settings for DBM Workshop Controller’s Cockpit

Customizing for the optional components SAP Multi Resource Scheduling (MRSS) and SAP Incentive and Commission Management (ICM) is delivered with the following BC Sets and must be activated separately:

Function BC Set Description

Appointment Scheduling

/DBM/DBM800_MRSS DBM–MRSS–specific Customizing; needs to be activated before /DBM/DBM800_APP_SCH

/DBM/DBM800_APP_SCH Settings for Appointment Scheduling

Incentive and Commission Management

/DBM/DBM800_ICM DBM–ICM–specific Customizing

Customizing Adjustments after Upgrade

Background of DBM Customizing Delivery during Upgrade

The SAP Dealer Business Management solution is highly flexible, and therefore relies extensively on Customizing settings. Changes to Customizing entries are usually delivered by a support package.

The reasons behind these changes are usually the refinement of processes or architectural reasons. Note that these Customizing changes in DBM are made for reasons whose ultimate objective is to improve the quality of the solution, and prevent any issues in the future.

Therefore, we highly recommend that these changes are reviewed and migrated to your existing Customizing.

The following steps describe this process.

Important Information

Before upgrading or applying a support package, we recommend that you generate a version for the current DBM Customizing in order to track any changes. This is beneficial, especially in cases where there are new table entries (relevant mainly for Customizing tables with delivery class G). To generate a version, make the following setting in Customizing for Dealer

Business Management under Framework Components Customizing Versioning Tools

Version Generator . Alternatively, you can compare the Customizing across your different systems, for example between your development and test systems.

How to Adjust the Customizing

Version Analyzer Overview:

1. You can locate the DBM delivery Customizing provided by SAP in your system in client 000.

2. The DBM solution provides a tool to help you analyze the changes to be made.

3. Note that the Version Analyzer provides an indication regarding the changes to be made. If you made any changes in the standard Customizing, then it is important to review the Version Analyzer display.


4. The Version Analyzer has grouped sets of Customizing tables, called Usages, based on the applications that use them.

5. You can select a usage in the Version Analyzer, and analyze the corresponding Customizing tables for the usage.

6. The following usages are available for analysis:

Usage Description

BILL Billing

INCOMPLLOG Incompletion Log

LAYOUT Order Layout

SAPGUI LC Lean Condition Generic Tables

OCF Object Control Framework

OE Order Control

ORDTP_SCHM Order Type Schema

ORD_PROCST Order Process Status

PRIC Pricing

VMSMATRIX Tables used in Vehicle Master

WD_UI WebDynpro/Drive UI Framework

Steps while Using the Version Analyzer:

1. Navigate to the Version Analyzer by using transaction /DBM/OE_VT_ANZ, or see

Customizing for Dealer Business Management under Framework Components

Customizing Versioning Tools Version Analyzer .

2. Select, for example, the usage OE and choose Execute.

3. On the left side, in Reference, select version type N - Current Customizing.

4. Select reference version 00000 Current Customizing.

5. Select the comparison version type D - Other Client.

6. Select the comparison version 000 - SAP AG (delivery Customizing).

7. You can choose the tables and check for entries that may need to be deleted, changed, or created.

8. If no changes have been made to the previous delivery Customizing and if the above instructions are followed correctly, the system displays the following entries:

o A red entry is a Customizing entry that can be deleted.

o A green entry is a Customizing entry that can be added.

o A yellow entry is a Customizing entry that can be changed.

9. Repeat the above steps for all the tables and all the usages and make the Customizing changes accordingly.


2 Generic Settings for Searches

2.1 Generic Settings for Searches Based on TREX TREX can be installed in the same server as DBM for test or evaluation purposes. System prerequisites are SAP NetWeaver 7.0, TREX 7.0, Version 39. In order to be able to use the search functions in DBM you must have TREX installed and configured. You can find further information about the installation of TREX on the SAP Service Marketplace under service.sap.com/instguides -> SAP NetWeaver -> SAP NetWeaver 7.4 -> Installation -> Installation - Standalone Engines and Clients Master Guide.

2.1.1 Setting Up the RFC Connection Procedure

1. On the SAP Easy Access screen, choose Tools Administration Administration

Network RFC Destinations.

2. Enter an RFC destination (default value: TREXDEFAULT_REG ).

3. Enter the connection type T (TCP/IP connection).

4. On the tab page Technical Settings, enter the following data:

o Choose Registered Server Program.

o Enter a program ID (default value: TREXRfcServer_00).

o Enter a gateway host and a gateway service.

5. On the Special Options tab page, set the indicator for non-unicode and the default setting for character conversion.

If TREX is installed on the same server as DBM, for example for test or evaluation purposes, make the following entries from the SAP Easy Access

screen by choosing Tools Administration Administration Network

RFC Destinations

o Connection type: T (TCP/IP connection)

o Technical settings:

Indicator for starting on explicit host

Program ID: d:\usr\sap\trex_01\TREXRfcServer.exe, or as indicated in the TREX installation document

IP address

Enter gateway host and gateway service

2.1.2 Transaction COM_SE_ADMIN Procedure 1. Enter transaction code COM_SE_ADMIN and then choose Goto -> Customizing -> System Settings -> Change -> New Entries. 2. Enter the following data:


o RFC Destination (default value TREXDEFAULT_REG)

o Search Engine: CL_COM_SE_TREX

o Max. Auth.Check: 100

3. Choose Goto -> Back.

2.1.3 Delta Indexing of TREX Objects

1. To plan a recurring job for the delta load, choose System Services Jobs Job

Definition .

2. Choose Step ABAP Program and execute report COM_SE_DISPATCHER

without a variant.

3. Enter the following data:

o Start condition: Immediate

o Period values: Other Period: 2 minutes

The period value depends on how often the data in the search engine is to be updated and how often the vehicle data is changed.

2.2 Generic Settings for SAP HANA-based Searches (Without TREX)

2.2.1 Set up Connection to SAP HANA Database Using DBCO

Implement steps provided in http://help.sap.com/nw74/ -> Application Help -> Function-Oriented View -> Search and Operational Analytics -> Embedded Search -> Setting Up Embedded Search -> Creating a Connection Between Embedded Search and SAP HANA or TREX/BWA.

2.2.2 Define Destination for Search Procedure

1. In Customizing, go to SAP NetWeaver -> Search and Operational Analytics -> SAP NetWeaver Enterprise Search -> HANA / TREX Connectivity -> Set HANA or TREX Destination.

2. Select Use SAP HANA option and enter there the database connection name created using DBCO transaction.

3. Choose Execute. Enhancement for SAP HANA Search 1. Maintain SAP HANA search objects in Customizing, under Logistics Execution -> Dealer Business Management (DBM) -> Enhancements for Embedded Search on SAP HANA -> Maintain SAP HANA Search Objects. 2. If enhancements are required, implement BAdI definition /DBM/BADI_ES_HANA_SRCH_PREP. In Customizing, go to Logistics Execution -> Dealer Business Management (DBM) -> Enhancements for Embedded Search on SAP HANA -> Embedded Search on SAP HANA: Criteria and Result Preparation.


3 Configuring a Client Use

You can use this procedure to create a logical system and make the client settings.

Procedure

1. In Customizing for SAP NetWeaver , choose SAP Web Application Server

System Administration Change & Transport System Configure Clients .

2. Choose the appropriate client.

3. Enter a logical system.

The default value is <system ID>CLNT<client number> .

4. In the field Std currency (standard currency), choose your own standard currency, for example EUR, USD.


4 Defining Field Control for the Loading Group and Transportation Group (HAWA) Use

The two fields MARA-TRAGR and MARC-LADGR, field selection group 94 are defined as required entries. Define both fields for the material type HAWA as optional entries. Otherwise, you have to set the entries 0001 and 0001.

Procedure

1. In Customizing for Logistics - General , choose Material Master Field Selection

Maintain Field Selection for Data Screens.

2. Choose the field selection group 94 and set the Opt. entry (optional entry) indicator for the following field references:

o HAWA

o MM01

o MM02


5 Enterprise Structure


5.1 Defining the Credit Control Area Procedure

1. In Customizing for the Enterprise Structure , choose Definition Financial

Accounting Define Credit Control Area.

2. Enter the credit control area 0001 .

3. Ensure that the field Update is blank. This means that no update of data from sales documents will take place.


5.2 Assigning Organizational Elements Use

To represent your enterprise structure in the system, you must assign the following distribution channels:

Q1 DBM new vehicles

Q2 DBM used vehicles

Q3 DBM service

Q4 DBM parts sales

Procedure

Execute the following activity in Customizing for the Enterprise Structure under Assignment

Sales and Distribution :

Assign sales organization to company code

Assign division to sales organization

Set up sales area

Assign sales office to sales area

Assign sales organization - distribution channel - plant

Assign sales area to credit control area (credit control area 0001)


5.3 Integrating Warehouse Management Prerequisites

The standard ERP Customizing settings specify that lean Warehouse Management (WHM) is

used for plant 0001, storage location 0001. Lean WHM must be deactivated. The standard

ERP Customizing settings specify entries for WHM usage with warehouse numbers assigned to plants and storage locations. If the DBM delivery process is used without WHM, the standard ERP delivery Customizing entries for WHM usage must be deleted for the relevant plants and storage locations where the DBM delivery is used.

If the DBM delivery process is used with WHM, lean WHM, or extended WHM, contact an SAP WHM expert for support.

Procedure

1. In Customizing for Enterprise Structure, choose Assignment Logistics Execution

Assign warehouse number to plant/storage location .

2. Delete the entry for plant 0001 and storage location. Delete the entries for relevant

plants and storage locations where the DBM delivery is used without WHM.


6 Logistics General


6.1 Setting Up Conversion Exit for Material Numbers Use

Instead of the 18-character material number, you can use the 40-character manufacturer part number.

The long Material number must be activated if you want to use the OEM-part numbers.

See also the following SAP Notes:

SAP Note Number Description

1152963 Activation of long material number

615290 MPN Conversion Exit: FAQ

831966 Restrictions when implementing the long material

735529 FAQ: DIMP/DI long material number and MPN

Procedure

1. In Customizing for Logistics - General , choose Interchangeability of Parts Set Up

Conversion Exit for Material Numbers.

2. Set the Active conversion exit indicator.

3. In the Output Length field, define the length of the manufacturer part number.

4. In the Delimiter field, you can enter a delimiter with which the manufacturer part number and manufacturer code can be separated. You can also set the Display ext. manufacturer indicator.

The conversion exit is not active in the standard system. If the conversion exit is not active, you must set the material number display to 18 characters.


6.2 Defining the Batch Level Use

You require batch management for the vehicle. The batch number is always one, in other words, a vehicle.

Procedure

1. In Customizing for Logistics – General, choose Batch Management Specify Batch

Level and Activate Status Management Batch Level.

2. Select Batch unique at material level.


6.3 Activating Internal Batch Number Assignment Use

When a new client is created from a client copy, internal number assignment in the target client is not active and must be activated manually.

Procedure

1. In Customizing for Logistics - General , choose Batch Management Batch

Number Assignment Activate Internal Batch Number Assignment Activate Batch

Number Assignment.

2. Select the radio button Automatic batch number assignment active.


6.4 Processing Number Ranges for Internal Batch Number Assignment Use

In the standard system, the number range 01 is defined with the interval 0000000001 to 9999999999 for the number range object BATCH_CLT.

Procedure

1. In Customizing for Logistics - General, choose Batch Management Batch Number

Assignment Maintain Internal Batch Number Assignment Range.

2. Check whether the number range 01 exists and, if necessary, maintain new number ranges.


6.5 Maintaining Company Codes for Materials Management Procedure

1. In Customizing for Logistics -General, choose Material Master → Basic Settings → Maintain Company Codes for Materials Management.

2. For company code 0001, enter the current year in the field Year and the current month in the field Period.

3. Set the ABp indicator (Allow Posting to Previous Period (Backposting)).


6.6 No Update of MOFF/MSTA Data with Separate Evaluation Procedure

For better performance, we recommend you set the flag No Update During Split Valuation on the Administration Data Update screen in the customizing transaction OMT0.


7 Sales and Distribution


7.1 Defining Common Distribution Channels and Divisions Use

A common distribution channel can be assigned to DBM distribution channels for master data created for customers and pricing conditions. In this case, you create this master data only for the reference distribution channel.

Procedure

1. In Customizing for Sales and Distribution, choose Master Data Define Common

Distribution Channels.

2. Reference all DBM-specific entries to sales organization 0001 and distribution channel 01. In other words, enter 01 in the fields DCh-Conds (reference distribution channel for conditions) and DCh-Cust/Mt (reference distribution channel for customers and material masters).


7.2 Defining Conditions for Value-Added Tax Procedure

1. On the SAP Easy Access screen, choose Logistics Logistics Execution Dealer

Business Management Master Data Pricing Condition Create Condition .

2. Enter MWST in the field Condition Type , then choose Key Combination and set the indicator Domestic Taxes.

3. Choose DE Germany in the field RecipCntry (recipient country) and enter the following data in the table:

Tax Classification (Customer) Tax Classification (Material) Tax Indicator

0 0 A0

0 1 A0

0 2 A0

1 0 A0

1 1 A1

1 2 A2


8 Materials Management


8.1 Adjusting Movement Types

If you plan to use DBM-related movement types for the DBM delivery integration, you have to adjust them. If the DBM delivery process is used, you have to adjust the following movement types (which are currently relevant and used in DBM). The changes facilitate goods issue

cancellation for DBM deliveries by using transaction VL09.

Procedure

1. In Customizing for Materials Management, choose Inventory Management and

Physical Inventory Movement Types Copy, Change Movement Types .

2. Allow transaction VL09 for the following movement types:

o 261

o 501

o 502


9 Dealer Business Management (DBM)


9.1 Defining an External Manufacturer Use

You define external manufacturers as original equipment manufacturers (OEM). You require the external manufacturer for the assignment of the division, in other words, the vehicle brand, to the manufacturer.

Procedure

1. From the SAP Easy Access screen, choose Logistics Execution Master Data

Partner Vendor Create.

2. Enter the creditor with the account group LIEF (creditors, external number assignment).

3. Enter the data for the external manufacturer in the Address and Control Data views.


9.2 Assigning an External Manufacturer Use

The original equipment manufacturer (OEM) has a controlling effect. You can use the manufacturer, for example, to control the interface or determine the labor value catalog.

Procedure

1. In Customizing for Logistics Execution , choose Dealer Business Management

(DBM) Enterprise Structure Assign Divisions to OEMs.

2. Enter a manufacturer for each division.


9.3 Maintaining Number Ranges for the DBM Order Use

To maintain number ranges for the DBM order, you use the number range object called /DBM/Order.

Procedure

1. In Customizing for Logistics Execution, choose Dealer Business Management

(DBM) Order Order Type Maintain Number Range for DBM Order.

2. Create a number range interval for the group DBM Order.


10 Business Partner Configuration Important SAP Notes

SAP Note Description

SAP Note 1076698

Refer to this SAP Note if you encounter the following problem: If you create a customer role and immediately the sales organization data, the business partner transaction dumps when saving.

SAP Note 956054

Customer/vendor integration as of ERP 2005

SAP Note 954816

Transactions for creating/linking business partners.

SAP Note 941955

Integration of FI customers/vendors with SAP business partner.

SAP Note 1076698

For creating sales organization data and new business partner with one commit at the same time (to avoid short dump).

The replication of data between business partner, customer master and vendor master is bidirectional and synchronous. The changes in the business partner are replicated directly within the same LUW to the corresponding ECC object, and vice versa.


10.1 Prerequisite Settings Procedure

The following Customizing settings are required for CVI:

Activate Synchronization Options

In Customizing for Cross-Application Components, navigate to Master Data

Synchronization Synchronization Control Synchronization Control Activate

Synchronization Options.

You must activate the following replications for synchronization between the business partner and the customer in DBM:

From business partner to customer

From business partner to vendor

From customer to business partner

From customer to business vendor

Post Processing Office (PPO) and Synchronization cockpit

If you want to use the business partner in DBM, you must first start the MDS cockpit first to create business partners for existing customers. The MDS cockpit creates the customer role and the FI customer role as well if the company code data is available.

You can use the synchronization cockpit [External] for mass creation of business partners from customers and vendors.


Synchronization Synchronization of Mass Data Execute Synchronization Cockpit .

The Postprocessing Office (PPO) is integrated in the synchronization cockpit, so that it can be used to process synchronization errors. If the PPO has not been activated, the synchronization cockpit does not start synchronization if errors occur. The system displays the relevant error message.

You can use the transactions below to execute the CVI process for one customer/vendor (for example, for creating a business partner for an existing customer):

1. FLBPD1: Create a business partner based on the selected customer.

2. FLBPC1: Create a business partner based on the selected vendor.

3. FLBPD2: Assign business partner to customer.

4. FLBPC2: Assign business partner to vendor


You can connect the master data synchronization between the business partner and the customer to the PPO. After you define the connection, the system writes a postprocessing order (PPO order) if an error occurs during the synchronization. You can use transaction MDS_PPO2 (Postprocessing Desktop) to call the postprocessing orders. You can use this function to analyze and process errors. You set up the PPO for the synchronization between the business partner and the customer. If an error occurs, there are inconsistent datasets in the systems until the PPO orders are processed consistently.

If you do not activate the PPO for the master data synchronization between the business partner and the customer, the system generates a short dump if an error occurs. The system displays the cause of the synchronization error in the error table LS_ERROR-OBJECTS in the dump / debugger. We recommended that you to activate the PPO for the testing phase. Otherwise, it should be deactivated so that the errors cause immediately a short dump that you can analyzed.

To connect the CVI to the PPO, you must make two Customizing settings:

1. Activate the PPO for the synchronization object BP


Synchronization Synchronization Control Synchronization Control Activate PPO

Requests for Platform Objects in the Dialog .

Activate the PPO for the synchronization object BP (use input help).

2. Activate Creation of Postprocessing Orders

In Customizing for Cross-Application Components, navigate to General Application

Functions Postprocessing Office Business Processes Activate Creation of

Postprocessing Orders .

For the software component AP-MD, make the following entries:

Component Business Object Act

AP-MD CVI_01 X

AP-MD CVI_03 X

For further controlling of postprocessing orders (workflow connection), refer to the Customizing documentation for the required steps.


10.1.1 Synchronization from Business Partner to Customer Procedure

You must define the customer business partner role categories.

In Customizing for Cross-Application Components , navigate to Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Customer Integration → Set BP Role Category for Direction BP to Customer .

If the business partner role changes, CVI automatically updates the SD customer.

Enter the following data:

Field Value

BP Role Cat FLCU01

Description Business Partner Customer (FS: BP)

Custmr-Based Yes

Optional for Customer No

Role Control Setting BPOD_TRD001_DEB_ROLLE

Default Settings

Field Value

BP Role Cat. FLCU00

Description Business Partner FI Customer (FS: BP)

Custmr-Based Yes

Optional for Customer No

Role Control Setting

Default Settings


10.1.2 Synchronization from Business Partner to Vendor Procedure

You must define the vendor business partner role categories.

In Customizing for Cross-Application Components , navigate to Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Vendor Integration → Set BP Role Category for Direction BP to Vendor .

If the business partner role changes, CVI automatically updates the SD vendor.


Role Cat. Description

FLVN00 Business Partner FI Vendor (FS:BP)

FLVN01 Business Partner Vendor (FS:BP)


10.1.3 Synchronization from Customer to Business Partner Procedure

You must define business partner roles.

In Customizing for Cross-Application Components , navigate to Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Customer Integration → Define BP Role for Direction Customer to BP .

When you create an SD customer, CVI automatically creates the roles Customer und FI Customer.

See the example settings below:

Group BP Role

0001 FLCU00

0001 FLCU01

0005 BUP002

DEBI FLCU00

DEBI FLCU01

KUNA FLCU00

KUNA FLCU01


10.1.4 Synchronization from Vendor to Business Partner Procedure

You must define business partner roles.

In Customizing for Cross-Application Components , navigate to Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Vendor Integration → Define BP Role for Direction Vendor to BP

When you create an SD vendor, CVI automatically creates the Vendor und FI Vendor roles.


Group BP Role

0001 FLVN00

0001 FLVN01

KRED FLVN00

KRED FLVN01

LIEF FLVN00

LIEF FLVN01


10.1.5 Define Number Assignment for Direction BP to Customer Procedure

For the number assignment from the business partner to the customer and vice versa, you must assign the groupings and number ranges.

In Customizing for Cross-Application Components , navigate to Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Customer Integration → Field Assignment for Customer Integration → Assign Keys: Define Number Assignment for Direction BP to Customer.

It is not possible to set the flag “same number” for the internal number range.


Group. Short Name Acc. Name Same Number

0001 Int. No. Assgnmnt 0001 Sold-to Party No

0002 Ext. No. Assgnmnt KUNA Customer (ext. number assgnmnt) Yes

GPEX Ext. No. Assgnmnt DEBI Customer (general) No

GPIN Int. No. Assgnmnt DEBI Customer (general) No

If you want to have the same internal numbers for the business partner and for the automatically created SD customer, the same number range must be applied to the business partner and to the customer. Navigate to Logistics General → Business Partner → Customers → Control → Define Account Groups and Field Selection for Customers . The number range for the business partner is internal. The number range for the customer is set to external.

In this case, the customer cannot created with an internal number, only by using another account group with internal number range assignment. If you want to create customers that have the same internal number as the related business partner, another account group account group for the business partner with internal number range is needed. The business partner’s internal number range should be the same as the customer’s number range, but the customer’s should be external.

During the upgrade the same internal number distribution can be provided as follows (if the customer already has SD customer in the system):

1. Create a business partner from the customer with MDS. Set up the same number range for the business partner as it is for the customer.

2. Create new number ranges - the same for the business partner and customer, and start creating business partners (and customer automatically in the background with CVI) with these new number ranges.


10.1.6 Define Number Assignment for Direction BP to Vendor Procedure

For the number assignment from the business partner to the vendor, and vice versa, you must assign the groupings and number ranges.

In Customizing for Cross-Application Components , navigate to Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Vendor Integration → Field Assignment for Vendor Integration → Assign Keys: Define Number Assignment for Direction BP to Vendor.

It is not possible to set the flag “same number” for the internal number range.


Group. Short Name Acc. Name Same Number

0001 Int. No. Assgnmnt 0001 Vendor No

0002 Ext. No. Assgnmnt LIEF Vendor (ext. number assgnmnt) Yes

GPEX Ext. No. Assgnmnt KRED Vendor (int. number assgnmnt) No

GPIN Int. No. Assgnmnt KRED Vendor (int. number assgnmnt) No

To provide the same internal numbers for the business partner and for the vendor, the same method can be applied as described in Define Number Assignment for Direction BP to Customer.


10.1.7 Define Number Assignment for Direction Customer to BP Procedure

Customer account groups are assigned to the business partner groupings relevant for the replication. Using the related number ranges, the system determines whether the customer numbers are assigned internally or externally, or whether there is number equivalence. See the example settings below:

Group Grp. Same No.

0001 0001 No

KUNA 0002 Yes


10.1.8 Define Number Assignment for Direction Vendor to BP Procedure

Account groups of the vendor are assigned to the business partner groupings relevant for the replication. Using the related number ranges, the determination is made as to whether the vendor numbers are assigned internally or externally or whether there is number equivalence. See the example settings below:

Group Grp. Same No.

0001 0001 No

KRED 0001 No

LIEF 0002 Yes


10.1.9 Business Add-Ins (BAdIs) Procedure

The following BAdIs are available for customer-specific mapping.

In Customizing for Cross-Application Components , navigate to Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Business Add-Ins (BAdIs)

BAdI: Data Assignment BP <-> Customer/Vendor/Contact Person.

BAdI: Data Assignment of Bank Details BP -> Customer/Vendor.

BAdI: Data Assignment of Payment Cards BP <-> Customer.

BAdI: Data Assignment of Form of Address from Customer/Vendor to BP.

BAdI: Defaults for Creating Data from BP to Customer/Vendor.

If a customer has no title, the business partner is created with category Organization. The delivered CVI_MAP_BP_CATEGORY implementation returns this title value. A new implementation of BAdI CVI_MAP_TITLE ( Data Assignment of Form of Address from Customer/Vendor to BP ) with name /DBM/CU_CVI_MAP_BP_CATEGORY has been created which should be switched on in Customizing using the Active(IMG) flag. Select BAdI: Data Assignment of Form of Address from Customer/Vendor to BP.


10.1.10 Synchronize Contact Person between Business Partner and Customer Procedure

1. In Customizing for Cross-Application Components , navigate to Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Customer Integration → Field Assignment for Customer Integration → Assign Attributes → Contact Person → Activate Assignment of Contact Persons .

2. Set the Cntct Person Active flag.

This setting is needed to automatically create KNVK entries when a contact person relationship is created for a business partner.


10.1.11 Maintain Collective Billing Field in the BP Transaction Procedure

The following BAdI does not have to be implemented. The structures CMDS_EI_SALES_DATA and CMDS_EI_SALES_DATAX were enhanced with DBM specific fields. (see append structure /DBM/CMDS_EI_SALES_DATA_A and /DBM/CMDS_EI_SALES_DATAX_A). These structures are used in CMDS_EI_EXTERN. The fields are maintained in the PBO and PAI function modules of the view DBM060.

We do not fill the DATAX, but if you create the business partner with BAPI, the DATAX append is a prerequisite.

In Customizing for Cross-Application Components , navigate to Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Business Add-Ins (BAdIs).

Set BAdI CVI_MAP_BUSINESS_ADDRESS implementation active.

In the BUPT, nothing was set for the business partner relationships. The KNVK entries are generated only for the relationship category ‘BUR001’. It is hard coded in the source code. This is why DBM does not use new relationship categories or relationship types.


10.2 Synchronization Cockpit Procedure

After you complete the configuration steps above, you can start the synchronization cockpit.

In the test phase, set the PPO.

In the productive phase do NOT set the PPO

1. Start the MDS for the customer.

2. This step is for the MDS for the vendor problem (job terminates if the vendor is equal to the customer). The PPO is set, so there is no dump. If you encounter this error, you can connect the business partners and vendors with transaction LBPC2.

Business partners should now be created for all existing SD customers, depending on the selection criteria in the cockpit.


10.3 Upgrade Report Procedure

After you complete the synchronization process, start the report /DBM/UPDATE_BUPA to fill the /DBM/VBPA-PARTNER field for the existing DBM orders. This report does not lock any DBM orders. We therefore recommend that you only run the report when the system is locked for users.

Add transaction /DBM/BP_CM to the relevant customizing table

It is necessary to be able to start the /DBM/BP_CM transaction from within the notification transaction.

1. To add the transaction, see Customizing for Cross-Application Components -> SAP Business Partner -> Business Partner -> Basic Settings -> Business Partner Roles -> Define Application Transactions.

2. Enter the /DBM/BP_CM transaction code and a description.


10.4 Quick Creation of Business Partner Procedure

When you use transaction BP to create a business partner, you must enter various customer data. In most cases, the sales data is the same for all business partners. You can use the Quick Creation (QC) process to easily create business partners. In order to create a BP using the QC process, reference business partners must be created to get the sales data for the newly created business partners.

The QC process can be used in several transactions in DBM (for example DBM Order, Vehicle Assignment) to create BP with different roles.

Customer Role / Organizational Data

The customer role can be different depending on the caller transaction. The customer roles are maintained through the BAdI /DBM/CU_BP_QUICK_ROLES. The organizational data area depends on the selected customer role.

Reference Business Partners

Reference business partners (or reference customers) are used to supply sales data for the newly created business partner. It is very important to set the reference business partner’s sales and company data correctly otherwise orders could not be invoiced for the business partners that have been created by using the Quick Creation process. You can only create orders for the business partners that have FI Customer role. If the business partner does not have this role then in the billing process, the system creates the role. The system will try to create this role using the reference business partner’s company code. If no company code is maintained for the reference business partner, then the FI customer role cannot be created for the order’s business partner either.

If you use the quick creation process to create a vendor, then the Vendor and FI Vendor roles, and the purchasing view must be created for billing.

Criteria Tables

Criteria tables are used to determine the reference customer, depending on the selected or maintained data on the Quick Creation screen. You can create several criteria tables, and customize the access control. In each of the criteria tables, you can define several criteria fields.

One master criteria table /DBM/C_CU_BP_001 is delivered in delivery customizing. The criteria fields are Sales Organization (VKORG), Distribution Channel (VTWEG) and Division (SPART).

Further criteria tables can be created in the customer namespace.

In Customizing for Logistics Execution , navigate to Dealer Business Management → Customer Data Management → Business Partner → Define Table of Criteria

You must define fields for all criteria tables.

Criteria Access Sequence

In Customizing for Logistics Execution , navigate to Dealer Business Management → Customer Data Management → Business Partner → Define Access Sequence .

When you use the Quick Creation process to create a business partner, the system looks up the criteria tables in the order that is defined in the criteria access sequence Customizing.


Define Reference Business Partners

In order to have reference business partners, one or more business partners must be created using transaction BP. The sales and distribution data that is maintained for the reference business partner is copied for the business partner.

Condition Processing

You maintain the records in the criteria table by using transaction /DBM/CU_BP_COND. You can insert several combinations of criteria fields with the reference business partner. In the Quick Creation process, the system looks up these tables in the order of the customized sequence and if the data that entered by the user in the Quick Creation popup is found in the criteria table, then the system uses the relevant reference business partner.


Sales Organization Distribution Channel Division Cust.No.

0001 01 01 REF_PER_C

0001 Q3 01 REF_PER_C

0001 Q4 01 REF_PER_C

In the example above, if the user selects 0001 for Sales organization 01 for distribution channel and 01 for division, then the system selects the partner REF_PER_C as the reference business partner.


11 Accounting (Financials, Controlling) See SAP Note 930634.

We strongly recommend that you consult an SAP CO/FI expert if setting up the DBM FI/CO configuration. The configurations steps described in this chapter are example process configuration, and can differ from customer to customer.

SAP fills the field ZUONR with the DBM order and split number in SD and Accounting.


11.1 Processing the Controlling Area Use

You can use this procedure to edit the settings for the controlling area for each fiscal year. The system requires a version 0 for the current fiscal year.

Procedure

1. In Customizing for Controlling , choose General Controlling Organization

Maintain Versions.

2. In the Controlling area choose Settings Settings for Each Fiscal Year

3. Create a version 0 for the current fiscal year in the same way as for the existing entries.


11.2 Chart of Accounts Use

You can use this procedure to edit the settings for the chart of accounts. The chart of accounts is a classification scheme consisting of a group of general ledger (G/L) accounts. For each G/L account, the chart of accounts contains the account number, the account name, and technical information.

Within the chart of accounts, revenue and cost accounts are created and maintained. The example chart of accounts delivered with the SAP System is INT. The following guidelines are based on the example chart of accounts INT.

Procedure

For further information, refer to the standard SAP ERP documentation.


11.3 Creating Accounts Use

G/L account master records contain the data that is always needed by the general ledger to determine the account's function. The G/L account master records control the posting of accounting transactions to G/L accounts and the processing of the posting data. G/L accounts represent revenues and costs.

Each created new account needs to be assigned to a chart of accounts.

Procedure

For further information, refer to the standard SAP ERP documentation.


11.4 Creating Cost Elements Use

You create primary cost elements to transport costs and revenues to Controlling.

Primary cost elements need a corresponding G/L account. G/L accounts representing revenues need to have a cost element with cost element category 11. G/L accounts representing costs need to have the Cost Elements with Cost Element Category 1. All G/L accounts needed for Controlling must have a corresponding primary cost element.

Secondary cost elements do not have a corresponding G/L account, and exist only in Controlling.

Procedure

Before creating Cost Elements, see SAP Note 1003330.

1. On the SAP Easy Access screen, choose Accounting Controlling Cost Center

Accounting Master Data Cost Element Individual Processing Create Primary

.

2. Create the primary cost elements 800000 with cost element category 11 and 410000, 980000, 980001, 999000, 999100, 999001, 999101 with cost element category 1 (if not already available in chart of account INT, if using an own chart of account the accounts might have a different number).

3. On the SAP Easy Access screen, choose Accounting Controlling Cost Center

Accounting Master Data Cost Element Individual Processing Create

Secondary .

4. Create the secondary cost element 640100 with cost element category 43 for activity allocation (if not already available).


11.5 Copying the Cost Element Group Use

Cost element group DBM_DB is a DBM template and delivered in client 000. It is used to structure all cost elements posted to the DBM internal order in the reporting cost analysis. You can copy the structure to the current client, where you can integrate your own cost elements. Use this structure to collect all relevant cost elements for DBM for easier further cost analysis in the DBM order. For more information, see Defining Reports in the Information System .

Procedure

1. 1On the SAP Easy Access screen, choose Accounting Controlling Cost

Element Accounting Master Data Cost Element Group Change.

2. Choose Extras Copy from Client .


11.6 Creating a Profit Center Use

If you want to use profit center accounting, you must create profit centers. You always need a dummy profit center. We recommend creating a profit center for every workshop or for every original equipment manufacturer (OEM) or any other dependency for assigning profit centers. Profit centers are automatically assigned to DBM internal orders by means of the criteria technique described in the chapter Defining Profit Center Control .

Procedure 1. In Customizing for Controlling, choose Profit Center Accounting Master Data Profit

Center Create Dummy Profit Center .

2. Create a Dummy Profit Center. For example, SAP-DUMMY.

3. In Customizing for Controlling choose Profit Center Accounting Master Data Profit

Center Define Profit Center.

4. In the field Profit Center enter for example, WORKSHOP.


11.7 Creating Cost Centers Use

You use this procedure to create a cost center for the activity allocation posting from the cost center to the DBM internal order.

Procedure

1. On the SAP Easy Access screen , choose Accounting Controlling Cost Center

Accounting Master Data Cost Center Individual Processing Create.

2. Create a cost center, for example Workshop .


11.8 Creating and Assigning an Activity Type and a Price Procedure

1. In the standard system, create an activity type (assignment of an allocation cost element, that is, a secondary cost element) and maintain the activity price for a specific cost center.

The labor values are posted from the cost center performing the activity to the DBM order on the basis of this activity type and price. The activity type and the providing cost center are stored in Customizing for Dealer Business Management (DBM).

2. Create version 0 for the current fiscal year. See Processing the Controlling Area.

You must define a plan price for the newly-created activity type and appropriate cost center.

3. In Customizing for Controlling , choose Cost Center Accounting → Master Data → Activity Types → Create Activity Types (for example, MONT).

4. Edit the master data for the activity type on the tab page Basic Data as follows:

In the field ATyp category (activity type category), enter the value1(manual entry, manual allocation).

In the field Allocation cost elem, choose the appropriate allocation cost element by using the F4 help.

In the field Activity Unit , enter H for hours.

In the field CCtr categories , enter*(all cost center types).

5. On the SAP Easy Access screen, choose Accounting → Controlling → Cost Center Accounting → Planning → Activity Output/Prices → Change.

6. Enter then save the following data for the price:

Period

Fiscal Year

Activity Type

Cost Center


11.9 Defining Number Ranges for Internal Order Types Use

The internal orders assigned to the number ranges (delivered as standard) are already copied by DBM Customizing, which is part of the DBM 7.00 object list.

To display more customer-specific data in the internal order, see SAP Note 1074411.

Procedure

1. In Customizing for Controlling , choose Internal Orders Order Master Data

Maintain Number Ranges for Orders .

2. On the first level of a DBM order, check the number range assignment for the header order type Q100 DBM – Order (1 st level) (internal number assignment).

3. On the second level of a DBM order, check the number range assignment for the following bill-to parties order types:

Q200 – DBM – Vehicle (internal number assignment)

Q210 – DBM – External Billing (2 nd level) (internal number assignment)

Q220 – DBM – Internal Billing (2 nd level) (internal number assignment)

Q230 – DBM – Collective Int. Ord. (2 nd level) (external number assignment)

Q240 DBM – Release Order (2 nd level)

Q250 DBM – Multi Branch Service (2 nd level)

Q700 DBM – Multi Branch Service (0 level)


11.10 Create Account Assignment Groups for Internal Business Partners Use

If working with internal service processes with or without suborder it is necessary to create different account assignments groups for the involved business partner.

Procedure

1. In Customizing, choose Sales and Distribution → Basic Functions → Account Assignment/Costing → Revenue Account Determination → Check Master Data Relevant For Account Assignment .

2. Select Customers: Account Assignment Groups.

3. Enter Account Assignment Group:

I0 Internal Revenue

I1 Int Sub Order Rev


11.11 Assign Account Assignment Group to Business Partner Use

You assign the account assignment group to the customer within the customer master data record.

Procedure

1. On the SAP Easy Access screen choose Logistics Logistics Execution Master

Data Partner Customer Display Total

2. To configure the Account Assignments Group for the customer open DBM Sales Area under the tab Billing Document

3. Assign Account Assignment Group I0 to an internal customer using the internal service order process (for example 4000) and assign I1 to the internal customer used for the suborder processes (for example 7000) process. External customers do not have an assigned account assignment group.


11.12 Assign Account Assignment Group to Material Use

To be able to bill materials and labor with a service order, it is necessary to assign the account assignment group to the affected materials. This configuration step is necessary for all materials in the service order billing process.

Procedure

On the SAP Easy Access screen choose Logistics Materials Management Material

Master Material Change Immediately.

Two possibilities are now available to configure the Account Assignment:

1. Take the price material of the labor values, and enter the material master data in the Sales: sales org. 2 tab. In the Account Assignment Group field, enter 02 Performances.

2. For all parts used in the DBM order processes, maintain the material master data in the Sales: sales org. 2 tab, and in the Account Assignment Group field, enter 01 Trading Goods.


11.13 Revenue Account Determination Use

To find the revenue accounts if billing a DBM order the revenue account determination needs to be maintained.

Procedure

1. In Customizing, navigate to Sales and Distribution → Basic Functions → Account Assignment/Costing → Revenue Account Determination → Assign G/L Accounts.

2. Select the condition table Cust.Grp/MaterialGrp/Acctkey.

3. Copy the entries below in condition table C001 for the revenue account determination. If you use a different chart of accounts, sales organization, account assignment groups (AGG), or cost elements, you must take this into account for the entries below.

V KOFI INT 0001 I0 01 ERL 980000

V KOFI INT 0001 I0 02 ERL 980001

V KOFI INT 0001 I1 01 ERL 999000 999100

V KOFI INT 0001 I1 01 ERS 999100 999000

V KOFI INT 0001 I1 02 ERL 999001 999101

V KOFI INT 0001 I1 02 ERS 999101 999001


11.14 Processing and Activating the Results Area Use

With this procedure, you process and activate the interfaces for Profitability Analysis (CO-PA) and for the controlling areas assigned to your operating concern.

Procedure

1. In Customizing for Controlling , choose Profitability Analysis Structures Define

Operating Concern Maintain Operating Concern.

2. Generate the cross-client and client-specific part for operating concern S001 on the tab page Environment . In most cases you will create your own operating concern with your own characteristics and value fields.

3. In Customizing for Controlling , choose Profitability Analysis Flows of Actual

Values Activate Profitability Analysis to activate the interfaces for CO-PA.


11.15 Assigning SD Condition Types to Value Fields Use

You can use this procedure to assign value fields to Profitability Analysis .

Procedure

1. In Customizing for Controlling under Profitability Analysis Flows of Actual Values

Transfer of Incoming Sales Orders Assign Value Fields.

2. Choose Maintain Assignment of SD Conditions to CO-PA Value Fields.

3. Make the following entries for the operating concern S0001:

Condition Type (CTyp)

Value field (Val. fld )

Transfer Condition Values with +/- Signs to CO-PA (Transfer +/-)

QPR A ERLO S

QPR T ERLO S X

QSB P ERLO S X

QSM L ERLO S

The CO-PA cookbook document provides further information about how to transfer vehicle data to value fields.


11.16 Defining Account Assignment for Cost Posting in Order Use

You define for each plant which activity type is used for activity allocation from the workshop cost center to the internal order of the DBM order. You also define which cost center is credited during this process. You can restrict the selection by specifying the material group as well as the plant. The material group must be defined in the material that is used for the labor value items in the service order. In most cases the cost center will depend on the plant and the activity type on the material group.

Procedure

1. In Customizing for Logistics Execution , choose Dealer Business Management (DBM)

Order Account Assignment Define Account Assignment for Cost Postings in Orders.


Plant

Material group (labor value = 90)

Cost element (no information is required for this field)

Activity type

Cost center

Example

Plant Material group Cost element Activity type Cost center

0001 90 MONT WORKSHOP


11.17 Defining Internal Order Type for Bill-To Party Use

If the system is customized to create separate internal order for each bill-to party during invoicing, do not set the Collective Internal Order indicator in the Customizing settings for the DBM order type. At the time of invoicing, the system posts the revenue and costs to these bill-to parties according to the split values. For more information, see Controlling Collective Orders.

Procedure

1. In Customizing for Logistics Execution, choose Dealer Business Management (DBM)

Order Account Assignment Internal Order for Bill-To Party Define Internal Order Type for Bill-To Party.


Controlling area

DBM order type

Account assignment category (use only in case of internal DBM order processes)

Internal order type (Q210/Q220/Q240/Q250)

Internal billing document (flag can be set in internal DBM orders to let the system post internal revenues)

Example

Controlling Area

DBM Order Type

Account Assignment Category

Internal Order Type

Internal Billing Document

0001 2000 Q210

0001 2003 25 Q240

0001 2103 25 Q240

0001 4000 01 Q220

0001 4000 02 Q220 X

0001 4000 10 Q220

0001 4000 11 Q220

0001 4100 10 Q220

0001 4100 11 Q220

0001 7000 70 Q250 X


11.18 Defining Parameters for Settlement Rule Use

With billing, the DBM order settlement rules are created for the internal order for bill-to parties, which you can settle to CO-PA. For more information, see SAP Note 944375.

Procedure

1. In Customizing for Logistics Execution , choose Dealer Business Management (DBM)

Order Account Assignment Internal Order for Bill-To Party Define Parameters for Settlement Rule.


DBM order type

Operating concern

Characteristic (defined for your operating concern)

Source structure

Source assignment

Field from DBM order (if necessary, you can append your own characteristics to the communication structure /DBM/CO_IO_COM)

Example

DBM Order Type

Operating Concern

Characteristic Source Structure

Source Assignment

DBM Order

2000 S001 KNDNR Q1 1 KUNNR


2000 S001 VTWEG Q1 1 VTWEG


2003 S001 KNDNR Q1 1 KNDNR












11.19 Collective Order Control Use

To model dealer processes, additional objects were developed on the basis of ERP. One of these key /DBM/objects is the DBM order. A display transaction has been developed for the following orders:

Service order

Vehicle order

Parts order

An internal order on the first level acts as a cost collector in the background. That is, the users do not have to manage and track these costs themselves. The DBM order and the internal order are linked. When the invoice is created, all cost and revenue collected on this level is reposted to the second level and here the balance will be 0.

In the DBM order split, the system divides the postings between several bill-to parties. When an invoice is created in the background for every bill-to party and, depending on the Customizing settings, an additional internal order is created. This means that an internal order also exists for every bill-to party. When invoicing takes place, the system posts the revenues and costs to these bill-to party internal orders according to the split values. If you wish, you can use Customizing settings in the DBM order to determine that a separate internal order is not created for each bill-to party, but rather the costs and revenue are posted to the appropriate collective internal orders according to the Customizing settings, for example, in accordance with the business transaction (by means of order control).

If you set the Collective Internal Order indicator in the DBM order type, the system posts the costs and revenue to a collective order when invoicing takes place and the costs and revenue can then be forwarded to and settled using Profitability Analysis (CO-PA). The collective order that is debited with the costs is determined by the criteria listed below:

Define Criteria Table

This entry is provided by delivery customizing. You can use the existing criteria table.

Check Access Sequences

This entry is provided by delivery customizing. You can use the existing access sequences.

Assign Internal Order

Procedure

1. On the SAP Easy Access screen, choose Accounting Controlling Internal

Orders Master Data Special Functions Order Create .

2. In the Order Type field, enter Q230 .

3. You can now maintain the Order fields, for example DBM_COLLECT .


(DBM) Order Account Assignment Internal Order for Bill-To Party Collective

Internal Order Control Define Table of Criteria .

5. Ensure you can use the standard criteria in the table below.




Internal Order Control Define Access Sequences .

7. Ensure you can use the standard access sequences.



Internal Order Control Assign Internal Order .

9. Assign the internal order with the following entries:

o Controlling area

o DBM order type

o Account assignment category (ACC); (optional)

o Warranty category (optional)

o Internal order that was created manually before (use order type Q230)

Example

Controlling Area

DBM Order Type

Account Assignment Category

Warranty Category

Order

0001 2000 DBM_COLLECT


11.20 Defining Internal Order Account Assignment Use

You define account assignment categories like new vehicle, used vehicle, scrap and so on, which are available in internal service orders (4000) or internal service orders with revaluation (4100). For each account assignment category, you can define which account assignment object is debited, for example, internal order or cost center. The account assignment category, which is found in the internal service orders, is determined with the following criteria technique:

Define Table of Criteria

This entry is provided by delivery customizing. You can use the existing criteria table.


This entry is provided by delivery customizing. You can use the existing access sequences.

Assign Account Assignment Object for Internal Order

Procedure


(DBM) Order Account Assignment Internal Order Account Assignment Define

Account Assignment Categories for Internal Order . Ensure you can use the standard account assignment categories provided by delivery customizing.



Table of Criteria .

Ensure you can use the standard criteria table provided by delivery customizing.



Access Sequences .

Ensure you can use the standard access sequences provided by delivery customizing.


(DBM) Order Account Assignment Internal Order Account Assignment Assign

Account Assignment Object for Internal Order .

5. Assign the account assignment category with the following entries:

o Controlling area

o Sales organization

o Plant

o DBM internal order types

o Account assignment category


o Number

o Changeable

o Cost Center

o Cost Element

o Internal Order

o Bill-to party

o Function module (/DBM/CO_ INT _ GET _VEHICLE is delivered to determine the vehicle internal order)


Example

CO Area

SOrg Plant Order Type

AAC No. Chg. Cost Ctr. Cost El.

Int. Order

Bill-To Party

Function Module

0001 0001 0001 2003 25 1 X Cust with AAG I0

0001 0001 0001 2103 25 1 X Cust with AAG I0

0001 0001 0001 4000 01 1 X Workshop Cust with AAG I0

0001 0001 0001 4000 02 1 Workshop 600200 Cust with AAG I0

0001 0001 0001 4000 10 X Cust with AAG I0

/DBM/CO_ INT _ GET _VEHICLE

0001 0001 0001 4000 11 Cust with AAG I0


0001 0001 0001 4100 01 X Workshop Cust with AAG I0

0001 0001 0001 4100 02 Workshop 600200 Cust with AAG I0

0001 0001 0001 4100 10 X Cust with AAG I0


0001 0001 0001 4100 11 Cust with AAG I0


0001 0001 0001 4100 10 1 Cust /DBM/CO


with AAG I0

_ INT _ GET _VEHICLE

0001 0001 0001 4100 11 1 X Cust with AAG I0


0001 0001 0001 4101 10 1 Cust with AAG I0


0001 0001 0001 4101 11 1 X Cust with AAG I0


0001 0001 0001 7000 70 1 X Cust with AAG I1

/DBM/CO_ INT _ GET _HEADER_INTORD


11.21 Internal Order Account Revaluation Use

You define a link between a DBM order type for revaluation and a CO production order type, which automatically posts the revaluation of a new or used vehicle to the vehicle stock.

Procedure


(DBM) Order Account Assignment Internal Order Revaluation Define Order

Type for Revaluation .

2. Assign the order type with the following entries:

o DBM order type

o CO production order type

o Cost element (used for primary cost reposting from vehicle order to CO production order)

o Movement type (used for taking the vehicle from stock into the CO production order)

o Movement type (used for delivery of CO production order into stock)

Example

DBM Order Type

CO Production Order

Cost Element Movement Type

Movement Type

4100 CP01 use your own cost element

261 101

4101 CP01 use your own cost element

261 101

You cannot post revenue in the CP01 CO Production Order. Therefore, do not specify a revenue type cost element.


11.22 Release Production Order Immediately Use

This setting is necessary to release the CO production order for the revaluation process immediately after creation.

Procedure

1. In Customizing for Controlling, navigate to → Product Cost Controlling → Cost Object Controlling → Product Cost by Order → Manufacturing Orders → Check Order Types

2. Double click the order type CP01 to view the detailed production order setting overview.

3. Check value Release Immediately.


11.23 Automatic Postings Use

To post FI and CO relevant goods issue postings automatically, in case of a material consumption, the following configuration is necessary.

Procedure

1. In Customizing for Materials Management , navigate to Valuation and Account Assignment → Account Determination → Account Determination without Wizard → Configure Automatic Postings.

2. Select Account Assignment

3. Select the GBB entry and choose INT in the popup for the chart of account using INT (or the one using in the project)

4. Add or configure the accounts for the automatic posting and for the corresponding valuation class (3100)

5. Enter the following configuration:

o 0001 AUF 3100 895000 895000


11.24 Defining Default Values for Cost Object Controlling

This setting is necessary to define default values for CO production orders without quantity structure for each plant and order type.

Procedure

1. In Customizing for Production, choose Repetitive Manufacturing Cost Object

Controlling Define Default Values for Cost Object Controlling

2. Check if all your plants are defined for order type CP01.


11.25 Defining Valuation of Goods Received

This setting is necessary to define how receipts are evaluated for materials with moving average price control.

Procedure

1. In Customizing for Production, choose Shop Floor Control Integration Define

Valuation of Goods Received .

2. Check if all your plants are defined.


11.26 Defining Profit Center Control Use

You define how the profit center is determined with the lean condition technique. If the system creates an internal order on the first level or on the second level (bill-to party), data for the profit center is pre-populated. You only require these settings if you wish to use Profit Center Accounting .

Define Table of Criteria

You can use the existing criteria table.


You can use the existing access sequences.

Assign Profit Center

Procedure


(DBM) Order Account Assignment Profit Center Control Define Table of

Criteria .

2. Ensure you can use the standard criteria table.


(DBM) Order Account Assignment Profit Center Control Define Access

Sequences .

4. Ensure you can use the standard access sequences.


(DBM) Order Account Assignment Profit Center Control Assign Profit Center

.

6. Assign the profit center with the following entries:

o Plant

o Distribution channel

o Division

o DBM order reason

o Material group

o Profit center

Example

Plant Distr. Chnl Div. Ord. Reason Mat. Group Profit Ctr

0001 Q3 01 01 Workshop


11.27 Defining Reports in the Information System Use

You define your own report for cost analysis if you decide not to use the standard DBM

template. To display the report, choose Goto Cost Analysis .

For more information on defining your own report, see Define Report Parameters for Cost Analysis in the Customizing activity documentation as well as the SAP Notes 871601 and 932551 .

Procedure

In Customizing for Dealer Business Management (DBM), see Order Basic Functions

Account Assignment Cost Analysis Define Report Parameters for Cost Analysis .


11.28 Field Control Movement Type 261 Account 410000 Procedure

1. In Customizing for Materials Management , choose Inventory Management and

Physical Inventory Settings for Enjoy Transactions Settings for Goods Movements

(MIGO) Field Selection per Mvt Type.

2. Set the movement type 261 , field GSBER to Optional entry.


11.29 Defining Document Type for Customer Advance Payment (Deposits) You define the document type to be used for customer advance payments (deposits) in DBM.

Procedure

1. In Customizing for Financial Accounting (New), choose Financial Accounting

Global Settings (New) Document Document Types Define Document Types for

Entry View .

2. Copy the entry DZ to ZD (for example).


(DBM) Order Basic Functions Account Assignment Specify Document Type for

Customer Advance Payment .

4. Enter the created entry ZD in the Document Type field.


(DBM) Cash Desk Define Business Transaction .

6. Choose New Entries and create a new cash desk business transaction (CD BT) with the following data:

o CD BT: 99, for example

o Description: Customer Advance Payment


(DBM) Cash Desk Define Document Type .

8. Choose New Entries and create a new cash document category (CD Cat.) with the following data:

o CD Cat.: EZ

o Document Type for Accounting Interface (AI Doc. Ty.): ZD

o Number Range (No): 01

o Subledger Account Posting Key (PK): 15

o Description: Customer Advance Payment


(DBM) Cash Desk Define Cash Desk Work Center .

10. Select the cash desk work center that is allowed to work with customer advance payments and then double-click on Business Transaction.

11. Choose New Entries and enter the following data:

o Cash Doc. Cat.: EZ

o Cash Desk BT: 99

o G/L Account: 10000


11.30 Defining External Service Procedure

For more information, see SAP Note 1040943.


11.31 Setting Up Profitability Analysis (CO-PA) Procedure

See SAP Note 2092713 and the cookbook attached to it.

We strongly recommend that you consult an SAP CO-PA expert for setting up CO-PA.

For the Profitability Analysis (CO-PA), you can define the data sources and parameters for profitability segment for the three processes - vehicle sales, vehicle service, and parts sales - in Customizing for Dealer Business Management. Apart from transferring data from the DBM order header and split header to the CO-PA, it is also possible to transfer data from the following data sources:

Relevant business partner data (such as general BP data or address) from the DBM order

DBM/Vehicle Management System (VMS) vehicle data

Vehicle object data (such as vehicle model details, vehicle partner, or vehicle registration details)

You can enhance the list of data sources using any other SAP tables or customer-specific tables. The SAP Note mentioned above provides more details.

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


12 Parts


12.1 Creating Spare Parts Use

The DBM material is based on the standard system. Dealer Business Management (DBM ) has the following differences and enhancements to the standard system:

Additional DBM data (generic data)

o Part to be returned

(returned to manufacturer for further technical development)

o Part that has to be kept (legal requirement)

o Part that has to be disposed of (legal requirement)

o Check multiple entry

Simplified user interface

o Default views

o Aggregated display

You can process parts using the following transactions:

Transaction Description

/DBM/MM01 Create material – DBM

/DBM/MM02 Change material – DBM

/DBM/MM03 Display material – DBM

/DBM/MMXX Create material from the original parts master.

It is not necessary to maintain all the parts from a manufacturer (all models, model ranges, years of manufacture) in the system for productive operation. This number would be multiplied further for dealers that handle several brands. The dealer works with just a subset of the entire parts range to handle parts sales and service. These parts are also fully maintained in the SAP system.

Table /DBM/OMARA contains all of the parts supplied by the manufacturer. The search help function can be used to find entries in this table. A complete master record is created in the SAP system if necessary.

MM01 Create material (SAP standard)

MM02 Change material (SAP standard)

MM03 Display material (SAP standard)

MM06 Flag for deletion (SAP standard)

You can add manufacturer-specific fields according to the enhancement concept.


The following information for DBM material data within a parts master is important and should be maintained for DBM order follow up processes ( for example, procurement and SD billing documents).

Field Data Description

Material Type HAWA Trading goods

Properties copied from HAWA

Industry Sector M

Material Group Customer and brand-specific settings possible

General Item Category Group

NORM Normal SAP standard item

Checking Group for Availability Check

Customer-specific setting

Procurement type F External:

supplied by manufacturer

Materials planning (MRP)

Customer-specific settings for manufacturer parts (MRP is manufacturer-specific)

For inventory-managed materials from other vendors, such as tires (for example, summer and winter tires) and accessories, you can use SAP MRP and materials planning functions

Tax classification Customer-specific setting (see SAP Note 109005 for tax levied on used parts)

Transportation group

Loading group

0001 Delivery functions are not currently integrated into the DBM order,

Since transport and loading groups are required fields in the material type HAWA, you either have to define them with default values or set the field control for these fields in Customizing appropriately.

If you created your own value for general item category or transportation group you can also use those values when creating or updating a parts master record.

For DBM material masters, you have to set the screen sequence to A1 .

Procedure

1. In Customizing for Logistics – General choose Material Master Configuring the

Material Master Assign Screen Sequences to User/Material

Type/Transaction/Industry Sector .

2. Set the screen sequence to A1 .


12.2 Creating a Sales Price for Spare Parts Procedure



2. Enter QPRT in the field Condition Type and enter the required data.


12.3 Search Help for Spare Parts Use

Only spare parts are meaningful in the search result for materials in the order. The high number of dummy materials, for example, for vehicle models, labor values (LVs), vehicle features, and so on, can thus be filtered out. The filter is based on the material group.

Prerequisites

The material group has been created and saved in the system.

Procedure

In Customizing for Logistics Execution , choose Dealer Business Management (DBM)

Part Assign Material Type for Spare Part.


12.4 Exchange Parts


12.4.1 Setting Up Customizing

To use the exchange part process, you have to activate BC Set /DBM/DBM800_EXP. This BC

Set contains the following necessary Customizing settings:

Technical item category

Item copy control

Procedure

Activate BC Set /DBM/DBM800_EXP by using transaction SCPR20.


12.4.2 Setting Up the Material Master

You can set up spare parts as used parts or exchange parts for the exchange part process in the material master.

Procedure

1. Start transaction /DBM/MMXX.

2. Make an entry in the Type of Part field and the Used Part field.

More Information

SAP Library for Dealer Business Management on SAP Help Portal at http://help.sap.com

SAP for Industries SAP for Automotive Dealer Business Management <release>,

<language> Parts Management Order Processing Exchange Parts .

http://help.sap.com/


12.4.3 Restricting Material Group for Material Search

You can restrict the materials for the used parts search help in the DBM order.

Procedure


(DBM) Part Assign Valid Material Group for Material Search .

2. Assign the relevant material group to the used part item categories.

3. Make the settings in the material master of the used parts (transaction /DBM/MMXX).


12.4.4 Assignment of SD Conditions to Value Fields

In case you are using rebates in the DBM order, for example, if a fixed rebate (SKTO) is assigned to the payment terms of the corresponding customer, it is necessary to select the Transfer +/- checkbox of the corresponding pricing condition type.

Procedure

1. Call transaction KE4I.

2. Select the Transfer +/- checkbox for the condition, which is used for rebate.


13 Service


13.1 Defining a Labor Value Catalog Procedure


(DBM) Service Labor Value Define Labor Value Catalog .


o ID for labor value catalog

o Text for the labor value catalog

o Multiple selection for labor values

o Suggested setting: set the indicator. If you want to add multiple labor value catalog to the same OEM, set the same parameters for each catalog.

o Wildcard for labor values

Suggested setting: set the field to 1 . If you want to add multiple labor value catalogs to the same OEM, the settings must be the same for each catalog.


13.2 Defining a Hierarchy Level Procedure


(DBM) Service Labor Value Define Hierarchy Level .

2. Define the hierarchy level. If you want to add multiple labor value catalogs to the same OEM, the settings must have the same hierarchy levels.


13.3 Determining a Catalog

You specify an access sequence for each criterion. By doing so, you stipulate which fields the SAP system checks when it searches for a valid labor value catalog.

Procedure


(DBM) Service Labor Value Catalog Determination Assign criteria .

2. Assign the criteria.

If you want to add multiple labor value catalogs to the same OEM, we recommend that you enter the sequence number with different values.


13.4 Creating a Labor Value Group Procedure

1. On the SAP Easy Access screen choose Logistics Logistics Execution Dealer

Business Management Master Data Labor Value Edit Labor Value Group.

2. Define values for the labor value group.

Example

01 Mechanics

02 Electricity

03 Painting


13.5 Creating a Dummy Material for Labor Value

You must assign a dummy material to each labor value for processing in the SAP system.

Procedure


Business Management Master Data Part Create Material - DBM .


Field Data Description

Material Type DIEN Service

Industry Sector M Mechanical engineering

Material Group Default value 90

Define your own material groups for labor values, such as dummy material for mechanics, electrics and electronics.

Base Unit of Measurement

Default value: min

You must define an “industry minute”, that is, the base unit of measurement used to calculate the time required to perform service tasks (manufacturer-specific)

General Item Category Group

LEIS From the material type


13.6 Creating Labor Values Use

Manufacturers create catalogs (for example, labor value catalog and local OEM system) for work performed on the vehicle. The labor values (LVs) consist of a description and a predefined time.

The labor value is used in the service order. A separate item category and search help is provided for LVs.

Prerequisites

In Customizing for Dealer Business Management (DBM), define the following data:

Labor value catalog

ID for the labor value catalog

Hierarchy level

Manufacturer-specific, mostly one- or two-level

Catalog determination

Determination uses the following criteria technique:

o Definition of the criteria table and access sequence

o Assignment of criteria

o Example 1: manufacturer 1 finds catalog 1; manufacturer 2 finds catalog 2

o Example 2: manufacturer 1 + country DE finds catalog 1, manufacturer 1 + country AT finds catalog 5

Procedure


Business Management Master Data Labor Value Edit Labor Value Group .

2. Enter the group description for the appropriate labor value catalog and the hierarchy level.


Business Management Master Data Labor Value Edit Labor Value .

4. Assign the labor value main type.

5. By doing this, you create the link to the vehicle (no check table, manufacturer-specific).

6. Assign the labor value group.

7. If you set the indicator for multiple entry, the system displays a message if the labor value is entered more than once in the service order. This is useful, for example, with the labor value for installing and de-installing the motor since a vehicle usually only has one motor.

8. Enter a predefined time for the labor value (dependent on labor value main type) and a sales price.


9. Assign the dummy material.

10. You must do this for integration with ERP. The system creates a sales order on the basis of the DBM order.


13.7 Creating a Sales Price for Labor Values Use

The sales price is defined via the reference material (allocation material) and the appropriate condition.

Procedure



2. Enter the sales price for condition type QPRA (sales price) and QPSA (costs).


13.8 Defining a Service Package Use

A service package can consist of different items; for example, n labor values, n parts, and n texts. The manufacturer usually supplies this information in the form of a catalog (local OEM system). However, the dealer can also create its own packages.

The package master is a DBM object.

Procedure


(DBM) Service Package Define Number Range for DBM Package .

2. Define number ranges for package types.


(DBM) Service Package Define Package Variant Type.

4. Define variant selection field for variant type.


(DBM) Service Package Define Material Type for Parts Package .

6. Enter the material types.


(DBM) Service Package Generate Selection Options for Customer Fields .

8. Generate selection options for customer fields.


Business Management Master Data Package Edit Package .

10. Save the following data for the package:

o Package type

o Package category

o Model key

o Versions

o Package variant


13.9 Creating Customer Advisers Use

In the personnel mini-master, you create the customer advisers for the following areas:

Service

Parts

Vehicle

We recommend that you create your own action for the personnel mini-master.

Procedure

1. On the SAP Easy Access screen, choose Human Resources Personnel

Management Administration HR Master Data Personnel Actions .

2. Set the following:

o Set Action Type, for example, Hiring

Start is the first of the month

o EE (Employee) Group 1

o EE subgroup, for example DU (Salaried Employees)

o Infotype Organizational Assignment

Set the indicator to No Assignment

o Infotypes

Skip planned working time , basic pay , bank details , and absence quotas


13.10 Appointment Scheduling


13.10.1 Defining a Job Catalog Procedure


(DBM) Service Workshop Scheduling Job Catalog Define Job Catalog .


o An ID for the job catalog (in the Labor Value Catalog ID field)

o A description for the job catalog

o A wildcard


13.10.2 Defining a Hierarchy Level Procedure


(DBM) Service Workshop Scheduling Job Catalog Define Hierarchy Level .

2. Define the hierarchy level.

If you want to add multiple job catalogs to the same OEM, the settings must have the same hierarchy levels.


13.10.3 Determining a Job Catalog

You specify an access sequence for each criterion. By doing so, you stipulate which fields the SAP system checks when it searches for a valid job catalog.

Procedure


Service Workshop Scheduling Job Catalog Catalog Determination Assign

Criteria .

2. Assign the criteria.


13.10.4 Defining a Workshop Department Procedure


Business Management Master Data Workshop Scheduling Define Workshop

Department (Labor Value Group) .

2. Define values for the labor value group.

Example

01 – Mechanic

02 – Electric

03 – Paint Shop


13.10.5 Creating Job IDs

Workshop managers can create job catalogs containing estimated times for service requests that customers frequently make at a workshop. The job IDs consist of a description and the estimated time.

The job ID is used in the service order.

Prerequisites

In Customizing for Dealer Business Management, define the following data:

Job catalog

ID for the job catalog

Hierarchy level

This hierarchy level is manufacturer-specific and has one or two levels.

Catalog determination

The following criteria technique is used to determine the catalogs:

o Definition of the criteria table and access sequence

o Assignment of criteria

Example 1: manufacturer 1 finds catalog 1; manufacturer 2 finds catalog 2

Example 2: manufacturer 1 + country DE finds catalog 1, manufacturer 1 + country AT finds catalog 5

Procedure


Business Management Master Data Workshop Scheduling Job Catalogs

Maintain Job Catalog .

2. Choose the appropriate job catalog and display the jobs.

3. For new job IDs, assign the labor value group.

You can assign a package to a job ID. If a service advisor schedules an appointment using the job ID the package is assigned to, the system will add all the items maintained in the package to the service order.

4. Enter the estimated time for the job ID (dependent on the labor value main type).


14 Quality Inspection of Vehicle Service


14.1 Setting Up Quality Inspection of Vehicle Service Prerequisites

You have activated the BC set Settings for DBM Quality Inspection

(/DBM/DBM800_QUAL_CHECK).

You have checked the settings in Customizing for Quality Management. In particular, you have made sure that there is an inspection type for DBM in Customizing for

Quality Management under Quality Inspection Inspection Lot Creation Maintain

Inspection Types . Inspection type 89_DBM is provided in the BC set as an example.

You have checked the settings in Customizing for Dealer Business Management

(DBM) under Service Quality Inspection .

Procedure

1. For the material assigned to the vehicle model, you maintain the inspection setup and assign an inspection type. You do this in the Quality Management view of the material master. In the inspection setup, you specify that you want inspections to be carried out for this material. For more information, see SAP Library on the SAP Help Portal at http://help.sap.com/erp. Under Application Help, open SAP Library and choose

SAP ERP Central Component Logistics Quality Management (QM) Quality

Planning (QM-PT) Basic Data (QM-PT-BD) QM-Specific Data in the Material

Master (QM-PT-BD-MM) Creating and Changing QM Data for a Material Editing

the Inspection Setup .

2. On the SAP Easy Access screen under Dealer Business Management Master

Data Quality Inspection , you create the necessary master data and assign the material (vehicle model) and plant to the inspection plans. With this assignment, you can have the materials (vehicle models) included in or excluded from special inspections in specific plants. For more information about inspection plans and inspection characteristics, see SAP Library on the SAP Help Portal at http://help.sap.com/erp. Under Application Help, open SAP Library and choose

SAP ERP Central Component Logistics Quality Management Quality Planning

(QM-PT) .

3. On the SAP Easy Access screen under Dealer Business Management Master

Data Quality Inspection Determine Quality Inspection Plan

(/DBM/QMI_I_PLAN), you assign an inspection plan (Group field) and a group

counter. You can assign more than one inspection plan and group counter. By entering a date, you define that the inspections should be done within a certain time frame.

http://help.sap.com/erp

http://help.sap.com/erp


15 Service Contracts

The contract item materials in a DBM service contract should only be of material type Service

(DIEN); otherwise errors can occur.


15.1 Assigning a Service Item Group

The service item group specifies a set of service items, for example, wheels, parts, or labor values. The service item group is used in service contracts to specify the coverage and percentages of a contract item.

Procedure


(DBM) Service Service Contract Define Service Item Group .

2. Specify the service item groups and their hierarchies.

3. In the DBM master data transactions (/dbm/mm01, /dbm/mm02), specify the service

item group for the relevant parts and labor values on the Basic Data tab page.

4. Define the service item groups that are relevant for the DBM service contract under the contract item details on the DBM Data tab page where the coverage and percentages are defined.


15.2 Determining Contract Split Indicator

The contract split indicator is necessary to copy contracts into a DBM order. This information is also used during the creation of splits in the fast split.

Procedure


Business Management Master Data Contract Edit Contract Split Indicator .

2. Define one contract split indicator for the order type 2003 (Service Contract Release

Order) and one for the order type 2103 (Service Contract Release Order Returns)

with the following values:

Split Indicator

Description Order Type

Customer Account Assignment Category

Behavior of SAP Credit Management

CONTRACT1 SerContrReleaseOrder 2003 AAG IO 25 Considers Entire Job Amount (Standard Behavior)

CONTRACT2 SerContrReleaseOrderReturns 2103 AAG IO 25 Considers Entire Job Amount (Standard Behavior)

3. For the customer, enter AAG IO (account assignment category, internal order).


Business Management Master Data Contract Change Conditions for

Determining Contract Split Ind. .

5. Enter the condition records for the relevant order types:

Order Type Split Indicator

2000 CONTRACT1

2103 CONTRACT2


16 Vehicle The VMS vehicle forms the basis of the DBM vehicle.

See also:

SAP Library under InfoSources in SAP Automotive Vehicle Management System

(VMS)

From the SAP Easy Access screen, choose Logistics Logistics Execution

Vehicle Management System

Implementation Guide (IMG) for Logistics Execution under Vehicle Management System (VMS)


16.1 Assigning an Internal Order Type in the Control Table Use

For vehicle processing, an internal order is also used to handle the value flow. The user does not to have to manage this internal order.

Service and value-increasing activities are handled by means of a service order. The system uses the internal order for the vehicle to post/calculate the costs.

Procedure


(DBM) Vehicle Enter Control Value.

2. Assign the internal order type with control value Q200 to the control object /DMB/V_AUART.


16.2 Enhancement Concept (Vehicle) Use

To fulfill the requirements of a Dealer Business Management system, the vehicle object from the Vehicle Management System (VMS) had to be extended. This was carried out on the basis of the SAP product.

For more information, refer to the related documentation listed below:

In the SAP Library choose SAP Product Concepts

In the Implementation Guide (IMG) for Cross-Application Components choose SAP Product

In the documentation for function module /DBM/VM01 in development package /DBM/VEHICLE_MASTER

Procedure

1. Call transaction COMM_HIERARCHY Maintain Categories and Hierarchies.

2. Create a new product hierarchy as follows:

1. Choose New Hierarchy and enter the hierarchy ID DBM_VHCLE with the same text as description.

2. Choose New Category , enter the category ID ROOT with the same text as description and leave the indicator for the product/object assignment blank.

3. Choose New Category , enter the category ID DBM_VEHICLE with the same text as description and leave the indicator for the product/object assignment blank.

4. Place your cursor in DBM_VEHICLE and Choose New Category .

5. Enter the category ID DBM_PASSENGERCAR with the same text as description.

6. Enter the basic data for the category:

Product type: 01 material

Object family: 0602 vehicle (Automotive DBM)

Category Description: DE, DBM CAR

7. Enter further categories with the same attributes (for example, lorry, van, motorcycle).

3. In Customizing for Cross-Application Components , chose SAP Product Product

Category Assign Catalog Hierarchies to Applications. The category hierarchy created in transaction COMM_HIERARCHY has to be assigned to an application in Customizing.

4. Choose Assign Hierarchies to Applications and assign the ID you have created, for example, DBM_VHCLE to the application 03 Product .

5. Choose Assgmt per Product Type for Application Product and assign the ID you have created, for example, DBM_VHCLE to the application 01 Material .


6. Also in transaction COMM_HIERARCHY Maintain Categories and Hierarchies , on the tab page Set Types, you assign set types by placing the cursor on DBM_PASSENGERCAR .

o DBM_V_IKEYS Key

o DBM_V_IMODEL Model data

o DBM_V_IMODELT Model texts

o DBM_V_IOPTION Features

o DBM_V_OPTIONT Feature texts

o DBM_V_IPARTNER Partner

o DBM_V_IREGHIST Registration history

o DBM_V_ISINT Maintenance and service intervals

o DBM_V_IVEHICLE Vehicle master

o DBM_V_IWTY Warranty data

o DBM_V_IRCL Recalls

o DBM_V_IPRICES Vehicle prices

o DBM_V_IFINANC Financing

o DBM_V_ILEASING Leasing

o DBM_V_ICOND Conditions

o DBM_V_IGENOPT Generic option data

7. In Customizing for Cross-Application Components, choose SAP Product Settings

for Product Type Number Assignment Define Number Ranges for the Product

Type "Material".

8. Define a number range interval for all categories for which individual objects have been created.

Refer also to SAP Notes 903914 (DBM: Technical Documentation on Vehicle Process) and 900850 (DBM: Technical Documentation for Vehicle Data Enhancements) for enhancement cookbooks.


16.3 Vehicle Search If the standard vehicle search is not sufficient, the enhancement concept is described in SAP Note 905556 (Enhancing the Vehicle Search User Interface /DBM/VSEARCH).

16.3.1 Vehicle Search with Search Engine TREX

16.3.1.1 Setting Up the RFC Connection for TREX

Refer to chapter Setting Up the RFC Connection.

16.3.1.2 Transaction COM_SE_ADMIN Procedure

1. Choose Goto Customizing Business Objects and Indexes. .

2. Choose Settings for Business Object and enter the business object VEHICLE

with class /DBM/CL_SE_VEHICLE.

3. Choose Settings for Object Type/Index , enter the object type 1 and select the

Multilingual checkbox.

4. From the Search Engine Service Administration screen, choose Index

Create/Activate Indexes .

5. Choose the entry VEHICLE and start the indexing.

If you use the integrated VMS and DBM scenarios (see SAP Note 941633), you must make sure that the VMS-related VMSVEHICLE business object does not have an active index and that SAP Note 1388118 is implemented in your system.

16.3.2 Vehicle Search using SAP HANA For more information, see chapter Generic Settings for SAP HANA-based Searches.

1. Run transaction ESH_COCKPIT. 2. Choose Create. 3. In the dialog box,select the software component IS-A-DBM (Dealer Business

Management). 4. Select the model /DBM/VEHICLE. 5. Choose Create Connector. 6. Wait for the status of object to be in Prepared. 7. Select the object again in the table of search object connectors. 8. Choose Actions ->Schedule Indexing.

A dialog box opens, listing the technical and authorization objects. Select the Start Immediately checkboxes for objects, wherever applicable. In the Full Indexing Mode menus, choose Clear Index Content.

9. Choose OK. 10. Wait for the connector status to become Active.


16.4 Creating a Dummy Material for the Vehicle Model Use

You create the following data:

Material

Class

Configuration Profile

Then you assign this configurable material with the material type VEHI to a dummy class. You create a configuration profile for the material. In the application menu for the Vehicle Management System (VMS) , you have to assign the material to a material role and the material role to the user.

Procedure

For Class

1. From the SAP Easy Access screen, choose Cross-Application Components

Classification System Master Data Classes.

2. Enter the class type 300 (variants) and a description.

3. On the tab page Char. (characteristics) , create a dummy material with the following data:

o Data type: CHAR

o Number of chars: 3

o Dummy value

For Material


Business Management Master Data Part Create Material .


o Industry sector M (Mechanical engineering)

o Material type: VEHI Confi. Vehicle

In the Classification view, a dummy class is assigned under A.

3. Choose the following views:

o Basic Data 1

o Basic Data 2

o Classification

o Sales and Distribution: Sales Organization Data 1

o Sales and Distribution: Sales Organization Data 2

o Sales: General Plant Data


o Purchasing

o MRP 1

o MRP 2

o MRP 3

o General Plant Data/Storage 1

o General Plant Data/Storage 2

o Accounting 1

4. In Basic Data 1, enter an existing division and the general item category group 0002 (configuration).

5. In the view Sales and Distribution: Sales Organization Data 2 , enter the item category group 0002 (configuration).

6. In the view Sales and Distribution: General/Plant Data, enter no check for the availability check.

7. In the Purchasing view, set the indicator for batch management requirement and enter the manufacturer. You can only enter it if the setting Use Manufacturer No is enabled in transaction omt0.

8. In the MRP 1 view, enter the MRP type for No planning

9. In the Accounting 1 view, enter the valuation category X and the valuation class 3100 .

For Configuration Profile

1. From the SAP Easy Access screen, choose Logistics Production Process

Process Order Environment Master Data Material Master Environment

Configuration Profile Create .


o Priority 01

o Profile name

o Assign class type 300 and dummy class (stored under A)

3. Save your configuration profile.

Additional information about how to use material master for vehicle models can be found in SAP Note 1258776 (Smart Usage of Material Master for Vehicle Models). Information about how to enhance the DBM model master is provided in SAP Note 929089 (DBM: Technical Documentation on Model Master).


16.5 Creating a Dummy Material for Vehicle Features Use

Standard features and optional extras are defined during configuration in the manufacturer system. Standard features can have a price = 0, optional extras have a price > 0.

The vehicle is delivered with the desired configuration. The dealer can also add accessories to the vehicle. Accessories can be inventory-managed materials or manual parts.

Procedure


Business Management Master Data Part Create Material – DBM .

2. For standard features and optional extras, create a material with the following data:

o Industry sector M (Mechanical engineering)

o Material type NLAG (Non-stock material)

o You can choose from the following views:

Basic Data 1

Basic Data 2

Sales and Distribution: Sales Organization Data 1

Sales and Distribution: Sales Organization Data 2

Sales: General Plant Data

Purchasing

MRP 1

MRP 2

MRP 3

Accounting 1


o From the above-mentioned views, choose the following:

Basic Data 1: Division, Material Group (recommended)

Sales and Distribution: Sales Organization Data 2 : item category group NLAG

MRP 1 : MRP characteristic ND (no MRP)

MRP 2: procurement type P

Non-inventory-managed dummy materials for vehicle features are required for all features that are priced separately and built in to the vehicle by the OEM or distributor (and not by the dealer), for example, a radio.


16.6 Creating Search-Relevant Customizing Procedure

You need to maintain standard VMS customizing to search for vehicles of particular models.

1. On the SAP Easy Access screen, choose Logistics Logistics Execution Vehicle

Management System Basic Data VMS Roles Assign Vehicle Model .

2. Assign the dummy material to the material role QMAT .


Management System Basic Data VMS Roles Assign User Roles .

4. Assign the material role (for example, QMAT ) and the organization role (for example, QORG ) to the user.


16.7 Determining the Navigation Profile Use

If you want to create a vehicle, you must maintain Customizing settings for the determination of the navigation profile.

Procedure


(DBM) Vehicle Navigation in Vehicle Master Navigation Profile Determination

Assign Navigation Profile.

2. Enter the following data for the access sequence /DBM/VEHPRO_CTRL :

Category ID Division Nav. Prof. (Navigation Profile)

<blank> <blank> INIT (initial screen)

DBM_PASSENGERCAR 01 DBM1 (standard navigation profile)


16.8 Maintaining the Model Catalog Procedure


(DBM) Vehicle Vehicle Model Master Process Model Catalog.

2. Assign an appropriate template material to a model catalog.


16.9 Model Catalog Determination Procedure


(DBM) Vehicle Vehicle Model Master Model Catalog Determination Define

Access Sequences.

2. Check whether an appropriate access sequence has been defined.


(DBM) Vehicle Vehicle Model Master Model Catalog Determination Assign

Model Catalog.

4. Use the access sequence you have just defined to assign a model catalog.


16.10 Creating a Vehicle Model Procedure


Business Management Master Data Vehicle Model Edit Vehicle Model Master .

2. Create a vehicle model master record with the following data:

1. Select a model catalog.

2. Create a vehicle model and enter the sales code and service code for the model.

3. Enter the existing dummy material in the Material field.

Alternatively you can create a new material with an internally- or externally-assigned material number.


Business Management Master Data Vehicle Model Edit Body Type .

CAB Convertible , KOM Station Wagon etc.


Business Management Master Data Vehicle Model Edit Vehicle Type .

PKW Passenger Car


Business Management Master Data Vehicle Model Edit Fuel Type .

Diesel, Gasoline

6. On the SAP Easy Access screen, choose Logistics Logistics Execution Dealer Business Management → Master Data → Vehicle Model → Edit Features Category

. You must define feature categories, and assign corresponding materials.


16.11 Assigning Vehicle Model and Users to VMS Roles Procedure


Management System Basic Data VMS Roles Assign Vehicle Model.

2. Assign the dummy material to the material role QMAT .


Management System Basic Data VMS Roles Assign User Roles.

4. Assign the material role, for example, QMAT and the organization role, for example, QORG to the user.


16.12 Action Control Use

You execute the following for action control:

Define number range for action control

Check action control, such as DBM1 and DBM2 in Customizing for the Vehicle Management System (VMS) .

In action control determination, assign a primary and secondary matrix (for example DBM1 and DBM2) to the material.

Procedure

1. In Customizing, choose Logistics Execution Vehicle Management System (VMS)

Number Ranges Define Number Ranges for Action Control Determination.

2. Enter 01 as number range and VELO: Internal Key as number range object.


Control Data Define Action Controls and Define Action Matrices.

4. Ensure the action control matrices provided by delivery customizing are adequately reflecting your business processes.


Management System Basic Data Define Action Control Determination.

6. Define the action control determination.


16.13 Defining Number Ranges for Internal Vehicle Number Procedure


Number Ranges Determine Number Ranges for Internal Vehicle Number .

2. Enter 01 as number range and VELO: Vehicle No. as number range object.


16.14 Maintaining Number Ranges for Vehicle Chain Order Group Use

The number range object is called /DBM/OG .

Procedure


(DBM) Vehicle Vehicle Master Define Number Range for Vehicle Chain Order

Group . To have this customizing node, implement SAP Note 1042653, or you can maintain the number range object directly with transaction SNRO .

2. Create a number range interval for the Vehicle Chain Order Group .


16.15 Creating a Customer Use

The standard system forms the basis for the Dealer Business Management (DBM) customer master. The following changes and additions have been made:

Simplified user interface

Simplified navigation

Aggregated display

Procedure

On the SAP Easy Access screen, choose Logistics Logistics Execution Dealer

Business Management Master Data Customer Business Partner Cockpit

You can use transaction /DBM/BP to create, change and display business partners. If you create a business partner with a customer role, the corresponding SD customer is also created in the background.


16.16 Creating a Vehicle and Assigning a Customer Procedure


Business Management Vehicle Processing Vehicle Master .

2. Enter the following data and choose Continue (Enter).

o Vehicle BT (Business Transaction)

o Division

o Plant

3. Choose a model catalog and a sales code for the vehicle model, and save your data. When you save, the system creates the vehicle.

4. If the system prompts you to ‘Execute the upgrade report COM_PRODUCT_UPGRADE’, you must execute the report. You can find information about how to execute the report in the report documentation (SE38 → Goto → Documentation ). In addition, check SAP Note 906042. Generally, you only execute this report if the system requests it.

5. You execute the report in all the systems in the landscape along the transport route (execute in system 1 → transport to system 2 → import in system 2 → execute in system 2, and so on). That is, you first execute the report in the development system. In a customer system, ensure that you transfer customer-specific set types to the relevant systems before you execute the report. It is possible that the transport request remains empty after the report has been executed. Refer to SAP Note 1055794 for more information about this issue.

6. Choose Actions .

7. Choose Assign Customer , and enter the customer number.

8. Save your entries.


16.17 Mass Vehicle Processing


16.17.1 Enhance the Action Control

You execute the following for action control:

Check action control, such as DBM1 and DBM2 in Customizing for the Vehicle Management System (VMS).

In action control determination, assign a primary and secondary matrix (for example, DBM1 and DBM2) to the material.

Procedure


Control Data Define Action Controls and Define Action Matrices .



Management System (VMS) Basic Data Define Action Control Determination .

4. Define the action control determination.


16.17.2 Enhance VMS Action Technical Details

You use this procedure to define the screens to be called during trigger of actions.

Procedure


Enhancements Define Technical Details for Actions .


Bulk actions delivered are normally created as primary actions (apart from the action for pre-delivery inspection. This action does not follow the VMS action framework and cannot be executed through VMS action APIs.), with an alias to corresponding single actions. These also define the program and screen to be used while triggering the action.


16.17.3 Define Bulk Actions

You use this procedure to enable actions to be applicable for a set of vehicles in the Mass

Vehicle Processing function (transaction /DBM/MASSACTIONS).

Procedure

1. In Customizing, choose Logistics Execution Dealer Business Management (DBM)

Vehicle Vehicle Master Vehicle Control Define Bulk Actions .

2. Select the actions that need to be bulk-enabled.

3. Save the entries.


16.17.4 Define Vehicle Creation Control Value

You use this procedure to define which actions must be executed on vehicles in the Mass Vehicle Processing function (transaction /DBM/MASSACTIONS).

Procedure


Vehicle Define Control Values Define Vehicle Creation Control Value .

2. Maintain the entry as follows:

o Control Object: /DBM/V_VEH_CREA_BULK

o Description: Action: Bulk Vehicle Creation

o Control Value: QCRB

3. Save the entry.


16.17.5 Determine Vehicle Stock Age

This setting defines the actions to be performed on vehicles to determine their stock age.

Procedure


Vehicle Define Control Values Define Sales Control Value .

2. Add new actions or change existing ones, as required.


16.18 Additional Costs


16.18.1 Define Categories for Additional Costs

In this Customizing activity, you define the different categories of additional costs that can incur from a third party, such as transportation, maintenance, or insurance costs.

You can post or cancel additional vehicle costs only using the Mass Vehicle Processing transaction. Standard SAP ERP transactions (such as those used for purchase orders, goods receipts, and invoices) do not support posting or cancellation of additional vehicle costs.

Procedure


(DBM) Vehicle General Data Define Categories for Additional Costs .

2. Choose New Entries.

3. Enter a unique key for the category as well as a brief description.



16.18.2 Create Dummy Material for Additional Cost Category Procedure


Business Management (DBM) Master Data Part Create Material .


o Industry sector: M (Mechanical engineering)

o Material type: DEIN Service

3. In Basic Data 1, enter the general item category group as NLAG (non-stock materials) or LEIS (services without delivery).

4. Save the material.


16.18.3 Assign Material to Additional Cost Category Procedure


Business Management (DBM) Master Data Additional Costs Assign Material to

Additional Cost Category .

2. To assign a dummy material for a category, choose New Entries.

3. Enter the dummy material for the category and the plant for which this assignment is valid.



17 Vehicle Sales Assistant


17.1 Maintaining Number Ranges for the DBM Deal Use

You can create number ranges for DBM deals. You cannot create DBM deals without number ranges.

You can also assign the number range for deals. Each combination of plant and sales organization can have a separate number range.

Procedure

To define number ranges for deals, in Customizing, go to Logistics Execution Dealer

Business Management (DBM) Vehicle Sales Deal Deal Number Range Define Number

Range for DBM Deal .

To assign the deal number ranges, in Customizing, go to Logistics Execution Dealer

Business Management (DBM) Vehicle Sales Deal Deal Number Range Assign Deal

Number Range .


17.2 Assign Notification Types

Using this procedure, you can perform the following:

Define the notification type to be used in the process of deal creation.

Define the task code group and task code to be assigned to test drives in the vehicle sales assistant (VSA).

Define the notification type task that must be displayed in the Activities Today area of the VSA home screen.

Define default source code for notification type

The notification type is determined by the control code assigned, for example, fleet order.

Procedure

1. In Customizing, go to Logistics Execution Dealer Business Management (DBM)

Vehicle Sales Assign Notification Types and maintain necessary entries.

2. Define notification type for each control code.

3. Define the task code group and task code corresponding to the notification type. This task code is used to identify whether the activity is related to test drives, and populates additional fields to capture relevant data on the VSA interface.

4. If there are multiple control codes defined, all the corresponding notification tasks will be available in the Activities Today area of the VSA home screen.

5. If you want to maintain any default values for the source of the activity, this can be done in this Customizing.


17.3 Define Alias for VSA Events If you would like to control the visibility of events based on any other events, you can maintain those events in this Customizing activity. This will internally check both the events before showing them on the user interface.

For example, the creation of an order from a quotation is not supported if the quotation is already rejected. Therefore, before showing the event Create Order from Quotation for a selected quotation, with the help of this Customizing setting the system checks whether or not the quotation is rejected.

Procedure

In Customizing, go to Logistics Execution Dealer Business Management (DBM) Vehicle Sales UI Control Define Alias for VSA Events.


17.4 Define Hierarchy Mapping

Using this procedure, you define hierarchy mapping based on which the order items are displayed hierarchically in the user interface for a deal.

While order items (that is to say, either item categories or features classes) are displayed in the UI, these are segregated into different hierarchy elements based on their mapping. Then based on which hierarchy elements are mapped to that particular order type, order items are displayed in the UI.

Procedure

In Customizing, go to Logistics Execution Dealer Business Management (DBM) Vehicle

Sales UI Control Define Hierarchy Mapping .


17.5 CRM-DBM Integration

If there is an external system connected where sales leads are created for processing in SAP DBM, there are settings that need to be defined. For more information on how to set up the system to support external systems, refer to SAP Note 1964300.



17.5.1 Map CRM Product Category to DBM Technical Item Category

In this Customizing activity, you can map the CRM product category to the SAP DBM technical item category.

When a CRM lead is transferred to the SAP DBM system, the CRM products attached to this lead are identified as parts, packages, or models in the SAP DBM system based on this mapping.

Procedure


Sales CRM-DBM Integration Map CRM Product Category to DBM Technical Item

Category and maintain necessary entries.


17.5.2 Map CRM Lead Partner to DBM Deal Partner

In this Customizing activity:

You can map the CRM lead partner function to the SAP DBM deal partner function.

When you create a deal in the SAP DBM system from a lead that was transferred from a CRM system, you need to identify a main partner from all the business partners associated with that lead.

The CRM partner whose partner function is defined as the main partner will be identified as the customer for the SAP DBM deal.

Procedure


Sales CRM-DBM Integration Map CRM Lead Partner to DBM Deal Partner and maintain necessary entries.


17.5.3 Map CRM Lead Source to DBM Notification Source In this Customizing activity, you can map the CRM lead source to the SAP DBM notification source.

When a CRM lead is transferred to the SAP DBM system, a DBM notification source code corresponding to the source of lead gets identified based on this Customizing setting.

Example

To maintain DBM notification source code group and code, you should identify the catalog defined for DBM notification type. You can do so in the following IMG activity: Cross-Application Components -> Notification -> Notification Creation -> Notification Content -> Catalogs and Catalog Profiles for Notification Type.

For example, for notification type D4, catalogs defined are:

2 [Tasks]

D [Coding]

You can find code groups and corresponding codes defined for catalogs under IMG activity: Cross-Application Components -> Notification -> Notification Creation -> Notification Content -> Maintain Catalogs -> Edit Catalogs.

Procedure


Sales CRM-DBM Integration Map CRM Lead Source to DBM Notification Source and maintain necessary entries.


17.5.4 Assign Default Task Code For Notification Type

In this Customizing activity, you can assign a default task code to a notification type.

You can specify a default task code as well as a task description for each notification type. During the creation of a notification, default task details are identified and attached depending on its type.

Procedure


Sales CRM-DBM Integration Assign Default Task Code for Notification Type and maintain necessary entries.


17.6 Define Object Control Framework - Event Schema In this Customizing activity, you create event schemas to group certain events together. You can execute only those events that are listed within the defined schemas.

Procedure

In Customizing, go to Logistics Execution Dealer Business Management (DBM)

Framework Components Object Control Framework - Event Schema .


17.7 Define Automatic Rejection Reason for Quotations In this Customizing activity, you can define the reason for automatic rejection of alternative quotations whenever an order is created from a specific quotation.

Let us assume that there are three quotations existing for a customer requirement. If you select one of these quotations and create an order from it, the other two quotations are automatically rejected and assigned the reason defined here.

Procedure


Sales Deal Define Automatic Rejection Reason for Quotations . Select a rejection reason from the menu options and save the change.


17.8 Assign Rejection Reason In this IMG activity you can assign rejection reasons defined in SAP ERP to objects within the vehicle sales assistant (VSA) application. The reasons explain why an object was rejected.

If this Customizing setting is not maintained, all the rejection reasons defined in SAP ERP are displayed by default.

Procedure


Sales UI Control Assign Rejection Reason . Assign a rejection reason to the relevant DBM object.


17.9 Define Calculation Sheet Using the Calculation Sheet function, you can summarize the revenue, discount, and cost values for all vehicles (including trade-in vehicles) that are part of the order. You can thereby calculate the profit made on each order. The layout of the calculation sheet is flexible and can be changed in SAP DBM Customizing. For example, you may at times want to ascertain the calculated profitability (including costs); you could later decide that the cost information must not be shown and that only the overall discount should be displayed.

Procedure

Use the Customizing activities and BAdIs under Logistics Execution Dealer Business

Management (DBM) Vehicle Sales Calculation Sheet to define groups, cell types, and schema for the calculation sheet.


17.10 Deal Search

17.10.1 Deal Search with Search Engine TREX

17.10.1.1 Setting Up the RFC Connection


17.10.1.2 Transaction COM_SE_ADMIN for Deal Search Procedure

1. Enter transaction code COM_SE_ADMIN and then choose Goto Customizing

System Settings Change New Entries .




o Max. Auth. Check: 100

3. Choose Goto Back

4. Choose Goto Customizing Business Objects and Indexes. .

5. Choose Settings for Business Object and enter the business object DBMDEAL with

class /DBM/CL_SE_DEALSEARCH.

6. Choose Settings for Object Type/Index, enter the object type 1 and select the

Multilingual checkbox.


Create/Activate Indexes for Object Type 1 of object DBMDEAL. This will be available through BC set /DBM/DBM800_VSA.

8. Choose the entry DBMDEAL and start the indexing (full).

17.10.2 Deal Search using HANA For more information, see chapter Generic Settings for SAP HANA-based Searches.


Management). 4. Select the model /DBM/DEAL. 5. Choose Create Connector. 6. Wait for the connector status to become Prepared. 7. Select the object again in the table of search object connectors. 8. Choose Actions ->Schedule Indexing. 9. A dialog box opens, listing the technical objects. Select the Start Immediately

checkboxes for objects, wherever applicable. In the Full Indexing Mode menus, choose Clear Index Content.



17.11 Activity Search

17.11.1 Activity Search Using TREX



17.11.1.2 Transaction COM_SE_ADMIN for Activity Search 1. Enter transaction code COM_SE_ADMIN and then choose Goto Customizing System Settings Change New Entries . 2. Enter the following data:



o Max. Auth.Check: 100

3. Choose Goto Back . 4. Choose Goto Customizing Business Objects and Indexes. .

5. Choose Settings for Business Object and enter the business object DBMACTVTY

with class /DBM/CL_SE_ACTIVITYSEARCH.

6. Choose Settings for Object Type/Index , enter the object type. 7. From the Search Engine Service Administration screen, choose Index Create/Activate Indexes.

8. Choose the entry DBMACTVTY and start the indexing.

9. To plan a recurring job for the delta load, choose System Services Jobs

Job Definition .


without a variant.


Start condition: Immediate

Period values: Other Period: 2 minutes


17.11.2 Activity Search using SAP HANA For more information, see chapter Generic Settings for SAP HANA-based Searches.


Management). 4. Select the model /DBM/ACTIVITY. 5. Choose Create Connector. 6. Wait for the status of object to be in Prepared. 7. Select the object again in the table of search object connectors. 8. Choose Actions ->Schedule Indexing. 9. A dialog box opens, listing the technical objects. Select the Start Immediately

checkboxes for objects, wherever applicable. In the Full Indexing Mode menus, choose Clear Index Content.



17.12 Model Search

17.12.1 Model Search Using TREX



17.12.1.2 Transaction COM_SE_ADMIN for Model Search

1. Choose Goto Customizing Business Objects and Indexes .

2. Choose Settings for Business Object and enter the business object

DBMMODEL with class /DBM/CL_SE_MODELSEARCH.

3. Choose Settings for Object Type/Index, enter the object type 1 and select

the Multilingual checkbox.



5. Choose the entry DBMMODEL and start the indexing.

17.12.2 Model Search using SAP HANA For more information, see chapter Generic Settings for SAP HANA-based Searches.

1. Run transaction ESH_COCKPIT. 2. Choose Create. 3. In the dialog box,select the software component IS-A-DBM (Dealer

Business Management). 4. Select the model /DBM/MODEL. 5. Choose Create Connector. 6. Wait for the status of object to be in Prepared. 7. Select the object again in the table of search object connectors. 8. Choose Actions ->Schedule Indexing. 9. A dialog box opens, listing the technical objects. Select the Start

Immediately checkboxes for objects, wherever applicable. In the Full Indexing Mode menus, choose Clear Index Content.


Note: If a new vehicle model is created and generic options are configured in model master, it is required to schedule indexing for the search model /DBM/MODEL for the search to work correctly. In transaction ESH_COCKPIT, perform steps 7 – 11.

17.13 Business Partner Search

17.13.1 Business Partner Search Using TREX



17.13.1.2 Transaction COM_SE_ADMIN for Business Partner Search

1. Choose Goto Customizing Business Objects and Indexes .


2. Choose Settings for Business Object and enter the business object

BUS1006 with class /DBM/CL_SES_BP.

3. Choose Settings for Object Type/Index, enter the object type 1 and select

the Multilingual checkbox.



5. Choose the entry BUS1006 and start the indexing.

17.13.2 Business Partner Search using SAP HANA For more information, see chapter Generic Settings for SAP HANA-based Searches.

1. Run transaction ESH_COCKPIT. 2. Choose Create. 3. In the dialog box,select the software component IS-A-DBM

(Dealer Business Management). 4. Select the model /DBM/BUPA. 5. Choose Create Connector. 6. Wait for the status of object to be in Prepared. 7. Select the object again in the table of search object connectors. 8. Choose Actions ->Schedule Indexing, 9. A dialog box opens, listing the technical objects. Select the Start

Immediately checkboxes for objects, wherever applicable. In the Full Indexing Mode menus, choose Clear Index Content.



17.14 SAP Business Warehouse Management Integration in DBM Use This topic describes necessary activities for the configuration of DBM deal.

Prerequisites Before starting these activities, you need to perform or check the following activities:

RFC connectivity between source R/3 and BW has been set up.

General BW and R/3 settings are done.

Configuration Basic Configuration: Extractors

Use This section describes the activities in an R/3 Source System to set up the Customizing for the extractors. Execute the transaction SBIW in the source system. Below the structure item Data Transfer to the SAP Business Information Warehouse you will find all the described activities. Search for the activities with the title of the relevant section of the Configuration Guide. Some activities in this chapter are also required for other building blocks. If you have performed them already, you do not have to carry them out again. In that case you can skip certain activities in this chapter.

Transfer Business Content DataSources

Use If you want to transfer data from a source system into a BW system using a Business Content DataSource, you first have to transfer the Business Content DataSource in the source system from the D version into the active version (A version). This means that the necessary dictionary objects, like extract structures and so on, are created on the database.

Prerequisites The activity Transfer Application Component Hierarchy (transaction RSA9) must have been completed for your source system client.

Procedure These steps must be carried out in the SAP source system:

1. Run transaction SBIW.

2. In the Display IMG view, choose Data Transfer to the Business Information Warehouse Business Content DataSources Transfer Application Component Hierarchy. Alternatively, run transaction RSA9.

3. In the Display IMG view, choose Data Transfer to the Business Information Warehouse Business Content DataSources Transfer Business Content DataSources.

4. In the Installation of DataSource from Business Content view, expand the node SAP,

mark the relevant DataSources, and choose Select Sub-tree +/- .

5. Once you have selected all required DataSources and nodes, choose Activate DataSources from the application toolbar.

6. If a dialog box appears requesting the user to enter a development class, enter the appropriate development class and choose Save.

Relevant DataSources

Path Relevant DataSources


DBM_ROOT 0DBM_DLDOC, 0DBM_DLGOP, 0DBM_DLHDR, 0DBM_DLITM, 0DBM_DLREQ

Note that some of the Business Content DataSources may have already been activated before. If you reactive these, you will have to replicate the DataSource and activate the relevant Transfer Rule again in BW system, since the timestamp is changed in your reactivation. One way to avoid this is to check if the DataSource has not been activated at this point. You can mark one DataSource and then choose Version Comparison from the Application Toolbar. If version A is different from version D, that means this DataSource has not been activated yet, and that you can activate it. Otherwise, do not activate this DataSource again.

If you want to continue with the next activity, do not leave the transaction.

Postprocess DataSources and Hierarchy

In the Display IMG view, choose Data Transfer to the Business Information Warehouse Postprocessing of DataSources Edit DataSources and Application Component Hierarchy.

Check if the newly activated DataSources are available.


17.15 Activity Printing Use The printing function covers the test drive activity as well. It can be further extended in Customizing to print other activities.

Procedure To extend the printing function to cover more activities, go to Customizing activities for Dealer Business Management (DBM) under Order -> Basic Functions -> Output Determination.

See Also For more information, also refer to the following chapters:

Defining Printout Forms

Defining Condition Tables


18 Warranty Processing


18.1 Warranty Customizing Procedure

In order to copy DBM-specific data to warranty claims, make the settings described in

Customizing for Dealer Business Management under Service Warranty Business Add-

Ins (BAdIs) Warranty Documentation.


18.2 Assigning Warranty Claim Item Type – Order Item Category For each manufacturer and division, you assign a warranty claim item type to each item category for which a warranty claim can be created in the service order. The system copies these settings when a warranty claim is created from a service order.

Procedure

In Customizing for Logistics Execution, choose Dealer Business Management (DBM) → Service → Warranty → Assign Warranty Claim Item Type to Order Item Category.


18.3 Editing Warranty Data Procedure


Business Management Master Data Warranty Edit Warranty Master Data .

2. Choose Warranty Category in the navigation area, and enter the following data:

o Warranty Category, for example 01

o Warranty Control, for example 1 ( Vehicle Warranty)

For technical reasons, tables /DBM/S_WTY_KIND and /DBM/S_WTY_KINDT have been delivered without entries. Make the following entries using transaction code SE16N:

1 Vehicle Warranty

2 Goodwill

3 Parts Warranty

4 Recall

5 Parts Goodwill

o Manufacturer

Enter a manufacturer (debtor number of manufacturer or vendor/supplier) that has also been created as a creditor. You can make references by

choosing Control Data Account Control and making an entry in the Vendor field. You have to edit general data, company code data and sales area data for the customer master.

o Tax classification of customer

o Type of warranty claim ( 1DBM or self-defined)

3. Choose Warranty Profile in the navigation area, and enter the following data:

o Warranty Profile, for example WTY01

o Warranty Category, for example 01

o Warranty Control, for example 1 ( Vehicle Warranty)

o Warranty Period/Runtime

o Mileage/kms

4. Choose Warranty Determination Sales Code in the navigation area, and enter the following data:

o Warranty Ctrl, for example 01 (Vehicle Warranty)

o Tax. Depart. Cty, for example DE

o Division, for example 01


o Model Sales Code

o Enter a model sales code that has been created with transaction /DBM/VMODEL

o Warranty Profile, for example WTY01

5. Choose Warranty Determination Brand in the navigation area, and enter the following data:

o Warranty Ctrl, for example 01 (Vehicle Warranty)

o Tax. Depart. Cty, for example DE

o Division, for example 01

Example

Field Entry

Warranty Profile WTY001

Warranty Category W1

Warranty Control 1

Warranty Period/Runtime 24

Unit of Measure for Warranty Period/Runtime MON

Mileage In 0

Mileage Out 9999999

Unit of Measure for Counter KM

Standard Warranty Category X

If you want to copy DBM-specific data to warranty claims, make the settings described in

Customizing for Dealer Business Management under Service Warranty Business Add-

Ins (BAdIs) Warranty Documentation.


18.4 Defining Catalog Code Procedure

In Customizing for Logistics – General choose Equipment und Tools Management (ETM)

Master Data Catalogs Define Catalog Code. You can create your own catalogs. Refer to the Customizing activity documentation for more information.


18.5 Defining Automatic CO Account Assignment Determination Use

You have to define account assignments for posting the accounting documents from warranty processing in CO.

Procedure

In Customizing for Plant Maintenance and Customer Service choose Warranty Claim

Processing (or start transaction OWTY) Accounting Define Automatic CO Account

Assignment Determination (see also long text of customizing).

Example

Use cost element 800010 in controlling area 0001 the cost center WARRANTY .

Primary cost element 800010 should exist as GL account in company code 0001 and must be in the cost element group INT DBM_DB .


18.6 Allowing Change of CO Account Assignments for Condition Use

You define the conditions under which the person responsible is allowed to change the automatically-determined account assignment. This will allow the person to post to a different account assignment object during warranty claim processing.

Procedure

In Customizing for Plant Maintenance and Customer Service, choose Warranty Claim

Processing (or start transaction OWTY) Accounting Allow Changeability of CO Account

Assignments for Condition (see also long text of customizing).

Example

Enter all condition types which are used in pricing procedure for your claim type. For claim type 1DBM and pricing procedure WT0002, enter the following data:

1DBM HA00

1DBM HB00

1DBM K005

1DBM K007

1DBM K020

1DBM K030

1DBM MWST

1DBM NETP

1DBM PRIC

1DBM PRIV

1DBM PROC

1DBM PROV

1DBM VST


18.7 Defining Warranty Number Range Use

In this Customizing activity, you define the number range for claims You can create an internal and external number range for each claim type. The number range object is called WTY_CLAIM .

Procedure

1. In Customizing for Plant Maintenance and Customer Service choose Warranty

Claim Processing (or start transaction OWTY) Define Number Ranges for Warranty

Claims .

2. Create two groups, Warranty Claim and Recall .

3. Assign 1DBM to the Warranty Claim group and CDBM to the Recall group.


18.8 WTYRCL Customizing Procedure

In Customizing for Logistics Execution choose Dealer Business Management (DBM)

Service Recall Documentation.


Service Recall Define Order Type and Warranty Category for Recalls. You can define the order type and the warranty category which is used for recall split creation.

Refer to the Customizing activity documentation for more information.

Example

Enter the following data for the OEMs:

OEM Order Type: Warranty Category:

<Manufacturer number> 2001 01


18.9 Defining Recall Priority Procedure


Service Recall Define Recall Priority. Here you can add your own values.

Refer to the IMG activity documentation for more information.


18.10 Defining Order Type and Warranty Category for Recalls Procedure


Service Recall Define Order Type and Warranty Category for Recalls. Here you can define the type of order to be created according to on the OEM and warranty category.

Refer to the Customizing activity documentation for more information.


18.11 Assigning Item Type and Item Category to OEM Use

You must assign the item types (such as FRC , MATC , TEXT and so on) to DBM Item Categories . This mapping is used when a recall is copied into a DBM Order and this mapping defines which items or labor values have to be added to the DBM Order.

Procedure

On the SAP Easy Access screen choose Logistic Logistics Execution Dealer Business

Management Warranty Recalls Assign Item Type and Item Category to OEM .


19 Cash Desk

To use DBM cash desk, you have to activate the BC Set Settings for DBM Cash Desk

(/DBM/DBM800_CASHDESK).


19.1 Setting Characteristics of Document Type SK Use

You define document type SK Cash Document to perform credit-side and debit-side postings in the cash desk.

Procedure

1. In Customizing for Financial Accounting (New) , choose Financial Accounting

Global Settings (New) Document Document Types Define Document Types for

Entry View.

2. Choose the document type SK Cash Document and then choose Detail .

3. In the screen Account Types Allowed , set the Customer and Vendor indicators.


19.2 Defining Business Transactions Use

The cash desk functions support G/L account postings. You can configure these business transactions as follows:

Restrictions on business account assignment (cost center)

G/L account predefined

Tax indicator predefined

Procedure


(DBM) Cash Desk Define Business Transaction.

2. Enter business transactions, such as 17 Office Material , 68 Bank .


19.3 Assigning a Number Range to Cash Desk Document Types Use

Use the number range object /DBM/TILL for the cash desk functions.

Define range for the /DBM/TILLK object.

Procedure

1. From the SAP Easy Access screen, choose Tools ABAP Workbench

Development Other Tools Number Ranges.

2. Enter the number range object /DBM/TILL .

3. Enter data to confirm that the number ranges are assigned to a company code.

4. Choose Goto Number Ranges and create an interval according to the entries in the cash desk document types.

5. The default value for the interval is 01 . This value is also transported with the business configuration set Cash Desk Document Types .

Refer to the manual steps as described in SAP Note 1267644:

1. Execute transaction SNRO.

2. Create new number object /DBM/TILLK, if it does not exist.

Field Entry

short text AWKEY

long text Awkey for acc.documents in cashdesk

Number length domain CHAR12

Warning% 10,0

Main memory buffering checked

No. of numbers in the buffer 20

Create new range interval.

Number range 01

From number 000000000001

To number 999999999999


19.4 Setting Up a Cash Desk Work Center Use

You can use this procedure to assign organizational and content settings to a cash desk.

Procedure


(DBM) Cash Desk Define Cash Desk Work Center.

2. Enter the required data.

3. On the SAP Easy Access screen, choose Tools Administration Monitor

System Monitoring User Overview.

4. Copy the desired terminal and enter it in the IMG activity Maintaining Cash Desk Work Center in the field CDWC: Computer .

This ensures that the cash desk can only be started at a specific work center (since there can also be connections to local systems, such as a cash drawer).

5. In accordance with Accounting, assign the following data to the cash desk work center:

o Business transactions

o Master data (cost centers)

o Accounts


20 Dynamic Sheet


20.1 Define Style Use You use this Customizing activity to define the style of the sheet with respect to the character formats it uses. You can assign these character formats to a layout and change the values by double- clicking on a character format.

Procedure


Customer Data Management Dynamic Sheet Define Style.


20.2 Define Content Object Use

You use this Customizing activity to define the content objects you can use to add to the dynamic sheet. The name of the content object appears as a title on the sheet.

The content object is the basic unit of the Dynamic Sheet. You can assign parameters to each content object. The parameter names must first be defined in the activity Define Content Object Parameters . The syntax for parameters is <Tablename>-<Fieldname>.

Procedure


Customer Data Management Dynamic Sheet Define Content Object.

Example

The Order Content Object has the /DBM/SPLHDR_DB-AUFART parameter with value ‘1000’. The business logic uses this value and select the entries from /dbm/splhdr_db with the AUFART = 1000.

The Order content object only checks the parameter /DBM/SPLHDR_DB-AUFART. If you wish to create parameters for your own content objects, you must implement the check in the implementation class of the BAdI. If you wish to create your own content objects, refer to the Business Add-Ins documentation (BAdI: Content Objects for Dynamic Sheet).


20.3 Define Content Object Parameters Use You use this Customizing activity to define the content object parameters. These values are assigned to the content objects.

Procedure


Customer Data Management Dynamic Sheet Define Content Object Parameters.


21 Notification


21.1 Maintaining Enhancements and BAdI Implementations Procedure


Customer Data Management Notification Business Add-Ins (BAdIs) Notification

Documentation , and follow the instructions in this section


21.2 Defining Notification Types for DBM Use

You use this Customizing activity to assign standard notification types to DBM notification types.

The following DBM notification types are supported:

S - Sales Activity

C - Complaint

D - Vehicle Damage Rep.

If you define a new notification type or copy a notification type, you also maintain this data in this Customizing table.

The program logic may differ in some cases according to the DBM notification type. For example, the customer is not required data for DBM notification type D , but it is for DBM notification type S .

Procedure


Customer Data Management Notification Define Notification Types for DBM .


21.3 Defining Outcome Type and Outcome Code Use

You use this Customizing activity to define the possible outcome types and outcome codes for the notification types D1 Sales Activity and D2 Complaint . These outcome types and codes can be assigned to notification tasks. On the outcome code level, you define which code values (texts) should be copied to the task long texts. You also define whether the value should appear in upper case.

Default outcome types:

contact result

competitor

other offer

kind of contact

Default outcome codes:

buys over central

business lost

delivered

Procedure


Customer Data Management Notification Define Outcome Type and Outcome Code .


21.4 Assigning Outcome Type to Task Code Use

You use this Customizing activity to assign the outcome types to the task codes. The outcome types that the user then chooses depends on the task codes.

Procedure


Customer Data Management Notification Assign Outcome Type to Task Code .


21.5 Assigning Task Code to Order Type Use

You use this Customizing activity to define the task code group and the task code for the automatically-generated tasks, in accordance with the order type and the notification type.

When you create a notification for notification types D1 Sales Activity and D2 Complaint from a DBM order (transaction code /DBM/ORDER01 or /DBM/ORDER02), the system always generates a task in the background.

Procedure


Customer Data Management Notification Assign Task Code to Order Type .


21.6 Defining Follow-Up Task Code Use

You use this Customizing activity to determine the date on which you would like the task to start, in accordance with the original notification type, task code group and task code. You can define follow-up tasks for the notification types D1 Sales Activity and D2 Complaint .

In the field Number of Days (Date of the Follow-Up Task in Days), you can set the number of days from which the task should begin, counted from the end-date of the original task. If an end-date does not exist, then the number of days is counted from the start date of the original task.

Procedure


Customer Data Management Notification Define Follow-Up Task Code .

Example

If the field Number of Days (date of the follow-up task in days) is set to 4, and the end-date of the original task is 18.08.2006, the task would begin on 22.08.2006.


21.7 Setting BAdI: Input Help for Outcome Type Use

You can use this BAdI to process the event ON_F4 in the ALV grid for the outcome type of the table /DBM/CU_OUTCOME. You can use this BAdI to change the behavior of the standard input help or make your own check on the manually-entered value.

Procedure


Customer Data Management Notification Business Add-Ins (BAdIs) BAdI: Input Help for

Outcome Type.


21.8 Setting BAdI: Input Help for Outcome Code Use

You use this BAdI to process event ON_F4 in the ALV grid for the outcome codes of table /DBM/CU_OUTCOME. You can use this BAdI to change the behavior of the standard input help.

Procedure


Customer Data Management Notification Business Add-Ins (BAdIs) BAdI: Input Help for

Outcome Code.


21.9 Setting BAdI: Input Help for Outcome Code Value Use

You use this BAdI to process the event ON_F4 in the ALV grid for the outcome code value of the table /DBM/CU_OUTCOME. You can use this BAdI to change the behavior of the standard input help, or perform your own check on the manually-entered value.

Procedure


Customer Data Management Notification Business Add-Ins (BAdIs) BAdI : Input Help for

Outcome Code Value .


21.10 Setting BAdI: Filter Text of Outcome Code Use

You use this BAdI to select which outcome code texts from outcome tables are copied to the long text of the appropriate task. You can override the standard behavior that copies the texts if they have indicator FLGTO = 'X' set in table /DBM/CU_OUTCOME.

Procedure


Customer Data Management Notification Business Add-Ins (BAdIs) BAdI: Filter Text of

Outcome Code .


21.11 Configuring E-Mail for Notification Procedure

To send e-mails from the Notification, make the following settings:

1. Maintain the profile parameters for SMTP

icm/server_port_X = PROT=SMTP,PORT=250<INSTANCE No.>, TIMEOUT=300

2. Enter transaction code SCOT

You maintain node SMTP (client dependent); the node exists for each client by default. Configure the following data for your SMTP node as follows:

Node SMTP

Description Mail Server

Mail-Host <your mail server name>

Mail-Port <your mail port, default is 25 >

Under Supported address types , enable Internet and set the address areas you allow (for example, *sap.com ).

3. Enter a default domain by choosing Menu Settings->Default Domain . Use, for example, <CLNT>.<SID>.R3.sap.corp ->

4. Schedule job for automatic send/receive process by choosing Menu View Jobs Create and then entering the following data:

Jobname: SAPCONNECT_SMTP_<CLIENT>

Program: RSCONN01

Variant: INT

Period: For example 10 minutes

Note: For user data in SU01 of mail users: if you want to send only, add your standard email address, for example, Internet Mail [email protected] (Communication Method: E-Mail)


22 Order


22.1 Order Search

22.1.1 Order Search with Search Engine TREX

22.1.1.1 Setting Up the RFC Connection


22.1.1.2 Transaction COM_SE_ADMIN for Order Searches

Procedure

1. Enter transaction code COM_SE_ADMIN and then choose Goto Customizing

System Settings Change New Entries .




o Max. Auth. Check: 100

3. Choose Goto Back


Create/Activate Indexes for Object Type 1 of object Order. This will be available

through BC set /DBM/DBM800_EOS.

If you are using enhanced order search, you need to create additional indexes for search levels such as item, job, split, and task. The BC set

/DBM/DBM800_EOS delivers the different object types for the object Order.

New indexes need to be created for each object type, as described above.

5. Choose the entry ORDER and start the indexing (full) for each object type.

6. To plan a recurring job for the delta load, choose System Services Jobs Job

Definition .


without a variant.


o Start condition: Immediate

o Period values: Other Period: 2 minutes



22.1.2 Order Search using HANA For more information, see chapter Generic Settings for SAP HANA-based Searches.


Management). 4. Select the models /DBM/ORD_HEADER. 5. Choose Create Connector.

Wait for the connector status to become Active. 6. Repeat steps from Step 2-5 for each of the following models: /DBM/ORD_ITEM,

/DBM/ORD_JOB, /DBM/ORD_SPLIT, and /DBM/ORD_TASK.


22.3 Defining Order Search Use

The order search requires manual entries in the first installation. You must perform the following steps for order search.

Procedure


Order Order Search Define Order Search View .

2. Enter the data as indicated in the table below.

Field Value

Order Search View Standard

Program Name /DBM/SAPLORDER_UI

Scrn.No 1006

3. In Customizing for Logistics Execution choose Dealer Business Management

Order Order Search Define Order Search Attributes.


ScrNo Screen Field Table Name Database Field

Att Type

1105 /DBM/SPLHDR_COM-AUFART /DBM/SPLHDR_DB AUFART S String

1105 /DBM/VBAK_COM-ANGE_USER

/DBM/VBAK_DB ANGE_USER S String

1105 /DBM/VBAK_COM-AUDAT /DBM/VBAK_DB AUDAT D Date

1105 /DBM/VBAK_COM-FERTIG_DAT

/DBM/VBAK_DB FERTIG_DAT D Date

1105 /DBM/VBAK_COM-HSTAT /DBM/VBAK_DB HSTAT S String

1105 /DBM/VBAK_COM-LICPL /DBM/VBAK_DB LICPL S String

1105 /DBM/VBAK_COM-PERNR /DBM/VBAK_DB PERNR S String

1105 /DBM/VBAK_COM-SPART /DBM/VBAK_DB SPART S String

1105 /DBM/VBAK_COM-VGUID /DBM/VBAK_DB VGUID S String

1105 /DBM/VBAK_COM-VHVIN /DBM/VBAK_DB VHVIN S String

1105 /DBM/VBAK_COM-VKORG /DBM/VBAK_DB VKORG S String

1105 /DBM/VBAK_COM-VTWEG /DBM/VBAK_DB VTWEG S String

1105 /DBM/VBAK_COM-WERKS /DBM/VBAK_DB WERKS S String

1105 /DBM/VBAK_COM-W_LEITZAHL

/DBM/VBAK_DB W_LEITZAHL S String


1105 /DBM/VBPA_COM-KUNNR /DBM/VBPA KUNNR S String

1105 /DBM/VBPA_COM-PARTNER /DBM/VBPA PARTNER S String

1105 /DBM/VBPA_COM-PARVW /DBM/VBPA PARVW S String

5. Install ORDER index. Enter into transaction COM_SE_ADMIN. Call menu Goto

Customizing Business Objects And Indexes .

6. Click Settings for Business Object and then click New Entries . Enter in the table fields with the following values:

7. Business Object: ORDER

8. Class for Bus. Object: /DBM/CL_SE_ORDERSEARCH

9. Save your entries.

10. Then select the new object.

11. Click Settings for Object Types .

12. Click New Entries .

13. Enter in the fields the following values:

Business Object ORDER or VEHICLE

Object Type: 1

Max. No Tasks: 1

Max Obj.Pack: 10

Scope of log: Only fatal errors

Multilingual = X

14. To have the new index build for the first time, you have to select it out of the list of active indexes (starting screen of transaction ses_admin) and click the button index immediately.

15. To have the data always up to date, a job has to be created, which runs every minute, but it should have already been created.

22.4 Defining Enhanced Order Search

The enhanced order search requires manual entries in the first installation. You must perform the following steps to run it.

Procedure

1. Activate BC Set /DBM/DBM800_EOS by using transaction SCPR20.

2. In Customizing for Logistics Execution, go to Dealer Business Management

Order Order Search Define Order Search View .



Field Value

Order Search View ORDER_SEARCH_ENH

Program Name /DBM/SAPLORDER_UI

Screen Number 4000

4. In Customizing for Logistics Execution, go to Dealer Business Management

Order Order Search Define Order Search Attributes .

5. Enter the data as indicated in the table below:

Screen Number

Screen Field Table Name Database Field Attribute Type

4001 /DBM/VBAK_COM-AWTYP

/DBM/VBAK_DB AWTYP S String

4001 /DBM/VBAK_COM-FERT_DATE_TMSTP

/DBM/VBAK_DB FERT_DATE_TMSTP D Date

4001 /DBM/VBAK_COM-MCODESD

/DBM/V_MODEL MCODESD S String

4001 /DBM/VBAK_COM-VALID_FR_TSTMP

/DBM/VBAK_DB VALID_FR_TSTMP D Date

4001 /DBM/VBAK_COM-VALID_TO_TSTMP

/DBM/VBAK_DB VALID_TO_TSTMP D Date

4002 /DBM/SPLHDR_COM-AUFART

/DBM/SPLHDR_DB AUFART S String

4002 /DBM/SPLHDR_COM-KUNNR

/DBM/SPLHDR_DB KUNNR S String

4002 /DBM/SPLHDR_COM-SHSTAT

/DBM/SPLHDR_DB SHSTAT S String

4002 /DBM/SPLHDR_COM-WTY_TYPE

/DBM/SPLHDR_DB WTY_TYPE S String

4002 /DBM/SPLHDR_COM-CLCSTAT

/DBM/SPLHDR_DB CLCSTAT S String

4002 /DBM/SPLHDR_COM-KDAUF_AUFK

/DBM/SPLHDR_DB KDAUF_AUFK S String

4002 /DBM/SPLHDR_COM-KDPOS_AUFK

/DBM/SPLHDR_DB KDPOS_AUFK S String

4002 /DBM/SPLHDR_COM-KOSTL

/DBM/SPLHDR_DB KOSTL S String

4002 /DBM/SPLIT_COM-CNTTY

/DBM/SPLIT CNTTY S String

4003 /DBM/JOB_COM-ABGRU

/DBM/JOB ABGRU S String


4003 /DBM/JOB_COM-ADDITIONAL_WORK

/DBM/JOB ADDITIONAL_WORK S String

4003 /DBM/JOB_COM-APPROVED

/DBM/JOB APPROVED S String

4003 /DBM/JOB_COM-APPROV_USER

/DBM/JOB APPROV_USER S String

4003 /DBM/JOB_COM-DEFERRED_WORK

/DBM/JOB DEFERRED_WORK S String

4003 /DBM/JOB_COM-FOLLOW_UP

/DBM/JOB FOLLOW_UP D Date

4003 /DBM/JOB_COM-IDENT_USER

/DBM/JOB IDENT_USER S String

4003 /DBM/JOB_COM-KDAUF_AUFK

/DBM/JOB KDAUF_AUFK S String

4003 /DBM/JOB_COM-KDPOS_AUFK

/DBM/JOB KDPOS_AUFK S String

4003 /DBM/JOB_COM-PACKAGE_ID

/DBM/PACK_H PACKAGE_ID S String

4003 /DBM/JOB_COM-PACKAGE_TYPE

/DBM/PACK_H PACKAGE_TYPE S String

4003 /DBM/JOB_COM-REJECTED

/DBM/JOB REJECTED S String

4003 /DBM/JOB_COM-SPLIT_INDICATOR

/DBM/JOB SPLIT_INDICATOR S String

4003 /DBM/JOB_COM-STATUS

/DBM/JOB STATUS S String

4004 /DBM/VBAP_COM-ITCAT

/DBM/VBAP ITCAT S String

4004 /DBM/VBAP_COM-ITOBJID

/DBM/VBAP ITOBJID S String

4004 /DBM/VBAP_COM-ITSTAT

/DBM/VBAP ITSTAT S String

4005 /DBM/TASK_COM-DEPT

/DBM/TASK DEPT S String

4005 /DBM/TASK_COM-TSTAT

/DBM/TASK TSTAT S String

6. To build the new index for the first time, you must select Order Business Object from

the list of active indexes (starting screen of transaction SES_ADMIN) and choose the

Index Immediately button.

7. Choose the Full indexing mode.


22.4.1 Defining BAdI: Enhanced Order Search - UI Enhancement

You can use this BAdI as a screen enhancement BAdI in the package /DBM/ORDER under

the /DBM/ORDER enhancement spot. You can use it to replace subscreens in the enhanced

order search view with other subscreens.

This BAdI is always called as it is not based on a filter.

Prerequisites

Only one implementation is active.

Procedure

In Customizing for Logistics Execution, choose Dealer Business Management (DBM)

Order Business Add-Ins (BAdIs) BAdI: Enhanced Order Search - UI Enhancement .


22.4.2 Defining BAdI: Enhanced Order Search - Criteria Enhancement

You can use this BAdI to change the search criteria for the enhanced order search in the

package /DBM/ORDER under the /DBM/ORDER enhancement spot. Using this BAdI, you can

add, delete, or modify search criteria for the order search.


Prerequisites


Procedure


Order Business Add-Ins (BAdIs) BAdI: Enhanced Order Search - Criteria Enhancement .


22.4.3 Defining BAdI: Enhanced Order Search - Result Enhancement

You can use this BAdI to change the enhanced order result list in the package /DBM/ORDER

under the /DBM/ORDER enhancement spot.

Customer includes are available for each tab of the enhanced order search, that is to say, at header, job, item, split and task levels respectively, as follows:

/DBM/S_ORD_HEADER_CI

/DBM/S_ORD_JOB_CI

/DBM/S_ORD_ITEM_CI

/DBM/S_ORD_SPTHDR_CI

/DBM/S_ORD_TASK_CI

If you want any additional fields, you must add those fields to the respective customer includes. This BAdI must then be implemented for populating data into the newly added fields.


Prerequisites


Procedure


Order Business Add-Ins (BAdIs) BAdI: Enhanced Order Search - Result Enhancement .


22.5 Up-selling and Cross-selling

Up-selling indicates the complete replacement of a customer’s originally required item with another item that is higher in value.

Cross-selling refers to the marketing of additional items along with the customer’s originally required item.

Procedure

Activate BC Set /DBM/DBM800_UPS_CRS by using transaction SCPR20.


22.5.1 Define Proposal Type

You define the proposal type, which can be either of the following kinds:

Up-selling, which involves offering customers more expensive products or services, upgrades, or other add-ons in place of those they had originally intended to purchase.

Cross-selling, which involves offering customers products or services in addition to those they had originally intended to purchase.

Flexible, which is a predefined combination of products and services from the up-selling or cross-selling categories.

Package replacement, which offers customers other packages as add-ons in place of existing packages.

Proposal types must be categorized into Additional, Replace, Flexible (which is applicable for packages, where an item within a package can be identified as an up-selling/cross-selling alternative to the original item) or Package Replacement (only for replacing one package entirely with another).

Procedure

1. Activate BC Set /DBM/DBM800_UPS_CRS by using transaction SCPR20.


(DBM) Order Specific Processes Up-selling and Cross-selling Define Proposal

Type .

3. In the editing mode, choose New Entries.

4. Enter a name and description for the proposal type. In the Proposal Category column, select a value to define its behavior.

5. Save the values.

You can create multiple proposal types using the above procedure.


22.5.2 Define Replacement Procedure

You define whether the original item is to be rejected or deleted during the up-selling process.

Replacement procedures can be either of the following:

Reject Original Items

Delete Original Items

Standard Settings

When Reject Original Items is the selected option, you must mandatorily select a reason for rejection. The values for this Rejection Reason field are derived from the IMG activity Define Reasons for Rejection. To add a new rejection reason, you need to add it within this IMG activity.

When Delete Original Items is the selected option, the Rejection Reason field is not mandatory.

Procedure

1. Activate BC Set /DBM/DBM800_UPS_CRS by using transaction SCPR20.


(DBM) Order Specific Processes Up-selling and Cross-selling Define

Replacement Procedure .

3. Select the procedure in the Replacement Procedure field and save the selection.


22.6 Defining a Reason for Rejection

All defined rejection reasons from Sales and Distribution (SD) are also available in Dealer Business Management (DBM). In Customizing for Dealer Business Management, you can define for each rejection reason whether pricing should be deactivated for an item with that rejection reason. If the rejection reason is used in DBM orders, it is important that you set the value to X (No cumulation - Values cannot be used statistically) or Y (No cumulation - Values can be used statistically) in the Price Cumulation field. For more information, see the documentation of the following Customizing activity and the field help of the field Price Cumulation in this Customizing activity.

Procedure

In Customizing for Logistics Execution, choose Dealer Business Management Order

Basic Functions Define Reasons for Rejection .


22.7 Working with Suborders Use

You use the suborder for the multi-branch service. In the main order, you can create a suborder to assign work tasks to another branch. The suborder for a task in the main order corresponds to a job in the suborder.

Procedure

1. Define a plant customer for each plant used in the suborder process

o Execute transaction SPRO. Navigate to Materials Management → Purchasing → Purchase Order → Set up Stock Transfer Order → Define Shipping Data for Plants .

2. Account assignment category

o In Customizing for Dealer Business Management , navigate to Order → Account Assignment → Internal Order Account Assignment → Assign Account Assignment Object for Internal Order .

The following data is an example:

i. 0001 0001 0001 7000 70 1 PLANT_0001 /DBM/CO_INT_GET_HEADER_INTORD

ii. 0001 0001 0002 7000 70 1 PLANT_0001 /DBM/CO_INT_GET_HEADER_INTORD

3. Zero level order definition:

o Define number range interval for internal order type Q700.

i. Execute transaction SPRO. Navigate to Investment Management → Internal Orders as Investment Measures → Master Data → Orders → Define Order Types . Select Q700 and assign it to the A – ZZZZZZZZZZZZ interval.

o Zero level internal order creation

i. Use transaction KO01 to create an internal order.

o Set zero level internal order:

i. In Customizing for Dealer Business Management , navigate to Master Data → Account Assignment → /DBM/MBS_0LEVEL - Zero level internal order for suborder .


Do not forget to extend the settlement rules for your suborder order type (in our delivery is 7000) (see section Defining Parameters for Settlement Rule ) with values similar to those in the example below.

Example

DBM Order Type

Operating Concern

Characteristic Source Structure

Source Assignment

DBM Order






22.8 Defining Copying of Order Items

DBM order items are copied during different scenarios such as copying of orders with the copy tool, copying items during creation of a suborder, adding packages to an order, and copying packages from service contracts to orders. In some cases, the correct item category needs to be determined while copying the items to the target order. This is relevant especially during the DBM delivery process. You have to make the following settings to determine the correct item category.

Procedure


Order Copying of Items Determination of Item Category Define Criteria .

If, for example, during creation of a suborder, the source plant uses DBM deliveries and the target plant does not use DBM deliveries, the correct item category needs to be determined for the suborder items in the target plant. The same applies if packages are added to orders that are created in different plants where the DBM delivery process is different.

2. Specify the entries for the relevant plants in your company as follows (for example):

In criteria table /DBM/IC_ENG_IC, specify:

Usage for Copying Items

Source Control Code

Source Item Category

Target Plant

Target Item Category

2 CS D020 0002 P002

3 PC P002 0001 D020


22.9 Define Order Type Schema

Use A new order type schema PDI_REL has been created and should be active. All PDI-relevant

order types should be maintained in this schema.

Procedure In Customizing for Logistics Execution, choose Dealer Business Management (DBM) -> Order -> Order Type -> Order Type Schema.


23 Archiving


23.1 Maintaining Enhancements and BAdI Implementations Procedure


Archiving Archiving Documentation , and follow the instructions.


23.2 Archiving Control for DBM Order Use

Residence time determines the time interval (in calendar days) that must elapse between the time of closing the DBM order (the date when order gets status Closed ) and setting the deletion indicator by the preprocessing program.

The wildcard character * also can be used and the program must use the strongest condition if there is more than one. Conditions with fixed values are stronger than condition with * . The DBM order is not be archived if no conditions match.

Procedure

You can configure archiving for DBM orders in Customizing for Logistics Execution

Dealer Business Management (DBM) Archiving Archiving Control For DBM Order.

Example

Sales org: *

Order type: *

Residence time: 200

Sales org.: 0001

Order type: 2000

Residence time: 500

In this case, if customer would like to archive a DBM order with order type 2000 or with sales org 0001 then the preprocessing program will check if the 500 days have elapsed. In each other case the program will check if 200 days have elapsed.


24 Time Recording


24.1 Creating Customer Include Fields for Table CATSDB

DBM Time Recording allows the creation of time stamps on order, task, and item level. To be able to transfer this additional data to CATS, relevant fields have to be added to the table CATSDB via the Customer Include CI_CATSDB.

Procedure

Add fields for order, task, and item to Customer Include CI_CATSDB by adding the structure

/DBM/CATSDB to that Customer Include.

You must add structure /DBM/CATSDB to Customer Include CI_CATSDB or add

exactly the same components (same component name and component type as in

/DBM/CATSDB), otherwise DBM Time Recording cannot be used and will run into

errors.

Adding Customer-Specific Index For Table CATSDB

See SAP Note 1121243.



24.2 Transferring DBM Data to CATS Procedure

To ensure the transfer of the DBM specific data of the time stamps (order, task, item), you must create a relevant project for SAP Enhancements:

1. Use transaction CMOD

Enter a project name and then create the project.

2. Click Enhancement assignments and enter enhancements CATS0002 and CATS0005

3. Choose Components and then double-click EXIT_SAPLCATS_002 .

4. Create includeZXCATU02

Fill in the fields for DBM Order Task or Item accordingly for transfer to CATS.

Example

The class method /DBM/CL_TM_DBMDATA_EXAMPLE->FILL_CATS_DBM_DATA holds the example logic to fill the DBM specific data into the CATS record. This is just an example of how the data can be filled. This class method must be called inside the include 'ZXCATU02'.

The user exit parameter 'enrich_table' is a table. It will have only one record in this case. Pass the single record into the class changing parameter 'cs_enrich_table' which is returned with DBM fields updated with data. Update this back into the 'enrich_table' parameter.

Sample coding for transferring the DBM data to CATS:

DATA:

lo_dbmdata TYPEREFTO /dbm/cl_tm_dbmdata_example.

FIELD-SYMBOLS: <ls_enrich_table> TYPE cats_comm.

READTABLE enrich_table ASSIGNING <ls_enrich_table> INDEX1CREATE OBJEC

T lo_dbmdata. CALLMETHOD lo_dbmdata->fill_cats_dbm_data

EXPORTING is_tcats = sap_tcats

CHANGING cs_enrich_table = <ls_enrich_table>.

In the Time Sheet (transaction CAT2), you can call a pop-up with the additional fields by clicking Additional fields . If you want to use this functionality you must perform following steps, after you have added the fields to the structure CATSDB

Create the subscreen 1000 for program SAPLXCAT , which contains the additional fields. This subscreen is included in the dialog box that is called in the time sheet.

Also a function module to receive data in the transfer structure fields and to return the data to the calling program needs to be created. The function module used is EXIT_SAPLCATS_005 . You can do the relevant coding in the customer enhancement project, which was created for the transfer of the DBM specific data, as mentioned above.

For the optional process of subsequent cost processing, it is also necessary to create an implementation for the enhancement CATS0006, and to change the coding of the enhancement CATS0002, to ensure that the DBM Order is updated accordingly if subsequent costs were posted for it.

CATS0002: The method /DBM/CL_TM_DBMDATA_EXAMPLE->SET_SUBSEQ_COSTS contains the logic to set the flag in the DBM Order, that


subsequent costs occurred. Corresponding coding must be added to the include ZXCATU02.

CATS0006: Add coding to the include ZXCATU05, such as the method /DBM/CL_TM_DBMDATA_EXAMPLE->SAVE_ORDER to save the updated DBM order.

If you want to use the subsequent costs process for time recording, add the following coding to include ZXCATU02 (in addition to the coding above for transferring DBM data).

Note: You must adapt this coding.

A) Add following data declaration to the top include ZXCATTOP:

DATA go_order TYPE REF TO /dbm/cl_order.

B) Call the coding of CATS0002 below, only if the field of <ls_enrich_table> (used for the DBM order number) is not empty. You have to change the first line of the coding if the field which was added to the include CI_CATSDB (view paragraph ‘Creating Customer Include Fields for Table CATSDB’) for the DBM order number has a different name than in this example (DBMVBELN). The first line must be:

IF NOT <ls_enrich_table>-<fieldname for DBM Order> IS INITIAL.

Coding of CATS0002

IF NOT <ls_enrich_table>-dbmvbeln IS INITIAL.

DATA: lv_ok_code TYPE sy-ucomm.

lv_ok_code = sy-ucomm.

IF lv_ok_code = 'TIME'

OR lv_ok_code = 'COPY'.

CALL METHOD lo_dbmdata->set_sub_seq_costs

EXPORTING

is_tcats = sap_tcats

is_enrich_table = <ls_enrich_table>

CHANGING

co_order = go_order

EXCEPTIONS

order_error = 1

order_closed = 2

order_not_relevant = 3.

IF sy-subrc = 1.

MESSAGE e057(/dbm/rfc_common) WITH sy-uname go_order-

>ms_vbak_com-vbeln.

ENDIF.

IF sy-subrc = 2.

MESSAGE e350(/dbm/tm) WITH go_order->ms_vbak_com-vbeln.

ENDIF.

ENDIF.

IF lv_ok_code = 'SAVE'.


EXPORTING


is_enrich_table = <ls_enrich_table>

CHANGING


co_order = go_order

EXCEPTIONS

order_error = 1

order_closed = 2


IF sy-subrc = 1.

MESSAGE e057(/dbm/rfc_common) WITH sy-uname go_order-

>ms_vbak_com-vbeln.

ENDIF.

IF sy-subrc = 2.


ENDIF.

if sy-subrc = 3.

message e002(/dbm/subseq_costs) with go_order->ms_vbak_com-

vbeln.

endif.

CALL METHOD lo_dbmdata->save_order

CHANGING

co_order = go_order

EXCEPTIONS

parameter_error = 1

OTHERS = 2.

ENDIF.

ENDIF.

The coding, implemented for user-exit CATS0006 can look as follows: DATA:

lo_dbmdata TYPE REF TO /dbm/cl_tm_dbmdata_example,

lv_ok_code TYPE syucomm.

lv_vbeln TYPE /dbm/vbeln_va,

lv_status TYPE status_vb,

ls_job_com TYPE /dbm/job_com.

FIELD-SYMBOLS:

<ls_enrich_table> TYPE cats_comm.

CREATE OBJECT lo_dbmdata.

*READ TABLE check_table ASSIGNING <ls_enrich_table> INDEX 1.

lv_ok_code = sy-ucomm.

IF lv_ok_code = 'SAVE'.

IF NOT go_order IS INITIAL.

* Check, if order is approved

CALL METHOD go_order->mo_status->get_header

EXPORTING

iv_action = 'CUST_APPROVAL'

RECEIVING

ev_status = lv_status.


IF lv_status = 'A'.

LOOP AT go_order-

>mt_job_com INTO ls_job_com WHERE jobnr <> '000000'.

IF ls_job_com-rejected IS NOT INITIAL OR

ls_job_com-deferred_work IS NOT INITIAL OR

ls_job_com-approved IS INITIAL.


ENDIF.

ENDLOOP.

ELSEIF lv_status = 'B'.


ENDIF.

CREATE OBJECT lo_dbmdata.

CALL METHOD lo_dbmdata->save_order

CHANGING

co_order = go_order

EXCEPTIONS

parameter_error = 1

OTHERS = 2.

ENDIF.

ENDIF.

IF lv_ok_code = 'YES'.


EXPORTING


is_enrich_table = gs_enrich_table "<ls_enrich_table>

IMPORTING

ev_vbeln = lv_vbeln

CHANGING

co_order = go_order

EXCEPTIONS

order_error = 1

order_closed = 2


IF sy-subrc = 1.

MESSAGE e057(/dbm/rfc_common) WITH sy-uname lv_vbeln.

RETURN.

ENDIF.

IF sy-subrc = 2.

MESSAGE e350(/dbm/tm) WITH lv_vbeln.

RETURN.

ENDIF.

ENDIF.


24.3 Setting Up Data Entry Profiles Use

You must define a default data entry profile for the configuration of the data entry in the time sheet.

Procedure

In Customizing for Cross-Application Components choose Time Sheet Specific Settings

for CATS classic Set Up Data Entry Profiles or enter transaction CAC1 .


24.4 Maintaining HR Master Data Use

For the use of DBM Time Recording, a minimum set of info types must be maintained for the relevant employees by using transaction PA30 (Maintain HR Master Data ).

Procedure

1. Maintain the following info types:

0000 - Actions

0001 - Organizational Assignment

0002 - Personal Data

0050 - Time Recording Info

0315 - Time Sheet Defaults

2. To maintain absences, use info type 0007, Planned Working Time.

3. To assign employees to a specific terminal group, create an individual info type with transaction PM01.

This info type can contain fields for:

Explicit assignment to a terminal group: data element /DBM/TM_VT_STTGR

Explicit assignment active: data element /DBM/TM_OVERW_I

Assignment for shared employee: data element /DBM/TM_VT_SBTGR (there can be more than one field for assignment as shared employee


24.5 Additional Information If CATS accumulates 0 hours for the time booked, 0 times (quantity) is calculated for the actual times. This can occur for a few reasons:

1. If the relevant work schedules for the employee grouping/work schedule rule is not created for the period. The working schedules can be generated using transaction PT01. The work schedule is maintained for each employee in the HR master record in the info type 0007 (Planned Working Time).

2. If time is booked during the time interval which is defined as a 'Break' in the Break Schedules in standard customizing, and if this break time is defined as 'Unpaid' time then 0 actual time is booked by CATS. This can be overrun in the CATS profile being used by setting the flag No Deduction of Breaks active.


25 Integration with SAP Credit Management

You can integrate SAP Credit Management in your DBM system. This allows you to use the credit limit check in DBM orders.


25.1 Setting Up the Credit Limit Check

To set up the credit limit check, see the Configuration Guide for SAP Credit Management on

SAP Service Marketplace at http://service.sap.com/fscm SAP Credit Management

Media Library Other . The following documentation only gives you some additional hints.

SAP FSCM (SAP Financial Supply Chain Management) uses SOA services to communicate with other applications. If SAP FSCM runs on the same host (the calling application), services can be configured as local Web services. If SAP FSCM runs on a different host (the calling application), services run over XI.

Procedure

1. Configure the following services by using transaction SOAMANAGER:

o Outbound services

SAP APPL 6.05

http://sap.com/xi/PI/FIN/Operational/Global

CreditWorthinessQuery_Out (synchronous)

CreditCommitmentNotification_Out (asynchronous)

CreditManagementAccountByIDQuery_Out

DocumentedCreditDecisionERPBusinessTransactionDocum

entNotification_Out

o Inbound services

FINBASIS 736

http://sap.com/xi/FSCM/Global

CreditWorthinessQuery_In

CreditCommitmentNotification_In

CreditManagementAccountByIDQuery_In

DocumentedCreditDecisionERPBusinessTransactionDocum

entNotification_In

2. Use the HTTPS protocol when configuring the logical port binding/connection. HTTPS

needs to install certificates with transaction STRUST on your host.

3. Configure the System Landscape Directory (SLD) for your business system. Check the SLD configuration by using transaction SLDCHECK.

4. Check the Web service utilities for error messages by using transaction SRTUTIL.


(DBM) Order SAP Credit Management (SAP Financial Supply Chain

Management) Activate Credit Limit Check for Payment Terms .

http://service.sap.com/fscm


6. Activate the credit limit check for a term of payment.

7. In Customizing for Financial Supply Chain Management, choose Credit

Management Integration with Accounts Receivable Accounting and Sales and

Distribution Integration with Sales and Distribution Define Risk Categories .

8. Check whether the risk categories are maintained in accordance with the risk classes

in Customizing for Financial Supply Chain Management under Credit Management

Credit Risk Monitoring Master Data Create Risk Classes .


25.2 Setting Up the Documented Credit Decision Prerequisites

You have set up Adobe Document Server correctly. To check the connection, see SAP Note 944221.

You have activated the following business functions:

FIN_FSCM_CCD_3

FIN_FSCM_CCD_2

FIN_FSCM_CCD

FIN_FSCM_CCD_INTEGRATION_3

FIN_FSCM_CCD_INTEGRATION

You have activated the following BC Sets:

UKM_DCD_CUST

/DBM/DBM800_CLC

You have applied SAP Note 1741485.

Procedure


Management Credit Risk Monitoring Documented Credit Decision Define Case

Types for Documented Credit Decision .

2. Create the missing case types.


Management Credit Risk Monitoring Documented Credit Decision PDF Form for

Snapshot Assign Forms .

4. Create the missing forms.

If the customer number and the business partner number differs:

If the customer (SD) number differs from the business partner (BP) number, a number

conversion is necessary. Business Add-In (BAdI) UKM_CONV2PARTNER has to be

implemented.

Procedure

1. Check the Configuration Guide for SAP Credit Management on SAP Service

Marketplace at http://service.sap.com/fscm SAP Credit Management Media

Library Other .

2. Implement BAdI UKM_CONV2PARTNER as described.



http://service.sap.com/fscm


26 Storage Goods Manager


26.1 Creating Required Master Data Procedure

To be able to use the DBM storage goods, you should configure the following settings for the specific objects in the master data:

Categories. Call transaction COMM_HIERARCHY Maintain Categories and Hierarchies . The categories are linked hierarchically in your base hierarchy. The set types are assigned to the actual category. You require one main category and eight sub-categories. When you maintain the categories that contain the set types, note the following:

a) Choose the product type: 01 Material.

b) Assign the object family 0603 Storage Goods (Automotive DBM).

c) Assign the set types.

d) Do not define any relationship types.

e) Leave the indicator for the product/object assignment blank for the main category

Enter the following categories. Only the mentioned set types can be used.

Main category (the name is free): it should contain the set types DBM_S_HIS and DBM_S_MAIN, these set types are inherited for the sub-set types as well.

You can use some or all of the sub-categories, but only the mentioned set types are allowed:

o DBM_S_HTfor Hard Top: contains the type dependent Set type DBM_S_HT

o DBM_S_RRfor Roof Rack: contains the type dependent Set type DBM_S_RR

o DBM_S_RSfor Rim Set: contains the type dependent Set type DBM_S_RS

o DBM_S_SCfor Snow Chain: contains the type dependent Set type DBM_S_SC

o DBM_S_SRfor Ski Rack: contains the type dependent Set type DBM_S_SR

o DBM_S_SWfor Summer Wheel: contains the type dependent Set type DBM_S_SW

o DBM_S_TSfor Tire Set: contains the type dependent Set type DBM_S_TS

o DBM_S_WWfor Winter Wheel: contains the type dependent Set type DBM_S_WW

The name of the categories is fixed. You have to maintain them in the customizing table under Dealer Business Management → Storage Goods Manager → Define Storage Type for Putaway.


Assign number ranges with the customizing node: Cross-Application Components, choose SAP Product → Settings for Product Type → Number Assignment → Define Number Ranges for the Product Type "Material".

Define number ranges for assignment of the product ID.

Create one or more groups and assign all the categories that you use in your system for Storage Goods. Note that categories are master data. Define a number range interval for all categories for which individual objects have been created.


26.2 Integrating Storage Goods into Memo Pad Use

There is a new BAdI implementation for displaying storage goods, and branching to the transaction /DBM/STG_SEARCH with the corresponding storage goods ID.

Procedure

You can define your own layout by using the new content object STG. In Customizing for

Logistics Execution , choose Dealer Business Management (DBM) Customer Data

Management Dynamic Sheet Layout Define Layout.


26.3 Defining Number Range for Storage Goods Use

In this Customizing activity, you can define a number range for DBM storage goods.

Procedure


Storage Goods Manager Define Number Range for Storage Goods .


26.4 Defining Storage Type for Putaway Use

In this Customizing activity, you can define which storage types you want to use for putaway from the eight types we provide:

Hard top

Roof rack

Rim set

Snow chain

Ski rack

Summer wheel

Tire set

Winter wheel

Furthermore, for each storage type, you can define a procedure that controls the printing of forms.

Prerequisites

To define a storage type, create a new category, see Creating the Necessary Master Data .

Procedure


Storage Goods Manager Define Storage Type for Putaway .


26.5 Defining Putaway Location Use

In this Customizing activity, you can define one or more locations for storage goods putaway for each plant.

Procedure


Storage Goods Manager Storage Define Putaway Location .


26.6 Defining Putaway Bin Use

In this Customizing activity, you can define one or more putaway bins for each putaway location. Furthermore, you can define the size of each putaway bin in meters.

Procedure


Storage Goods Manager Storage Define Putaway Bin .


26.7 Defining Permitted Storage Type for Putaway for Each Warehouse Use

In this Customizing activity, you can define one or more storage types that can be used for the putaway bin.

Procedure


Storage Goods Manager Storage Define Permitted Storage Type for Putaway for Each

Warehouse.


26.8 Defining Wheel Rim Size Use

In this Customizing activity, you define rim sizes.

Procedure


Storage Goods Manager Type-Dependent Data Wheel Rim Data Define Wheel Rim Size

.


26.9 Defining Wheel Rim Type Use

In this Customizing activity, you can define rim types.

Procedure


Storage Goods Manager Type-Dependent Data Wheel Rim Data Define Wheel Rim

Type.


26.10 Defining Wheel Rim Manufacturer Use

In this Customizing activity, you define the rim manufacturer.

Procedure


Storage Goods Manager Type-Dependent Data Wheel Rim Data Define Wheel Rim

Manufacturer.


26.11 Defining Tire Size Use

In this Customizing activity, you define tire sizes.

Procedure


Storage Goods Manager Type-Dependent Data Tire Data Define Tire Size .


26.12 Defining Tire Manufacturer Use

In this Customizing activity, you define tire manufacturers.

Procedure


Storage Goods Manager Type-Dependent Data Tire Data Define Tire Manufacturer .


26.13 Defining Standard Position of Storage Goods Use

In this Customizing activity, you define the standard positions for storage goods on a vehicle.

Procedure


Storage Goods Manager Type-Dependent Data Define Standard Position of Storage

Goods.

Example

Storage types for putaway:

set of winter wheels (01)

set of summer wheels (02)

set of rims (07)

set of tires (08)

Possible positions for storage types:

HL (back left)

HR (back right)

VL (front left)

VR (front right)


26.14 Defining Reminder / Expediting Data Use

In this Customizing activity, you define the following dunning/expediting data for each storage type for putaway:

A planned length in days, after which the first reminder is due. The date on which the first reminder is due is the reminder base date.

A reminder interval in days; this interval defines the length of time that elapses between reminders.

Procedure


Storage Goods Manager Type-Dependent Data Define Reminder/Expediting Data .


26.15 Defining Status Use

In this Customizing activity, you select which status to use from the ones provided for the storage goods.

Procedure


Storage Goods Manager Control Define Status

Example

Possible status of storage goods:

Created

Deleted

For removal from stock

For storage

Removed from stock

Stored

Scrapped


26.16 Defining Actions Use

In this Customizing activity, you select which actions to use from the ones provided for administering the storage goods.

Procedure


Storage Goods Manager Control Define Actions .

Example

Possible actions for the storage goods are:

Create

List Overview

Save

Reminder

Confirm putaway in storage

Confirm removal from storage

Delete Storage Goods

Putaway in storage

Removal from storage

Extend Time in Storage

Cancel prepare putaway in storage

Cancel prepare removal from storage

Prepare putaway in storage

Prepare removal from storage

Scrap Storage Goods


26.17 Defining Action Matrix Use

In this Customizing activity, you define how the status of a storage good changes when you execute a specific action.

Procedure

In Customizing for Logistics Execution , choose Dealer Business Management (DBM) → Storage Goods Manager → Control → Define Action Matrix

Enter the following:

The start status of the storage good (old status)

The action

The status of the storage good after you have executed the action (new status)

Ensure you have a line in the matrix with old status blank, and action ‘CRE’ (Create).


26.18 Defining Printout Forms Use

We do not ship smart forms with Storage Goods Manager. You can define them in the SAP

Easy Access screen by choosing Tools Form Printout Smart Forms .

Procedure


Storage Goods Manager Message Determination Define Message Type .

Here you can add an output type, and specify your smart form under ‘Processing routines’ as follows:

Program: /DBM/STG_FORMS

Form Routine: ENTRY

PDF/Smart form Form: name_of_your_smartform


26.19 Defining Condition Tables Use

In this Customizing activity, you define the condition tables for message determination in the Storage Goods Manager. This message determination is similar to the message determination used in Sales and Distribution (SD).

In the Storage Goods Manager, there are two different options for calling message determination:

Explicitly in dialog mode: Choose the print function in the order processing transaction.

Automatically by an action: When executing an action the message determination is called. When depending on the given status and action a message can be found the storage goods will be printed out.

You can find more information in the Implementation Guide (IMG) for Sales and Distribution (SD) under Maintain Condition Tables.

Procedure


Storage Goods Manager Message Determination Define Condition Table .


26.20 Defining Access Sequence Use

In this Customizing activity, you define the access sequences for message determination in Dealer Business Management (DBM). The message determination used in DBM is similar to that of standard Sales and Distribution (SD).

You can find more information in the Implementation Guide (IMG) for Sales and Distribution (SD) under Maintain Access Sequences.

Procedure


Storage Goods Manager Message Determination Define Access Sequence .


26.21 Defining Message Types Use

In this Customizing activity, you define message types for message determination in Dealer Business Management (DBM).

The message determination used in DBM is similar to that of standard Sales and Distribution (SD).

You can find more information in the Implementation Guide (IMG) for Sales and Distribution (SD) under Maintain Output Types.

Procedure


Storage Goods Manager Message Determination Define Message Type .


26.22 Defining Message Schema Use

In this Customizing activity, you define the output determination procedures for message determination in DBM. The message determination used in DBM is similar to that of standard Sales and Distribution (SD).

You can find more information in the Implementation Guide (IMG) for Sales and Distribution (SD) under Maintain Output Determination Procedure.

In the Customizing activity Define Storage Types for Putaway, you assign output determination procedures to each storage type.

Procedure


Storage Goods Manager Message Determination Define Message Schema .


27 Text Handling


27.1 Defining Criteria Table Use

In this Customizing activity, you define your own criteria table with which the system then determines the appropriate text catalogs.

You can use the fields of structure /DBM/ORDER_TEXT_DET_COM (Lean Condition: Comm. Structure for Text Catalog Determin.) as possible key fields. If required, you can enhance the structure, for example if the keys for the criteria tables that are provided are insufficient to determine text catalogs with the desired logic.

Procedure


Text Control Determination of Text Catalog for DBM Order Define Table of Criteria.


27.2 Defining Access Sequences Use

In this Customizing activity, you define the access sequence with which the system searches for valid text catalogs in a criteria table.

You can control the sequence in which the system checks the selected criteria tables. If the system does not find a suitable entry in the first criteria table, it checks the next table.

Procedure


Text Control Determination of Text Catalog for DBM Order Define Access Sequences.


27.3 Defining Control Model Master Use

In this Customizing activity, you define how you want to control model texts and model option texts.

You can create different text determination procedures and maintain how they are determined.

Procedure


Text Control Control Model Master.


27.4 Defining Control Vehicle Master Use

In this Customizing activity, you can define how you want to control vehicle texts and vehicle option texts. You can create different text determination procedures, define how they are determined and define text access sequences to copy texts to the vehicle master.

You can maintain long texts on vehicle level in a separate text view. You can maintain long texts referring to features by using a separate function in the features view. You can copy vehicle and option long texts (with or without reference) from the model master when you create the model, or an option.

Procedure


Text Control Control Vehicle Master.


27.5 Defining Control Labor Value Master Use

In this Customizing activity, you define how you want to control labor value texts.

You can create different text determination procedures and maintain how they are determined.

Procedure


Text Control Control Labor Value Master.


27.6 Defining Control Package Master Use

In this Customizing activity, you define how you want to control main package and variant package texts. You can create different text determination procedures and define how they are determined. You can maintain long texts on main package level or on variant package level on a separate tab page.

Procedure


Text Control Control Package Master.


27.7 Defining Control Memo Pad Use

In this Customizing activity, you define how you want to control customer information and vehicle information texts.

You can create different text determination procedures and define how they are determined.

You can define text access sequences for transferring texts to the memo pad.

Long texts can be found in the vehicle master, model master and in the customer master. The texts that are found are displayed in the memo pad. The found/displayed customer and vehicle information texts should be controlled logically by the constellation determined by Customizing for text control and the maintained texts in the vehicle, model and customer master data.

Procedure


Text Control Control Memo Pad.


27.8 Defining DBM Order Control Use

In this Customizing activity, you can define how DBM order texts work in the system (at header, split header, job, task, and item level).

You can create different text determination procedures, and define text access sequences to copy texts to the different levels of a DBM order. You can copy long texts to the DBM order from the following text objects:

Vehicle

Package Master (main or variant package)

Labor Value Master

Material Master (central texts, sales dependent texts)

Business Partner Information

Customer Master

You can also copy texts from the text pool to the DBM order.

A text indicator is a one character long initial for a text ID within a text object. If you want to use the Web Dynpro long text tool, you must create text indicators.

Procedure


Text Control Control DBM Order.


27.9 Defining Storage Goods Control Use

In this Customizing activity, you define how you wish to control storage goods texts. You can create different text determination procedures and define how they are determined.

Procedure


Text Control Control Storage Goods.


27.10 Defining Rule Key Use

In this Customizing activity, you define keys that represent text access sequence rules.

You can assign these rules to text access sequences to control which entries of a text access sequence have to be applied.

The keys enable you to implement the rules as they are available as filter values for the BAdI: Definition of Rule.

Procedure


Text Control Business Add-Ins (BAdIs) Rule of Text Access Sequence Define Rule Key.


27.11 Defining BAdI: Definition of Rule Use

In this Customizing activity, you can implement rules for text access sequences. The keys that are defined in the activity Define Rule Key are used as filter criteria for these BAdI implementations.

Procedure


Text Control Business Add-Ins (BAdIs) Rule of Text Access Sequence BAdI: Definition

of Rule.


27.12 Defining Text Determination Logic Key Use

In this Customizing activity, you define keys that represent text determination logic.

You can assign these text determination logic keys to text access sequences to trigger specific text determination logic.

These keys enable you to implement the text determination logic as they are available as filter values for the BAdI: Definition of Text Determination Logic.

Procedure


Text Control Business Add-Ins (BAdIs) Text Determination Logic of Text Access

Sequence Define Text Determination Logic Key.


27.13 Defining BAdI: Definition of Text Determination Logic Use

In this Customizing activity, you implement text determination logic. The keys that are defined in the activity Define Text Determination Logic Key are used as filter criteria for these BAdI implementations.

Procedure


Text Control Business Add-Ins (BAdIs) Text Determination Logic of Text Access

Sequence BAdI: Definition of Text Determination Logic.


27.14 Defining Text Handling for Purchase Requisition Procedure

For information, see SAP Note 1050958.


28 Sundry Items in a Fleet Order

By using a fleet order, you can sell many vehicles in a single order and you can add sundry items to the fleet order, for example motor insurance or tire insurance. For the sundry items, you must make the settings as described in Creating Activity Type for Sundry Items.


28.1 Creating Activity Type for Sundry Items

The system requires an activity type for the sundry items to distinguish between activities for the external service and activities for the sundry items.

Procedure

1. In Customizing for Controlling, choose Cost Center Accounting Master Data

Activity Types Create Activity Types and create a new activity type for the sundry items.

2. Define a price for the combination of the created activity type and the cost center by

using the transaction Change Activity Output/Prices (KP26) on the SAP Easy Access

screen under Accounting Controlling Cost Center Accounting Planning

Activity Output/Prices Change . For the sundry items, all prices in this transaction should be EUR 0.

The unit of the activity type price needs to be the same as the unit of the pricing reference material from the sundry item.

3. In Customizing for Dealer Business Management (DBM), choose Order Basic

Functions Account Assignment Define Account Assignment for Posting Costs in

Order and enter the required data for the activity type defined in step 1. Assign the material group for sundry items to this activity type.

Example

The following table displays an example of an activity type QEXTER for the sundry items with

the required data in the Customizing activity Define Account Assignment for Posting Costs in Order:

Plnt Matl Group Cost Element Act Typ Cost Center

DBM1 91 None QEXTER WORKSHOP


29 Optional Components


29.1 SAP Incentive and Commission Management Integration Procedure

For related documentation, see DBM ICM Configuration Guide on SAP Service Marketplace

at http://service.sap.com/instguides under Industry Solutions Industry Solutions Guides

SAP for Automotive .

For more information, see SAP Note 1022451.

http://service.sap.com/instguides



29.2 SAP Multi Resource Scheduling Integration Procedure

For more information, see DBM MRS Configuration Guide on SAP Service Marketplace at

http://service.sap.com/instguides under Industry Solutions Industry Solutions Guides

SAP for Automotive .

http://service.sap.com/instguides

SAP Dealer Business Management: Business Scenario and Busine

Documents

Transcript of SAP Dealer Business Management: Business Scenario and Busine