1. “All Lawson, All the Time!”
Helvetica 24pt. bold
1/2/2019
Upgrade Planning
“All Lawson, All the Time!”
1/2/2019

2. Why Upgrade? Decommission Timing of Upgrade 7.2.x Applications
Helvetica 24pt. bold
1/2/2019
Why Upgrade?
Decommission
7.2.x Applications
7.2.x SEA Applications
Logan – Internet Object Services 7.3
7.3.3 Environment
7.2.x Applications and 7.3.x Environment off support
Timing of Upgrade
Customers wishing to upgrade at quarter-end or year-end
Large backlog at year end is possible
Multiple conversions required – waiting could cause bottleneck in available certified upgrade providers
1/2/2019

3. Product Release Requirements
Helvetica 24pt. bold
1/2/2019
Product Release Requirements
Applications
7.2.4 is the minimum application release required to move to 8.0.x
7.2.3 and earlier releases must first apply cyclicals to get to 7.2.4
7.2.4 & can upgrade directly to 8.02 or 8.03 depending on Environment
Environment
7.3.3_ESP8 or 8.01_ESP1 required to move to 8.02
8.01_ESP2 required to move to 8.03
Summary
The upgrade process may require various system administration services (patches, cyclicals, other upgrades)
Apps, Environments, Database, O/S
1/2/2019

4. Evaluate Upgrade Environment(s)
Helvetica 24pt. bold
1/2/2019
Evaluate Upgrade Environment(s)
Current Production
Continued processing requirements
Test
Initial upgrade test
Second upgrade test
Final upgrade
Training
Changes in current process
New functionality
Sufficient HW capacity?
Internal tech support?
Production Server
Prod & Test DB Server
Test Server
Tape Library
1/2/2019

5. Evaluate Upgrade Environment(s) - continued
Helvetica 24pt. bold
1/2/2019
Evaluate Upgrade Environment(s) - continued
Development
Modification development
Interface development
Other Custom Development
Other Upgrade Environments
Operating System
Database
COBOL and C compilers, MSKTool Kit
IOS, SEA, any other applications
1/2/2019

6. Upgrade Environment Usage – What it Looks Like
Helvetica 24pt. bold
1/2/2019
Upgrade Environment Usage – What it Looks Like
1/2/2019

7. Helvetica 24pt. bold
1/2/2019
Analyze DB Changes
1/2/2019

8. Upgrade Project – The 16 Steps
Helvetica 24pt. bold
1/2/2019
Upgrade Project – The 16 Steps
Steps 1 – 4 (Technical)
These Steps Involve Copying the Database to the New Upgrade Environment and Product Lines
Step 5 (Functional)
Run the Setup Programs
Step 6 (Functional)
Run Prejob Programs
Steps 7 – 12 (Technical)
Unload of 7.2x Data
Load to the 8.x Data Structure
1/2/2019

9. Upgrade Project – The 16 Steps
Helvetica 24pt. bold
1/2/2019
Upgrade Project – The 16 Steps
Step 13 (Functional)
Run Postjob Programs
Step (Technical)
Backup and Verification of Record Counts
Step 16 (Functional and Technical)
Verify Upgrade Data
1/2/2019

10. Project Management Tools Operations Tools
Helvetica 24pt. bold
1/2/2019
Upgrade Tools
Project Management Tools
Project Definitions:
Roles
Expectations
Timeframes
Budget
Reporting
Project Plan
Issues List
Project Management DB
Operations Tools
Upgrade procedures
Document Modifications
Script Documentation
Upgrade Log
End User Tools
Data Considerations
Upgrade Setup Decisions
Procedure Documentation
Testing Guidelines
Security Setup Procedures
Validation documentation
1/2/2019

11. Intellectual Property Library
Helvetica 24pt. bold
1/2/2019
Intellectual Property Library
Certified Interfaces
Report Libraries
Source Code Control Tools – ZZRC
Testing Scripts
1/2/2019

12. Lessons Learned - Environment
Helvetica 24pt. bold
1/2/2019
Lessons Learned - Environment
MSP levels in sync in environments (patches also)
Apply MSP #6 at a minimum
MSP must be applied prior to upgrade being run (PR issues)
Jobdefs can be copied from DEV80 to PROD80
Security changed enough that you need to review it in detail BEFORE you start the upgrade
1/2/2019

13. Lessons Learned - Application
Helvetica 24pt. bold
1/2/2019
Lessons Learned - Application
PR customers: review BSI closely-spend time to test/clean up employee address information
Setting up locations: can use website
Attend training before/as part of the planning
BR users: ATTEND TRAINING
Look closely at 3rd party software and any upgrades needed
Allow time for interface validation (especially if sending files to providers)
Be sure to test EVERYTHING-Reports, forms output. Processes.
1/2/2019

14. Lessons Learned - Application
Helvetica 24pt. bold
1/2/2019
Lessons Learned - Application
AC users: Insert summary level before project start & rebuild structure
Procurement Training – Major differences
Matching Training – Major differences
Comments – new attachment files
HR – Location codes now used by BSI (HR04)
Parallel Run recommended for PR users
Set-up Invoice Handling Code (MA05) to default on AP Process level
Review Procurement Codes – Multiple companies
1/2/2019

15. All data must be prepared before upgrade (data considerations)
Helvetica 24pt. bold
1/2/2019
Lessons Learned - Data
All data must be prepared before upgrade (data considerations)
Allow time to clean up current data/purge/delete
Test out small samples first, then move onto the larger files
1/2/2019

16. Lessons Learned – Project Planning
Helvetica 24pt. bold
1/2/2019
Lessons Learned – Project Planning
Modify process so that user involvement is eliminated during upgrade process
Changes set up in spreadsheets (ex. Input into UG25)
Review customization documentation - if incorrect, takes time to isolate and update documentation
Resolution of error - identify the root of the problem/ upgrade or 8.0 issue?
Testing is sooooooo important. Need scripts to do this (keep for future usage)
Allow time to handle bug issues
Internal Constraints: month-end/year-end, vacation, training
1/2/2019

17. Additional Considerations
Helvetica 24pt. bold
1/2/2019
Additional Considerations
Run DVP’s in Production ENV – Procurement or Distribution Users
Upgrade Phases
Preparation
Upgrade
Job Completion times
Lead times
Verify that each job has “Completed” without errors before running the next on-line program
Check job logs and print file for messages
1/2/2019

18. Options: In-House, Remote or Never Again?
Helvetica 24pt. bold
1/2/2019
Options: In-House, Remote or Never Again?
Traditional – In House
Do it yourself…use your own Technical & Functional experts
Use an Upgrade Partner - experts with multiple upgrade experience
Use your own customer supplied hardware
Remote – Efficient Off-site Upgrade
Copy Customer Configuration to netASPx Operations Center
Upgrade within ASP on netASPx hardware
Test over Secure VPN Connection
Copy Upgraded Configuration to Customer location
Application Service Provider
Migrate to netASPx and free upgrades provided for life of agreement
1/2/2019

19. “All Lawson, All the Time!”
Helvetica 24pt. bold
1/2/2019
Questions?
Upgrade Planning
“All Lawson, All the Time!”
1/2/2019