News, Events and Articles
You are here: / News, Events and Articles

Empty AP160ACHTAPE File

, ,

Description:
When running the AP160 the job did not create an AP160ACHTAPE to be sent to the bank, this file is empty.

Resolution:
AP160 runs the Lawson utility cnvtape to read the AP160ACHTAPE_SEQ file and to write out the AP160ACHTAPE file. To resolve this issue, you need to perform the following:

A. When using Lawson Security:

  1. Open Lawson Security Administrator
  2. Double Click on Profile Id “ENV”
  3. Double Click Security Class “DBAccess”
  4. Click “Add Rule” Button
  5. Select Securable Types “Executables”
  6. Expand Delivery Tokens
  7. Check box by cnvexp
  8. Click “Grant All Access” radio button
  9. Click Apply Button.
  10. Click on Profiles
  11. Double Click on Profile Id “ENV”
  12. Double Click Security Class “TranslTools”
  13. Double click on Rule Object “TRANSLATE”
  14. Right click Translation Tools and choose Select Next Level
  15. If cnvtape doesn’t exist under TRANSLATE then you must add it through Tokendef – Environment Form IDs – Category: TRANSLATE – Title: Convert Tape File
  16. Make sure radio button next to Grant All Access is checked
  17. Click Apply Button
  18. Double Click on Class Assignment>select the Role you want to assign the TranslTools Security Class to>Click Assign Security Classes Button>highlight TranslTools>click “>” Button>Click Close Button>Make sure that Role is assigned to user.

Once you have change users access, have the user run AP160 for Rerun Options – Recreate Tape=Y and the serial number of your tape to create the AP160ACHTAPE file which will be sent to the bank.

Cybersecurity In The Age Of AI: 3 Imperatives For Resilient ERP

Once upon a time, securing enterprise resource planning (ERP) systems meant locking the data center door. But as Supply Chain Management expert Richard Howells explains in a Forbes article, today’s ERPs span clouds, APIs, and AI tools that power global operations—and that connectivity brings new risks.

The challenge isn’t a shortage of tools; it’s that attackers evolve faster than our defenses. Traditional threats like phishing and ransomware remain, but now AI makes them faster and smarter. Generative AI can craft convincing phishing emails, while deepfakes give scams frightening credibility. IBM reports that ransomware breaches now average over $5 million, and insider misuse continues to climb.

Complexity and Shared Responsibility
ERP systems no longer live in a single, secure space. As IBM consultant Ryan Throop notes, “ERP used to be about roles and authorizations—now it’s about resilience.” Cloud providers protect infrastructure, vendors handle patches, and integrators manage connectivity, but the enterprise itself still owns data protection. That patchwork often leaves dangerous visibility gaps.

Three Keys to ERP Resilience

  1. Culture and Hygiene – Human error is still the biggest risk. Modern security awareness training now simulates real-world attacks, helping ERP users understand the stakes of careless actions.
  2. AI for Defense – AI can detect anomalies, flag suspicious access, and cut breach costs by millions, allowing teams to focus on strategic response.
  3. Governance and Trust – Leading companies demand transparency from partners, standardize third-party security assessments, and share threat intelligence across ecosystems.

Ultimately, ERP cybersecurity isn’t just about keeping threats out—it’s about building digital trust. By combining culture, AI-driven defense, and strong governance, organizations strengthen resilience and confidence across their entire value chain.

 

For Full Article, Click Here

File Not Found error in LID when adding a job

, ,

After a fresh install of Lawson, you may receive a “file not found” error in LID when adding a batch job.  Or, inquiring on certain forms might time out.  The batch job itself may show an error message alluding to the LUU utilities (such as invalid fstab option).  The issue is potentially an incorrect LAW_COBRTS_PATH.

To resolve, open a command line utility with the Lawson environment variables set.  Type command “laconfig”.  The configuration window pops open.

Select your environment.

On the environment tab, check the LAW_COBRTS_PATH.  If it is incorrect, fix it.

 

Reboot the server, or restart the services, and try your batch job again.

 

The Great Cloud Recalculation

In today’s digital landscape, enterprise systems are indispensable for businesses to stay competitive. But as cloud infrastructure becomes increasingly vital, companies are rethinking their approach to cost management. As Craig Powers highlights in ERP Today, organizations are moving beyond traditional cost-cutting tactics to adopt more strategic “cost takeout” strategies—focused on improving efficiency and reducing waste without sacrificing performance.

Cost takeout involves right-sizing infrastructure, consolidating redundancies, and streamlining operations. Many companies have found that migrating to a new cloud provider, like Oracle Cloud Infrastructure (OCI), offers an opportunity for significant cost reductions. By analyzing their financial structure and leveraging cloud capabilities, companies can unlock savings while setting the stage for future business transformation—especially in areas like data and AI (artificial intelligence). For instance, a global education services company reduced monthly infrastructure costs by 30% and improved scalability, while a retail optimization provider cut labor costs by 40% after moving to OCI. While the potential benefits of cloud migration are clear, the process requires careful planning. Cost takeout isn’t just about finding a cheaper provider, Powers states, it’s about ensuring that the migration process itself is cost-effective. Companies should conduct proof-of-concept trials, analyze total cost of ownership (TCO), and collaborate across IT, finance, and business teams to maximize savings.

Powers concludes for ERP (enterprise resource planning) leaders, this means taking a closer look at your current infrastructure and considering migration to more cost-efficient solutions. As Powers advises, reexamining the financial side of enterprise systems could free up resources for innovation and growth—while optimizing both performance and costs.

 

For Full Article, Click Here

The ERP Acceleration Paradox: 5 Strategies to Beat the 75% Failure Rate

High-profile enterprise resource planning (ERP) failures like Hershey’s $100 million Halloween disaster and Nike’s $400 million overhaul reveal a troubling truth: the rush to deliver “on time and on budget” often derails success. This Acceleration Paradox, according to tech writer Puneet Thakkar, shows that true speed isn’t about cutting corners—it’s about accelerating value realization through smarter strategy, disciplined execution, and a focus on measurable business outcomes. In his article for SSON, Thakkar dives into the troubling statistics behind ERP transformations—and offers five strategic playbooks to beat the odds. He points out the paradox: while companies push for faster, on-time, on-budget ERP roll-outs, the actual success rate is alarmingly low—somewhere between 55% and 75% of ERP projects fail to deliver what they set out to achieve. He argues that real “acceleration” isn’t about rush-launching software, but about speeding up meaningful business value.

The five strategies he recommends are:

  1. Anchor in value, not just technology. Don’t treat ERP as a software purchase. Treat it as a business transformation, with clear targets.

  2. Adopt a modular, agile-friendly architecture. Thakkar advocates composable ERP (“Lego-brick” style) and moving from a big-bang waterfall to a hybrid waterfall + agile delivery model for faster adjustments.

  3. Clean and prepare your data early; don’t leave it until last minute. Data quality isn’t just a tech task—it’s foundational. Prioritise migrating only critical “hot” data, and use AI/ML tools for cleansing.

  4. Embed automation from day one—even through testing and process mining. Use process-mining to reveal your current state, then automate your testing (via RPA) to avoid launch surprises.

  5. Engineer adoption, don’t just train. Training is not enough. Use digital adoption platforms for on-the-job guidance, and build a network of “super users” so the transformation is adopted socially and operationally.

Thakkar emphasizes that a successful ERP isn’t just a “system of record”—it must become an “engine of velocity.” When you align your roadmap to business value, design flexible architecture, clean your data, automate smartly, and prioritize people change, you shift from chasing launch metrics to achieving transformation outcomes.

For Full Article, Click Here

A Guide to Managing Infor Year-End Updates for AP and Payroll

, ,

Join us for an in-depth session on best practices for planning, implementing, and testing Lawson year-end updates for Accounts Payable (AP) and Payroll (PR). Our experts will guide you through key steps to ensure a smooth and compliant year-end process — from preparation and configuration to validation and testing.

Gain valuable insights, practical tips, and actionable steps to help your organization close the year efficiently and confidently.

 

 

Get Started Today!

Don’t wait!  Contact us to get a quote on your server migration now!

An accompanying article for this webinar can be found here

How to find users that report directly under a manager in XM

, ,

Follow the steps below to learn how to find users that report directly under a manager in XM

 

First, in Mingle, go to Infor XM

 

Next, select Admin >> Users

 

Then locate the manager you want to search for users under:

 

Search fore your manager by name, then pick a result:

Now that we have the manager we want, click Find at the bottom and on the right hand side you’ll see all the users that are under this manager.

And that’s all there is to it! Just repeat the steps to view all users under different managers.

APIX Achieves SOC 2 Type 2 Compliance: Strengthening Trust and Security for Our Customers

, ,

At Nogalis, security and trust have always been at the heart of everything we do. Today, we’re proud to announce that our APIX ERP Archive Solution is officially SOC 2 Type 2 compliant — a major milestone that reinforces our commitment to safeguarding your data.

After earning SOC 2 Type 1 compliance earlier this year — confirming the strength of our security design — we set our sights on the next milestone: SOC 2 Type 2. This certification demonstrates that our controls don’t just look strong on paper; they perform reliably in practice, ensuring your data remains protected with the highest standards of security and trust.

Developed by the AICPA, the SOC 2 framework is an independent standard for managing customer data based on five key trust principles: security, availability, processing integrity, confidentiality, and privacy. Meeting these standards confirms that our internal controls and processes align with the most rigorous data protection requirements.

Our SOC 2 Type 2 assessment was conducted by independent auditing firm Sensiba LLP, who worked closely with our team throughout the process. Their expertise, professionalism, and partnership were instrumental in helping us reach this milestone.

What this means for you:

  • Your archived ERP data is protected under industry-leading security practices.
  • Our systems are continuously monitored and improved for data integrity and availability.
  • We remain transparent and accountable in every step of our data handling.

We’re proud to share this achievement with our customers and partners, and we’ll continue to invest in security and compliance as part of our promise to deliver the safest, most reliable ERP archiving experience possible.

Thank you for trusting Nogalis and the APIX ERP Archive Solution with your data.

— The Nogalis Team

Simplifying SSO with Infor LTR as STS

, ,

In today’s enterprise environment, seamless and secure access across applications is critical. Organizations increasingly rely on Single Sign-On (SSO) to simplify user authentication and improve security posture. If you’re already leveraging Infor’s suite of products, you might be surprised to learn that Infor LTR (Lawson Technology Runtime)—commonly seen as middleware—can act as a powerful SSO tool, much like Infor OS.

At Nogalis, we’ve helped numerous organizations harness Infor LTR as a Security Token Service (STS), enabling robust, federated SSO integrations across Azure AD, AD FS, Okta, and other SAML 2.0-compliant identity providers. This article outlines how Infor LTR can simplify your authentication landscape while ensuring scalability and security.

What Is Infor LTR?

Infor LTR is the core runtime wrapper for Infor web applications and will be supported until at least 2029. While often viewed as an infrastructure component, it also functions as a flexible STS, enabling secure federated identity across your enterprise apps.

Why Use Infor LTR as Your STS?

  • Federated SSO across multiple Identity Providers (IdPs)
    Infor STS supports Azure AD, MS Entra, AD FS, Okta, and any SAML 2.0-compliant provider.
  • Centralized SAML Authentication
    You can configure all your applications to use Infor STS as the single point of SSO integration.
  • Long-Term Viability
    With support guaranteed into 2029, LTR is a stable investment in your identity infrastructure.

How It Works – The Big Picture

  1. Establish Trust between your application and identity provider using STS.
  2. Exchange Federation Metadata between STS and your IdP.
  3. Configure your applications to delegate authentication to Infor STS.
  4. SAML-based handshake manages identity, assertions, and access.

Installation & Setup

Step 1: Migrate LTR to STS Mode

Using the LTR ISO, mount and run (in a command utility):

setup.exe –v”MIGRATETOSTS=true”

Step 2: Access STS Admin

This is your hub for managing Identity Providers (IdPs) and Service Providers (SPs). You’ll:

  • Add/Edit IdP connections
  • Add/Edit SP connections
  • Download metadata files and certificates

Identity Provider Configuration

🔹 Azure AD

  • Create a Non-Gallery App in Azure
  • Upload the Infor STS SP Metadata file
  • Export the Azure AD IdP Metadata and import it into STSAdmin

🔹 AD FS

  • Add a new Claims-Aware Relying Party Trust
  • Import the Infor STS SP Metadata XML
  • Download FederationMetadata.xml from AD FS and import it into STS

🔹 Okta

  • Create a SAML App Integration in Okta
  • Manually configure Entity ID and endpoints (Okta doesn’t accept SP metadata files)
  • Download and import Okta’s IdP Metadata XML into STS

Application Configuration

In your Infor or third-party app:

  1. Set SSO Service URL to:

https://your-ltr-server.com:9553/inforsts/infor/{GUID}/idp/samlSSO

  1. Configure SAML properties:
    • UsernameField
    • PasswordField
    • SLOUrl
  2. Upload STS signing certificate as the IdP certificate in your app
  3. Export app’s signing cert, then import it into STS Admin

Final Checklist – What You’ve Done

✅ Downloaded IdP federation metadata
✅ Downloaded STS SAML SP metadata
✅ Uploaded metadata files to STS and your IdP
✅ Configured your app to use Infor STS as the SSO provider
✅ Completed mutual trust between your application, STS, and identity provider

Ready to Get Started?

At Nogalis, we specialize in Lawson and CloudSuite implementations, migrations, and custom development. Whether you’re looking to modernize your identity strategy or get more from your Infor investment, we’re here to help.

📧 Contact us at:
Desi Houze – desi@nogalis.com
Tan Rezaei – tan@nogalis.com

🔗 Learn more about our Lawson Data Archive Solution