开发与测试
sap-s4-migration
This skill supports SAP S/4HANA migration projects including approach selection (brownfield, greenfield, bluefield), SAP Readiness Check analysis, simplification item resolution, Business Partner migration, custom code remediation via ATC, Universal Journal migration, and post-cutover validation. Use when user mentions S/4HANA migration, system conversion, greenfield, brownfield, SUM, DMO, readiness check, simplification item, BP migration, custom code, ACDOCA, Clean Core, RISE with SAP, S/4HANA Cloud, selective data transition, H4S4, conversion project.
BoxLogoDev · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add BoxLogoDev/sapstack --skill sap-s4-migration技能说明
name: sap-s4-migration description: > This skill supports SAP S/4HANA migration projects including approach selection (brownfield, greenfield, bluefield), SAP Readiness Check analysis, simplification item resolution, Business Partner migration, custom code remediation via ATC, Universal Journal migration, and post-cutover validation. Use when user mentions S/4HANA migration, system conversion, greenfield, brownfield, SUM, DMO, readiness check, simplification item, BP migration, custom code, ACDOCA, Clean Core, RISE with SAP, S/4HANA Cloud, selective data transition, H4S4, conversion project. allowed-tools: Read, Grep
1. Approach Decision Tree
Q1: Keep existing configuration and historical data?
YES → System Conversion (Brownfield)
NO → New Implementation (Greenfield)
SOME → Selective Data Transition (Bluefield / Shell Conversion)
Q2: Target deployment model?
On-premise → Full flexibility; custom code with restrictions
RISE (PCE) → Managed infrastructure; same S/4HANA functionality
S/4HANA Cloud PE → Clean Core only — no modifications, no ABAP CBO
Approach Comparison
| Aspect | Brownfield | Greenfield | Bluefield |
|---|---|---|---|
| Data migration | Automatic (SUM/DMO) | Manual (LTMC) | Selective |
| Configuration | Carried over | Redesigned | Mix |
| Custom code | Must remediate | Can replace with standard | Must remediate |
| Project duration | Shorter | Longer | Longest |
| Risk | Medium | Lower (for processes) | High (complex) |
| Best for | Large existing systems | Major transformation | Demerger / consolidation |
2. SAP Readiness Check — Critical Simplification Items
FI / Accounting
| Item ID | Impact | Description | Resolution |
|---|---|---|---|
| S4TWL_ACDOCA | High | Universal Journal mandatory; BSEG becomes secondary | Ensure New GL active; run Universal Journal migration |
| S4TWL_NEWGL | High | Classic GL not supported — New GL must be active | Activate New GL in ECC before SUM run |
| S4TWL_ASSETACCTG | High | New Asset Accounting mandatory; Classic AA removed | Run RAALTD01 migration report; verify parallel ledgers |
| S4TWL_MATERIAL_LEDGER | High | Material Ledger is mandatory in S/4HANA | Activate ML in ECC first if possible |
| S4TWL_BP | High | Business Partner mandatory; vendor/customer must become BP | Run BP migration (FLBPD1/FLBPD3) before conversion |
| S4TWL_COFI_RECONCILIATION | Medium | FI-CO reconciliation ledger removed | Ensure no open reconciliation items |
MM / Logistics
| Item ID | Impact | Description | Resolution |
|---|---|---|---|
| S4TWL_INVENTORY | High | Inventory tables restructured; MBEW→ACDOCA | No direct MBEW access — use CDS |
| S4TWL_PLANT | High | Valuation area must equal plant (1:1) | Consolidate if multiple valuation areas per plant |
| S4TWL_CENTRALPURCHORG | Medium | Central purchasing org restrictions | Review org structure |
SD / Revenue
| Item ID | Impact | Description |
|---|---|---|
| S4TWL_SD_CRM | Medium | CRM integration changes |
| S4TWL_REVENUE_RECOGNITION | High | VBREVN replaced by IFRS 15 POB approach |
ABAP / Custom Code
| Item ID | Impact | Description |
|---|---|---|
| S4TWL_COMPATIBILITY_SCOPE | High | Defines which classic APIs still supported |
3. Business Partner Migration (Mandatory for All Conversions)
Every customer and vendor must be converted to a Business Partner before go-live.
Migration Steps
Step 1: Pre-checks
PREC_CUST → customer readiness check
PREC_VEND → vendor readiness check
Fix all errors before proceeding
Step 2: BP configuration
BUPA_PRE_MERGE → BP grouping and number range configuration
Define BP grouping: customer grouping / vendor grouping
Step 3: Mass creation
FLBPD1 → vendor → Business Partner (mass conversion)
FLBPD3 → customer → Business Partner (mass conversion)
Step 4: Verification
BP transaction → check grouping, roles (FLVN00 / FLCU00)
FBL1N / FBL5N → verify AP/AR still works via BP ↔ vendor/customer link
Step 5: Post-migration check
BUPA_CHECK → Business Partner consistency check
Reconcile customer/vendor count vs BP count
Common BP Migration Errors
| Error | Root Cause | Fix |
|---|---|---|
| "Duplicate BP for vendor" | Vendor already linked to a BP | Check existing BP link: LFA1-BKVID |
| "Number range not defined" | BP grouping number range missing | BUBA → maintain number ranges |
| "Missing mandatory field" | BP grouping requires field not in vendor | Map fields in customizing |
4. Custom Code Remediation (ATC — ABAP Test Cockpit)
Most Common ATC Findings
| Finding | Root Cause | S/4HANA Replacement |
|---|---|---|
| SELECT from BSEG | Table no longer primary storage | CDS: I_JournalEntryItem |
| SELECT * from MARA | Performance + table changes | Targeted CDS with specific fields |
| SELECT from MKPF/MSEG | MATDOC is new primary | CDS: I_MaterialDocumentItem |
| SELECT from BSID/BSAD | ACDOCA is source | CDS: I_CustomerLineItem |
| SELECT from BSIK/BSAK | ACDOCA is source | CDS: I_SupplierLineItem |
| CALL TRANSACTION | Compatibility issues | BAPI or RAP action |
| Logical database PNPCE | Deprecated | Direct SELECT + AUTHORITY-CHECK |
| Old BAdI (CL_EXITHANDLER) | Classic BAdI | New BAdI (GET BADI / SE19) |
| Non-Unicode strings | S/4HANA is Unicode-only | String templates |...| |
ATC Check Process
- SE80 / ATC → run check on custom package
- Filter results: Priority 1 (blocker) and Priority 2 (high) must be fixed
- Priority 3/4: fix before go-live but not hard blockers
- Document findings → assign to developers → track remediation
5. Universal Migration Timeline
Phase 1 — Discover (
阅读完整来源 ↗