Del
I'd TAR it if i were you.
Just looking at some SOE's from my FP.K environment and they are happily displaying payroll messages and pay methods.

Baz,

What version of the form are you on. FP K delivers 11.5.53. Our pre 'K' environment is 11.5.47 and this is ok.

Cheers,

Del

11.5.53 is the one we're running here.

Sorry for the delayed reply...

Our DBA's are currently struggling to upgrade our first test env to 11.5.10 cu2 with FamPack K for HRMS and FamPack G for Fins.

Being a mere funky I don't understand the detail but they initially tried merging all the upgrade components to apply in one hit. This failed badly and wasted quite a lot of time. Oracle didn't advise against this, but with the benefit of our experience they have since said that the components should be applied separately.

Just in case anyone else is considering merging!

I think we did Pack K first, then threw on CU2, and then rolled in a few straggler patches.
It took them a couple of goes to get it right, but they're now getting quite good at it.
Its amazing how good these DBA's can get when they try!

My upgrade path is
11.5.10 -> CU2(11.5.10.2) -> Family Pack K

CU2 had just 1 problem . A ldt related to AZ schema failed but there is a fix from Oracle for this.

I decided to apply K later because a number of prereqs for K are included in CU2. Basically my base instance is 11.5.10 so the above path makes sense. Also it helps if the DBAs have experience with HR/Pay shops just not to get panicky if a lookup .ldt fails or a form that is rarely used fails to recompile.

But FP K has come up with a number of ldt errors related to BEN. Am fixing them one by one. Hope to complete FP K by the end of the week.

Thanks Barry and Vin,

I have obediently passed on your info to my DBA mate here and encouraged him to join up!

See you, Sandra

Another FP K Question. Has anyone come across a problem with the seeded formula COURT_ORDER not compiling due to a package error? If so, what was the resolution?

Cheers,

Del

And another one. Anyone noticed a reduction in the number of characters you can have in a fast formula message, and what that limit is. Some of our formulas now error with 'value exceeded allowable range'.

Hey Del,

Have you tried running the process 'Bulk Compile Formulas' to compile the court order formula? This should produce an output file which lists those that didn't compile- if it still doesn't, I'd have a look at the package and if it's invalid then try and compile that first..

I've had the 'value exceeded allowable range' message from trying to compile messages which were too long before, but pre family pack K. Seems odd that they have reduced the maximum allowable message size..

Cheers

Simon