Career Corner Discussions
Join the conversation in the Career Corner group to ask career-related questions, find approaches to building skills, and seek career advancements.
cancel
Showing results for 
Search instead for 
Did you mean: 

Expert views solicited.

Former Member
0 Kudos
141

Hi all,

I am a fresher, who joined the IT industry 4 months back.

I received a general training in ABAP. Presently I am working in a project and I am doing ABAP HCM work.

After several days of hard work, now I have gained some (though still very little) understanding of ABAP HCM (infotypes, LDBs etc).

I have received a proposal of switching my project.

In the new project, I will have the option of taking up either ABAP Workflow or ABAP Dynpro.

I find HCM abap quite intersting. But I have no prejudices (given my almost non existant experience).

I HAVE A STRONG INCLINATION TOWARDS FUNCTIONAL SAP. I AM NOT VERY COMFORTABLE WITH LOTS OF CODING.

I AM MORE INTERESTED IN LEARNING THE BUSINESS PROCESSES AND GAINING AN OVERVIEW OF BUSINESS.

I request you all to advice me whether I should go for the new project or should I continue in ABAP HCM?

Also, if I go for the new project, should I go for ABAP Workflow or ABAP Dynpro?

Please enlighten me about the FUTURE PROSPECTS, PRESENT MARKET DEMAND and GROWTH possible in all the three technologies.

Thanks in advance.

Regards.

Edited by: SUD239492 on Oct 7, 2010 4:01 PM

Moderator Message: Moved from ABAP, General.

Edited by: kishan P on Oct 7, 2010 8:05 PM

2 REPLIES 2

Sm1tje
Active Contributor
0 Kudos
101

Sorry, but this is not the place for questions like these.

Good luck anyway.

MarcinPciak
Active Contributor
0 Kudos
101

My preffered order would be: ABAP HCM, ABAP Workflow, ABAP Dynpro.

Maybe this is beacuse I am working as ABAP HCM consultant, but maybe this is because dynpro programming requires lots of coding and itself has little to do with functional SAP side (or even nothing). Worfklow seems the most functional one (to me) as it requires adapting business logic using more graphical representation then coding itself. Of course some ABAP is also required there (for custom solutions) but you could use standard BOR objects as well - then custom ABAP coding would not be necessary. I think this however is not too much module-specific as it might be used accross all SAP areas. Great fun I think though - I am going to take some course of that soon so maybe can suggest more on this later.

ABAP HCM is interesing too. Knowing that particular area allows you to transfer to Functional HCM, which combined with ABAP places you in front sit for good job opportunities. In Poland (where I am come from) ABAP HCM developers are hunted. Be aware though that i.e. functional payroll HCM would require some legal knowledge of country-specific payroll, which might be useless when switching to other country payroll. Anyhow general concepts stay the same.

One more word regarding dynpro. As long as they offer you Web Dypro this might be a great project too, as this is right now one of the top most UI programming technology in ABAP. But as we talk about classic dynpros with possible combination of GUI controls this will become complex (but doens't mean uninteresing). Also, classing dynpros might soon be replaced by pure web applications (web dynpros) so they might become obsolete, however this transition might take some time as long as SAP GUI is in daily use.

To sum up. Going for ABAP HCM most likely will require some dynpro knowledge too as list reports are already obsolete and no one uses them nowadays. Workflow, on the other hand could require some ABAP coding, but not necessarly.

Hope this claryfies a little bit what you are going to struggle with, or rather enjoy with:)

Regards

Marcin