The approach would be to copy all Production Master Data to UNIT TEST.
Initially, a Configuration Copy of Master Configuration will be carried out over UNIT TEST. This will
delete all master and transaction data. A Request/Model will be set up in Intedex to extract all
master data from Production and write it to UNIT TEST. This Model can be re-used to refresh the
data to avoid tampered data and keep it current with Production.
Advantages of extracting Production data to UNIT TEST with Intedex
|
Advantage
|
Description
|
Return
|
|
Testing Integrity
|
Minimal errors in testing due to correct
master data setup
|
Improved Service
Level
|
|
Accurate error tracking
|
Accurate replication of Production issue
using same Customer, Vendor, Material
etc
|
Reduced effect on
Business and less
Consulting Hours
|
|
Speed to Repair
|
No need to waste time trying to create
master data to get a true snapshot of
the error. Reduction in multiple
transports
|
Reduced effect on
Business and less
Consulting Hours
|
|
Reduction in Transports
|
Less transports to fix issue. Accurate
unit testing occurs in Development and
not only in TEST
|
Less Basis Consulting
Hours
|
|
Less need for Retesting
|
Accurate unit testing occurs in
Development and not only in TEST
|
Less Functional
Consulting Hours
|
|
Testing Scripts
|
Created in Development with
Production Data means no need for
data conversion when transported to
TEST
|
Less Functional
Consulting Hours
|
|
Training Scripts
|
Created in Development with
Production Data means no need for
data conversion when transported to
TEST
|
Less Functional
Consulting Hours
|
|
Support for new
dimension initiatives
(CRM,APO etc)
|
Representative data is uploaded to
these systems accelerating the
implementation
|
Less Functional
Consulting Hours
Data integrity
improving overall
speed of
implementation
|
Previous
Next 
