Why some self-called ‘developers’ create module-pools if they don’t understand the whole concept of them? Where’s the sense of create a module-pool for each action of the same concept? Why must I find a module-pool for create data, another one for display it, and a third one to delete them? Where did those self-called ‘developers’ learn about the module-pool thing?
Maybe I’m the one who’s wrong, but I ever supposed a module-pool is a bunch of code pieces and screens, that, under the same concept, allow the easy maintenance of a business concept’s actions. I mean, if I must maintain the object Ob, I will create a SINGLE module-pool, with enough code pieces (modules) and screens to be able to maintain all the Ob’s properties. I will save time and space if I can use a single screen and block and/or hide its useless items when they are not needed…
Then I’ll decide if I want a single transaction or more of them, calling the proper screen, who will block by itself its parts what will not be used by the calling transaction. It will save time and space, and, better than this, will make my life easier when the users will ask me to modify the screen. Think about it: I will to modify ONE screen, when all those self-called ‘developers’ will must to modify three or more.
Why people cannot (or want not) learn the advantages of a tool before to use it?
I’m almost six years old here. And I’m starting to feel I can do my work with the same knowledge I had when I started to develop in ABAP. It’s not about compatibility, it’s about evolution. If I didn’t need to learn new tricks to continue doing my work, it means ABAP is optimized? I don’t think so.
What does it mean, then?
It means two things (or more): I will be able to continue being an ABAPer without any kind of effort (wow!) and I will be able to continue using unoptimized techniques (ouch!). The quality of my work relies absolutely over my will. And I don’t have will (not time) enough to seek new ways to do old things. From time to time a question here raises an answer that shows me a new way, that I try to append to my developing “tools”, but no more.
I’m still working with programs which use of unoptimized (and weird) coding makes my worktime a hell. The code works, of course (more or less), but each change I must do takes too much time because the use of things like “OCCURS 0 WITH HEADER LINE” or “TABLES:”. And I don’t have enough time (nor my boss wants me to invest time on it) to fix/upgrade/optimize those old sentences.
I’m still finding (from time to time) old-school coders (doh! how many people will call me “old-school coder” now?) who still use sentences like the ones I said you. Why? Because they don’t need to evolve. It’s their fault or SAP’s? Am I the only one who feels sad because that? Or maybe all you had enough will/time/luck to be able to evolve your programs (and your skills) to use optimized calls?
Doh, I’m still trying to find time to test my old objects skills with ABAP
More Doh’es… I just had some kind of dejà vu (matrix error?) when thinking about to post this post in the TI blog, and though “I though it before”. And I was right. I wrote about this kind of things there: Evolution needed?
I think I failed miserably trying to evolve myself. But it’s not just my fault only. I think someone in Walldorf shall start to remove some sentences/adds from ABAP, before we’ll be too used to use them.
I spent all the fucking morning finding relations between around 20 tables, 30 function modules and around 30 programs (with their transaction codes).
I did all the job using a spreadsheet I uploaded into our documental server (I will not tell the brand nor the software).
Do you know the idiotic face someone has after return to work and see all this work disappeared? Just because (maybe) someone pressed the wrong button?
For Pete’s Sake! (hey doc) I’ll never again will work with attachments if able. Will be better and safer to work in local and upload the changes manually each time.
This time, Sandi Wright is providing us with few pearls of genie about SAP acronyms. I thought they cannot be lost, and (wishing she will allow me to keep those posts here) I decided to copy them here.
I will try to keep them updated, shame on me if you don’t like ’em. In any case, you can find them here
Maybe you have used sometime the wonderful SFMDR (SAP Function Module Documentation Repository) from Richard Harper (his friends call him “Rich”… both).
When he launched the idea, I was one of the first SAPFans to jump over the wagon to help him with its translations…
An archeological excavation made this Sunday in the Montseny Natural Park has found a claw from an extinct (obviously) dinosaur. The dinosaur has been called Slowraptor Montsenionensis, or simply slowraptor.
Few days ago (maybe only two, but time lasts longer if you are working) we had a guy at the SAPFans forum who made few mistakes posting a little advertising there:
– He didn’t read the basic rules of the site
– He didn’t choose the appropiate forum to his message
– He multi-posted his advertising message through few boards there
– He used big coloured bold letters to make our eyes ask for aeuthanasia
Of course, the General Discussion regulars made fun about his post (as we do about any post, serious or not… it’s the way SF’s GD works today), and the guy claimed for peace (ironnically, maybe… I’m not much versed in English to notice it sometimes).