My Oracle Support Banner

E1: 44H: R44H7113 Commitment Generation Fails with Error "Commitment G/L Account Invalid" on the R44H7113 when the G/L Date of the Record is in the Prior Calendar Year. No way to set the G/L Date to be Used. (Doc ID 2924243.1)

Last updated on MARCH 09, 2023

Applies to:

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


When the Lot Start Workfile records (LSWF) are created in one year (2022) and then the year rolls to the next year, (2023), when running the R44H7113 - Commitment Generation (in the new year 2023) to create commitments for these records the takeoffs are not committed due to the G/L Date being in the prior year.  The R44H7113 will not create the commitment and will generate error "Commitment G/L Account Invalid" on the R44H7113 pdf.  

To correct this and create commitments for these records, the users have to delete the workfile lines and regenerate them (via R44H700) so the workfile lines will then have a G/L date (year) that is in the same year as the current year when committing these records.  The R44H700 sets a new G/L Date on these records when re-added to the LSWF.

This deletion and re-generation of LSWF records causes a lot of rework.  This situation is common for TBD (To Be Determined) and Estimated Takeoffs, so this happens many times and wastes a great deal of time.  

The R44H7113 should have the functionality, via processing option or other means to allow the user to set the G/L Date for when this commitment will be posted.  Adding this ability would resolve this type of G/L Date issue. 

If there is a way to set the G/L Date for these commitment records when running R44H7113, that would resolve the issue. The R44H7113 (and/or related BFs) are validating the current/processing date against the G/L Date value on the LSWF records and or against the effective dates of the various apps such as Supplier Assignment & Material Item Pricing that are used to create the takeoffs so there is no way to avoid this issue when the related records cross calendar years.

The issue can be reproduced at will with the following steps:
1. Have LSWF F44H711 records for a prior year, G/L Date.
2. Attempt to run the R44H7113 over this data.
3. Any record in the LSWF that has a G/L Date that is not in the current year will not be committed and the R44H7113 will show error 'Commitment G/L Account Invalid'.
4. Only way to create commitments for these LSWF records is to delete them from the LSWF, add them back via R44H7113 using a current G/L Date and then you will be able to create the commitments since the G/L Date in LSWF matches the current year.


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

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