Some challenges

Designing a payroll system for a few million employees. Mapping cash management reconciliation, costing of payments, continuous calculations and voiding of payments on the core process.

eBS 12.2 : summer sleep

We went throught the updated RCD docs today on metalink and very little has been added for HCM. Succession planning got some extra features.

For Payroll, they only announced that Enhanced Retropay will be the only supported flavor of Retropay. So when you upgrade to 12.2, and your localisation is not yet on Enhanced Retropay, you have to pay attention.

Fusion HCM

The radio silence of Oracle around Fusion is over. Last week a webcast explained the Next Generation of Hr software in the cloud.

If the Easter tea leaves are right, Fusion HCM will be available within a few weeks. Fusion Talent management will be Saas-ed by Oracle.

mission accomplished : apex on apps

Years ago we developed a solution to integrate Apex with Oracle's eBusiness suite.

It worked fine on 11i, and we came with a jsp solution for some of our initial R12 customers.

We had sometimes the "Apex is not supported by Oracle for the EBusiness Suite" discussion.

On the Apex site you can now read the "official" white paper how to integrate Apex on Apps. You should be on a recent 12.1.3, and it requires some patching.

The paper is introduced on David Peake's blog, Apex product manager.

I will blog how it works out, the next time we gonna use the official integrator.

Upgrade stories : Web Adi again

We had a nasty web ADI issue on a few of the upgraded instances. It worked before, it works on some other R12 instances, but we are not able to make it working again.

It throws all the time "Mail Merge Aborted due to error in creating the Mail Merge Data Source". Nothing in the log files.

Escalated the P2, but no reactions from support side. After some background fighting, a senior support analyst jumped in, and the next day it worked.

The $BNE_TOP/sql/BNENLINS.sql script fixed some NLS data issues in the custom integrator, et voila.

Upgrade stories : Apex integration

The security model in 12.1.3 is a little bit more picky, so we had to add a few more configuration steps to made the secured HR views working again. Without these 2 steps, the secured views returned 0 rows.

First, we registered the APEX_PUBLIC_USER in eBS via the regular Forms, and then a little update was needed to make it working.

update fnd_oracle_userid a
set a.read_only_flag = 'U'
where a.oracle_username = 'APEX_PUBLIC_USER';

No electricity, but the application is up

Dakar is having more troubles then normal with electricity. Never thought that the SaaS model would be that useful when the light goes out. And the extra battery in the office dies, and the router goes down. But you still can access the application over your smartphone and finish your payroll run.

And hope you can charge your phone's battery some time in the evening ...

Payroll 13th month

A monthly payroll has 12 periods, but a customer requested a 13th run, so that all corrections made over 2010 would still be processed in 2010.

By using the standard processes a little bit smarter, we achieved the goal.

Retropay was launched so that the differences were created in December again.

The Payroll ran again for December with an element set, that contained only retro element types. So only the differences found by Retropay were processed by the second December run.

And just a tweak of the (custom) payslip, so that only run results of that latest run were shown, completed the picture.

And the post-payroll processes pick up all results of both December runs.

Upgrade stories : Bursting

The parameters of the concurrent "XML Publisher Report Bursting Program" have changed between 11i and R12. Oracle added a new parameter, before the previously defined 2 parameters.

The new and hidden parameter is called "Dummy for Data Security", and is defaulted by "select xdo_cp_data_security_pkg.get_concurrent_request_ids from dual".

Upgrade stories : Web Adi error

Launching Web ADI from HR forms throws a http 404 error under Internet Explorer. Firefox shows a more meaningful "Resource /OA_HTML/oracle.apps.bne.webui.BneApplicationService not found on this server".

After some digging, it was found that the web html call of seeded and custom Web ADI forms functions had 'oracle.apps.bne.webui.' before 'BneApplicationService'.

It looks like the upgrade scripts do not clean that up correctly.

Upgrade stories : 12.1.2 or 12.1.3

So which version to choose from?

12.1.2 is out for a while, so a nice list of fixes exists already.

12.1.3 is new on the block from August 2010 on. Going for this version brings you to the latest and finest verion of the eBusiness Suite. And will fix some previous bugs. And will introduce some new bugs.

To make things a little more complicated, Metalink states:

"R12.HR_PF.B.Delta.3 (9114911) - Oracle HRMS RUP 3: This is the lowest level of HRMS Release Update Pack (RUP) on which Netherlands Payroll customers are supported for 2010/11 Year End processing and statutory updates effective from 01-Jan-2011."

And this Rup 3 is already included in the 12.1.3 version, but is an extra Rup to install on top of 12.1.2.

I gonna propose 12.1.3. Either way we will have issues to fix, so it seems better to fix them in the latest version. As such, the customer is one relaese point higher, and support can not ask you to upgrade to 12.1.3.

Upgrade stories : Extended support for 11.5.10

Plan is to blog some articles about ongoing R12 upgrades, within the HCM domain.

If you are on 11.5.10 right now :
- Premier support ends by November 2010
- you are forced into Extended support from December 2010 on
- Oracle does not bill extra money for the extended support for the first year
- So you pay extra money for Extended support from December 2011 on

You can avoid the extra money, if
- you talk to your account manager
- Oracle revises their extra money support policy, or extends the grace period
- you upgrade to R12 (which will cost you also money)

Count your options.

Retropay by Employee

I'm posting the last time a lot about Apex. While in reality I'm mainly busy with Oracle Payroll.

If your legislation uses advanced or enhanced retropay, there is the RetroNotifications process to run, to identify which employees have retrospective changes.

And in a next step, you run the RetroPay process. The enhanced version does not have any assignment set parameter anymore. In other words, the people selected by RetroNotifications will be processed by Retropay.

We have now a customer that wants to see the effect of changes in the past as soon as possible on a payslip.

So we engineered a RetroPay by Employee process, on top of the standard Retropay process. It forces an assignment into retropay, runs retropay for all assignments of an employee (yes, multi-assignments), and runs the payroll for all these assignments. All in one process.

It is now part of our Popay Payroll Toolkit.

Apex 4.0

Oracle will never confirm this, but I guess Apex 4.0 will see the light before the end of the worldcup.

This could be understood in between the lines of what was told at the OBUG Apex SIG day in Belgium yesterday.

The feature list looks impressive, and with all demonstrations seen yesterday, I have a way better understanding of the way forward.

But I'm still wondering how to use Websheets in an eBusiness suite context.

And by the way: how to integrate Apex with a version control system is still an open question for me.

Apex on R12 - patch 7377023

This patch brings back the good old SSWA plsql menu functions on R12. And in more recent versions of R12, they are part of the base install.

That does not mean that the eBS team supports mod_plsql. No. But it gives more possibilities to integrate Apex on Apps.

Again:
- Oracle supports Apex
- Oracle supports mod plsql
- Oracle does not support customizations
- Oracle eBS does not support customizations
- Oracle eBS does not support mod plsql anymore
- Oracle eBS does not support Apex applications

So bottomline: Apex on Apps in R12 is supported within Oracle, but not by the eBS team.

The readme of the patch says :

Mod_plsql technology is supported by Oracle Server Technologies Support teams.
Oracle E-Business Suite Support and Development is unable to provide
instructions or diagnostic assistance on any issues that arise from custom
development using mod_plsql.

Fusion on the iPad?

Too many posts these days about the iPad, so one more will not make the difference.

The last (and only) demo I saw from Fusion looked a lot like Flash. But there is not a lot of love lost between Apple and Flash. Meaning that Oracle has still to release their next gen platform, but will not be able to use the next gen client device.

Apex 4.0 Release date

Patrick Wolf shows again a good reason why we should look forward for the 4.0 release of Apex. Cascading LOVs for dummies.

But one little phrase makes me think that the 4.0 production release is not yet for tomorrow. "(Note: Popup LOV and List Manager will be added as well in the final product)". So not yet code complete ...

Busy busy busy

3 customers are live this month with payroll in the Netherlands. So i hope you understand that there was not that much time to maintain this blog.

So 14000 people more receive an Oracle payslip this month.

The errors we correct next month with Retropay.

NL Daily tax tables

Two NL Payroll customers ask in the same week if one can activate the NL daily taxation tables. Coincidence.

While i answered the first time NO, except when an employee is hired or fired in the middle of the month, the second time i dived a little deeper in the seeded fast formulas and plsql functions, to discover a hidden fast formula to configure.

Define the fast formula NL_OVERRIDE_SOCIAL_INSURANCE_DAYS with the business logic required, and you have full control over the proration (daily tax) happening.

Apps - Apex on R12

We just got the Apps-Apex integration working on R12.

Yes you need a separate Apache server, but the rest is almost the same. Nothing has to be changed within the Apex application, you still set the VPD call to initialize the apps session.

Only the menu function to launch Apex from is changed from a plsql based one, into a jsp menu function. So yes, an extra jsp page needs to be compiled on the Apps j2ee server.