Forbes Council Member and SAP S/4HANA Cloud Solution Architect RahulBhatia shares an article that provides a comprehensive guide on planning a public cloud ERP implementation. It emphasizes the importance of thorough preparation and strategic planning to ensure a successful transition to cloud-based ERP. One of the first steps is to define clear objectives and outcomes for the implementation project, aligning them with overall business goals. The article suggests conducting a needs assessment to identify specific requirements and gaps in current systems. Engaging stakeholders early in the process is crucial, as their input can guide decision-making and foster buy-in. Bhatia recommends forming a dedicated project team with representatives from various departments to ensure diverse perspectives. A detailed project timeline with milestones should be established to track progress and maintain momentum. Choosing the right vendor is another critical step; organizations should evaluate potential partners based on their expertise, track record, and support capabilities. The article highlights the necessity of budgeting for not just the initial implementation but also ongoing maintenance and potential scaling needs. Training and change management are essential components, as employees must be equipped to adapt to new systems and processes. The guide also stresses the importance of data migration and integrity, advising organizations to develop a robust plan for transferring data to the new ERP system. Testing the system before going live is crucial to identify and address any issues. Post-implementation support and continuous improvement should be part of the long-term strategy, ensuring the ERP system evolves with the organization’s needs. Bhatia encourages organizations to remain flexible and open to adjustments throughout the implementation process, as challenges are likely to arise. By following these guidelines, businesses can enhance their chances of a successful public cloud ERP implementation that delivers long-term benefits.

 

For Full Article, Click Here

  1. Select User ConfigurationUsers.
  2. \
  3. Highlight a user. In User Tasks, click New.

 

  1. Select a task.
  2. If the assignment is temporary, specify the Startand Stop Dates.

If the assignment is not temporary but will begin on a future date, specify a Start Date only.

If the assignment is immediate and permanent, leave the date fields blank.

  1. Click Save.

Alternatively, you can use this procedure:

  1. Select User ConfigurationTask.
  2. Select a task.
  3. In User Tasks, select ActionsCreate.
  4. Select a user from the User list.
  5. If the assignment is temporary, specify Startand Stop Dates.
  6. Click Save.

If you’re receiving this error, its usually a simple fix. Also note your IBM Websphere SystemOut.log should be throwing exception errors as well.

 

First let’s make sure no crystalras.exe processes are using a lot of CPU power, if they are zeroed out, chances are no one is in the system attempting to run a report:

 

Once that is verified, open up the Central Configuration Manager directly on the LBI server and highlight your SAP Crystal Reports Server processes, click STOP

 

Wait 10 seconds while they are in STOPPED status, then select and start them back up.

Now log back into LBI and try to run reports.

 

If this is still not working, try to reboot the entire server again. If it’s not resolved, it’s likely something with your configuration settings.

 

Good luck!

If you have a job in job schedular that has a status of Waiting or Waiting on Time and you would need it to run immediately, you can assign the highest priority to the job and it will run immediately on the designated queue regardless of how congested the job queue is. If another job that calls the same program in the same data area is already running, however, the selected job is given a status of Waiting Step and is still listed on the Waiting Jobs form.

To run a waiting job immediately

  1. Access Job Scheduler and click the Waiting Jobs button.
  2. Select the Waiting or Waiting on Time job that you want to run.
  3. From the Actions menu, select Run Job Immediately.
  4. If you want to change the job queue, select the name of the job and click Change.

This job queue overrides the job queue assigned for the job when it was submitted. If you do not assign a job queue, Job Scheduler assigns the default job queue (**********).

 

Infor previously announced that all versions of on-premises Infor OS and Infor OS Lite products would transition from Supplementary Update Maintenance to Sustaining Maintenance by December 31, 2024. This transition has been extended to March 31, 2025, for on-premises Infor OS and Infor OS Lite products used with Infor Lawson V10 applications.  This does NOT affect cloud customers.

On-Premise Products Affected:

  • Infor Lawson System Foundation (LSF)
  • Infor Human Resource Management (HRM)
  • Infor Lawson Enterprise Financial Management (EFM)
  • Infor Lawson Supply Chain Management (SCM)
  • Other products within the Infor Lawson V10 suite

Action Required:

Customers using on-premises Infor Lawson V10 applications with on-premises Infor OS or Infor OS Lite must migrate or upgrade to the Infor Local Technology Runtime (LTR) platform before March 31, 2025.

On-premises Infor Lawson V10 applications are certified for use with the Infor LTR platform. For details on the required Infor Lawson V10 versions compatible with Infor LTR, refer to the Infor Lawson Compatibility Matrix available on Infor Concierge under Important Documents > Lifecycle Policies tab.

For more information, please review Knowledge Base (KB) article 3531027, which includes the original product announcement and an FAQ document.

NOTE that if you do not see Infor LTR in your product downloads, you will need to schedule some time with your account representative to get the product for you.

 

Problem:

I ran AP155 and AP170 before running AP150 and received the same message that there is no data in report file.  I ran AP150 again and am seeing the same message.

Please see screenshots below:

 

Resolution:

 

Check AP52 if it shows that these invoices are waiting to be brought into Lawson via AP520.

Run the AP520 in update mode and then process the AP150.

 

Before we get started, you’ll need to have distribution groups setup already. See our article on how to do that if you haven’t. You’ll likely need higher privileged access to perform these tasks.

Assuming you already have distribution groups setup, follow the steps below.

  1. Login to Lawson portal.
  2. Go to a Lawson job that you want to set a distribution group for.
  3. Once the job is created, click on the “Reports” button above the Job Name.
  4. In Report Properties, select Distribution Group and then select one of your created distribution groups from the Group Name drop down box and press OK when done.
  5. Click “Change” to save the report properties. Now Inquire on the job and click Reports again to verify the changes were made.

That is, your reports will now show up in the users print manager that are in the selected distribution group. All without having to go to LID.

 

If this task is crucial for your organization’s ongoing operations and requires expert organization and proactive management without the need for a full-time or on-site staff, Nogalis offers specialized consultant services. Our team of experts excels in maintaining and optimizing Lawson systems, providing proactive support tailored to your specific needs. Explore how Nogalis can improve your operational efficiency by contacting us through our dedicated contact page.