Lift-and-shift ERP (enterprise resource planning) migrations often fall short in supporting modern, subscription-based revenue models, but decoupling billing with platforms like Zuora simplifies complexity, ensures compliance, and enables faster, more flexible monetization. In a recent ERP Today, Radhika Ojha highlights a growing challenge for ERP teams: lift-and-shift migrations aren’t keeping up with today’s recurring and usage-based revenue models. Moving a legacy ERP to the cloud might improve infrastructure, but it doesn’t fix outdated billing logic. Traditional ERPs were built for linear transactions—one order, one invoice, one payment. That’s not enough when your business model includes subscriptions, mid-cycle changes, and usage-based billing. The result? Manual workarounds, custom code, and risk of revenue leakage. Ojha shares a real-world use case with 24 Hour Fitness. Their Oracle ERP could only bill members on six fixed days per month. This led to complex proration and delayed revenue recognition. Instead of re-engineering their ERP, they integrated Zuora—a purpose-built billing platform—and moved to daily billing. The outcome: more flexibility, fewer errors, and faster cash flow. The smarter approach, according to Ojha, is to let your ERP handle the general ledger. Use a platform as a revenue sub-ledger to manage subscriptions, billing, and compliance. This decoupled model reduces ERP customization, speeds up transformation, and gives finance real-time data. This matters to ERP teams because it reduces risk during ERP migrations, it automates complex billing and revenue recognition, and it supports faster product launches and pricing changes. If your revenue model has evolved, Ojha concludes, your ERP strategy needs to evolve too. Lift-and-shift alone just won’t get you there.
For Full Article, Click Here
How to remove the Infor Logo from your Lawson Business Intelligence dashboard
Articles, Frontpage Article, NewsBefore:
After:
If you found this article helpful, Nogalis offers managed services and technical resources to assist with customizing and maintaining your Lawson Business Intelligence dashboard. Whether it’s tasks like removing logos or other system configurations, our team provides the support you need. Contact us to learn more about our managed service offerings and how we can assist with your Lawson system needs.
Beyond the Inbox: The Human Side of AP Automation
NewsKey takeaways for ERP professionals:
Use OCR to extract invoice data from emails automatically.
Replace manual chasing with rule-based approval matrices.
Rely on native NetSuite apps like SquareWorks for seamless integration and reliability.
Automation isn’t just a tech upgrade—it’s a catalyst for transforming the role and morale of AP teams.
For Full Article, Click Here
Weekly Patch Notification: August 9, 2025
Articles, Frontpage Article, PatchesUpdating GLMonitor
Articles, Frontpage Article, NewsSometimes the following error on GL may occur: Resolving “Cannot run this program while GL190 is running” error when trying to release journal entries in GL40.1
You may run into this error at some point in GL40.1 or GL45.1:
Fortunately, there’s an easy fix to this. First login to Lawson portal and search GLMONITOR:
In GLMONITOR, type in GL190 and hit Inquire, if you get results and notice the run time, the process is in fact still running and causing the issue with GL40:
Go to job scheduler by opening LID and typing in jobschd >> F7 + A to select all users >> Then W to go to waiting screen.
Look for any GL190 jobs running and verify the User Name is the same one in GLMONITOR when inquiring on GL190 program. Check the error and if its safe to recover, recover it and let the job complete.
Go back to GLMonitor and inquire on GL190 to verify the job is no longer running:
Go to GL40.1 and release your Journal Entries. Good luck!
Why Lift-and-Shift ERP Strategies Are Inadequate for Modern Revenue Models
NewsLift-and-shift ERP (enterprise resource planning) migrations often fall short in supporting modern, subscription-based revenue models, but decoupling billing with platforms like Zuora simplifies complexity, ensures compliance, and enables faster, more flexible monetization. In a recent ERP Today, Radhika Ojha highlights a growing challenge for ERP teams: lift-and-shift migrations aren’t keeping up with today’s recurring and usage-based revenue models. Moving a legacy ERP to the cloud might improve infrastructure, but it doesn’t fix outdated billing logic. Traditional ERPs were built for linear transactions—one order, one invoice, one payment. That’s not enough when your business model includes subscriptions, mid-cycle changes, and usage-based billing. The result? Manual workarounds, custom code, and risk of revenue leakage. Ojha shares a real-world use case with 24 Hour Fitness. Their Oracle ERP could only bill members on six fixed days per month. This led to complex proration and delayed revenue recognition. Instead of re-engineering their ERP, they integrated Zuora—a purpose-built billing platform—and moved to daily billing. The outcome: more flexibility, fewer errors, and faster cash flow. The smarter approach, according to Ojha, is to let your ERP handle the general ledger. Use a platform as a revenue sub-ledger to manage subscriptions, billing, and compliance. This decoupled model reduces ERP customization, speeds up transformation, and gives finance real-time data. This matters to ERP teams because it reduces risk during ERP migrations, it automates complex billing and revenue recognition, and it supports faster product launches and pricing changes. If your revenue model has evolved, Ojha concludes, your ERP strategy needs to evolve too. Lift-and-shift alone just won’t get you there.
For Full Article, Click Here
Never Too Small: 3 Ways SMEs Use Cloud ERP To Drive Growth
NewsFor years, enterprise resource planning (ERP) systems were tools only large corporations could afford—complex, costly, and time-consuming to implement. But with the rise of cloud-based ERP solutions, that’s changing fast. Small and mid-sized enterprises (SMEs) are now tapping into powerful systems that help them scale, stay competitive, and even shape the future of the technology itself. In a recent Forbes article, content strategist Andrea Waisgluss highlights how SMEs are using cloud ERP to their advantage in three key ways:
Cloud ERP isn’t just leveling the playing field—it’s giving SMEs the tools to lead. Whether it’s quicker rollouts, smarter tech, or a seat at the table in shaping future features, these businesses are proving that size is no barrier to innovation.
For Full Article, Click Here
Resolving the “Operator Not Authorized to Change Unit Cost” error
Articles, Frontpage Article, NewsThis is one of those Lawson errors that could waste a morning of work looking through the Infor knowledge base, analyzing/changing security, and or reviewing logs.
So, you’re on PO20.1 and want to make a change to a PO entry and get this error:
To resolve this is actually incredibly simple and can be changed on PO04.1 at the bottom of the Buyer Information Tab (your settings may be different based on your needs):
If you happen to get a similar issue for a requisition cost change “Requester not authorized to change unit cost”, simply go to RQ04 and allow unit cost override for the specific requester (your settings may be different based on your needs):
If you found this article helpful, Nogalis offers expert managed services to resolve Lawson errors like this quickly and efficiently. Our offerings include troubleshooting technical issues, streamlining processes, and providing functional finance resource assistance. Whether it’s addressing security settings, resolving errors, or enhancing workflows, our managed services ensure your finance operations run smoothly without the need for a full-time, in-house team. Contact us to learn how we can simplify and optimize your Lawson experience.
7 enterprise cloud strategy trends shaking up IT today
NewsIn a recent article from CIO.com, tech expert John Edwards gathers insight from industry experts and outlines seven major trends redefining how enterprises approach cloud strategy today. As organizations navigate rising costs, increased security threats, and growing infrastructure complexity, a more thoughtful and adaptive cloud model is emerging. Rather than defaulting to “cloud-first,” businesses are rethinking where and how workloads run, embracing hybrid models, automation, and industry-specific platforms. The article emphasizes a shift toward agility, governance, and workload optimization. Below is an overview of the 7 key trends:
Cloud strategy in 2025 is about intelligent placement, security integration, and financial discipline—not just infrastructure migration. As complexity grows, so does the need for smarter, more flexible architectures.
For Full Article, Click Here
Update SQL Tables after Data Refresh
Articles, Frontpage Article, NewsWhen you perform a data refresh in your SQL database, such as reloading data into tables, you may need to take steps to ensure dependent objects and overall database performance are optimized. Follow these steps to Update your SQL Tables after a Lawson Data Refresh.
First, open up the properties for the DB that was just refreshed and you can see that the DB tables have the PROD name.
Next, run the following SQL query for the TEST DB:
ALTER DATABASE INFORLAWTEST10 MODIFY FILEGROUP INFORLAWPROD10_DATA NAME = INFORLAWTEST10_DATA
ALTER DATABASE INFORLAWTEST10 MODIFY FILEGROUP INFORLAWPROD10_INDEX NAME = INFORLAWTEST10_INDEX
You’ve now updates your SQL tables post-refresh.
What Most Healthcare Cloud Migrations Get Wrong (And How To Get It Right)
NewsIn a recent Forbes article by Forbes Council Member Sandipan Biswas, it highlights a critical issue in healthcare IT: many cloud migrations fail not because of technical gaps, but due to a flawed mindset. Organizations often treat migration as a basic infrastructure upgrade, overlooking its broader strategic implications for compliance, security, and patient care. Biswas outlines five common missteps and how to avoid them.
Five Common Cloud Migration Mistakes:
Fix: Use migration as a chance to modernize with modular, serverless architectures.
Fix: Define roles, access, and lifecycle policies before moving data.
Fix: Enforce encryption, least-privilege access, and continuous monitoring.
Fix: Build in logging, tracing, and performance dashboards from the start.
Fix: Treat it as an ongoing process with regular updates and long-term ownership.
Cloud migration in healthcare must be approached as a long-term transformation, not a one-time project. By avoiding these common traps, organizations can build secure, compliant, and scalable systems that support both innovation and patient trust.
For Full Article, Click Here