E1: 44H: Can R44H700 - Lot Start Worlfile Generation Use Business Function Get Next Order Number (B4302960) to Retrieve the Next Available Next Number?
(Doc ID 2868988.1)
Last updated on OCTOBER 14, 2022
Applies to:JD Edwards EnterpriseOne Homebuilder - Version 9.2 and later
Information in this document applies to any platform.
The P44H601 - Bid Entry is used to create a Bid Contract, typically with document type = BC.
When the Bid Contracts are added to the Lot Start Workfile (LSWF) by running the R44H700 - Lot Start Worlfile Generation, the system assigns a second document type/number as defined in the P44H001 - Lot Start Documents Revisions.
When the R44H700 is submitted and a Bid Contract (BC doc type) is pulled into the LSWF, a second OS document type will be assigned to this record based on the P44H001 settings shown below.
Currently the R44H700 uses X0010GetNextNumber to retrieve the Next Number that is assigned to the OS document type. This business function does not check to see if the Next Number value has already been used in the database.
After LSWF records are created for the BC/OS Bid Contract, a next step in the process is to create commitments for these LSWF records in the F4301/F4311 purchasing tables. This is done by running the R44H7113 - Commitment Generation UBE. This UBE is what creates the F4301 & F4311 records.
Homebuilder Commitment Generation R44H7113 uses Get Next Order Number (B4302960) to retrieve the next available Next Number (NN) which checks for existing F4301 records and finds the next available unused NN rather than reusing a number that is already used by previously created F4301/F4311 records. For Takeoff contracts that were previously added to the LSWF as a TO document type with no number yet assigned, (which is standard processing), when the R44H7113 creates the commitment (F4301/F4311) records it also assigns the Next Number value to these Takeoff records using Get Next Order Number (B4302960) which first checks if the next number has already been used. If it exists in the database, it will be skipped and the next sequential number will be used, if it has not already been used. With this validation, the TO document number assigned will be unique and will not already exist in the F4301/F4311.
For Bid Contracts, the secondary document type and document number have already been assigned during processing of the R44H700 using X0010GetNextNumber so the R44H7113 does not assign or otherwise change the existing BC/OS document numbers. This can result in the incorrect update/change of these existing F4301 records while adding new records to the existing F4311 records for this specific document number.
If the R44H700 would use BSFN B4302960 to retrieve the Next Number, numbers that already exist in the database will be skipped and a previously unused Next Number value will be assigned.
This enhancement is requesting that the R44H700 be changed/enhanced to use business function Get Next Order Number (B4302960) to retrieve the next number for the OS document type.
Further testing of the R44H700 as it relates to reuse of OS document Next Numbers has shown how the update of these existing F4301/F4311 records results in data corruption. Due to this data corruption a new bug has been created to address this situation and implement the suggested change requested in Enh 34161931.
Bug 34476452 - R44H700 ASSIGNS OS NEXT NUMBER THAT ALREADY EXISTS IN THE F4301/F4311 CORRUPTING F4301 DATA has been created requesting that Enh 34161931 be implemented and/or the next number business function be changed from the current X0010GetNextNumber to Get Next Order Number (B4302960) to avoid this data corruption.
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