Next Generation ABAP Development (upd)

Next Generation ABAP development bookAnd even more on Thomas Jung… This time he teams up with “Mr. ABAP “(I thought that was Horst Keller? – so there is more than one) Rich Heilman to give us a book on “Next Generation ABAP Development”.

“ANOTHER book on ABAP ?”, I hear you shout. Now before you yawn and click away, check out Thomas’ blog post on SDN or read this:

“The structure of this book reflects the workflow of a development project. The first half of the book focuses on creating the data and application logic layers and then service-enabling them. The second half of the book focuses on creating the user interface layers.”

Sounds very promising ! Now let’s pick out some bits from the table of contents:

Chapter 3: Data Persistence Layer
In this chapter, we’ll build the logic that controls the persistence of application data. We’ll start by generating persistent object classes for the underlying data dictionary tables created in Chapter 2. Then, we’ll build a set of business object classes to hide the inner technical details of the Persistent Objects. In addition to the new technology of Persistent Objects, we’ll show you how to use ZIP compression on large strings.

ZIP Compression on large strings?! Wehey.

Chapter 4: Consuming a Web Service
Not all project data will originate from one centralized system. For example, in the sample application, some data will be stored in a legacy system and accessed remotely via Web Services. In this chapter, we will examine the process for generating a Web Service proxy object and integrating this proxy into the data persistence layer.

VERY nice !

Chapter 5: Shared Memory Objects
After some analysis, it will become apparent that the sample application has some static data that will be accessed repeatedly. In this chapter, we will describe how you can provide the best performance by structuring the data access for this type of data into an ABAP Shared Memory Object.

Now which ABAPer hasn’t been at this point and wants help with it? My wallet is opening slowly…

Chapter 7: ABAP and SAP NetWeaver Master Data Management
This is the first of our “What-If” chapters. Here, we look at an alternative approach to the project where our master data is modeled and stored in SAP NetWeaver Master Data Management (SAP NetWeaver MDM), instead of the local Data Dictionary. This chapter will focus on how we would alter the data persistence layer to read this data via the SAP NetWeaver MDM ABAP application programming interface (API) instead of directly from the local database.

It doesn’t get more “now” than this!

Chapter 11: Classic Dynpro UI/ALV Object Model
In this chapter, we turn our attention to user interface logic. In the sample application requirements, there are a group of internal users who are full time SAP GUI users and who need powerful reporting tools. Therefore, we’ll learn how to build a classic Dynpro screen on top of the Model View Controller (MVC), which uses the ALV Object Model for its reporting output.

Chapter 12: Web Dynpro ABAP
Since most of the sample application’s users are not SAP GUI users, we’ll look at how you can build a Web Dynpro user interface for these users. This chapter will focus on real world Web Dynpro applications that contain multiple component usages, ALV integration, and table popins.

Sounds already as if this is a book written by people who know what is required out there now – and what is going to come fairly soon. Especially Chapter 11 is something I come across a lot in my day-to-day work. But there is one more….

Chapter 16: RSS Feed Using an ICF Service Node
In this chapter, we’ll examine how Internet Communication Framework (ICF) Service Nodes can be combined with XML processing in ABAP to produce interesting Web 2.0 type projects. As the final example of the book, we’ll implement an RSS Feed using these technologies.

Right, this is probably not something that most companies would use right here and now, but RSS feed implementation will soon become very commonplace for most ERP installations and not just for a chosen disruptive and experimental few. Still, a very interesting topic indeed.

On the whole – I am thrilled and can’t wait until the beginning of August when this book comes out – it says the “book hits the shelves” on SDN, but there must be a misunderstanding, maybe it’s SAP’s shelves?.

Jung and Heilman crammed all this into 330 pages and a CD with examples, which suggests that not too much detail is provided. The 17 chapters cover a mighty lot of ground. have written a total of 485 pages, which seems ample considering they are covering a mighty lot of ground here. But let’s wait and see.

[UPDATE] Whilst sappress.com announces the book for release in August 2007, I managed to order an english version of it at Galileo Press (SAP PressGermany). Let’s see what happens Stefan Proksch, technical editor of Galileo Press kindly explained in the comments why Galileo Press released the book already. He also told me that there will be a German version of the book, to be released in August this year.

Starship Enterprisey – I love ABAP

Craig and Thomas have really hit bullseye with their “I love ABAP” podcast on the strangely-named “Starship Enterprisey Radio”. Interviewing Thomas Jung of SAP Labs, the three of them once and for all do away with some of the prejudices and (flawed) opinions that seem to have manifested themselves over the last few years.

I have always liked Thomas’ blog contributions on SDN – and I have to admit that his posts have helped me along quite a few times in my daily work. Thomas is a true Guru and totally passionate about everything ABAP.

The podcast also does a tremendously good job in outlining where ABAP is heading to for the future.

Fasten your seat belts – Warp 9, Mr. Sulu !

SAP Web 2.0 discussion forum

Under the headline ” Forum: SAP 2.0 – We want to know what you think!”  SAP created a new SDN discussion forum a few days ago.  I am going to be honest with you and say that at first glance it looked to me like another way of getting SDN feedback – on top of the SDN questionnaires. In addition, I thought that any 2.0 discussion seemed outdated in the light of recent Web 3.0 comments by Henning Kagermann.

However there is more to it. Amongst other, there are posts about grades of JS integration, development interdependencies between EP/KM and Virtual Communities.

Well, it’s in my SAP Blogs&Feeds folder now…

Business Apps on Microsoft Surface?

I just had a quick google for “microsoft surface business application” and surprisingly enough the SAP Blogsphere has not jumped onto this one yet (well, Craig has – sort of).

So let me join him…

  1. surface desks with (any) SAP UI on it – not a good idea from an ergonomical perspective. Might work if the desk is slightly tilted upwards, like those used by architects (probably way back!). Privacy could be an issue here, as your desk could be easily overlooked.
  2. surface apps that work with RFID products – place the product on it or near it and all relevant SAP transactional and master data can be displayed for you – areas of application for this are endless (POS, warehouse GI/GR, manufacturing, etc)
  3. graphics-based development modeling tools (valid for SAP or non-SAP)
  4. SD/ CRM / SRM doc flow (any doc flow app really): integration of document flow and archived docs – due to the increase of screen real estate, it would be possible for a customer service clerks to immediately have all order-relevant documents on display as the customer is getting in touch.

In general (and if you leave financial issues aside for a moment), I’d say that MS’s surface UI technology brings advantages due to a) more screen real estate and/or b) through a new and sophisticated way of connecting devices and products by simply placing them on the table. Privacy and ergonomics could be a concern in any area (business or consumer). And what about portability? Most people work on laptops these days. It would mean you still have your laptop (or similar) device in order to work whilst on the move.

I personally want to see Pong on it first.

TechTarget on SAP consulting trends

In his latest “SAP consulting trend trilogy” on SearchSAPs Jon Reed summarises in great fashion the current opportunities, challenges and threats of the SAP Consulting market. In his recent contribution he talks to a large extend about the North American SAP freelance market, but I guess in Europe the general tendencies are the same.

His main conclusions are very much the same as David Foote’s statements from back in February this year (link to previous post on this site): Due to the changes introduced by the Netweaver platform the traditional skill sets of both SAP developers and Basis staff is in flux. In detail, Reed and Foote are both identifying 3 main trends:

  • infrastructure (or “integration and reduction” as Foote calls it)
  • functional (Foote calls them “Modellers” or “Enablers”)
  • business intelligence (data mgt, data warehouse, BW, BI)

Reed explains that the surge of New Dimension product installs is triggered by an increased number of installs at medium sized companies. I’d agree with Reed on this one, but would also add that another contributing factor is that only recently companies properly understood the contribution these products can make to their business and how it can provide them with competitive advantage.

This one made me smile:

Contrary to what SAP may imply — that everyone is moving to 6.0 — companies are upgrading to a range of SAP releases.

On the whole, part one, two and three of Jon Reed’s “SAP consulting trends” document make a very worthwhile read. SearchSAP tends to sometimes pack older SAP career posts into new ones and makes it look as if these were recent, but not in this case. If you’re a SAP Consultant: read it. Once you’ve finished reading it – read it again.

All I would like to see now is a more detailed analysis of the European SAP market…