jd edwards & peoplesoft 1 | brent coutts | coopers.pdf

The most comprehensive Oracle applications & technology content under one roof The most comprehensive Oracle applications & technology content under one roof

8.0 to 9.0 – Lessons Learnt

Brent Coutts Coopers Brewery Limited

The most comprehensive Oracle applications & technology content under one roof

Who We Are

• Coopers Brewery Limited

• Established by Thomas Cooper in 1862

• Mission

– Our family brewery creates great crafted beers and other natural products for the enjoyment of everyone


Our Products


Our Market Share

3.8%

96.2%

0

10

20

30

40

50

60

70

80

90

100

Australian Beer Market

Coopers Brewery

Competitors


Brew Floor


Brewery Entrance


Who I Am

• Custodian of Coopers Business Systems

• Commenced with Coopers Brewery Jan 2007

• Previous JD Edwards experience with Fosters

• SAP experience with Southcorp and Kimberly-Clark

• Enjoy working as a business focussed IT professional within manufacturing organisations


Executive Summary

• Overall a successful implementation

• Small project team

• Changes in JD Edwards functionality caused issues

• Third party software stability and service


Existing Environment

• JD Edwards ERP8.01

• Original implementation in partnership with Jigsaw (now Red Rock)

• Live April 2004

• Green Stack – Microsoft SQL Server 2000

– IBM WebSphere (albeit limited usage)


Existing Environment

• Infrastructure

– Shared application & database server

– Deployment server

– Create!Form server

– Demand Management server

• Support

– One JD Edwards developer 1 day per week

– CNC outsourced to Red Rock


Infrastructure Upgrades

• Upgraded physical application server together with upgrade to Windows Server 2003 and SQL Server 2005

• Virtualisation of Create!Form server

• Virtualisation of Demand Management server

• “Proper” DR with log shipping


Business Case

• Risk minimisation

• General feeling of being “left behind”

• Ageing infrastructure

• Licensing costs (particularly for DR)

• Existing Oracle instance on Windows


Approach

• Engaged Red Rock as service provider

• Largely a technical upgrade

• New functionality to be adopted after go-live

• Use virtualisation to maximum

• After workshop, made the decision to go full Red Stack


Project Structure

• Modified Red Rock Project Methodology

• Steering committee not required

• Project managers within Coopers and Red Rock

• Small technical team

• Weekly meetings

• Flexibility in approach


Project Tasks

• Infrastructure (SAN, vSphere) months in advance

• Retrofit changes – 4 weeks solid effort

• Build JD Edwards environment

• Redo every Create!Form and Create!Stream script

• Testing, then go live


Timing

• Flexibility the key

• Blackout periods

• Started planning early 2010

• Preliminary workshops and scope of works

• Kick off in September 2010

• Hiatus during late December / early January

• Retrofit completed on time


Testing

• Pragmatic approach

• Focus on sales orders, load building, invoicing

• Difficulty in getting testing done by users

• Testing workshops to test the minimum to transact

• Test scripts written by project team

• One-on-one training and testing


Forms Development

• New version of Create!Form v7

• Every form and script to be converted

• Estimate 25% of project cost

• Licensing during upgrade


Pre Go Live

• 3 data conversions to check timing and accuracy

• Test manual cutover tasks

• Final round of user testing

• Go / no go decision

• Forms printing bug found


Go Live

• 1600 on Friday 18-Mar-2011

• System available at 1000 on Sunday 20-Mar-2011

• Cutover tasks run

• Ready for business 0600 Monday 21-Mar-2011


What Went Wrong

• Scheduled pick dates on orders (mode of transport)

• Rebates missing • Invoices (both through transportation and

printing) • Printing overall (both Create!Form and Oracle

default) • MRP failed • .., then relatively smooth sailing..


What Went Wrong – Part 2

• Printing failed completely – every print job had to be monitored

• Price adjustments “dropped off”

• Commissions configuration had changed – no accumulations

• Complicated rebate structure – detail postings

• 2nd month end (1st full month)


What Went Right

• Retrofitting modifications

• Infrastructure

• Data conversion

• CNC overall

• Integrations

• Waiting for right Tools release


What Did We Learn?

• Don’t go bleeding edge for printing

• Bugs in Oracle software and how they are resolved

• Changes in functionality between 8.0 and 9.0

• Users focussed on testing outcome


What Would We Do Differently?

• No need for two project managers – just one from Coopers

• One technical consultant from Coopers

• CNC from 3rd party

• Look more closely at printing – BI Publisher

• Firmer testing regime


What’s Next?

• Unlocking standard functionality

– Pricing

– Advanced preferences

• SOA

• Pilot BI Publisher


Questions?

• Feel free to contact me at:

– [email protected]

• Reference visits no problem

mailto:[email protected]

jd edwards & peoplesoft 1 | brent coutts | coopers.pdf

Technology