My Oracle Support Banner

E1: 07: Timecard Correction Batch Type 51 (Pro-Forma Daily Timecard Journals) Incorrectly Posts Through to R053953 (Burden) And R053952 (Employee History) (Doc ID 3048800.1)

Last updated on DECEMBER 10, 2024

Applies to:

JD Edwards EnterpriseOne Time and Labor - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

With timecard correction if the Payroll Journal Proof/Edit Report (R05229) creates a proforma batch 51 F0011 and Journal Entry Proforma F063951 that are in error there no option to fix the issue.
If the user goes forward with changing the batch status in P0011 to approved and posting the batch, the post R09801 will fail but the account error is carried into history in F0618 and F0724.

Steps:
1. Time Entry by EE Transaction History (fastpath to P051191|W051191E), find employee with history, row exit Timecard Correction which calls Reclassify/Correct Historical Timecards (P05602). Enter the correction account.
2. Run Generate Timecard Corrections R05602 in Proof and then Final.
3. Run Generate Timecard Entries (R052901) and Payroll Journal Proof/Edit Report (R05229) creates the proforma batch 51 F0011 and Journal Entry Proforma F063951. Review the R05229 and note Error: Account Number xxxx.xxx is Invalid.
4. Batches P0011 change the batch status from E to A. Row exit Post by Batch.
Sequence of execution:
- the R09801 ZJDE0027 calls the R053951
- the R053951 calls financial function B0900049 which inserts the F0911
- the R053951 calls the R053952 and R053953 which inserts to F0618 and F0724 with an invalid account.
- the R09801 then finishes and tries to post the F0911 but fails with invalid account.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.