# Salesforce / CM / BI Report Lineage Index

Date: `2026-07-07`

## 用法

这份文档是
`报表地图版`
。

它回答的是：

- `这张报表主要连着哪些模型`
- `这些模型背后主要靠哪些 CRM 对象`
- `最敏感字段是什么`
- `当前最应该先查哪类 gap`

如果要按
`单张报表`
展开看完整证据，
看：

- [salesforce-cm-bi-report-trace-cards-2026-07-07.md](/Users/amber/ai/nexuscrm-pingcap-pack/docs/salesforce-cm-bi-report-trace-cards-2026-07-07.md)

如果要看
`这张报表的消费面证据到底有多硬`
，
再看：

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

如果要 2 分钟快读，
看：

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

## Report Lineage Index

| `report_id` / 报表面 | 当前最像在看什么 | 主 datasource / 模型 | 关键对象 | 最敏感字段 | 当前默认先查哪类 gap |
|---|---|---|---|---|---|
| `1733a75e-a1b2-4415-8732-2c053657e245` | `pipeline data quality / cleanup monitor` | `dws_data_quality_alerting`、`date_spine`、`salesforce_opportunities`、`dws_salesforce_pipeline_data_quality_cleanup_detail_v2` | `Opportunity`、`Quote`、次级 `Account` | `stage_name`、`forecast_category`、`probability`、`close_date`、`launch_date`、`quote_service_start_date`、`quote_service_end_date` | `Opportunity/Quote L2 parity`，再看 owner-team / trigger residue |
| `837f6250-3c3d-44b9-af6f-4db9aeb30a94` | `ARR summary + regional/company forecast` | `dws_salesforce_arr_summary`、`dws_fy25_regional_acv_achivement_and_forecast_detail`、current-month order MRRARR datasources | `Opportunity`、`Order`、`Order_Product__c`、`Account`、次级 `Revenue__c` | `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` | `Order carry-over + RevRec + line-item parity` |
| `aadb4637-a4be-41e0-a045-8df92303e595` | `opportunity snapshot / account lens` | `salesforce_opportunities_snapshot` + legacy `salesforce.account/opportunity/org_c/user` | `Opportunity`、`Account`、`Opportunity_Product__c` | `account_id`、`account_name`、`fy26_icp`、`fy26_segmentation`、`arr_amount_usd`、`opportunity_name`、`opportunity_product_family` | `Opportunity/Account parity`，次级 opp-product bridge residue |
| `0f2ad8b8-a0a5-40e1-842a-f208c6247c0b` | `opportunity stage duration / conversion` | `dws_opportunity_stage_duration`、`dws_opportunity_stage_conversion_rates`、`salesforce_opportunities` | `Opportunity`、`Opportunity_Product__c` | `arr_amount_usd`、`opportunity_name`、`opportunity_product_family`、`stage_duration_days` | `Opportunity parity`，次级 opp-product legacy bridge residue |
| `d9161f0e-f04c-49dc-82e1-053ab508ce67` | `opportunity + account + PLG pipeline blend` | `salesforce_opportunities`、legacy `salesforce.account/opportunity/org_c/user`、`plg_pipelines` | `Opportunity`、`Account`、`Org__c` | `account_id`、`account_name`、`arr_amount_usd`、`mapped_stage_name`、`opportunity_name`、`region` | `Opportunity + Account shared-key parity` |
| `fd12e3fc-d36f-4cc5-b2d9-9ed2808489dc` | `lead funnel / ICP path` | `dws_icp_summary`，较早还打 `dws_lead_timeline`、`dim_lead` | `Lead`、`CampaignMember`、`Opportunity`、次级 `Account` / `Contact` | `lead_mql_timestamp`、`lead_iqm_timestamp`、`lead_status`、`lead_surrogate_key`、`first_touch_campaign`、`last_touch_before_iqm`、`last_touch_before_opp_creation` | `Lead lifecycle parity`，再看 CampaignMember response/involvement parity |
| `8c6f30a4-c6fe-4536-ac62-d937d0176ebd` | `campaign attribution / contact-opportunity touch` | `salesforce_campaign_members`、`salesforce_campaign_attributions`、`dws_campaign_attribution`、`dws_campaign_attribution_details`、次级 `salesforce_opportunities` / `dim_opportunity` | `CampaignMember`、`Contact`、`Opportunity`、`Lead`、次级 `Campaign` / `OpportunityContactRole` | `first_responded_date`、`campaign_member_status`、`has_responded`、`is_contact_involved`、`contact_response_date`、`attributed_arr`、`attributed_acv` | `CampaignMember parity`，再看 Contact stitching parity |
| `58339683-7a7a-4bb6-91bd-14b149572ac9` | `account + current/monthly order MRRARR composite` | `nexuscrm_final.nexuscrm_account/org_c`、legacy `salesforce.account/...`、`dws_salesforce_account_quarterly_mrrarr_bo_subscription_and_cloud_pivot`、`dws_salesforce_order_current_monthly_mrrarr_bo_subscription_and_cloud` | `Account`、`Org__c`、`Order`、`Order_Product__c`、次级 `Revenue__c` | `account_number`、`fy26_icp`、`fy26_segmentation`、`account_current_order_type`、`order_product_family`、`arr_usd_cd_rate_current_month`、`mrr_usd_cd_rate_finance` | `Account current-order-type + Order carry-over parity`；repo 侧当前更像 `account_current_order_type` 先稳定落在 account-quarterly/account-basic-info 链，current-month order 模型自身仍保留一部分 `NULL` placeholder |
| `673c89ef-fb02-4303-a9a2-5519a652051c` | `account + global ARR forecast master surface` | `nexuscrm_final.nexuscrm_account/org_c`、legacy `salesforce.account/opportunity/org_c/user`、`salesforce.user_role`、global ARR forecast snapshot / snapshot_v2、repo-side `dws_global_arr_forecast_cloud_account_best_and_base` / `dws_global_arr_forecast_op_to_cloud_best_and_base_detail` | `Account`、`Org__c`、`Opportunity` | `account_id`、`account_number`、`fy26_icp`、`fy26_segmentation`、`owner_user_id`、`sales_team_name`、`forecast_date`、`basecase_arr_usd`、`bestcase_arr_usd`、`tenant_region` | `Account dimension parity`，次级 tenant bridge drift；repo-side forecast account 模型已带 `account_current_order_type`，但当前 live report query 还没把它打成这张 front-door 的 direct field hit |
| `2128769b-9f86-4c7a-a9f4-8cc7491868e3` | `account + forecast variant` | legacy `salesforce.account/opportunity/org_c/user`、`salesforce.user_role`、global ARR forecast `best_and_base` / `snapshot_v2`、repo-side `dws_global_arr_forecast_cloud_account_best_and_base` / `dws_global_arr_forecast_op_to_cloud_best_and_base_detail` | `Account`、`Org__c`、`Opportunity` | `account_number`、`fy26_icp`、`fy26_segmentation`、`account_id`、`account_name`、`account_industry`、`forecast_date`、`tenant_id`、`tenant_region` | `Account dimension parity`，次级 tenant bridge drift；repo-side forecast account 模型已带 `account_current_order_type`，但当前 live report query 还没把它打成这张 front-door 的 direct field hit |
| `690c8087-0697-4272-b05e-2ee37d728c15` | `PLG signup / billing-capable cloud funnel` | `dws_tidb_cloud_marketing_funnel_1_to_3_stage_new_users_monthly_group`、`dws_daily_external_cloud_billing_capable_user_detail_2023_to_day`、`dws_daily_external_cloud_signup_active_engaged_billingcapable_user_count`、多张 weekly accumulated count datasource；当前未见 direct `Lead` 表命中 | `Account`、`Org__c`、`tenant bridge`，谨慎次级 `Lead` | `tenant_id`、`tenant_name`、`tenant_email`、`tenant_region`、`account_id`、`account_name`、`account_current_order_type`、`traffic_funnel_type` | `Account/Org shared-key parity`，再看 order-side contamination |
| `00675e54-cae4-4562-ae95-002a3b22b3d4` | `tenant / cluster / component detail` | `dws_cloud_all_clusters_component_detail_basic_info`、`dws_cloud_tenants_project_cluster_basicinfo`、`dws_cloud_tenants_basicinfo`、次级 `dwm_dbaas_cluster_components` / `billing.aws_prod_billing_2022` | `Org__c`、`Account`、`tenant bridge` | `tenant_id`、`tenant_name`、`tenant_region`、`tenant_plan`、`tenant_email`、`account_id` | `Account/Org tenant-bridge parity`，再看 cloud-cluster stitching |
| `1e22be38-bbfe-4c28-9d7d-596d143c39c5` | `cloud billing / account-owner` | `azure_billing*`、`dwd_aws_prod_billing_v2`、`gcp_monthly_billing_with_support_cost_alloc`、`dim_realtime_cloud_account_project_owner`、`dws_cloud_tenants_basicinfo`，并混入 HR / project / invoice 辅助源 | `Account`、`Org__c`、`tenant bridge` | `account_id`、`tenant_id`、`tenant_name`、`account_current_order_type`、project-owner / support-cost allocation 邻近字段 | `Account/Org shared-key parity`，再看 billing-owner mapping drift |
| `31605bff-7555-430c-9377-c26a69be7e49` | `Cloud Billing Breakdown Detail` | `dws_cloud_tenants_basicinfo`、`dws_cloud_all_clusters_component_detail_basic_info`、`dwd_aws_prod_billing_v2`、`dws_aws_prod_billing_v2`、`dws_azure_prod_billing_v2`、`dws_gcp_prod_billing_v2`、`gcp_monthly_billing_with_support_cost_alloc`、次级 `salesforce_opportunities` | `Account`、`Org__c`、`Opportunity`、`tenant bridge` | `account_current_order_type`、`account_id`、`account_name`、`tenant_id`、`tenant_name`、expense / support-cost allocation 邻近字段 | `Account/Org shared-key parity`，再看 cloud-billing allocation contamination |
| `eae0ca4f-c747-40ef-b34c-f7f50cb1d1a2` | `prod tenant daily cost alert` | `dws_monitor_cloud_prod_daily_cost_alert`、`dws_monitor_cloud_prod_tenant_daily_cost_alert`、`dws_cloud_tenants_basicinfo`、次级 `aws_prod_billing_average_cost_monitor` audit 源 | `Org__c`、`Account`、`tenant bridge` | `tenant_id`、`tenant_name`、`tenant_region`、prod cost alert 邻近字段 | `Account/Org tenant-bridge parity`，再看 billing monitor drift |
| `f9c4bd70-8ce4-487c-abb1-5518ffffd6bd` | `activated-order / monthly revrec by account+tenant` | `model_tidbcloud.dws_cloud_tenants_basicinfo`、`dws_salesforce_activated_order_account_basic_info_v3`、`dws_salesforce_activated_order_account_monthly_revrec_v3`、`salesforce_order_daily_view`、`salesforce_org_monthly_revrec`、`monthly_revrec_collections` | `Order`、`Order_Product__c`、`Account`、`Org__c`、次级 `Revenue__c` / `Invoice_Collection__c` | `tenant_id`、`tenant_name`、`account_current_order_type`、`order_product_family`、`mrr_usd_cd_rate_finance`、`collections_status_c`、`invoice_status_c`、`cash_collected_c`、`payable_amount_usd_2_exc_tax_c`、`plg_bd_pool_c`、`marketplace_c` | `Order + Invoice_Collection carry-over parity`，再看 RevRec / line-item parity；repo 侧当前更像 `account_current_order_type` 先从 `activated_order_account_basic_info_v3` / `dws_cloud_tenants_basicinfo` 进来，而 `activated_order_account_monthly_revrec_v3` 自身仍保留 `NULL` placeholder |

## Report Grouping

| 报表组 | 当前最核心的 surface |
|---|---|
| `Pipeline / Forecast / Opportunity Quality` | `1733...`、`837...`、`aadb...`、`0f2...`、`d916...` |
| `Lead Funnel / Qualification` | `fd12...` |
| `Campaign Attribution / ICP Analysis` | `8c6f...` |
| `Order / ARR / RevRec / Collections` | `583...`、`837...`、`f9c4...` |
| `Account / Tenant Linkage / Customer Identity` | `673...`、`212...`、`690...`、次级 `583...` / `00675...` / `1e22...` / `31605...` / `eae0...` / `aadb...` |

## 一句话收口

`如果要先判断“这条差异会打哪张报表”，最稳的做法不是先从对象猜，而是先从报表 lineage 看它背后的主模型、关键对象、最敏感字段，再回到对象 / 机制 / 字段视角去定位具体 gap。`