Select Page
Freight Forward to the Future: P21 Web UI Migration Options

Freight Forward to the Future: P21 Web UI Migration Options

Transitioning to the P21 Web UI Version

Keeping your Prophet 21 ERP system up to date poses numerous challenges, especially when dealing with upgrades. The testing, retesting, troubleshooting, and remediation processes can be time-consuming and demanding. Transitioning to the P21 Web UI introduces even greater challenges, with larger changes, increased risks, and heightened frustrations for end users. Consequently, the adoption of the P21 Web UI has been progressing slowly, akin to molasses in January, as they say in Canada.

Prophet 21 P21 Web UI Migration Distribution Warehouse

In November, EstesGroup sponsored the Southeast User Group chapter of the P21WWUG, presenting on P21 Infrastructure Best Practices and the elusive topic of Web UI Migrations. Our polls revealed that two-thirds of customers have yet to fully migrate from the P21 desktop application.

For customers still tethered to a desktop version seeking a way out, we recommend two approaches when planning a P21 Web UI migration: incremental or big bang.

An Incremental Approach

For those committed to the last branched version (2021.1) and hesitant to fully transition from the P21 desktop, an incremental approach is advisable. The customer creates an ecosystem as a live testing model, gradually shifting from the old to the new through the following steps:

  • Develop an adoption plan for “branched” usage, initially allocating specific hours for web UI use.
  • Configure a branched deployment in the live environment, allowing parallel use of desktop and web UI.
  • Instruct users to incrementally operate on the web UI during designated hours.
  • Address reported shortcomings incrementally through IT or ERP administrator intervention.
  • Create a remediation work plan for identified issues and initiate resolution.
  • Conduct remediation and testing cycles until all issues are resolved.
  • Increase web UI usage until reaching a predefined cutoff amount of time.
  • Attain user and management signoff, and officially transition all users to the web UI.
  • Stabilize the live cutover environment and provide ongoing support.

A Big Bang Approach

For customers seeking a more significant leap to a web-only version (2022+), the big bang approach is recommended. This involves an implementation-level cutover executed in one decisive move:

  • Deploy the Web UI to a middleware-only test environment.
  • Conduct user testing, addressing and communicating issues as they arise.
  • Create a remediation work plan and resolve identified issues.
  • Document remediations and compile into a cutover plan, expanding the testing pool.
  • Conduct a mock cutover (CRP), regression testing, and address any remaining issues.
  • Attain user and management sign-off for the “go live” decision.
  • Repeat the cutover to the new version in the live environment with Web UI.
  • Stabilize the live cutover environment and provide ongoing support.

The Weight (and Freight) of Risk in P21 Migrations

The choice between incremental and big bang approaches depends on your risk tolerance and desired rewards. If you seek to minimize risks, choose the incremental approach. For maximizing rewards, opt for the big bang. Each approach comes with its own set of risks, rewards, and characteristics. If you need assistance with your Web UI Migration, please reach out to us!

Overcoming Epicor Cutover Challenges: A Tale of Cryptic Errors

Overcoming Epicor Cutover Challenges: A Tale of Cryptic Errors

Epicor Admin Quick Tip: Regen After a Refresh

I once had an Epicor go-live brought to its knees by an administrative snafu – as cutover weekend neared, the Epicor admin refreshed the Epicor production environment with a copy of the Epicor Pilot database. Such a step is not uncommon in an Epicor cutover. But this had not been the first time that a production refresh had occurred, and there had been subsequent customization activities developed since the last Epicor database refresh. As such, there were several Epicor user-defined fields that were present in the Pilot database but new to Production. This small discrepancy created unexpected hardship to all involved.

Epicor Cutover Database Admin

Chaos to Resolution in Epicor

The net result for the Epicor core team that was cutting over to the new system over the weekend was a litany of cryptic Epicor error messages, abysmal system performance, and a near mutiny by the Epicor user community. After roping in a few Epicor administrative experts, we were able to discern the discrepancy, regenerate the data model, and move beyond this hurdle. But the memory of that small Epicor system administration rule-of-thumb gone wrong stuck with me, long after the project had wrapped up.

One reason for this latent memory is that it finds itself refreshed by new instances – just recently, I found an end user reaching out to me over some cryptic errors in a test environment, an Epicor environment that had just recently been refreshed from a seed database. My first question: “Did you regenerate the Epicor data model after refreshing the Epicor database?” Problem solved, albeit this time, without the pitchforks and torches.

Echoes of CRC Errors 

Does this issue sound familiar? For those of us whose Epicor administrator duties go back to Epicor 905, Epicor Vantage, or some earlier Progress-based version, these issues might be likened to the familiar “CRC errors” that once plagued our Epicor custom solutions. In that case, a field had most often been added to the database, and that field caused an existing Progress-based compiled assembly to malfunction. The table structure at the database level did not match the table structure at the application level, and chaos ensued.

Sometimes, the resolution to an Epicor issue is simple. In this case, a simple Epicor admin policy would be to regenerate the data model when refreshing an Epicor environment. This ensures that you will not have any mismatch with your Epicor UD fields, and that the users can jump in without issue.

This is especially true in an environment where custom solutions are being developed, as is the case with many Epicor implementation projects, where changes are most often occurring. This can also be the case in Epicor projects that are heavy in the use of the Epicor Product Configurator module, or longtime Epicor customers who have undergone a significant amount of Epicor customization.

Post-Model Regen

Now that you’ve regenerated the data model, don’t forget the subsequent step of retrieving a copy of the Epicor database’s data model, so that the application server in question can store it locally, for use by the application itself. At a minimum, the Epicor admin should recycle the application pool for the application server instance in question – this is accomplished from the administration console. Now, I’ve had some administrators tell me that it is preferable to start and stop the ERP application pool, rather than simply recycle it. The difference between stopping and recycling an IIS application pool demands its own article, so I will stop at mentioning this controversy for the time being, without discussing its resolution.

Epicor Regen After Refresh

Epicor Cutover Success

The art of efficient Epicor system administration often boils down to steering clear of preventable pitfalls. The instance described here serves as a prime illustration of a minor adjustment that can avert substantial issues. By ensuring the proper regeneration of the data model and taking the necessary steps to maintain database consistency, ERP administrators can fortify their systems against disruptions.

Do you need help with your Epicor cutover or are you looking for more admin tips?

If you find yourself seeking guidance in the realm of ERP administration, don’t hesitate to reach out. Our Epicor Kinetic consultants can assist you in navigating the intricacies of your ERP environment, ensuring smooth operations and enhanced productivity for your organization. EstesGroup brings your company functional, technical, and custom solutions for Kinetic ERP. Manufacturers will benefit from our full-suite of services and solutions, including on-premise expertise and 24/7/365 IT and ERP consultants. From third-party integrations to private cloud and hybrid cloud managed services, Estes provides everything your team needs to succeed before, during, and after go-live.

Best Practices for Evaluating a Next-Generation B2B Platform

Best Practices for Evaluating a Next-Generation B2B Platform

How to Think about E-Commerce as a Manufacturer

E-commerce continues to be a pivotal topic in the manufacturing world – distributors caught on to e-commerce comparatively quickly, as the demand for streamlined processing became a core competency. But in the manufacturing world, where product complexity is many times greater than the items delivered over traditional distribution channels, the acquisition and fulfillment of complete, complex, and high-dollar products becomes much more complicated.

B2B E-Commerce

Manufacturing companies that successfully leverage e-commerce as part of their overall go-to-market strategy do so in a variety of ways and seek to achieve a variety of benefits. That said, I thought it would be beneficial to cover some of the ways in which manufacturing companies are successfully leveraging e-commerce solutions to the benefit of their bottom line and their strategic initiatives.

Expanding Your Spare Parts Business

As a consultant, I once noticed an interesting trend when it came to system configuration – customers routinely spend an inordinate amount of time configuring their ERP system around their finished goods. And then they go live, and we all realize that the vast majority of their orders are not for finished goods but rather for spare parts. In many organizations, these orders amount to a significant revenue stream. Why is that? The margins achieved by service parts, replacement parts, spare parts, and related value streams are generally much higher than they are for finished goods. When a customer is in a bind, their machines are down, and product is not getting out the door, the demand for simple components goes way up, and as a result, the asking price similarly climbs.

To that end, e-commerce systems can streamline the process for finding the right part you need and expediting the fulfillment process, getting the order in the queue, without the need to chase down a customer service rep.

Expedited Warranty Processing

The flip side of the spare parts business is the world of warranty. In these cases, customers need some form of service part to address an issue covered by the original product’s warranty, often at no cost. Deploying your warranty parts to your e-commerce system allows your customer base to get a hold of the parts they need as soon as possible and helps cut down your own warranty costs by reducing the degree of human interaction. The net result is a better overall service offering, without the increase in overhead.

Finished Goods Acquisition

While our discussion has thus far centered on the acquisition of component parts, many manufacturers have extended their e-commerce offerings to include finished goods. I’ve seen customers readily deploy their highly standardized and stocked finished good products to their e-commerce systems, and in doing so, provide another avenue for customer service and order taking. This can be of great value to organizations that cater to both a B2B and B2C community. It can also service the lead-time needs of existing customers – in cases where companies are short-staffed on the order entry / customer service front, an e-commerce connection allows your customer base to get “first in line” when placing an order. In many industries, such a priority can shorten order-to-deliver lead times, which can be of great value to a given customer.

Customer Portal

The ability to stay on top of your orders has become of increasing importance to customers in B2B relationships. This includes but is not limited to orders that were placed online. When a customer places an order, they often expect online status information, to be able to track their orders through the fulfillment process. This can be important both for quick-turn items, where delivery timing is of the essence, or for large, long lead time items, where status at various stages becomes critical to know. E-commerce solutions provide a natural way to provide customers with updates to order status, whether the order was placed online or through a customer service representative. This allows you to provide an easy means of constant status to your customers while saving your own team.

Dealer Interaction

One important customer channel for many manufacturers is the dealer-distributor network. Dealers and distributors are a strange blend of outside sales and end customers, and their needs overlap the two. A goal for many organizations is to make their dealer-distributor network as much an extension of their own organization as possible. How is this done? Through seamless communication, often fostered by an e-commerce-enabled dealer portal. Dealer portals often combine elements of traditional e-commerce with elements that betray the intimacy that dealers need and expect from their manufacturing partners. Are you looking to better service the needs of your dealers and distributors? Give e-commerce a try.

24/7 Customer Service

As you might have noticed, many of the above circumstances have referenced difficulties in getting your order placed. This is surprisingly common, and I am forever shocked and surprised by the challenges many companies have in finding reliable customer service and order processing resources. Customer service is a difficult business, and many workers who might have posted for these roles have found other options. That said, the time it takes for your customers to get their orders into your system and “into the queue” can be a deal maker or a deal breaker. 

Providing an easy means to enter orders and get them immediately into the fulfillment cycle can be an enticing option. Also, in our increasingly remote world, where employees routinely look to get tasks done at odd hours, the ability to provide 24/7 customer service can be of great value to many organizations. When your customer is in a pinch due to an emergency or machine downtime, the ability to immediately get in front of you can be of immense value.

Separating the Best from the Rest

As you can see, e-commerce has grown in breadth and depth over the years to cover an increasing number of avenues and solve a variety of problems for customers. But now that we know what a world-class e-commerce solution can do for you, the question remains: what are the best practices for evaluating a world-class e-commerce solution? In our webinar on October 25th, 2023, our friends at Parttrap can help you see what you need to look for when evaluating an e-commerce solution.

B2B
EstesGroup Fall ’23 Prophet 21 Summit

EstesGroup Fall ’23 Prophet 21 Summit

Prophet 21 Summit Virtual EstesGroup Distribution P21

Mastering Prophet 21 in 2023

This past February, EstesGroup’s own Brent Merritt presented to the Carolinas’ Prophet 21 World Wide User Group chapter on the subject of P21 architecture best practices. Then we went out to a very fine Cajun restaurant with a live band and spicy food. The band was so fun and the food so good that we ended up ordering far too many desserts, in an attempt to extend the evening. I wasn’t hungry for days. Moreover, Brent’s presentation was so well received that we thought it would be a nice idea to give that presentation to a broader audience.

Are you looking to confirm whether your P21 hardware configuration is appropriate? Or are you about to refresh your on-premise P21 environment? Or are you considering scaling up or scaling out your existing P21 ecosystem, to accommodate organizational growth? And what impact will this have on the P21 database or application layers? On September 21st, 2023, Brent Merritt will provide answers to these common P21 questions and more. The EstesGroup team will also present on SQL Server Query Optimization and Web UI Migration Best Practices. Guests from our Partner Network will include DCKAP, Web Connect, and Conveyance.

P21 Summit Agenda

All Prophet 21 Sessions are Noted in Central Time

  • 11 AM: P21 Architecture Best Practices – Brent Merritt, EstesGroup
  • Noon: Integrated Distribution Commerce for P21 Users – DCKAP
  • 1 PM: From Inbox to Order: Streamlining the P21 Sales Process – Web Connect
  • 2 PM: Introduction to P21 APIs – Conveyance
  • 3 PM: SQL Server Query Optimization – Brad Vandenbogaerde, EstesGroup
  • 4 PM: Web UI Migration Best Practices – EstesGroup IT Team

DCKAP

EstesGroup has long been partners and friends with the DCKAP team. P21 ecommerce is an important topic for many Prophet 21 distributors, so we’ve had a lot to talk about. In 2022, I attended DCKAP’s Round-Up event in Austin, TX, to discuss hybrid cloud strategies

At last year’s Estes’ Integrate 2022 event, DCKAP’s Aaron Pallares presented a Distributor’s Guide To Breaking Operational Silos. Estes is excited to have DCKAP on board once again to discuss the intersection of Prophet 21 distribution and ecommerce.

Web Connect for Prophet 21

One fortuitous outcome of this year’s P21WWUG CONNECT 2023 event was the opportunity Estes had to start a new friendship with the team at Web Connect. The Web Connect team delivers a suite of P21-integrated utilities that extend and expand on Prophet 21’s native functionality. Whether it’s automating the P21 quoting and ordering processes, providing customers with access to P21 information, or helping P21 sales users access and communicate their P21 sales data in new and exciting ways, Web Connect continues to help P21 users optimize their sales processes. EstesGroup is looking forward to the Web Connect team’s insights on how technology can bolster a company’s Prophet 21 sales processes.

Conveyance Solutions

EstesGroup has been working hand-in-hand with our consulting partners from Conveyance Solutions, often working together both on P21 implementations and P21 optimizations. The Conveyance team brings a wealth of knowledge to the table when it comes to implementing Prophet 21. One such subject is the matter of the P21 API. Prophet 21’s API is a nebulous subject for many of us, as it differs significantly from the earlier P21 integration solutions that predated the P21 Middleware Server

But just what is the P21 API? What are APIs in general? How is it related to Epicor’s Prophet 21 web version? And how can the Prophet 21 API be put to use to automate processes and integrate the P21 application with third-party solutions? The Conveyance team will be tackling this topic at our Fall ’23 Prophet 21 Summit.

Prophet 21 World Wide User Group – Lake Erie Insights

Earlier this summer, Estes own Brad Vandenbogaerde headed down to Cleveland to hang out with the P21WWUG Lake Erie chapter and to give a workshop on some Prophet 21 SQL query optimization techniques. Unfortunately, some technical challenges prevented him from accessing the necessary server domains, resulting in a more broadly-spanning conversation on P21 SQL Server tips and techniques. On September 21st, Brad will revisit his original presentation on Prophet 21 SQL queries.

P21WWUG CONNECT 2023 Insights

One of the most surprising discoveries from this year’s P21WWUG CONNECT 2023 event was the realization that a huge volume of the user community is still utilizing the legacy P21 desktop application. The migration to the P21 web client has been much slower than anticipated. While many customers are experimenting with the P21 Middleware Server layer, much of what is being conducted against the last P21 2021 version that supports both the P21 Middleware Server and the P21 Desktop client. This creates a problem because that version is a suboptimal way to transition into the Web UI version due to performance issues. Worse still, this version is losing support in the near future. The Estes’ team will spend the final session at the Fall ’23 Prophet 21 Summit addressing this subject, based on the work we’ve performed in helping customers make this important move. What is the best way to approach a P21 web migration from a planning perspective? And what are the most common hangups when migrating to the web version, and how are they most easily resolved? We’ll cover answers to both questions during this session.

The Fall ’23 Prophet 21 Summit Brings Your P21 Problems to an End

The EstesGroup team will be concluding the final session early to allow us to hold a roundtable discussion and to allow our attendees to bring up any and all of their P21 questions. Our P21 consulting staff will provide real-time answers. Epicor Prophet 21 events are a great opportunity for our team to better understand the needs of our user community and to provide some P21 help to our customers and friends. We look forward to seeing you there!

Prophet 21 Summit 2023 Registration
How to Optimize Prophet 21 Performance

How to Optimize Prophet 21 Performance

Load Balancing the P21 Server Stack into an N-Tier Architecture

Enterprise Resource Planning (ERP) system scalability is always a concern. Your user count grows. The database gets larger. The organization adds branches. As this all snowballs, several interconnected challenges begin to affect an ERP system’s ability to keep up. A central aspect of a company’s overall system performance is the ability to effectively divide user workload when the user count exceeds the capacity of a given application server.

Prophet 21 Load Balancing Performance Optimization

Epicor’s Prophet 21 distribution ERP software is no exception to this general concern, and one significant element of handling performance challenges when scaling your Prophet 21 application relates to load balancing. That said, when understanding how P21 load balancing functions within a P21 installation, it would be helpful to understand some basic application architecture concepts.

A common form of application architecture involves a three-tiered architecture:

  • At the lowest level, the database server stores and organizes an application’s data.
  • At the highest level, the user interacts with the application through the client user interface, whether browser-based or desktop-deployed.
  • The application server is responsible for orchestrating the interaction between the client and the database levels – the business logic at the AppServer level converts requests from the client into commands at the database level.

Epicor’s Kinetic application has such a 3-tiered architecture, going back to the days of its antecedents, E10, Epicor 905, and Epicor Vantage – the Epicor AppServer has long been the hub of Epicor administration. But not all ERP systems had such an architecture. Epicor’s P21 ERP is one such application. Historically, the Epicor Prophet 21 application was a 2-tiered architecture:

  • The P21 database stored the application’s data, as is the case with most ERP systems.
  • The P21 desktop application functioned both as the user interface and as the source of the Prophet 21 application’s business logic, communicating directly with the Prophet 21 database.

With the more recent versions of the Prophet 21 application and the introduction of the P21 Middleware Server, the P21 ERP application has taken on a more contemporary 3-tiered architecture. The Prophet 21 Middleware Server is essentially an application server layer. The introduction of the P21 application server layer allowed for innumerable capabilities that had been previously unavailable with the P21 desktop application.

One such capability is the P21 API layer. ERP systems normally provide API connectivity at the application server layer – the ERP API functions in the place of a client application, sending requests to the application server. The application server layer interprets these requests as it would a request from an end user client.

The API layer allows for an exponential increase in integration opportunities, enabling a more decoupled hybrid cloud architecture — one where multi-system interactions no longer had to reside at the database level.

The challenges to scaling a P21 ecosystem don’t end with a three-tier server stack.

As user counts increase, the need for additional application servers similarly increases. And with fluctuations in the timing that users access the application, it becomes difficult to manage and balance the user load across the overall environment. This can lead to performance bottlenecks, among other things. Enter P21 load balancing.

A system admin can implement load balancing in one of several forms. Load balancing can occur from within the application itself – the application decides how a given user session will be handled. An admin can also choose to implement load balancing from outside the application, using an external load balancer.

When using an external load balancing appliance to level out your P21 ERP user sessions, the load balancer controls the user flow differently than a traditional 3-tiered application configuration. In such an environment, the client application speaks first to the load balancer, rather than speaking to the middleware server directly. Based in the middleware servers available, and the current load profiles in play, the load balancer guides the client request to the appropriate P21 middleware server.

What makes external load balancing of your P21 environment so helpful is its transparency – the balancing of user load is, in fact, invisible to the end users involved. This allows your P21 administrator to fine-tune performance over time, as load patterns surface.

Better still, the use of an external load balancer adds a layer of security, allowing for identify management, multi-factor authentication, and security group management, to better lock down and secure your P21 enterprise. This abstraction of the application server from the client allows for a truly N-tiered architecture: an architecture that can segregate various interactions with the P21 database, allowing for a diverse orchestration of functionality and capability.

Prophet 21 Performance in Action

EstesGroup provided the infrastructure for the P21 Lake Erie User Group meeting in December of 2022 at the Embassy Suites hotel in the greater Cleveland area. This Epicor Prophet 21 ecosystem included a load balanced P21 middleware server layer. A depiction of the system architecture can be seen in the image below:

Prophet 21 Perfomance P21WWUG

Do you need help optimizing your Epicor Prophet 21 performance? Chat with us now to begin a conversation with a P21 expert today!