T2.16
Matching
Which lots answer an enquiry line, how well, and why.
A match needs an enquiry line to match against. The MVP workbook carried no enquiries, so rfq and rfq_line hold no rows and remnant_match, which points at one, holds none either. The stock and the catalog behind a match are both there: the floor and every specification read the database on the other boards.
Enquiry lines
askingrows
rfq_line: a match is scored against one of these, and the workbook carried none
Enquiries
askingrows
rfq: the Business Events sheet named no enquiry, and the import refused to invent one
Matches scored
askingrows
remnant_match: lot, score, explanation, anchor price, decision
Items on the floor
askingrows
the stock a match would be scored over is there; only the line to score it against is missing
Specifications
askingrows
the catalog a match resolves through is there too
Candidate lots
LotSpecificationWeightAgeScoreWhyDecision
No remnant_match rows. Scoring the floor against a line nobody asked for would be an invented enquiry, and the import refused to write one.
What the database does hold
rfq rowsasking
rfq_line rowsasking
remnant_match rowsasking
item rowsasking
The enquiry line
what was asked for
Nothing to show yet
rfq_line holds no rows; there is no line on screen to match against.
Evidence
why this lot answers the line
Nothing to show yet
remnant_match.explanation holds no rows.
Anchor price
Nothing to show yet
remnant_match.anchor_price_per_kg holds no rows. What a specification actually sold for is on the Pricing board, which reads the database.
Decision
accepted, rejected, ignored
Nothing to show yet
remnant_match.decision holds no rows, and MATCH_DECIDED (F3.9) has never been written to the ledger.
Substitutions offered
Nothing to show yet
substitution_rule holds no rows: no alloy has been declared a substitute for another in this tenant.