SYSPRO Data Viewer

SYSPRO Business Activity Queries are SQL views that are created in the relevant company databases and (because they are defined in SYSPRO) are recognized as data sources. They provide a view into the business data commonly used during the typical business management process. The queries are built and secured in the core ERP system and then surfaced to users via their enterprise reporting and connectivity solutions.

Business insight tiles (also called insight tiles or just tiles) are essentially SQL scripts displayed in a tile format within a SYSPRO web view. These tiles are context-driven and let you act instantly on events, facilitating informed business decisions and sound business behavior.

KPIs on tiles can be used to highlight values approaching or exceeding pre-determined objectives or thresholds. This lets you proactively keep an eye on approaching targets. These targets could be a certain value, company-wide goal or a specific target agreed for a person or a role within the organization.

In the context of SYSPRO Business insight tiles and SYSPRO Business Activity Queries, a data source can be considered as one of the following:

• SYSPRO base table (e.g. InvMaster)

• SYSPRO custom form table (e.g. InvMaster+)

• SYSPRO Business View

• User defined base table (i.e. any base table in the current database that is not part of the standard SYSPRO database)

• User defined custom form table (i.e. any base table defined with a trailing + sign that doesn't form part of the standard custom table definitions)

• User defined views (i.e. any view in the company database that is not defined as a SYSPRO Business View)

In SQL, a view is a virtual table whose contents are defined by a query. Like a table, a view consists of a set of named columns and rows of data.

Unless indexed, a view does not exist as a stored set of data values in a database. The rows and columns of data come from tables referenced in the query defining the view and are produced dynamically when the view is referenced.

A view acts as a filter on the underlying tables referenced in the view. The query that defines the view can be from one or more tables or from other views in the current or other databases.

Examples of what views can be used for:

• To focus, simplify and customize the perception each user has of the database.

• As security mechanisms by letting users access data through the view, without granting the users permissions to directly access the underlying base tables of the view.

• To provide a backward compatible interface to emulate a table that used to exist but whose schema has changed.

You can restrict operator access to programs by assigning them to groups and applying access control against the group (configured using the Operator Groups program).

You can restrict operator access to programs by assigning them to roles and applying access control against the role (configured using the Role Management program).