Professional Documents
Culture Documents
USING SAP-APO
Agenda
Our company : Beiersdorf
Overview and strategy
Our experiences
Experience with SAP APO and next steps
JrgenBttcher
JrgenBttcher
In 2007, group sales exceeded 5.5 billion the best result in the companys more than 125-year history Sales growth of 9.1 % (adjusted for currency translation effects)
14,8 %
335
387
14,2 % 71,0 %
301
302
Europe America Africa, Asia, Australia 2003 2004 2005 2006 2007
JrgenBttcher
JrgenBttcher
All major supply chain processes (for example: plan, source, make, deliver, and return) will be managed centrally. Clear end-to-end and cash-to-cash process responsibilities.
Supplier
Production Center
Distribution Center
Market / Customer
Plan
Source
Make
Deliver
Cash-to-cash
JrgenBttcher
Processes will be tailored to our business model, optimized, and measured end to end from supplier to customer Implement continuous improvement processes
JrgenBttcher
Running down inventories at outlets Ensuring short restocking times Minimizing tied-up capital Reducing shelf management effort (retail-ready packaging)
JrgenBttcher
Beiersdorf Shared Services A Beiersdorf company providing best-practice services to support Beiersdorfs growth
BSS provides IS and accounting services to internal customers in the Beiersdorf group BSS established on April 1st 2003 as a wholly owned affiliate of Beiersdorf AG BSS translates enterprise into systems architecture providing regional/global systems
Regional ERP SAP systems Europe, Asia, Americas / global supply chain systems: PLM, APO/CRP. . . BSS hosts SAP R/3 systems of 62 companies worldwide and provides infrastructure services groupwide Accounting services to Europe and Middle East Number of employees: approx. 360, 270 of which at BSS premises in Hamburg Local/regional IS in the Americas and Asia/Pacific under BSS guidance with some 100 employees
ADVANCED PLANNING @ BEIERSDORF 12 5 Dec 2007
Brazil
BLASS*
Latin America SAP ERP 6.0 (Latin1)
North America
SAP R/3 4.6c (Latin1)
BESS*
Europe SAP R/3 4.6C (MDMP)
BASS*
Asia SAP ERP 6.0 (Unicode)
Australia
SAP R/3 4.6c (Latin1)
SAP APO
Europe & Americas& Dubai SCM 5.0 (Latin1)
SAP SRM
Germany only (Latin1) SAP SRM 5.0
HR*
Germany, Italy SAP ERP 6.0 (Latin1)
HCM BW
SAP BW
Latin and North America SAP BW 3.1 (Latin1)
e-recruiting
global 6.0 (Unicode)
SAP BW
Europe and corporate reporting SAP BW 3.1 (Latin1)
SAP BW POS
SAP BW 3.1 (Latin1)
Americas
ADVANCED PLANNING @ BEIERSDORF
Europe
* Multiple SAP clients in one system 13
Asia
5 Dec 2007
BESS2*
PRIME, PCs, and other clients SAP ERP 6.0
BASS*
Asia SAP ERP 6.0
SAP APO
Global (Latin1) SCM 2008
HR*
Global SAP ERP 6.0
HCM
e-recruiting
Global 6.0
BI
Americas
ADVANCED PLANNING @ BEIERSDORF
-All
Europe
* Multiple SAP Clients in one System. Applications not explicitly mentioned are Unicode. 14
Asia
5 Dec 2007
PRIME rollout
2000
2000: First tests of replenishment scenario with SAP APO 2.0 2001: Pilot SNP France-Poland with SAP APO (weekly replenishment) 2003: Big-bang implementation (DP, SNP, PPDS) in Germany (Release 3.1) 2004: Big-bang implementation (DP, SNP, PPDS) in France 2005: Start of international DP + SNP rollout 2006: Major rollout in Europe + United States (release 4.0) 2007: Rollout PRIME, Asia started 2008: Rollout PRIME, South America, Asia, and Australia
2008
Since January 2007 SAP SCM release 5.0
JrgenBttcher
JrgenBttcher
Integrated Planning
Target: stock reduction with high service level by optimization of planning processes (faster and more accurate)
Demand planning
JrgenBttcher
Production
Distribution
Sales
Mid-term
Master planning
Demand planning
Production Planning
APO-PPDS
Distribution Planning
APO-SNP Transportation Quantities and modes
Short-term
Lot sizes
Scheduling
APO-PPDS Due dates
Transportation Planning
APO-SNP / TP/VS
Supply
JrgenBttcher
Planning of compounds (PP) Fixed batch sizes | Monthly lot sizes Detailed scheduling compounds
2/3 weeks
15-month
JrgenBttcher
JrgenBttcher
BI
EDW
APO-DP
Demand planning Promotion planning
External sources
BI
Reporting
MM
Materials management
APO-SNP
Supply network planning Deployment Transport load builder
PP-PI
Production planning process industry
APO-PPDS
Production planning Detailed scheduling
JrgenBttcher
Planning books
PRIME template
APO-SNP Global
SNP-Europe
SNP-America
SNP-AAA
PC 1
PC 2
JrgenBttcher
DP:
Planning customer demands
3 standardized planning areas (split by region because of time zones) Standardized rollout with predefined structure / key figures as well as process and reporting Monthly baseline approach, weekly promotions added
JrgenBttcher
Load history
Correct history
Forecast
Correct plan
Transfer to SNP
Daily upload from BI Fill 10 different key figures Structure: Product Plant Country
Manual corrections in separate data view (e.g. promotions) Automatic outlier correction (history 5 a)
Statistical forecast approx. 40 predefined models (monthly) Life-cycle (predecessor/ successor) planning used
Promotion planning used (weekly) Manual adjustment for future events (media, sales)
Daily transfer
JrgenBttcher
JrgenBttcher
JrgenBttcher
Define networks
Demand transfer
SNP planning
Deployment
TLB
SNP planning
Distributes demands within supply network Creates distribution demands rounded to logistical units (pallet/layer/carton)
Deployment
Confirms distribution demands according to receipt situation (stocks, planned orders, etc.) Push and pull logic used
TLB
Combines all demands per date to order and optimizes truck Generates purchase order
JrgenBttcher
SNP
Demand Stock
History
data
Master data
Stock
Production orders
TLB confirmation
Reporting
Purchase
order
Orders
Master Data
Reporting
Inbound delivery + GR
DESADV
Invoice
JrgenBttcher
SNP: Example
JrgenBttcher
Weekly delivery
Forecast on SKU level (not EAN) 6 customers in 3 companies 200-400 SKUs each
JrgenBttcher
JrgenBttcher
JrgenBttcher
PPDS: Example
JrgenBttcher
Alert Management
Exception-based planning: Used in DP SNP PPDS Important part for a complex supply chain Predefined alerts used worldwide Reporting on number of alerts
JrgenBttcher
Our experiences
Experience with SAP APO and next steps
Data Volume
APO users Locations Location products Planned daily Resources Customer order lines per day Purchase reqs. per day Planned orders Trucks per day 700 Active users (all modules DP, SNP, PPDS)
33 plants, of which 2 PPDS locations 6 VMI customers Including, raw- semi, historic articles Active finished goods In 2 locations Only partially transferred to APO / special development 150,000 in SNP, 80,000 in PPDS, additional 150,000 extra on weekends Mainly on weekends, partly daily Planned by TLB
JrgenBttcher
40
177,000 26,000
700
> 100,000 230,000 80,000
40
Demand planning
APO implementation will increase turnover and profit by: Improving responsiveness to market opportunity (daily planning works)
Reducing stock while maintaining high service level usually stock reduction in CRP > 30% (daily delivery according to demand instead of monthly as before)
Improving production and transportation efficiency Scaling down of obsolete stocks Optimizing planning processes faster and more accurate (improved forecast accuracy by some 20%)
JrgenBttcher
Learnings
Very flexible and professional tool APO-DP/SNP/PPDS is used for planning; Microsoft Excel etc. not in use anymore Various design options, APO-DP/SNP is more a tool-set standardization required design-strategy: All companies use same planning area (data standardization: horizon, frequency, parameter) Standard planning books for fast rollout (process standardization by fixed proceedings) Various processes supported
JrgenBttcher
JrgenBttcher
www.sap.com/emea/sapphire
SAP 2008
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwhnte SAP-Produkte und Services sowie die dazugehrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Lndern weltweit. Alle anderen in diesem Dokument erwhnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte knnen lnderspezifische Unterschiede aufweisen.
SAP 2008