Thank you Oracle Support for being there in the same boat as I am. You sometimes get treated the same way as airline gate and checkin employees do. But there is a reason why you don’t get to speak to the people that are actually responsible for your troubles. We want to keep you out of jail…..
The question is directed towards Oracle Development. When? When? WHEN!?
Release the PIM rollup patch and get organized for 12.1.3! Free my patch.
Fusion apps are fun and it is great to work on the new products but all of us who are actually still implementing R12.1 applications need you to fix the bugs in this version please?
I am too small a firm to participate in all the “inside” alpha and beta testing. I am not allowed to play in any reindeer games. So I am not privy to the secret release information. I get my information from just asking questions. Thanks for providing the facts to me Oracle Support!
If Oracle Sales knew how hard it was to acquire the organized list of patches to ensure the first half of the implementation is not an embarrassment of bugs, then maybe they could help us get these patches in order?
Thank God it is not major issues in the first place.
We need R12.1.3 fixed and organized and we need to know what to tell our clients regarding R12.2 release.
I don’t think I am allowed to tell you the patch number for this latest fix for PIMDH R12.PLM_PF.C 12.1.3 but get ready. As soon as I have a released patch, I will let you know.
I am probably going to recommend this rollup patch for all off the shelf 12.1.3 PIM instances. There are a lot of disorganised one-off patches for 12.1.3 that need consolidated.
You can’t easily attain the exact list of one off patches from the patch query in metalink. I have opened SRs to obtain a list because I want to be proactive. But it takes weeks and development is not cooperative in their response to the desires of both support and client. I know they are not doing it intentionally but clients are not as patient as consultants and support analysts. We need answers NOW!
Clients: Don’t delay and don’t let fear get in the way. When this mysterious rollup patch gets released and you are in 12.1.3, you should set a high priority to patching your instances with it. Bad design led to your inability to add this patch. Let’s nip it in the bud right here and right now.
It is worth the time money and effort to find out why you cannot add this rollup patch to your instances. hmmmm?
In the meantime, there are over 30 patches for 12.1.3 PIM data hub that you will need to patch up. Some or most of these will be included in the rollup patch C. But some of these patches actually fix problems that you might have skipped or worked around through your implementation.
A few problem areas that I experienced over the last six months come to mind:
2 ) Publishing functionality
3) Product Workbench
Question in the back row: Hey Bob, How do I know what I have already?
Answer: Simple, run the query that Oracle support provides you in a metalink note that is necessary to let you know. The output is as simple as:
Current PIM Patch Level: R12.PLM_PF.B (6658960)
Product Installation: R12.EGO.C.3: Installed
If you were experienced PIM implementors, the latest R12.1.3 rollup sql query return is stated in bold above.
Bad patches cost us all a lot of time and money. Bugs in software cost us alot more time and money. Please keep the patches up to date and encourage Oracle Development to fix the issues (minor as they may seem) in Oracle PIM Data Hub.
Otherwise, stop reading for now and get to work helping me get this patch released to us.
Have a great day,
- Shared vs Full HR Install in the PIM Data Hub instance (mckinleyalexandra.wordpress.com)