<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0"><id>tag:blogger.com,1999:blog-5750484</id><updated>2012-02-16T12:41:36.854+01:00</updated><category term="CWB" /><category term="apex" /><category term="AME" /><category term="2.0" /><category term="gross net payroll oracle" /><category term="Documentool" /><title type="text">Implementing Oracle Hrms : my daily adventures</title><subtitle type="html">Popay, Oracle Payroll, Apex and Documentool.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://oraclehrms.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://oraclehrms.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default?start-index=26&amp;max-results=25" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>130</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/popay" /><feedburner:info uri="popay" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry><id>tag:blogger.com,1999:blog-5750484.post-6315597639513415256</id><published>2012-01-15T18:05:00.001+01:00</published><updated>2012-01-15T18:05:32.834+01:00</updated><title type="text">Making Quickpay faster</title><summary type="html">For years we know that quickpay is not the fastest payroll process, and we pointed to the wait time of the concurrent manager.

But we had a closer look, and saw that even an empty Quickpay took always at least 5 seconds, excluding the time doing nothing in a concurrent queue.

A sql trace file was generated at concurrent program level.


OVERALL TOTALS FOR ALL NON-RECURSIVE STATEMENTScall     &lt;img src="http://feeds.feedburner.com/~r/popay/~4/EkgwkYlxF3M" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/6315597639513415256" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/6315597639513415256" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/EkgwkYlxF3M/making-quickpay-faster.html" title="Making Quickpay faster" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2012/01/making-quickpay-faster.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-4302655146284093189</id><published>2011-09-08T13:51:00.001+02:00</published><updated>2011-09-08T13:51:29.614+02:00</updated><title type="text">Some challenges</title><summary type="html">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.&lt;img src="http://feeds.feedburner.com/~r/popay/~4/3F8GCXjNuzg" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/4302655146284093189" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/4302655146284093189" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/3F8GCXjNuzg/some-challenges.html" title="Some challenges" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2011/09/some-challenges.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-7579034228115498401</id><published>2011-05-18T20:17:00.002+02:00</published><updated>2011-05-18T20:23:34.262+02:00</updated><title type="text">eBS 12.2 : summer sleep</title><summary type="html">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.&lt;img src="http://feeds.feedburner.com/~r/popay/~4/Y9IVgKcvNk4" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/7579034228115498401" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/7579034228115498401" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/Y9IVgKcvNk4/ebs-122-summer-sleep.html" title="eBS 12.2 : summer sleep" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2011/05/ebs-122-summer-sleep.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-4057529760942383214</id><published>2011-04-24T10:27:00.003+02:00</published><updated>2011-04-24T10:35:43.070+02:00</updated><title type="text">Fusion HCM</title><summary type="html">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.&lt;img src="http://feeds.feedburner.com/~r/popay/~4/JIRgMvXEUrA" height="1" width="1"/&gt;</summary><link rel="related" href="http://www.oracle.com/us/products/applications/fusion/hcm/index.html" title="Fusion HCM" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/4057529760942383214" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/4057529760942383214" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/JIRgMvXEUrA/fusion-hcm.html" title="Fusion HCM" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2011/04/fusion-hcm.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-3967366151635439955</id><published>2011-04-22T10:46:00.004+02:00</published><updated>2011-04-22T10:59:08.885+02:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="apex" /><title type="text">mission accomplished : apex on apps</title><summary type="html">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 &lt;img src="http://feeds.feedburner.com/~r/popay/~4/drd7jdvkPjM" height="1" width="1"/&gt;</summary><link rel="related" href="http://dpeake.blogspot.com/2011/03/oracle-e-business-suite-and-apex-white.html" title="mission accomplished : apex on apps" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/3967366151635439955" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/3967366151635439955" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/drd7jdvkPjM/mission-accomplished-apex-on-apps.html" title="mission accomplished : apex on apps" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2011/04/mission-accomplished-apex-on-apps.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-1886757657793218501</id><published>2011-02-18T14:29:00.002+01:00</published><updated>2011-02-18T14:42:33.470+01:00</updated><title type="text">Upgrade stories : Web Adi again</title><summary type="html">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 &lt;img src="http://feeds.feedburner.com/~r/popay/~4/GeoCAzgxIvI" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/1886757657793218501" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/1886757657793218501" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/GeoCAzgxIvI/upgrade-stories-web-adi-again.html" title="Upgrade stories : Web Adi again" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2011/02/upgrade-stories-web-adi-again.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-5240241045396314034</id><published>2011-02-18T14:22:00.002+01:00</published><updated>2011-02-18T14:28:14.002+01:00</updated><title type="text">Upgrade stories : Apex integration</title><summary type="html">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 &lt;img src="http://feeds.feedburner.com/~r/popay/~4/AdZQzsPRBjo" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/5240241045396314034" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/5240241045396314034" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/AdZQzsPRBjo/upgrade-stories-apex-integration.html" title="Upgrade stories : Apex integration" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2011/02/upgrade-stories-apex-integration.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-6840411301956961578</id><published>2011-02-10T08:38:00.002+01:00</published><updated>2011-02-10T08:44:53.101+01:00</updated><title type="text">No electricity, but the application is up</title><summary type="html">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 ...&lt;img src="http://feeds.feedburner.com/~r/popay/~4/t6KwowqsgGU" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/6840411301956961578" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/6840411301956961578" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/t6KwowqsgGU/no-electricity-but-application-is-up.html" title="No electricity, but the application is up" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2011/02/no-electricity-but-application-is-up.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-5490401642773439271</id><published>2010-12-20T19:33:00.002+01:00</published><updated>2010-12-20T19:39:58.556+01:00</updated><title type="text">Payroll 13th month</title><summary type="html">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&lt;img src="http://feeds.feedburner.com/~r/popay/~4/Io8FWzYGLsA" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/5490401642773439271" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/5490401642773439271" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/Io8FWzYGLsA/payroll-13th-month.html" title="Payroll 13th month" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2010/12/payroll-13th-month.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-3383265706929732324</id><published>2010-10-29T13:12:00.002+02:00</published><updated>2010-10-29T13:16:27.343+02:00</updated><title type="text">Upgrade stories : Bursting</title><summary type="html">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".&lt;img src="http://feeds.feedburner.com/~r/popay/~4/MkVLWsKTZ7s" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/3383265706929732324" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/3383265706929732324" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/MkVLWsKTZ7s/upgrade-stories-bursting.html" title="Upgrade stories : Bursting" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2010/10/upgrade-stories-bursting.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-6811090346285975704</id><published>2010-09-12T09:46:00.002+02:00</published><updated>2010-09-12T09:53:32.805+02:00</updated><title type="text">Upgrade stories : Web Adi error</title><summary type="html">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&lt;img src="http://feeds.feedburner.com/~r/popay/~4/G83R_3KfOQ8" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/6811090346285975704" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/6811090346285975704" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/G83R_3KfOQ8/upgrade-stories-web-adi-error.html" title="Upgrade stories : Web Adi error" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2010/09/upgrade-stories-web-adi-error.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-5359881829998749118</id><published>2010-09-12T09:33:00.003+02:00</published><updated>2010-09-12T09:45:27.477+02:00</updated><title type="text">Upgrade stories : 12.1.2 or 12.1.3</title><summary type="html">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) - &lt;img src="http://feeds.feedburner.com/~r/popay/~4/ra3pEz95QiA" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/5359881829998749118" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/5359881829998749118" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/ra3pEz95QiA/upgrade-stories-1212-or-1213_12.html" title="Upgrade stories : 12.1.2 or 12.1.3" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2010/09/upgrade-stories-1212-or-1213_12.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-4089066013075408619</id><published>2010-09-12T09:17:00.003+02:00</published><updated>2010-09-12T09:32:30.164+02:00</updated><title type="text">Upgrade stories : Extended support for 11.5.10</title><summary type="html">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 onYou can avoid the extra money, if- you &lt;img src="http://feeds.feedburner.com/~r/popay/~4/B3FGjy7JCw8" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/4089066013075408619" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/4089066013075408619" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/B3FGjy7JCw8/upgrade-stories-1212-or-1213.html" title="Upgrade stories : Extended support for 11.5.10" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2010/09/upgrade-stories-1212-or-1213.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-1010939229184037439</id><published>2010-07-17T10:14:00.002+02:00</published><updated>2010-07-17T10:23:55.214+02:00</updated><title type="text">Retropay by Employee</title><summary type="html">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 &lt;img src="http://feeds.feedburner.com/~r/popay/~4/QzY7WyTNyn8" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/1010939229184037439" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/1010939229184037439" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/QzY7WyTNyn8/retropay-by-employee.html" title="Retropay by Employee" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2010/07/retropay-by-employee.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-2091310422461988070</id><published>2010-06-18T12:37:00.002+02:00</published><updated>2010-06-18T12:42:31.468+02:00</updated><title type="text">Apex 4.0</title><summary type="html">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 &lt;img src="http://feeds.feedburner.com/~r/popay/~4/4kRGj7o5Grs" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/2091310422461988070" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/2091310422461988070" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/4kRGj7o5Grs/apex-40.html" title="Apex 4.0" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2010/06/apex-40.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-2400562340094081654</id><published>2010-05-01T10:14:00.004+02:00</published><updated>2010-05-01T10:28:02.025+02:00</updated><title type="text">Apex on R12 - patch 7377023</title><summary type="html">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-&lt;img src="http://feeds.feedburner.com/~r/popay/~4/JKW9Ch8yGnU" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/2400562340094081654" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/2400562340094081654" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/JKW9Ch8yGnU/apex-on-r12-patch-7377023.html" title="Apex on R12 - patch 7377023" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2010/05/apex-on-r12-patch-7377023.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-4872166740379922130</id><published>2010-04-06T18:51:00.002+02:00</published><updated>2010-04-06T18:55:24.155+02:00</updated><title type="text">Fusion on the iPad?</title><summary type="html">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.&lt;img src="http://feeds.feedburner.com/~r/popay/~4/VNnKWl0KMC8" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/4872166740379922130" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/4872166740379922130" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/VNnKWl0KMC8/fusion-on-ipad.html" title="Fusion on the iPad?" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2010/04/fusion-on-ipad.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-9078677472227154874</id><published>2010-03-01T10:07:00.002+01:00</published><updated>2010-03-01T10:13:51.680+01:00</updated><title type="text">Apex 4.0 Release date</title><summary type="html">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 ...&lt;img src="http://feeds.feedburner.com/~r/popay/~4/ajiNCgJyfAQ" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/9078677472227154874" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/9078677472227154874" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/ajiNCgJyfAQ/apex-40-release-date.html" title="Apex 4.0 Release date" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2010/03/apex-40-release-date.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-5711284708348543776</id><published>2010-01-23T14:01:00.002+01:00</published><updated>2010-01-23T14:03:59.669+01:00</updated><title type="text">Busy busy busy</title><summary type="html">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.&lt;img src="http://feeds.feedburner.com/~r/popay/~4/IKQsXxGmatw" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/5711284708348543776" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/5711284708348543776" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/IKQsXxGmatw/busy-busy-busy.html" title="Busy busy busy" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2010/01/busy-busy-busy.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-3700182113769301069</id><published>2009-07-06T21:52:00.002+02:00</published><updated>2009-07-06T21:57:19.947+02:00</updated><title type="text">NL Daily tax tables</title><summary type="html">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 &lt;img src="http://feeds.feedburner.com/~r/popay/~4/EqRQHdFdBUw" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/3700182113769301069" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/3700182113769301069" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/EqRQHdFdBUw/nl-daily-tax-tables.html" title="NL Daily tax tables" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2009/07/nl-daily-tax-tables.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-2841129414388851925</id><published>2009-04-08T15:16:00.002+02:00</published><updated>2009-04-08T15:25:54.363+02:00</updated><title type="text">Apps - Apex on R12</title><summary type="html">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 &lt;img src="http://feeds.feedburner.com/~r/popay/~4/HNNigNoHHU0" height="1" width="1"/&gt;</summary><link rel="related" href="https://sites.google.com/a/popay.be/apex-on-apps/" title="Apps - Apex on R12" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/2841129414388851925" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/2841129414388851925" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/HNNigNoHHU0/apps-apex-on-r12.html" title="Apps - Apex on R12" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2009/04/apps-apex-on-r12.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-5300651763366925538</id><published>2009-02-14T14:39:00.002+01:00</published><updated>2009-02-14T14:49:44.010+01:00</updated><title type="text">Exit 2.0 &amp; SOA</title><summary type="html">The cloud is now the buzzword. SOA and Web 2.0 are losing popularity.I tried also to translate Web 2.0 concepts into HR processes, but no luck. It looked good on the powerpoint, but not on the workfloor. Oracle Fusion development started within the SOA and 2.0 hype period. Curious how marketing will convert that into the buzzword popular at the time Fusion will pop up.Good things is that &lt;img src="http://feeds.feedburner.com/~r/popay/~4/Xk2xcWBS5aU" height="1" width="1"/&gt;</summary><link rel="related" href="http://www.techcrunch.com/2009/02/14/the-death-of-web-20/" title="Exit 2.0 &amp; SOA" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/5300651763366925538" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/5300651763366925538" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/Xk2xcWBS5aU/exit-20-soa.html" title="Exit 2.0 &amp; SOA" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2009/02/exit-20-soa.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-6645427494309078837</id><published>2009-01-27T18:25:00.002+01:00</published><updated>2009-01-27T18:30:24.154+01:00</updated><title type="text">One more customer on R12</title><summary type="html">One of our HR customers in the Netherlands upgraded to R12 last weekend. It was mainly a technical DBA exercise. Operating system became linux, the database became a full 10 and the upgrade scripts pumped the eBusiness Suite up to the 12.0.6 level.&lt;img src="http://feeds.feedburner.com/~r/popay/~4/e0rVBtPGbv8" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/6645427494309078837" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/6645427494309078837" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/e0rVBtPGbv8/one-more-customer-on-r12.html" title="One more customer on R12" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2009/01/one-more-customer-on-r12.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-6572295138013693135</id><published>2009-01-24T20:43:00.003+01:00</published><updated>2009-01-24T20:50:28.177+01:00</updated><title type="text">Release 12.1: Oracle Payroll for India</title><summary type="html">I never saw a functional business driver to migrate towards the 12 Release. R12.1 should overcome that. I hope. I hoped. For payroll, only some stuff for our India colleagues is present.For some more details in the other HR modules, check the RCD doc.&lt;img src="http://feeds.feedburner.com/~r/popay/~4/tjn_m_Ne6xY" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/6572295138013693135" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/6572295138013693135" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/tjn_m_Ne6xY/release-121-oracle-payroll-for-india.html" title="Release 12.1: Oracle Payroll for India" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2009/01/release-121-oracle-payroll-for-india.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-5750484.post-1709440530927680231</id><published>2008-11-22T10:53:00.002+01:00</published><updated>2008-11-22T11:03:50.012+01:00</updated><title type="text">back to basics</title><summary type="html">We wanted to extend the Dutch localization so that the mandatory assignment extra info fields where defaulted automatically when entering a new employee.First step was to cook up some plsql, based on api's, that creates the assignment extra infos. Easy.Now we only need to fire that code when they create a new employee.So a user hook would be nice, but since the assignment screen is still not &lt;img src="http://feeds.feedburner.com/~r/popay/~4/wri-e2lExdg" height="1" width="1"/&gt;</summary><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/1709440530927680231" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5750484/posts/default/1709440530927680231" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/popay/~3/wri-e2lExdg/back-to-basics.html" title="back to basics" /><author><name>thierry</name><uri>http://www.blogger.com/profile/11767682220351777439</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://oraclehrms.blogspot.com/2008/11/back-to-basics.html</feedburner:origLink></entry></feed>

