| Status | |
| Owner | Antonio Zappone |
| Stakeholders | Gilles Madjarian, Mario Tonda |
Issue
A key decision is required on when to deploy the new consolidations tool. Along with a multiphase ERP implementation comes options on when to deploy, whether in Phase 1, 2 or X.
Decision
Optionally supplement with additional details or diagrams if required, else delete this 'Details' section.
New the Consolidation Tool will be deployed in the later Phase. The exact phase will be concluded when the Deployment Approach is finalised (estimated to be August 2024).
Background & Context
BFC (Business Objects Financial Consolidation) is the current consolidations tool. This is an SAP system however it is not integrated with the EPRs, rather data is loaded from the source EPRs.
SAP is phasing out BFC and support will cease in 2030 (extended from 2027).
Syensqo existing license is until xxxxx.
Assumptions
Clearly describe the underlying assumptions which informed or limited the choices available, or impacted the decision: cost, schedule, regulatory requirements, business drivers, country footprint, technology, etc. Include links as necessary. This section is important because a future change in circumstances might invalidate some key assumptions, which then prompts a decision to be revisited.
S4HANA will be Deployment over more than one Phase.
Group Reporting is the latest SAP Consolidations Module. It is assumed that this will be implemented for Syensqo, however this decision will be made in detailed designed.
With the implementation of the new Consolidation tool to occur in the later Phase of the deployment come additional time in the detailed design phase. As such, the suitability of Group Reporting for Syensqo will be assessed in the next phase, and is not part of the Key Decision at this point in time.
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.
BFC support ends in 2030. It is assumed to deployment will occur prior to this date.
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.
The major impacts on the decision are on the following:
Integration impacts:
- Interfacing or data loading into the consolidation system. There is an impact whether data is flowing into BFC or new Consolidation tool.
- Aligned with the deployment decision load packages loads from the source system, being PF1, WP1, or S4HANA, will continue.
Data:
- Timing and complexity of data conversion impact.
- Aligned with the deployment decision historical data loads will occur in the later phase and and "one" load.
Reporting:
- Report produced via BFC
- Aligned with the deployment decision, existing Reports will continue to be produced from BFC until the new Consolidation tool is implemented in the later phase.
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".
Existing BFC Rules will continue
S4HANA business rules relevant at this point in time will be largely caverned to the Enterprise Structure Definition.
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
Continue with BFC in the initial phase\s and deploy the new Consolidation tool in the later Phase
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.
