SAPManual step
Current official baseline
Actual values still need to be updated manually in the corporate system before extraction.
CSV exportofficial source for the current scenario
From fragmented SAP and GDTec extraction to a single view for monitoring epics, periods, balances and budget execution with far less manual work.
The flow below summarizes the case architecture: what still requires manual intervention, what is automated, and how the solution separates official data from planning scenarios.
Actual values still need to be updated manually in the corporate system before extraction.
Reflects information from the primary system and adds data not directly available from the same source.
Extracted files are organized in a shared network folder and become a recurring input to the solution.
Performs cleaning, consolidation, source matching and preparation of current and simulated views.
Consolidated view of the actual scenario recorded in the official sources.
Separate area for testing assumptions without changing the official view.
For more complex analyses, manual work could reach approximately 8 hours.
Contract-by-contract consultation, consolidation of multiple epics, comparison of planned, actual and authorized values, and creation of new Excel views.
Source updates, file extraction, base loading and refresh of the entire processing and visualization structure.
The solution eliminated the need to rebuild the analysis for every new question: the structure is already prepared to answer different slices and scenarios.
*Estimate based on the pre-automation operational flow. The 25–30 minute duration corresponds to the current observed process.Budget data was available across corporate platforms, but turning it into a useful management view required extensive querying, copying, consolidation and manual calculations.
To monitor budgets by epic, contract, month or year, the process could require checking items one by one, moving values into spreadsheets and rebuilding the consolidated view. The broader the period, the greater the operational effort and risk of inconsistencies.
The technical design separates extraction, storage, processing and consumption so they do not depend on the same manual step.
SAP and GDTec remain the official sources. The solution does not change those systems; it organizes how their data is consumed.
The shared folder becomes a predictable entry point. New files can feed the process without rebuilding the structure from scratch.
Power Query centralizes cleaning, typing, rules and consolidation. Complexity stays in the technical layer — not with the person consuming the information.
Decision-makers work with two clear views: the current official scenario and a simulation area to test assumptions without changing actuals.
Analyze a specific epic or the full portfolio without manually rebuilding the base for each analysis.
Switch between months and years while keeping history available for analysis.
Monitor authorized, actual, planned values and balances in a single view.
New exports enter the flow without requiring manual reconstruction of the consolidated structure.
It turns multiple operational sources into an information layer ready for consultation, comparison and decision-making — reducing dependence on recurring manual manipulation.
Some project decisions show where the real complexity was — without turning the case into implementation documentation.
Exported files become a recurring input layer. Power Query reads, processes and consolidates the content without requiring each file to be handled individually.
The processing layer keeps source complexity away from users who only need to consult budgets, history and balances.
understand the context · structure the problem · build a reliable solution