After summarizing project experience across many SAP implementations, the SAP Optimization Solution Package 2.0 was organized as a set of reusable scenarios. The purpose is not to sell a list of functions, but to start from better solution thinking.
A good SAP solution should be based on SAP and go beyond SAP when needed. It should understand standard logic, recognize unreasonable requirements, solve difficult problems, and remain useful beyond one project.
What the package covers
The package includes multi-organization scenarios such as centralized purchasing, centralized sales, and intercompany transactions; special stock and transaction scenarios such as supplier consignment, customer-owned materials, MTO, subcontracting, and operation subcontracting; MRP optimization including specified suppliers and MTO; BOM optimization such as purchasing BOM and customer BOM; sales, production, procurement, globalization, and tax-related scenarios.
Why a package is useful
Many SAP pain points repeat across companies. If every project starts from zero, teams spend too much time rediscovering the same problems. A solution package provides a better starting point, but it still requires business judgment and adaptation.
The standard for a good solution
A good solution is not only technically feasible. It should make management clearer, handle exceptions, avoid unnecessary invention, and keep room for future changes. It should be iterated like a product rather than frozen as a project document.