Hi everyone,
I recently joined big D for an SAP role where I was told I’d be working on ABAP development (especially newer areas like CDS views).
However, after joining the project, the reality has been quite different:
- Most of the work assigned is related to BW, not ABAP
- Tasks are very basic/repetitive and not really development-focused
- There hasn’t been any ABAP exposure so far
- Work expectations are quite intense (full-time office, weekends sometimes)
When I discussed this with my manager, I was told that ABAP doesn’t have much future and I should focus on becoming a BW consultant instead.
The thing is, my background and interest are strongly aligned with ABAP (and I was planning to move towards newer areas like RAP/BTP). I don’t mind learning new things, but this feels like a completely different direction than what I signed up for — and the work itself isn’t very engaging or skill-building either.
I’m still very early in my career, so I’m worried about getting stuck in the wrong track if I continue like this for a few months.
My questions:
- Is it normal for roles to be this different from what was promised?
- Should I try to switch projects internally this early, or wait it out?
- Is moving from ABAP to BW a good long-term decision, or should I stick to my original path?
- How do you usually handle situations where the assigned work doesn’t match your skillset or career goals?