Data Integrity Monitoring

1
Data Integrity Monitoring
Brown Brothers Milawa Vineyard Pty Ltd
2
Overview

• Brown Brothers
• Family owned Wine Company located in North
  East Victoria
• JDEdwards since July 1999
• OneWorld Xe
• Update 6, Service Pack 21
• Financials, Distribution, Manufacturing,Demand
  Consensus

3
Overview

• The pursuit of Data Integrity across an ERP
  system is an ongoing process but is essential for
  the proper working of the software and the
  business processes that are dependant upon it..
  
• Address Book, Customer Master, Item Master, Item
  Branch set up and Category Codes.
• Unit of Measure Conversions in the Item Master.
• Item Ledger to General Ledger integrity.
• Sales Orders Stuck at statuses.
• Works orders advanced to statuses but no Parts
  List.
• Sales Order History ex F42119 vs General Ledger.
• QOH vs Item Ledger
• Item physical attributes - EAN type data, for
  current and pending configuration.
• Etc., etc

4
Overview

• This presentation explores the approach taken at
  Brown Brothers to implement a Data Integrity
  Monitoring Scheme that seeks to minimise the
  instances and the impact of Data Integrity
  Issues.
• Originally had a series of reports published but
  because people had to remember to go and look at
  them it ultimately did not work well.
• First step was to design a Cover sheet that
  allocated responsibility, linked to Reports and
  Work Instructions and was part of our normal
  Business Management (Quality) System.
• Second step was to design and implement a system
  whereby staff would get Emailed copies of
  Integrity reports by exception. The Emails
  contain embedded links to the Reports themselves
  and again the Work Instructions.

5
Overview

• The monitoring scheme uses a combination of third
  party tools to provide Data Integrity Reports, on
  a by exception basis, to the relevant staff along
  with links to Work Instructions on how to rectify
  the situation.
• Cognos Impromptu, PowerPlay or Microsoft Query
  form the basis of the suite of reporting tools
  used at Brown Brothers.
• Access front end into SQL database for the Report
  Register.
• SQL
• Email.

6
Overview

• The Data Integrity Monitoring Scheme also
  provides summary reports that can be used for
  trending and analysis.
• Use of Cognos PowerPlay to generate Cubes which
  are published across the Intranet.

7
AGENDA

• The Scheme Cover Sheet
• The Data Integrity Reports
• The Work Instructions
• The Count Reports
• The Database
• The Messaging system.
• The Trending and Analysis.

8
Data Integrity Monitoring Scheme

• 1) The Data Integrity monitoring Scheme HACCP
  chart
• (Hazard Analysis of Critical Control Points)
• Report Id Description.
• Report Schedule Frequency and by whom.
• Review and Action by Whom and Frequency.
• System Description.
• Link to Work Instructions.
• Link to report.

9
HACCP Chart Data integrity Monitoring Scheme
10
Data Integrity Monitoring Scheme

• 2) The Data Integrity Reports
• Impromptu reports published as pdf.
• Nightly Schedule
• Ability to access all reports via the Intranet

11
Data Integrity Monitoring Scheme

• 3) The Work Instructions
• Each Integrity Report has a Work Instruction
  that-
• Identifies the report.
• Explains the logic and the intent.
• Explains what to do to rectify the situation.

12
Data Integrity Monitoring Scheme

• Report NameIR1 WO 46 - Blank Parts List
• Report NumberIR1
• Reporting Tool Impromptu
• Database Id 1.csv
• Report Logic
• This report looks at all Manufacturing Works
  Orders at a status of 46 and returns a record if
  there is no Parts List attached to the Works
  Order.
• Background and Instructions if there are records
  which require to be rectified.
• If a Works order is processed through the system
  without a Parts List and is backflushed there
  will be no Components issued. To rectify the
  situation the Works Order must have its status
  returned to 42 - at this point it must be
  remembered to Freeze the Works Order again so
  that it will be included in the next MRP
  regeneration. After this has been done MRP needs
  to be regenerated again.

13
Data Integrity Monitoring Scheme

• 4) The Count Reports
• Each Impromptu report has an accompanying
  impromptu report which does not contain any logic
  of its own.
• This second report simply counts the number of
  records returned in its parent report and
  publishes the result as a .csv file in a standard
  format.

14
AGENDA
15
Data Integrity Monitoring Scheme
16
Data Integrity Monitoring Scheme

• The Database
• SQL Database.
• Access front end.
• Drives
• Messaging
• Saving of Count reports into audit section for
  Reporting.
• Stops upload of data to EAN Net if necessary.
• Data repository for HACCP Chart.

17
Data Integrity Monitoring Scheme
18
Data Integrity Monitoring Scheme

• The Messaging system.
• Once per day a macro is run that -
• Saves all the pdf reports into a file.
• Saves all count .csv reports into a file.
• Once this has occurred, all reports with greater
  than zero count are E-mailed to the recipients.
• Count reports are archived for reporting
  purposes.
• Other Processes are stopped if required.

19
Data Integrity Monitoring Scheme
20
Data Integrity Monitoring Scheme

• The Trending and Analysis.
• A Cognos PowerPlay Cube has been created across
  the archived report data to enable trending and
  analysis to take place.

21
HACCP Chart Data integrity Monitoring Scheme