Bid Evaluation

Module code: bid_evaluation, a menu entry with no folder of its own. It opens the RFQ module with type=bid, and rfq.php then titles the page "Bid Evaluation" and shows the bid screens instead of the RFQ header.

How this page was verified

Written from master on 2026-09-06 and compared with the big five the same day. The whole entry is a branch inside rfq.php, rfq_handler_form.php and rfq_handler_post.php.

How the entry works

• db/seeds/DefaultTsModules.php seeds a bid_evaluation row in ts_modules, so it has its own cid, its own privileges and its own place in the menu.
• _menu.php maps that code to the rfq folder and appends &type=bid to the link.
• rfq.php reads $_GET['type']; on bid it assigns title_page, swaps the toolbar for the bid tabs and hides the RFQ-only buttons. The form handler checks $_GET['modproc_type'] == 'bid' in the same way.

There is no modules/bid_evaluation/ directory. Grep for type_bid, "bid" and modproc_type when you work on it.

What the screens do

The bidder list, the per-vendor bid rows, the tabulation and the approval of the evaluation. The data is in ts_rfq_bid, ts_rfq_bidder_invited and the bid_* columns of ts_rfq. Submitting the evaluation posts the second procurement routing of the RFQ; bid.class.php generates the evaluation document and files it under Procurement Documents. All of this is described on the RFQ page.

Privileges

Because bid_evaluation is its own module row, a user can see RFQs and not Bid Evaluation, or the reverse. When a user reports "I cannot see the bid tab", check the privileges of both module codes in Users and Privileges.

Instance differences

Same as the RFQ: installed on master and JOTRE, not installed in the QA databases of Jadestone, Medco and Timas.

Related

• RFQ: the module this entry opens.
• Purchase Order: what an approved bid becomes.