Files
wyndham-ARR/.project-docs/50-evidence/topics/2026-07-31-live-company-job-booking-room-diagnostic.md
2026-07-31 15:11:42 +08:00

35 lines
2.4 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Evidence Topic: Live 2131 company-job Booking Room diagnostic
- Date: 2026-07-31 14:5215:00 Asia/Shanghai
- Status: Resolved diagnostic; no code or data mutation
- Scope: Persisted company job `8aa1fdef3b644f3a9cc0f26924445a29` and its five published XLSX artifacts
- Confidence: Fact
- Stale trigger: New Booking source activation, Finance-version change, report regeneration, or a processor/rule change
## Facts
- The job succeeded for `2026-07`, period `21-month-end` / label `21-31`, with five successful company results.
- Artifact-tool inspection of the published workbooks found 598 populated `21-31` rows: 224 have a nonblank
`Booking Room` and 374 are blank. The per-company totals are LianTai 144/167, QBD 31/128,
DY-AI-Easy-KB 39/28, FengRun 5/33 and HanaTour 5/18 (filled/blank).
- Current Finance facts classify as 614 with a consistent nonblank Group Code and 372 with neither Group Code field
populated. The latter remain their own blank-`Booking Room` output rows.
- Of the rows with a Group Code, only `LLT260719MA` and `LT260718KC` have no current Booking source match. They account
for the other two blank output rows; no other nonblank Group Code yielded an empty `Booking Room`.
- The LianTai workbook's `21-31` sheet row 26 is a representative direct match:
`RES_COMMENT=LT260718KB` and `Booking Room=【DBL】12`. The accepted Markdown contains twelve `LT260718KB` / `DBL`
source rows, so the output is the expected Group-Code aggregation.
- `Total Booking Price` is independent of the Booking mapping. It displays the Finance fact's room-category/price
composition (for example `RM3` and static prices), while Booking only contributes room type and booked quantity. The
current Markdown source has no unit-price field from which a Booking-derived total could be calculated.
## Finding
There is no observed failure to write `Booking Room` in the generated job. Blank cells match the established rule for
missing or unresolved Group Codes; the apparent all-blank impression can result from looking at the leading no-code
rows in a workbook. In the LianTai sheet, the first matching Booking value occurs at Excel row 26.
If the intended business rule is instead to derive a price from the Markdown Booking room type, that is a separate
product change: the Markdown schema needs a price source and an explicit room-type-to-price policy. It is not supported
by the current Group Code / room type / quantity contract.