My Oracle Support Banner

E1: 44H: P44H601 Bid Contract Preferred Subcontractor Functionality is not Working When Running R44H700 - Lot Start Workfile Generation (Doc ID 2490501.1)

Last updated on MARCH 25, 2019

Applies to:

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

Symptoms

Bid Contract Preferred Subcontractor functionality is not working.  

When a Bid Contract header has box/field Preferred Subcontractor checked, no Supplier Assignment record should be required.  The Bid should create Lot Start Workfile records when running R44H700.  

When the Preferred Subcontractor flag is set it indicates this as a preferred Subcontractor and there is no need to derive a supplier from the Supplier Assignment (F44H604) table.  When the system locates a preferred subcontractor's bid during the Lot Start process, the search is finished.  If two preferred subcontractors exist for the same cost code, the system selects the first preferred subcontractors that are found.

Currently, for a Bid Contract to pull into the Lot Start Workfile (F44H711), the Bid Contract Preferred Subcontractor box must be unchecked and a valid Supplier Assignment (F44H604) record must exists for the related Bill Item/Trade Code value that is associated to the account(s) used on the Bid Contract.

EXPECTED BEHAVIOR
-----------------------
In order to assign a Subcontractor to a trade, the following must happen: either the Bid Header record for that subcontractor is marked as Preferred Subcontractor or the Subcontractor must be assigned to the trade code associated to the Cost Code on the Bid Detail through Supplier Assignment. The Preferred Subcontractor Flag should override Supplier Assignment if they are in disagreement. Currently, having the Preferred Subcontractor flagged on a Bid Header record is preventing the Bid Detail lines from being pulled into the Lot Start Workfile record during the Lot Start Workfile Generation. Because of this, the Preferred Subcontractor functionality can not be used at all. This is happening for both Base House and Option Bids.


These scenarios have been tested and produce the following results:

Test 1:  Preferred Subcontractor Flagged + No Supplier Assignment = No Lot Start Workfile Records Created
Test 2:  Preferred Subcontractor Flagged + Expired Supplier Assignment = No Lot Start Workfile Records Created
Test 3:  Preferred Subcontractor Flagged + Valid Supplier Assignment = No Lot Start Workfile Records Created
Test 4:  Preferred Subcontractor Not Flagged + Valid Supplier Assignment = Lot Start Workfile Records Successfully Created.
Test 5:  Preferred Subcontractor Not Flagged + Expired Supplier Assignment = Lot Start Workfile Records Successfully Created

Of these 5 tests, only Test 4 produces the correct results.

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.