E1: 44H: Budget Amount Associated to a TBD Takeoff is not Updated Following Assignment of TBD Supplier (Doc ID 2506345.1)

Last updated on APRIL 19, 2023

Applies to:

Symptoms

Selection of TBD Supplier Does Not Update/Revise Budget Amount

The Supplier TBD process for Takeoffs creates multiple records in the Lot Start Workfile, which inflates the Budget Amount for the involved Cost Codes on the Lot. When a Supplier is finally assigned and commitment generation is run, the budget amount in the JA remains the same, and is much larger than the amount that is now in the PA Ledger. This in turn overstates the HA ledger for the Lot and provides an inaccurate reading of what the total costs on the Lot will be.

In contrast to the TBD Takeoff process, the Supplier TBD process for Bid Contracts allows the creation of a Supplier TBD record using a Flag in the Bid Header creation form. When the Lot Start Workfile Generation is run, only the record for the Supplier TBD vendor is brought into the workfile. This causes an accurate creation of the JA budget for the job. When the row exit to the Assign Supplier is used, the full list of eligible suppliers is available to the user, one of which can then be selected. Only 1 black text record is created in the workfile for the selected Vendor, which then replaces the original Budget Amount in the JA. When Commitment Generation is run, the amount of the Bid is then entered into the PA ledger for the Cost Code. The resulting Job Status Inquiry shows a Budget Original Amount = Open Commitments = Estimate to Completion.

The budget is not updated correctly to reflect the new actual budget amounts after a supplier is selected in the TBD process.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.