Select Page
An Introduction to the SYSPRO Database

An Introduction to the SYSPRO Database

An Introduction to the SYSPRO SQL Database Structure

In the early versions of SYSPRO, the ERP’s data was entirely stored in C-ISAM files. These C-ISAM files were essentially text files containing system data. They could cause a lot of trouble if you had to investigate or troubleshoot data problems as they were lacking a stable framework to review and analyze them. Thankfully, a modern SQL database structure was introduced between SYSPRO 6.1 and 7. In today’s SYSPRO 8 version, essentially all components of the ERP have now been converted and are stored in traditional SQL database tables. Knowing what SYSPRO’s database looks like becomes a vital tool if you are tasked to troubleshoot data problems, analyze company data, or build SQL queries to pull data for custom reports.

SYSPRO SQL Database Structure

So what does a SYSPRO database structure look like? 

The “System-Wide” Database

Both SYSPRO 7 and SYSPRO 8 contain what SYSPRO calls the “system-wide” database. While the name of the database can be customized to the business’ liking, it is commonly named “sysprodb” by default. The database contains information about operators, administrative settings, system information, and licensing details. Any data pertaining to system-wide configurations that span all SYSPRO companies will be found in this database. Particularly important tables to take note of in this database are:

  • AdmOperator – Contains data of all operators on file in SYSPRO along with their role, group, and other access level details. 
  • AdmSysVersion – Header table containing the database version details of the SYSPRO environment.
  • SysproAdmin – Table containing a list of the companies in your SYSPRO environment. This table becomes relevant when creating test companies or setting up SYSPRO’s default test databases. 

The Company Databases

Each company created in SYSPRO will have its own database and default company tables. By default, SYSPRO names these companies ‘SysproCompany’ along with the company’s ID at the end. Ex, SysproCompanyT, SysproCompanyA, etc. These are the databases where your company’s transactional data is stored. 

At a first glance, these databases can be overwhelming. A standard SYSPRO database can have over 1000 tables in it. The good thing is that while this full list of tables compromises all of SYSPRO’s functionality, it is unlikely that your environment is both licensed and actively using SYSPRO’s full suite of products. This means that most of these tables will be empty and will not be worth much of your attention.

Instead, there are about 25 – 50 tables in any given environment that sees most of the action. To provide a cheat sheet, here are some of the commonly used tables in SYSPRO that are essential to the daily use of SYSPRO:

  • ApInvoice – Supplier invoices
  • ApSupplier – Supplier header details
  • ApSupplierAddr – Addresses for the suppliers
  • ArCustomer – Customer header details
  • ArInvoice – Customer invoices
  • ArTrnDetail – Details about each invoice. Used extensively for sales reporting
  • BomOperations – Operations against a BOM
  • BomStructure – Structure against a BOM
  • InvMaster – Master for all stock codes in SYSPRO
  • InvMovements – Inventory transaction details against each SKU
  • InvPrice – Sell prices against each SKU
  • InvWarehouse – Master table for inventory counts of each SKU
  • PorMasterHdr – Purchase order header
  • PorMasterDetail – Purchase order details
  • SorMaster – Sales order master
  • SorDetail – Sales order details
  • WipMaster – Master for jobs
  • WipJobAllLab – Labor details against jobs
  • WipJobAllMat – Material details against jobs
  • WipJobPost – History of material/labor issued to jobs

The “Deployment” Database

Unique to SYSPRO 8, this database handles information relating to the release version of your SYSPRO environment. The “SYSPRO 8 Installer” tool uses this database exclusively to verify which products are available to you and whether any recent updates have become available. In addition, it contains information about which machines have SYSPRO clients installed on them and which versions they have installed. 

Admins, do you grasp the SYSPRO database structure for efficient data troubleshooting and analysis?

This covers the databases you will see in a usual SYSPRO environment. Knowing what SYSPRO’s database structure looks like is essential for any SYSPRO admin to effectively be able to find, troubleshoot, and analyze vital company data. 

How to Handle Unknown Processes in SYSPRO

How to Handle Unknown Processes in SYSPRO

Handling Unknown Processes in SYSPRO as an ERP Administrator

In SYSPRO, an “Unknown Process” is the result of a SYSPRO client having lost its connection to the host server prematurely. When an unknown process is detected, it means that a process is still running on the host server despite the client connection having been disconnected. Unknown processes can occur in the event of network disruption or a SYSPRO client shutting down unexpectedly.

Unknown Processes in SYSPRO ERP Admin

While SYSPRO generally catches common disconnects and clears these processes gracefully, in some cases, a process may linger and be declared as a “runaway” process. From an administrative point of view, it is important to stay on top of unknown processes as they can hog up valuable resources for others and can cause general instability if they are not terminated on a regular basis. Additionally, unknown processes can even consume user licenses which can affect other operators’ access to SYSPRO if you have an environment with limited user licensing.

To monitor and terminate any current unknown processes, you can use SYSPRO’s “Users” (IMPUSN) program. You can access the program by going to Main Menu > Administration > Logout Users. This program displays a list of all currently signed-in operators using SYSPRO. On the left-hand side, there is a “Processes” pane that you can filter for “Unknown”. A list of unknown processes will be displayed in the pane once selected. If you have any unknown processes in your system, the “End All Unknown Processes…” button will be enabled. Clicking it will clear the hung processes on the application server, and the previously hogged up server resources will once again be available.

SYSPRO Unknown Processes

To monitor operators seeing frequent disconnects, you can use the built-in Client-Server Diagnostic program (IMPDG5). Note that this program can only be run from a client machine. You can also make use of the System Audit Query program (IMPJNS) where you are able to filter for various system-related events such as client-server disconnects. These tools are sure to provide you with detailed information about any potential operator seeing frequent disconnects or unexpected client shutdowns.

SYSPRO ERP System Audit Screen

Please be aware that terminating unknown processes is only a temporary solution to the potential problem that is causing them to begin with. Be sure to monitor the specific client machines or operators encountering frequent disconnects.

Here are some helpful tips to reduce the number of unknown processes seen in your SYSPRO environment:

  • Educate your users about the importance of exiting SYSPRO “gracefully”. Unless SYSPRO is unresponsive, do not shut down Windows or use the Task Manager to kill SYSPRO. 
  • Set a “timeout” value against operators so that SYSPRO disconnects the user after a given time of inactivity. This can be done through the “Operators” program (IMPBOP). 
  • Schedule a task that performs a logout of all users in SYSPRO at a time where the system is not in use (generally overnight). 
  • Stay up to date with available SYSPRO hotfixes and the latest SYSPRO product releases to remain within SYSPRO’s product support. New hotfixes are usually only developed for the latest versions of SYSPRO.  

Looking for help with your SYSPRO ERP environment?

As an ERP Administrator handling Unknown Processes in SYSPRO, you know it’s crucial to vigilantly manage and terminate these processes to prevent resource depletion and licensing issues. The “Users” and “Client-Server Diagnostic” programs offer valuable tools for monitoring and addressing disconnects and unexpected shutdowns. However, it’s essential to address the root causes by educating users on proper exit procedures, setting timeout values, scheduling logouts during system downtime, and staying updated with SYSPRO hotfixes and releases to maintain product support and stability. Proactive management ensures the efficient operation of your SYSPRO environment.

If you find managing SYSPRO ERP processes and maintaining system stability a challenging task, consider reaching out to our team at EstesGroup. With our expertise in SYSPRO ERP consulting and our comprehensive suite of managed cloud and IT services, we can provide the support you need to streamline your operations, optimize performance, and ensure the smooth functioning of your SYSPRO environment. Don’t hesitate to leverage our experience and solutions to enhance your ERP management and IT infrastructure. Trust us at EstesGroup to help you navigate the complexities of SYSPRO with confidence.

EstesGroup News & Industry Roundups

"*" indicates required fields

Name*
Email*
Choose Your News*

Unlocking the SYSPRO System Audit Query

Unlocking the SYSPRO System Audit Query

System Audit Query – A SYSPRO ERP Administrator’s Go-To Report for SYSPRO Security Events

Being an administrator of an ERP system is no easy task. Thankfully, SYSPRO ships with several convenient programs that allow an administrator to actively monitor important events that are taking place within the system. One especially useful tool that stands out is the System Audit Query program (IMPJNS).

SYSPRO System Audit Query

SYSPRO System Audit

What You’ll Find in the SYSPRO System Audit Query Program

SYSPRO creates security logs automatically as events take place throughout the ERP. These logs are created to assist system administrators to better manage and review security related incidents in SYSPRO. The System Audit Query program is the place where these logs can be retrieved and analyzed. The program allows you to filter a time period for various security and system health-related events such as:

  • Access having been denied to a company or a program
  • Any security changes made to Groups, Roles, or specific operators
  • Logins attempted and any related error messages
  • Multi-Factor authentication changes or errors
  • System setup changes and activity related to licensing

Along with information about these events, the report can tell you which operator triggered the event, any notes associated with the event, as well as the name of the computer where the activity took place.

SYSPRO Security System Audit Query

One particularly important event that the System Audit Query program can identify for you is client-server disconnects. These are common problems reported by SYSPRO users and they can be highly complicated to investigate. SYSPRO generally has limited information about these events so the System Audit Query log is one of the few places where you can obtain valuable information about when/where they occur.

Along with the use of System Audit Query, you can investigate specific events even further by using the Job Logging Query program (IMPLOG). This program allows you to review and monitor general operator activity throughout SYSPRO.

For instance, if the System Audit Query reports technical issues relating to a specific operator, you can use the Job Logging Query program to analyze whether a specific program or user behavior is the cause of the problem. Be warned that the Job Logging Query program can take a long time to process if you choose to generate the report without filters. In a busy SYSPRO environment with a high number of daily users, the activity logs for operators will be dense and can take time to compile.

SYSPRO Job Logging Query

SYSPRO ERP Job Logging Query

A Day in the Life of a SYSPRO Admin

From the perspective of a SYSPRO administrator, actively monitoring the System Audit Query program is essential for ensuring the integrity of both the overall security and general stability of your ERP environment. The role of an ERP system administrator is undoubtedly challenging, requiring constant vigilance to ensure the smooth operation of crucial business processes.

Fortunately, SYSPRO equips administrators with a range of invaluable tools to actively monitor and maintain the system’s integrity. Among these, the System Audit Query program (IMPJNS) shines as a beacon of efficiency and reliability. With SYSPRO and its robust capabilities, administrators can confidently navigate the complex landscape of ERP management, ensuring their organizations operate seamlessly and securely.

Unlock the Full Potential of SYSPRO ERP Security with EstesGroup! Discover How Our Expert Consulting and Cutting-Edge Cloud Technology Services Can Help Your Business!

Elastic Computing Revolutionizes Business Dynamics

Elastic Computing Revolutionizes Business Dynamics

Cloud Resources are Changing the Manufacturing and Distribution Industry Landscapes

In the world of cloud options for businesses, elastic computing refers to the ability to dynamically scale computing resources up or down based on demand, without the need for significant manual intervention. It involves the use of cloud computing and virtualization technologies to provide flexibility and cost-efficiency in managing IT infrastructure. This allows for greater flexibility and scalability, as resources can be easily scaled up or down based on dynamic business needs. Cloud computing also eliminates the need for organizations to invest in and maintain their own physical infrastructure, such as on-site servers, reducing costs and increasing efficiency.

Elastic Computing Cloud Servers

What is Virtualization?

Virtualization, on the other hand, involves creating a virtual version of a device or resource, such as a server, operating system, or storage device. This virtualization technology allows multiple virtual instances to run on a single physical machine, effectively maximizing the utilization of hardware resources. By consolidating multiple virtual machines onto a single physical server, organizations can reduce the number of physical servers required, leading to cost savings in terms of hardware, power, and cooling.

Bringing Cloud and Virtualization Together

When combined, cloud computing and virtualization technologies offer numerous benefits for managing IT infrastructure. Firstly, they provide flexibility in terms of resource allocation. With cloud computing, organizations can easily scale up or down their computing resources based on their needs, ensuring that they have the right amount of resources at any given time. Virtualization allows for the efficient utilization of hardware resources, enabling organizations to make the most of their existing infrastructure.

Pay-As-You-Go, Quick-To-Market Technologies

At the end of the day, new cloud-based technologies offer cost savings throughout the entire business ecosystem. By leveraging cloud computing, organizations can avoid the upfront costs associated with purchasing and maintaining physical infrastructure. Instead, they can pay for the resources they actually use on a pay-as-you-go basis. 

Virtualization further reduces costs by allowing organizations to consolidate their hardware resources, reducing the number of physical servers required and the associated costs of power, cooling, and maintenance.

Additionally, cloud computing and virtualization technologies enhance the agility and scalability of IT infrastructure. With cloud computing, organizations can quickly provision and deploy resources, allowing for faster time-to-market for new applications and services. Virtualization enables organizations to easily scale their infrastructure up or down based on demand, ensuring that they can meet changing business needs without disruption.

Furthermore, these technologies improve the reliability and availability of IT infrastructure. Cloud computing providers typically offer robust infrastructure with built-in redundancy and failover mechanisms, ensuring high availability of services.

Virtualization also enhances reliability by isolating virtual machines from each other, preventing issues in one virtual machine from affecting others.

The use of cloud computing and virtualization technologies in managing IT infrastructure provides organizations with flexibility, cost-efficiency, agility, scalability, reliability, and availability. By leveraging these technologies, organizations can optimize their resource utilization, reduce costs, and improve their overall IT operations. Here are the top 10 benefits of elastic computing for manufacturing and distribution businesses:

Scalability

Elastic computing allows businesses to easily scale their IT infrastructure to accommodate fluctuating demand, ensuring that resources are available when needed without over-provisioning.

Cost Efficiency

By scaling resources up or down as required, businesses can optimize their IT costs, paying only for the computing power they actually use, reducing overall expenses.

Resource Optimization

It enables efficient use of computing resources, avoiding underutilization during periods of low demand and preventing resource bottlenecks during peak periods.

Improved Performance

Elasticity ensures that applications and systems can maintain consistent performance levels even during traffic spikes or increased workloads.

Flexibility

Businesses can quickly adapt to changing market conditions or unexpected events, such as seasonal variations in demand or unforeseen disruptions by adjusting computing resources in real time.

Reduced Downtime

Elastic computing minimizes the risk of system failures or downtime due to resource constraints, as additional resources can be provisioned automatically in response to increased load.

Enhanced Disaster Recovery

Elastic computing can support robust disaster recovery and backup solutions, enabling businesses to replicate their systems across multiple locations or cloud regions for data redundancy and resilience.

Global Reach

Businesses can leverage cloud providers’ global data center networks to expand their operations into new regions and markets without the need for physical infrastructure investments.

Resource Isolation

Elastic computing can provide resource isolation and security, ensuring that applications and data remain protected even when sharing cloud infrastructure with other users.

Agility and Innovation

With the ability to rapidly provision and experiment with new resources and technologies, businesses can innovate more quickly and bring new products or services to market faster.

The Value in Cloud Elasticity

In manufacturing and distribution, elastic computing is particularly valuable because it allows companies to handle seasonal demand fluctuations, respond to supply chain disruptions, and efficiently manage their IT costs. In today’s fast-paced and ever-changing marketplace, businesses need to be agile in order to stay competitive. This means being able to quickly adapt to new trends, technologies, and customer demands. Agility allows companies to respond swiftly to market changes, seize new opportunities, and stay ahead of the competition.

However, agility alone is not enough. Businesses also need to ensure the reliability and performance of their critical systems. These systems are the backbone of the organization, supporting key operations and processes. Any downtime or performance issues can have severe consequences, such as lost revenue, damaged reputation, and dissatisfied customers.

By combining agility with reliability and performance, businesses can achieve a winning formula. They can swiftly respond to market changes while maintaining the stability and efficiency of their critical systems. This requires a careful balance between innovation and stability, as well as a robust infrastructure and effective risk management strategies.

Agility enables businesses to quickly adapt their strategies, products, and services to meet changing customer needs and preferences. It allows them to experiment, iterate, and pivot as necessary, without being tied down by rigid processes or outdated technologies. This flexibility is crucial in a dynamic marketplace where customer expectations are constantly evolving.

On the other hand, reliability and performance ensure that businesses can deliver on their promises consistently. Customers expect products and services to work flawlessly, without any disruptions or delays. Critical systems, such as e-commerce platforms, supply chain management systems, or customer support systems, need to be highly available, scalable, and efficient. This requires robust infrastructure, rigorous testing, and proactive monitoring to identify and address any issues before they impact the business.

Why Manufacturers and Distributors are Choosing EstesCloud

Businesses need both agility, reliability, and performance to thrive in today’s dynamic manufacturing and distribution industry landscape. Agility allows companies to adapt and innovate, while reliability and performance ensure that their critical systems can support their operations effectively. By striking the right balance between these two factors, businesses can remain competitive, deliver exceptional customer experiences, and achieve long-term success.

Ready to move your business to the cloud? In the cloud and ready for a better cloud environment?

Cloud Hosting Epicor Kinetic ERP Logo
SYSPRO UI & Layout Problem Solving

SYSPRO UI & Layout Problem Solving

Troubleshooting user interfaces and personal layout issues in SYSPRO

Throughout the various releases and versions of SYSPRO, user interfaces and layout issues are common. Despite several significant changes to the methods of how SYSPRO stores and saves user settings, these issues are still frequently occurring even in the latest SYSPRO releases. User changes not being saved, pane locations not sticking to where they were configured, and SYSPRO windows appearing off screen are a few of these types of problems. To effectively combat these issues from a SYSPRO administrator perspective, it is important to understand how SYSPRO handles files relating to user settings and program layouts. All these issues begin and end within a folder called “Settings”.

SYSPRO UI User Interfaces Cloud

SYSPRO stores personal operator settings in text files within a folder found both locally on the client machine and on the SYSPRO application server. The folder is called “Settings” and can be found in the following locations:

  • Client machine – “C:\SYSPROClient\Base\Settings”
  • Application Server – “C:\SYSPRO\Base\Settings”
SYSPRO User Interfaces

When a user closes out of SYSPRO on their client machine, any changes made to their layouts or personal settings will be saved to this directory. The client machine syncs the files to the application server and overwrites any non-identical files for that user. The settings are stored on the application server to serve as a backup in case the user gets a new computer or signs in from another machine.

When the user signs in to SYSPRO again, the client machine compares the local setting files to the ones on the application server and restores any missing files or updates existing ones based on the modified date of the files.

As this back-and-forth process takes place, it is possible that settings files become corrupt due to various reasons such as a disconnect between the client and the app server. Thankfully, it is almost always the local files on the client machine that are corrupt and not the ones on the application server. What this means is that it is possible to clear and “refresh” a user’s settings by renaming the client-machine’s “Settings” folder (ex, “Settings_old”). By doing so, SYSPRO notices that the folder is no longer there and recreates a new “Settings” folder based on the files stored on the application server. This is an effective solution to a variety of issues that an operator may experience in a SYSPRO client environment.

Instead of renaming the entire “Settings” folder, it is a good practice to target specific settings files first. For instance, if it relates to an issue within Sales Order Entry (IMP040), you can search the “Settings” folder for IMP040 specific files and try removing those first. When the user signs-in to SYSPRO, the app server files will be restored to the client as they are detected as missing. If this doesn’t resolve the issue, you can then attempt the full renaming of the “Settings” folder.

If you choose to target any specific files, be sure to back them up and restore them to the folder if removing them did not resolve the issue.

Troubleshooting application server file corruption

If corruption is suspected with the application server files, then there is little that can be done in terms of restoring or recovering the user’s settings. As explained above, the app server replaces the files on the client machine in the event of any discrepancies between the user’s settings files. If they are corrupt on the app server, they will transfer and overwrite the local files and remain corrupt. In this case, we recommend seeking support from SYSPRO’s support team itself as modifying the “Settings” folder on the application server can result in potential loss of layouts and user settings for all operators in your SYSPRO environment.

Also, note that SYSPRO is and have actively been updating the amount of information stored on the application server and in the SQL database with each new SYSPRO release. Prior to SYSPRO 8 2021 R1, many types of settings are only stored locally and cannot be restored by the app server. You can try this suggested fix if you are dealing with an older SYSPRO release, however, there is no guarantee that the app server has a copy to restore so the user’s layout may reset to default.

If this fix does not resolve the user’s problem, you can try to either “Repair” or uninstall and reinstall the SYSPRO client on the user’s machine itself. This may help resolve corruption within direct program files unrelated to personal user files. If you renamed the “Settings” folder and it did not resolve the problem, be sure to restore the prior settings folder by renaming the original folder back to “Settings”.

Looking for more help with SYSPRO UI & other ERP system or IT issues? Schedule a free one-on-one consulting session with a SYSPRO ERP or IT consultant today!

SYSPRO Data Integrity: A Guide to Balance Functions

SYSPRO Data Integrity: A Guide to Balance Functions

How to Ensure Data Integrity Within SYSPRO – Balance Functions Explained

Ensuring data integrity is a top priority for any software product, especially for an ERP such as SYSPRO. As users go about performing their daily activities, various problems can arise, even with the most mature ERP systems. The most common issues seen within SYSPRO that can lead to data instability are users being disconnected, programs freezing up, or business objects unexpectedly stopping in the middle of processing. With tens (or potentially hundreds) of daily active users, it is imperative for your business that the data within SYSPRO stays consistent. So how does SYSPRO combat data integrity problems and maintain the overall stability of its data? The answer is SYSPRO balance functions!

SYSPRO Data Integrity Balance Functions

A balance function in SYSPRO is a detailed process used to correct and adjust database information if discrepancies are detected. They are built in to SYSPRO’s Period-End programs and are supposed to be run prior to posting GL entries or performing Month-End/Year-End tasks. SYSPRO’s balance functions can help “balance” a module by comparing user transaction data to its own control totals and correcting any noticed discrepancies. Some examples of these discrepancies that it can correct include:

  • GL journal entries that have not been properly completed or are still marked with “in-process” flags if they were abandoned. Users unexpectedly disconnecting from the system can be a cause of this.
  • Failed inventory transactions. Minor hiccups from bugs or networking issues during inventory transactions can result in inaccurate inventory counts. For example, a stock code may display as having available quantity on-hand but an attempt to issue or release the quantity results in errors.
  • Specific key documents being locked down by users for maintenance that fail to be released once complete. Again, a potential result of unexpected user disconnects or program errors. These are commonly encountered within sales/purchase order entry and customer/supplier setups programs.

Scheduling SYSPRO Data Integrity Tasks

While most SYSPRO environments generally only run these balance functions during their period-end tasks, it is strongly recommended to schedule balance functions to run regularly. Sites with heavy user activity (including custom business object activity) may want to run balance functions overnight several days throughout the week. The result of this will be an improved and overall smoother SYSPRO experience for all users.

Balance functions are not found separately within their own respective program. Instead, they are usually part of and located within period-end programs. The naming convention of some of these programs may not be clear and it is not easy to identify all of them. As such, here is a full list of the programs within SYSPRO that contain or can perform the functionality of a “balance function”:

  • AP Period End
  • AR Period End
  • AR Bank Deposit Slip
  • Cash Book Period End
  • Assets Period End
  • Inventory Period End
  • Sales Order Purge
  • Purchase Order Purge
  • GRN Purge
  • Sales Analysis Update

It is imperative to understand that some of these programs contain critical data-altering functionality within SYSPRO relating to period-end module closures or purging of data. You should tread with caution when accessing these programs and ensure you only have “Balance” selected. NOT any unwanted options pertaining to period-end and/or data purge functionality! 

Some of the above-listed programs may have an option called “Reset lowest unprocessed journal”. As it is not always checked by default, it is recommended to enable this option prior to executing a balance function. It performs an additional data-stability feature intended to fix GL journal issues. 

SYSPRO Data Integrity Balance Functions AR Period Example

SYSPRO environments that are not familiar with the power of balance functions can (and will) encounter unwanted issues and potentially unstable data problems. Knowing how to utilize, execute, and schedule balance functions is key to ensuring your SYSPRO environment’s data remains both stable and trouble-free.

Ready to discover how an EstesGroup ERP consultant tackles data integrity challenges & ensures your company’s success? Chat with us now or sign up for a free demo to see what your business would look like in EstesCloud!

SIGN UP FOR A CLOUD DEMO TODAY

"*" indicates required fields

Name*
Email*