2018 YE Initial CTP for Apps 10

We have just installed the 2018 YE Initial CTP for Apps 10 in Test. There are 50+ PR programs listed as affected in the appinstallanalysis.log not to mention several BN/LP/PA programs. In addition we were required to run a reorg which I don't recall ever having to do before for YE CTPs. I am quite concerned about the short timeframe to be able to test/verify all of the affected programs. Has anyone else encountered a similar situation?

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

sriman-shivakoti

I must have missed the announcement. When did they come out?

Hans Mueller

December 3

Robert Canham

We just got ours installed. We did not need a reorg, so you may have something else hanging out there.

As for the impacted list, I did see a significant number of programs that were compiled due to IFSVALWS. Looking into that further, this is a work file for IFSVALPD which appears to do validation of input strings for special characters. Not sure how much of an impact that is, but it seems low impact to me.

unknown

We didn't have to do a reorg either. Must have had another patch that didn't get activated.

unknown

Same here. I applied at the end of last week and no reorg in my Test environment.

0911060553270289.pdf

plancor

Applied here this morning to Test, and yes, we needed a reorg and it functionally changed 63 programs.

0712131256598360.doc

Hans Mueller

Folks... I hope that everyone understands how S3 application patching works, and how the impact to applying this patch or any patch will be different for each customer depending on the "other" CTPs and MSPs you have already taken.

20241015_183206.jpg

Robert Canham

Correction to my previous post. We missed the Benefits year end since it is in a different place. That did cause a reorg. I have to dig further in to see what the impact is program wise.

jreese

Hans,

The issue is this patch should only be including changes needed for the year end processing and not bundled up with other fixes. They have tried this in the past and no one has time to be testing changes this time of year other than those that are critical changes.

plancor

Hans, just because it's understood, doesn't make it any less painful. This is a forum for customers to share successes and struggles. Please understand - and pass on - our frustrations.

bhillz

RE: jreese: Spot on! running an On-Premise shop, having just the required Year-End changes makes everyone's life simpler in this stressful/busy time period. Having N additional/unforeseen patches applied is not in anyone's best interest.

Hans: I do understand from a vendor's perspective, you would like everyone to be on the latest/greatest. It makes you life simpler. After all, you already fixed the bug, who wouldn't want it?

For Cloud, especially Multi-tenant, there is no choice. You get everything on the vendors timetable. It also means that you either: trust the vendor coded everything correctly every time or you are forever reading the latest release notes and TESTING everything-always.

This isn't necessarily a reason not to go multi-tenant cloud, just realize the consequences.

unknown

Hello,

I came to this forum after downloading the patch from:

www.inforxtreme.com > Downloads > Products (opens dl center window)

Lawson Applications > Lawson Applications - Regulatory Releases > Regulatory Release - Payroll Initial Download 2018 - All Supported Platforms patch.

Do you know where I can download the Benefits year end patches?

Reverse_Charge_Verfahren_03.pdf

Hans Mueller

I understand your frustrations, but I want to make sure that the frustrations are properly placed. I also am trying to ensure that folks who are reading and contributing to these forums have a base understanding of how this patching all works, because there is often confusion.

First, its important to note the background of how S3 CTPs are applied and how the patching mechanism works. Every CTP that is applied is compared to the individual programs and libraries already installed on the target system. And the comparison goes back to the base version. So every CTP is potentially able to patch any application file in the system that it relies on in order to get it to the prerequisite level to support a compile. That is flexibility that you all have asked for and rely on every day, but it also creates a very high level of variability. Customer A's impact is different from Customer B's impact is different from Customer C's impact of any specific CTP. So even two customers' on the same MSP will have different impacts depending on individual CTPs they have processed.

Second, for many years, the Payroll and AP product development teams have done everything possible to isolate the Year End CTPs from spilling over and including "other" non year end content. That has been a policy in place for almost 15 years - I was on the Global User Group when we pushed that back many years ago. The truth is they go to exceptional lengths to keep isolation wherever they can. But they can't do it ALL the time. There are at times common libraries that are used by both YE and other programs and if those libraries require updates - then they will require compiles of those other programs. That may not be ideal, and may cause you to have to expand your testing - but its not something that is just introduced willy nilly. We do our best to not do that whenever we can.

Third, delivering database changes within Year End are against policy - UNLESS - those database changes are required by the actual regulatory requirement being implemented in Year End. So again, this is attempted to be minimized as much as possible because we know the customer impact.

I have talked to both Development teams this morning. From the AP side, there are no AP dbreorgs required, but there are database changes in Lease Management due to a new regulatory requirement starting Jan 1, 2019. This is for ASU842 and a factsheet has been published on Xtreme for those customers who are using this functionality. On the PR side, there are no database changes as part of the PR YE delivery, so no dbreorg is stemming from that delivery.

Another factor that needs to be considered here is that some of you are ST Cloud or Managed Services S3 v10 customers. In discussing this thread with Development, it appears that ST Cloud Customers are being updated with more than just the YE Deliverables. The ST Cloud team is also applying a series of additional regulatory updates that have come out over the last year if they are not already applied. So the patching impact extends beyond Year End specifically - and at least one of those updates has associated database changes requiring dbreorgs to be run. I personally do not know the scope of what is included in their more full maintenance activity, but any ST cloud customer with concerns around this can reach out to their CSM/SDM for more information here. I am only noting this here because you may be associating this extra work with the traditional YE updates, when they really aren't.

Hopefully that helps better explain the differing impact to customers here.

unknown

Just to set the record straight, we have not installed the ACA changes yet - our situation pertains strictly to PR.

unknown

plancor - that is exactly what we got

hmueller19 - I already entered an incident last week

unknown

Margie - exactly! We have a similar list and would not expect to see all of those non-YE/non-PR programs affected.

Darla Hengel

A note from Infor Development:

Programs are made up of different objects of code including, but not limited to, screen, reports and libraries. Libraries are generally pieces of code that can be shared between many programs. For example, there are many programs that create and edit time records, including PR35, PR36 and PR530. All of these programs utilize the PRTRDPD library to perform their functions. If a change is made to PRTRDPD, then all the programs that use it must be recompiled to allow the changes to take effect.

When viewing the contents of a CTP or patch package, including those for Payroll or Benefits ACA, the delivered version of any object must also include all previous versions. For example, this year’s year end patch package includes PR251PD version 60, which means it also has versions 1 through 59. If, for example PR251PD version 54 required a certain version of a database file or library to compile, those other objects must also be included for every CTP or package that has version 60.

An explanation for the additional programs that need to be recompiled is as follows. Included in this year’s year end package was a change made to the PR299PD object, bringing in version 1.1.69.1.6.1.14.1.42, so the previous version 1….41 is also included. Version 1….41 of PR299PD requires that version 7 of IFSVALPD library be pulled in. This library is used across many programs which is why many non-year end programs are being listed as needing to be compiled.

If you are being required to perform a database reorg, there is a version of a database table’s .tbl file included in the installation that is more recent than what is currently installed on your system.

plancor

Your response and description are appreciated. Thank you for taking the time to post. Your description is, I think, what most of us are familiar with regarding application patches in general. What seems to be new this year is the impact caused by the year end patches. In past years, year end patches have been limited as far as impact on the rest of the applications. Somehow this limitation was achievable in prior years.

Darla Hengel

Penny -

While we understand the frustration that additional programs needing to be recompiled, or a dbreorg needing to be done causes, there were no changes in the delivery method of the Year-end patch this year compared to last year. Development strives every year to limit the impact of Year-end programs as much as possible, however, due to what is being updated, some years are more successful in minimizing the impact than others.

unknown

Does anyone have a checklist or script they follow for testing the YE CTP? We don't have a formal testing for the YE CTP but I would like to create a document and would appreciate seeing or knowing what others do. Thank you!

sriman-shivakoti

We run through the programs that compiled to make sure they didn't break. WE also look out for what is to be different on W-2s or 1095s.

unknown

I've installed the initial 2018 YE CTP for payroll and read that I should be searching for any additional CTPs that may become available via JT number and not KB number because KB numbers tend to change. Since I seem to be suffering from a case of 'male blindness' , not sure if is acute or terminal , can someone tell me the JT number associated with KB 2028599? tia

0712131256598360.doc

Darla Hengel

KB #2028599 is an informational article, not a JT.

This KB will provide you with information of any upcoming JTs/CTPs related to Year End. So any bugs, new Federal/State updates, etc. You should sign up for KB #2028599 and you will receive an email when the article is updated so that you are aware when new Year-end info is released.

Copyright © 2025 Infor. All rights reserved.