Professional Documents
Culture Documents
7.0
Parts Management
1
Agenda
1. Overview
2. Parts Master & OEM Parts Master
2
Parts Management
Objectives, Issues, Capabilities and Benefits
Objective:
Keep inventory levels low by ensuring parts availability for workshop and counter
sales with increased inventory turns
■ Managing high volumes of parts ■ End-to-end parts processing across all ■ Increased parts availability
in multi-brand environments dealer group locations
■ Increased parts turnover
■ Unpredictable failure & demand ■ Advanced replenishment planning
of parts routines ■ Increased inventory accuracy and
reduced write-offs
■ Increasing customer expectations ■ High service level for counter,
workshop and emergency repair (VOR) ■ Decrease average working capital
■ Positioning parts department as a
true source of profitable revenue ■ Leverage buying power of a multi-
brand group
3
SAP Dealer Business Management is
an End-to-end, Cross-functional Solution
SAP Dealer Business Management connects processes across departments to enable a
customer-centric and efficient operation of a dealership or dealer group
Appointment Service
Workshop Scheduling Processing
Vehicle
Procurement Parts
Parts & Sales
Logistics
Parts
Procurement Logistics
4
Aligning Stakeholders to Achieve
A Customer-centric & Profitable Dealership
Effective Management of a Dealership or Dealer Group requires alignment of several stakeholders with
differing objectives
How can I grow my business How can I sell more vehicles How do I service customers How do I keep inventory
by improving at better margins right and on time at every levels low by ensuring parts
visit? availability for workshop &
counter sales
Cash Flow & Profitability Revenue & Margin Premium Customer Throughput
Customer Loyalty Visibility in Distribution Service Margin
Chain Upsell opportunities Service Level
Workshop Efficiency & Inventory turns
Utilization
5
Parts Management
SAP Solution
SAP solution
SAP differentiators
■ Complete solution for service parts in an integrated multi-brand dealer group environment, enabling all
aspects of planning, procurement, warehouse management, catalog integration, fulfillment, OEM interfacing,
collaboration and analytics
■ Simple parts counter sales process with full parts data visibility, online availability & pricing check during
order creation, including a simple cash desk module
■ Global OEM parts master and simplified process for dealer parts master creation during the sales process
6
Parts Management
Overview Parts Logistics
Service Level - Increase parts availability and reduce working capital at the same time Parts
Sales
Parts
Logistics
Process overview
1 2 3 4
OEM & dealer Replenishment Inventory Purchase
Gather
parts Inputs
master Statistical Modeling
Planning Publish Forecast
Management & Finalize Forecast
Requisition &
(stock) Physical Inventory Order
■ Lean OEM parts ■ Advanced planning ■ Inventory types and ■ Shared services for
master file with open routines for parts stock handling (e.g. central purchasing
integration to OEM consignment stock)
data ■ Planning with multiple ■ ATP at different
replenishment types, ■ Integrated quantity & planning levels
■ Simplified and partially e.g. consumption- value flow
automated creation of based planning, net
■ External procurement
dealer parts master requirement
■ Return parts of non-original parts
processing
calculation, order- ■ Express (VOR)
■ Easy maintenance and based planning
handling of parts kits ■ Multiple automated purchase orders
including kits pricing inventory processes
(e.g. permanent)
■ Backorder process
7
Parts Management
Overview Parts Sales (Over the Counter)
Parts Logistics
Process overview
1 2 3 4
Parts
Parts Picking & Billing &
Availability
Order Goods Movement Cash- in
Check
8
Parts Sales: Process Flow
Cash Desk
• Easy-to-use cash desk for OTC
cash and credit card payments
• Integration with accounting
• Cash receipts
• Printing of sales checks
9
Replenishment Planning
Goods Receipt
• Stock postings
• Backorder Processing for DBM
Orders
Purchasing
• Conversion PREQ into PO
• Conversion Scheduling Lines
into Delivery Schedules
• Transfer to supplier Replenishment Run (MD02, MD03, MD04)
10
DBM 7.0 – Scenario Parts Management New in
Backorder Process – with Replenishment DBM 7.0
11
Cash Desk – Process Flow
Cash Desk
• Open the cash desk work
center
• List the invoice(s) via customer
Customer Invoice or billing document
• Customer wants to pay for
DBM service or parts
order
12
Parts Returns Processing
Process Flow
Add Data
• Add additional data and
make price adjustments
Create Credit Memo
• Create a credit
memo/parts return via
copy functionality
© SAP 2009 / Page 13
13
Agenda
1. Overview
2. Parts Master & OEM Parts Master
14
Master Data: Spare Parts (Material Master)
Based on the standard material master with enhancements for dealer business parts
Easy-to-use material master maintenance transaction
/DBM/MM01 Create material – DBM
/DBM/MM02 Change material – DBM
/DBM/MM03 Display material – DBM
15
Master Data: Spare Parts (Material Master)
Prerequisite views: Basic data 1, Sales data, Purchasing, MRP1 and Accounting
Material
master data
The material master is grouped into several views: Basic data, sales and distribution data,
purchasing data, various further data for engineering/design, accounting, costing,
warehouse management, and so on.
Basic data is relevant for all areas. It is valid for all organizational units within a client.
Sales organization data is relevant for sales and distribution. It is valid for the respective
sales organization and the distribution channel.
The sales plant data is also relevant for sales and distribution. It is valid for the respective
delivering plant.
There is additional data for several other areas that is valid for various organizational units.
16
Master Data: Manufacturer Part Number (MPN)
Optionally, in DBM, you can use the 40-character manufacturer part number, where more
than 18 characters are processed.
Example:
18-character manufacturer part number
Material number (external): A062115561
Manufacturer part number and manufacturer: do not enter
The prerequisite for using the manufacturer part number is that the conversion exit in
Customizing is active.
17
MPN: Maintenance in Material Master
MPN and manufacturer fields can be maintained in the material master (transaction
/DBM/MM01, View Basic Data)
As a prerequisite the external manufacturer has to be maintained in the vendor
master data (transaction XK01, View Control)
If the vendor master number and the external manufacturer number is different in
the vendor master a transformation is also done in the material master
18
MPN: Customization
For the usage of the Material Parts Number (MPN) an activation of a conversion exit is
mandatory as prerequisite in Customizing.
IMG Æ Logistics General Æ Interchangeability of Parts Æ Set Up Conversion Exit
for Material Numbers.
In this activity, you can activate a conversion exit and/or set the output length to
more than 18 characters.
For the implementation of MPN several important notes are existing.
19
Original Parts Master
The Original Parts Master is the entirety of all parts that an OEM can deliver.
For a multi-brand solution like SAP DBM multiple OEM parts masters have to be
maintained and stored in single parts master records although only a small percentage
of parts is actively used in the dealership.
To avoid having superfluous parts master records related to different OEM‘s you can
use optionally the functionality OMARA.
Therefore it is possible to load the Original Parts Master Data to the DBM system
without creating an active parts master record.
Function Group /DBM/PART_ORIGINAL includes several function modules for creating,
updating and deleting original parts master data
The parts master record is only created if the part is really required in the DBM order
processing.
The active parts master record can be created from the original parts master using
transaction /DBM/MMXX.
20
Example: SAP DBM Interfacing OEM Systems
e.g. Parts Master Data
SAP DEALER BUSINESS
OEM MANAGEMENT
OR
Regular Create Create Original
data updates Parts Master Parts Master
Master Data
Parts Create
Data Parts Master
Prices
Labor Operation
Catalogs
Vehicle
(/Model) Data
Recalls
21
Creation of Parts from Original Parts Master
You can use this function to create a parts master from the Original Parts Master by
using a reference material.
Prerequisites:
Data for the active parts master record to be created must be available in tables
/DBM/OMARA and /DBM/OMAKT.
You must have created a suitable reference material.
Activities:
To access the function for creating a parts master record from the original parts master,
enter the transaction code /DBM/MMXX.
The system displays a selection screen with the following subscreens
While executing an active parts master record is created with data from suitable ref. mat.
In a DBM order you can search in the Original Parts Master if a part is not maintained in the
Parts Master. Therefore use the F4-help within item category P002 and step to the second
search tab. You can also create a material from the original parts master when you create a
DBM order. In this case, you have to maintain the reference material by choosing
Environment → Reference Materials.
22
Master Data: Supersession
DBM supports the simple Supersession functionality also used in the industry solution
SAP Automotive (IS-DIMP).
The supersession of parts takes place automatically in a DBM order.
Example: Part A must be replaced by part B; this replacement creates a
relationship between part A and part B.
The supersession takes place based on the order and stock quantity.
When you create a new parts item, depending on the Customizing, you can choose
one of the proposed materials displayed in a dialog box.
Depending on the Customizing, by selecting the appropriate material the user can
adjust the quantity as required.
The quantity can be split into several items based on the supersession chain.
Order Supersession: When you create a new parts item, you receive the message that
material X has been replaced with material Y.
When you create a new parts item, you can choose one of the alternate materials displayed
in a dialog box.
Supersession takes place based on quantity; in other words, the order quantity is used.
When you create a new parts item, you can choose one or both of the materials displayed
in a dialog box. By double-clicking on a line, you can adjust the quantity as required.
23
Master Data: Supersession
Order Supersession: When you create a new parts item, you receive the message that
material X has been replaced with material Y.
When you create a new parts item, you can choose one of the alternate materials displayed
in a dialog box.
Supersession takes place based on quantity; in other words, the order quantity is used.
When you create a new parts item, you can choose one or both of the materials displayed
in a dialog box. By double-clicking on a line, you can adjust the quantity as required.
24
Master Data: Supersession Customizing
1 => 1:1: Supersession in the DBM Order takes place automatically in the background. When
creating a new part item, the user receives the information that part A has been replaced by part B.
2 => 1:1: When creating a new part item, the user can choose one of two parts in a dialog window.
Supersession takes place for the entire order quantity.
3 => 1:N: When creating a new part item, the user can choose one or multiple parts in a dialog
window. By double-clicking on a line, the user can adjust the quantity per item.
© SAP 2009 / Page 25
25
Pricing for Parts
26
Pricing
Pre-requisite:
5 Pricing concept in SAP
5 Sales and Distribution: Pricing procedures and concepts
The Customizing table is also responsible for the mapping of input and output fields
(communication structure) to the individual condition records. The pricing executed with
these condition records and for the condition types defined for the fields returns the values
via this mapping table to the input/output fields.
If entries for fields of the different communication structures are missing, they are not taken
into account for pricing.
27
Pricing
28
Optional: Standard Stock/Inventory Queries
Stock/requirements list
Transaction MD04
The most up-to-date stock and requirements situation is displayed for a part.
Stock overview
Transaction MMBE
The Stock Overview provides an overview of all part stock over all organizational
levels.
Material document list
Transaction MB51
This report provides for documents posted in Inventory Management.
List of stock values
Transaction MB5L
This report is used to display the total stock quantity and the total stock value for a
material at plant and storage location level.
29
Copyright 2009 SAP AG
All Rights Reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein
may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries,
eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+,
POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex,
MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos
are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and
services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries.
Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only.
National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only,
without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed
as constituting an additional warrant.
30