Entdecken Sie eBooks
Kategorien
Entdecken Sie Hörbücher
Kategorien
Entdecken Sie Zeitschriften
Kategorien
Entdecken Sie Dokumente
Kategorien
Warranty Management
1. Complaints may be raised via multiple different channels (excel files, portals,
manual creation, unexpected returns,…)
2. Different streams within the process (quality information, finance and stock) are
often handled separately, have no / little integration and lack transparency
Customer Portal (e.g. B2B) Excel (e.g. KTL) Manual creation (e.g. UI5)
ERP
Solution
SAP Warranty Management works with claim objects that keep track of the transparency through an easy versioning concept.
▪ Within one claim, inbound and outbound processes can be processed for each partner.
▪ Within one category, there can be a unlimited number of versions which document the proceeding of a claim.
Customer
Vendor
▪ Through the flexible process design the rule engine can be called for each version. The rule framework is designed as well to call also self-defined rules and to automate
the validation process as much as desired.
▪ Based on the full integration to all relevant SAP modules, prices can be directly derived from SD or MM within the claim depending on the version and postings of costs /
revenues can be made into FI and CO directly out of the claim, separated by the version.
OEM
Branch /
Dealer Plant
abroad
Customer
Warranty deals with diverse organizational settings and players
◼ Direct an indirect sales organizations
◼ Consolidated and independent businesses
Service Center
◼ Organizational units take different roles in different stages of the
process
◼ Frequently changing players (dealers and suppliers)
Company
Internal Supplier
Customer
Within the customer facing warranty process the goal is to manage and handle claims
submitted by customers.
Within the vendor facing warranty process the goal is to recover costs from
internal (intercompany) or external (supliers recovery) sources.
Based on Claims
(e.g. if the customer claim
process is used)
• Costs arising from the customer facing
Claim / Version process can be claimed internally (from a
Creation different plant / entity) or externally (from
the respective vendor.
There are two
Claim major process
Processing variants
Based on Service Activities
(service on internal assets, serialized equipment, …)
Claim
• Internal service activities (repair) for an
Payment
asset or the replacement of an asset can
& Posting
be validated with regards to warranty
terms and conditions. If the requirements
are met, the costs can be claimed from
the respective vendor.
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13
Process Overview
Customer Claim Management „Manufacturer / OEM“
Warranty Customer Process - OEM
Create the claims from dealer portal / inbound IDocs. Perform second checks on claim regarding If necessary, postings can be reversed, changed and
Enrich the claim with data from the reference object warranty terms, Value thresholds, special then again posted. Due to the versioning concept, the
(asset). conditions,… transparency is kept during the whole process.
Customer Customer
Financial Claim
Claim Creation Inbound Outbound
posting Correction
Processing Processing
Create Claim Validate Master Data Perform content checks Check financial limits Reverse Posting
Submit Claim Derive Prices Validate returning part Post costs on accounts Correct Claim
Perform formal checks
Perform first checks on a claim regarding After potentially adjusting the claimed amount,
completeness (mandatory fields), post the claim costs on the appropriate FI
duplicates, master data,… accounts and CO objects.
Master Data
Master Data
Validate and adjust the prices Claim Customer Customer Financial Claim
Creation Inbound Outbound Posting Correction
Master Data
Create (financial) approval levels for your claims Claim Customer Customer Financial Claim
Creation Inbound Outbound Posting Correction
Master Data
Master Data
Master Data
• Reimbursement is
Customer claim data often “self-taken” via
(e.g. via Excel file) initial debit (under-
8D analysis report
payment of parts
delivery)
XLS
Perform validations e.g. on warranty terms, Claims can be reverse posted, changed
value thresholds, special conditions. Review and then posted again. Due to the
claims manually only if necessary. Send versioning concept, the transparency of
collective objection report to the customer. what was changed is given.
Upload your customer files with the upload tool Claim / Notification Claim
Processing
Financial
Posting
Claim
Correction
Creation
Master Data
Header Data
Data
Theinheader
internal format,
holds converted
all general data
Excel Data (External data) out
likeoffile
external and enriched
name, uploading status, by
customer orSAP file receive
data date.
External Data
This section holds the unconverted
data rows and header information
of the uploaded excel file.
SAP Data (Internal data)
Internal Data
This section contains Data in an
internal format, converted out of
external data lines and enriched by
SAP data.
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 26
Cross functions
Master Data
▪ Data conversions
Use predefined DDIC conversion
logic or function modules to
convert the data in a SAP
compatible format.
Create Claims for each customer file line item Claim / Notification Claim
Processing
Financial
Posting
Claim
Correction
Creation
Master Data
Master Data
Master Data
Create one transparent FI posting for all claims Claim / Notification Claim
Processing
Financial
Posting
Claim
Correction
Creation
Master Data
Keep track of all your claims with the warranty Claim / Notification Claim
Processing
Financial
Posting
Claim
Correction
Creation
workbench
Master Data
Supplier Supplier
Financial Claim
Claim Version Creation Outbound Inbound
posting Correction
Processing Processing
Master Data
Master Data
▪ Cost Collector
• Determination of costs related to the object
(scrapping / QM related costs)
Master Data
▪ Warranty Determination by
• Technical Object with multiple master
warranty assignment
• Spare Part warranty
▪ Warranty Check
• Dedicated profile to cover customer
specific warranty checks
• Using additional sources, e.g.
contracts
Master Data
Master Data
▪ Dunning Procedure
• In case the decision is overdue, the
vendor can be reminded
• The functionality is included in the
action framework.
• Standard message framework is used
to send messages
▪ Value correction
• The IV version contains the same
values as the OV version.
• Decision from vendor may have
different values
• A screen is provided to easily adjust
these values in the IV version
Master Data
▪ Claim Correction
• In case the claim has not been fully
reimbursed or rejected, it is possible
appeal the decision
• The starting point is again an OV
version which will be copied from the
latest IV version
• The data is the same except the fact
that the amount to be claimed will be
reduced to the difference between the
latest OV and IV versions
• The process of submitting the new
OV version and receiving the result is
identical to the versions before
Mobile
SAP Cloud Platform
C-Suite
Executives
Business
Users SMART BUSINESS INTELLIGENCE +
COLLABORATIVE ENTERPRISE PLANNING + PREDICTIVE ANALYTICS
Direct Access /
No sync required*
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC *When using HANA or other supported data sources 45
Use the Exploration Mode to investigate
Stories present the analytical content, which can be shared across the enterprise
Sender
recipient
sender
Sender
Model Company
Get ready to use, preconfigured processes to accelerate your SAP solution deployment.
Project
Lifecycle
Migrate,
Install integrate,
extend, test
▪ Internet
Overview-, Detail- and Customer presentations
http://www.sap.com/acs
▪ OSS-System
Notes
(Search term: Automotive Consulting Solutions)
Clemens Paulus
Senior Warranty Consultant
Consulting Automotive
M +49/151/438 19510
E clemens.paulus@sap.com