Well, sort of. Okay, I just re-used, de-cluttered and re-wrote a custom report to create a batch input thingy, but Thursday and Friday I looked at the original report and was like "What does this all mean? Do I need this? What is this for?! How do you spell ABAB?" and now I have a shiny, clean program (probably written in oldschool technique all over), but it works and I understand what the parts do. And I even used a function module delivered by SAP for something. :D
WOHOOO!
But it showed that I haven't looked at ABAP code since... well I guess something like 2 years or more. It was all SQL and Java script for me these past long months (doing IDM stuff).
I'd love to work on the code new to bring it up to modern day ABAP or "best practice programming". And I don't mean OO. :P
I'll ask my colleague to help me with this when she's back.
Congrats! We knew you could do it!
It's nice to learn a new skill but I feel these days becoming an ABAPer is like winning a ticket to a cruise on Titanic. :) Good thing you still have all other skills to fall back to.
Yeah, I'm pretty grateful I don't need to become an ABAPer. ^^ IDM is still my main system. But I'm also the admin for one ERP module and for that one I needed that program. But it's been some time, since I needed to actually program something for that part of my job. And what I did earlier were mostly reports, not something that should update fields.
It's nice to have the chance to dabble in so many different things, though. :)
Old school ABAP is alive and well and living in the real world. You should see some of my ABAP - I know some people who would call it prehistoric, not just old:-)
The most important thing is - "it works and I understand what the parts do". That's all you need.
Steve.
>And I don't mean OO. :P
Ahhh...goatdammit, Steffi. If you only knew the power of the dark side...