My Oracle Support Banner

E1: 07: R05229 Is Showing An Invalid Account Error When Credit Liability P069045 Subsidiary Is Set Up With *UNION (Doc ID 1561254.1)

Last updated on AUGUST 20, 2021

Applies to:

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

Symptoms

The AAIs work for the Group Plan DBAs, but not for the DBA set up at the employee level.  DBA is setup to go to accoun xxx.xxxx.*UNION. This mean when the payroll journal entry is run, system should replaced the *UNION with the actual union code as the subsidiary.  However, in this case, it is not.  System appeared to not assign the subsidiary at all.

Step to duplicate:

1. Set up a DBA and flag the effect on G/L with N                                                                  

2. Attach the DBA to the employee DBA Instructions  

3. Set up an AAI  P069045-credit liability for the new DBA from step 1 above with *UNION in the subsidiary field                   

4. Add a timecard and confirm the Union code is populated                            

5. Run payroll, verify DBA from step 1 is calculated.                                                                      

6. Run the payroll journal entry step.  check the R05229 journal batch proof and notice the DBA from step 1 is sent to an invalid account because the subsidiary is not populate.  It should be the Union code.                                      

Changes

 

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
Changes
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.