# Salesforce / CM / BI Object-to-FrontDoor Impact Index

Date: `2026-07-07`

## 用法

这份文档是
`对象 -> 报表`
桥接版。

它回答的是：

- `某个对象在 Salesforce 现网主要做什么`
- `CM 本地已经接住了什么`
- `当前还差什么`
- `最先打哪张 front-door 报表`
- `次级还会外溢到哪些报表`
- `这些报表影响的证据有多硬`

如果要先从对象本身快速读，
看：

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

如果要先看 front-door 消费面证据强弱，
看：

- [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)

如果要先看报表背后的主模型，
看：

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

## 读法

| 问题 | 默认读法 |
|---|---|
| `这个对象最先会把哪张报表打歪` | 先看 `主 front-door` |
| `是不是已经坐实是前台报表影响` | 先看 `证据强度` |
| `是 parity 还是 runtime` | 最后看 `默认 gap 类型` |

## Object-to-FrontDoor Index

| 对象 | Salesforce 现网主要会做什么 | CM 目前已支持什么 | 当前主要差异 / 待补 / 疑似待补什么 | 主 front-door | 次级 front-door / consumer | 证据强度 | 默认 gap 类型 |
|---|---|---|---|---|---|---|---|
| `Lead` | 维护 lifecycle、`lead_mql_timestamp`、`lead_iqm_timestamp`、status-change 时间戳、lead-account stitching、convert 后 campaign path | `IQM_Completion_Flow`、`Lead_Status_Duration`、`Lead_Auto_Create_Org`、`BN_Lead_Relate_to_Account_by_Email_Domain_Flow`、`Std_ConvertLeadCampaignPreview` 已在 | `Lead_StatusChangeTimestamp` 仍过宽；Lead assignment / reminder / notification 长尾 parity 未清；清完后才是 `LeadTrigger` / `LeadAITrigger` | `fd12...` `lead funnel / ICP path` | `8c6f...`；`salesforce_leads`、`dim_lead`、`dws_lead_timeline`、`dws_icp_summary` | `fd12...` 为 `report-backed`；模型链为 `repo lineage + live schema` | `semantic mismatch + L2 Lead parity`，后续才到 `Lead runtime` |
| `Opportunity` | 维护 stage、forecast、probability、ARR/ACV、cloud-order-type、launch/close helper、owner-team 邻近语义 | `Std_OpportunityStageDerivedFields`、`Opportunity_Cloud_Order_Type_Set`、`Opportunity_Close_Date_Auto_Set`、`Opportunity_Pricebook_Default` 已在 | `OpportunityShareToPersalesOwner` / `OpportunityUpdateShareToPerSalOwner` 缺失；后续才是 `OpportunityTrigger` | `1733...` `pipeline data quality / cleanup monitor` | `837...`、`aadb...`、`0f2...`、`d916...`；`salesforce_opportunities`、`dim_opportunity` | `1733...` / `837...` 已 `report-backed`；`aadb...` / `0f2...` / `d916...` 当前更像 `lineage-backed secondary consumer`，本轮 live window 未看到 `requestor = looker_studio` 命中 | `L2 exact-flow parity`，后续才到 `Opportunity / Quote runtime` |
| `Quote` | 维护 service-window、nonstandard terms、submit 时 validation、quote-account-opportunity 对齐 | Quote 字段、`Quote_Reset_IsConvert_On_Submit`、`Quote_Account_Opportunity_field`、validation substrate 已在 | `Quote_update_nonstandard_conditions_checkbox` / `_2` 缺失；一组 quote validation 仍 local inactive | `1733...` `pipeline data quality / cleanup monitor` | 次级 `salesforce_opportunities` quote enrichment 邻近链、`837...` | `1733...` 为 `report-backed`；Quote cleanup 字段已在 front-door 字段片段里坐实 | `L2 Quote parity + activation-state mismatch` |
| `CampaignMember` | 维护 `first_responded_date`、response / involvement、first/last touch、lead-contact convert 后 relink | `Lead_Set_First_And_Last_CampaignMember*`、`Contact_Set_First_And_Last_CampaignMember*`、`Std_ConvertLeadCampaignPreview`、`Std_RelinkLeadChildren` 已在 | `Campaign_Member_Key_Message_Update` 缺失；清完后才看 `Trigger_CampaignMember` | `8c6f...` `campaign attribution / contact-opportunity touch` | `fd12...`；`salesforce_campaign_members`、`dws_campaign_attribution`、`dws_campaign_attribution_details` | `8c6f...` 为 `report-backed`；当前这轮 front-door live query 最硬的是直接打 `dws_campaign_attribution`，字段已复现到 `attributed_arr`、`campaign_id`、`campaign_name`、`contact_response_date`、`opportunity_contact_role`；raw `campaign_member` 更多是 substrate/lineage 层 | `L2 CampaignMember parity`，后续才到 `runtime candidate` |
| `Contact` | 参与 lead/contact merge、campaign attribution stitching、默认值与 account helper 长尾 | Contact 基础对象、公式、`Contact_Set_First_And_Last_CampaignMember*` 已在 | Contact live Flow peer 未见本地 peer；残余 Contact trigger surfaces 仍在 | `8c6f...` `campaign attribution / contact-opportunity touch` | `fd12...`；`dws_campaign_attribution_details`、`dws_lead_timeline`、`dim_lead` | `8c6f...` / `fd12...` 都是 `report-backed`；Contact 语义在 front-door 字段里直接出现 | `Contact stitching parity + runtime candidate` |
| `Account` | 维护 `Account_ID`、ICP、segmentation、industry、current-order-type、partner-sales-owner、contract-valid 和 shared dimension | `Account_ID__c`、`Current_Order_Type__c`、`Contract_Valid_*` 字段 substrate 已在；`Org_Set_Account` 已在；本地还已有 `Account_status_Flow`、`Account_First_Order_Start_Date_Update`、`Account_Auto_Submit_Approval` 这组 active Flow | `Account_Current_Order_Type`、`Account_Partner_Sales_Owner_Set`、`Account_Contract_Valid_Message` 缺失；后续才是 `AccountTrigger` | 当前最直接的字段级前台命中是 `31605...` / `f9c4...`（`account_current_order_type`）与 `673...` / `212...`（`sales_team_name` / `owner_user_id`）；次级才到 `583...` | `690...`、`1e22...`、`aadb...`；`salesforce_accounts`、`dim_account`、`dim_tenant` | `31605...` / `f9c4...` / `673...` / `212...` 已能从 live query 直接点到 account-side关键字段；而 repo-side current-order-type 又分成两档：`583...` / `f9c4...` 邻近的 account-basic-info / account-quarterly / tenant 模型会真带值，但部分 current-month order / monthly-revrec fact 自身仍保留 `NULL` placeholder。`690...` / `1e22...` 当前更像 account/tenant bridge 邻近面；`aadb...` 当前仍更像与 Opportunity 共用的 `lineage-backed secondary consumer` | `L2 Account dimension parity`，后续才到 `Account runtime candidate` |
| `Org__c` | 维护 tenant/account bridge、`Accumulate_revenue_to_Org__c`、cloud registration source 上游 org identity | `Org_Set_Account` 已在；`Cloud_Registration_Source_from_Org_to_Order` 已在 | 缺口更集中在下游 carry-over peer：`Order_Org_Auto_Set_Account_*`、`Cloud_Registration_Source_from_Org_to_Collections` | `583...` `account + current/monthly order MRRARR composite` | `690...`、`837...`、`f9c4...`、`673...`；`dws_cloud_tenants_basicinfo`、`salesforce_org_monthly_revrec` | `583...` / `690...` / `f9c4...` 都是 `report-backed`；org bridge 字段在 live schema 已坐实 | `shared bridge parity` |
| `Order` | 维护 quote/payment 继承、order-org-account-tenant carry-over、cloud-registration-source、revrec entity、PLG pool、激活语义 | `Order_Quote_Payment_Field_Inheritance`、`Cloud_Registration_Source_from_Org_to_Order`、`Order_Default_RevRec_Entity`、`Std_OrderActivateStamp` 已在 | `Order_Org_Auto_Set_Account_*`、`Order_Set_PLG_BD_Pool` 缺失；清完后才看 `OrderTrigger` | `583...` `account + current/monthly order MRRARR composite` | `837...`、`f9c4...`；`salesforce_orders`、`salesforce_order_daily_view`、`cp_order_monthly_revrec` | `583...` / `837...` / `f9c4...` 都是 `report-backed`；order-day / revrec 细面仍有 `direct-query spillover` | `L2 finance carry-over parity`，后续才到 `Finance runtime` |
| `Revenue__c` | 维护 revrec 明细、`Amount_Before_Adjust`、credit、status、PLG pool、`Name` identity | Revenue 字段、`RevRec_Account`、order 侧 revenue rollup substrate 已在 | `RevRec_Set_PLG_BD_Pool` 缺失；`Revenue__c.Name` auto-number 未补；后续才是 `RevenueTrigger` | `837...` `ARR summary + regional/company forecast` | `f9c4...`；`salesforce_revrec`、`salesforce_orders.revenues`、`salesforce_org_monthly_revrec`、`monthly_revrec_orders` | `837...` 为 `report-backed`；更细 revenue 明细仍偏 `direct-query spillover` | `L2 revrec parity + auto-number parity`，后续才到 `Finance runtime` |
| `Invoice_Collection__c` | 维护 collections helper、status、payable / collected / exc-tax、invoice status、marketplace、org-to-collection bridge、PLG pool、`Name` identity | IC helper 字段 substrate 已在；Order 侧已有 collections rollup | `Collection_Set_PLG_BD_Pool`、`Collection_Amount_and_Payable_Amount_exc_tax*`、`Cloud_Registration_Source_from_Org_to_Collections` 缺失；`Name` auto-number 未补 | `f9c4...` `activated-order / monthly revrec by account+tenant` | `salesforce_order_daily_view`、`salesforce_org_monthly_revrec`、`monthly_revrec_collections` | `f9c4...` 为 `report-backed`；collections / payable 细面仍偏 `direct-query spillover` 而非完整命名 dashboard registry | `L2 collections parity + auto-number parity` |
| `Contract` | 维护 `ContractNumber`、business status、activated/effective 时间、过期与 account contract-valid 邻近语义 | `ContractNumber`、`Std_ContractActivateStamp`、`Contract_Archived_Status_Autopromote` 已在；Account 侧已有 `Contract_Valid_*` substrate | `Auto_Expire_Contract`、`Contract_Update_Account_Contract_Valid` 未见本地 peer；但 `Order_Activate_Contract_*` 已属 intentional replacement | 主：`673... / 212...` 邻近 account governance | `583...`、`837...`、`salesforce_orders`、`salesforce_order_daily_view` | 更偏 `lineage + schema`，没有单独 contract dashboard 被坐实 | `intentional replacement + contract governance parity` |
| `Order_Product__c` | 维护 `order_product_family`、product-name、net-fees、service-window、manday、surplus | `Order_Product__c` 公式/rollup/validation substrate 已在 | `Order_Product__c.Name` auto-number 未补；清完后仍有 custom line-item trigger residue | 主：`837...` `ARR summary + regional/company forecast` | `583...`、`f9c4...`、`salesforce_order_daily_view`、`cp_order_monthly_revrec` | `837...` / `583...` / `f9c4...` 为 `report-backed` | `line-item parity + runtime residue` |
| `Opportunity_Product__c` | 维护 legacy opp-product product-family / service-window / net-fee 读取面 | `Opportunity_Product__c` 字段 substrate 已在；本地 active flow 仍直接读取它 | `Opportunity_Product__c.Name` auto-number 未补；仍带 legacy custom-object residue | 主：`0f2...` `opportunity stage duration / conversion` | `1733...`、`aadb...`、次级 `837...` | `0f2...` / `aadb...` 当前更像 `lineage-backed secondary consumer`；更硬的 report-backed blast radius 仍先经过 `1733...` / `837...` | `auto-number parity + legacy bridge residue` |

## 最高优先对象主链

1. `Lead`
   直接决定 `fd12...` 这张 lead funnel / ICP front door。
2. `CampaignMember + Contact`
   直接决定 `8c6f...` attribution 前台面的 response / involvement / stitching 语义。
3. `Account + Org__c + Order`
   是 `583...`、`690...`、`673.../212...`、`837...`、`f9c4...` 共用的 shared-key / tenant-bridge / carry-over 主链。
4. `Revenue__c + Invoice_Collection__c + Order_Product__c`
   是 finance 类 front-door 最容易先漂的 helper / revrec / line-item 明细链。

## 一句话收口

`如果问题是“某个对象到底会先打哪张报表”，先看这张索引；如果问题是“这张报表证据到底有多硬”，再回 consumer registry。`