作者:Sajiv Francis 约 2 分钟阅读 更新日期:2026-07-22 标签:企业架构, EA, SAP
SAP S/4HANA solution-architecture references — migration, configuration, and
accounting design from real program work. Identifiers are durable by design — scope
item codes, transaction codes, IMG paths, and SAP Note numbers rather than rot-prone
portal URLs.
Product Costing — Product costing in SAP S/4HANA — standard cost estimation, production order execution, period-end variances, and Material Ledger actual costing. A two-part series.
Production Planning — Discrete manufacturing in SAP S/4HANA — routings and operations, order confirmations, and the planning-to-execution flow.
Project System — SAP S/4HANA Project System (PS) — WBS architecture, Resource-Related Billing, and cross-entity funded CapEx settlement.
SAP Material Ledger — SAP Material Ledger and actual costing in S/4HANA — multi-currency / multi-valuation inventory, actual vs standard cost, and the parallel-ledger handling of inventory measurement.
SAP Asset Accounting (FI-AA) — SAP Asset Accounting in S/4HANA — fixed-asset capitalization, depreciation areas for parallel valuation, AuC, and the accounting-standard differences it implements.
SAP Central Finance (CFIN) — SAP Central Finance — real-time replication of financial postings from source SAP and non-SAP ERPs into a central S/4HANA system via SLT, for unified reporting without a full conversion.
SAP Profitability and Performance Management (PaPM) — SAP PaPM — an in-memory calculation and allocation engine for cost and profitability modeling: high-volume allocations, what-if simulation, and multidimensional profitability analysis over S/4HANA and BW data.
SAP Revenue Accounting (RAR) — SAP Revenue Accounting and Reporting — implementing ASC 606 / IFRS 15 in S/4HANA: contract combination, performance obligations, SSP allocation, and fulfillment-based recognition.
What is published here: solution-architecture references for SAP S/4HANA —
product costing and Material Ledger, asset accounting, Central Finance, PaPM, and
revenue accounting (RAR) — grounded in SAP standard documentation and shaped by real
implementation work. Claims point to durable identifiers (scope items, transaction
codes, IMG paths, SAP Notes) so they stay valid as portal URLs rot. What is not:
client names or program specifics, proprietary configuration exports, or reproductions
of SAP’s copyrighted documentation — those are referenced by identifier, not reproduced.