Danone — SAP S/4HANA Finance architecture
Conceptual foundation, mapping of financial flows, and defending the target architecture in front of a panel.
Context
A Finance transformation programme on SAP S/4HANA. The point of the scoping phase is not to pick modules, but to lay a conceptual foundation clear enough that the architecture decisions that follow can actually be argued about.
What I did
- Conceptual foundation for the Finance domain: business objects, master data, ownership boundaries.
- Mapping of financial flows and of the interfaces with the rest of the IS.
- Target architecture deck, built to be defended in front of business stakeholders as much as technical ones.
- Defence in front of a panel.
Outcome
[TODO: metric] functional scope covered by the mapping, or defence grade.
What I took from it
In front of a business decision-maker, an architecture is not defended on technical correctness but on how clearly it frames the trade-offs. A diagram you cannot explain in two minutes does not exist in the room.