We present to you some of the diagnostic tools available in Sage 300 ERP used for monitoring, tuning, diagnosing and solving issues that arise in the field. In addition, we provide a couple of exercises so you can view how the tools can come in useful for diagnostic purposes.

1. Sage 300 ERP
Technical Tour of Diagnostic Tools

2. CPE Credit
• In order to receive CPE credit for this session, you must be present for the entire
session.
– Session Code: C-137
– Recommended CPE Credit = 1.5
– Delivery Method = Hands-on
– Field of Study = Specialized Knowledge and Applications
• Visit the Sage Summit Connect kiosks to enter CPE credit during the conference.
#SageSummit

3. Introduction
• Simon Millichip – Supervisor, Customer Support Sage 300 ERP
• This session will provide details on tools for Monitoring, Tuning, Diagnosing, and
solving issues that arise in the field for Sage 300 ERP.
• Follow us @Sage_Summit
– Use the official Summit hashtag: #SageSummit
• Follow Sage 300 ERP Customer Support: @sage300erpcs
#SageSummit

4. Agenda
• Architecture
• COM Spy
• DBSpy
• RVSpy
• Exercises
• Q&A
#SageSummit

5. Sage 300 ERP Architecture
• Sage 300 ERP uses a “3-tiered layered architecture”
• Meaning 3 distinct layers that interact with each other:
User Interface
Views
Database
• Screens for the user to interact with
Sage 300 ERP
• Business Logic to calculate values
• Provides access to the underlying
Data

6. • View Layer
• A “View” is an specific term for the module of business logic that
maps to a database table
• Think of like a screen that gets input, processes it, and then
outputs it
• Database Layer
• View layer uses this layer to talk to the database
• Sage 300 ERP just saves and retrieves data to/from the Database
Sage 300 ERP Architecture

7. COM Spy
DBSpy
RVSpy
COM Spy
Sage 300 ERP Architecture

8. COM Spy
• Formerly know as the Accpac Spy
• COM Spy should be able to diagnose problems with the
various COM and ActiveX controls that make up a UI form
• Screens (UIs) are made up of “Active X controls” including:
• Text boxes (AccpacFieldControl)
• Lists/Grids (AccpacViewList / AccpacGrid)
• Buttons
• Finders (AccpacFinder)
• etc.

9. Control Description
AccpacDataSource The Datasource sends information
to an attached View so that it can
be processed and saved in the
database.
AccpacFieldEditControl Text boxes that allow user input.
They send the input to an attached
Datasource
AccpacViewList A table that you can enter entries
into and provide information in
each cell. This information is sent
to an attached Datasource
User Interface Controls

10. AccpacFieldEditControl
AccpacViewList AccpacDataSource
(not visible)

11. DBSpy
• DBSpy records everything that happens at the Database Layer
• It is good for diagnosing problems with the database server
• It records every error from the database even if they don’t
make it up to be displayed at the UI level
• Enhanced logging:
– For SQL Server or Oracle
– A4W.INI
– [A4WSQLS]
– Logdetails=271232

12. DBSpy
• Common functions:
– OPEN-TABLE
– SELECT
– FETCH
– Etc.
• Return codes for functions could tell if there is a problem
– DBS_NO_MORE_DATA
• No more records to fetch, might not be a problem
– DBS_NOT_FOUND
• Cannot find a record requested, could indicate a problem

13. RVSpy
• RVSpy records everything that happens at the Business Logic
Layer:
• Records operations on all application views, including 3rd party
applications
• Can include DBSpy output to show what database calls are
made for a particular view call
• Views are identified by View IDs
– First 2 characters are always the application prefix so you can
determine if a view is Sage 300 ERP or a 3rd party application

14. RVSpy
• Common return codes for functions
– 0 = success
– 1 = Warning
– 1020 = RECORD_NOT_FOUND
– 1024 = RECORD_INVALID
– 1026 = RECORD_CONFLICT (Record modified by another user)
– 1041 = TABLE_NOT_FOUND
– 1120 = KEY_INVALID

15. Hands On Exercise’s
• We will run through two exercises so you can view how the
tools can come in useful for diagnostic purposes.
• We will be using data sets RVSPY1 and RVSPY2 to perform
these.

16. Exercise 1
1) Launch Sage 300 ERP 2012
2) Open company RVSPY1
3) Launch the Order Entry UI
4) Open up DBSpy
5) Re-Launch the Order Entry UI and then review the DBSpy Log

17. Exercise 2
1) Launch Sage 300 ERP 2012
2) Open company RVSPY2
3) Run Day End Processing
4) Open up RVSpy
5) Re-run DEP then review the RVSpy Log

18. Q&A

19. Your Feedback is Important to Us!
• Completing a session survey is fast and easy:
Complete the survey on your mobile phone, laptop, or tablet
through the Sage Summit mobile app.
– IOS, Blackberry, or Android users may download the app from the
at the App Store by searching “Sage Summit”.
• Remember each completed survey is another entry for one of several daily prize
drawings, including an Apple iPad!
• Your feedback helps us improve future sessions and presentation techniques.
• Session code for this session: C-137
#SageSummit

20. #SageSummit
Contact Information
• Presenter Contact Information:
– Simon Millichip
– Simon.millichip@sage.com
– Follow Sage 300 ERP Customer Support: @sage300erpcs
• Follow us @Sage_Summit
– Use the official Sage Summit hashtag: #SageSummit
• Don’t forget to use the Sage Summit mobile or web app for all your conference needs.
Thank you for your participation.