Hi

A number of issues are being reported by consultants elsewhere while testing family pack K. Please can you guys contribute with any issues you face on this front .
(See below)

>>>>>>>>>>>>>>>>>>>
After we upgraded and users Viewed Output on this report it was not legible. We noticed this report had XML in the format type in Concurrent Program registration. There were other reports also. I changed the type back to Text and users can now view them. There was
no mention of this in the readme for the Family Pack K.

Other reports that were in XML format.

Gross To Net Summary
Element Link Details Report
Cost Breakdown Report for Costing Run
Cost Breakdown Report for Date Range
Audit Report
Advance Pay Listing
Employee Assignments Without Payrolls
Employee Assignments Not Processed
Payroll Actions Not Processed

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
(Post Family Pack K)

Since Family Pack K we now have PDF format for payroll related reports (eg : Payroll Message Report). This report was normally printed by selecting print options. Now our Payroll department must view output and use tools copy to print the report.

>>>>>>>>>>>>>>>>>>>>>

We've had a few issues with many of the customisations here at ***.
I'll badger one of the funky contractors to add some content of value, and i'll trawl our problem-report list for FP-K specific issues.

Vin
Can you elaborate...
Are you saying that these reports are now comming out in XML format since Pack K went in?
If so, is this not something to do with the move to XMLPublisher???

Things we've spotted are standard API's having new and changed parameters which are knocking out some of our API hooks etc.

Baz

I have simply consolidated these problems from various other lists for the benefit of members on this list. I suppose sites experiencing these problems have raised TARs with Oracle and likely to update with replies shortly.

Another one :

>>>>>>>>>>>>>>>>>>>>>

Has anyone else seen an error when attempting to modify the status of a person from married to divorced etc? Getting error: FRM 40735 up-date trigger raised unhandled exception ORA -29861.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>

Oracle has provided a patch for a known issue with the HRGLOBAL.

Patch =>4556903.
Bug =>4556903: PERFORMANCE ISSUE: APPLYING HRGLOBAL.DRV AFTER HRMS FP.K

After applying HR_PF.K, API(HR_ASSIGNMENT_API.UPDATE_EMP_ASG_CRITERIA)
does not populate people_group_id in per_all_assignments_f
even though the combination exists in the pay_people_groups.

Patch
=====
Patch 4633742
Description UPDATE_EMP_ASG_CRITERIA DOESN'T POPULATE PEOPLE_GROUP_ID

Folks,

I attended the HR SIG yesterday and an interesting item was brought to light by the representative from Devon CC, in an implementation presentation. Apparently, Family Pack K has installed a major issue with Absence.
I understand, for future compatibility, Oracle have added a constraint which effectively blocks duplicate absences. This is particular issue for DCC, as they run multiple assignments, and record absence at assignment level and not employee level. A colleague continued the conversation which elaborated on this and it appears that this applies to ALL ABSENCES and not just Sickness. Given the response from Oracle, I don’t believe that they will be doing anything to rectify this. Listening around I also understand that a few other Family Pack K installations have been stalled by this.

It may be worth a look while testing !!

If I get any further info I’ll update the stream.

Brian

It's only overlapping sicknesses that are the problem, not overlapping absences. I'm at DCC.

Reduce Data Volumes and Improve Performance by Producing Fewer Run Result Values (New feature)

Oracle Payroll has enhanced the payroll run to eliminate unwanted run result values. The payroll run no longer saves null run results, that is, those run results that do not contain a value. This change improves the performance of the payroll run and reduces the space needed for the run results.

Do not implement this feature if you have written your own reports that depend on null result values. Oracle Payroll does not suppress null run results unless your System Administrator has enabled this feature by:

Checking that the Generic Upgrade Mechanism contains an upgrade called Enable Sparse Matrix Null Run Result Values Functionality

Running the Enable Sparse Matrix Null Run Result Values Functionality upgrade

Has anyone come across a problem with the SOE on Family Pack K. We are testing the new Void Payments from Electronic Transfer File (BACS) and the SOE no longer displays the payment method nor the payroll messages. Let me know, otherwise I'll raise a TAR.

Cheers,

Del

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

Thanks Simon.

We ran the bulk compile. That's how we found the problem. I have since raised a TAR with Oracle and it looks as if we have an old version of a function. They have supplied a patch that we are in the process of applying. I'll post our findings here.

We have had the 'value exceeded allowable range' message pre FP K also but a particular formula that was ok pre FP K now gives the error, so I am assuming the maximum character length has reduced. (Uh!)

Cheers,

Del

Del
Could you post the patch number?

Cheers
Baz

We have a minor problem in that when we first enter our 11.5.10 FP K env we need to do anything in core forms first before switching resp and doing any functions in Manager Self-service, otherwise we get the old "System Error, contact your System Administrator" message.

Does anyone have a fix for this please?

Thanks, Sandra

Baz,

The Court Order patch number is 4395503

Just found another little gem with FP K. New fields have been introduced on the User Defined Table Structure form. In the columns button there is a new field 'User Column Key'. When you apply FP K this is populated with the column name. "So what?" you might say, "Am I bovvered?" You will be if the column name is more than 30 characters cos that's the limit of the User Column Key and you get a forms truncation error. You might also get corrupt characters appearing as well. These will be different every time you query the form. I also tried to create a new table structure and when I entered a column name more than 30 characters it truncated the User Column Key, saved the record and I could no longer query back the column. I have TAR'd it and will keep you posted.

Well, it's a known bug. Oracle advise to apply patch 4685013 to resolve the problem.

Cheers,

Del

Not sure if this is another FP.K. special, but very recently I have had occasion to run the 'delete element entry' api. Well after much faffing about with setting profile options (HR:Purge Element Entry Permission= All) and thereafter doing the apps_initialise thing to pick up said profile option value, the api duly does the business.

However, an interesting side effect is, it doesn't seem too fussed about the presence of run results any more. In fact it left 20 of the poor little blighters orphaned, all alone in the world without their parent element entries to keep them warm and safe from harm. I am not in a position to try this out on a non-FP.K. instance, so if anyone else out there could try it, I'd be very interested to know the outcome...

Strangely the system does not need the element entry to support the run results. This has been the case for many a year (as I can testify having loaded pay history into the results and result values tables without the originating entries - all you need is an element link).

However should the need arise to run a retropay, these results will get negated because of the missing original element entry.

Another problem doing the rounds.
Slow performance of code that uses the function pay_balance_pkg.get_value

APPLY PATCH 4745996 which fixes pay_balance_pkg to run faster.
------------------------------
Bug 4745996: Performance of pay_balance_pkg.get_value on a balance.
Functional Description:
The CBO elected a sub-optimum plan for a particular statement used within pay_balance_pkg.get_value. CBO hints have been added to the statement to assist the CBO is slecting the optimum plan.

Technical Description:
The CBO elected a sub-optimum plan for a particular statement used within pay_balance_pkg.get_value. CBO hints have been added to the statement to assist the CBO is selecting the optimum plan.

A ha! That would explain several things....
Cheers for this Vinoo...Put another beer on the tab

And another one...

Hit this one on friday however don't have access to a non-FP.K environment anymore to compare.

Extra Element Info DFF "Historic Rate - Element Attribution" now has a whole load more mandatory attributes.
Now, either these are completely new attributes, added in FP.K, or they were already existing and have now been made mandatory.

Items in question are:
"Term Time Factor" - EEI_INFORMATION12
"Sum Multiple Entries" - EEI_INFORMATION13
"Lookup Input Values" - EEI_INFORMATION14

Either way, no default values are populated into any rows that were existing prior to FP.K.
Which means that the moment you (or your users) touch the record it throws a wobbly and insists on these values being populated.

This is more of a CU2 side effect related patch but a couple of sites have reported missing responsibilities after CU2 upgrade

Patch 4719658

ONE OFF PATCH FOR MISSING RESPONSIBILITIES

This one-off contains the following fixes:

Bug4507634: FND_USER_RESP_GROUPS_API.SYNC_ROLES_ONE_RESP_SECGRP DOES NOT
PASS OVERWRITE MODE
Bug4699363: FND_USER_RESP_GROUPS_API.SYNC_ROLES_ONE_RESP_SECGRP DOES NOT
PASS OVERWRITE MODE
Bug4722061: WFDS 4.6 ROLLUP FOR FND.H

This also contains the "Sync responsibility role data into the WF table"
Concurrent Program which will execute after the patch has been applied
and the Concurrent Managers are running.

Has anyone enabled the functionality in FP K to reduce data volumes and improve performance by producing fewer run result values. i.e. the payroll run no longer saves null run results. Apparently you have to enable this feature by running the 'Enable Sparse Matrix Null Run Result Values Functionality' upgrade.

Anyone know how to set this up?

Cheers,

Del

Just found out that this functionality is only enabled for the US. It's not available in the UK. (Marvellous!!)

Del - look upwards:

From October:

"Reduce Data Volumes and Improve Performance by Producing Fewer Run Result Values (New feature)

Oracle Payroll has enhanced the payroll run to eliminate unwanted run result values. The payroll run no longer saves null run results, that is, those run results that do not contain a value. This change improves the performance of the payroll run and reduces the space needed for the run results.

Do not implement this feature if you have written your own reports that depend on null result values. Oracle Payroll does not suppress null run results unless your System Administrator has enabled this feature by:

Checking that the Generic Upgrade Mechanism contains an upgrade called Enable Sparse Matrix Null Run Result Values Functionality

Running the Enable Sparse Matrix Null Run Result Values Functionality upgrade
"

Yikes - the self service Appraisal function is now obsolete!

I really do not want to have to go through and re-Personalise/customise that one. Has anyone found a way round this?

Geoff,

I no understand? October 2005?

Del