Dbm DEALER BUSINESS MANAGEMENT

SAP Dealer Business Management: Business Scenario andBusiness Process ConfigurationRelease DBM 8.0 SP04

CUSTOMERDocument Version 2.0: 2015-06-24

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

SAP Copyright and Disclaimers

Copyright

© 2015 SAP AG or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may bechanged without prior notice.

SAP and other SAP products and services mentioned herein as well as their respective logosare trademarks or registered trademarks of SAP AG (or an SAP affiliate company) inGermany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors. National product specifications may vary.

These materials are provided by SAP AG or an SAP affiliate company for informationalpurposes only, without representation or warranty of any kind, and SAP AG or its affiliatedcompanies shall not be liable for errors or omissions with respect to the materials. The onlywarranties for SAP AG or SAP affiliate company products and services are those that are setforth in the express warranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additional warranty.

In particular, SAP AG or its affiliated companies have no obligation to pursue any course ofbusiness outlined in this document or any related presentation, or to develop or release anyfunctionality mentioned therein. This document, or any related presentation, and SAP AG’s orits affiliated companies’ strategy and possible future developments, products, and/or platformdirections and functionality are all subject to change and may be changed by SAP AG or itsaffiliated companies at any time for any reason without notice. The information in thisdocument is not a commitment, promise, or legal obligation to deliver any material, code, orfunctionality. All forward-looking statements are subject to various risks and uncertainties thatcould cause actual results to differ materially from expectations. Readers are cautioned not toplace undue reliance on these forward-looking statements, which speak only as of their dates,and they should not be relied upon in making purchasing decisions.

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

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


Important Disclaimers on Legal Aspects

SAP Library document classification: PUBLIC

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

Coding SamplesAny software coding and/or code lines / strings ("Code") included in this documentation areonly examples and are not intended to be used in a productive system environment. TheCode is only intended better explain and visualize the syntax and phrasing rules of certaincoding. 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 ifsuch damages were caused by SAP intentionally or grossly negligent.

Internet HyperlinksThe SAP documentation may contain hyperlinks to the Internet. These hyperlinks areintended to serve as a hint where to find supplementary documentation. SAP does notwarrant the availability and correctness of such supplementary documentation or the ability toserve for a particular purpose. SAP shall not be liable for any damages caused by the use ofsuch documentation unless such damages have been caused by SAP's gross negligence orwillful misconduct.

AccessibilityThe information contained in the SAP Library documentation represents SAP's current view ofaccessibility criteria as of the date of publication; it is in no way intended to be a bindingguideline on how to ensure accessibility of software products. SAP specifically disclaims anyliability with respect to this document and no contractual obligations or commitments areformed either directly or indirectly by this document.

Gender-Neutral LanguageAs far as possible, SAP documentation is gender neutral. Depending on the context, thereader 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 thirdperson singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves theright to use the masculine form of the noun and pronoun. This is to ensure that thedocumentation remains comprehensible.


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

Version Date Status/Change

2.0 2015-06-24 Information added about Maintaining Number Ranges for the DBM Deal andTransaction COM_SE_ADMIN for Business Partner Search

1.0 2015–05–18 Initial


Icons in Body TextIcon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types ofinformation at a glance. For more information, see Help on Help ® General InformationClasses and Information Classes for Business Information Warehouse on the first page of anyversion of SAP Library.

Typographic ConventionsType Style DescriptionExample text Words or characters quoted from the screen. These include field names, screen

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

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

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

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

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

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

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


Table of Contents1 General Information ...................................................................................................... 112 Configuring a Client ...................................................................................................... 143 Defining Field Control for the Loading Group and Transportation Group (HAWA) .......... 154 Enterprise Structure ...................................................................................................... 16

4.1 Defining the Credit Control Area ............................................................................. 174.2 Assigning Organizational Elements ......................................................................... 184.3 Integrating Warehouse Management ...................................................................... 19

5 Logistics General .......................................................................................................... 205.1 Setting Up Conversion Exit for Material Numbers .................................................... 215.2 Defining the Batch Level ......................................................................................... 225.3 Activating Internal Batch Number Assignment ......................................................... 235.4 Processing Number Ranges for Internal Batch Number Assignment ....................... 245.5 Maintaining Company Codes for Materials Management ......................................... 255.6 No Update of MOFF/MSTA Data with Separate Evaluation ..................................... 26

6 Sales and Distribution ................................................................................................... 276.1 Defining Common Distribution Channels and Divisions ........................................... 286.2 Defining Conditions for Value-Added Tax ................................................................ 29

7 Materials Management .................................................................................................. 307.1 Adjusting Movement Types ..................................................................................... 31

8 Dealer Business Management (DBM) ........................................................................... 328.1 Defining an External Manufacturer .......................................................................... 338.2 Assigning an External Manufacturer ........................................................................ 348.3 Maintaining Number Ranges for the DBM Order ..................................................... 35

9 Business Partner Configuration ..................................................................................... 369.1 Prerequisite Settings............................................................................................... 37

9.1.1 Synchronization from Business Partner to Customer ........................................ 399.1.2 Synchronization from Business Partner to Vendor ............................................ 409.1.3 Synchronization from Customer to Business Partner ........................................ 419.1.4 Synchronization from Vendor to Business Partner ............................................ 429.1.5 Define Number Assignment for Direction BP to Customer ................................. 4310.1.6 Define Number Assignment for Direction BP to Vendor................................... 449.1.7 Define Number Assignment for Direction Customer to BP................................. 459.1.8 Define Number Assignment for Direction Vendor to BP .................................... 469.1.9 Business Add-Ins (BAdIs) ................................................................................. 479.1.10 Synchronize Contact Person between Business Partner and Customer .......... 489.1.11 Maintain Collective Billing Field in the BP Transaction .................................... 49

9.2 Synchronization Cockpit ......................................................................................... 509.3 Upgrade Report ...................................................................................................... 519.4 Quick Creation of Business Partner ........................................................................ 52

10 Accounting (Financials, Controlling) ............................................................................ 5410.1 Processing the Controlling Area ............................................................................ 5510.2 Chart of Accounts ................................................................................................. 5610.3 Creating Accounts ................................................................................................ 5710.4 Creating Cost Elements ........................................................................................ 5810.5 Copying the Cost Element Group .......................................................................... 5910.6 Creating a Profit Center ........................................................................................ 6010.7 Creating Cost Centers .......................................................................................... 6110.8 Creating and Assigning an Activity Type and a Price ............................................. 6210.9 Defining Number Ranges for Internal Order Types ................................................ 6310.10 Create Account Assignment Groups for Internal Business Partners ..................... 6410.11 Assign Account Assignment Group to Business Partner ...................................... 6510.12 Assign Account Assignment Group to Material .................................................... 6610.13 Revenue Account Determination ......................................................................... 6710.14 Processing and Activating the Results Area ........................................................ 6810.15 Assigning SD Condition Types to Value Fields .................................................... 6910.16 Defining Account Assignment for Cost Posting in Order ...................................... 7010.17 Defining Internal Order Type for Bill-To Party ...................................................... 71


10.18 Defining Parameters for Settlement Rule ............................................................ 7210.19 Collective Order Control ...................................................................................... 7410.20 Defining Internal Order Account Assignment ....................................................... 7610.21 Internal Order Account Revaluation .................................................................... 8010.22 Release Production Order Immediately ............................................................... 8110.23 Automatic Postings ............................................................................................. 8210.24 Defining Default Values for Cost Object Controlling ............................................. 8310.25 Defining Valuation of Goods Received ................................................................ 8410.26 Defining Profit Center Control ............................................................................. 8510.27 Defining Reports in the Information System......................................................... 8610.28 Field Control Movement Type 261 Account 410000 ............................................ 8710.29 Defining Document Type for Customer Advance Payment (Deposits).................. 8810.30 Defining External Service .................................................................................... 8910.31 Setting Up Profitability Analysis (CO-PA) ............................................................ 90

11 Parts ........................................................................................................................... 9111.1 Creating Spare Parts ............................................................................................ 9211.2 Creating a Sales Price for Spare Parts .................................................................. 9411.3 Search Help for Spare Parts ................................................................................. 9511.4 Exchange Parts .................................................................................................... 96

11.4.1 Setting Up Customizing .................................................................................. 9711.4.2 Setting Up the Material Master ....................................................................... 9811.4.3 Restricting Material Group for Material Search ................................................ 9911.4.4 Assignment of SD Conditions to Value Fields ............................................... 100

12 Service ..................................................................................................................... 10112.1 Defining a Labor Value Catalog .......................................................................... 10212.2 Defining a Hierarchy Level .................................................................................. 10312.3 Determining a Catalog ........................................................................................ 10412.4 Creating a Labor Value Group ............................................................................ 10512.5 Creating a Dummy Material for Labor Value ........................................................ 10612.6 Creating Labor Values ........................................................................................ 10712.7 Creating a Sales Price for Labor Values .............................................................. 10912.8 Defining a Service Package ................................................................................ 11012.9 Creating Customer Advisers ............................................................................... 11112.10 Appointment Scheduling ................................................................................... 112

12.10.1 Defining a Job Catalog ............................................................................... 11312.10.2 Defining a Hierarchy Level .......................................................................... 11412.10.3 Determining a Job Catalog ......................................................................... 11512.10.4 Defining a Workshop Department ............................................................... 11612.10.5 Creating Job IDs ........................................................................................ 117

13 Quality Inspection of Vehicle Service ......................................................................... 11813.1 Setting Up Quality Inspection of Vehicle Service ................................................. 119

14 Service Contracts...................................................................................................... 12014.1 Assigning a Service Item Group .......................................................................... 12114.2 Determining Contract Split Indicator .................................................................... 122

15 Vehicle...................................................................................................................... 12315.1 Assigning an Internal Order Type in the Control Table ........................................ 12415.2 Enhancement Concept (Vehicle) ......................................................................... 12515.3 Vehicle Search with Search Engine TREX .......................................................... 12715.4 Setting Up the RFC Connection .......................................................................... 12815.5 Transaction COM_SE_ADMIN ............................................................................ 12915.6 Creating a Dummy Material for the Vehicle Model ............................................... 13115.7 Creating a Dummy Material for Vehicle Features ................................................ 13315.8 Creating Search-Relevant Customizing ............................................................... 13515.9 Determining the Navigation Profile ...................................................................... 13615.10 Maintaining the Model Catalog .......................................................................... 13715.11 Model Catalog Determination ............................................................................ 13815.12 Creating a Vehicle Model .................................................................................. 13915.13 Assigning Vehicle Model and Users to VMS Roles ............................................ 14015.14 Action Control ................................................................................................... 14115.15 Defining Number Ranges for Internal Vehicle Number....................................... 142


15.16 Maintaining Number Ranges for Vehicle Chain Order Group ............................. 14315.17 Creating a Customer ......................................................................................... 14415.18 Creating a Vehicle and Assigning a Customer ................................................... 14515.19 Mass Vehicle Processing .................................................................................. 146

15.19.1 Enhance the Action Control ........................................................................ 14715.19.2 Enhance VMS Action Technical Details ...................................................... 14815.19.3 Define Bulk Actions .................................................................................... 14915.19.4 Define Vehicle Creation Control Value ........................................................ 15015.19.5 Determine Vehicle Stock Age ..................................................................... 151

15.20 Additional Costs ................................................................................................ 15215.20.1 Define Categories for Additional Costs ....................................................... 15315.20.2 Create Dummy Material for Additional Cost Category ................................. 15415.20.3 Assign Material to Additional Cost Category ............................................... 155

16 Vehicle Sales Assistant ............................................................................................. 15616.1 Maintaining Number Ranges for the DBM Deal ................................................... 15716.2 Assign Notification Types .................................................................................... 15816.3 Define Hierarchy Mapping................................................................................... 15916.4 CRM-DBM Integration......................................................................................... 160

16.4.1 Map CRM Product Category to DBM Technical Item Category...................... 16116.4.2 Map CRM Lead Partner to DBM Deal Partner ............................................... 16216.4.3 Map CRM Lead Partner to DBM Deal Partner ............................................... 16316.4.4 Assign Default Task Code For Notification Type ........................................... 164

16.5 Define Object Control Framework - Event Schema ............................................. 16516.6 Define Automatic Rejection Reason for Quotations ............................................. 16616.7 Define Automatic Rejection Reason for Quotations ............................................. 16716.8 Define Calculation Sheet .................................................................................... 16816.9 Deal Search with Search Engine TREX .............................................................. 16916.10 Transaction COM_SE_ADMIN for Deal Search ................................................. 17016.11 Transaction COM_SE_ADMIN for Business Partner Search ............................. 171

17 Warranty Processing ................................................................................................. 17217.1 Warranty Customizing......................................................................................... 17317.2 Assigning Warranty Claim Item Type – Order Item Category ............................... 17417.3 Editing Warranty Data ......................................................................................... 17517.4 Defining Catalog Code ........................................................................................ 17717.5 Defining Automatic CO Account Assignment Determination ................................ 17817.6 Allowing Change of CO Account Assignments for Condition................................ 17917.7 Defining Warranty Number Range ...................................................................... 18017.8 WTYRCL Customizing ........................................................................................ 18117.9 Defining Recall Priority........................................................................................ 18217.10 Defining Order Type and Warranty Category for Recalls ................................... 18317.11 Assigning Item Type and Item Category to OEM ............................................... 184

18 Cash Desk ................................................................................................................ 18518.1 Setting Characteristics of Document Type SK ..................................................... 18618.2 Defining Business Transactions .......................................................................... 18718.3 Assigning a Number Range to Cash Desk Document Types ............................... 18818.4 Setting Up a Cash Desk Work Center ................................................................. 189

19 Dynamic Sheet ......................................................................................................... 19019.1 Define Style ........................................................................................................ 19119.2 Define Content Object ........................................................................................ 19219.3 Define Content Object Parameters ...................................................................... 193

20 Notification ................................................................................................................ 19420.1 Maintaining Enhancements and BAdI Implementations ....................................... 19520.2 Defining Notification Types for DBM .................................................................... 19620.3 Defining Outcome Type and Outcome Code ....................................................... 19720.4 Assigning Outcome Type to Task Code .............................................................. 19820.5 Assigning Task Code to Order Type ................................................................... 19920.6 Defining Follow-Up Task Code............................................................................ 20020.7 Setting BAdI: Input Help for Outcome Type ......................................................... 20120.8 Setting BAdI: Input Help for Outcome Code ........................................................ 20220.9 Setting BAdI: Input Help for Outcome Code Value .............................................. 203


20.10 Setting BAdI: Filter Text of Outcome Code ........................................................ 20420.11 Configuring E-Mail for Notification ..................................................................... 205

21 Order ........................................................................................................................ 20621.1 Order Search with Search Engine TREX ............................................................. 20721.2 Transaction COM_SE_ADMIN for Order Searches ............................................. 20821.3 Defining Order Search ........................................................................................ 20921.4 Defining Enhanced Order Search........................................................................ 211

21.4.1 Defining BAdI: Enhanced Order Search - UI Enhancement ........................... 21421.4.2 Defining BAdI: Enhanced Order Search - Criteria Enhancement ................... 21521.4.3 Defining BAdI: Enhanced Order Search - Result Enhancement .................... 216

21.5 Up-selling and Cross-selling ............................................................................... 21721.5.1 Define Proposal Type ................................................................................... 21821.5.2 Define Replacement Procedure .................................................................... 219

21.6 Defining a Reason for Rejection .......................................................................... 22021.7 Working with Suborders ...................................................................................... 22121.8 Defining Copying of Order Items ......................................................................... 223

22 Archiving ................................................................................................................... 22522.1 Maintaining Enhancements and BAdI Implementations ....................................... 22622.2 Archiving Control for DBM Order ......................................................................... 227

23 Time Recording ........................................................................................................ 22823.1 Creating Customer Include Fields for Table CATSDB ......................................... 22923.2 Transferring DBM Data to CATS ......................................................................... 23023.3 Setting Up Data Entry Profiles............................................................................. 23423.4 Maintaining HR Master Data ............................................................................... 23523.5 Additional Information ......................................................................................... 236

24 Integration with SAP Credit Management .................................................................. 23724.1 Setting Up the Credit Limit Check ....................................................................... 23824.2 Setting Up the Documented Credit Decision ....................................................... 240

25 Storage Goods Manager ........................................................................................... 24125.1 Creating Required Master Data ........................................................................... 24225.2 Integrating Storage Goods into Memo Pad .......................................................... 24425.3 Defining Number Range for Storage Goods ........................................................ 24525.4 Defining Storage Type for Putaway ..................................................................... 24625.5 Defining Putaway Location.................................................................................. 24725.6 Defining Putaway Bin .......................................................................................... 24825.7 Defining Permitted Storage Type for Putaway for Each Warehouse .................... 24925.8 Defining Wheel Rim Size .................................................................................... 25025.9 Defining Wheel Rim Type ................................................................................... 25125.10 Defining Wheel Rim Manufacturer ..................................................................... 25225.11 Defining Tire Size ............................................................................................. 25325.12 Defining Tire Manufacturer ................................................................................ 25425.13 Defining Standard Position of Storage Goods ................................................... 25525.14 Defining Reminder / Expediting Data................................................................. 25625.15 Defining Status ................................................................................................. 25725.16 Defining Actions ................................................................................................ 25825.17 Defining Action Matrix ....................................................................................... 25925.18 Defining Printout Forms .................................................................................... 26025.19 Defining Condition Tables ................................................................................. 26125.20 Defining Access Sequence ............................................................................... 26225.21 Defining Message Types................................................................................... 26325.22 Defining Message Schema ............................................................................... 264

26 Text Handling............................................................................................................ 26526.1 Defining Criteria Table ........................................................................................ 26626.2 Defining Access Sequences ............................................................................... 26726.3 Defining Control Model Master ............................................................................ 26826.4 Defining Control Vehicle Master .......................................................................... 26926.5 Defining Control Labor Value Master .................................................................. 27026.6 Defining Control Package Master ........................................................................ 27126.7 Defining Control Memo Pad ................................................................................ 27226.8 Defining DBM Order Control ............................................................................... 273


26.9 Defining Storage Goods Control ......................................................................... 27426.10 Defining Rule Key ............................................................................................. 27526.11 Defining BAdI: Definition of Rule ....................................................................... 27626.12 Defining Text Determination Logic Key ............................................................. 27726.13 Defining BAdI: Definition of Text Determination Logic ........................................ 27826.14 Defining Text Handling for Purchase Requisition ............................................... 279

27 Sundry Items in a Fleet Order ................................................................................... 28027.1 Creating Activity Type for Sundry Items .............................................................. 281

28 Optional Components ............................................................................................... 28228.1 SAP Incentive and Commission Management Integration ................................... 28328.2 SAP Multi Resource Scheduling Integration ........................................................ 284


1 General Information

CustomizingAll Customizing (table contents of DBM and ERP tables) which is changed in DBM 800 withrespect to DBM 800 is part of the object list of the DBM 800 installation. All new customizingentries delivered with DBM 800 are included in the BC Sets listed in the following table. TheBC Set /DBM/DBM800_BASIS contains basic settings for all DBM processes. Its activation ismandatory. All other BC Sets only need to be activated if the corresponding process will beused in your system.

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

Function BC Set Description

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

Calculation Sheet /DBM/DBM800_CALC_SHEET Settings for DBM CalculationSheet

Cash Desk /DBM/DBM800_CASHDESK Settings for DBM Cash Desk

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

ProfitabilityAnalysis (CO-PA)

/DBM/DBM800_COPA Settings for CO-PA Integration

Enhanced OrderSearch

/DBM/DBM800_EOS Settings for DBM EnhancedOrder Search

Exchange PartProcess

/DBM/DBM800_EXP Settings for DBM ExchangePart Process

Fleet OrderProcess

/DBM/DBM800_FLEET Settings for DBM Fleet OrderProcess

Notification /DBM/DBM800_NTF Settings for DBM Notification

Order MassProcessing

/DBM/DBM800_OMP Settings for DBM Order MassProcessing

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

Quality Inspection /DBM/DBM800_QUAL_CHECK Settings for DBM QualityInspection

Vehicle ServiceHistory

/DBM/DBM800_SERV_HIST Settings for DBM VehicleService History

Up-selling andCross-selling

/DBM/DBM800_UPS_CRS Settings for DBM Up-selling andCross-selling

Vehicle MassTransaction

/DBM/DBM800_VEH_MASS Settings for DBM Vehicle MassTransaction


Vehicle SalesAssistant

/DBM/DBM800_VSA Settings for DBM Vehicle SalesAssistant

WorkshopController’sCockpit

/DBM/DBM800_WCC Settings for DBM WorkshopController’s Cockpit

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

Function BC Set Description

AppointmentScheduling

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

/DBM/DBM800_APP_SCH Settings for Appointment Scheduling

Incentive andCommissionManagement

/DBM/DBM800_ICM DBM–ICM–specific Customizing

Customizing Adjustments after UpgradeBackground of DBM Customizing Delivery during Upgrade

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

The reasons behind these changes are usually the refinement of processes or architecturalreasons. Note that these Customizing changes in DBM are made for reasons whose ultimateobjective 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 yourexisting Customizing.

The following steps describe this process.

Important Information

Before upgrading or applying a support package, we recommend that you generate a versionfor the current DBM Customizing in order to track any changes. This is beneficial, especiallyin cases where there are new table entries (relevant mainly for Customizing tables withdelivery class G). To generate a version, make the following setting in Customizing for DealerBusiness Management under Framework Components Customizing Versioning ToolsVersion Generator . Alternatively, you can compare the Customizing across your differentsystems, 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 inclient 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 bemade. If you made any changes in the standard Customizing, then it is important toreview the Version Analyzer display.


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

5. You can select a usage in the Version Analyzer, and analyze the correspondingCustomizing 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 seeCustomizing for Dealer Business Management under Framework ComponentsCustomizing 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 aboveinstructions 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 theCustomizing changes accordingly.


2 Configuring a ClientUseYou can use this procedure to create a logical system and make the client settings.

Procedure1. 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, forexample EUR, USD.


3 Defining Field Control for the Loading Group andTransportation Group (HAWA)UseThe two fields MARA-TRAGR and MARC-LADGR, field selection group 94 are defined asrequired entries. Define both fields for the material type HAWA as optional entries. Otherwise,you have to set the entries 0001 and 0001.

Procedure1. 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) indicatorfor the following field references:

o HAWA

o MM01

o MM02


4 Enterprise Structure


4.1 Defining the Credit Control AreaProcedure

1. In Customizing for the Enterprise Structure , choose Definition FinancialAccounting 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 salesdocuments will take place.


4.2 Assigning Organizational ElementsUseTo represent your enterprise structure in the system, you must assign the followingdistribution channels:

· Q1 DBM new vehicles

· Q2 DBM used vehicles

· Q3 DBM service

· Q4 DBM parts sales

ProcedureExecute 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)


4.3 Integrating Warehouse ManagementPrerequisitesThe standard ERP Customizing settings specify that lean Warehouse Management (WHM) isused for plant 0001, storage location 0001. Lean WHM must be deactivated. The standardERP Customizing settings specify entries for WHM usage with warehouse numbers assignedto plants and storage locations. If the DBM delivery process is used without WHM, thestandard ERP delivery Customizing entries for WHM usage must be deleted for the relevantplants and storage locations where the DBM delivery is used.

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

Procedure1. 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 relevantplants and storage locations where the DBM delivery is used without WHM.


5 Logistics General


5.1 Setting Up Conversion Exit for MaterialNumbersUseInstead of the 18-character material number, you can use the 40-character manufacturer partnumber.

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

Procedure1. 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 partnumber 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 exitis not active, you must set the material number display to 18 characters.


5.2 Defining the Batch LevelUseYou require batch management for the vehicle. The batch number is always one, in otherwords, a vehicle.

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

Level and Activate Status Management Batch Level.

2. Select Batch unique at material level.


5.3 Activating Internal Batch Number AssignmentUseWhen a new client is created from a client copy, internal number assignment in the targetclient is not active and must be activated manually.

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

Number Assignment Activate Internal Batch Number Assignment Activate BatchNumber Assignment.

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


5.4 Processing Number Ranges for Internal BatchNumber AssignmentUseIn the standard system, the number range 01 is defined with the interval 0000000001 to9999999999 for the number range object BATCH_CLT.

Procedure1. 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 numberranges.


5.5 Maintaining Company Codes for MaterialsManagementProcedure

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 currentmonth in the field Period.

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


5.6 No Update of MOFF/MSTA Data with SeparateEvaluationProcedureFor better performance, we recommend you set the flag No Update During Split Valuation onthe Administration Data Update screen in the customizing transaction OMT0.


6 Sales and Distribution


6.1 Defining Common Distribution Channels andDivisionsUseA common distribution channel can be assigned to DBM distribution channels for master datacreated for customers and pricing conditions. In this case, you create this master data only forthe reference distribution channel.

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

Distribution Channels.

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


6.2 Defining Conditions for Value-Added TaxProcedure

1. On the SAP Easy Access screen, choose Logistics Logistics Execution DealerBusiness Management Master Data Pricing Condition Create Condition .

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

3. Choose DE Germany in the field RecipCntry (recipient country) and enter thefollowing 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


7 Materials Management


7.1 Adjusting Movement Types

If you plan to use DBM-related movement types for the DBM delivery integration, you have toadjust them. If the DBM delivery process is used, you have to adjust the following movementtypes (which are currently relevant and used in DBM). The changes facilitate goods issuecancellation for DBM deliveries by using transaction VL09.

Procedure1. 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


8 Dealer Business Management (DBM)


8.1 Defining an External ManufacturerUseYou define external manufacturers as original equipment manufacturers (OEM). You requirethe external manufacturer for the assignment of the division, in other words, the vehiclebrand, to the manufacturer.

Procedure1. 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 numberassignment).

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


8.2 Assigning an External ManufacturerUseThe original equipment manufacturer (OEM) has a controlling effect. You can use themanufacturer, for example, to control the interface or determine the labor value catalog.

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

(DBM) Enterprise Structure Assign Divisions to OEMs.

2. Enter a manufacturer for each division.


8.3 Maintaining Number Ranges for the DBMOrderUseTo maintain number ranges for the DBM order, you use the number range object called/DBM/Order.

Procedure1. 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.


9 Business Partner ConfigurationImportant SAP Notes

SAP Note Description

SAP Note1076698

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

SAP Note956054

Customer/vendor integration as of ERP 2005

SAP Note954816

Transactions for creating/linking business partners.

SAP Note941955

Integration of FI customers/vendors with SAP business partner.

SAP Note1076698

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

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


9.1 Prerequisite SettingsProcedureThe following Customizing settings are required for CVI:

Activate Synchronization Options

In Customizing for Cross-Application Components, navigate to Master DataSynchronization Synchronization Control Synchronization Control ActivateSynchronization Options.

You must activate the following replications for synchronization between the business partnerand 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 tocreate business partners for existing customers. The MDS cockpit creates the customer roleand 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 partnersfrom customers and vendors.

In Customizing for Cross-Application Components, navigate to Master DataSynchronization Synchronization of Mass Data Execute Synchronization Cockpit .

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

You can use the transactions below to execute the CVI process for one customer/vendor (forexample, 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 thecustomer to the PPO. After you define the connection, the system writes a postprocessingorder (PPO order) if an error occurs during the synchronization. You can use transactionMDS_PPO2 (Postprocessing Desktop) to call the postprocessing orders. You can use thisfunction to analyze and process errors. You set up the PPO for the synchronization betweenthe business partner and the customer. If an error occurs, there are inconsistent datasets inthe systems until the PPO orders are processed consistently.

If you do not activate the PPO for the master data synchronization between the businesspartner and the customer, the system generates a short dump if an error occurs. The systemdisplays the cause of the synchronization error in the error table LS_ERROR-OBJECTS in thedump / 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 thatyou can analyzed.

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

1. Activate the PPO for the synchronization object BP

In Customizing for Cross-Application Components, navigate to Master DataSynchronization Synchronization Control Synchronization Control Activate PPORequests 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 ApplicationFunctions Postprocessing Office Business Processes Activate Creation ofPostprocessing 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 theCustomizing documentation for the required steps.


9.1.1 Synchronization from Business Partner toCustomerProcedureYou 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 CustomerIntegration → 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


9.1.2 Synchronization from Business Partner toVendorProcedureYou 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 VendorIntegration → 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)


9.1.3 Synchronization from Customer to BusinessPartnerProcedureYou must define business partner roles.

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

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

See the example settings below:

Group BP Role

0001 FLCU00

0001 FLCU01

0005 BUP002

DEBI FLCU00

DEBI FLCU01

KUNA FLCU00

KUNA FLCU01


9.1.4 Synchronization from Vendor to BusinessPartnerProcedureYou must define business partner roles.

In Customizing for Cross-Application Components , navigate to Master Data Synchronization→ Customer/Vendor Integration → Business Partner Settings → Settings for VendorIntegration → 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


9.1.5 Define Number Assignment for Direction BPto CustomerProcedureFor the number assignment from the business partner to the customer and vice versa, youmust 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 CustomerIntegration → Field Assignment for Customer Integration → Assign Keys: Define NumberAssignment 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 theautomatically created SD customer, the same number range must be applied to the businesspartner and to the customer. Navigate to Logistics General → Business Partner → Customers→ Control → Define Account Groups and Field Selection for Customers . The number rangefor 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 anotheraccount group with internal number range assignment. If you want to create customers thathave the same internal number as the related business partner, another account groupaccount group for the business partner with internal number range is needed. The businesspartner’s internal number range should be the same as the customer’s number range, but thecustomer’s should be external.

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

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

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


9.1.6 Define Number Assignment for Direction BPto VendorProcedureFor the number assignment from the business partner to the vendor, and vice versa, youmust 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 VendorIntegration → Field Assignment for Vendor Integration → Assign Keys: Define NumberAssignment 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 samemethod can be applied as described in Define Number Assignment for Direction BP toCustomer.


9.1.7 Define Number Assignment for DirectionCustomer to BPProcedureCustomer account groups are assigned to the business partner groupings relevant for thereplication. Using the related number ranges, the system determines whether the customernumbers are assigned internally or externally, or whether there is number equivalence. Seethe example settings below:

Group Grp. Same No.

0001 0001 No

KUNA 0002 Yes


9.1.8 Define Number Assignment for DirectionVendor to BPProcedureAccount groups of the vendor are assigned to the business partner groupings relevant for thereplication. Using the related number ranges, the determination is made as to whether thevendor 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


9.1.9 Business Add-Ins (BAdIs)ProcedureThe 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. Thedelivered CVI_MAP_BP_CATEGORY implementation returns this title value. A newimplementation of BAdI CVI_MAP_TITLE ( Data Assignment of Form of Address fromCustomer/Vendor to BP ) with name /DBM/CU_CVI_MAP_BP_CATEGORY has been createdwhich should be switched on in Customizing using the Active(IMG) flag. Select BAdI: DataAssignment of Form of Address from Customer/Vendor to BP.


9.1.10 Synchronize Contact Person betweenBusiness Partner and CustomerProcedure

1. In Customizing for Cross-Application Components , navigate to Master DataSynchronization → 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 personrelationship is created for a business partner.


9.1.11 Maintain Collective Billing Field in the BPTransactionProcedureThe following BAdI does not have to be implemented. The structuresCMDS_EI_SALES_DATA and CMDS_EI_SALES_DATAX were enhanced with DBM specificfields. (see append structure /DBM/CMDS_EI_SALES_DATA_A and/DBM/CMDS_EI_SALES_DATAX_A). These structures are used in CMDS_EI_EXTERN. Thefields 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 DATAXappend 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 aregenerated 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.


9.2 Synchronization CockpitProcedureAfter 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 equalto 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 theselection criteria in the cockpit.


9.3 Upgrade ReportProcedureAfter you complete the synchronization process, start the report /DBM/UPDATE_BUPA to fillthe /DBM/VBPA-PARTNER field for the existing DBM orders. This report does not lock anyDBM orders. We therefore recommend that you only run the report when the system is lockedfor 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 notificationtransaction.

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

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


9.4 Quick Creation of Business PartnerProcedureWhen you use transaction BP to create a business partner, you must enter various customerdata. In most cases, the sales data is the same for all business partners. You can use theQuick Creation (QC) process to easily create business partners. In order to create a BP usingthe QC process, reference business partners must be created to get the sales data for thenewly 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 rolesare maintained through the BAdI /DBM/CU_BP_QUICK_ROLES. The organizational dataarea depends on the selected customer role.

Reference Business Partners

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

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

Criteria Tables

Criteria tables are used to determine the reference customer, depending on the selected ormaintained data on the Quick Creation screen. You can create several criteria tables, andcustomize the access control. In each of the criteria tables, you can define several criteriafields.

One master criteria table /DBM/C_CU_BP_001 is delivered in delivery customizing. Thecriteria 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 upthe 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 createdusing transaction BP. The sales and distribution data that is maintained for the referencebusiness partner is copied for the business partner.

Condition Processing

You maintain the records in the criteria table by using transaction /DBM/CU_BP_COND. Youcan insert several combinations of criteria fields with the reference business partner. In theQuick Creation process, the system looks up these tables in the order of the customizedsequence and if the data that entered by the user in the Quick Creation popup is found in thecriteria 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 distributionchannel and 01 for division, then the system selects the partner REF_PER_C as thereference business partner.


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

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

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


10.1 Processing the Controlling AreaUseYou 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.

Procedure1. 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 existingentries.


10.2 Chart of AccountsUseYou can use this procedure to edit the settings for the chart of accounts. The chart ofaccounts 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. Theexample chart of accounts delivered with the SAP System is INT. The following guidelines arebased on the example chart of accounts INT.

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


10.3 Creating AccountsUseG/L account master records contain the data that is always needed by the general ledger todetermine the account's function. The G/L account master records control the posting ofaccounting transactions to G/L accounts and the processing of the posting data. G/L accountsrepresent revenues and costs.

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

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


10.4 Creating Cost ElementsUseYou create primary cost elements to transport costs and revenues to Controlling.

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

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

ProcedureBefore creating Cost Elements, see SAP Note 1003330.

1. On the SAP Easy Access screen, choose Accounting Controlling Cost CenterAccounting 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 (ifnot already available in chart of account INT, if using an own chart of account theaccounts might have a different number).

3. On the SAP Easy Access screen, choose Accounting Controlling Cost CenterAccounting Master Data Cost Element Individual Processing CreateSecondary .

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


10.5 Copying the Cost Element GroupUseCost element group DBM_DB is a DBM template and delivered in client 000. It is used tostructure 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 costelements. Use this structure to collect all relevant cost elements for DBM for easier furthercost analysis in the DBM order. For more information, see Defining Reports in the InformationSystem .

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

Element Accounting Master Data Cost Element Group Change.

2. Choose Extras Copy from Client .


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

Procedure1. 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 ® ProfitCenter ® Define Profit Center.

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


10.7 Creating Cost CentersUseYou use this procedure to create a cost center for the activity allocation posting from the costcenter to the DBM internal order.

Procedure1. 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 .


10.8 Creating and Assigning an Activity Type anda PriceProcedure

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

The labor values are posted from the cost center performing the activity to the DBMorder on the basis of this activity type and price. The activity type and the providing costcenter 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 appropriatecost 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(manualentry, manual allocation).

· In the field Allocation cost elem, choose the appropriate allocation costelement 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 CenterAccounting → Planning → Activity Output/Prices → Change.

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

· Period

· Fiscal Year

· Activity Type

· Cost Center


10.9 Defining Number Ranges for Internal OrderTypesUseThe internal orders assigned to the number ranges (delivered as standard) are already copiedby 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.

Procedure1. 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 headerorder 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 thefollowing 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)


10.10 Create Account Assignment Groups forInternal Business PartnersUseIf working with internal service processes with or without suborder it is necessary to createdifferent account assignments groups for the involved business partner.

Procedure1. In Customizing, choose Sales and Distribution → Basic Functions → Account

Assignment/Costing → Revenue Account Determination → Check Master DataRelevant For Account Assignment .

2. Select Customers: Account Assignment Groups.

3. Enter Account Assignment Group:

· I0 Internal Revenue

· I1 Int Sub Order Rev


10.11 Assign Account Assignment Group toBusiness PartnerUseYou assign the account assignment group to the customer within the customer master datarecord.

Procedure1. 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 Areaunder the tab Billing Document

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


10.12 Assign Account Assignment Group toMaterialUseTo be able to bill materials and labor with a service order, it is necessary to assign theaccount assignment group to the affected materials. This configuration step is necessary forall materials in the service order billing process.

ProcedureOn the SAP Easy Access screen choose Logistics ® Materials Management ® MaterialMaster ® 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 theSales: sales org. 2 tab. In the Account Assignment Group field, enter 02Performances.

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


10.13 Revenue Account DeterminationUseTo find the revenue accounts if billing a DBM order the revenue account determination needsto be maintained.

Procedure1. 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 accountdetermination. If you use a different chart of accounts, sales organization, accountassignment groups (AGG), or cost elements, you must take this into account for theentries 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


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

Procedure1. 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 thetab page Environment . In most cases you will create your own operating concernwith your own characteristics and value fields.

3. In Customizing for Controlling , choose Profitability Analysis ® Flows of ActualValues ® Activate Profitability Analysis to activate the interfaces for CO-PA.


10.15 Assigning SD Condition Types to ValueFieldsUseYou can use this procedure to assign value fields to Profitability Analysis .

Procedure1. 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 vehicledata to value fields.


10.16 Defining Account Assignment for CostPosting in OrderUseYou define for each plant which activity type is used for activity allocation from the workshopcost center to the internal order of the DBM order. You also define which cost center iscredited during this process. You can restrict the selection by specifying the material group aswell as the plant. The material group must be defined in the material that is used for the laborvalue items in the service order. In most cases the cost center will depend on the plant andthe activity type on the material group.

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

® Order ® Account Assignment ® Define Account Assignment for Cost Postings inOrders.

2. Enter the following data:

· Plant

· Material group (labor value = 90)

· Cost element (no information is required for this field)

· Activity type

· Cost center

ExamplePlant Material group Cost element Activity type Cost center

0001 90 MONT WORKSHOP


10.17 Defining Internal Order Type for Bill-ToPartyUseIf the system is customized to create separate internal order for each bill-to party duringinvoicing, do not set the Collective Internal Order indicator in the Customizing settings for theDBM 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 CollectiveOrders.

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

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


· Controlling area

· DBM order type

· Account assignment category (use only in case of internal DBM orderprocesses)

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

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

ExampleControllingArea

DBM OrderType

Account AssignmentCategory

InternalOrder Type

Internal BillingDocument

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


10.18 Defining Parameters for Settlement RuleUseWith 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.

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

® Order ® Account Assignment ® Internal Order for Bill-To Party ® DefineParameters 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 characteristicsto the communication structure /DBM/CO_IO_COM)

ExampleDBMOrderType

OperatingConcern

Characteristic SourceStructure

SourceAssignment

DBMOrder

2000 S001 KNDNR Q1 1 KUNNR


2000 S001 VTWEG Q1 1 VTWEG


2003 S001 KNDNR Q1 1 KNDNR











10.19 Collective Order ControlUseTo model dealer processes, additional objects were developed on the basis of ERP. One ofthese key /DBM/objects is the DBM order. A display transaction has been developed for thefollowing 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 usersdo not have to manage and track these costs themselves. The DBM order and the internalorder are linked. When the invoice is created, all cost and revenue collected on this level isreposted 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. Whenan invoice is created in the background for every bill-to party and, depending on theCustomizing settings, an additional internal order is created. This means that an internal orderalso exists for every bill-to party. When invoicing takes place, the system posts the revenuesand costs to these bill-to party internal orders according to the split values. If you wish, youcan use Customizing settings in the DBM order to determine that a separate internal order isnot created for each bill-to party, but rather the costs and revenue are posted to theappropriate collective internal orders according to the Customizing settings, for example, inaccordance 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 thecosts and revenue to a collective order when invoicing takes place and the costs and revenuecan then be forwarded to and settled using Profitability Analysis (CO-PA). The collective orderthat 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 accesssequences.

· Assign Internal Order

Procedure1. 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 .

4. In Customizing for Logistics Execution , choose Dealer Business Management(DBM) Order Account Assignment Internal Order for Bill-To Party CollectiveInternal Order Control Define Table of Criteria .

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


6. In Customizing for Logistics Execution , choose Dealer Business Management(DBM) Order Account Assignment Internal Order for Bill-To Party CollectiveInternal Order Control Define Access Sequences .

7. Ensure you can use the standard access sequences.

8. In Customizing for Logistics Execution , choose Dealer Business Management(DBM) Order Account Assignment Internal Order for Bill-To Party CollectiveInternal 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)

ExampleControllingArea

DBM OrderType

Account AssignmentCategory

WarrantyCategory

Order

0001 2000 DBM_COLLECT


10.20 Defining Internal Order AccountAssignmentUseYou 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 assignmentobject is debited, for example, internal order or cost center. The account assignmentcategory, which is found in the internal service orders, is determined with the following criteriatechnique:

· 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 accesssequences.

· Assign Account Assignment Object for Internal Order


(DBM) Order Account Assignment Internal Order Account Assignment DefineAccount Assignment Categories for Internal Order . Ensure you can use thestandard account assignment categories provided by delivery customizing.

2. In Customizing for Logistics Execution , choose Dealer Business Management(DBM) Order Account Assignment Internal Order Account Assignment DefineTable of Criteria .

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

3. In Customizing for Logistics Execution , choose Dealer Business Management(DBM) Order Account Assignment Internal Order Account Assignment DefineAccess Sequences .

Ensure you can use the standard access sequences provided by deliverycustomizing.

4. In Customizing for Logistics Execution , choose Dealer Business Management(DBM) Order Account Assignment Internal Order Account Assignment AssignAccount 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 determinethe vehicle internal order)


ExampleCOArea

SOrg Plant OrderType

AAC No. Chg. Cost Ctr. CostEl.

Int.Order

Bill-ToParty

FunctionModule

0001 0001 0001 2003 25 1 X CustwithAAGI0

0001 0001 0001 2103 25 1 X CustwithAAGI0

0001 0001 0001 4000 01 1 X Workshop CustwithAAGI0

0001 0001 0001 4000 02 1 Workshop 600200 CustwithAAGI0

0001 0001 0001 4000 10 X CustwithAAGI0

/DBM/CO_ INT _GET_VEHICLE

0001 0001 0001 4000 11 CustwithAAGI0


0001 0001 0001 4100 01 X Workshop CustwithAAGI0

0001 0001 0001 4100 02 Workshop 600200 CustwithAAGI0

0001 0001 0001 4100 10 X CustwithAAGI0


0001 0001 0001 4100 11 CustwithAAGI0



0001 0001 0001 4100 10 1 CustwithAAGI0


0001 0001 0001 4100 11 1 X CustwithAAGI0


0001 0001 0001 4101 10 1 CustwithAAGI0


0001 0001 0001 4101 11 1 X CustwithAAGI0


0001 0001 0001 7000 70 1 X CustwithAAGI1

/DBM/CO_ INT _GET_HEADER_INTORD


10.21 Internal Order Account RevaluationUseYou 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.


(DBM) Order Account Assignment Internal Order Revaluation Define OrderType 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 COproduction order)

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

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

ExampleDBM OrderType

CO ProductionOrder

Cost Element MovementType

MovementType

4100 CP01 use your own costelement

261 101

4101 CP01 use your own costelement

261 101

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


10.22 Release Production Order ImmediatelyUseThis setting is necessary to release the CO production order for the revaluation processimmediately after creation.

Procedure1. 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 settingoverview.

3. Check value Release Immediately.


10.23 Automatic PostingsUseTo post FI and CO relevant goods issue postings automatically, in case of a materialconsumption, the following configuration is necessary.

Procedure1. 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 correspondingvaluation class (3100)

5. Enter the following configuration:

o 0001 AUF 3100 895000 895000


10.24 Defining Default Values for Cost ObjectControlling

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

Procedure1. 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.


10.25 Defining Valuation of Goods Received

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

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

Valuation of Goods Received .

2. Check if all your plants are defined.


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

· Define Table of Criteria

You can use the existing criteria table.


You can use the existing access sequences.

· Assign Profit Center


(DBM) Order Account Assignment Profit Center Control Define Table ofCriteria .

2. Ensure you can use the standard criteria table.

3. In Customizing for Logistics Execution , choose Dealer Business Management(DBM) Order Account Assignment Profit Center Control Define AccessSequences .

4. Ensure you can use the standard access sequences.

5. In Customizing for Logistics Execution , choose Dealer Business Management(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

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

0001 Q3 01 01 Workshop


10.27 Defining Reports in the Information SystemUseYou define your own report for cost analysis if you decide not to use the standard DBMtemplate. To display the report, choose Goto Cost Analysis .

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

ProcedureIn Customizing for Dealer Business Management (DBM), see Order Basic FunctionsAccount Assignment Cost Analysis Define Report Parameters for Cost Analysis .


10.28 Field Control Movement Type 261 Account410000Procedure

1. In Customizing for Materials Management , choose Inventory Management andPhysical 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.


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

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

Global Settings (New) Document Document Types Define Document Types forEntry View .

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

3. In Customizing for Logistics Execution, choose Dealer Business Management(DBM) Order Basic Functions Account Assignment Specify Document Type forCustomer Advance Payment .

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

5. In Customizing for Logistics Execution, choose Dealer Business Management(DBM) Cash Desk Define Business Transaction .

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

o CD BT: 99, for example

o Description: Customer Advance Payment

7. In Customizing for Logistics Execution, choose Dealer Business Management(DBM) Cash Desk Define Document Type .

8. Choose New Entries and create a new cash document category (CD Cat.) with thefollowing 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

9. In Customizing for Logistics Execution, choose Dealer Business Management(DBM) Cash Desk Define Cash Desk Work Center .

10. Select the cash desk work center that is allowed to work with customer advancepayments 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


10.30 Defining External ServiceProcedureFor more information, see SAP Note 1040943.


10.31 Setting Up Profitability Analysis (CO-PA)ProcedureSee SAP Note 2092713 and the cookbook attached to it.

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

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

· Relevant business partner data (such as general BP data or address) from theDBM 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-specifictables. The SAP Note mentioned above provides more details.

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


11 Parts


11.1 Creating Spare PartsUseThe 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 severalbrands. The dealer works with just a subset of the entire parts range to handleparts sales and service. These parts are also fully maintained in the SAPsystem.

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 completemaster 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 shouldbe maintained for DBM order follow up processes ( for example, procurement and SD billingdocuments).

Field Data Description

Material Type HAWA Trading goods

Properties copied from HAWA

Industry Sector M

Material Group Customer and brand-specific settings possible

General ItemCategory Group

NORM Normal SAP standard item

Checking Group forAvailability Check

Customer-specific setting

Procurement type F External:

supplied by manufacturer

Materials planning(MRP)

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

For inventory-managed materials from other vendors, suchas tires (for example, summer and winter tires) andaccessories, you can use SAP MRP and materials planningfunctions

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

Transportationgroup

Loading group

0001 Delivery functions are not currently integrated into the DBMorder,

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

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

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

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

Material Master Assign Screen Sequences to User/MaterialType/Transaction/Industry Sector .

2. Set the screen sequence to A1 .


11.2 Creating a Sales Price for Spare PartsProcedure

1. On the SAP Easy Access screen, choose Logistics Logistics Execution DealerBusiness Management Master Data Pricing Condition Create Condition .

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


11.3 Search Help for Spare PartsUseOnly spare parts are meaningful in the search result for materials in the order. The highnumber of dummy materials, for example, for vehicle models, labor values (LVs), vehiclefeatures, and so on, can thus be filtered out. The filter is based on the material group.

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

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Part Assign Material Type for Spare Part.


11.4 Exchange Parts


11.4.1 Setting Up Customizing

To use the exchange part process, you have to activate BC Set /DBM/DBM800_EXP. This BCSet contains the following necessary Customizing settings:

· Technical item category

· Item copy control

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


11.4.2 Setting Up the Material Master

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

Procedure1. Start transaction /DBM/MMXX.

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

More InformationSAP Library for Dealer Business Management on SAP Help Portal at http://help.sap.comSAP for Industries SAP for Automotive Dealer Business Management <release>,<language> Parts Management Order Processing Exchange Parts .

http://help.sap.com/


11.4.3 Restricting Material Group for MaterialSearch

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


(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).


11.4.4 Assignment of SD Conditions to ValueFields

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

Procedure1. Call transaction KE4I.

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


12 Service


12.1 Defining a Labor Value CatalogProcedure

1. In Customizing for Logistics Execution , choose Dealer Business Management(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 valuecatalog 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 thesame OEM, the settings must be the same for each catalog.


12.2 Defining a Hierarchy LevelProcedure

1. In Customizing for Logistics Execution, choose Dealer Business Management(DBM) Service Labor Value Define Hierarchy Level .

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


12.3 Determining a Catalog

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


(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 youenter the sequence number with different values.


12.4 Creating a Labor Value GroupProcedure

1. On the SAP Easy Access screen choose Logistics Logistics Execution DealerBusiness Management Master Data Labor Value Edit Labor Value Group.

2. Define values for the labor value group.

Example· 01 Mechanics

· 02 Electricity

· 03 Painting


12.5 Creating a Dummy Material for Labor Value

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

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

Business Management Master Data Part Create Material - DBM .


Field Data Description

Material Type DIEN Service

Industry Sector M Mechanical engineering

Material Group Defaultvalue 90

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

Base Unit ofMeasurement

Defaultvalue: min

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

General ItemCategory Group

LEIS From the material type


12.6 Creating Labor ValuesUseManufacturers create catalogs (for example, labor value catalog and local OEM system) forwork performed on the vehicle. The labor values (LVs) consist of a description and apredefined time.

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

PrerequisitesIn 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


Business Management Master Data Labor Value Edit Labor Value Group .

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

3. On the SAP Easy Access screen, choose Logistics Logistics Execution DealerBusiness 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 laborvalue is entered more than once in the service order. This is useful, for example, withthe labor value for installing and de-installing the motor since a vehicle usually onlyhas one motor.


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

9. Assign the dummy material.

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


12.7 Creating a Sales Price for Labor ValuesUseThe sales price is defined via the reference material (allocation material) and the appropriatecondition.


Business Management Master Data Pricing Condition Create Condition .

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


12.8 Defining a Service PackageUseA service package can consist of different items; for example, n labor values, n parts, and ntexts. The manufacturer usually supplies this information in the form of a catalog (local OEMsystem). However, the dealer can also create its own packages.

The package master is a DBM object.


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

2. Define number ranges for package types.

3. In Customizing for Logistics Execution , choose Dealer Business Management(DBM) Service Package Define Package Variant Type.

4. Define variant selection field for variant type.

5. In Customizing for Logistics Execution , choose Dealer Business Management(DBM) Service Package Define Material Type for Parts Package .

6. Enter the material types.

7. In Customizing for Logistics Execution , choose Dealer Business Management(DBM) Service Package Generate Selection Options for Customer Fields .

8. Generate selection options for customer fields.

9. On the SAP Easy Access screen, choose Logistics Logistics Execution DealerBusiness 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


12.9 Creating Customer AdvisersUseIn 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.

Procedure1. 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


12.10 Appointment Scheduling


12.10.1 Defining a Job CatalogProcedure

1. In Customizing for Logistics Execution, choose Dealer Business Management(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


12.10.2 Defining a Hierarchy LevelProcedure

1. In Customizing for Logistics Execution, choose Dealer Business Management(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 musthave the same hierarchy levels.


12.10.3 Determining a Job Catalog

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


Service Workshop Scheduling Job Catalog Catalog Determination AssignCriteria .

2. Assign the criteria.


12.10.4 Defining a Workshop DepartmentProcedure

1. On the SAP Easy Access screen, choose Logistics Logistics Execution DealerBusiness Management Master Data Workshop Scheduling Define WorkshopDepartment (Labor Value Group) .

2. Define values for the labor value group.

Example· 01 – Mechanic

· 02 – Electric

· 03 – Paint Shop


12.10.5 Creating Job IDs

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

The job ID is used in the service order.

PrerequisitesIn 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 + countryAT finds catalog 5


Business Management Master Data Workshop Scheduling Job CatalogsMaintain 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 appointmentusing the job ID the package is assigned to, the system will add all the itemsmaintained in the package to the service order.

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


13 Quality Inspection of Vehicle Service


13.1 Setting Up Quality Inspection of VehicleServicePrerequisites

· 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 forQuality Management under Quality Inspection Inspection Lot Creation MaintainInspection Types . Inspection type 89_DBM is provided in the BC set as anexample.

· You have checked the settings in Customizing for Dealer Business Management(DBM) under Service Quality Inspection .

Procedure1. 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 materialmaster. In the inspection setup, you specify that you want inspections to be carriedout for this material. For more information, see SAP Library on the SAP Help Portal athttp://help.sap.com/erp. Under Application Help, open SAP Library and choose

SAP ERP Central Component Logistics Quality Management (QM) QualityPlanning (QM-PT) Basic Data (QM-PT-BD) QM-Specific Data in the MaterialMaster (QM-PT-BD-MM) Creating and Changing QM Data for a Material Editingthe Inspection Setup .

2. On the SAP Easy Access screen under Dealer Business Management MasterData Quality Inspection , you create the necessary master data and assign thematerial (vehicle model) and plant to the inspection plans. With this assignment, youcan have the materials (vehicle models) included in or excluded from specialinspections in specific plants. For more information about inspection plans andinspection characteristics, see SAP Library on the SAP Help Portal athttp://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 MasterData Quality Inspection Determine Quality Inspection Plan

(/DBM/QMI_I_PLAN), you assign an inspection plan (Group field) and a groupcounter. You can assign more than one inspection plan and group counter. Byentering a date, you define that the inspections should be done within a certain timeframe.

http://help.sap.com/erp

http://help.sap.com/erp


14 Service Contracts

The contract item materials in a DBM service contract should only be of material type Service(DIEN); otherwise errors can occur.


14.1 Assigning a Service Item Group

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


(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 serviceitem 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 underthe contract item details on the DBM Data tab page where the coverage andpercentages are defined.


14.2 Determining Contract Split Indicator

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


Business Management Master Data Contract Edit Contract Split Indicator .

2. Define one contract split indicator for the order type 2003 (Service Contract ReleaseOrder) and one for the order type 2103 (Service Contract Release Order Returns)with the following values:

SplitIndicator

Description OrderType

Customer AccountAssignmentCategory

Behavior ofSAP CreditManagement

CONTRACT1 SerContrReleaseOrder 2003 AAG IO 25 ConsidersEntire JobAmount(StandardBehavior)

CONTRACT2 SerContrReleaseOrderReturns 2103 AAG IO 25 ConsidersEntire JobAmount(StandardBehavior)

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

4. On the SAP Easy Access screen, choose Logistics Logistics Execution DealerBusiness Management Master Data Contract Change Conditions forDetermining Contract Split Ind. .

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

Order Type Split Indicator

2000 CONTRACT1

2103 CONTRACT2


15 VehicleThe 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 ExecutionVehicle Management System

· Implementation Guide (IMG) for Logistics Execution under Vehicle ManagementSystem (VMS)


15.1 Assigning an Internal Order Type in theControl TableUseFor vehicle processing, an internal order is also used to handle the value flow. The user doesnot to have to manage this internal order.

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


(DBM) Vehicle Enter Control Value.

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


15.2 Enhancement Concept (Vehicle)UseTo fulfill the requirements of a Dealer Business Management system, the vehicle object fromthe Vehicle Management System (VMS) had to be extended. This was carried out on thebasis 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 SAPProduct

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

Procedure1. 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 thesame text as description.

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

3. Choose New Category , enter the category ID DBM_VEHICLE with the sametext as description and leave the indicator for the product/object assignmentblank.

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

5. Enter the category ID DBM_PASSENGERCAR with the same text asdescription.

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 ProductCategory Assign Catalog Hierarchies to Applications. The category hierarchycreated in transaction COMM_HIERARCHY has to be assigned to an application inCustomizing.

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


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

6. Also in transaction COMM_HIERARCHY Maintain Categories and Hierarchies , onthe tab page Set Types, you assign set types by placing the cursor onDBM_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 Settingsfor Product Type Number Assignment Define Number Ranges for the ProductType "Material".

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

Refer also to SAP Notes 903914 (DBM: Technical Documentation on Vehicle Process) and900850 (DBM: Technical Documentation for Vehicle Data Enhancements) for enhancementcookbooks.


15.3 Vehicle Search with Search Engine TREXUseThe vehicle search function in Dealer Business Management (DBM) is based on TREX.TREX can be installed in the same server as DBM for test or evaluation purposes. Systemprerequisites are SAP Netweaver 7.0, TREX 7.0, Version 39. In order to be able to use thesearch functionalities in DBM you must have TREX installed and configured.

You can find further information about the installation of TREX on the SAP ServiceMarketplace under service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.0(2004s) Installation Installation – Standalone Engines SAP NetWeaver Search andClassification TREX .

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


15.4 Setting Up the RFC ConnectionProcedure

1. On the SAP Easy Access screen, choose Tools Administration AdministrationNetwork 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 defaultsetting for character conversion.

If TREX is installed on the same server as DBM, for example for test orevaluation purposes, make the following entries from the SAP Easy Accessscreen by choosing Tools Administration Administration NetworkRFC 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 indicatedin the TREX installation document

§ IP address

§ Enter gateway host and gateway service


15.5 Transaction COM_SE_ADMINProcedure

1. Enter transaction code COM_SE_ADMIN and then choose Goto CustomizingSystem Settings Change New Entries .


o RFC Destination (default value TREXDEFAULT_REG)

o Search Engine: CL_COM_SE_TREX

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 VEHICLEwith class /DBM/CL_SE_VEHICLE.

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

7. From the Search Engine Service Administration screen, choose IndexCreate/Activate Indexes .

8. Choose the entry VEHICLE and start the indexing.

9. Choose Goto Customizing Business Objects and Indexes .

10. Choose Settings for Business Object and enter the business object DBMMODEL withclass /DBM/CL_SE_MODELSEARCH.

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

12. From the Search Engine Service Administration screen, choose IndexCreate/Activate Indexes .

13. Choose the entry DBMMODEL and start the indexing.

14. To plan a recurring job for the delta load, choose System Services Jobs JobDefinition .

15. Choose Step ABAP Program and execute report COM_SE_DISPATCHERwithout a variant.


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 beupdated and how often the vehicle data is changed.


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


15.6 Creating a Dummy Material for the VehicleModelUseYou create the following data:

· Material

· Class

· Configuration Profile

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

ProcedureFor Class

1. From the SAP Easy Access screen, choose Cross-Application ComponentsClassification 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 followingdata:

o Data type: CHAR

o Number of chars: 3

o Dummy value

For Material

1. On the SAP Easy Access screen, choose Logistics Logistics Execution DealerBusiness 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 itemcategory group 0002 (configuration).

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

7. In the Purchasing view, set the indicator for batch management requirement andenter the manufacturer. You can only enter it if the setting Use Manufacturer No isenabled 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 ProcessProcess Order Environment Master Data Material Master EnvironmentConfiguration 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 inSAP Note 1258776 (Smart Usage of Material Master for Vehicle Models). Information abouthow to enhance the DBM model master is provided in SAP Note 929089 (DBM: TechnicalDocumentation on Model Master).


15.7 Creating a Dummy Material for VehicleFeaturesUseStandard features and optional extras are defined during configuration in the manufacturersystem. 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 accessoriesto the vehicle. Accessories can be inventory-managed materials or manual parts.


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 categorygroup NLAG

§ MRP 1 : MRP characteristic ND (no MRP)

§ MRP 2: procurement type P

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


15.8 Creating Search-Relevant CustomizingProcedureYou need to maintain standard VMS customizing to search for vehicles of particular models.

1. On the SAP Easy Access screen, choose Logistics Logistics Execution VehicleManagement System Basic Data VMS Roles Assign Vehicle Model .

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

3. On the SAP Easy Access screen, choose Logistics Logistics Execution VehicleManagement 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.


15.9 Determining the Navigation ProfileUseIf you want to create a vehicle, you must maintain Customizing settings for the determinationof the navigation profile.


(DBM) Vehicle Navigation in Vehicle Master Navigation Profile DeterminationAssign 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)


15.10 Maintaining the Model CatalogProcedure

1. In Customizing for Logistics Execution , choose Dealer Business Management(DBM) Vehicle Vehicle Model Master Process Model Catalog.

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


15.11 Model Catalog DeterminationProcedure

1. In Customizing for Logistics Execution , choose Dealer Business Management(DBM) Vehicle Vehicle Model Master Model Catalog Determination DefineAccess Sequences.

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

3. In Customizing for Logistics Execution , choose Dealer Business Management(DBM) Vehicle Vehicle Model Master Model Catalog Determination AssignModel Catalog.

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


15.12 Creating a Vehicle ModelProcedure

1. On the SAP Easy Access screen, choose Logistics Logistics Execution DealerBusiness 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 themodel.

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.

3. On the SAP Easy Access screen, choose Logistics Logistics Execution DealerBusiness Management Master Data Vehicle Model Edit Body Type .

CAB Convertible , KOM Station Wagon etc.

4. On the SAP Easy Access screen, choose Logistics Logistics Execution DealerBusiness Management Master Data Vehicle Model Edit Vehicle Type .

PKW Passenger Car

5. On the SAP Easy Access screen, choose Logistics Logistics Execution DealerBusiness Management Master Data Vehicle Model Edit Fuel Type .

Diesel, Gasoline

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

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


15.13 Assigning Vehicle Model and Users to VMSRolesProcedure

1. On the SAP Easy Access screen, choose Logistics Logistics Execution VehicleManagement System Basic Data VMS Roles Assign Vehicle Model.

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

3. On the SAP Easy Access screen, choose Logistics Logistics Execution VehicleManagement 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.


15.14 Action ControlUseYou execute the following for action control:

· Define number range for action control

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

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

Procedure1. 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.

3. In Customizing, choose Logistics Execution Vehicle Management System (VMS) Control Data Define Action Controls and Define Action Matrices.

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

5. On the SAP Easy Access screen, choose Logistics Logistics Execution VehicleManagement System Basic Data Define Action Control Determination.

6. Define the action control determination.


15.15 Defining Number Ranges for InternalVehicle NumberProcedure

1. In Customizing, choose Logistics Execution Vehicle Management System (VMS) Number Ranges Determine Number Ranges for Internal Vehicle Number .

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


15.16 Maintaining Number Ranges for VehicleChain Order GroupUseThe number range object is called /DBM/OG .


(DBM) Vehicle Vehicle Master Define Number Range for Vehicle Chain OrderGroup .To have this customizing node, implement SAP Note 1042653, or you can maintainthe number range object directly with transaction SNRO .

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


15.17 Creating a CustomerUseThe standard system forms the basis for the Dealer Business Management (DBM) customermaster. The following changes and additions have been made:

· Simplified user interface

· Simplified navigation

· Aggregated display

ProcedureOn the SAP Easy Access screen, choose Logistics Logistics Execution DealerBusiness Management Master Data Customer Business Partner Cockpit

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


15.18 Creating a Vehicle and Assigning aCustomerProcedure

1. On the SAP Easy Access screen, choose Logistics Logistics Execution DealerBusiness 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 reportCOM_PRODUCT_UPGRADE’, you must execute the report. You can find informationabout how to execute the report in the report documentation (SE38 → Goto →Documentation ). In addition, check SAP Note 906042. Generally, you only executethis 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 insystem 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 therelevant systems before you execute the report. It is possible that the transportrequest remains empty after the report has been executed. Refer to SAP Note1055794 for more information about this issue.

6. Choose Actions .

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

8. Save your entries.


15.19 Mass Vehicle Processing


15.19.1 Enhance the Action Control

You execute the following for action control:

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

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


Control Data Define Action Controls and Define Action Matrices .


3. On the SAP Easy Access screen, choose Logistics Logistics Execution VehicleManagement System (VMS) Basic Data Define Action Control Determination .

4. Define the action control determination.


15.19.2 Enhance VMS Action Technical Details

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


Enhancements Define Technical Details for Actions .


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


15.19.3 Define Bulk Actions

You use this procedure to enable actions to be applicable for a set of vehicles in the MassVehicle Processing function (transaction /DBM/MASSACTIONS).

Procedure1. 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.


15.19.4 Define Vehicle Creation Control Value

You use this procedure to define which actions must be executed on vehicles in the MassVehicle Processing function (transaction /DBM/MASSACTIONS).


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.


15.19.5 Determine Vehicle Stock Age

This setting defines the actions to be performed on vehicles to determine their stock age.


Vehicle Define Control Values Define Sales Control Value .

2. Add new actions or change existing ones, as required.


15.20 Additional Costs


15.20.1 Define Categories for Additional Costs

In this Customizing activity, you define the different categories of additional costs that canincur from a third party, such as transportation, maintenance, or insurance costs.

You can post or cancel additional vehicle costs only using the Mass VehicleProcessing transaction. Standard SAP ERP transactions (such as those used forpurchase orders, goods receipts, and invoices) do not support posting or cancellationof additional vehicle costs.


(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.



15.20.2 Create Dummy Material for AdditionalCost CategoryProcedure

1. On the SAP Easy Access screen, choose Logistics Logistics Execution DealerBusiness 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-stockmaterials) or LEIS (services without delivery).

4. Save the material.


15.20.3 Assign Material to Additional CostCategoryProcedure

1. On the SAP Easy Access screen, choose Logistics Logistics Execution DealerBusiness Management (DBM) Master Data Additional Costs Assign Material toAdditional 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 isvalid.



16 Vehicle Sales Assistant


16.1 Maintaining Number Ranges for the DBMDealUseTo maintain number ranges for the DBM deal, you use the number range object called/DBM/Deal.


16.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 vehiclesales assistant (VSA).

· Define the notification type task that must be displayed in the Activities Today area ofthe VSA home screen.

The notification type is determined by the control code assigned, for example, fleet order.

Procedure1. 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. Thistask code is used to identify whether the activity is related to test drives, andpopulates additional fields to capture relevant data on the VSA interface.

4. If there are multiple control codes defined, all the corresponding notification tasks willbe available in the Activities Today area of the VSA home screen.


16.3 Define Hierarchy Mapping

Using this procedure, you define hierarchy mapping based on which the order items aredisplayed hierarchically in the user interface for a deal.

While order items (that is to say, either item categories or features classes) are displayed inthe UI, these are segregated into different hierarchy elements based on their mapping. Thenbased on which hierarchy elements are mapped to that particular order type, order items aredisplayed in the UI.

ProcedureIn Customizing, go to Logistics Execution Dealer Business Management (DBM) VehicleSales UI Control Define Hierarchy Mapping .


16.4 CRM-DBM Integration

If there is an external system connected where sales leads are created for processing in SAPDBM, there are settings that need to be defined. For more information on how to set up thesystem to support external systems, refer to SAP Note 1964300.



16.4.1 Map CRM Product Category to DBMTechnical Item Category

In this Customizing activity, you can map the CRM product category to the SAP DBMtechnical item category.

When a CRM lead is transferred to the SAP DBM system, the CRM products attached to thislead are identified as parts, packages, or models in the SAP DBM system based on thismapping.

ProcedureIn Customizing, go to Logistics Execution Dealer Business Management (DBM) VehicleSales CRM-DBM Integration Map CRM Product Category to DBM Technical ItemCategory and maintain necessary entries.


16.4.2 Map CRM Lead Partner to DBM DealPartner

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 transferredfrom a CRM system, you need to identify a main partner from all the businesspartners associated with that lead.

The CRM partner whose partner function is defined as the main partner will beidentified as the customer for the SAP DBM deal.

ProcedureIn Customizing, go to Logistics Execution Dealer Business Management (DBM) VehicleSales CRM-DBM Integration Map CRM Lead Partner to DBM Deal Partner and maintainnecessary entries.


16.4.3 Map CRM Lead Source to DBM NotificationSourceIn this Customizing activity, you can map the CRM lead source to the SAP DBM notificationsource.

When a CRM lead is transferred to the SAP DBM system, a DBM notification source codecorresponding 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 catalogdefined 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 -> NotificationContent -> Maintain Catalogs -> Edit Catalogs.

ProcedureIn Customizing, go to Logistics Execution Dealer Business Management (DBM) VehicleSales CRM-DBM Integration Map CRM Lead Source to DBM Notification Source andmaintain necessary entries.


16.4.4 Assign Default Task Code For NotificationType

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 dependingon its type.

ProcedureIn Customizing, go to Logistics Execution Dealer Business Management (DBM) VehicleSales CRM-DBM Integration Assign Default Task Code for Notification Type andmaintain necessary entries.


16.5 Define Object Control Framework - EventSchemaIn this Customizing activity, you create event schemas to group certain events together. Youcan execute only those events that are listed within the defined schemas.

ProcedureIn Customizing, go to Logistics Execution Dealer Business Management (DBM)Framework Components Object Control Framework - Event Schema .


16.6 Define Automatic Rejection Reason forQuotationsIn this Customizing activity, you can define the reason for automatic rejection of alternativequotations whenever an order is created from a specific quotation.

Let us assume that there are three quotations existing for a customer requirement. If youselect one of these quotations and create an order from it, the other two quotations areautomatically rejected and assigned the reason defined here.

ProcedureIn Customizing, go to Logistics Execution Dealer Business Management (DBM) VehicleSales Deal Define Automatic Rejection Reason for Quotations . Select a rejection reasonfrom the menu options and save the change.


16.7 Assign Rejection ReasonIn this IMG activity you can assign rejection reasons defined in SAP ERP to objects within thevehicle 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 aredisplayed by default.

ProcedureIn Customizing, go to Logistics Execution Dealer Business Management (DBM) VehicleSales UI Control Assign Rejection Reason . Assign a rejection reason to the relevantDBM object.


16.8 Define Calculation SheetUsing the Calculation Sheet function, you can summarize the revenue, discount, and costvalues for all vehicles (including trade-in vehicles) that are part of the order. You can therebycalculate the profit made on each order. The layout of the calculation sheet is flexible and canbe changed in SAP DBM Customizing. For example, you may at times want to ascertain thecalculated profitability (including costs); you could later decide that the cost information mustnot be shown and that only the overall discount should be displayed.

ProcedureUse the Customizing activities and BAdIs under Logistics Execution Dealer BusinessManagement (DBM) Vehicle Sales Calculation Sheet to define groups, cell types, andschema for the calculation sheet.


16.9 Deal Search with Search Engine TREXUseThe Deal Search function in Dealer Business Management (DBM) is based on TREX. TREXcan be installed in the same server as DBM for test or evaluation purposes. Systemprerequisites are SAP Netweaver 7.0, TREX 7.0, Version 39. In order to be able to use thesearch functionalities in DBM you must have TREX installed and configured.

ProcedureYou can find more information about the installation of TREX on the SAP Service Marketplaceunder http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.0 (2004s) Installation Installation – Standalone Engines SAP NetWeaver Search and ClassificationTREX.

For information on how to define the RFC connection, see Setting Up the RFC Connection[Page 126].

http://service.sap.com/instguides


16.10 Transaction COM_SE_ADMIN for DealSearchProcedure

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


5. Choose Settings for Business Object and enter the business object DBMDEAL withclass /DBM/CL_SE_DEALSEARCH.


7. From the Search Engine Service Administration screen, choose Index Create/Activate Indexes for Object Type 1 of object DBMDEAL. This will beavailable through BC set /DBM/DBM800_VSA.

8. Choose the entry DBMDEAL and start the indexing (full).


16.11 Transaction COM_SE_ADMIN for BusinessPartner SearchProcedure

1. Enter transaction code COM_SE_ADMIN and then choose Goto Customizing System Settings Change New Entries .





3. Choose Goto Back


5. Choose Settings for Business Object and enter the business object BUS1006 withclass /DBM/CL_SES_BP.


7. From the Search Engine Service Administration screen, choose Index Create/Activate Indexes for Object Type 1 of object BUS1006.

8. Choose the entry BUS1006 and start the indexing (full).


17 Warranty Processing


17.1 Warranty CustomizingProcedureIn order to copy DBM-specific data to warranty claims, make the settings described inCustomizing for Dealer Business Management under Service Warranty Business Add-Ins (BAdIs) Warranty Documentation.


17.2 Assigning Warranty Claim Item Type – OrderItem CategoryFor each manufacturer and division, you assign a warranty claim item type to each itemcategory for which a warranty claim can be created in the service order. The system copiesthese settings when a warranty claim is created from a service order.

ProcedureIn Customizing for Logistics Execution, choose Dealer Business Management (DBM) →Service → Warranty → Assign Warranty Claim Item Type to Order Item Category.


17.3 Editing Warranty DataProcedure

1. On the SAP Easy Access screen, choose Logistics Logistics Execution DealerBusiness 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_KINDThave been delivered without entries. Make the following entries usingtransaction 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 bychoosing Control Data Account Control and making an entry in theVendor field. You have to edit general data, company code data and salesarea 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 thefollowing 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 followingdata:

o Warranty Ctrl, for example 01 (Vehicle Warranty)

o Tax. Depart. Cty, for example DE

o Division, for example 01

ExampleField 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 inCustomizing for Dealer Business Management under Service Warranty Business Add-Ins (BAdIs) Warranty Documentation.


17.4 Defining Catalog CodeProcedureIn Customizing for Logistics – General choose Equipment und Tools Management (ETM)Master Data Catalogs Define Catalog Code. You can create your own catalogs. Refer tothe Customizing activity documentation for more information.


17.5 Defining Automatic CO Account AssignmentDeterminationUseYou have to define account assignments for posting the accounting documents from warrantyprocessing in CO.

ProcedureIn Customizing for Plant Maintenance and Customer Service choose Warranty ClaimProcessing (or start transaction OWTY) Accounting Define Automatic CO AccountAssignment Determination (see also long text of customizing).

ExampleUse 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 bein the cost element group INT DBM_DB .


17.6 Allowing Change of CO AccountAssignments for ConditionUseYou define the conditions under which the person responsible is allowed to change theautomatically-determined account assignment. This will allow the person to post to a differentaccount assignment object during warranty claim processing.

ProcedureIn Customizing for Plant Maintenance and Customer Service, choose Warranty ClaimProcessing (or start transaction OWTY) Accounting Allow Changeability of CO AccountAssignments for Condition (see also long text of customizing).

ExampleEnter all condition types which are used in pricing procedure for your claim type. For claimtype 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


17.7 Defining Warranty Number RangeUseIn this Customizing activity, you define the number range for claims You can create aninternal and external number range for each claim type. The number range object is calledWTY_CLAIM .

Procedure1. In Customizing for Plant Maintenance and Customer Service choose Warranty

Claim Processing (or start transaction OWTY) Define Number Ranges for WarrantyClaims .

2. Create two groups, Warranty Claim and Recall .

3. Assign 1DBM to the Warranty Claim group and CDBM to the Recall group.


17.8 WTYRCL CustomizingProcedureIn Customizing for Logistics Execution choose Dealer Business Management (DBM)Service Recall Documentation.

In Customizing for Logistics Execution choose Dealer Business Management (DBM)Service Recall Define Order Type and Warranty Category for Recalls. You can definethe order type and the warranty category which is used for recall split creation.

Refer to the Customizing activity documentation for more information.

ExampleEnter the following data for the OEMs:

OEM Order Type: Warranty Category:

<Manufacturer number> 2001 01


17.9 Defining Recall PriorityProcedureIn Customizing for Logistics Execution choose Dealer Business Management (DBM)Service Recall Define Recall Priority. Here you can add your own values.

Refer to the IMG activity documentation for more information.


17.10 Defining Order Type and WarrantyCategory for RecallsProcedureIn Customizing for Logistics Execution choose Dealer Business Management (DBM)Service Recall Define Order Type and Warranty Category for Recalls. Here you candefine the type of order to be created according to on the OEM and warranty category.

Refer to the Customizing activity documentation for more information.


17.11 Assigning Item Type and Item Category toOEMUseYou must assign the item types (such as FRC , MATC , TEXT and so on) to DBM ItemCategories . This mapping is used when a recall is copied into a DBM Order and this mappingdefines which items or labor values have to be added to the DBM Order.

ProcedureOn the SAP Easy Access screen choose Logistic Logistics Execution Dealer BusinessManagement Warranty Recalls Assign Item Type and Item Category to OEM .


18 Cash Desk

To use DBM cash desk, you have to activate the BC Set Settings for DBM Cash Desk(/DBM/DBM800_CASHDESK).


18.1 Setting Characteristics of Document TypeSKUseYou define document type SK Cash Document to perform credit-side and debit-side postingsin the cash desk.

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

Global Settings (New) Document Document Types Define Document Types forEntry 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.


18.2 Defining Business TransactionsUseThe cash desk functions support G/L account postings. You can configure these businesstransactions as follows:

· Restrictions on business account assignment (cost center)

· G/L account predefined

· Tax indicator predefined


(DBM) Cash Desk Define Business Transaction.

2. Enter business transactions, such as 17 Office Material , 68 Bank .


18.3 Assigning a Number Range to Cash DeskDocument TypesUseUse the number range object /DBM/TILL for the cash desk functions.

Define range for the /DBM/TILLK object.

Procedure1. 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 inthe cash desk document types.

5. The default value for the interval is 01 . This value is also transported with thebusiness 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


18.4 Setting Up a Cash Desk Work CenterUseYou can use this procedure to assign organizational and content settings to a cash desk.


(DBM) Cash Desk Define Cash Desk Work Center.

2. Enter the required data.

3. On the SAP Easy Access screen, choose Tools Administration MonitorSystem Monitoring User Overview.

4. Copy the desired terminal and enter it in the IMG activity Maintaining Cash DeskWork Center in the field CDWC: Computer .

This ensures that the cash desk can only be started at a specific work center (sincethere 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 workcenter:

o Business transactions

o Master data (cost centers)

o Accounts


19 Dynamic Sheet


19.1 Define StyleUseYou use this Customizing activity to define the style of the sheet with respect to the characterformats it uses. You can assign these character formats to a layout and change the values bydouble- clicking on a character format.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Customer Data Management Dynamic Sheet Define Style.


19.2 Define Content ObjectUseYou use this Customizing activity to define the content objects you can use to add to thedynamic 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 eachcontent object. The parameter names must first be defined in the activity Define ContentObject Parameters . The syntax for parameters is <Tablename>-<Fieldname>.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Customer Data Management Dynamic Sheet Define Content Object.

ExampleThe 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 theAUFART = 1000.

The Order content object only checks the parameter /DBM/SPLHDR_DB-AUFART. If youwish to create parameters for your own content objects, you must implement the check in theimplementation class of the BAdI. If you wish to create your own content objects, refer to theBusiness Add-Ins documentation (BAdI: Content Objects for Dynamic Sheet).


19.3 Define Content Object ParametersUseYou use this Customizing activity to define the content object parameters. These values areassigned to the content objects.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Customer Data Management Dynamic Sheet Define Content Object Parameters.


20 Notification


20.1 Maintaining Enhancements and BAdIImplementationsProcedureIn Customizing for Logistics Execution choose Dealer Business Management (DBM)Customer Data Management Notification Business Add-Ins (BAdIs) NotificationDocumentation , and follow the instructions in this section


20.2 Defining Notification Types for DBMUseYou use this Customizing activity to assign standard notification types to DBM notificationtypes.

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 inthis Customizing table.

The program logic may differ in some cases according to the DBM notification type. Forexample, the customer is not required data for DBM notification type D , but it is for DBMnotification type S .

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Customer Data Management Notification Define Notification Types for DBM .


20.3 Defining Outcome Type and Outcome CodeUseYou use this Customizing activity to define the possible outcome types and outcome codesfor the notification types D1 Sales Activity and D2 Complaint . These outcome types andcodes can be assigned to notification tasks. On the outcome code level, you define whichcode values (texts) should be copied to the task long texts. You also define whether the valueshould appear in upper case.

Default outcome types:

· contact result

· competitor

· other offer

· kind of contact

Default outcome codes:

· buys over central

· business lost

· delivered

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Customer Data Management Notification Define Outcome Type and Outcome Code .


20.4 Assigning Outcome Type to Task CodeUseYou use this Customizing activity to assign the outcome types to the task codes. Theoutcome types that the user then chooses depends on the task codes.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Customer Data Management Notification Assign Outcome Type to Task Code .


20.5 Assigning Task Code to Order TypeUseYou use this Customizing activity to define the task code group and the task code for theautomatically-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 froma DBM order (transaction code /DBM/ORDER01 or /DBM/ORDER02), the system alwaysgenerates a task in the background.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Customer Data Management Notification Assign Task Code to Order Type .


20.6 Defining Follow-Up Task CodeUseYou use this Customizing activity to determine the date on which you would like the task tostart, in accordance with the original notification type, task code group and task code. Youcan 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 ofdays from which the task should begin, counted from the end-date of the original task. If anend-date does not exist, then the number of days is counted from the start date of the originaltask.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Customer Data Management Notification Define Follow-Up Task Code .

ExampleIf the field Number of Days (date of the follow-up task in days) is set to 4, and the end-date ofthe original task is 18.08.2006, the task would begin on 22.08.2006.


20.7 Setting BAdI: Input Help for Outcome TypeUseYou can use this BAdI to process the event ON_F4 in the ALV grid for the outcome type ofthe table /DBM/CU_OUTCOME. You can use this BAdI to change the behavior of thestandard input help or make your own check on the manually-entered value.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Customer Data Management Notification Business Add-Ins (BAdIs) BAdI: Input Help forOutcome Type.


20.8 Setting BAdI: Input Help for Outcome CodeUseYou 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 inputhelp.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Customer Data Management Notification Business Add-Ins (BAdIs) BAdI: Input Help forOutcome Code.


20.9 Setting BAdI: Input Help for Outcome CodeValueUseYou use this BAdI to process the event ON_F4 in the ALV grid for the outcome code value ofthe table /DBM/CU_OUTCOME. You can use this BAdI to change the behavior of thestandard input help, or perform your own check on the manually-entered value.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Customer Data Management Notification Business Add-Ins (BAdIs) BAdI : Input Help forOutcome Code Value .


20.10 Setting BAdI: Filter Text of Outcome CodeUseYou use this BAdI to select which outcome code texts from outcome tables are copied to thelong text of the appropriate task. You can override the standard behavior that copies the textsif they have indicator FLGTO = 'X' set in table /DBM/CU_OUTCOME.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Customer Data Management Notification Business Add-Ins (BAdIs) BAdI: Filter Text ofOutcome Code .


20.11 Configuring E-Mail for NotificationProcedureTo 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 emailaddress, for example, Internet Mail [email protected] (Communication Method: E-Mail)


21 Order


21.1 Order Search with Search Engine TREX

The order search function in Dealer Business Management (DBM) is based on TREX, whichcan be installed in the same server as DBM for test or evaluation purposes. Systemprerequisites are SAP Netweaver 7.0, TREX 7.0, Version 39. To use the search functions inDBM, you must have TREX installed and configured.

ProcedureYou can find more information about the installation of TREX on the SAP Service Marketplaceunder http://service.sap.com/instguides SAP NetWeaver SAP Netweaver 7.0 (2004s)Installation Installation – Standalone Engines SAP Netweaver Search and ClassificationTREX .

For information on how to define the RFC connection, see Setting Up the RFC Connection[Page 128].



21.2 Transaction COM_SE_ADMIN for OrderSearchesProcedure

9. Enter transaction code COM_SE_ADMIN and then choose Goto CustomizingSystem Settings Change New Entries .





11. Choose Goto Back

12. From the Search Engine Service Administration screen, choose IndexCreate/Activate Indexes for Object Type 1 of object Order. This will be availablethrough BC set /DBM/DBM800_EOS.

If you are using enhanced order search, you need to create additionalindexes 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.

13. Choose the entry ORDER and start the indexing (full) for each object type.

14. To plan a recurring job for the delta load, choose System Services Jobs JobDefinition .

15. Choose Step ABAP Program and execute report COM_SE_DISPATCHERwithout a variant.


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 beupdated and how often the vehicle data is changed.


21.3 Defining Order SearchUseThe order search requires manual entries in the first installation. You must perform thefollowing steps for order search.


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 ManagementOrder Order Search Define Order Search Attributes.


ScrNo Screen Field Table Name DatabaseField

AttType

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 GotoCustomizing Business Objects And Indexes .

6. Click Settings for Business Object and then click New Entries . Enter in the tablefields 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 ofactive indexes (starting screen of transaction ses_admin) and click the button indeximmediately.

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.


21.4 Defining Enhanced Order Search

The enhanced order search requires manual entries in the first installation. You must performthe following steps to run it.

Procedure1. Activate BC Set /DBM/DBM800_EOS by using transaction SCPR20.

2. In Customizing for Logistics Execution, go to Dealer Business ManagementOrder 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 ManagementOrder Order Search Define Order Search Attributes .

5. Enter the data as indicated in the table below:

ScreenNumber

Screen Field Table Name Database Field AttributeType

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- /DBM/VBAP ITOBJID S String


ITOBJID

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 fromthe list of active indexes (starting screen of transaction SES_ADMIN) and choose theIndex Immediately button.

7. Choose the Full indexing mode.


21.4.1 Defining BAdI: Enhanced Order Search - UIEnhancement

You can use this BAdI as a screen enhancement BAdI in the package /DBM/ORDER underthe /DBM/ORDER enhancement spot. You can use it to replace subscreens in the enhancedorder search view with other subscreens.

This BAdI is always called as it is not based on a filter.

PrerequisitesOnly one implementation is active.

ProcedureIn Customizing for Logistics Execution, choose Dealer Business Management (DBM)Order Business Add-Ins (BAdIs) BAdI: Enhanced Order Search - UI Enhancement .


21.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 thepackage /DBM/ORDER under the /DBM/ORDER enhancement spot. Using this BAdI, you canadd, delete, or modify search criteria for the order search.



ProcedureIn Customizing for Logistics Execution, choose Dealer Business Management (DBM)Order Business Add-Ins (BAdIs) BAdI: Enhanced Order Search - Criteria Enhancement .


21.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/ORDERunder the /DBM/ORDER enhancement spot.

Customer includes are available for each tab of the enhanced order search, that is to say, atheader, 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 customerincludes. This BAdI must then be implemented for populating data into the newly added fields.



ProcedureIn Customizing for Logistics Execution, choose Dealer Business Management (DBM)Order Business Add-Ins (BAdIs) BAdI: Enhanced Order Search - Result Enhancement .


21.5 Up-selling and Cross-selling

Up-selling indicates the complete replacement of a customer’s originally required item withanother item that is higher in value.

Cross-selling refers to the marketing of additional items along with the customer’s originallyrequired item.

ProcedureActivate BC Set /DBM/DBM800_UPS_CRS by using transaction SCPR20.


21.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 tothose 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 ofexisting packages.

Proposal types must be categorized into Additional, Replace, Flexible (which is applicable forpackages, where an item within a package can be identified as an up-selling/cross-sellingalternative to the original item) or Package Replacement (only for replacing one packageentirely with another).

Procedure1. Activate BC Set /DBM/DBM800_UPS_CRS by using transaction SCPR20.

2. In Customizing for Logistics Execution, choose Dealer Business Management(DBM) Order Specific Processes Up-selling and Cross-selling Define ProposalType .

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.


21.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 SettingsWhen Reject Original Items is the selected option, you must mandatorily select a reason forrejection. The values for this Rejection Reason field are derived from the IMG activity DefineReasons for Rejection. To add a new rejection reason, you need to add it within this IMGactivity.

When Delete Original Items is the selected option, the Rejection Reason field is notmandatory.

Procedure1. Activate BC Set /DBM/DBM800_UPS_CRS by using transaction SCPR20.

2. In Customizing for Logistics Execution, choose Dealer Business Management(DBM) Order Specific Processes Up-selling and Cross-selling DefineReplacement Procedure .

3. Select the procedure in the Replacement Procedure field and save the selection.


21.6 Defining a Reason for Rejection

All defined rejection reasons from Sales and Distribution (SD) are also available in DealerBusiness Management (DBM). In Customizing for Dealer Business Management, you candefine for each rejection reason whether pricing should be deactivated for an item with thatrejection reason. If the rejection reason is used in DBM orders, it is important that you set thevalue to X (No cumulation - Values cannot be used statistically) or Y (No cumulation - Valuescan be used statistically) in the Price Cumulation field. For more information, see thedocumentation of the following Customizing activity and the field help of the field PriceCumulation in this Customizing activity.

ProcedureIn Customizing for Logistics Execution, choose Dealer Business Management OrderBasic Functions Define Reasons for Rejection .


21.7 Working with SubordersUseYou use the suborder for the multi-branch service. In the main order, you can create asuborder to assign work tasks to another branch. The suborder for a task in the main ordercorresponds to a job in the suborder.

Procedure1. 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 → DefineShipping Data for Plants .

2. Account assignment category

o In Customizing for Dealer Business Management , navigate to Order →Account Assignment → Internal Order Account Assignment → AssignAccount 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 toMaster Data → Account Assignment → /DBM/MBS_0LEVEL - Zerolevel internal order for suborder .


Do not forget to extend the settlement rules for your suborder order type (in our delivery is7000) (see section Defining Parameters for Settlement Rule ) with values similar to those inthe example below.

ExampleDBMOrderType

OperatingConcern

Characteristic SourceStructure

SourceAssignment

DBMOrder






21.8 Defining Copying of Order Items

DBM order items are copied during different scenarios such as copying of orders with thecopy tool, copying items during creation of a suborder, adding packages to an order, andcopying packages from service contracts to orders. In some cases, the correct item categoryneeds to be determined while copying the items to the target order. This is relevant especiallyduring the DBM delivery process. You have to make the following settings to determine thecorrect item category.


Order Copying of Items Determination of Item Category Define Criteria .

If, for example, during creation of a suborder, the source plant uses DBM deliveriesand the target plant does not use DBM deliveries, the correct item category needs tobe determined for the suborder items in the target plant. The same applies ifpackages are added to orders that are created in different plants where the DBMdelivery 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 forCopying Items

Source ControlCode

Source ItemCategory

TargetPlant

Target ItemCategory

2 CS D020 0002 P002

3 PC P002 0001 D020


21.9 Define Order Type Schema

UseA new order type schema PDI_REL has been created and should be active. All PDI-relevantorder types should be maintained in this schema.

ProcedureIn Customizing for Logistics Execution, choose Dealer Business Management (DBM) ->Order -> Order Type -> Order Type Schema.


22 Archiving


22.1 Maintaining Enhancements and BAdIImplementationsProcedureIn Customizing for Logistics Execution choose Dealer Business Management (DBM)Archiving Archiving Documentation , and follow the instructions.


22.2 Archiving Control for DBM OrderUseResidence time determines the time interval (in calendar days) that must elapse between thetime of closing the DBM order (the date when order gets status Closed ) and setting thedeletion indicator by the preprocessing program.

The wildcard character * also can be used and the program must use the strongest conditionif there is more than one. Conditions with fixed values are stronger than condition with * . TheDBM order is not be archived if no conditions match.

ProcedureYou can configure archiving for DBM orders in Customizing for Logistics ExecutionDealer Business Management (DBM) Archiving Archiving Control For DBM Order.

ExampleSales 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 salesorg 0001 then the preprocessing program will check if the 500 days have elapsed. In eachother case the program will check if 200 days have elapsed.


23 Time Recording


23.1 Creating Customer Include Fields for TableCATSDB

DBM Time Recording allows the creation of time stamps on order, task, and item level. To beable to transfer this additional data to CATS, relevant fields have to be added to the tableCATSDB via the Customer Include CI_CATSDB.

ProcedureAdd 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 addexactly the same components (same component name and component type as in/DBM/CATSDB), otherwise DBM Time Recording cannot be used and will run intoerrors.

Adding Customer-Specific Index For Table CATSDBSee SAP Note 1121243.



23.2 Transferring DBM Data to CATSProcedureTo ensure the transfer of the DBM specific data of the time stamps (order, task, item), youmust 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.

ExampleThe class method /DBM/CL_TM_DBMDATA_EXAMPLE->FILL_CATS_DBM_DATA holds theexample logic to fill the DBM specific data into the CATS record. This is just an example ofhow 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. Passthe single record into the class changing parameter 'cs_enrich_table' which is returned withDBM 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 OBJECT 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 byclicking Additional fields . If you want to use this functionality you must perform followingsteps, after you have added the fields to the structure CATSDB

· Create the subscreen 1000 for program SAPLXCAT , which contains the additionalfields. 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 thedata to the calling program needs to be created. The function module used isEXIT_SAPLCATS_005 . You can do the relevant coding in the customerenhancement project, which was created for the transfer of the DBM specific data, asmentioned above.

For the optional process of subsequent cost processing, it is also necessary to create animplementation for the enhancement CATS0006, and to change the coding of theenhancement CATS0002, to ensure that the DBM Order is updated accordingly if subsequentcosts 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, thatsubsequent costs occurred. Corresponding coding must be added to the includeZXCATU02.

· CATS0006: Add coding to the include ZXCATU05, such as the method/DBM/CL_TM_DBMDATA_EXAMPLE->SAVE_ORDER to save the updated DBMorder.

If you want to use the subsequent costs process for time recording, add the following codingto 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 theDBM order number) is not empty. You have to change the first line of the coding if thefield which was added to the include CI_CATSDB (view paragraph ‘CreatingCustomer Include Fields for Table CATSDB’) for the DBM order number has adifferent name than in this example (DBMVBELN). The first line must be:

IF NOT <ls_enrich_table>-<fieldname for DBM Order> IS INITIAL.

Coding of CATS0002IF 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'. 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.

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. MESSAGE e350(/dbm/tm) WITH go_order->ms_vbak_com-vbeln. ENDIF. ENDLOOP. ELSEIF lv_status = 'B'. MESSAGE e350(/dbm/tm) WITH go_order->ms_vbak_com-vbeln. 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'. CALL METHOD lo_dbmdata->set_sub_seq_costs EXPORTING is_tcats = sap_tcats 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 order_not_relevant = 3.

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.


23.3 Setting Up Data Entry ProfilesUseYou must define a default data entry profile for the configuration of the data entry in the timesheet.

ProcedureIn Customizing for Cross-Application Components choose Time Sheet Specific Settingsfor CATS classic Set Up Data Entry Profiles or enter transaction CAC1 .


23.4 Maintaining HR Master DataUseFor the use of DBM Time Recording, a minimum set of info types must be maintained for therelevant employees by using transaction PA30 (Maintain HR Master Data ).

Procedure1. 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 withtransaction 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 morethan one field for assignment as shared employee


23.5 Additional InformationIf CATS accumulates 0 hours for the time booked, 0 times (quantity) is calculated for theactual times. This can occur for a few reasons:

1. If the relevant work schedules for the employee grouping/work schedule rule is notcreated for the period. The working schedules can be generated using transactionPT01. The work schedule is maintained for each employee in the HR master recordin the info type 0007 (Planned Working Time).

2. If time is booked during the time interval which is defined as a 'Break' in the BreakSchedules in standard customizing, and if this break time is defined as 'Unpaid' timethen 0 actual time is booked by CATS. This can be overrun in the CATS profile beingused by setting the flag No Deduction of Breaks active.


24 Integration with SAP Credit Management

You can integrate SAP Credit Management in your DBM system. This allows you to use thecredit limit check in DBM orders.


24.1 Setting Up the Credit Limit Check

To set up the credit limit check, see the Configuration Guide for SAP Credit Management onSAP Service Marketplace at http://service.sap.com/fscm SAP Credit ManagementMedia Library Other . The following documentation only gives you some additional hints.

SAP FSCM (SAP Financial Supply Chain Management) uses SOA services to communicatewith other applications. If SAP FSCM runs on the same host (the calling application), servicescan be configured as local Web services. If SAP FSCM runs on a different host (the callingapplication), services run over XI.

Procedure1. 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

§ DocumentedCreditDecisionERPBusinessTransactionDocumentNotification_Out

o Inbound services

FINBASIS 736

http://sap.com/xi/FSCM/Global

§ CreditWorthinessQuery_In

§ CreditCommitmentNotification_In

§ CreditManagementAccountByIDQuery_In

§ DocumentedCreditDecisionERPBusinessTransactionDocumentNotification_In

2. Use the HTTPS protocol when configuring the logical port binding/connection. HTTPSneeds to install certificates with transaction STRUST on your host.

3. Configure the System Landscape Directory (SLD) for your business system. Checkthe SLD configuration by using transaction SLDCHECK.

4. Check the Web service utilities for error messages by using transaction SRTUTIL.

5. In Customizing for Logistics Execution, choose Dealer Business Management(DBM) Order SAP Credit Management (SAP Financial Supply ChainManagement) 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 CreditManagement Integration with Accounts Receivable Accounting and Sales andDistribution Integration with Sales and Distribution Define Risk Categories .

8. Check whether the risk categories are maintained in accordance with the risk classesin Customizing for Financial Supply Chain Management under Credit Management Credit Risk Monitoring Master Data Create Risk Classes .


24.2 Setting Up the Documented Credit DecisionPrerequisitesYou have set up Adobe Document Server correctly. To check the connection, see SAP Note944221.

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.

Procedure1. In Customizing for Financial Supply Chain Management, choose Credit

Management Credit Risk Monitoring Documented Credit Decision Define CaseTypes for Documented Credit Decision .

2. Create the missing case types.

3. In Customizing for Financial Supply Chain Management, choose CreditManagement Credit Risk Monitoring Documented Credit Decision PDF Form forSnapshot 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 numberconversion is necessary. Business Add-In (BAdI) UKM_CONV2PARTNER has to beimplemented.

Procedure

1. Check the Configuration Guide for SAP Credit Management on SAP ServiceMarketplace at http://service.sap.com/fscm SAP Credit Management MediaLibrary Other .

2. Implement BAdI UKM_CONV2PARTNER as described.



http://service.sap.com/fscm


25 Storage Goods Manager


25.1 Creating Required Master DataProcedureTo be able to use the DBM storage goods, you should configure the following settings for thespecific objects in the master data:

· Categories. Call transaction COMM_HIERARCHY Maintain Categories andHierarchies . The categories are linked hierarchically in your base hierarchy. The settypes are assigned to the actual category. You require one main category and eightsub-categories. When you maintain the categories that contain the set types, note thefollowing:

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 andDBM_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 areallowed:

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 typeDBM_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 typeDBM_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 typeDBM_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 typeDBM_S_WW

The name of the categories is fixed. You have to maintain them in the customizing tableunder Dealer Business Management → Storage Goods Manager → Define Storage Type forPutaway.


· Assign number ranges with the customizing node: Cross-Application Components,choose SAP Product → Settings for Product Type → Number Assignment → DefineNumber 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 forStorage Goods. Note that categories are master data. Define a number range interval for allcategories for which individual objects have been created.


25.2 Integrating Storage Goods into Memo PadUseThere is a new BAdI implementation for displaying storage goods, and branching to thetransaction /DBM/STG_SEARCH with the corresponding storage goods ID.

ProcedureYou can define your own layout by using the new content object STG. In Customizing forLogistics Execution , choose Dealer Business Management (DBM) Customer DataManagement Dynamic Sheet Layout Define Layout.


25.3 Defining Number Range for Storage GoodsUseIn this Customizing activity, you can define a number range for DBM storage goods.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Define Number Range for Storage Goods .


25.4 Defining Storage Type for PutawayUseIn this Customizing activity, you can define which storage types you want to use for putawayfrom 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 offorms.

PrerequisitesTo define a storage type, create a new category, see Creating the Necessary Master Data .

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Define Storage Type for Putaway .


25.5 Defining Putaway LocationUseIn this Customizing activity, you can define one or more locations for storage goods putawayfor each plant.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Storage Define Putaway Location .


25.6 Defining Putaway BinUseIn this Customizing activity, you can define one or more putaway bins for each putawaylocation. Furthermore, you can define the size of each putaway bin in meters.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Storage Define Putaway Bin .


25.7 Defining Permitted Storage Type forPutaway for Each WarehouseUseIn this Customizing activity, you can define one or more storage types that can be used forthe putaway bin.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Storage Define Permitted Storage Type for Putaway for EachWarehouse.


25.8 Defining Wheel Rim SizeUseIn this Customizing activity, you define rim sizes.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Type-Dependent Data Wheel Rim Data Define Wheel Rim Size

.


25.9 Defining Wheel Rim TypeUseIn this Customizing activity, you can define rim types.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Type-Dependent Data Wheel Rim Data Define Wheel RimType.


25.10 Defining Wheel Rim ManufacturerUseIn this Customizing activity, you define the rim manufacturer.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Type-Dependent Data Wheel Rim Data Define Wheel RimManufacturer.


25.11 Defining Tire SizeUseIn this Customizing activity, you define tire sizes.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Type-Dependent Data Tire Data Define Tire Size .


25.12 Defining Tire ManufacturerUseIn this Customizing activity, you define tire manufacturers.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Type-Dependent Data Tire Data Define Tire Manufacturer .


25.13 Defining Standard Position of StorageGoodsUseIn this Customizing activity, you define the standard positions for storage goods on a vehicle.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Type-Dependent Data Define Standard Position of StorageGoods.

ExampleStorage 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)


25.14 Defining Reminder / Expediting DataUseIn this Customizing activity, you define the following dunning/expediting data for each storagetype for putaway:

A planned length in days, after which the first reminder is due. The date on which the firstreminder is due is the reminder base date.

A reminder interval in days; this interval defines the length of time that elapses betweenreminders.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Type-Dependent Data Define Reminder/Expediting Data .


25.15 Defining StatusUseIn this Customizing activity, you select which status to use from the ones provided for thestorage goods.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Control Define Status

ExamplePossible status of storage goods:

· Created

· Deleted

· For removal from stock

· For storage

· Removed from stock

· Stored

· Scrapped


25.16 Defining ActionsUseIn this Customizing activity, you select which actions to use from the ones provided foradministering the storage goods.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Control Define Actions .

ExamplePossible 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


25.17 Defining Action MatrixUseIn this Customizing activity, you define how the status of a storage good changes when youexecute a specific action.

ProcedureIn 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).


25.18 Defining Printout FormsUseWe do not ship smart forms with Storage Goods Manager. You can define them in the SAPEasy Access screen by choosing Tools Form Printout Smart Forms .

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Message Determination Define Message Type .

Here you can add an output type, and specify your smart form under ‘Processing routines’ asfollows:

· Program: /DBM/STG_FORMS

· Form Routine: ENTRY

· PDF/Smart form Form: name_of_your_smartform


25.19 Defining Condition TablesUseIn this Customizing activity, you define the condition tables for message determination in theStorage Goods Manager. This message determination is similar to the messagedetermination used in Sales and Distribution (SD).

In the Storage Goods Manager, there are two different options for calling messagedetermination:

· Explicitly in dialog mode: Choose the print function in the order processingtransaction.

· Automatically by an action: When executing an action the message determination iscalled. When depending on the given status and action a message can be found thestorage goods will be printed out.

You can find more information in the Implementation Guide (IMG) for Sales and Distribution(SD) under Maintain Condition Tables.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Message Determination Define Condition Table .


25.20 Defining Access SequenceUseIn this Customizing activity, you define the access sequences for message determination inDealer Business Management (DBM). The message determination used in DBM is similar tothat 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.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Message Determination Define Access Sequence .


25.21 Defining Message TypesUseIn this Customizing activity, you define message types for message determination in DealerBusiness 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.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Message Determination Define Message Type .


25.22 Defining Message SchemaUseIn this Customizing activity, you define the output determination procedures for messagedetermination in DBM. The message determination used in DBM is similar to that of standardSales 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 outputdetermination procedures to each storage type.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Storage Goods Manager Message Determination Define Message Schema .


26 Text Handling


26.1 Defining Criteria TableUseIn this Customizing activity, you define your own criteria table with which the system thendetermines 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 thestructure, for example if the keys for the criteria tables that are provided are insufficient todetermine text catalogs with the desired logic.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Text Control Determination of Text Catalog for DBM Order Define Table of Criteria.


26.2 Defining Access SequencesUseIn this Customizing activity, you define the access sequence with which the system searchesfor valid text catalogs in a criteria table.

You can control the sequence in which the system checks the selected criteria tables. If thesystem does not find a suitable entry in the first criteria table, it checks the next table.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Text Control Determination of Text Catalog for DBM Order Define Access Sequences.


26.3 Defining Control Model MasterUseIn this Customizing activity, you define how you want to control model texts and model optiontexts.

You can create different text determination procedures and maintain how they aredetermined.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Text Control Control Model Master.


26.4 Defining Control Vehicle MasterUseIn this Customizing activity, you can define how you want to control vehicle texts and vehicleoption texts. You can create different text determination procedures, define how they aredetermined 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 longtexts referring to features by using a separate function in the features view. You can copyvehicle and option long texts (with or without reference) from the model master when youcreate the model, or an option.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Text Control Control Vehicle Master.


26.5 Defining Control Labor Value MasterUseIn this Customizing activity, you define how you want to control labor value texts.

You can create different text determination procedures and maintain how they aredetermined.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Text Control Control Labor Value Master.


26.6 Defining Control Package MasterUseIn this Customizing activity, you define how you want to control main package and variantpackage texts. You can create different text determination procedures and define how theyare determined. You can maintain long texts on main package level or on variant packagelevel on a separate tab page.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Text Control Control Package Master.


26.7 Defining Control Memo PadUseIn this Customizing activity, you define how you want to control customer information andvehicle 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. Thetexts that are found are displayed in the memo pad. The found/displayed customer andvehicle information texts should be controlled logically by the constellation determined byCustomizing for text control and the maintained texts in the vehicle, model and customermaster data.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Text Control Control Memo Pad.


26.8 Defining DBM Order ControlUseIn this Customizing activity, you can define how DBM order texts work in the system (atheader, split header, job, task, and item level).

You can create different text determination procedures, and define text access sequences tocopy texts to the different levels of a DBM order. You can copy long texts to the DBM orderfrom 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 touse the Web Dynpro long text tool, you must create text indicators.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM) ®Text Control ® Control DBM Order.


26.9 Defining Storage Goods ControlUseIn this Customizing activity, you define how you wish to control storage goods texts. You cancreate different text determination procedures and define how they are determined.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Text Control Control Storage Goods.


26.10 Defining Rule KeyUseIn 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 accesssequence 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.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Text Control Business Add-Ins (BAdIs) Rule of Text Access Sequence Define Rule Key.


26.11 Defining BAdI: Definition of RuleUseIn this Customizing activity, you can implement rules for text access sequences. The keysthat are defined in the activity Define Rule Key are used as filter criteria for these BAdIimplementations.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Text Control Business Add-Ins (BAdIs) Rule of Text Access Sequence BAdI: Definitionof Rule.


26.12 Defining Text Determination Logic KeyUseIn this Customizing activity, you define keys that represent text determination logic.

You can assign these text determination logic keys to text access sequences to triggerspecific text determination logic.

These keys enable you to implement the text determination logic as they are available as filtervalues for the BAdI: Definition of Text Determination Logic.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Text Control Business Add-Ins (BAdIs) Text Determination Logic of Text AccessSequence Define Text Determination Logic Key.


26.13 Defining BAdI: Definition of TextDetermination LogicUseIn this Customizing activity, you implement text determination logic. The keys that are definedin the activity Define Text Determination Logic Key are used as filter criteria for these BAdIimplementations.

ProcedureIn Customizing for Logistics Execution , choose Dealer Business Management (DBM)Text Control Business Add-Ins (BAdIs) Text Determination Logic of Text AccessSequence BAdI: Definition of Text Determination Logic.


26.14 Defining Text Handling for PurchaseRequisitionProcedureFor information, see SAP Note 1050958.


27 Sundry Items in a Fleet Order

By using a fleet order, you can sell many vehicles in a single order and you can add sundryitems 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.


27.1 Creating Activity Type for Sundry Items

The system requires an activity type for the sundry items to distinguish between activities forthe external service and activities for the sundry items.

Procedure1. In Customizing for Controlling, choose Cost Center Accounting Master Data

Activity Types Create Activity Types and create a new activity type for the sundryitems.

2. Define a price for the combination of the created activity type and the cost center byusing the transaction Change Activity Output/Prices (KP26) on the SAP Easy Accessscreen under Accounting Controlling Cost Center Accounting PlanningActivity Output/Prices Change . For the sundry items, all prices in this transactionshould be EUR 0.

The unit of the activity type price needs to be the same as the unit of thepricing reference material from the sundry item.

3. In Customizing for Dealer Business Management (DBM), choose Order BasicFunctions Account Assignment Define Account Assignment for Posting Costs inOrder and enter the required data for the activity type defined in step 1. Assign thematerial group for sundry items to this activity type.

ExampleThe following table displays an example of an activity type QEXTER for the sundry items withthe required data in the Customizing activity Define Account Assignment for Posting Costs inOrder:

Plnt Matl Group Cost Element Act Typ Cost Center

DBM1 91 None QEXTER WORKSHOP


28 Optional Components


28.1 SAP Incentive and Commission ManagementIntegrationProcedureFor related documentation, see DBM ICM Configuration Guide on SAP Service Marketplaceat http://service.sap.com/instguides under Industry Solutions Industry Solutions GuidesSAP for Automotive .

For more information, see SAP Note 1022451.




28.2 SAP Multi Resource Scheduling IntegrationProcedureFor more information, see DBM MRS Configuration Guide on SAP Service Marketplace athttp://service.sap.com/instguides under Industry Solutions Industry Solutions GuidesSAP for Automotive .


Dbm DEALER BUSINESS MANAGEMENT

Technology

Transcript of Dbm DEALER BUSINESS MANAGEMENT