E1: 44H: Preferred Supplier Bid Contract Selection Does Not Validate Lot Commitment Start Date Against Bid Effective Date Range When Processing the R44H700 Lot Start Workfile Generation
(Doc ID 2821735.1)
Last updated on JULY 14, 2022
Applies to:
JD Edwards EnterpriseOne Homebuilder - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
Existing Bid Contract records are evaluated during R44H700 Lot Start Workfile Generation processing to determine which bids should be included in the Lot being processed.
This validation includes checking the Bid Contact values for a match against the Bid Hierarchy below:
Level | Community/Area | Phase | Plan | Elevation |
1 | Community | Phase | Plan | Elevation |
2 | Community | Phase | Plan | [+] |
3 | Community | Phase | [+] | [+} |
4 | Community | [+] | Plan | Elevation |
5 | Community | [+] | Plan | [+] |
6 | Community | [+] | [+] | [+] |
7 | Area | [+] | Plan | Elevation |
8 | Area | [+] | Plan | [+] |
9 | Area | [+] | [+] | [+] |
[+] represents the wildcard value
This validation is being performed successfully, however it does not validate the Bid Contract effective date range against the Commitment Start Date (COMJ) for the Lot being processed. The Bid Contract should only be valid when the COMJ falls in between the Bid Effective Date and the Bid Cancel Date. Currently no validation of these dates is performed. As a result, incorrect/invalid bids are being pulled into the Lot Start Workfile.
Changes
This is occurring in the 9.2.5 (update 5) release.
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 |