My Oracle Support Banner

E1: 44H: Incorrect Option Reference when Creating Lump Sum Bid for Option Master Records with Wildcards (+) (Doc ID 2672409.1)

Last updated on JUNE 29, 2021

Applies to:

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

Symptoms

The Option Reference value of a new Bid Contract where the detail line contains an Option is pulled from the Option Description 1 field of the Option as seen in Option Master P44H501. 

In a situation where multiple plans use the same option number, but each of the Option Master records specific to the "Plan" have a different Option Description 1 value, the correct description pulls into the Bid Contract.  But it does not pull in correctly when the P44H601 - Enter Bids F44H401 also contains a Community & Plan specific Option record where Phase & Elevation are set with a wildcards (+). Find Best Match For Option function N44H0032 called by Lump Sum Bids does not find the correct valid Option Description 1 when processing through the + wildcards.

For example, Two plans use the same Option Number with different Option Description 1.

1st record has wildcard values for Community/Phase/Elevation and Plan is specific with plan number 2250.  Description is TEST OPT 1.
2nd record has wildcard values for Phase/Elevation.  Community is specific and Plan is specific with plan number 2515.  Description is TEST OPT 2.

When Bid Contracts are created for the 1st and 2nd records above, the Bid Contract Reference field is populated with the Option Description 1 value traced back to the Option Master specific to the Plan number.  So in our example, Plan 2250 has description TEST OPT 1 and that is what is seen in the Bid Contract Reference field. Plan 2515 has description TEST OPT 2 and that is what is seen in the Bid Contract Reference field.

Now the 2nd record is changes so it has wildcard values for Phase/Elevation only with a specific community and specific Plan 2250.  In the prior example, the plan was 2515.

Now the 2 Option Master records are set as follows:

1st record has wildcard values for Community/Phase/Elevation.  Plan has a specific Plan number 2250. 
2nd record has wildcard values for Phase/Elevation.  Community and Plan have specific Community/Plan numbers.  Plan on this record is the same value as the Plan on the 1st record, 2250.  Description is TEST OPT 1.

Now a 3rd record is added which has wildcard values for Phase/Elevation and Community is specific and Plan is specific with plan number 2515.  Description is TEST OPT 2. .  Community and Plan have specific Community/Plan numbers that differ from the 1st & 2nd records.  Description Test Opt 2 only exists on this record for this specific Community/Plan , (11020000 / 2515).

Now when adding a Bid Contract for community 11020000 but with plan 2250 (no community 11020000 specific Option record set for Plan 2250), the Reference is incorrectly populated with TEST OPT 2 which is only found on the Option record for community 11020000, Plan 2515. 

The N44H0032 should evaluate all variables for an “exact” match and then use wildcard of +.  It should first look for an exact match, then search for a best match based on Area, Community, Phase, Plan, Elevation using the + wildcards.  Expecting the Reference (description) to be from the Option Description of the Plan specific option.   So in this example, the Plan on the BC is 2250.  For any TESTOPT Option records set up in P44H401 with Plan 2250, the Description is Test Opt 1 and it is this description that we are expecting to default into the BC Reference field.

Changes

Find "Best Match" Option N44H0032
 

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.