ACA Patch and Testing

I'm so appreciative of the large discussion on patch testing and set-up, but I don't recall seeing comments on loading new backups into your Test or DEV environments. I'm nearly done with my initial testing, but I want a current database backup loaded to test the new payroll close procedures in my DEV environment.

My DBA is concerned about this, thinking he might need to back out the patches then load the database and re-install the patches. Has anyone else done this? And if so, are there procedures somewhere that I've missed?

Help, as always, is greatly appreciated!

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

unknown

Your DBA is correct - we just found this out the hard way!

[Updated on 11/6/2015 8:42 AM]

unknown

He is correct. Once you have applied a CTP that includes database changes you can't copy data from a product line that hasn't been updated yet.

marty

Ok thank you. I'm glad I checked. This group is so valuable!

unknown

Good practice is to update your test/dev product line data before applying the CTP.

todd-brown

If it is just one CTP that has a dbreorg included, what we have done in the past is, apply the data refresh, then copy the old dbdict to the current dbdict, run blddbdict/dbreorg. This will reapply the db changes. Then rerun the patchcompile from the CTP, to get the timestamps back in sync.

0911060553270289.pdf

unknown

If I have a set of patches being tested and need current data I uninstall the patches that include db changes, refresh the data and re-install the patches.

0911060553270289.pdf

marty

@BarbRich, yes we do update our product line data, but since I've been testing for a while, the data is old now. I am doing a second round and want fresh time records to work with.

@Todd Brown - thank you. I will forward all of the responses to him and let him decide our best course. We may just refresh TEST and apply the patches there (they are not currently in TEST).

unknown

Our ACA reporting requirements are being handled by a third party this year however we still want to apply the CTP's to get our code current and see what impact it has on our system. We always apply in our test productline first, but will need to apply in production at some point. Since we will not really be "using" the ACA updates, I'm not sure how much testing our HR team will be doing. Is there any harm in applying in production? I assume we will get these anyway in the next MSP like it or not.

[Updated on 11/6/2015 9:08 AM]

sriman-shivakoti

You will get it in the next release or you could get it if you get a CTP that "touches" one of the forms.

Our practice is to test all forms we use that are compiled in a CTP. You certainly don't want any surprises when following existing processes.

The ACA does affect BN32, BN32, BN100 series, BN531 etc.

unknown

Has anyone else been getting strange error messages on their BN100 since the ACA patch? I've been getting error messages that we've never received before and for plans other than the medical plan.

sriman-shivakoti

What error messages are you receiving? Have you applied the latest CTPs? Our BN100 was broken by the initial patch.

unknown

We have been getting "Employee not eligible to enroll until mm/dd/yyyy", which we weren't getting prior to the patch. I checked the plans and the plans are correct, so I'm not sure why we are getting that message now.

We applied one of the CTPs, but I believe we have the most recent still in Test.

Copyright © 2025 Infor. All rights reserved.