Archive for category: Frontpage Article

As of December 31, 2024, Infor is set to transition all versions of the products mentioned below to the next stage of support, following the Product Lifecycle Policy for Infor OS On-Premises (Infor OS OP) products.

The affected products moving from Supplementary Update Maintenance to Sustaining Maintenance are:

1. Infor OS
2. Infor OS Lite

Reasons for the Change

This transition is prompted by the retirement of several underlying prerequisite components that Infor OS OP relies on, including Amazon Corretto® 8 (Java®), as well as versions of Microsoft Windows®, Microsoft SQL Server, Microsoft .NET, and other prerequisite technologies.

Impact on Users

Supplementary Update Maintenance for these products will continue until December 31, 2024. After this date, they will enter Sustaining Maintenance. During this phase, users will retain access to existing patches, documentation, and Knowledge Base articles. However, no new updates or fixes will be provided for these products.

It’s crucial to note that the third-party products required for Infor OS OP are also approaching the end of their support cycles. Infor strongly advises careful consideration of the use of these products, as continuing to use Infor OS OP beyond 2025 may expose your environment to security risks.

Available Alternatives

Infor is offering two alternatives for customers with any version of the affected Infor OS OP products:

1. For customers active on support/maintenance: A no-cost license exchange to a new on-premises (OP) product called Local Technology Runtime (LTR).
2. For all customers: Purchase access rights to a new multi-tenant (MT) Infor OS tier, which includes a coterminous OP license to the LTR product available in option 1.

Introduction to Infor LTR

Infor LTR will replicate the critical core services of the current Infor OS OP product, including Security, Ming.le, ION, Infor Document Management (IDM), and API Gateway. This will be achieved using new technical prerequisites committed to support until the end of the decade. The hybrid LTR option allows connection to MT Infor OS, extending the multi-tenant world to on-premises customers.

Installing LTR involves a straightforward technical upgrade, akin to applying the latest version of Infor OS OP. This means no major rip-and-replace—just a simple, in-place upgrade. The transition from old Infor OS OP to new LTR OP will be seamless for end-users and administrators, requiring no retraining.

While LTR OP will be updated to maintain compatibility and resolve defects, new innovations and updates will only occur in Infor OS MT.

Infor’s Commitment to Business Requirements

For customers seeking to exchange their current Infor OS OP for a new OP-only solution, Infor LTR provides the same core functionality with planned support until the end of the decade.

For those aiming to leverage the latest technologies for digital transformation alongside existing on-premises applications—a hybrid solution:

1. Infor OS MT offers a more extensive and feature-rich set of services and capabilities.
2. Infor LTR OP is included, opening the door to unique hybrid deployment options.
3. Combining MT and LTR unlocks new functionality and possibilities, growing over time with Infor OS MT releases.
4. The Infor OS MT license option serves as a launchpad for digital transformation services such as Augmented Intelligence with Machine Learning (AI/ML), Enterprise Automation with Robotic Process Automation (RPA), and other add-on technology services exclusive to the MT world.

These options grant flexibility to run core technology services on-premises, in the multi-tenant cloud, or a mix of both, according to your requirements.

Next Steps

Infor strongly recommends initiating the transition planning process by reaching out to your Infor representative or submitting a support ticket. Regardless of the chosen path, Infor is committed to assisting you in developing the most effective strategy, ensuring you have the necessary products, capabilities, capacity, and licenses to meet your requirements.

 

If you have services for approval or other types of flows in IPA, and they stop getting triggered after a Landmark update, it is possible that you need to repackage and redeploy the LPS jars.  This is good practice after a Landmark CU anyway.

1. On the Landmark server, open a Landmark command window
2. Run the command “packageLPSClientJars”
3. Copy the LASYSDIR/LPS/LPSClientJars.jar file to the Lawson server at GENDIR/bpm/jar
4. Run commands stoppfem and stoppfrmi
5. Navigate to GENDIR/bpm/jar in a command window with environment variables set
6. Run tar -xvf LPSClientJars.jar
7. Run commands startpffrmi and startpfem
8. If the changes don’t take effect, reboot the Lawson server

 

Using Spreadsheet Designer

Go to the field and do a Ctrl + shift and left click on your mouse, this will give you the Business class that you will need to have and the name of the field.  In this example we will be looking at the Employee business and the field Work Type

 

Let’s open up Excel and go to the Infor tab, and we will be doing a query. Go to the Insert Query and click on the drop down arrow

This box will appear, do a drop down and pick the environment name for your Data Area

 

In the second box, we will be typing in the business class, in this example it will be Employee

 

As you are typing in the second box the business class will appear

 

Now you see all the field that you can pick from under Employee Business Class. The ones that are Orange are required fields and need to be in your Query.  The Employee is the Employee ID number

 

We will be using for this example the following fields,

HROrganization

Employee

Name.FullPresentationName

 

Scroll down and pick

StartDate

Adjusted Start Date

Relationship to Org

Relationship Status and click on Insert

 

Go to the Employee and rich click on your mouse, pick Add to Filter

 

Go to the bottom of the Insert, and you will see Employee. Next to Employee, under Value enter your Employee ID number.

 

Like Below

 

Now click off that field

 

Go to Refresh at the top of the page by the Infor sign and do a drop down

 

We will be clicking on Refresh

 

This box will appear

Your Information will appear,

 

Now let add Work Type to our report, Find the Field Work Type and check the box,

Click on Refresh again and the Work Type Information will be part of your Report

 

 

So you ran the PR160 again and it went into recovery due to an ACH file path parameter not being correct.

 

We don’t want to delete this but we also want to resolve it so we can recover it quickly.

 

To do this, perform a jobdump on this specific job:

jobdump -d -o Job -v JobName PR160JOBNAME -v UserName YourUSERNAME YourUSERNAME_dmp.txt

 

Once you dump this job, edit it in notepad or notepad++ and locate the incorrect path, example below:

 

Update this path ONLY to what you need it to be and use jobload to reload it:

jobload -c -o Job YourPR160JOBNAME.txt

 

Then recover the job and it should put the file in the correct path.