# Salesforce / CM / BI Runtime Report Impact Crosswalk

Date: `2026-07-07`

## 用法

这份文档只做一件事：
把
`真 runtime 边界`
直接映射到
`哪张报表`
、
`哪些字段`
、
`哪些下游模型`
。

适合回答：

- `这条真 gap 会先打哪张报表`
- `报表上先漂的是哪些字段`
- `哪些模型最该先看`

如果当前还在判断
`是不是 runtime`
，
先看：

- [salesforce-cm-bi-runtime-boundary-shortlist-2026-07-07.md](/Users/amber/ai/nexuscrm-pingcap-pack/docs/salesforce-cm-bi-runtime-boundary-shortlist-2026-07-07.md)

如果当前已经准备开 runtime issue，
再看：

- [salesforce-cm-bi-runtime-boundary-issue-drafts-2026-07-07.md](/Users/amber/ai/nexuscrm-pingcap-pack/docs/salesforce-cm-bi-runtime-boundary-issue-drafts-2026-07-07.md)

如果只想要
`超短执行版`
，
再看：

- [salesforce-cm-bi-frontdoor-execution-sheet-2026-07-07.md](/Users/amber/ai/nexuscrm-pingcap-pack/docs/salesforce-cm-bi-frontdoor-execution-sheet-2026-07-07.md)

## Runtime Crosswalk

| runtime 组 | Salesforce 现网会做什么 | CM 目前已支持什么 | CM 当前未支持 / 疑似未支持什么 | 主 front-door 报表 | 最敏感字段 | 最先打到哪组模型 |
|---|---|---|---|---|---|---|
| `Lead runtime` | `LeadTrigger` / `LeadAITrigger` 仍承担 lead lifecycle 收口、assignment / reminder / notification 长尾、lead-account / campaign 邻近残余语义 | `IQM_Completion_Flow`、`Lead_Status_Duration`、`Lead_Auto_Create_Org`、`BN_Lead_Relate_to_Account_by_Email_Domain_Flow`、`Std_ConvertLeadCampaignPreview` 已在；`lead_mql_timestamp` / `lead_iqm_timestamp` 已有主承接 | 在 `Lead_StatusChangeTimestamp` 收窄和已知 Lead parity 清完后，仍只存在于 live trigger 的 residual lead runtime | `fd12e3fc-d36f-4cc5-b2d9-9ed2808489dc` `lead funnel / ICP path` | `lead_mql_timestamp`、`lead_iqm_timestamp`、`lead_status`、`lead_surrogate_key`、`first_touch_campaign`、`last_touch_before_iqm`、`last_touch_before_opp_creation` | `salesforce_leads`、`dim_lead`、`dws_lead_timeline`、`dws_icp_summary` |
| `Opportunity / Quote runtime` | `OpportunityTrigger` / `QuoteTrigger` 仍承担机会质量、owner-team 邻近残余、quote cleanup / service-window 之外的 residual orchestration | `Std_OpportunityStageDerivedFields`、`Opportunity_Cloud_Order_Type_Set`、`Opportunity_Close_Date_Auto_Set`、`Opportunity_Pricebook_Default`、Quote validation substrate、quote enrichment 已在 | 在 `Quote_update_nonstandard_conditions_checkbox*`、`OpportunityShareToPersalesOwner*`、quote inactive validation 这些 parity 清完后仍残留的 trigger-only drift | `1733a75e-a1b2-4415-8732-2c053657e245` `pipeline data quality / cleanup monitor` | `stage_name`、`forecast_category`、`probability`、`close_date`、`launch_date`、`quote_service_start_date`、`quote_service_end_date`、`owner_team` | `dws_data_quality_alerting`、`rpt_data_quality_wtw_comparison`、`dws_salesforce_pipeline_data_quality_cleanup_detail_v2`、次级 `salesforce_opportunities` / `dim_opportunity` |
| `Finance runtime` | `OrderTrigger` / `RevenueTrigger` / custom line-item trigger surfaces 仍承担 order-account-tenant update 后 residual carry-over、revrec runtime orchestration、custom line-item finance drift | `Order_Default_RevRec_Entity`、`Cloud_Registration_Source_from_Org_to_Order`、`Order_Quote_Payment_Field_Inheritance`、Order 对 `Revenue__c` 的 rollup、`Order_Product__c` / `Revenue__c` / `Invoice_Collection__c` helper substrate 已在 | 在 `Order_Org_Auto_Set_Account_*`、`Order_Set_PLG_BD_Pool`、`RevRec_Set_PLG_BD_Pool`、`Collection_*`、auto-number parity 清完后仍只能依赖 live trigger 的 finance runtime | `837f6250-3c3d-44b9-af6f-4db9aeb30a94` `ARR summary + regional/company forecast`；`f9c4bd70-8ce4-487c-abb1-5518ffffd6bd` `activated-order / monthly revrec by account+tenant` | `arr_amount_usd`、`accurate_acv_amount`、`order_product_family`、`arr_usd_cd_rate_current_month`、`mrr_usd_cd_rate_finance`、`Recognized_Revenue_Amount__c`、`Amount_Before_Adjust__c`、`collections_status_c`、`payable_amount_usd_2_exc_tax_c`、`plg_bd_pool_c`、`marketplace_c` | `dws_salesforce_arr_summary`、current/monthly order MRRARR datasources、`salesforce_order_daily_view`、`salesforce_org_monthly_revrec`、`monthly_revrec_orders`、`monthly_revrec_collections` |

## Secondary Spillover

| runtime 组 | 次级 front-door 报表 | 为什么会外溢 |
|---|---|---|
| `Lead runtime` | `8c6f...` 次级，谨慎通过 campaign/contact stitching 外溢 | lead 侧 residual runtime 会通过 lead-to-campaign / convert 邻近链影响 attribution 输入 |
| `Opportunity / Quote runtime` | `837...`、`0f2...`、`aadb...`、`d916...` | 这些面都会复用 opportunity stage / ARR / quote-enrichment / owner-team 邻近语义 |
| `Finance runtime` | `583...`、次级 `690...` | finance carry-over / line-item drift 会污染 current-month MRRARR 和 account/tenant bridge 邻近面 |

## 排查顺序

1. `fd12...`
   先看 lead runtime 是否已经越过 parity 层。
2. `1733...`
   先把 Quote / owner-team parity 排干净，再看 opp/quote runtime residue。
3. `837...` 和 `f9c4...`
   先把 finance carry-over / collections / revrec parity 排干净，再看 trigger-only finance residue。

## 一句话收口

`如果现在只关心“真 runtime gap 到底先打哪张报表、哪些字段、哪些模型”，主看 `fd12...`、`1733...`、`837...`、`f9c4...` 这 4 张 front-door 就够了。`