监理报表 · 实体站筛选项 · PRD

作者 Luke　版本 v1.8　日期 2026-09-11　状态待开发评审　平台 BRAND_A & BRAND_B　类 R

版本记录

版本	日期	变更摘要
v1.8	2026-09-11	Sonnet 第二轮在 §2.2 补回 `GamingVenue` 与 `channel_type` 不联动的边界，并新增对应验收点。
v1.7	2026-09-11	Sonnet 首轮在 §3.3 补回监管传送边界与 outlet 编码警告；写明查询 0 笔仍须导出仅含表头的空档，并新增对应验收点。
v1.6	2026-09-11	L0 资讯图表中的范例选项改为 `1 - 实体站 A`，不显示启用／禁用状态；业务规则不变。
v1.5	2026-09-10	二次精简 §1～§4：删除 L0、范围与正文的重复说明，合并查询及异常规则；16 个验收点与业务结论不变。
v1.4	2026-09-10	Codex 候选精简版：保留 §2～§4 的业务结论与 16 个验收点；合并重复说明，改写为「条件 → 结果 → 例外」；目录、版本记录与附录分别默认折叠；重绘资讯图表。
v1.3	2026-09-09	既有需求重检：补 BO／Client 空视觉清单与本地图指纹；L0 不做边界逐项反指正文、红线或验收点；把正文既有边界补成可定位条款，并整理段落编号。业务口径、字段、文案与交互结论不变。
v1.2	2026-08-28	新增「修改筛选项后须按 `Serach` 才查询」；写入既有空态文案 `No More Data`；L0 资讯图表改为上传网址。
v1.1	2026-08-28	删除没有证据的空值防呆与对应验收点；关闭待确认项；简化 §3 跨站计数说明。规格结论不变。
v1.0	2026-08-28	初版：在 §2 新增 `GamingVenue:` 单选下拉；清单含禁用站；`All` 代表不筛选；§3 查询注单的 `outlet_id`；字段表维持 16 栏。

L0 · 快速掌握

监理报表实体站筛选核心逻辑资讯图表

① 一句话需求

在 Backoffice ▸ ReportCenter ▸ MegaxcessReport 新增 GamingVenue: 单选下拉，让审查人员直接查询并导出指定实体站的注单，不再导出全量后自行筛选与加总。

② 术语写死表

词	唯一含义
实体站	玩家注册时绑定的门店；绑定后不变。
`outlet_id`	注单上的实体站 ID；本需求直接筛选此栏。
`All`	不加入 `outlet_id` 条件。
已查询条件	上一次按下 `Serach` 并成功返回结果时的条件。

③ 全局红线表

不变量	违反后果	验证锚点
G1 下拉包含禁用实体站	禁用站的历史注单无法查询	`AC1` `AC2`
G2 `All` 不加入 `outlet_id` 条件	总数会静默漏掉禁用站注单	`AC3` `AC4`
G3 报表维持 16 栏及原 `outlet_id` 值	导出格式不再符合监理规格	`AC5`
G4 按 `Serach` 才套用条件	画面、页脚与导出会使用不同条件	`AC7` `AC8` `AC15`

④ 适用范围与「不做」边界

本次只在 MegaxcessReport 新增一个实体站筛选项。字段表、其他报表（含 代理盈亏）、实体站管理与权限结构都不改。阅读者为后台前端、报表后端与测试。

1. 范围

1.1　在既有查询条加入 GamingVenue:，位置在 Game Offering: 与 Line: 之间。

1.2　其余 6 个筛选项、Serach 文案、16 栏、排序、分页、页脚、明细子表、默认查询、其他报表、实体站管理、权限与提示语都不改；不做多选、模糊搜索、按名称输入、分组或小计。

2. 筛选项

2.1 值域与显示

项目	规则
标签	逐字为 `GamingVenue:`。
类型	单选下拉；默认选中 `All`。
清单	重新打开页面时读取实体站管理的全量清单；启用、禁用都显示。
选项格式	`ID - 名称`，连字号前后各一个半角空格。
排序	`All` 固定第一；其余按 ID 数值升序。

2.1.1　实体站禁用后仍有历史注单，因此不得从下拉移除。

2.2 查询语义

条件	结果
选择实体站	加入 `outlet_id = 所选 ID`；与其他筛选同时生效。
选择 `All`	不加 `outlet_id` 条件，包含禁用站历史注单。
修改后按 `Serach`	套用全部条件并回第 1 页。
修改但未搜索	表格、页脚、导出维持上一次成功查询。

2.2.1　GamingVenue 与 channel_type 不联动。选择实体站只叠加 outlet_id 条件，不得改写或排除 RGP／LBC 的既有取数。

3. 取数与输出

3.1 取数口径

3.1.1　直接筛选注单记录的 outlet_id，不得关联玩家当前资料。该值是玩家注册时绑定的实体站，不是下注地点；线上投注也按此值归属，且一个账号只绑定一个实体站。

3.2 表格、页脚与提示语

3.2.1　明细维持一行一笔注单与 16 栏。页脚按筛选结果重算，只合计 total_bet_amount、total_payout_amount。

场景	文案
查无资料	`No More Data`

3.3 导出

3.3.1　Export 导出上一次成功执行 Serach 的全部结果，不受分页或尚未搜索的修改影响。

3.3.2　查询结果为 0 笔时，Export 仍可使用；导出档只保留 16 栏表头，不含资料列。

3.3.3　本需求不改既有 outlet_id 送交监管方的流程，也不处理送出后的转码。现阶段未取得监管方的 outlet 编码定义，不得假设其编码与本系统 outlet_id 相同。

4. 权限与异常

筛选项随既有查看权限出现，导出沿用既有权限。清单失败沿用既有错误处理；不限制实体站数量，日期仍受 Data Range(settle time): 约束。

附录 A：验收标准

P0 为主路径或高风险口径；其余为 P1。

#	P	验收点
AC1	P0	实体站设为禁用后，该站仍显示在下拉（`G1`）。
AC2	P0	选中禁用站后，其历史注单仍可完整查询（`G1`）。
AC3	P0	区间内含禁用站注单时，选择 `All` 仍显示这些注单（`G2`）。
AC4	P0	选择 `All` 时，查询不得带任何 `outlet_id` 条件（`G2`）。
AC5	P0	报表仍为 16 栏；`outlet_id` 仍显示数字 ID，不新增实体站栏（`G3`）。
AC6	P0	ID `1`、`2`、`10`、`30002` 的排序为 `1 → 2 → 10 → 30002`。
AC7	P0	选择实体站并搜索后，页脚按筛选结果重算（`G4`）。
AC8	P0	选择实体站并搜索后，导出内容与该次查询结果一致（`G4`）。
AC9	P1	新增实体站后，不发版本；重新打开页面即可在下拉看到。
AC10	P1	`GamingVenue:` 位于 `Game Offering:` 与 `Line:` 之间。
AC11	P1	第一项逐字为 `All`，不是 `All Gaming Venue`、`ALL` 或双语。
AC12	P1	每个选项为 `ID - 名称`，使用半角连字号且前后各一空格。
AC13	P1	既有 6 个筛选项不变；按钮仍逐字为 `Serach`。
AC14	P1	同时选择 `GamingVenue:` 与 `Game Provider:` 时，两项同时生效。
AC15	P0	只修改实体站、未按 `Serach` 时，表格与页脚不变（`G4`）。
AC16	P1	修改实体站、未按 `Serach` 就导出时，使用上一次成功查询条件。
AC17	P0	上一次成功查询为 0 笔时，`Export` 仍可使用；档案含 16 栏表头且无资料列。
AC18	P0	既有送交监管方的流程与转码不变；实作不得假设监管方 outlet 编码等于本系统 `outlet_id`。
AC19	P0	选择任一实体站后，`RGP`／`LBC` 仍按既有 `channel_type` 取数；实体站条件不得改变两者范围。

附录 B：原型视觉清单

原型视觉清单

视觉 ID	载体	用途	证据
`VIS-BO-NONE`	BO	后台页面不使用图片或图片占位。	BO 原型只有报表控件。
`VIS-CLIENT-NONE`	Client	本需求不产出客户端页面。	§1 只改后台报表。

文档版本：v1.8 | 日期: 2026-09-11 | 作者: Luke | 文档状态：待开发评审

Megaxcess Report · Gaming Venue Filter · PRD

Author Luke　Source Version v1.8　Translation EN-1.0　Date 2026-09-11　Status Pending Development Review　Platform BRAND_A & BRAND_B　Class R

Version History

Version	Date	Change Summary
v1.8	2026-09-11	The second Sonnet review restored the rule in §2.2 that `GamingVenue` and `channel_type` do not affect each other, and added the corresponding acceptance criterion.
v1.7	2026-09-11	The first Sonnet review restored the regulatory-delivery boundary and outlet-code warning in §3.3. It also states that a zero-result query must still export an empty file containing only the headers, with corresponding acceptance criteria.
v1.6	2026-09-11	Changed the sample option in the L0 infographic to `1 - Gaming Venue A`, without showing enabled or disabled status. Business rules are unchanged.
v1.5	2026-09-10	Shortened §1–§4 again by removing repeated L0, scope, and body text and consolidating query and exception rules. The 16 acceptance criteria and business conclusions were unchanged.
v1.4	2026-09-10	Codex concise candidate: retained the business conclusions and 16 acceptance criteria from §2–§4, merged repeated explanations, and rewrote rules as condition → result → exception. The table of contents, version history, and each appendix default to collapsed. Redrew the infographic.
v1.3	2026-09-09	Revalidated the existing requirement: added empty BO/Client visual checklists and a local infographic fingerprint; linked each L0 boundary to its body section, red line, or acceptance criterion; converted existing boundaries into traceable clauses; and cleaned up paragraph numbering. Business definitions, fields, copy, and interactions are unchanged.
v1.2	2026-08-28	Added that changing a filter does not query until `Serach` is pressed; documented the existing empty-state copy `No More Data`; changed the L0 infographic to an uploaded URL.
v1.1	2026-08-28	Removed an unsupported empty-value safeguard and its acceptance criterion; closed open points; simplified the cross-venue counting explanation in §3. Specification conclusions are unchanged.
v1.0	2026-08-28	Initial version: added the single-select `GamingVenue:` dropdown in §2; included disabled venues; defined `All` as no filter; queried bet records by `outlet_id` in §3; retained the 16-column report.

Table of Contents

L0 · Quick Overview

Core logic of the Gaming Venue filter in Megaxcess Report

① Requirement in One Sentence

Add a single-select GamingVenue: dropdown under Backoffice ▸ ReportCenter ▸ MegaxcessReport. Reviewers can query and export bets from one Gaming Venue without exporting all records and filtering or totaling them manually.

② Fixed Terminology

Term	Only meaning in this document
Gaming Venue	The venue bound when the player registered. It cannot change afterward.
`outlet_id`	The Gaming Venue ID stored on the bet record. This requirement filters this field directly.
`All`	Do not add an `outlet_id` condition.
Applied query conditions	The conditions used by the most recent successful query after pressing `Serach`.

③ Global Invariants

Invariant	Failure Impact	Verification
G1 The dropdown includes disabled Gaming Venues.	Historical bets from a disabled venue cannot be queried.	`AC1` `AC2`
G2 `All` does not add an `outlet_id` condition.	Totals silently omit bets from disabled venues.	`AC3` `AC4`
G3 The report retains its 16 columns and original `outlet_id` values.	The export no longer meets the regulatory format.	`AC5`
G4 Conditions are applied only after pressing `Serach`.	The table, footer, and export use different conditions.	`AC7` `AC8` `AC15`

④ Scope and Exclusions

This release adds one Gaming Venue filter only to MegaxcessReport. It does not change the field list, other reports including Agent Win/Loss, Gaming Venue management, or permissions. Readers are backoffice frontend developers, report backend developers, and QA.

1. Scope

1.1 Add GamingVenue: to the existing query bar between Game Offering: and Line:.

1.2 Do not change the other six filters, Serach copy, 16 columns, sorting, pagination, footer, detail subtable, default query, other reports, Gaming Venue management, permissions, or messages. Do not add multi-select, fuzzy search, name input, grouping, or subtotals.

2. Filter

2.1 Values and Display

Item	Rule
Label	Exactly `GamingVenue:`.
Type	Single-select dropdown; `All` is selected by default.
Options	Load the complete list from Gaming Venue management whenever the page is reopened. Show both enabled and disabled venues.
Option format	`ID - Name`, with one ASCII space on each side of the hyphen.
Order	`All` is always first; all other options are sorted by numeric ID ascending.

2.1.1 A disabled Gaming Venue may still have historical bets and must not be removed from the dropdown.

2.2 Query Semantics

Condition	Result
Select a Gaming Venue	Add `outlet_id = selected ID`; combine it with the other filters.
Select `All`	Do not add an `outlet_id` condition; include historical bets from disabled venues.
Change filters and press `Serach`	Apply all conditions and return to page 1.
Change filters without searching	Keep the table, footer, and export on the most recent successful query.

2.2.1 GamingVenue and channel_type do not affect each other. Selecting a Gaming Venue only adds the outlet_id condition. It must not rewrite or exclude the existing RGP or LBC data scope.

3. Data and Output

3.1 Data Definition

3.1.1 Filter the outlet_id stored on the bet record directly. Do not join the player's current profile. This value is the Gaming Venue bound at registration, not the betting location. Online bets are attributed to this value, and each account is bound to only one Gaming Venue.

3.2 Table, Footer, and Copy

3.2.1 Keep one row per bet and all 16 columns. Recalculate the footer from the filtered results and total only total_bet_amount and total_payout_amount.

Scenario	Copy
No data	`No More Data`

3.3 Export

3.3.1 Export exports all results from the most recent successful Serach. It is independent of pagination and any changed filter that has not been searched.

3.3.2 Export remains available when the query returns zero records. The file contains the 16 column headers and no data rows.

3.3.3 This requirement does not change the existing process that sends outlet_id to the regulator or any transcoding after delivery. The regulator's outlet-code definition is not currently available. Do not assume it is the same as this system's outlet_id.

4. Permissions and Exceptions

The filter follows the existing view permission. Export follows the existing export permission. A list-loading failure uses the existing error handling. There is no limit on the number of Gaming Venues. Dates remain constrained by Data Range(settle time):.

Appendix A: Acceptance Criteria

P0 denotes a main path or high-risk rule. All others are P1.

#	P	Acceptance Criterion
AC1	P0	A disabled Gaming Venue remains in the dropdown (`G1`).
AC2	P0	Selecting a disabled venue returns all of its historical bets (`G1`).
AC3	P0	When the range contains bets from disabled venues, selecting `All` still returns those bets (`G2`).
AC4	P0	A query with `All` must not contain any `outlet_id` condition (`G2`).
AC5	P0	The report still has 16 columns; `outlet_id` remains a numeric ID and no new Gaming Venue column is added (`G3`).
AC6	P0	IDs `1`, `2`, `10`, and `30002` are ordered `1 → 2 → 10 → 30002`.
AC7	P0	After selecting a Gaming Venue and searching, the footer is recalculated from the filtered results (`G4`).
AC8	P0	After selecting a Gaming Venue and searching, the export matches that query result (`G4`).
AC9	P1	A newly added Gaming Venue appears in the dropdown after the page is reopened; no release is required.
AC10	P1	`GamingVenue:` is between `Game Offering:` and `Line:`.
AC11	P1	The first option is exactly `All`, not `All Gaming Venue`, `ALL`, or bilingual text.
AC12	P1	Every option is `ID - Name`, using an ASCII hyphen with one space on each side.
AC13	P1	The existing six filters remain unchanged, and the button remains exactly `Serach`.
AC14	P1	When both `GamingVenue:` and `Game Provider:` are selected, both conditions apply.
AC15	P0	Changing the Gaming Venue without pressing `Serach` does not change the table or footer (`G4`).
AC16	P1	If the Gaming Venue is changed and export is pressed without another `Serach`, use the most recent successful query conditions.
AC17	P0	When the most recent successful query returned zero records, `Export` remains available and produces a file with 16 headers and no data rows.
AC18	P0	The existing regulatory delivery and transcoding remain unchanged. The implementation must not assume the regulator's outlet code equals the system `outlet_id`.
AC19	P0	After selecting any Gaming Venue, `RGP` and `LBC` still use their existing `channel_type` scopes. The Gaming Venue condition must not change either scope.

Appendix B: Prototype Visual Checklist

Prototype Visual Checklist

Visual ID	Surface	Purpose	Evidence
`VIS-BO-NONE`	BO	The backoffice page uses no image or image placeholder.	The BO prototype contains only report controls.
`VIS-CLIENT-NONE`	Client	This requirement does not produce a client page.	§1 changes only a backoffice report.

Source document version: v1.8 | Translation: EN-1.0 | Date: 2026-09-11 | Author: Luke | Translation status: Pending Development Review