Charlotte Oracle Applications user Group

If you have a clean up script or a cron job or appworx -
you might consider adding the removal of the files below.

We used something called ud2490 ( just for my own reference)

find .  -mtime +1 -name "*.rti" -exec rm "{}" ";" 

Run time information (RTI)  files are  automatically generated and  cleaned
up when the  user logs in/out of our financials forms sessions.  They are
created by the f60webmx program.  In some cases when  the user logs out of
the forms sessions abruptly we get the orphaned  rti files.  We should
manually clean these up but only when they are not activie. 

 --------------

find . -mtime +1 -name "FNDCPGSC*.txt" -exec rm "{ }"
";" 

The FNDCPGSC*.txt   files are created by the oracle workflow manager
process.  We did not have any issues with these files being created before
we started doing XML payroll.  I believe there is a configuration problem
and we should find out what the problem is and I will continue to look for
a solution.   However, as a interim fix  -- oracle says  we should delete
these files at this time (service request number  7677613.993 ). 

visit this website to learn more about what files to delete and who and what is generating them and
what their file extension mean:

http://onlineappsdba.com/index.php/2008/01/12/log-files-in-applcsfappllog-directory/

Recently I learned about a two utilities to modify the context file on you machines - We mostly just us VI to modify these files — which can really get you into trouble unless you make a backup copy before hand.  The first Tool is adbldxml.pl

$ORACLE_HOME/appsutil/template/adxdbctx.tmp). This is illustrated in the figure above.

The second utility is used from within  the applications (inside  Oracle applicatios manager) OAM.  To navigate to this — I used the sysadmin responsibility that has the OAM tab or when you first login to the apps you can navigate or login to OAM. — Once there I immediately go to the site map — with the administration tab selected -system configuration section -autoconfig (a few seconds) click on the edit - parameters pencil for the tier you want to modify - then I go to the tab - labeled  environments - then  I choose the last option oa_environements.applsys  — here you can modify any of the parameters you want or need to modify — Once you save these changes — the templates — that autoconfig uses will be udpated — so that the next time you run autoconfig the changes will take effect inside your context file (*.xml). 

Hope this helps.

Greg

This is the page/note that you need to know about:

Oracle North American Payroll - 11.5.x Mandatory Patches  :Note:111499.1

Below is the login for metalink — Be sure to check out the new interface.  As the CSI/Metalink administrator for my company I was forced to familiarize myself with the new interface.  Three weeks later I can say that I do like it.  However, sometimes long tars/SR don’t show up as they should.

https://metalink.oracle.com/CSP/ui/signin_en.html?language=en

6699770 HRMS Family Pack K Rollup (RUP) 3

 This Release Update Pack is mandatory for Year End 2008

The About Document is located on Metalink. Note:  604051.1

Before you apply any HRMS R11i &12 Release Update Pack, always review the Oracle HRMS Product Family - Release 11i & 12 Information Metalink note 135266.1. This note will have the most up to date information for the HRMS product family.

Note: This Release Update Pack includes an HRGLOBAL. Please remember HRGLOBAL is a progressive patch. It is important to review MetaLink to ensure you’ve got the most recent HRGLOBAL. For information on HRGlobal, refer to Metalink Note: 145837.1

 
 
7395025 Q3 2008 Statutory and JIT Update   7244442
Q2 2008 Statutory and JIT Update  US Sep 30, 2008 The functional readme is available on MetaLink.

US Q3 2008 - Note: 728521.1

PreRequisite: AMERICAS YEAR END 2007 STATUTORY UPDATE - III (patch 6400000).

Note: HRMS Family Pack K Rollup 3 (6699770) is NOT a pre-requisite for the Q3 2008 Incremental Statutory Update if applying it outside of the End of Year Phase 1.

Applying Q3 2008 patch 7395025 is not required if applying US EOY Phase 1 patch.

Please review the patch readme for complete instructions.
 
7259999
 2008 Year End Phase I
 
 

 
 US, CA
 Sep 30 , 2008
 Pre-requisites: HRMS Family Pack K Rollup3 (6699770)
EOY Phase 1 contains infrastructure changes for US and Canada Year End 2008 processing.

The functional readmes for Year End Phase 1 are available on MetaLink.

CA EOY Phase 1 - Note: 737173.1
US EOY Phase 1 - Note: 737177.1

The Q3 2008 Incremental Statutory Update was released as a separate patch and is also included in the End of Year (EOY) Phase 1. (Note: Applying Q3 2008 patch 7395025 is not required if applying US EOY Phase 1 patch.)

Note: HRMS Family Pack K Rollup 3 (6699770) is NOT a pre-requisite for the Q3 2008 Incremental Statutory Update if applying it outside of the End of Year Phase 1.

This patch contains version 2.9.4 of Vertex Payroll Tax Q Series (Quantum) Libraries. Upgrading to Quantum 2.9.4 is mandatory for US and Canada Payroll customers.
 
7461741 DELIVER PAYROLL TAX Q SERIES (QUANTUM) VERSION 2.9.4   US Oct 10, 2008  After applying End of Year 2008 Phase 1 (patch 7259999) and upgrading to Quantum 2.9.4, customers running Oracle Payroll on the Windows operating platform are reporting the following error when running a quickpay:

HR_6882_HRPROC_ASSERT
LOCATION py3vntsetup:1a*
APP-PAY-06882: Assertion failure detected at location py3vntsetup:1a.

Cause: an internal error has occurred at location py3vntsetup:1a.
Action: please contact your Oracle customer representative.

*Note: LOCATION could also be ‘py3vntsetup:1b’.

This issue was reported in bug 7458425 - AFTER PATCH 7259999, QUICKPAY COMPLETES WITH ERROR LIBRARY ERROR: 126. This bug has been fixed and is now available as a one off patch (7461741).

Note: The above patch is mandatory for any R11i customer running Oracle Payroll on the Windows platform who is applying YE 2008 Phase 1.

This patch can be applied before or after applying YE 2008 Phase 1.