# CBF Blueprint Document — SAP S/4HANA Cloud Implementation
# CBF 蓝图文档 — SAP S/4HANA Cloud 实施项目

**Version / 版本**: V1.4 | **Date / 日期**: 2026年5月 | **Prepared by / 编制**: BOS Consulting Team

---

# Part I: Project Background / 第一部分：项目背景

## Company Overview / 公司概况

This project covers **CBF (Clyde Bergemann Forest S.A.)** in Belgium (Gosselies). CBW (Germany HQ) has an existing SAP S/4HANA system; SCB (Shanghai) is the parent company.
本项目覆盖 **CBF（比利时 Clyde Bergemann Forest S.A.）**，位于比利时戈斯利。CBW（德国总部）已有 SAP S/4HANA 系统，SCB（上海）为母公司。

| Entity / 实体 | Country / 国家 | Role / 角色 |
|---------------|----------------|-------------|
| **CBF** | Belgium / 比利时 (Gosselies) | Primary go-live entity / 首批上线实体 |
| **CBW** | Germany / 德国 | Group HQ, existing SAP / 集团总部，已有SAP系统 |
| **SCB** | China / 中国 | Parent company / 母公司 |

**Existing Systems at CBF / CBF 现有系统:**
- **Mafact**: ERP 系统，用于采购、库存、备件销售、组装跟踪
- **Winbooks**: 比利时财务/会计系统（总账、应收、应付、固定资产）
- **Dynamics 365**: CBW 用于新设备（NE）业务

## Core Objectives / 核心目标

1. **Cost Reduction / 降本增效**: Replace Mafact + Winbooks with SAP S/4HANA Cloud / 用 SAP S/4HANA Cloud 替换现有系统
2. **Business-Financial Integration / 业财一体化**: Real-time financial posting from business transactions, eliminating manual Excel-based reconciliation / 业务交易实时生成财务凭证，消除人工Excel对账
3. **Standardization / 标准化**: Group-wide standardized processes aligned with CBW / 与CBW对齐的集团标准化流程
4. **Compliance / 合规**: Belgian tax compliance — VAT Reverse Charge, DRC reporting, PEPPOL e-invoicing (mandatory from 2026-01-01) / 比利时税务合规 — 增值税逆向征收、DRC申报、PEPPOL电子发票（2026年1月1日起强制执行）

---

# Part II: Current System Landscape / 第二部分：现有系统现状

## As-Is Process Summary / 现有流程总结

### SD — Sales & Distribution / 销售与分销

| Aspect / 方面 | Current Status (Mafact) / 当前状态 |
|---------------|------------------------------------|
| Sales Organization / 销售组织 | Clyde Bergemann Forest S.A. |
| Product Lines / 产品线 | Legacy products assembled at CBF / CBF组装的传统产品；Aftermarket spares & service / 售后备件与服务；NE via CBW Dynamics 365 / 新设备通过CBW Dynamics 365 |
| Order Types / 订单类型 | Spare parts orders recorded in Mafact / 备件订单在Mafact中记录；Service orders NOT in Mafact / 服务订单不在Mafact中 |
| Quotation / 报价 | Generated in Mafact / Dynamics / 在Mafact/Dynamics中生成 |
| Pricing / 定价 | CBF original pricing standard, managed in Mafact / CBF原始定价标准，在Mafact中管理 |
| Customer Master / 客户主数据 | Customer types: OEM, Enduser, Agent/Reseller, Industrial Services; needs VAT/region classification per May 21 meeting / 客户类型：OEM、最终用户、代理商/经销商、工业服务；需按增值税/地区分类（5月21日会议） |
| Credit Management / 信用管理 | New process to be established in SAP / 将在SAP中新建流程 |
| Delivery / 发货 | Storekeeper packs, coordinates with freight forwarders / 仓库员打包，联系货运代理 |
| Invoicing / 开票 | Mafact issues delivery goods invoice; service orders manually booked in Winbooks / Mafact开具发货发票；服务订单手工录入Winbooks |
| E-Invoicing / 电子发票 | PEPPOL platform mandatory from 2026-01-01 / PEPPOL平台自2026年1月1日起强制执行 |

**Key SD Business Processes / SD关键流程:**

1. **Spare Parts Sales (Aftermarket)** / 备件销售（售后市场）: Standard sales from stock / 标准库存销售
2. **Service Orders** / 服务订单: Currently NOT tracked in any ERP / 当前不在任何ERP系统中跟踪 **[Issue #1 / 问题#1]**
3. **New Equipment Sales** / 新设备销售: Via CBW, assembled at CBF / 通过CBW处理，在CBF组装
4. **Third-Party Sales (BDK)** / 第三方销售: Identified in testing — PO trigger → vendor direct ship / 已在测试中识别 — 采购订单触发 → 供应商直发客户
5. **FOC / Free of Charge Deliveries** / 免费交货: Occasionally used / 偶尔使用
6. **Returns & Credit Memo** / 退货与贷项凭证: Managed manually / 人工管理

### MM — Procurement & Inventory / 采购与库存管理

| Aspect / 方面 | Current Status (Mafact) / 当前状态 |
|---------------|------------------------------------|
| Suppliers / 供应商 | ~1123, classified as Trade Creditors (Third Party / Inter Group) / 分为第三方贸易债权人/集团内贸易债权人 |
| Procurement Trigger / 采购触发 | Daily morning report: customer order + BOM + minimum safety stock / 每日晨报：客户订单+BOM+最低安全库存 |
| Purchase Orders / 采购订单 | Used for all procurement, issued manually in Mafact / 用于所有采购，在Mafact中手工创建 |
| Supplier Evaluation / 供应商评估 | Annual evaluation with file maintained / 年度评估，维护评估文件 |
| Inventory Valuation / 库存估值 | FIFO, historical value / 先进先出，历史成本 |
| Stock Count / 盘点 | Annual physical count, adjusted year-end / 每年一次实地盘点，年末调整 |
| Warehousing / 仓储 | Single store area, no external warehouse / 单一存储区域，无外部仓库 |
| Batch Management / 批次管理 | Not used / 未使用 |
| Parts Managed / 在管物料 | ~1000 active stock parts / 约1000个活跃库存物料 |

**Key MM Business Processes / MM关键流程:**

1. **Procure-to-Pay (standard goods procurement)** / 采购到付款（标准物料采购）
2. **Service Procurement** / 服务采购: Some services without PO / 部分服务无采购订单 **[Issue #2 / 问题#2]**
3. **Intercompany Procurement** / 集团内采购: CBF ↔ CBW group transactions / CBF与CBW之间的集团交易
4. **Inventory Management** / 库存管理: GR, GI, stock transfer / 收货、发货、库存转移
5. **Subcontracting** / 委外加工: Vendor A → Vendor B for processing → Customer / 供应商A送货到供应商B加工 → 客户 **[Issue #5 / 问题#5]**
6. **Emergency Procurement** / 紧急采购: Occasional / 偶发

### PP — Assembly (Production) / 组装（生产）

| Aspect / 方面 | Current Status (Mafact) / 当前状态 |
|---------------|------------------------------------|
| Nature / 性质 | Assembly only — NO raw materials production at CBF / 仅组装 — CBF无原材料生产 |
| Trigger / 触发 | Customer order → "Start of Manufacturing" in Mafact / 客户订单 → Mafact中"开始制造" |
| BOM / 物料清单 | Includes components + quantities for assembly / 包含组装的组件和数量 |
| Work Centers / 工作中心 | Not used / not planned / 未使用/未规划 |
| Production Monitoring / 生产监控 | Excel list for assemblies from Mafact; no system monitoring / 从Mafact导出Excel组装清单；无系统监控 |
| Semi-Finished / 半成品 | None — only finished assemblies / 无 — 仅有成品组装 |
| Subcontracting / 委外加工 | Identified as needed / 已识别为需项 **[Issue #5 / 问题#5]** |

**Key PP Business Processes / PP关键流程:**

1. **Customer-Triggered Assembly** / 客户触发的组装: Order received → reserve components → assemble → finished goods into stock / 收到订单 → 预留组件 → 组装 → 成品入库 **[Issue #6 / 问题#6]**

### QM — Quality Management / 质量管理

| Aspect / 方面 | Current Status / 当前状态 |
|---------------|--------------------------|
| Responsibility / 负责人 | Michael Scohy — Quality Control & Storeman / 质量控制兼仓管员 |
| Incoming Inspection / 来料检验 | All incoming parts checked against drawings / 所有来料按图纸检验 |
| Non-Conformance / 不合格品 | Non-compliance report sent to supplier / 向供应商发出不符合报告 |
| In-Process QC / 过程检验 | Not applicable (no production at CBF) / 不适用（CBF无生产） |
| Final Inspection / 成品检验 | Measurement on parts according to plan / 按计划进行零件测量 |
| QM System / 质量系统 | None — verbal communication / 无系统 — 口头沟通 |
| Certificates / 证书 | Not managed; problems not entered into ERP / 未管理；问题未录入ERP |

**Key QM Business Processes / QM关键流程:**

1. **Incoming Inspection** / 来料检验: 100% of incoming parts / 100%来料检验
2. **Non-Conformance Management** / 不合格品管理: Currently manual, sent to suppliers / 当前手工处理，发送给供应商

> **Note**: CBF has no production QC. Basic inspection functionality in MM may be sufficient instead of full QM module.
> **说明**: CBF 无生产过程质检。MM 模块的基础检验功能可能已足够，无需完整 QM 模块。

### FICO — Finance & Controlling / 财务与控制

| Aspect / 方面 | Current Status (Winbooks) / 当前状态 |
|---------------|--------------------------------------|
| Chart of Accounts / 会计科目表 | YCBE (Belgian National COA, exported from SAP test system) / 比利时国家科目表（已从SAP测试系统导出） |
| Accounting Period / 会计期间 | March to February / 3月至次年2月 |
| VAT Rates / 增值税税率 | 0% / 6% / 12% / 21% |
| Reverse Charge / 逆向征收 | Applied for intra-EU transactions / 适用于欧盟内部交易 |
| Withholding Tax / 预扣税 | 30% on payment at receipt / 收款时30% **[Issue #7 / 问题#7]** |
| Fixed Assets / 固定资产 | Managed in Excel (2 files: depreciation calc + asset details) / Excel管理（2个文件：折旧计算+资产明细） |
| Depreciation Method / 折旧方法 | Straight-line / 直线法 |
| Tax Reporting / 税务申报 | DRC — Government Declare report; BE GAAP basis / DRC政府申报报表，基于比利时公认会计准则 |
| Payment / 付款 | Isabell E-Banking for download/upload to Winbooks / Isabell网银与Winbooks对接 |
| AR/AP / 应收/应付 | Monthly foreign currency valuation; manual reconciliation / 月度外汇评估；手工对账 |

**Key FICO Business Processes / FICO关键流程:**

1. **General Ledger Accounting** / 总账会计: With Belgian YCBE chart of accounts / 使用比利时YCBE科目表
2. **AR Accounting** / 应收账款: Customer invoicing, credit management, dunning / 客户开票、信用管理、催款
3. **AP Accounting** / 应付账款: Vendor invoice verification, payment processing / 供应商发票校验、付款处理
4. **Asset Accounting** / 固定资产核算: Fixed asset master, depreciation / 固定资产主数据、折旧 **[Issue #7 / 问题#7]**
5. **VAT Reporting (Belgium-specific)** / 增值税报表（比利时特定）: Reverse charge, intra-EU / 逆向征收、欧盟内部 **[Issue #3 / 问题#3]**
6. **CO — Cost Center & Profit Center Accounting** / 成本中心与利润中心会计
7. **Intercompany Accounting** / 公司间会计: Group consolidation readiness / 集团合并准备

---

# Part III: Target Solution Design / 第三部分：目标方案设计

## Organizational Structure (Proposed) / 组织结构（建议）

| Level / 层级 | CBF (Belgium / 比利时) | Future: CBP (Poland / 波兰) — 预留 |
|--------------|------------------------|--------------------------------------|
| Company Code / 公司代码 | CBF1 | CBP1 (Future / 未来) |
| Sales Organization / 销售组织 | CBF Sales Org | CBP Sales Org (Future / 未来) |
| Purchasing Organization / 采购组织 | CBF Purchasing Org | CBP Purchasing Org (Future / 未来) |
| Plant / 工厂 | CBF Plant (BE01) | CBP Plant — TBD (Future / 未来) |
| Storage Location / 存储地点 | Workshop Store / 车间仓库 | TBD (Future / 未来) |

> **Status / 状态**: Organizational structure configuration completed as of May 13, 2026 / 截至2026年5月13日，组织结构配置已完成。

## Module Scope & Scope Items / 模块范围与Scope Item

> **Important Notice / 重要声明**: The following Scope Items (business processes) are proposed based on business research and meeting minutes. Specific SAP Scope Item IDs are not listed here — they must be verified against the BOS SAP Knowledge Base (`项目文档/BOS KB.lnk` → `references/02_scope/`) and the SAP S/4HANA Cloud Scope Item Catalog during configuration. Items marked with **[?]** require client confirmation.
>
> 以下 Scope Item（业务流程）基于业务调研和会议纪要提出。具体的 SAP Scope Item ID 未在此列出 — 需在配置阶段对照 BOS SAP 知识库（`项目文档/BOS KB.lnk` → `references/02_scope/`）及 SAP S/4HANA Cloud Scope Item 目录进行核实。标有 **[?]** 的项需要客户确认。

### SD — Sales & Distribution / 销售与分销

| Business Process / 业务流程 | Priority / 优先级 | Source / 依据 |
|----------------------------|-------------------|--------------|
| Sales Order Processing / 销售订单处理 | 必选 / Core | Meeting Apr 17, SD Research |
| Delivery Processing / 发货处理 | 必选 / Core | Meeting Apr 17, SD Research |
| Customer Invoice / Billing / 客户开票 | 必选 / Core | Meeting Apr 17, CBF Site Report |
| Credit Management / 信用管理 | 推荐 / Recommended | Meeting May 13 (New process needed) |
| Third-Party Sales (BDK) / 第三方销售 | 推荐 / Recommended | BDK Process Flow Test Doc |
| Free of Charge Delivery / 免费交货 | 评估选用 / Conditional | SD Research |
| Service Order Management / 服务订单管理 | **需要确认 / To Confirm** | **[Issue #1 / 问题#1]** |
| Consignment Sales / 寄售销售 | 不适用 / Not required | SD Research confirms not used |

### MM — Procurement & Inventory / 采购与库存管理

| Business Process / 业务流程 | Priority / 优先级 | Source / 依据 |
|----------------------------|-------------------|--------------|
| Purchase Requisition Processing / 采购申请处理 | 推荐 / Recommended | Meeting May 13 |
| Purchase Order Processing / 采购订单处理 | 必选 / Core | Meeting Apr 17, MM Research |
| Goods Receipt for PO / 采购收货 | 必选 / Core | Meeting Apr 17 |
| Inbound Delivery / 入库交货 | 推荐 / Recommended | MM Research |
| Service Procurement / 服务采购 | **需要确认 / To Confirm** | **[Issue #2 / 问题#2]** |
| Subcontracting / 委外加工 | **需要确认 / To Confirm** | **[Issue #5 / 问题#5]** |
| Consignment Procurement / 寄售采购 | 不适用 / Confirmed not used | MM Research |
| Batch Management / 批次管理 | 不适用 / Confirmed not used | MM Research |

### PP — Assembly / 组装

| Business Process / 业务流程 | Priority / 优先级 | Source / 依据 |
|----------------------------|-------------------|--------------|
| Basic Assembly / Production Order / 基本装配/生产订单 | **需要确认 / To Confirm** | **[Issue #6 / 问题#6]** |
| BOM Management / 物料清单管理 | 推荐 / Recommended | PP Research |

> **Note on PP / 关于PP的说明**: CBF operations are assembly-only (not full manufacturing). Current Mafact process: "Start Manufacturing" → reserve parts → "End Manufacturing" → remove components + add assembly to stock. The simplest SAP process should be selected.
>
> CBF 仅从事组装（非完整制造）。当前 Mafact 流程："开始制造"→ 预留零件 → "结束制造"→ 扣减组件 + 成品入库。应选择最简单的 SAP 流程。

### QM — Quality Management / 质量管理

| Business Process / 业务流程 | Priority / 优先级 | Source / 依据 |
|----------------------------|-------------------|--------------|
| Quality Inspection in GR / 收货质检 | 推荐 / Recommended | QM Research (100% incoming inspection) |
| Non-Conformance Management / 不合格品管理 | 推荐 / Recommended | QM Research (Currently manual) |

### FICO — Finance & Controlling / 财务与控制

| Business Process / 业务流程 | Priority / 优先级 | Source / 依据 |
|----------------------------|-------------------|--------------|
| General Ledger Accounting / 总账会计 | 必选 / Core | Meeting May 13 (Config completed) |
| Accounts Receivable / 应收账款 | 必选 / Core | Meeting Apr 17 |
| Accounts Payable / 应付账款 | 必选 / Core | Meeting Apr 17 |
| Asset Accounting / 固定资产核算 | 推荐 / Recommended | FICO Research (Currently Excel-managed) |
| Cost Center Accounting / 成本中心核算 | 必选 / Core | Meeting May 13 (Config completed) |
| Profit Center Accounting / 利润中心核算 | 推荐 / Recommended | Meeting May 13 (Config completed) |
| VAT Reporting (Belgium-specific) / 增值税报表 | **需要确认 / To Confirm** | **[Issue #3 / 问题#3]** |
| Withholding Tax Processing / 预扣税处理 | **需要确认 / To Confirm** | **[Issue #7 / 问题#7]** |
| Intercompany Reconciliation / 公司间对账 | 推荐 / Recommended | Multiple meetings |

## End-to-End Process Mapping / 端到端流程映射

### Procure-to-Pay (P2P) / 核心流程1：采购到付款

```
Flow / 流程: Requisition → PO → Goods Receipt → Invoice → Payment
             采购申请 → 采购订单 → 收货 → 发票校验 → 付款
```

**SAP System Behavior / SAP 系统行为:**
- PO created → Goods Receipt → automatic GRIR account posting / 采购订单 → 收货 → 自动过账到GRIR科目
- Invoice verification → automatic financial posting (MM-FI integration) / 发票校验 → 自动生成财务凭证（MM-FI集成）
- GRIR reconciliation and clearing at period-end / 期末GRIR对账与清账

**Confirmed from Meetings / 会议确认:**
- Supplier master data being migrated with validated tax codes / 供应商主数据正在迁移，已验证税码
- YCBE chart of accounts sent for validation / YCBE科目表已发送验证
- ~400 vendor + 300 customer tax codes being standardized to active list only / ~400个供应商+300个客户税码正在标准化为仅保留活跃税码

### Quote-to-Cash (Q2C) / 核心流程2：报价到收款

```
Flow / 流程: Inquiry → Quotation → Sales Order → Delivery → Billing → Payment
             询价 → 报价 → 销售订单 → 发货 → 开票 → 收款
```

**Confirmed from Meetings / 会议确认:**
- Spare parts sales: standard flow / 备件销售：标准流程
- Service orders: Issue #1 — NOT currently in any system / 服务订单：问题#1 — 当前不在任何系统中
- BDK (Third-Party) sales: tested with item category CB2 / 第三方销售（BDK）：已测试，项目类别CB2
- Credit management: new process to be established in SAP / 信用管理：将在SAP中建立新流程

### Assembly-to-Stock / 核心流程3：组装到库存

```
Flow / 流程: Customer Order → BOM Explosion → Start Assembly → Complete → Stock Receipt
             客户订单 → BOM展开 → 开始组装 → 完成 → 成品入库
```

**SAP System Behavior / SAP 系统行为:**
- "Start of Manufacturing" → component consumption from stock / "开始制造" → 组件从库存消耗
- "End of Manufacturing" → finished assembly into stock / "结束制造" → 成品组装件入库
- Financial posting via Material Movement automatically / 通过物料移动自动生成财务凭证

### Finance Close & Reporting / 核心流程4：财务结账与报告

**Key Dates / 关键日期:**
- Accounting periods / 会计期间: March to February (NOT calendar year) / 3月至次年2月（非自然年）
- Year-end close / 年末结账: End of February / 2月底
- Monthly close / 月度结账: Month-end / 月底

---

## Detailed Process Flows with Roles / 详细流程与角色

> **Legend / 图例:**
> - 🟦 **Blue / 蓝色** = SAP System Internal / SAP系统内执行
> - 🟧 **Orange / 橙色** = External (manual / physical) / 系统外执行（手工/物理操作）
> - Flowchart images stored in `flowcharts/` folder / 流程图图片保存在 `flowcharts/` 文件夹
>
> 流程图文件 (SVG): `flowcharts/flow_p2p.svg`, `flowcharts/flow_q2c.svg`, `flowcharts/flow_assembly.svg`, `flowcharts/flow_intercompany.svg`, `flowcharts/flow_bdk.svg`, `flowcharts/flow_fi_close.svg`

### Procure-to-Pay / 流程1：采购到付款

**Flowchart: `flowcharts/flow_p2p.svg`**

| Step / 步骤 | Description / 说明 | System / 系统 | Role / 角色 | SAP? |
|------------|-------------------|--------------|-------------|------|
| 1 | Identify Need / 识别采购需求 | Mafact / Manual | Buyer / 采购员 — Pascal Lust | ❌ External |
| 2 | Create Purchase Requisition / 创建采购申请 | SAP MM | Buyer / 采购员 | ✅ SAP |
| 3 | Create Purchase Order / 创建采购订单 (ME21N) | SAP MM | Buyer / 采购员 — Pascal Lust | ✅ SAP |
| 4 | Send PO to Supplier / 发送PO给供应商 | Email / Portal | Buyer / 采购员 | ❌ External |
| 5 | Supplier Delivers / 供应商发货 | Physical | Supplier / 供应商 | ❌ External |
| 6 | Goods Receipt / 收货 (MIGO) | SAP MM | Storekeeper / 仓管员 — Michael Scohy | ✅ SAP |
| 7 | Supplier Invoice Received / 收到供应商发票 | Mail / Email | Buyer / 采购员 — Pascal Lust | ❌ External |
| 8 | Invoice Verification / 发票校验 (MIRO) | SAP MM-FI | Buyer/AP Clerk / 采购/应付会计 | ✅ SAP |
| 9 | Payment / 付款 (F-53) | SAP FI | AP Clerk / 应付会计 | ✅ SAP |

**Key system behaviors / 关键系统行为:**
- **GRIR auto-posting**: Goods Receipt automatically posts to GRIR account / 收货自动过账到GRIR科目
- **Auto FI integration**: MM movement → automatic FI document / 物料移动 → 自动财务凭证
- **Subcontracting**: Special process (see Issue #5) — requires PO with subcontracting item category + BOM

### Quote-to-Cash / 流程2：报价到收款

**Flowchart: `flowcharts/flow_q2c.svg`**

| Step / 步骤 | Description / 说明 | System / 系统 | Role / 角色 | SAP? |
|------------|-------------------|--------------|-------------|------|
| 1 | Customer Inquiry / 客户询价 | Email/Phone | Customer / 客户 | ❌ External |
| 2 | Quotation / 报价 (VA21) | SAP SD | Sales / 销售 — Nicolas Blommaert | ✅ SAP |
| 3 | Sales Order / 销售订单 (VA01) | SAP SD | Sales / 销售 — Sylvie Ledoux | ✅ SAP |
| 4 | Credit Check / 信用检查 | SAP SD (Auto) | System / 系统自动 | ✅ SAP |
| 5 | Order Confirmation to Customer / 发送订单确认 | Email | Sales / 销售 | ❌ External |
| 6 | Picking / 捡配 | SAP WM/MM | Storekeeper / 仓管员 — Michael Scohy | ✅ SAP |
| 7 | Delivery / 发货 (VL01N) | SAP SD | Storekeeper / 仓管员 | ✅ SAP |
| 8 | Pack & Ship / 包装发运 | Physical | Storekeeper + Freight Forwarder / 仓管+货运代理 | ❌ External |
| 9 | Goods Issue Auto-Posting / 自动过账发货 (VL02N) | SAP SD-MM-FI | System Auto / 系统自动 | ✅ SAP |
| 10 | Customer Invoice / 客户开票 (VF01) | SAP SD-FI | AR Clerk / 应收会计 | ✅ SAP |
| 11 | Send Invoice via PEPPOL/Email / 发送发票 | PEPPOL/Email | AR Clerk / 应收会计 | ❌ External |
| 12 | Payment Receipt / 收款 (F-28) | SAP FI | AR Clerk / 应收会计 | ✅ SAP |

**Service Orders**: Currently NOT in any system — see Issue #1 for decision / 服务订单当前不在任何系统中 — 决策见 Issue #1

### Assembly-to-Stock / 流程3：组装到库存

**Flowchart: `flowcharts/flow_assembly.svg`**

| Step / 步骤 | Description / 说明 | System / 系统 | Role / 角色 | SAP? |
|------------|-------------------|--------------|-------------|------|
| 1 | Customer Order Received / 收到客户订单 | SAP/Email | Sales / 销售 | ❌ External |
| 2 | Check Component Stock / 检查组件库存 | SAP MM | Storekeeper / 仓管员 — Michael Scohy | ✅ SAP |
| 3 | Start Manufacturing / 开始制造 — reserve components / 预留组件 | SAP PP | System Auto / 系统自动 | ✅ SAP |
| 4 | Physical Assembly / 现场组装 | Physical | Workshop Worker / 车间工人 | ❌ External |
| 5 | End Manufacturing / 结束制造 — confirm completion / 确认完成 | SAP PP | Storekeeper / 仓管员 — Michael Scohy | ✅ SAP |
| 6 | Finished Goods Receipt / 成品入库 (auto component removal + FG add) | SAP PP-MM-FI | System Auto / 系统自动 | ✅ SAP |

**Process notes / 流程说明:**
- CBF is assembly-only; NO raw materials production / CBF仅有组装，无原材料生产
- BOM defines component quantities for the assembly / BOM定义组装所需组件数量
- No detailed routing, work centers, or capacity planning / 无详细工艺路线、工作中心或产能规划
- Issue #6: Decision needed on WIP tracking requirement / Issue #6：是否需要追踪在制品价值

### BDK Third-Party Sales / 流程4：第三方销售 (BDK/CB2)

**Flowchart: `flowcharts/flow_bdk.svg`**

| Step / 步骤 | Description / 说明 | System / 系统 | Role / 角色 | SAP? |
|------------|-------------------|--------------|-------------|------|
| 1 | Sales Order with Item Category CB2 / 创建销售订单 (项目类别CB2) (VA01) | SAP SD | Sales / 销售 — Sylvie Ledoux | ✅ SAP |
| 2 | Purchase Requisition Auto-Created / 自动创建采购申请 | SAP MM | System Auto / 系统自动 | ✅ SAP |
| 3 | Purchase Order to Vendor / 向供应商创建采购订单 (ME21N) | SAP MM | Buyer / 采购员 — Pascal Lust | ✅ SAP |
| 4 | Vendor Ships Directly to Customer / 供应商直发客户 | Physical | Vendor / 供应商 | ❌ External |
| 5 | Supplier Invoice / 供应商发票校验 (MIRO) | SAP MM-FI | Buyer / 采购员 — Pascal Lust | ✅ SAP |
| 6 | Customer Invoice / 客户开票 (VF01) | SAP SD-FI | AR Clerk / 应收会计 | ✅ SAP |

**Critical rule / 关键规则:**
> ⚠️ Customer invoice is **BLOCKED** until supplier invoice is posted. Billing quantity = supplier invoice quantity.
> ⚠️ 客户开票在供应商发票过账之前**被阻止**。开票数量 = 供应商发票数量。
> PO item is NOT relevant for Goods Receipt / PO项目不需要收货。

### Intercompany Procurement (CBF ↔ CBW) / 流程5：集团内部采购

**Flowchart: `flowcharts/flow_intercompany.svg`**

| Step / 步骤 | Description / 说明 | System / 系统 | Role / 角色 | SAP? |
|------------|-------------------|--------------|-------------|------|
| 1 | CBF Creates PO to CBW / CBF向CBW创建采购订单 | SAP MM | Buyer CBF — Pascal Lust | ✅ SAP |
| 2 | CBW Delivers Goods / CBW发货 | Physical | CBW Warehouse | ❌ External |
| 3 | CBF Goods Receipt / CBF收货 | SAP MM | Storekeeper CBF — Michael Scohy | ✅ SAP |
| 4 | CBW Invoices CBF / CBW向CBF开票 | SAP FI | CBW AR / CBW应收会计 | ✅ SAP |
| 5 | CBF AP Processing / CBF应付处理 | SAP FI | AP Clerk CBF / CBF应付会计 | ✅ SAP |
| 6 | Intercompany Settlement / 集团内部结算 | SAP FI (Auto) | System Auto / 系统自动 | ✅ SAP |

### Month-End Close / 流程6：月末结账

**Flowchart: `flowcharts/flow_fi_close.svg`**

| Step / 步骤 | Description / 说明 | System / 系统 | Role / 角色 | SAP? |
|------------|-------------------|--------------|-------------|------|
| 1 | Physical Inventory / 实物盘点 | SAP/Physical | Storekeeper — Michael Scohy | ✅ SAP |
| 2 | GRIR Clearing / GRIR清账 (F.13) | SAP FI | FI / 财务 — Vincent Delsaute | ✅ SAP |
| 3 | AP Payment Run / 应付付款运行 | SAP FI | AP Clerk / 应付会计 | ✅ SAP |
| 4 | AR Dunning Run / 应收催款运行 | SAP FI | AR Clerk / 应收会计 | ✅ SAP |
| 5 | Foreign Currency Valuation / 外汇评估 (F.08) | SAP FI | FI / 财务 — Vincent Delsaute | ✅ SAP |
| 6 | Asset Depreciation Run / 资产折旧运行 (AFAB) | SAP FI-AA | System Auto / 系统自动 | ✅ SAP |
| 7 | Cost Settlement / 成本结算 | SAP CO | CO Accountant / 成本会计 | ✅ SAP |
| 8 | VAT Return Preparation / 增值税申报准备 | SAP FI | FI / 财务 — Vincent Delsaute | ✅ SAP |
| 9 | DRC Government Report / 政府申报报表 (DRC) | SAP DRC | System Auto / 系统自动 | ✅ SAP |
| 10 | GL Period Close / 总账期间关闭 | SAP FI | FI / 财务 — Vincent Delsaute | ✅ SAP |

**Key dates / 关键日期:**
- Accounting period / 会计期间: March to February (NOT Jan-Dec) / 3月至次年2月
- Year-end close / 年末结账: End of February / 2月底
- Issue #3: Belgian VAT vs SAP standard differences affect steps 8-9 / 比利时增值税与SAP标准差异影响步骤8-9

---

# Part IV: Open Issues & Questions / 第四部分：未明确事项与问题

> The following issues could not be determined from available documentation. Each is presented with context and a recommended approach.
>
> 以下事项无法从现有文档中确定。每个事项附有背景说明和建议方案。

---

## Issue #1: Service Order Management / 问题#1：服务订单管理

**Context / 背景:**

From the CBF On-site Consulting Report and SD Research:
根据 CBF 现场咨询报告及 SD 调研：

> "They recorded spare parts order, not record the service order. Service order — Not in Mafact. Cost book will manually book in the Winbooks."

Service orders at CBF are currently **invisible in any ERP system**. Only service costs are manually booked in Winbooks. The May 13 meeting also confirmed some services are procured without a PO.
CBF 的服务订单目前**在任何 ERP 系统中均无记录**。仅服务成本手工录入 Winbooks。5月13日会议也确认部分服务无采购订单。

**Questions / 问题:**

1. Will service orders be managed in SAP S/4HANA Cloud? / 服务订单是否纳入 SAP S/4HANA Cloud 管理？
2. What is the typical service process (customer request → dispatch → completion → billing)? / 典型服务流程是什么（客户请求 → 派工 → 完成 → 开票）？
3. Are there service contracts or warranty management requirements? / 是否存在服务合同或保修管理需求？
4. How should service costs (employee time, materials used) be tracked? / 服务成本（员工工时、使用物料）如何追踪？

**Recommended Approach / 建议方案:**

- **Option A (Recommended / 推荐)**: Include Service Order Management in SAP (Scope Item J58 with service item categories). This provides end-to-end visibility and proper cost collection.
  **方案A（推荐）**：将服务订单管理纳入 SAP，实现端到端可视化与成本归集。

- **Option B (Minimal)**: Continue manual tracking for services; use SAP only for the invoice (proforma via VF01, as mentioned in Apr 30 meeting).
  **方案B（最小化）**：继续手工管理服务，仅使用 SAP 开具发票（如4月30日会议提到的通过 VF01 生成形式发票）。

---

## Issue #2: Service Procurement — PO Requirement / 问题#2：服务采购是否需要采购订单

**Context / 背景:**

From MM Research:
来自 MM 调研：

> "Some services require a purchase order. For example, no purchase order is required for subcontracting on site."

Some service procurements apparently do NOT go through a PO, while others do. There is no documented rule distinguishing them.
部分服务采购显然不需要采购订单，而其他则需要。尚无书面规则区分二者。

**Questions / 问题:**

1. What types of services require a PO vs. those that don't? What is the criterion (amount, type, vendor)?
   哪些服务需要采购订单，哪些不需要？判定标准是什么（金额、类型、供应商）？

2. How are non-PO service invoices currently handled? Approved by whom?
   无采购订单的服务发票目前如何处理？由谁批准？

3. Will SAP require all services to go through POs, or is departmental approval + non-PO invoice sufficient?
   SAP 是否要求所有服务通过采购订单处理，还是部门审批 + 无PO发票即可？

**Recommended Approach / 建议方案:**

- **Recommended / 推荐**: Move all service procurement to SAP PO process with appropriate approval workflows. This ensures all service costs are captured, proper budget control, and an audit trail for Belgian tax authorities.
  **建议将所有服务采购纳入 SAP 采购订单流程**，配置相应的审批工作流，确保所有服务成本被捕获、预算可控、满足比利时税务机关的审计要求。

- **Alternative / 备选**: Configure non-PO invoice process for low-value services with defined approval limits.
  为低值服务配置无PO发票流程，设定审批限额。

---

## Issue #3: Belgian VAT Logic vs. SAP Standard / 问题#3：比利时增值税逻辑与 SAP 标准差异

**Context / 背景:**

The May 21 meeting was dedicated to this topic. Key differences identified:
5月21日会议专门讨论此议题。已识别的关键差异：

| Aspect / 方面 | Belgian Local Requirement / 比利时本地要求 | SAP Standard / SAP标准 |
|---------------|--------------------------------------------|----------------------|
| **Reverse Charge / 逆向征收** | Output VAT + Input VAT posted simultaneously in single entry, needing balance sheet account mapping / 销项税+进项税同笔记账，需要资产负债表科目映射 | VK102/VK103 standard procedures |
| **Tax Code Determination / 税码确定** | Determined by departure + destination country / 根据发货国+目的国确定 | Supported via VK102/VK103 / 通过VK102/VK103支持 |
| **Tax Audit Traceability / 税务审计可追溯性** | Need fast retrieval of original invoices via GL accounts / 需要通过总账科目快速检索原始发票 | OB40 auto account determination / OB40自动科目确定 |
| **DRC Reporting / 政府申报** | Government Declare report format needed / 需要政府申报报表格式 | DRC module standard + potential customization / DRC模块标准+可能的定制 |

**Questions / 问题:**

1. Have the Belgian YCBE chart of accounts and Winbooks report templates been reconciled with SAP standard DRC capabilities?
   YCBE科目表和Winbooks报表模板是否已与SAP标准DRC功能进行比对？（5月21日会议状态："比较 SAP 和 Winbooks 生成的税报告一致性"）

2. The customer/vendor master currently has ~700 tax codes (400 vendor + 300 customer). Has the cleaned active list been provided? (Assigned to @Vincent in May 13 meeting)
   客户/供应商主数据现有约700个税码。已清理的活跃税码列表是否已提供？（5月13日会议分配给@Vincent）

3. Has the region-classified customer master data list (local Belgium, intra-EU, non-EU) been submitted? (Assigned to @Vincent in May 21 meeting)
   按地区分类的客户主数据清单（比利时本地、欧盟内部、欧盟外部）是否已提交？（5月21日会议分配给@Vincent）

**Recommended Approach / 建议方案:**

- **建议设置专门的并行测试环境进行增值税验证**，比对 SAP 生成的税务报表与 Winbooks 输出结果。关键验证场景：
  1. Domestic sale (Belgium → Belgium customer) / 国内销售（比利时→比利时客户）
  2. Intra-EU sale (Belgium → Germany/France) — reverse charge / 欧盟内部销售（比利时→德国/法国）— 逆向征收
  3. Extra-EU sale (Belgium → non-EU customer) — exempt with proof / 欧盟外部销售（比利时→非欧盟客户）— 凭证明免税
  4. Domestic purchase (Belgium supplier) / 国内采购（比利时供应商）
  5. Intra-EU purchase — reverse charge / 欧盟内部采购 — 逆向征收
  6. Import from non-EU / 从非欧盟进口

- **关键前置条件**：清理后的税码列表和按地区分类的客户主数据是此测试的前提。

---

## Issue #4: Financial Module Go-Live Strategy / 问题#4：财务模块上线策略

**Context / 背景:**

The Apr 17 meeting discussed the conflict between CBF's desire to "go-live with business modules first, postpone financial modules" and the integrated nature of SAP. Conclusion:
4月17日会议讨论了CBF"优先上线业务模块、推迟财务模块"的需求与 SAP 业财一体化本质之间的冲突。结论：

> "BOS consultants clearly stated: as long as purchase orders, sales orders, inbound/outbound shipments, and invoice verification exist, SAP will inevitably generate financial vouchers. Financial configurations (G/L accounts, customer/vendor master) cannot be avoided."
>
> "BOS顾问明确指出：只要存在采购订单、销售订单、出入库、发票校验等操作，SAP 必然会生成财务凭证。会计科目、客户/供应商主数据等财务配置无法避免。"

**Questions / 问题:**

1. Is the final decision to go-live with full business-financial integration, or is a parallel-operation approach with Mafact+Winbooks still being considered for a transition period?
   最终决定是业财一体化上线，还是在过渡期仍考虑与Mafact+Winbooks并行运行？

2. If parallel operation: what is the account mapping strategy between SAP YCBE and Winbooks chart of accounts? Has this been validated?
   如果并行运行：SAP YCBE 与 Winbooks 科目表的映射策略是什么？是否已验证？

3. What is the "no-movement business day" (business freeze date) for physical inventory count and data migration?
   用于实地盘点和数据迁移的"无业务移动日"（业务冻结日期）是哪天？

**Recommended Approach / 建议方案:**

- **Recommend full integration go-live / 建议采用完全集成上线**: Based on technical constraints raised in the Apr 17 meeting, full integration go-live is the only sustainable approach. Parallel operation adds complexity (dual data entry, reconciliation) without long-term benefit.
  基于4月17日会议提出的技术限制，完全集成上线是唯一可持续的方案。并行运行增加复杂性（双重数据录入、对账）而无长期收益。

- **Go-Live Sequence / 上线顺序**:
  1. Complete system configuration (target: ~end May 2026) / 完成系统配置（目标：2026年5月底）
  2. Master data migration (20-30 sample materials first, per May 13) / 主数据迁移（先试迁20-30个物料）
  3. Internal testing (18 scenarios: 8 MM + 10 SD) / 内部测试（18个场景：8个MM + 10个SD）
  4. UAT — July 2026 / 用户验收测试 — 2026年7月
  5. Go-live with inventory freeze / 库存冻结后上线

- **Key Success Factor / 关键成功因素**: Financial data consistency must be verified — SAP inventory value must match financial book value before go-live, with full discrepancy analysis completed.
  财务数据一致性必须验证 — SAP库存价值须与财务账面价值一致，差异分析完成后方可上线。

---

## Issue #5: Subcontracting Process / 问题#5：委外加工流程

**Context / 背景:**

Meeting May 13 identified this special process:
5月13日会议识别到此特殊流程：

> "Goods are delivered from Vendor A to Vendor B for processing, and Vendor B delivers finished goods directly to customers. The cost of finished goods (e.g., Material No.2810371) consists of raw material procurement cost from Vendor A and subcontracting processing fee charged by Vendor B."
>
> "物料从供应商A送到供应商B加工，供应商B将成品直接发运给客户。成品（如物料号2810371）成本由供应商A的原材料采购成本和供应商B的委外加工费构成。"

**Questions / 问题:**

1. Who bears the inventory risk during Vendor B's processing? Does title transfer?
   供应商B加工期间的库存风险由谁承担？所有权是否转移？

2. Are there multiple subcontractors involved simultaneously?
   是否同时涉及多个委外加工商？

3. What is the typical volume? How many such relationships exist?
   典型业务量是多少？有多少个这样的委外关系？

4. Is the finished product always identifiable with a unique material number (like 2810371)?
   成品是否始终以唯一物料号（如2810371）标识？

5. Does Vendor B ever add their own materials (not just CBF-supplied parts)?
   供应商B是否有时会添加自己的材料（不仅是CBF提供的零件）？

**Recommended Approach / 建议方案:**

- **Recommend using SAP standard Subcontracting process / 建议启用SAP标准委外加工流程**:
  - Create a "Subcontracting" PO type with special procurement type / 创建"委外加工"采购订单类型，特殊采购类型
  - Material provided to vendor tracked in SAP stock of material provided to vendor / 提供给供应商的物料通过SAP"供应商库存"跟踪
  - Component consumption managed via BOM / 通过BOM管理组件消耗
  - Settlement: raw material cost (from CBF warehouse) + processing fee (Vendor B invoice) / 结算：原材料成本（CBF仓库发出）+ 加工费（供应商B发票）

- **Prerequisite / 前置条件**: Sample data from Mr. Yu & Vincent per May 13 action items.
  需俞经理和Vincent提供示例数据（5月13日会议待办事项）。

---

## Issue #6: Assembly Process in SAP / 问题#6：SAP中的组装流程

**Context / 背景:**

PP Research confirms:
PP调研确认：

> "No schedule. We assemble the parts as soon as we have the components available."
> "There is just a 'start of manufacturing' in MAFACT and an 'end of manufacturing' operation."
> "The ERP should function like MAFACT."

This is an extremely basic assembly process — BOM → reserve parts → assemble → finished goods posting. There is NO:
这是一个极为简单的组装流程 — BOM → 预留零件 → 组装 → 成品过账。且不存在：
- Production planning or scheduling / 生产计划或排程
- Work center / routing management / 工作中心/工艺路线管理
- Capacity planning / 产能规划
- Semi-finished products / 半成品
- By-product / co-product management / 联产品/副产品管理

**Questions / 问题:**

1. Is the current "start manufacturing / end manufacturing" in Mafact sufficient, or are there requirements for tracking Work In Progress (WIP) value?
   当前 Mafact 的"开始制造/结束制造"是否已足够，还是有追踪在制品（WIP）价值的需求？

2. Are certificates of origin / compliance required with the finished product?
   成品是否需要原产地证明/合规证书？

3. Is serial number tracking required for valve blocks or other critical parts?
   阀块或其他关键零件是否需要序列号追踪？

**Recommended Approach / 建议方案:**

- **Recommend the simplest assembly approach / 建议采用最简单的组装方案**: Use SAP basic production order processing with minimal configuration:
  使用 SAP 基础生产订单处理，最小化配置：
  - Material type FERT (Finished Product) with assembly BOM / 物料类型 FERT（成品）+ 组装BOM
  - Work center as a single virtual center (no detailed capacity) / 工作中心设为单一虚拟中心（无需详细产能）
  - Production order with "start" and "complete" confirmation / 生产订单的"开始"和"完成"确认
  - No detailed scheduling or capacity leveling / 无需详细排程或产能平衡

- **Option**: If WIP tracking is not required, consider Value-Added Assembly (using MM-only movements with BOM explosion in sales order). This avoids the complexity of full PP while tracking component consumption.
  **备选方案**：如果不需要追踪WIP价值，可考虑增值组装方案（在销售订单中通过BOM展开进行物料移动，仅使用MM模块），避免完整PP模块的复杂性，同时追踪组件消耗。

---

## Issue #7: Withholding Tax / 问题#7：预扣税

**Context / 背景:**

From FICO Research:
来自 FICO 调研：

> "Withholding tax rate: 30%. Trigger: payment at receipt. Calculation base: not specified (n#a in survey). External report to tax offices."
>
> "预扣税率：30%。触发条件：收款时付款。计算基数：未明确（调研回复n#a）。需向税务机关提交外部报告。"

**Questions / 问题:**

1. Is withholding tax applicable to ALL foreign suppliers or only specific countries/types?
   预扣税适用于所有外国供应商还是仅限特定国家/类型？

2. Are there double tax treaty considerations (Belgium has treaties with many countries)?
   是否需要考虑双重征税协定（比利时与多国有税收协定）？

3. How is the external report to tax offices currently handled?
   目前如何向税务机关提交外部报告？

**Recommended Approach / 建议方案:**

- **Configure SAP standard withholding tax function / 配置SAP标准预扣税功能**:
  - Withholding tax type: Payment-based (triggered at payment, not invoice) / 预扣税类型：基于付款（付款时触发，非发票时触发）
  - Rate: 30% (confirmed from research) / 税率：30%（调研确认）
  - Base: To be confirmed with CBF finance — calculation base (excluding VAT vs including VAT) was not specified in research / 基数：需与CBF财务确认 — 调研中未明确计算基数（是否含增值税）
  - Reporting: Configure SAP withholding tax certificate / 报告：配置SAP预扣税凭证

- **关键点**：需要区分适用预扣税的供应商类别，并考虑税收协定的减免规则。

---

## Issue #8: QM Module Scope — Full QM or Basic MM Inspection / 问题#8：QM模块范围 — 完整QM还是仅MM基础检验

**Context / 背景:**

From QM Research:
来自 QM 调研：

> "No production at CBF. Only the assembly of parts."
> "No quality control report."
> "No system. If there is a problem, we ask for information verbally."
> "What are the requirements and expectations for the ERP system? — No idea."

CBF's quality operation is minimal: 100% incoming inspection (visual/drawing check), non-conformance reports to suppliers, and annual supplier evaluation. There is NO production QC, NO batch tracking, NO quality certificates management, and NO existing QM system at all.
CBF 的质量操作极为基础：100%来料检验（目视/按图纸核对）、向供应商发不符合报告、年度供应商评估。完全没有生产过程质检、批次追踪、质量证书管理，也没有现有质量系统。

**Questions / 问题:**

1. Is the full QM module needed, or is basic quality info in MM Goods Receipt (e.g., inspection lot, usage decision) sufficient?
   是否需要完整 QM 模块，还是 MM 收货中的基础质检功能（如检验批、使用决策）已足够？

2. Are there future quality requirements (certificates, batch traceability, PPAP) that the system must accommodate?
   是否有未来必须支持的质量需求（证书、批次追溯、PPAP）？

3. Who will be the key user for quality processes in SAP?
   谁将是 SAP 中质量流程的关键用户？

**Impact on Configuration / 对配置的影响:**

This decision determines whether QM-specific configurations are needed (inspection plans, quality info records, certificates) or only basic MM inspection functionality.
此决策决定是否需要 QM 特定配置（检验计划、质量信息记录、证书），还是仅需 MM 基础检验功能。

**Recommended Approach / 建议方案:**

- **建议**: Start with basic quality inspection in MM (inspection lot in Goods Receipt). This covers CBF's current needs without QM module overhead. The full QM module can be activated later if certificate management or batch traceability becomes required.
  **建议从 MM 基础收货检验开始**，覆盖 CBF 当前需求，避免 QM 模块的额外复杂度。未来如有证书管理或批次追溯需求，再启用完整 QM。

---

## Issue #9: Fixed Asset Data Migration / 问题#9：固定资产数据迁移

**Context / 背景:**

From FICO Research:
来自 FICO 调研：

> "Do you manage fixed asset in system or in excel? — In excel for the details and then at the end of each month the bookings are done manually in the system."
> "How many fixed asset master data? — We are using 2 excel files: 1 for the depreciation calculation, 2 for the details of the fixed assets."
> "Does each fixed asset have unique asset number? — No."
> "Depreciation method: Straight-line."

Fixed assets are managed entirely in Excel (2 files: depreciation calc + asset details), with no unique asset numbers. Manual monthly postings to Winbooks. The proposed SAP Asset Accounting scope requires clean asset master data with unique numbers, historical cost, accumulated depreciation, and capitalization dates.
固定资产完全在 Excel 中管理（2个文件：折旧计算 + 资产明细），无唯一资产编号，每月手工过账到 Winbooks。SAP 固定资产核算要求有带唯一编号、历史成本、累计折旧和资本化日期的清洁资产主数据。

**Questions / 问题:**

1. How many fixed asset records need to be migrated? What is the total value?
   需要迁移多少条固定资产记录？总价值多少？

2. What asset classes/categories exist (buildings, machinery, furniture, vehicles, etc.)?
   存在哪些资产类别（建筑物、机器设备、家具、车辆等）？

3. For assets without unique numbers: will new asset numbers be created in SAP, or a mapping rule defined?
   对于没有唯一编号的资产：是在 SAP 中创建新资产编号，还是定义映射规则？

4. Are there any assets under construction (AUC/CIP) that need separate handling?
   是否存在需要单独处理的在建工程资产？

5. What is the capitalization threshold for fixed assets vs. expense items?
   固定资产与费用项目的资本化阈值是多少？

**Impact on Configuration / 对配置的影响:**

Asset Accounting configuration (depreciation keys, asset classes, screen layout rules) depends on the asset data. Data migration from Excel to SAP requires significant preparation.
资产会计配置（折旧码、资产类别、屏幕格式规则）依赖于资产数据。从 Excel 到 SAP 的数据迁移需要大量准备工作。

**Recommended Approach / 建议方案:**

- **建议尽早启动固定资产数据清理**：
  - Assign temporary unique numbers to all existing assets in Excel / 在 Excel 中为所有现有资产分配临时唯一编号
  - Define asset classes and corresponding depreciation rules / 定义资产类别及对应折旧规则
  - Plan migration in a separate phase if asset data is complex / 如果资产数据复杂，可单独作为一阶段迁移

---

## Issue #10: Material Numbering Strategy / 问题#10：物料编码策略

**Context / 背景:**

From Apr 17 meeting:
来自4月17日会议：

> "CBF currently plans to use the CBW numbering system, while the CBS system adopts a different numbering system. It is recommended to follow the principle of 'one material, one number', and it is preferred to directly use the CBW number as the main number or establish a unified number mapping rule."
>
> "CBF 计划使用 CBW 的编码体系，而 SCB 系统使用不同的编码体系。建议遵循'一物一码'原则，优先推荐直接使用 CBW 编号为主编号，或建立统一编号映射规则。"

The May 30 meeting further confirmed material pricing should follow CBF's original calculation standards, but the numbering decision remains open.
4月30日会议进一步确认材料定价沿用 CBF 原有计算标准，但编码决策仍未确定。

CBF currently uses **7-digit part numbers** in Mafact. CBW uses a different system. The 20-30 sample materials for pilot migration need numbering rules before migration can proceed.
CBF 目前在 Mafact 中使用 **7 位零件号**。CBW 使用不同的编码体系。试迁的 20-30 个样品物料需要在迁移前确定编码规则。

**Questions / 问题:**

1. Has the final numbering decision been made: adopt CBW numbers, keep CBF 7-digit numbers, or create a new unified standard?
   最终编码决策是否已做出：采用 CBW 编号、保留 CBF 7位编号、还是创建新的统一标准？

2. For CBF-specific materials that don't exist in CBW: who assigns the number?
   对于 CBW 不存在的 CBF 特有物料：由谁分配编号？

3. What is the material creation approval workflow going forward?
   未来的物料创建审批流程是什么？

4. How to handle the CBF parts (~1000 active + historical) that already have 7-digit numbers in Mafact?
   如何处理 Mafact 中已有 7 位编号的 CBF 物料（约1000个活跃 + 历史物料）？

**Impact on Configuration / 对配置的影响:**

The numbering strategy affects material master configuration (number range, material type settings) and data migration rules. This decision is a prerequisite for full material master migration.
编码策略影响物料主数据配置（号码段、物料类型设置）和数据迁移规则。此决策是物料主数据全面迁移的前提条件。

**Recommended Approach / 建议方案:**

- **建议采用方案**: Adopt a unified group-wide numbering system aligned with CBW. For CBF-only materials, assign numbers from a reserved range within the CBW system.
  **建议采用与 CBW 统一的集团编码体系**。对于 CBF 特有物料，在 CBW 系统预留号段内分配。

- **Alternate / 备选**: Keep existing CBF 7-digit numbers, map to CBW via cross-reference table for group reporting. Pragmatic for legacy data but adds maintenance overhead.
  **保留 CBF 现有 7 位编号**，通过交叉引用表映射到 CBW 编号用于集团报表。对历史数据更务实，但增加维护成本。

- **前置依赖**: This decision must be made before material master migration can proceed beyond the 20-30 sample items.
  此决策必须在物料主数据全面迁移（超过 20-30 个样品）之前做出。

---

# Part V: Implementation Timeline / 第五部分：实施时间表

## Go-Live Plan Summary / 上线计划摘要

| Phase / 阶段 | Activity / 活动 | Estimated Duration / 预计时长 | Status / 状态 |
|-------------|-----------------|-------------------------------|--------------|
| 1 | Parallel System Activation / 并线系统激活 | 3 working days / 3个工作日 | ✅ Completed / 已完成 |
| 2 | System Configuration (MM/SD/FI) / 系统配置 | ~2 weeks (by ~May 26) / 约2周 | 🔄 In progress / 进行中 (MM 80%, SD near complete, FI complete) |
| 3 | Data Preparation & Migration / 数据准备与迁移 | Prep: 2 wks, Migration: 1 wk / 准备2周，迁移1周 | 📋 Pending — sample data (20-30 materials) first / 待办 — 先试迁20-30个物料 |
| 4 | Internal Testing (18 scenarios) / 内部测试（18个场景） | ~1 week / 约1周 | 📋 Pending / 待办 |
| 5 | User Training + UAT / 用户培训与UAT | July 2026 / 2026年7月 | 📋 Planned / 计划中 |
| 6 | Go-Live / 上线 | Target: ~Q3 2026 / 目标约2026年Q3 | 📋 Planned / 计划中 |

**Test Scenarios Defined (May 13) / 已定义测试场景:**
- **MM (8 scenarios / 8个场景)**: Purchase requisition, PO, GR, invoice verification, stock transfer, physical inventory etc. / 采购申请、采购订单、收货、发票校验、库存转移、实物盘点等
- **SD (10 scenarios / 10个场景)**: Sales order, delivery, billing, credit memo, debit memo, returns, BDK third-party etc. / 销售订单、发货、开票、贷项凭证、借项凭证、退货、BDK第三方销售等

## Configuration Status (as of May 13) / 配置状态（截至5月13日）

Source: CBF System Configuration Status Introduce PPTX (slides 3-4) + May 13 meeting / 来源：CBF系统配置状态介绍PPTX（第3-4页）+ 5月13日会议纪要

| Module / 模块 | Completed / 已完成 | Pending / 待完成 | % |
|--------------|-------------------|-----------------|---|
| Organizational Structure / 组织结构 | Customer org chart setup / 客户组织结构图建立 | — | 100% |
| MM — Basic Settings / MM基础设置 | Org structure, BP, material, warehouse config; basic MM module function test passed / 组织结构、业务伙伴、物料、仓库配置；基础MM功能测试通过 | **Subcontracting config / 委外加工配置** (pending sample data); **Return back config / 退货流程配置** | ~80% |
| MM — Material Master Data / 物料主数据 | Template ready / 模板已准备好 | **No data loaded yet / 尚无数据加载** (template ok, no data) | ~10% |
| SD — Sales Structure / SD销售结构 | Sales enterprise structure 100% / 销售企业结构100%完成 | Pending discrepancies to be verified in testing / 待差异在测试中验证 | ~100% |
| FI — Full config / FI完整配置 | COA, company code, cost elements, cost/profit centers, material-finance integration / 科目表、公司代码、成本要素、成本/利润中心、物料-财务集成 | — | 100% |

> **Note / 说明**: The MM pending items (Subcontracting, Return Back config) are standard configuration tasks awaiting business data and confirmation. See Issue #5 for subcontracting details.
> **说明**：MM 待完成项（委外加工、退货流程配置）为标准配置任务，正在等待业务数据和确认。委外加工详见 Issue #5。

---

# Part VI: Appendices / 第六部分：附录

## A: Document References / 文档引用

| Doc / 文档 | Date / 日期 | Key Content / 主要内容 |
|------------|-------------|----------------------|
| Meeting Minutes — Apr 17 / 会议纪要4月17日 | 2026-04-17 | Go-Live strategy, business-first vs integration conflict / 上线策略、业务优先与集成冲突 |
| Minutes of Meeting — Apr 30 / 会议纪要4月30日 | 2026-04-30 | 5-phase roadmap, master data strategy, YCBE export / 五阶段路线图、主数据策略、YCBE导出 |
| Minutes of Meeting — May 13 / 会议纪要5月13日 | 2026-05-13 | Config status, migration strategy, subcontracting / 配置状态、迁移策略、委外加工 |
| Minutes of Meeting — May 21 / 会议纪要5月21日 | 2026-05-21 | Belgian VAT logic vs SAP standard, customer classification / 比利时增值税与SAP标准差异、客户分类 |
| SD Research — CBF / SD调研 | Nov 2025 | Sales org, quotation, order types, credit management / 销售组织、报价、订单类型、信用管理 |
| MM/WM Research / MM/WM调研 | Nov 2025 | Suppliers, procurement PO flow, inventory management / 供应商、采购流程、库存管理 |
| PP Research / PP调研 | Nov 2025 | Assembly process, BOM (minimal) / 组装流程、BOM（极简） |
| QM Research / QM调研 | Nov 2025 | Incoming inspection only / 仅来料检验 |
| FICO Research / FICO调研 | Nov 2025 | GL, AR, AP, Fixed Assets, VAT, Withholding Tax / 总账、应收、应付、固定资产、增值税、预扣税 |
| CBF On-site Consulting Report / CBF现场咨询报告 | Nov 2025 | Detailed current system analysis / 详细现有系统分析 |
| BDK Process Flow Test / BDK流程测试 | 2026 | Third-party sales process (CB2 item category) / 第三方销售流程（CB2项目类别） |
| CBF System Config Status / CBF系统配置状态 | 2026-05-13 | Config completeness by module / 各模块配置完成度 |

## B: Key Contact Persons / 关键联系人

| Name / 姓名 | Role / 角色 | Department / 部门 |
|-------------|------------|-------------------|
| Manager Yu / 俞经理 | CBF Project Lead / CBF项目负责人 | Client Side / 客户方 |
| Thea | CBF Team Member / CBF团队成员 | Client Side / 客户方 |
| Vincent Delsaute | CBF Finance Lead / CBF财务负责人 | Finance / 财务部 |
| Manager Zhan / 詹经理 | CBF Team Member / CBF团队成员 | Client Side / 客户方 |
| Pascal Lust | Purchase Manager / 采购经理 | Procurement / 采购部 |
| Michael Scohy | Quality Control & Storeman / 质控兼仓管 | Logistics/QC / 物流/质检 |
| Sylvie Ledoux | Spares & Service Sales / 备件与服务销售 | Sales (Aftermarket) / 销售（售后） |
| Nicolas Blommaert | Sales Manager / 销售经理 | Sales / 销售部 |
| Zhang Jing / 张静 | BOS Consultant Lead / BOS顾问负责人 | BOS Consulting |
| Zhao Tianjian / 赵天健 | BOS Consultant / BOS顾问 | BOS Consulting |
| Eric | BOS Configuration Support / BOS配置支持 | BOS Consulting |

## C: Glossary / 术语表

| Term / 术语 | Meaning / 含义 |
|-------------|---------------|
| CBF | Clyde Bergemann Forest S.A. (Belgium / 比利时) |
| CBW | Clyde Bergemann Werlieferant (Germany HQ / 德国总部) |
| SCB | Shanghai Clyde Bergemann (Parent / 母公司) |
| YCBE | Belgian National Chart of Accounts / 比利时国家会计科目表 |
| YCOA | Standard SAP Chart of Accounts / SAP标准会计科目表 |
| COA | Chart of Accounts / 会计科目表 |
| DRC | Document Compliance (SAP module for regulatory reporting) / 单据合规（SAP监管报告模块） |
| GRC | Governance, Risk & Compliance / 治理、风险与合规 |
| BDK | SAP process: Third-party sales (item category CB2) / SAP流程：第三方销售（项目类别CB2） |
| GRIR | Goods Receipt / Invoice Receipt account / 收货/发票收据科目 |
| PE | Parallel Environment (test system) / 并行环境（测试系统） |
| UAT | User Acceptance Testing / 用户验收测试 |
| PEPPOL | Pan-European Public Procurement On-Line (e-invoicing) / 泛欧公共采购在线平台（电子发票） |
| RE | Reverse Charge (intra-EU VAT mechanism) / 逆向征收（欧盟内部增值税机制） |
| WIP | Work In Progress / 在制品 |
| FOC | Free of Charge / 免费 |
| FERT | Finished Product (SAP material type) / 成品（SAP物料类型） |

---

**Document History / 文档历史**

| Version / 版本 | Date / 日期 | Author / 编制 | Changes / 变更 |
|---------|------|--------|---------|
| V1.0 | 2026-05 | BOS Team | Initial blueprint based on Apr-May meetings + research docs / 基于4-5月会议纪要+调研文档的初版蓝图 |
| V1.1 | 2026-05 | BOS Team | Removed CBP references (except org structure placeholder); Full bilingual Chinese-English / 移除CBP引用（组织架构预留除外）；全中英双语 |
| V1.2 | 2026-05 | BOS Team | Fixed SD customer count error; Removed unverifiable Scope Item IDs; Added Issue #8 (QM scope), #9 (Fixed Asset migration), #10 (Material numbering); Added config status detail (MM 80% breakdown, MM material 10%) / 修正SD客户数量错误；移除不可验证的Scope Item ID；新增Issue #8(QM范围)、#9(固定资产迁移)、#10(物料编码)；补充配置状态明细 |
| V1.3 | 2026-05 | BOS Team | Added 6 detailed process flowcharts (SVG); Added role/responsibility for each process step; Added SAP internal/external markers / 新增6个详细流程图(SVG)；新增每个流程步骤的角色职责；新增SAP系统内外标识 |
| V1.4 | 2026-05 | BOS Team | Fixed heading styles for TOC generation; Added structured auto-numbering (1/1.1/1.1.1); Embedded flowcharts in DOCX with fixed arrow markers / 修正标题样式以支持目录生成；新增结构化自动编号(1/1.1/1.1.1)；流程图嵌入DOCX并修复箭头显示 |

> **Important Notice / 重要声明**: This blueprint is based solely on available documentation. Sections marked with **[?]** or **Issue #N** require confirmation from client stakeholders. No assumptions have been made — all gaps are explicitly documented as questions with recommended solutions.
>
> 本蓝图仅基于现有文档编制。标有 **[?]** 或 **Issue #N** 的部分需要客户确认。未做任何猜测假设 — 所有信息缺口均已明确记录为问题点并附有建议方案。