Integrating Legacy Applications with JD Edwards ... · • Extend existing webMethods Middleware...

Integrating Legacy Applications with JD Edwards

Wednesday, November 17, 2015

Opportunities and Challenges

Introduction

2© Deloitte LLP and affiliated entities.

Alan is Project Manager for Integrations for Canfor Corporate IT and has extensive ERP integration and migration experience focused in manufacturing and process control automation, B2B connectivity, A2A interface standardization, and integration integrity and governance.

He has over 30 years of experience in design, programming, project management, and application architecture with a wide range of ERP systems including JDE, Epicor, SAP, Baan, PowerMAN, and Protean.

Alan CondonProject Manager -Integrations

Integrations ManagerProject Edge Role:

Sid has over 17 years of consulting experience that includes ERP assessments, business process redesign, net new implementations upgrades of ERP Applications, transition planning and project management. He has over 15 years’ experience implementing various releases of Oracle JD Edwards EnterpriseOne software for companies of all sizes in countries such as India, Singapore, Malaysia, Thailand, Philippines, Australia, New Zealand, USA Canada.

Sid AryaSenior Manager

Project Manager & Solution LeadProject Edge Role:

• Lumber capacity: 6 billion board feet• 12 mills in British Columbia• 1 in Alberta• 17 operations in U.S. South

Lumber Mills• 3 - South Carolina • 1 - North Carolina• 3 - Georgia• 3 - Alabama• 1 - Mississippi• 1 – ArkansasOther• 2 - Laminating Plants -

Arkansas & Georgia• 1 Re-Manufacturing Mill -

South Carolina• 2 Chip Mills - Texas &

Louisiana• 6500 employees

About: Canfor

Pulp and Paper Operations3 Kraft Pulp & 1 Paper mill in central BC + 1 BCTMP mill in BC north

Market pulp capacity: 1.1 million tonnesKraft paper capacity: 140,000 tonnes

One of the Largest Integrated Forest Companies

C A N F O R C O R P O R A T I O N

Canfor is one of the few primary lumber manufacturers to offer

products third-party certified to all of the independent certification programs

in North America

Percentage of Production

CSA FSC SFI Total

Canadian mills 85% 10% 5% 100%

US mills - - 100% 100%

Our success depends on the well‐being of the forests we manage. Through all of our forest management activities, our skilled forest professionals protect:

‐ Biodiversity‐ Species at risk‐ Wildlife‐ Other Forest Values

A World Leader in Sustainable Forestry

IntroductionCanfor Project EDGE


In January 2012 Canfor undertook an initiative to replace a legacy business system with the implementation of Oracle JD Edwards EnterpriseOne 9.1 (Tools 9.1.4), Oracle Transportation Management 6.3.2, Oracle’s Demantra 7.3.1.4, .NET application modules and Oracle Business Intelligence 11.1.1.6.8.

The combined solution of Oracle’s JDE E1 & OTM was based on a business need for:• Greater logistics and transportation planning capabilities• Improved inventory planning and management• Financial net revenue projections and integration with their existing financial history

• On June 30th 2014 Phase 1 of the EDGE program was implemented for Canfor Canadian lumber operations

• Planning began in Nov. 2014 for Phase 2 of the program which extended the core system to include the functionality for US South lumber operations

• Phase 2 was delivered on time / on budget on Sep 28th 2015

Canfor partnered with Deloitte to implement the Oracle systems.

Project Timeline – Phase 1Introduction


7

6

7

8

28

0 5 10 15 20 25

Total

D

C

B

A

MONTHS

PHA

SE

Design

Build

Deliver

Operate

Application Footprint – Phase 1Introduction


Identifying opportunities to accelerate configuration and documentation activities was particularly beneficial due to the scope of work:

• Configuring 10 JDE Modules• Developing 95 JDE WFRICE

objects• Documenting system

configuration in Design Books• Developing knowledge transfer

and training documentation

Project Timeline – Phase 2Introduction


1

3

4

3

11

0 1 2 3 4 5 6 7 8 9 10 11

Total

E

D

C

B

A

MONTHS

PHA

SE

Design

Build

Deliver

Operate

EDGE Applications


Canfor’s Legacy Applications


S# Application Purpose Importance to Canfor Final Disposition

1 Kronos Payroll & Garnishments system

Payroll, HR, and Human Resource Management

Retained – Integrated with JDE

2 Infor MP2 – Material Planning

MRO system Mills and Plant manage all Work Order and Purchase Orders with this system


3 Log Procurement Log Purchasing and Tract Management system

Custom application specific to USS operations Log operations


4 iNSELS – Integrated New South Express Logistics System

Trucking FleetManagement & Backhaul Invoices

Manages dispatch operations for Fleet and Drivers (Canfor employees) including Backhaul business

Retained – Integrated with OTM/JDE

5 FAS – Fixed Asset System Depreciation and Fixed Asset Management System

Retained – No integration to JDE – uses Manual JE’s

6 DGS – Data Gathering System

Lumber Production data collection

Leverage existing production data collection investment


7 Koppers Wood Treating System

Treated Lumber Processing data collection

Provide connection of treating process to availability of inventory status

Retained – Integrated with JDE through DGS

8 7i MRO System Implementation deferred to Phase 3

9 ADP Payroll system Implementation deferred to Phase 3

Legacy Diagram


Challenges


Challenges faced by the Solution and Integration Teams:

• Canfor did not own the source code for 2 of the legacy applications, however limited direct database accessibility and modification was available.

• Custom data tables and views

• Stored Procedures and Triggers

• Where Canfor had application source code, a full re-write of the applications or a request to extensively customize them was not feasible. Almost certainly would not fit into the project schedule.

• All Legacy applications relied on some combination of master data from the former ERP system (Vendor, Customer, GL Accounts, etc) and were dependant on the architecture of this master data.

• Real-time translation and cross reference of legacy data to JDE master data would be necessary.

• Needed to leveraged the stability of the existing interfaces to accounting to lessen our risk and meet the project timeline.

Opportunities


• Use Standard JDE and OTM interfacing mechanisms

• Leverage proven functionality not in OTM or JDE, and retained through the integration of the legacy applications.

• Extend existing webMethods Middleware architecture already in-place for B2B and A2A interfaces at Canfor for the integration of legacy applications

• Create a “bridge” between legacy stack and oracle stack that can be leveraged for future implementations and acquisitions (Canfor Pulp, Scotch Gulf, Anthony Lumber, etc.)

• Design EDGE Bridge to provide cross-reference mechanisms to associate OTM/JDE standard with master data of legacy apps GL Account codes, vendor numbers, customer codes, etc.

• Auditing capabilities for all legacy app transactions and data transformation

• Provide meaningful error notifications across systems

Interfaces


Interface Purpose Type of Data

Master JDE - Vendor Master Send Vendor Master data from JDE to EDGE Bridge Master Data

Master JDE - Customer Master Send Customer Master data from JDE to EDGE Bridge Master Data

Payroll Payroll to JDE General Ledger

Periodic Payroll JE’s from Kronos system to JDE General Ledger Transactional Data

Payroll Garnishment to JDEAccounts Payable

Periodic vouchers for Garnishment Payment for employees from Kronos system to JDE Accounts Payable

Transactional Data

Log Procure

Log Procurement Voucher to JDE Accounts Payable

Vouchers for Log settlements from Log Procurement system to JDE Accounts Payable

Transactional Data

MRO MRO Inventory Adjustment to JDE General Ledger

Daily transfer of Inventory adjustment information from MP2 system to JDE General Ledger

Transactional Data

MRO MRO Purchases to JDEPurchase Order

Daily MRO Purchase Receipts from MP2 system to JDE Procurement Transactional Data

iNSELS iNSELS Backhaul Invoice JDE Accounts Receivable

Invoices for Freight charges from iNSELS to JDE Accounts Receivable and General Ledger

Transactional Data

iNSELS OTM – Tender Offer Brings initial shipment request from OTM to Trucking Company – iNSELS can Accept or Reject

Transactional Data

iNSELS OTM – Tender Response Sends message to OTM to Accept or Reject Tender Offer shipment Transactional Data

iNSELS OTM – Planned Shipment Updates iNSELS with status and shipment information from OTM to keep iNSELS in sync

Transactional Data

iNSELS OTM – Shipment Actuals Updates OTM with shipment weights, equipment numbers and other bill of lading information

Transactional Data

iNSELS OTM – Shipment Status Updates OTM with shipment progress status information allowing customers to view in OTM Customer Portal

Transactional Data

JDE/OTM to Legacy Legacy to JDE/OTM

EDGE Bridge


Vendor Master to JDE Bridge


F0101Z2

F0401Z1

F0111Z1

F0115Z1

R5604Z1 F5501Z1

Edge_Stage_apmaster

Custom Batch to extract information from Address Book JDE Interoperatibiliy tables

Customer Master to JDE Bridge


F0101Z2

F03012Z1

F0111Z1

F0115Z1

R5603BZ1 F5603002

Edge_Stage_armaster

Custom Batch to extract information from Address Book JDE Interoperatibiliy tables

Kronos to JDE General Ledger


1

Edge_Stage_GL F0911Z1R09110Z

F0911

Where tran_code = ‘H’

JDE General Ledger

Kronos Garnishments to JDE A/P


2

Edge_Stage_AP

F0411Z1

R04110ZA

F0411

Where class_code =

"GARN"

F0911Z1F0911

JDE General Ledger

JDE AP Ledger

MP2 to General Ledger


2

Edge_Stage_GL F0911Z1R09110Z

F0911

Where tran_code = ‘M’

JDE General Ledger

MP2 Receipts to JDE Procurement


EDGE_Stage_MP2Receipts

F4301Z1

F4311Z1

F47071

F47072

R5500002 – A custom batch reused from Phase 1 used to call several other batch programs in a sequence

R4311Z1I

R47071

F4301

F4311

F4311

F43121

PO Header & Detail

PO Detail & Receiver

Log Procurement to JDE A/P


2

Edge_Stage_AP

F0411Z1

R04110ZA

F0411

F0911Z1F0911

Where class_code =

%LOGS%

JDE General Ledger

JDE AP Ledger

iNSELS Invoice to JDE A/R, G/L


2

Edge_Stage_AR

F03B11Z1

R03B11Z1A

F03B11

F0911Z1F0911

JDE AR Ledger

JDE General Ledger

What worked well?


• Analyst and Programmer resources worked well all the phases – agile approach

• Process and Terminology was a big challenge for the technical experts

• Geographic spread of the team

• Shared IT resources - mitigation

• Coordination

• PO Receipts – custom – challenge

• Did not test for every possible scenarioFew disconnects

• Integrity and notification of errors – to guarantee integrating between systems

• Proactive error reporting through WebMethods

Combined Design & Build: 4 mo’s Confirm process model and detailed architectureDevelop project plans for Environment and migration, UAT and Training/Change ManagementFull package configurationData Conversion completed for Master Data and for sample sets of transaction data Complete the Build scope identified to date• Local interfaces• Specific technical objects for this regions (versions,

workflows, etc.)Full end to end detailed Conference Room Pilot to complete detailed fit/gap analysisCompleted functional specification and development for all new WFRICE Completed Unit/Integrated TestsComplete Regression testing as items are finished INT testingDevelop any training and UAT materials

Deliver / Go-Live: 3 mo’s TBC* Complete all User Acceptance and any outstanding

Regression testing and issue resolution System performance testing Complete all data conversion Deliver all training materials Mock cut-over rehearsals Implement post go-live support organization and perform

knowledge transfer 3 day cut over event

Post Production Support: 1 ½ mo’s Issue resolution and ongoing knowledge transfer and

follow-up training

Comparison to Previous Phases Phase 1: 22 months Phase 2: 13 months

Phase 3 – Setup for Success

Questions & Answers


Deloitte, one of Canada's leading professional services firms, provides audit, tax, consulting, and financial advisory services. Deloitte LLP, an Ontario limited liability partnership, is the Canadian member firm of Deloitte Touche Tohmatsu Limited.

Deloitte refers to one or more of Deloitte Touche Tohmatsu Limited, a UK private company limited by guarantee, and its network of member firms, each of which is a legally separate and independent entity. Please see www.deloitte.com/about for a detailed description of the legal structure of Deloitte Touche Tohmatsu Limited and its member firms.

The information contained herein is not intended to substitute for competent professional advice.

© Deloitte LLP and affiliated entities.

Integrating Legacy Applications with JD Edwards ... · • Extend existing webMethods Middleware...

Documents

Transcript of Integrating Legacy Applications with JD Edwards ... · • Extend existing webMethods Middleware...