E1: 05T: Historical Timecard Correction R05602 Does Not Give Error with Inactive Burden Account (Doc ID 2936507.1)

Last updated on DECEMBER 10, 2024

Applies to:

Symptoms

Generate Timecard Corrections, R05602, does not verify if the associated burden account has a blank posting edit code to allow posting to the general ledger.

Steps:
1. Set up AAI (auto accounting instructions), P069042, for journal type BF (burden fringe) to default to object account (example) 8125.
2. Set up in Employee Entry, P0801, an example employee with home company 00050 and business unit 50.  Add a medical benefit to the employee's DBA Instructions, P050181.  Run the employee through payroll, P07210, and note the $$ medical benefit to the existing burden fringe account 50.8125 during payroll journal entries, P07220.
3. Process Final Update, R07250, to create actual Journal Entries.  Post journals with G/L Post R09801.
4. In Account P0901, set the burden fringe account to inactive (I) for Posting Edit code.
5. Launch Time Entry by EE Transaction History, (P051191 | W051191E), find employee, row exit to Timecard Correction. Set Date Worked in Timecard Dates tab and find.
Choose Reclassify (form exit) and enter a different business unit and account for the Labor Account Number.
6. Run through Generate Timecard Corrections, R05602, in proof mode. Note no failure was given for the burden account that is inactive.

Changes

Cause

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