If you’re starting to look at SAP Travel Management, a question you’ll likely face is whether to customize your Portal portion using Web Dynpro for Java or Web Dynpro for ABAP. With the introduction of the Java stack in Netweaver 7, you’d think that Java was the logical go-forward platform, but this is not the case with Travel. We are implementing Travel at my company, and have heard from several sources, including SAP, that future development in Travel will be strictly Web Dynpro for ABAP.
This may cause a bit of consternation if you, like us, had tooled your Portal team with Java gurus. Perhaps SAP were thinking that most shops have plenty (hah!) of ABAP resources, so they might drive more adoption by utilizing them with Travel. Another possible reason for the ABAP only decision might be that there would be significant interaction required with the core SAP system, and therefore ABAPpers would feel more at home.
The problem that we have is that most of our ABAPpers have little web experience and our Java/Portal people have little ABAP experience. There are 4 exits from this quandry:
- You still have the option to go with Web Dynpro for Java, but you will not be able to get enhancements down the road and a future upgrade might be problematic
- Your ABAP resources will need to become Portal experts….a new breed of ABAPper called a PortABAPper
- Your Portal/Java resources will need to take up ABAP, becoming JABAPpers
- Close your eyes, do a Hail Mary and hire a consultant (Note: the Hail Mary is not because you might regret the consultant, but because you might regret not having the in-house expertise when it’s over.)
The silver lining? There’s nothing like the opportunity to learn something new.