migrating from se to ee rené bergkamp vice-president of r&d, financials - qad qad explore 2012

Migrating From SE to EE

René Bergkamp Vice-President of R&D, Financials - QAD

QAD Explore 2012

2

The following is intended to outline QAD’s general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, functional capabilities, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functional capabilities described for QAD’s products remains at the sole discretion of QAD.

Safe Harbor Statement

Migrating from SE to EE

3

• Why upgrade?• Migrate to a more Effective Enterprise• Approaches• Experience from the field• Questions

Agenda


4

Why Upgrade?


5

• Internationalization• Enterprise Financials• Corporate governance• New powerful capabilities in other areas• Centralization/standardization• Clean up data/setup• Remain on a supported release• Move to On Demand

Common Upgrade Reasons

Migrating from SE to EE: Why upgrade?

6

Migrate to a More Effective Enterprise


7

• Standardization• Dealing with currencies• Consolidated financial reporting• Compliance• Limiting customizations• Introducing shared services• Managing the company IT eco system

Considerations

Migrating from SE to EE: Migrate to a more effective enterprise

8

• Transforming from loosely coupled groups of local operating business to an effective (global) enterprise- Centralization of systems- Standardization of practices

• Main areas of improvement- Effective planning, reporting and closing

process- Better management/enforcement of (global)

compliance - Shared services

Standardization


9

• Balancing act between ‘corporate’ desire for standardization and ‘local’ arguments of being different

• Global first- Imposed corporate standard way of working- Local legal requirements and statutory

reporting are considered as ‘after the facts’

• Local first- Every entity is free to set up according to the

specific local requirements- Global visibility is obtained afterwards by

translation mechanisms

Defining the Desired Standardization


10

• Enterprise Edition helps with- Shared Sets and translatable descriptions

master data- Accounting layers to support multi-GAAP - Financial Report Writer- Unicode

Defining the Desired Standardization


11

• Buying/selling/paying in different currencies- Processing payments centrally for multiple

countries- Supporting international payment formats- Supporting international payment processes

• Having operating units in countries with different currencies- Consolidated, management and statutory

reporting- Functional currency different from country

currency- Reconciling the sub-ledgers

Dealing With Currencies


12

• Enterprise Edition helps with- Process, pay and receive money in any

currency- Downloadable drivers on QAD Store- Financial shared services- Second base currency- Report in any presentation currency- Business Intelligence

Dealing With Currencies


13

• Running consolidated reporting during the month

• Faster closing of books• Easier analysis and verification of figures• Tracking of intercompany relationships in

order to efficiently perform eliminations

Producing Consolidated Financial Reports


14

• Enterprise Edition helps with- Period close marks- Multi-layer accounting- Dedicated posting segment for intercompany

code- Reporting of intercompany transactions- Financial Report Writer- Allocations- Business Intelligence

Producing Consolidated Financial Reports


15

• Meeting local legal requirements• Internal controls• Enterprise Edition helps with

- Segregation of duties- Automated checks and balances- QAD Internationalization/QAD Store

Managing (Global) Compliance


16

• Improve efficiency by- Economies of scale / harmonized processes- Increase corporate control over business units- Increase customer / supplier visibility- Free up working capital / increase cash flow- Allow business units to focus on core activities

• Enterprise Edition helps with- Support of cross-company payment processing- Central management of customers/suppliers

using shared sets- Support for intercompany transactions

Introducing Shared Services


17

• Less customization means easy upgrades and less risk

• Enterprise Edition helps with- Configuration options

• Browses and Browse collections• Design mode/simplified screens• Report Framework modified reports

- New functionality in complete suite- Non-intrusive customization options

Limiting Customizations


18

• QAD Enterprise Applications is not the only solution in your company- Need to easily integrate with other solutions

• Enterprise Edition helps with- Support for Web services/XML- QXtend- QAD Store: connectors

Managing the Company IT Eco System


19

Upgrade Approaches


20

•Setup master data still fits the needs?

•Master data is still in good shape?

•Historical data correct & important?

Data

•Business concept and processes still OK?

•New functionality to improve processes?

•Future plans can be covered?

Process

•Which customizations can be eliminated?

•Can customizations replaced by standard?

•Can Browses/BI replace custom queries?

•Can custom layouts use the Report Framework

Customization

Questions to Ask

Migrating from SE to EE: Upgrade approaches

21

• Technical migration (1:1 conversion)• Reload master data in new database• Re-implementation• Mix-mode:

- Technical migration- Financial implementation- Optional change/split of domains

Types of Migration

Migrating from SE to EE: Upgrade approaches

22

Experience From the Field


23

• Characteristics- Data setup still fits the needs- Historical data important to keep

• Solution- Technical migration

• Benefits- Short lead time- Low cost

Raypak

Migrating from SE to EE: Experience from the field

24

Technical Migration


New DB

Converted

data

Old DB

25

• Characteristics- Change and clean up of data- Historical data in new database is not required

• Solution- Reload

• Benefits- New clean data setup- Better use of new functionality- Allows for optimizing future efficiency

Royal Sanders


26

Reload


New DB

Sharedsets

Old DB

Data entry

Domain1

Overallmaster data

27

• Characteristics- Business concept and processes changed- Master data setup changed- Historical data in new database is not required- Desire for new functionality- Standardization is a driver

• Solution- Re-implementation & re-load

• Benefits- New business model in place- New standardized data setup- Optimized use of functionality

Beaphar


28

Re-Implementation & Re-load


Domain1

New DB

Sharedsets

Overallmaster data

Data load

Domain2

Domain3

Old DB

29

HSV


• Characteristics- Operational data setup still fits the needs- Historical data important to keep- Financial Setup change to benefit of new EF

• Move some sites/entities into separate domains

- Some services is required to establish this mix

• Solution- Mixed-Mode- Operational part converted using standard conversion

procedures- Financial opening balance

• Benefits- Historical data kept in new database- New financial setup and functionality- Shorter lead-time than with re-implementation

30

Mixed Mode


New DB

SharedSets

converteddata

Old DBChart ofAccounts

Balances

Newfinancials

Newfinancials

31

Impact on Your Business

Re-Implement

Mix-Mode

Re-Load

Flexibility

Du

rati

on

TechnicalMigration


32

Tools and Tips


QXtend Excelerator for Data Load• Excel based tool• User functions for query and update of

data• Grid view of data in the worksheets• Review any error

Migrating from SE to EE: Tools and tips

33

34

Process Maps


Customer

35

Process Maps

Operational Metrics

Compliance check points

Training

Tooltips


36

• Browse collections instead of:- Modified or umbrella screens

• Simplified screens/design mode with:- Fewer and controlled fields

• Browse instead of queries• Potential replacement with

enhancements/new modules in new versions

Reduce Customizations


37

• Report Framework/Crystal Reports:- Modify layout of standard reports and external

documents

Report Framework


38

Easy On Boarding


Industry Process Models

TemplatesR&D

Software Enhancements

Streamlined Methodologies

Tools

Project Role Changes

39

• Why upgrade?• Migrate to a more Effective Enterprise• Approaches• Experience from the field

Summary


40

• Attend these related sessions:- Training QAD Enterprise Financials at Explore

(Thursday afternoon and Friday morning)

• Stop by the Solutions Expo• Q-Scan

Next Steps


Q-Scan Scope plan & budget

benefits case

QAD 2012

41

René BergkampVice-President of R&D, Financials - QAD [email protected]

Questions & Answers


migrating from se to ee rené bergkamp vice-president of r&d, financials - qad qad explore 2012

Documents

ee slide

effective enterprise

enterprise edition

effective planning

desired standardization

systems standardization

financials qad qad

financial reporting