There are only 13 pages which detail how to create your own BAPI and the extra 50 pages on BAPIs mearly list the BAPIs that SAP delivers with less documentation than SAP already gives in their BAPI transaction...

Unfortunately, I didn't have a chance to look at the book before buying it because I bought it at a large conference in between classes. If I had spent 5 minutes looking at it before I bought it, I wouldn't have. But since the previous ABAP book from the same publishing company was of very good quality, I bought it thinking it would be the same quality. Since buying the book last year I've only looked at it for about 20 minutes. I would not recommend.

One of the junk books I;ve read lately. Poor content, structure and presentation. Lots of pages but no information. The authors/publishers tried very hard to increase the book size with all sorts of tricks. About thirty pages of the book are either blank or have chapter titles but no useful info. Not many useful code samples. The chapters on Java, OOP etc are really not necessary as there are lot of excellent tutorials/free books available on the internet. Very little information on the actual Java&BAPI as the title suggests. I;ve noticed a couple of errors in the Java related chapters. I will be very surprised if rest of the book is error free. Please do not waste your money by buying this POS.

I wish the authors put more content on the interaction of Java and BAPI, with more example codes on how to use Java to call BAPI etc. It would be perfect if they could use some real-world sample codes or lead their readers go through some complete exercise. Instead, the authors put lots of unnecessary information there, which we can find more in detail from other sources. We do not get what we really want from this book. I am surprised this book even got published.

This book is an homage to SAP, first, and consultants, second.

According to the fairy tale included as a "real world example" of an SAP implementation, when your implementation gets rough, all you need to do is throw more money and consultants at it because the consultants know best. If you just turn your company over to the knowledgeable consultants, and don't worry about the bill, everything will work out fine.

The book does not include any detailed information about how the system works. It does not include any information about how to deal with interfaces or data conversion or any discussion of customizations and modifications. It does not include any discussion of any of the widely publicized failed SAP implementations and why they went wrong.

Basically, the book tells you the history of SAP (as a software and as a company), gives you a high level fairy tale (an SAP version of "The Elves and the Shoemaker" where the business is suffering during the SAP implementation and the consultants magically come in and solve all the problems and the company lives happily ever after), and then goes on to say that SAP is so good that even when the author had criticisms about the software, it was just because she wasn't taking a broad enough view of how the SAP software was evolving, and once she talked to the nice developers at SAP, they showed her why what they were doing was right.

The bottom line from this book:

1) SAP good 2) Consultants wise and helpful

For more depth, you'll have to go somewhere else.