Oracle E-Business Suite Blog

I am pleased to announce that I have worked through most of the Payroll issues that I encountered in my first pass of testing.  The fact that the data was scrambled had no impact on my testing afterall.  What happened early on is that some of my testing failed with the following error message: 
APP-FND-00314: Invalid printer ( noprint ) and print style ( USLWPORTRAIT) combination. 

The failure of these tests impacts the rest of testing as they are sequential.  I found the following solution in Metalink:  

Solution

To implement the solution, please execute below steps:

1. Copy the INLOC_P.prt from $JA_TOP/IN60105D2 directory to $FND_TOP/reports directory.

2. Navigate to "Install -> Printer -> Register" under system administrator responsibility and query for all printers installed at your site.

3. For each printer installed, check the type and click on "Printer Types"button and query for all printer types.

4. Add a new record under printer drivers with "INLOC_BACS" as style and "INLOC_AT_EFT" as driver name and save the record.

5.Bounce the Concurrent Manager after this step for the changes to take effect.

However, for testing purposes (I did not need to print) I did the following:

 

 

You may find that you will need to follow these steps a few times in the process of testing.  I am now able to run the tests and continue with the next steps.

*************************** 

I have one outstanding issue for Payroll remaining.  It is when I run the GRE Total Reports program.  I am getting the following error: 

MSG-00001: tmp002:
REP-1401: 'cf_1formula': Fatal PL/SQL error occurred.
ORA-01422: exact fetch returns more than requested number of rows

REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error:
REP-1401: MSG-00001: tmp002:
REP-1401: 'cf_1formula': Fatal PL/SQL error occurred.
ORA-01422: exact fetch returns more than requested number of rows

 I found the following information on Metalink:

Subject:	Error Running GRE Totals Report REP-1401 and ORA-1422
	Doc ID:	152461.1	Type:	PROBLEM
	Modified Date:	23-MAY-2009	Status:	PUBLISHED

  
fact: Oracle Payroll 11.5.3 
fact: PAYUSTOT - GRE Totals Report 
symptom: GRE Totals Report fails 
symptom: ERR REP-1401: 'cf_1formula': Fatal PL/SQL error occurred 
symptom: ORA-01422 : Exact fetch returns more than the requested number of  rows 
symptom: GRE Totals report completes successfully for other GREs 
change: NOTE ROLE:  Troubleshooting Step:  Here is the formula function for CF_1Formula: function CF_1Formula return VARCHAR2 is begin   declare  l_sui_ein    varchar2(20); begin  select  sein.org_information3 into    l_sui_ein from    hr_organization_information   sein where   sein.organization_id                   = :gre_id and     sein.org_information1  = :state and     sein.org_information_context           = 'State Tax Rules';  A simple select, the ORA-1422 indicates the system found two rows that met this  criteria. 
cause: A duplicate state tax rule was entered in the GRE State Tax Rules  set up.  
  fix:  Delete the duplicate State Tax record  US HRMS Manager (or similar responsibility) --> Work Structures -->  Organization --> Description - Find the organization defined as your GRE   Arrow down to the Organization Classification = GRE/Legal Entity --> OTHERS   Select State Tax Rules from the list   Inspect the rows returned for a duplicate state code (first two characters)   Delete the duplicate row using the red "X" from the toolbar 

 

I followed the instructions and found the duplicate state tax rule.  I removed one and reran the program with success.  This closes out all my payroll issues.  None of the issues I encountered seem to be a result of the upgrade.

Comment (0)

I have completed my first pass of payroll testing.  I am disappointed to say that I found a larger number of issues than I had hoped for.  However, it is very possible and likely that the issues I encountered are due to the fact that this testing instance consists of scrambled data.  I am currently researching possible causes.

Comment (0)

During testing of core HR earlier I found that I was not able to terminate an employee.  I was able to duplicate the issue when using other test employees that same day.  I have since retested and was successful with terminating an employee.  It appears to have been intermittent as I did not place any requests to correct the "issue" making this a non-issue.

Comment (0)

During my testing of core HR I found that I was not able to terminate an employee in the core forms.  I am in the process of following up with this.  Everything else with HR has passed with flying colors! 

Comment (1)

Just a quick review of the 12.1.1 release notes on Core HR. Some exciting things come with the upgrade to 12.1! Looks like there is an option to deeplink where single sign on (SSO) will come in handy. This will benefit employees and other end users as it could possibly provide a one-stop shopping experience.

However, I did read that the HR Helpdesk offered with 12.1 is currently only available for the US and UK legislations. I am hoping that a global HR Helpdesk is on the roadmap. This will be a great benefit to those companies who have centralized helpdesks that support all legislations.

One change for Payroll regarding an employee's assignment costing details and workflow.  To migrage historical data a concurrent program has been provided.

In Payroll India a legislative solution for labor welfare fund deductions has een added.  Also, medical and other leave claims can now be submitted and approved through Oracle.

 

Comment (0)