Creating custom reports in any Enterprise Resource Planning (ERP) system, including Epicor Kinetic, can be a surprisingly difficult endeavor. I’ve seen numerous cases in custom report development where the final deliverables did not match the expectations. Why does this happen? Most often, it’s not due to technical challenges but rather the difficulty in defining what you actually need.
If you are considering creating a custom report and are in the process of specifying report requirements in Epicor, there are a few things to keep in mind.
When requesting a custom report in Epicor ERP, simply providing a paper copy of a report from your legacy system and asking the developer to recreate it in Epicor is not enough to ensure a successful outcome. While the legacy report may serve as a starting point, it’s essential to recognize that the data structure and available fields in Epicor may differ from your previous system. To create an effective custom report, you need to provide more specific details about your requirements, taking into account the unique features and capabilities of Epicor ERP. Similarly, offering a one-line description of your desired report and expecting the developer to “get it done” is insufficient for achieving the desired results. A brief, vague description leaves too much room for interpretation and can lead to misunderstandings. So, make note of these two things not to do when planning your approach:
Simply pulling out a paper copy of a report from the legacy system and saying, “Do it in Epicor,” is not sufficient.
Providing a one-line description and saying, “Get it done,” is also inadequate.
Investing time in creating detailed specifications can save you from multiple rounds of revisions and ensure a more efficient and successful custom report development process in Epicor ERP.
In other words, if you want a good report, you need to specify the details.
Key Elements for Specifying an Epicor Report
To ensure your custom report meets your expectations, consider the following key elements:
Query Logic
What should the underlying query return? For example, specifying the report logic might involve “all active parts of Part Class X” or “all sales order miscellaneous charges that have not yet been invoiced.” Providing this basic logic helps the developer structure the underlying query.
Filters
Do you need to run the report filtered by something, such as the part, supplier, or site? If so, note it, as this will affect how the report is created.
Groupings
How do you want the data in the report grouped? For instance, you may want the data grouped “by site and customer.”
Sorts
Within the groupings, how should the data be sorted? This will impact how the underlying query is structured before the data is passed to the report designer. For example, you might want to “group by site and customer, and sort by invoice number” or “sort alphabetically by part number.”
Fields and Field Order
It’s important to know the specific ERP fields where the data lies, and the order they should appear in the report. If it’s a calculated field, you need to provide the calculation (e.g., past due = due date – current date).
Sample Data
Often, to build a report, you will need the underlying data in the development environment. For example, if you are specifying a report that collects all miscellaneous charges, you may need to create some sales orders and sales order lines with miscellaneous charges.
Mockup
Providing a visual mockup of what you are looking for helps the developer organize the output. If you are replacing an existing report from a legacy system, this may be a good time to use the legacy report copy, albeit with the necessary edits to make it specific to the new ERP system.
By considering these key elements and providing clear specifications, you can help ensure that your custom report meets your expectations and delivers the insights you need.
When defining report requirements in Epicor ERP, it’s crucial to provide clear and detailed specifications to ensure the final output meets your expectations.
Epicor report requirements should include query logic, filters, groupings, sorts, fields, sample data, and a visual mockup to guide the developer in creating a custom report that aligns with your business needs. By effectively communicating your Epicor report requirements, you can streamline the development process and obtain the insights you need to make informed decisions and drive your business forward. Creating custom reports in Epicor ERP can be a complex process, but by understanding and addressing the key challenges, you can ensure your reports meet your specific needs. The most significant hurdle is often not the technical aspects but rather the difficulty in clearly defining your requirements. By providing detailed specifications, you can help bridge the gap between your expectations and the final deliverable. Remember, effective communication and collaboration are essential to overcoming challenges.
Installing client machines for SYSPRO ERP can be a tedious process. Accessing the SYSPRO 8 Installer on each client machine, signing in to the installer, going through the various tabs and steps to successfully install both the client and the necessary reporting software. What if there was a significantly easier way to perform these installations? As a matter of fact – there is!
Instead of going through the installer every time you install a SYSPRO client, you can create and export a SYSPRO product batch file. The batch file allows you to both quickly and quietly install a SYSPRO client along with the necessary reporting software without using the SYSPRO installer at all.
You can create your own SYSPRO batch file installer by following the steps outlined below.
STEP ONE: Launching the SYSPRO Installer
Find and launch the latest version of the SYSPRO Installer. By default, this file is located in: “\\*servername*\SYSPRODeploy”.
STEP TWO: Signing In
Go through the steps of signing in to the installer using your SYSPRO InfoZone credentials.
STEP THREE: Click to Select
Click on “SYSPRO ERP Software”.
STEP FOUR: Selecting Deployment Group
Click “Select” on your desired deployment group.
STEP FIVE: Exporting SYSPRO 8 Client
You should now see the available product list for your SYSPRO environment. In the top left-corner of the product list header there will be a little “Export” button. Click this button.
STEP SIX: Export
The product list now changes to an “Export” selection. Find and select the SYSPRO 8 Clientand click to continue the export.
STEP SEVEN: SYSPRO Terms
You will be asked to review and agree to general installation terms. Proceed through the export wizard until you can select to begin the export.
Effortless SYSPRO 8 Client Installation with Batch Files
A batch file is now created and can be used to install the SYSPRO 8 client along with its required services. By default, the batch file is stored in “\\*servername*\SYSPRODeploy\Exports”. Following similar steps, you can create an additional batch file for reporting software by navigating through the “Additional Software” section of the installer and selecting your version of Crystal Reports to export. Using these batch files, you can now quietly install a full SYSPRO client configuration with only a few clicks!
Here are a few helpful tips to keep in mind when using the batch files:
Run the batch file to install the SYSPRO client first prior to installing any reporting software.
To ensure that the products are installed properly, make sure that you run the batch files as administrator. Additionally, the domain user running the batch files will need sufficient access to the SYSPRODeploy folder on the SYSPRO Server where the targeted products and install files are located.
You can use the Programs & Features part of Windows to verify that the products installed successfully after running the batch files.
If something fails to install, you can always use the SYSPRO 8 Installer program to retry the installation manually.
Advanced SYSPRO Debugging Tools – The “Diagnostics” Setup Option
Outside of general SYSPRO database tables in SQL and eSignatures that are not enabled by default, it can be particularly difficult to investigate custom e.net transactions and SQL issues in SYSPRO. Thankfully, an advanced “Diagnostics” tool is available. Contrary to similar administrative tools such as the System Audit Query and Job Logging programs, this tool is not a standalone program. Instead, it is a settings-related options found inside your SYSPRO’s Setup Options program.
The setting in question is called “Diagnostics” and can be found within SYSPRO’s Setup Options program at: System Setup General Options Diagnostics. The field is a dropdown containing a variety of input options with not-so-descriptive naming conventions such as “dev02”, “enet01”, “enetxi”, and “srsd04”. While all the items available in the diagnostics list serve an important purpose, we will focus this article on the e.net-type diagnostics that can be used to help diagnose and potentially resolve complicated transaction issues.
SYSPRO E.net Options
When customizing SYSPRO particularly with third party programs or VBScripts, you are likely to encounter programmatic use of SYSPRO’s business objects. In extremely rare cases, you may experience issues running these business objects. Perhaps you don’t get an XML response, or you are encountering critical system errors with limited details about the errors. In this case, the “enet” diagnostic options can be useful. The “enet01” option creates a log of all business objects that have processed in the system since the diagnostic option was turned on. It saves important information such as transaction date/time, method names (logon, logoff, get, post), and status messages of each transaction. Consider the “enet01” option the “summary” of e.net type diagnostics.
If you require more detail about your e.net transactions, you can use the “enetxx” option. This diagnostics option saves the XML-In and XML-Out details of each business object transaction. The XML-In is the data that was passed to the business object. The XML-Out is the response provided back by the object. The “enetxi” option can be used to only monitor XML-In and the “enetxo” only monitors XML-Out.
While there are several other diagnostic types to choose from, it is unlikely that the information returned by these options will be of any help to you. The remaining diagnostic types are more commonly used by internal SYSPRO staff for testing and debugging of significant errors or new programs in SYSPRO. You can open SYSPRO’s “Help” documentation by pressing “F1” to learn more about the other diagnostics options if it should be of interest.
System Impact and Log File Growth
It is important to know that some of these diagnostics options can result in very large log files if they are not turned off after an issue has been investigated. Particularly the “enetxx” option as the XML-In and XML-Out for every business object transaction can be significantly lengthy. If you are trying to monitor automated tasks and will have to leave these diagnostics on for extended periods of time, be sure to keep an eye on the log file sizes.
Additionally, many of these diagnostic types can slow down the overall system performance. Every post and query in SYSPRO use some type of business object. These transactions will see a slight performance hit due to SYSPRO recording and logging the data input/output. When you have completed investigating an issue, be sure to clear the log files and turn off the diagnostics options that you had enabled.
The EstesWay to Advanced Diagnostics in SYSPRO
In conclusion, navigating through complex SYSPRO issues, especially those involving custom e.net transactions and SQL intricacies, can be daunting without the right tools and expertise. Fortunately, the “Diagnostics” setup option within SYSPRO’s Setup Options program provides a valuable resource for investigating and resolving such challenges. By utilizing specific diagnostic settings like “enet01” and “enetxx,” users can gain insights into business object transactions and detailed XML data, aiding in the troubleshooting process. However, it’s crucial to exercise caution with these diagnostic options, as they can lead to substantial log file growth and potential system performance impacts if left unchecked. Nevertheless, with the support and guidance of EstesGroup consultants, businesses can effectively leverage these advanced debugging tools to overcome SYSPRO-related hurdles and optimize their operations.
Empower your users with advanced diagnostics in SYSPRO ERP today.
Follow these steps to get immediate assistance with SYSPRO ERP:
Contact EstesGroup consultants via chat, website, or phone.
Describe your SYSPRO issue and request advanced diagnostic assistance.
Schedule a consultation with EstesGroup SYSPRO ERP specialists.
Collaborate with consultants to enable and utilize diagnostic tools.
Implement recommendations provided by EstesGroup for issue resolution.
Manufacturers and distributors can benefit significantly from a Managed Services Provider (MSP) managing one website or kin websites as part of an integrated IT services, IT security, and enterprise cloud strategy. An external IT provider ensures that the world will view web-based company representation with optimal performance, scalability, and security, reduced downtime and enhanced user experience. Through robust IT security measures, a cloud provider like EstesGroup safeguards sensitive data, mitigating the risk of cyber threats. Additionally, integrating enterprise cloud solutions facilitates seamless data access, collaboration, and scalability, enabling manufacturers and distributors to focus on core business functions while staying agile and competitive in the digital landscape.
For businesses, websites serve as crucial repositories for sharing information, necessitating proper hosting and data management to connect with customers, ensure security, and facilitate growth. When exploring website hosting services and ERP hosting solutions, businesses encounter various cloud options, with managed hosting and shared hosting being the primary types. Understanding the distinctions in the website vs. ERP hosting conversation empowers businesses to make informed decisions aligning with their unique identities.
Is your website hosting forgotten data?
While your IT team is focusing on critical tasks, your website might go unnoticed, opening the path to vulnerability and chaos. In the realm of website hosting, discerning between managed hosting and shared hosting is essential. Managed hosting is ideal for businesses seeking comprehensive control and responsibility, with the service provider acting as a dedicated IT department overseeing all aspects of the website. Conversely, shared hosting accommodates businesses needing performance and security but may lack the size or budget for full-service management. Multiple businesses share resources like RAM and CPU under a shared server, potentially impacting performance during traffic surges. Managed hosting suits larger enterprises prioritizing ultimate performance and security, while shared hosting remains viable for budget-conscious smaller businesses.
Managed Hosting vs. Shared Hosting vs. Managed ERP Hosting
Businesses should consider several key differences between managed and shared hosting for websites and ERP hosting for enterprise resource planning applications. Here are a few things to keep in mind as you unravel your web of business data.
Resources: Managed hosting provides dedicated server resources, ensuring optimal performance, while shared hosting involves resource-sharing, potentially leading to performance issues during high traffic.
Customization: Managed hosting offers customized solutions, tailored to specific business needs, whereas shared hosting tends to be more one-size-fits-all.
Security: Managed hosting prioritizes security, protecting individual businesses, whereas shared hosting may compromise security if one business on the shared server experiences a breach.
Optimal Performance: Managed hosting eliminates performance issues associated with shared resources, providing consistent and optimized performance.
Updates: Managed hosting ensures prompt updates and security patches, while shared hosting may require businesses to schedule updates themselves.
Email: Both hosting types offer email services, with managed hosting providing premium plans for enhanced features.
Cost: Shared hosting is more affordable, making it suitable for smaller businesses with budget constraints, while managed hosting, though more expensive, offers superior performance and security.
How ERP Hosting Gets Tangled in Your Website Web
The discussion on website hosting parallels ERP hosting, where businesses can opt for a managed service provider to host their ERP software in a remote, cloud-based data center. This centralized approach provides cost-effective, secure, and scalable solutions, enabling businesses to focus on operations rather than maintaining on-premise infrastructure.
Businesses must comprehend the disparities between the many available cloud options to make informed choices for their website and ERP hosting needs. While managed hosting excels in performance, security, and support, startups or small businesses with budget constraints may consider shared hosting initially. Managed hosting proves invaluable for businesses seeking to eliminate on-premise responsibilities, allowing them to concentrate on optimization and growth.
Complex Cloud Hosting Environments
Experience seamless business operations with our fully managed ERP hosting, ensuring optimal performance, security, and scalability as we take charge of your ERP software in a secure, remote, and cloud-based environment. Ready to tackle website vs. ERP hosting? Elevate your online presence with our fully managed website hosting, where a dedicated IT team handles every aspect, providing tailored solutions for peak performance, robust security, and unmatched support. Trust EstesGroup to streamline your technology infrastructure, allowing you to focus on growth and innovation without the burden of managing complex hosting environments.
The medical device manufacturing sector plays a vital role in supplying essential products that impact lives. Manufacturers must adhere to the strictest compliance standards while successfully organizing and managing their operations. Effective Enterprise Resource Planning (ERP) systems can be an important aspect of this organization and management. There are many benefits to implementing ERP systems, and manufacturers will find that the right solutions will improve their operations, ultimately increasing operational productivity and software functioning.
Tracking Data Health
Given the diverse range of medical supplies and their components, manufacturers require software integrations capable of efficiently tracking parts and finished products. ERP systems facilitate seamless tracking and management of order histories, revisions, and product recalls. Tailored ERP solutions offer real-time insights throughout the manufacturing process, aiding in documentation and data export for compliance with medical device manufacturing standards. These systems also enable revision tracking during manufacturing, assisting businesses during inspections and audits. Providing recall tracking, ERP systems empower businesses to identify potential concerns in medical devices, implementing protocols to prevent recalls and ensuring comprehensive tracking support for the complex manufacturing of medical devices.
Healthy Supply Chain Management
ERP systems for the medical device manufacturing industry offer robust support for supply chain management. Businesses can easily manage various aspects, including the Approved Supplier List (ASL), tracking, manufacturing documentation, data reporting, validation and revalidation, risk assessment, and quality control and inspection.
Seamless ERP Integrations
The most effective ERP systems are tailored to seamlessly integrate with existing systems and software. Customized ERP systems provide a unified approach to operational management, allowing for flexible software integrations under a single system. For instance, integration with the Laboratory Information Management System (LIMS) provides crucial data insights while safeguarding data and permissions. ERP systems collaborate with and enhance existing systems, enabling businesses in the medical device manufacturing industry to focus on quality and efficiency in supplying and distributing medical devices.
The Longevity of Med Device Manufacturing
In a world where medical devices like artificial hips and knees are essential and can change lives, ERP systems emerge as crucial tools for meeting industry demands. A fully-customizable ERP system offers comprehensive data tracking and supply chain management, alongside flexibility in system and software integrations. Implementation of effective ERP systems empowers businesses to gain insights into their manufacturing processes, enhancing operational efficiency and productivity. A unified system with vital software integrations allows businesses to prioritize fulfilling essential orders and providing individuals with the medical devices they need.
Where Security Takes the Pulse
Meet ECHO, EstesGroup’s cloud solution for complex application management. In the rapidly evolving landscape of medical device manufacturing, top-tier security and cloud solutions stand as the vanguards of fortified operations. Paired seamlessly with effective ERP systems, these cutting-edge technologies offer a robust shield against potential threats. Advanced security protocols embedded within the cloud infrastructure provide an extra layer of protection for sensitive data, ensuring compliance with stringent industry standards.
Global Health Requires Private Cloud ERP
Cloud solutions enable manufacturers to securely store and access critical information, fostering a dynamic and collaborative environment. This integrated approach not only enhances the resilience of the manufacturing process but also aligns with the industry’s commitment to delivering high-quality, life-changing medical devices. As the medical manufacturing sector embraces innovation, the synergy between ERP, top-tier security, and cloud solutions emerges as a formidable force, propelling the industry towards a future of heightened efficiency and reliability.
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 totroubleshoot data problems, analyze company data, or build SQL queries to pull data for custom reports.
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.
