DEMANTRA DEMAND MANAGEMENT CONFIGURE TO ORDER IMPLEMENTATION ENGINEERING A COMPLETE ORACLE SOLUTION DO BUSINESS BETTER.

Transcription

1 DEMANTRA DEMAND MANAGEMENT CONFIGURE TO ORDER IMPLEMENTATION ENGINEERING A COMPLETE ORACLE SOLUTION Scan the QR Code to learn more DO BUSINESS BETTER

2 Table of Contents 03...Overview 03...Business Requirement 04...Upgrade Strategy 04...Implementation Challenges & Strategy to Overcome 04...CTO Non EBS Data Load Strategy 05...Lessons Learned 05...Benefits of Demantra CTO Implementation 06...Conclusion 07...About the Author 07...About Wipro Ltd.

3 Overview The customer is a leading Process Automation Technologies and Services company, part of the large fortune 100 companies, located in the US, Europe, and Asia Pacific. With revenues of $24.4 Billion, it is one of Oracle s largest Global Demantra implementation centers, spanning across US, Europe and Asia with approximately 15,000 SKUs, 250 locations and 25~30 forecast users across the globe. The customer was on an earlier version of EBS , and was undergoing a complete system overhaul comprising an upgrade from Release 7.2 to by using the using Demantra tool for forecasting CTO Models. Oracle Demantra provides an out -of -the box Configure to Order (CTO) solution from version 7.3 with a standardized Model Bill of Materials BOM integration support from EBS and above. This white paper focuses on how you can convert and load the BOM model and its related data into Demantra CTO base tables for customers who are using the earlier version of EBS (i.e ), which does not support BOM data conversion. Business Requirements Calculate the planning percentage for dependent demand based on independent demand ( Models Sales History) Bring the CTO structure from EBS (source system) to Demantra Calculation of part forecast final number based on final consensus for forecasting CTO Models forecast of independent demand Extract older Non-CTO structure sales history in EBS Solution provided should be scalable in future considering the future (source system) and use the same to generate accurate forecasting for integration with ASCP R12 rollout future CTO Models 03

4 Upgrade Strategy The customer decided to upgrade from the current version of 7.2 to Demantra version , which would support the CTO scenario and would meet the above mentioned business requirements. The challenge however, was to load the CTO Structure from EBS to Demantra as EBS cannot be integrated with Demantra for CTO history download. Therefore, we followed the legacy download (NON EBS Download) process by populating the CTO be considered as a component for multiple models. To meet this challenge, we were required to load the data at the model-item level combination in the item hierarchy, so that a unique record sanity is maintained in the system Each model family consists of multiple base models and one particular base model may belong to multiple model family. To overcome this challenge, data was loaded at the model family-base model combination Structure in the interface table, and then massaging the data and loading it into Demantra s CTO interface tables. Implementation Challenges and the Strategy to Overcome Every organization has its own set of processes that fit their business needs. They have their own specific product structure. We faced similar challenges with our client as well, whose existing product structure was Non-CTO and they were transitioning to a CTO structure slowly due to evolving business needs. Our main challenge was to retrofit their CTO Non EBS Data Load Strategy As the data residing at the source instance was in the Non-CTO structure format, we were not able to use the Demantra standard CTO load process. We needed to follow the CTO Non EBS Load strategy as mentioned below and update the current Non-CTO Structure at the staging table in Oracle and message the data in Demantra staging table. We then brought it to the required format in Demantra BIIO tables, where the standard Demantra workflow pushed the data to Demantra base tables. historical structure as well as the newly developed structure to have one common CTO structure format to bring in consistency in the forecasting process. Given below are the challenges we faced and the strategies we developed for each, to successfully overcome them: EBR-BOM Explosion Table (Source) Business was having history data as the Non-CTO Structure (Model and option item with no option class defined) and recent and future data after implementing the Oracle Configurator would be in Conversion of Sales History to CTD structure CTO format with option class and option item defined for each Model. So we needed to map the part of sales history with Non-CTO Structure (before implementing Oracle Configurator) to the current EBS (Source) Sales History Oracle Staging Demantra (Target) CTO Structure so that all the model data that was pulled in from source would have the same CTO Structure Load Data through Demantra Workflow EBS is not integrated with Demantra so the standard CTO history download was not possible. To resolve this, CTO history was loaded to Demantra interface table following the Non EBS CTO data load process CTO Sales History Demantra Staging Demantra Interface table BIIO Table One of the challenges was the One-to-Many relationship in Item Hierarchy. Each model consisted of certain items, but one item may 04

5 Lessons Learned Like any other implementation project, Demantra CTO implementation also had certain learning s during the implementation. Few of the important ones are listed below: Benefits of Demantra CTO Implementation Demantra version comes bundled with new functionalities and features which gives customers not only cutting edge technology over Keep it simple and use out-of-box features as much as possible Demantra helps to re-evaluate the current forecasting process which may not be optimal as it driven by an excel based limited functionality Make sure that your item hierarchy and location hierarchy are well defined and given proper thought, based on your business processes as this is the key for having an accurate forecasting process their traditional excel based forecasting process, but also empowers them to handle different type of business scenarios. Below are some of the important benefits: Demantra version supports spare parts forecasting commonly known as SPF functionality Demantra has a tight integration with R12, ASCP R12 Users should be involved at an early stage and trained on the system. Forecasting at the model level in Demantra helps calculate the parts This will help them understand Demantra s functionalities and how forecast accurately using the planning percentage calculations it can be leveraged. Try not to modify the Seeded data model functionality Availability of CTO structure in Demantra helps planners and demand analysts to forecast more accurately for parts which help in the maintenance of optimum inventory levels, resulting in cost savings for the organization Real-time collaboration Ability to slice and dice data and make important observations Improved User Interface 05

6 Conclusion Industries that operate in a CTO environment face real challenges in the planning and forecasting of finished goods sales as well as their component. The accuracy of forecasting at the component, i.e. the dependent demand level is equally important as an independent demand level. Better control at the inventory level of the component always helps organizations to improve their input cost. Having a strong forecasting tool which can help customers in forecasting independent and dependent demands is very important for accurate planning. Demantra , not only helps in the forecasting process but its integration with value chain planning also improves the capability to analyze the forecast and sales data to help in making some important planning decision. At Wipro we have a dedicated Demantra Centre of Excellence which continues to explore the different ways that the tool can be used and applied to different business verticals to meet challenging requirements of customers. For any further queries or questions you can reach us at manish.gupta14@wipro.com. 06

7 About the Author Manish Gupta is a Demantra Solution Architect at Wipro. He is a domain expert in Demantra Demand Management and Sales & Operations Planning. Manish did his Post Graduation from NITIE, Mumbai India and specializes in Supply Chain Management. He has 12+ years of experience in functional consulting including requirements study, gap analysis, designing solutions for package implementation, upgrades and application support. He has worked on many large business transformation projects. About Wipro Ltd. Wipro Ltd. (NYSE:WIT) is a leading Information Technology, Consulting and Outsourcing company that delivers solutions to enable its clients do business better. Wipro delivers winning business outcomes through its deep industry experience and a 360 degree view of "Business through Technology" - helping clients create successful and adaptive businesses. A company recognized globally for its comprehensive portfolio of services, a practitioner's approach to delivering innovation and an organization wide commitment to sustainability, Wipro has a workforce of 140,000 serving clients across 57 countries. For more information, please visit 06

8 DO BUSINESS BETTER NYSE:WIT OVER 140,000 EMPLOYEES 57 COUNTRIES CONSULTING SYSTEM INTEGRATION OUTSOURCING WIPRO TECHNOLOGIES, DODDAKANNELLI, SARJAPUR ROAD, BANGALORE , INDIA. TEL : +91 (80) , FAX : +91 (80) , info@wipro.com North America South America United Kingdom Germany France Switzerland Poland Austria Sweden Finland Benelux Portugal Romania Japan Philippines Singapore Malaysia Australia China South Korea New Zealand WIPRO LTD No part of this booklet may be reproduced in any form by any electronic or mechanical means (including photocopying, recording and printing) without permission in writing from the publisher, except for reading and browsing via the world wide web. Users are not permitted to mount this booklet on any network server. IND/BRD/SEP NOV 2014