E1:07: Enable Date Effective Timecard Rate Assign Incorrect Account number (Doc ID 2262364.1)

Last updated on MAY 04, 2017

Applies to:

JD Edwards EnterpriseOne US Payroll - Version 9.1 and later
Information in this document applies to any platform.

Symptoms

System: E1 9.1 release
actual behavior: When the Enable Date Effective Timecard Rates is turn on in the P05001S-HRM foundation system option and the employee have correct historical data in the F08042, system does not appeared to be reading the effective date in the F08042 to the CO, MCU and ANI on the auto generated timecards. For example, a salary employee was under company 00001. The F08042 showed the HMCO field for company 00001 and HMCU 1 with the effective on as 01/01/17. Then on 04/19/17, employee changed HMCO-company to 00007 with HMCU-home business unit of 7FC. The F08042 showed the HMCO field for company 00007 and home business unit-HMCU of 7FC with the effective on as 04/19/17. When timecards are entered manually via P051121 using work date of 04/18/17 and 04/24/17, system assigned correct HCMO, CO, HMCU, and ANI (account number) to both timecards base on the effective date in the F08042. Timecard with date 04/18/17 contained account number 1.8115 and timecard date 04/24/17 contained account number 7FC.8115.  However, using the same employee but let the system automatically generated the timecards due to employee being salary, the CO, MCU and ANI-account number come in incorrectly for timecard date 04/18/17.  System assigned the same account number for both timecards, which is wrong.  Timecard with 04/18/17 date should have the account number that belong to company 1 and home business unit 1, in this case 1.8115 but it is currently assign with 7FC.8115.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms