Here at *** we have a test environment with 11.5.10 and FP-K, including the 11.5.10 cummulative update pack 2.

We have an issue with PERWSSPP failing compilation due to missing column reference: STARTING_STEP.

We have TAR'ed it, but think there may be a missing step or script from the CU2 update.
I'd appreciate it if anyone else has encountered the same issue.

Cheers
Barry

Hi Barry,

I can't help you with your query I'm afraid but I wondered if you had any advice about when we should apply the upgrade? Are there any Payroll process dependencies for example or can it be done whenever our DBA feels like it?

Thanks for any help
Sandra

Hi Baz,

Guess what? I can't help you either but here down at the Down we are about to do an impact assessment on Family Pack K. If anyone has any insight or advice would they care to share it here.

Cheers,

Del

Hi Del,

I've done the painful task of scraping out of the RCD and "About" docs just the Core and UK bits and stuck them in a spreadsheet so that it's easy to track the impact for your client. I'll email them to you separately.

See you, Sandra

Hi Sandra

Here is some info I collected for my family pack K upgrade
I am still in the process of applying it but have hit problems with ATG and Framework (This could be unrelated to K). However will rant about it later.........

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Courtesy : "Nick DiGiorgio"

There are six "gotchas" that I ran into while applying HRMS Family Pack K.

1. Unlock the CTXSYS account and set the password to the shipped
default value or ICXINBLS.sql will fail (reverse this when done for security):

> sqlplus SYSTEM/<password>
ALTER USER CTXSYS ACCOUNT UNLOCK;

Check that can log in as ctxsys/<password>, if not
> sqlplus SYSTEM/<password>
ALTER USER CTXSYS IDENTIFIED BY <DEFAULT_PASSWORD_FOR CTXSYS>;

2. If you have a multi-node environment with Forms/Web on a separate
server, then adpatch will fail with about 3382 jobs remaining on the
backend server on jobs GHR_SF50_REPORT.PDF and GHR_SF52_REPORT.PDF.

This is a known bug (Bug 4484284). The fix is:
On the backend server (patch does fine on Forms/Web server),
> mkdir $APPL_TOP/ghr/11.5.0/html
> chmod 775 $APPL_TOP/ghr/11.5.0/html
> cp <main_patch_directory_path>/3500000/ghr/html/*
$APPL_TOP/ghr/11.5.0/html/

3. BUG 4484906 ORA-20107: HRRBDEIB INTERNAL PROC ERR%
PAY_PATCH_STATUS. This bug can occur if adpatch is run with more
workers than there are server processors. For example, for most
everything it works well to run 8 adworkers on a 4 processor box--but
for the hrglobal.drv shipped with HRMS Family Pack K adpatch should
be ran with only 4 workers. That is,
adworkers=processors. Sadly, when we hit this error the only way to
fix it was to drop the applsys.FND_INSTALL_PROCESSES table, delete
all rows from PAY_PATCH_STATUS for this failed HRGLOBAL.drv run, and
start the HRGLOBAL driver over from the beginning using just 4
threads for our 4 processor box.

4. We sort of did this one to ourselves. HRMS Family Pack K is
shipped with new seeded FastFormula functions. We had, for years, a
custom FastFormula function named GET_HOURLY_RATE. The patch brings a
new function with just the same name and blew up because it couldn't
insert a record for the seeded function. Oracle says to use a
distinct pre-fix naming convention for customizations so hopefully you have.

5. The Tech Stack Pre-req patch 11i.ATG_PF.H (Patch 3438354) fails
about 30 minutes after starting for us due to invalid JTF objects,
and I couldn't get passed them by restarting workers. The fix was to
compile the invalid JTF objects. From the $AD_TOP/sql directory I
used sqlplus apps/<appspassword> @adcompsc.sql apps apps JTF%.

6. There are an assortment of annoying little bugs (from Workflow to
Concurrent Processing toAutoConfig) in the mandatory Tech Stack
upgrade (11i.ATG_PF.H and related patches). However, we just applied
the new 11.5.10 CU2 for ATG, Patch 4125550, and it seems they're
fixed by this patch. The CU2 patch does require the new 11i.ADI.2
(4337683) patch.

Give the Apps DBA some time on this upgrade.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Cheers
Vin

Our original issue was due to a missing pre-req!

However, we've had no issues putting K onto an 11.5.10 instance. Infact the DBA's here said it was one of the smoothest FP's to put in in many a while!.

However, we are aware of some issues with CU2 which have delayed us putting it in. Some of the are Framework-related - there is a new version of JDeveloper with the framework components that needs to go hand-in-hand with CU2 as it has some backward compatibility issues with any earlier framework code. Note this is only applicable if you are developing with framework...

Hello Vin,

You are an absolute star! Your info meant nothing to me (was it actually in English) but I passed it onto my DBA friend and he was dead pleased.

See his response below. He also asks if you want any info from tecknicul something or other. Let me know and I'll act as go-between.

Thanks very much, see you Sandra

I'm not trying to compete with your top techie, but my feedback (if you or he are interested) to the 6 gotchas is:

(i) Reset of CTXSYS schema password to default (funnily enough CTXSYS!) should always be done as scripts always fail in this area!!

(ii) This is useful to know as we can make the changes in advance of our upgrade (we will be merging 11.5.10.2 with HRMS K so a big thanks to Vin for this one!

(iii) The day we can run 8 workers on our servers (aka Pizza boxes!) I will turn Buddhist! Seriously this does give us something to think about due to merge mentioned above. i.e. we will of course want to upgrade with as many workers as feasbile, which on Prod is 8-10 (num. of CPUs). I think we would therefore be ok on this one, but might get errors on test upgrades if we don't bear this in mind.

(iv) Customisations being blown away due to non-custom naming convention is a big boo-boo by their developers! Ours should all be (XYZ) or XX_ .... If not, then I'm out of here!!!

(v) The tech-stack pre-req patch is included in the 11.5.10.2 CU Maintenance pack, so it will be worth us just checking JTF invalids as a pre-req step.

(vi) We have AD.I.2 patch lined aup already as our 1st pre-req patch (we are on AD.I.1 at present),so we shouldn't hit this one either.

.... has your buddy actually performed the 11.5.10. Upgrade, or is he just doing HRMS K? If he is, does he want any info on technology stack validation issues under Apps and the RDBMS Oracle Home? I've found a couple of bugs in this area this week, so he is welcome to my findings in this area in return.

Does anyone know where the new (11.5.10 FamPack K) functionality for uploading Batche lines via a browser is? I've searched every likely place and can't find it.

Oracle call it "Transfer spreadsheet info directly to Batch Element Entry" in their About FamPack K document on Metalink.

Thanks, Sandra

Sandra,

Did you find the functionality for uploading Batch lines via a browser? If so can you update the thread, if not I've managed to get Web ADI to upload to Batch Element Entry (not pretty but it works). Contact me if you want my notes on how to do it.

Pat

Hello Pat,

Nice to hear from you, long time no chat!

No I haven't found it yet. Do you think Web ADI is the way that Oracle intend in the "About FPK" doc and they just omitted to explain it properly, or is it that you couldn't find it either and decided to be more resourceful?
Either way, yes I would like a copy of your notes please.

Thanks very much
Sandra