My Oracle Support Banner

E1: 44H: P44H711 Lot Start Workfile Review Row Exit to Assign Supplier for TBD Takeoff Does Not Create the Expected 'Estimated' Takeoff (Doc ID 2816018.1)

Last updated on MARCH 10, 2022

Applies to:

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

Symptoms

After taking Update 5 which included Bug 31820739 - TBD TAKEOFF ASSIGNMENT OF SUPPLIER INCORRECTLY CREATES AN ESTIMATED TAKEOFF, you can no longer create an Estimated Takeoff after assigning a supplier for a TBD (To Be Determined) Takeoff as defined in Supplier Assignment P44H604.

When a Takeoff is defined as an Estimated Takeoff (Est. Takeoff Flag = 1) it should appear in the Lot Start Workfile (LSWF) in Green text and have a value of E in the Com P.S. column of the P44H711.  Currently when the Supplier Assignment records for the Takeoff also are defined with a TBD supplier, the LSWF record will pull into the LSWF in Blue text, which is correct.  After assignment of the supplier via row exit to Assign Supplier via P44H704 - Supplier on the Fly, the new record created in the LSWF is in black text as if it is a standard Takeoff.  But since the Takeoff Master record is defined as an Estimated Takeoff, the LSWF record after assigning the supplier should be in green text so the user knows the final quantity still needs to be adjusted/set.  Also, the Com P.S. field is set = blank as opposed to E for Estimated as expected.  These records need to be in Green text with Com P.S. = E to allow use of the row exit to revise the Takeoff and set the actual quantity for this detail line.

The steps required to duplicate this include:

1.  Use P44H602 - Takeoff Master to create a Takeoff set with a 1 in the Est. Takeoff Flag field.  This establishes this Takeoff as an Estimated Takeoff which will require update of the quantity later in the process.
2.  Use P44H603 - Material Item Pricing to add the associated pricing based on the trade code associated to the cost code on the Takeoff record.
3.  Use P44H604 - Supplier Assignment to add suppliers for this Takeoff.  Specifically, use a TBD Supplier such as 999999 with the Assignment Status field set = 2.  Also add 2 additional Suppliers with the Assignment Status field set = 1.  This establishes the Takeoff as a TBD Takeoff.
4.  Run the R44H700 Lot Start Workfile Generation UBE to pull this Takeoff into the LSWF - lot start workfile F44H711.
5.  The record in the LSWF should appear in Blue text with a T in the Com P.S. field to indicate the actual supplier must be selected using the row exit to assign supplier via P44H704 Supplier on the Fly.
6.  After assigning a supplier, a new record is added to the LSWF.  However, this record is displayed in Black text and Com P.S. = blank.  It should be Green text and have an E in the Com P.S. to indicate this is an estimated takeoff in need of an update to the quantity, again via row exit.
7.  Since this record is incorrectly created in Black text w/ a blank Com P.S. value, it is no longer an estimated takeoff and the quantity cannot be updated using the Revise Takeoff row exit.


After using P44H704 Supplier on the Fly to assign a supplier for a TBD Takeoff displayed in Blue text in P44H711 Lot Start Workfile Review, the added takeoff record for the actual supplier is created as a standard takeoff with black text and Com P.S. = blank, not an Estimated Takeoff as it is defined in the Takeoff Master P44H602.  This new record should have Com P.S. = E for Estimate and the record should be displayed in Green text .

Changes

These results first appeared after taking Update 5 which included Bug 31820739 - TBD TAKEOFF ASSIGNMENT OF SUPPLIER INCORRECTLY CREATES AN ESTIMATED TAKEOFF.

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.