ERP Implementation Checklist

Copyright - Alto CIM Services Ltd.

System testing and verification is a crucia l part of the system acceptance and is the
opportunity to ensure that the system meets all aspects of the specification. The programme
vendor will also use this as a means of gaining acceptance of the system and its installation
although a period of `live' use shoul d p r e c e d e a n y f o r m a l a c c e p t a n c e .

T e s t i n g s h o u l d b e c a r r i e d o u t i n a t e s t d a t a b a s e that must be populated with applicable data
that will be used in a live environment and not test data. Pre-configured test data should only
be used for testing the impact of system adjustm e n t s o r f o r t r a i n i n g p u r p o s e s o n c e t h e s y s t e m
is installed, established and operating correctly.

Testing should take the following form:

·

·
·
·
·
·

Parametric testing (eg Yields, AOQ, pan size, Unit of measure, source code
etc.)
BOM testing
Testing of transactions
Reports
MPS output validity (Single level and multi level if applicable)
MRP output validity (Full regeneration and net change)

The following table represents the minimum testing requirement in terms of processes and
transactions that should be verified as wo r k i n g c o r r e c t l y f o r system acceptance:

Item

1.1
1.2
1.3
1.4

1.5
1.6
1.7
1.8
1.9
1.10
1.11
1.12
1.13

Demand sources
Product configurations
Forecast consumption
System triggers (credit limit exceeded,
escalation of overdue orders, kanbans
etc.)
Inventory movements
Re-order points
Time fencing
Reschedule and order action validity
Capacity limits, workstation loading
Pick logic
Ship consolidation logic
Cycle count logic
Sales order price field "pick-up" from
pricing table
Continued

1.2-C18465

2