Bachelor's Degree in Computer Engineering
Autonomous University of Barcelona (UAB)Specialisation in Information TechnologiesHighest honours (Matrícula de Honor) in
Computer NetworksProgramming MethodologyArtificial IntelligenceComputer Structure
sy-uname = 'JUANMA'About · Résumé
Juan Manuel Vallecillos
Senior SAP Consultant at VISEO Iberia.ABAP developer specialised in FI, MM and process automation.
I've spent over 7 years between ABAP code and finance and procurement processes that never behave exactly like the documentation says. My job is to make them work.
01 · In 30 seconds
The essentials
- ROLE
- Senior SAP Consultant · VISEO Iberia
- EXPERIENCE
- Over 7 years in SAP projects, since 2019
- EDUCATION
- Bachelor's in Computer Engineering · UAB
- MODULES
- FI · MM
- SPECIALTY
- ABAP and integration: reports, enhancements, BAPIs, user-exits and interfaces with external systems
- ENVIRONMENT
- SAP ECC and S/4HANA
- INDUSTRIES
- Airlines · Manufacturing · Distribution · Services
- LANGUAGES
- Spanish · Catalan · English
- LOCATION
- Barcelona
02 · Career
My SAP journey
- Apr 2024 — presentApr 2024 — presentSenior SAP ConsultantVISEO Iberia
Development and maintenance of ABAP solutions for the FI and MM modules on S/4HANA. Requirements analysis with the functional team, reports, enhancements and interfaces with external systems.
- Sep 2022 — Apr 2024Sep 2022 — Apr 2024Business & Integration Arch Sr AnalystAccenture
Techno-functional role in SAP integration projects: solution design and ABAP development focused on integration with middleware and external systems, on international projects.
- Oct 2019 — Sep 2022Oct 2019 — Sep 2022Application Development Analyst · SAP ABAPAccenture
ABAP development on FI and MM implementation and support projects: reports, BAPIs, user-exits and Smartforms/Adobe forms. My first S/4HANA projects.
03 · Education
Education
04 · Stack & modules
What I work with
ABAP
Classic and object-orientedBAdIsUser-exitsEnhancement framework
FI
Payables and receivablesFixed assetsPeriod-end closingBank integrations
MM
PurchasingStock managementIDocsSupplier integration
Automation
Background jobsBDC / CALL TRANSACTIONBAPIsInterfaces
Tools
ABAP WorkbenchADT (Eclipse)TransportsVersion controlJiraServiceNow
Forms & integration
SmartformsSAPscriptsMiddleware integrationExternal system interfaces
05 · How I work
Eight things I care about
01
Process first, code second.Before touching anything I try to understand what the business needs and why it fails today.
02
Document what I do.Functional designs, technical designs and process documentation for users. It's often missing, and it's what keeps knowledge from depending on a single person.
03
Everything goes through the ticket.I review the incidents and requests the client raises in their ticketing tool (Jira, ServiceNow or whatever they use) and use it actively: analysis, status and solution, so anyone can follow the work.
04
Think about performance from the start.Efficient SQL and real data volumes in mind before they become a problem, not once the report already takes minutes in production.
05
Test the way it will really run.In background, with real volumes and at period-end, not just in dialog mode with three records. That is where problems show up.
06
Write code for whoever comes next.Clear names, modern ABAP syntax and no tricks only I understand. Someone will have to maintain it a few years from now.
07
Raise issues early.I'd rather have an awkward conversation today than a fire at month-end.
08
Speak both languages.The functional consultant's and the developer's. A good part of the job is translating between them.
06 · How I got here
How I got here
The programming bug bit me early. At 8 or 9 I was playing Habbo Hotel and all I wanted was to build one just like it; then came MSN Groups pages (I had one dedicated to Pokémon, no shame about it), and as a teenager I set up and customized game servers, tweaking the client and the server until they did what I wanted. I had no idea what I was doing most of the time — it was all trial, error, and breaking things until I understood why they broke. That's where I really started programming, with no idea that years later I'd end up doing basically the same thing — changing how a system behaves when it wasn't built for that — but with SAP instead of an online game, and a lot less room for trial and error.
I ended up in SAP almost by accident. During my university internship search I interviewed with EY and Accenture for cybersecurity roles; Accenture didn't have any cybersecurity openings at the time, but offered me an internship in "cloud programming" instead. I said yes without thinking much about it, and that's how I first came across SAP — nothing like what I'd imagined, and with no plan to stay any longer than strictly necessary. More than 7 years later, I'm still here. I'm not entirely sure how that happened; I suspect it has something to do with the fact that the problems SAP gives you look suspiciously like the ones that hooked me as a kid tinkering with servers: systems that refuse to do what you want, until you find the right way to ask.
07 · Outside the code
Outside the code
When I'm not in front of the ABAP code editor, I'm usually in front of another screen: video games and tinkering with side projects (this site is one of them) take up a good chunk of my free time — yes, I'm aware of the irony of resting from programming by programming something else.
I also keep an eye on investing, more out of curiosity about how it works than any strategy worth mentioning here. I know the programmer-plus-gamer combo means too many hours sitting down, so I try to make up for it with sports — with more discipline than I'll admit to here — and generally take personal development pretty seriously, even if that sounds like a LinkedIn line I'm specifically trying to avoid on this page.
Want to get in touch?
To discuss an article, suggest a topic or just connect, I'm on LinkedIn and on the contact form.