Warranty Management and Warranty Data

Transcription

1 Bitte decken Sie die schraffierte Fläche mit einem Bild ab. Please cover the shaded area with a picture. (24,4 x 7,6 cm) Warranty Management and Warranty Data Analytics@Continental Frank Pischulti, Head of BA Cross Applications, Continental Clemens Paulus, Consultant, SAP Consulting

2 Agenda Point of departure / Pain points in OEM business WDA providing transparency on incident reporting WTY providing transparency in financial execution Implementation roadmap

3 Point of departure Where we came from 3

4 Pain points when processing incidents with OEMs Inhomogeneous formats provided by OEMs Different formats of OEMs leads to difficulties for an overall reporting / comparison. Unused data potential Information is provided in non-standardized form in Excel/CSV/PDF Data information (on incidents and reason for failure) holds massive potential to evaluate reasons, root cause, One DB Financial claims Financial files must be validated / checked for correctness within short time. Manual work necessary.

5 Point of departure - Huge number of different file formats (and files) from different customers - Due to different formats of OEMS: - Specialized data bases / reporting was built per OEM - No standardized template process for payment - Validation of data only with help of self-developed solutions (SAP based and non-sap based) - No comprehensive reporting possible with focus on incidents / defects 3 rd defect 3% 1 st defect 2% 2 nd defect 2,5% Label 1 Label Label Label

6 Other data sources Target landscape Internal SAP local ERP Data Global Warranty Data Observation Markets Invoice Disputes, Price conditions Billing Part Requests Returned Parts Disputes (FI) Sign / Approval Cost Collector Q.COM WTY Warranty (Field & 0-Mileage) Commercial Processing WDA Warranty Data analytics (IPTV) CQTS Field complaints & 8D NCC IPTV Pareto Quality Reporting 2.0 Visualization (Front End)

7 Warranty Data analysis Mining the data, finding insights 7

8 Warranty Data Analysis - Overview

9 Warranty Data Analysis Example VW

10 Conti System Architecture OEM Portals Continental Quality Tracking System CQTS Shipments, Customer Mat No, Conti Mat No, Returned Parts, Long Texts... Billing Agent Technology HANA DB Side-car-scenario PAL ETL (Self-Developed) Central ERP with WTY Upload Tool De-central ERP with WTY and Dispute Management Quality Reporting 2.0 Visualization (Front End) IPTV/RPPD, MIS/MOP Business Objects Design Studio

11 Upload Tool for financial processing in WTY 11

12 Consolidation of Data SAP Warranty Management Each OEM format can be mapped and transferred into a generic, comparable structure. Based on this a template process can be established to execute a template financial process (with variants if needed) for each OEM.

13 Conversion of data into homogenous internal structure external data internal data

14 Creating SAP Standard objects for processing external data internal data internal data SAP Warranty Management (WTY)

15 Big Picture of Integration (customer side) Debit FI Dispute Management FI CO WTY Master data 0km Parts CQTS Enrich information Description Upload is always done via customer excel files. If part was sent back and is recorded in QM- Tool CQTS claims receive additional information 0KM cases have no excel files but are directly reported within CQTS. Excel file can be generated for 0KM cases to use template upload process ERP SD MM

16 Creating Cost collectors Excel-List / WDA Upload Tool Folgebeleg Folgebeleg Claims 1 Claim per Damage External Data Source Central ERP Local ERP Folgebeleg Folgebeleg Internal order 1 Internal order per claim Description Each line in external list (Excel or data base download) stands for 1 damage case and therefor creates a separate claim. For each claim / case a separate internal order (cost collector) is created where external costs (claimed by OEM) and internal costs (rework, investigation, ) can be saved Cost collectors can be used for charge back process

17 Charge Back Process Claim 1 Material A Claim 2 Material B Claim 3 Material C Collective Claim Material A Values of claim 1 Values of claim 4 Values of claim 5 Claim 4 Material A Claim 5 Material A Collective Claim Material B Values of claim 2 Values of claim 6 Values of claim 7 Vendor 1 Vendor 2 Claim 6 Material B Claim 7 Material B Claim 8 Material C Collective Claim Material C Customer Process Values of claim 3 Values of claim 8 Description Customer files create one claim per damage Based on specific criteria (e.g. material number) multiple claims can be combined into a collective claim (so called supplier dispute) and charged to the respective vendor Cost collector is used to transport external and internal costs.

18 Integration of WDA and WTY Upload Flow 18

19 Upload Flow HANA first WDA WTY Sharepoint Python Script WDA - HANA Push WTY-Upload: External Data WTY-Upload: Internal Data WTY-Claims in SPIRIT Upload in WTY only used if mapping for format is not available Convert Process

20 Lessons learned - Warranty is a complex process, often underestimated, which has great commercial potential - Change is never easy: Early involvement of end-user drives user acceptance - Focus on master data during testing phase, use data which is as realistic as possible - Users save time, and they can spend it on meaningful tasks, analyzing data, customer interaction, supplier charge back

21 Long-term Roadmap Upload Flow 21

22 Upload Flow Usage of Internal Data in HANA WDA CSE Sharepoint Python Script WDA - HANA WTY- Analytics Push SLT WTY-Upload: External Data WTY-Upload: Internal Data WTY-Claims in SPIRIT Upload in WTY only used if not WDA mapping available Convert Process

23 Upload Flow Complete Upload in HANA WDA SPIRIT Sharepoint Python Script WDA - HANA Upload Mappings WTY-Upload: Internal Data Process WTY-Claims

24 Thank You! Frank Pischulti Head of BA Cross Applications Continental Automotive GmbH Sodener Strasse Schwalbach am Taunus P: +49 (0) M: +49 (0) F: +49(0) E: frank.pischulti@continental-corporation.com Clemens Paulus Consultant Warranty Management Consulting Automotive SAP Deutschland SE & Co. KG Hasso-Plattner-Ring Walldorf M +49/151/ E clemens.paulus@sap.com 24