| Status | |
| Owner | |
| Stakeholders | The persons consulted or otherwise involved in making this decision. Type @ to mention people by name |
Issue
Syensqo currently operates on the SAP ECC platform, utilizing the SAP Warehouse Management (WM) solution for its logistics and inventory management processes. SAP WM is serving as the backbone of their warehouse operations for packed items; handling tasks such as goods receipt, putaway, picking, and inventory tracking. However, with the transition to SAP S/4HANA, SAP WM becomes obsolete and new possibilities emerge.
Decision
A decision is required whether to continue with the familiar SAP Stock Room Management (SAP WM solution in S/4 HANA) or to use the new SAP Extended Warehouse Management (EWM) solution.
Background & Context
Acronym / Term | System | Definition |
SAP Warehouse Management (WM) | ECC | This is the Warehouse Management Solution in ECC which is currently used by Syensqo. |
SAP Stock Room Management | S/4 HANA | This is the new name of the -older- SAP WM solution for S/4HANA. |
SAP Extended Warehouse Management (EWM) | S/4 HANA | This is the new Warehouse Management Solution in S/4 HANA. This solution can support more complex warehouse processes. |
Assumptions
Note that there are some limitations (SAP Note 2882809) compared to SAP WM. Based on the AS IS analysis these limitations should have limited impact for this decision document.
Constraints
Capture any additional constraints that the chosen alternative (i.e. the decision made) might impose on other parts of the overall design, solution, or processes.
Impacts
Describe the impact of the decision on processes, infrastructure, other SAP modules or systems, data cleansing and migration, developments, automations, interfaces, in-flight projects, etc.
Business Rules
The decision may translate into business rules which enforce the decision and will require configuration. List these business rules here. For example, "An Outline Agreement cannot be created via the RFQ process. An awarded RFQ can only result in a Purchase Order".
Options considered
List the options (viable options or alternatives) you considered. These often require a longer explanation with diagrams, or references to other documents (links are best, but attachments are also possible). Use enough detail to adequately explain what you considered so that a project or business stakeholder reviewing this decision will not come back and ask "did you think about...?"; this leads to loss of credibility and questioning of other decisions. This section also helps ensure that you considered enough suitable alternatives rather than just copy/pasting SAP's recommendations.
Option A: Option Title
Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Option B: Option Title
Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Option C: Option Title
Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Option D: Option Title
Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Evaluation
Outline why you selected a position. The best format could be a pro/con table (sample below), but is up to you as the author. You must consider complexity, feasibility, cost/effort to implement, but also ongoing operational impact and cost. You must consider the program principles and explain any deviations in detail. This is probably as important as the decision itself.
Option A | Option B | Option C | Option D | |
|---|---|---|---|---|
| Criterion 1 |
|
|
|
|
| Criterion 2 |
|  Con |
|
|
| Criterion 3 |  Pro | Con | Con | Pro |
See also
Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.
