{"id":1527,"date":"2012-10-07T21:30:48","date_gmt":"2012-10-07T21:30:48","guid":{"rendered":"http:\/\/www.pixelbase.co.uk\/?p=1527"},"modified":"2014-10-09T10:14:50","modified_gmt":"2014-10-09T10:14:50","slug":"abap-development-for-sd-in-sap-exits-badis-and-enhancements","status":"publish","type":"post","link":"https:\/\/www.pixelbase.co.uk\/?p=1527","title":{"rendered":"ABAP Development for SD in SAP: Exits, BAdIs and Enhancements"},"content":{"rendered":"

A few weeks ago, when I announced my first SAP publication<\/a>, \u201cABAP Development for Sales and Distribution in SAP\u201d<\/a>, I promised a post in which I delve a little deeper into the book, its background and how it came about. A little “behind the stage” article if you like.<\/p>\n

\"\"<\/a>

good to finally hold it in my hands!<\/p><\/div>\n

One of Pixelbase\u2019s main mantras is very much to \u201cKeep it Real\u201d, to provide value for money and real-world advice. It probably might not come as a big surprise to you that \u201cABAP Development for SD in SAP\u201d was written along the same lines. In order to achieve a certain \u201creal-world feel\u201d, I decided to create end-to-end examples and use two characters (Junior ABAPer \u201cChristine\u201d and Senior SD Consultant \u201cSean\u201d) and a fictive company (\u201cByrell Corporation\u201d). While Christine is a young developer, well-versed in topics such as OO programming, Sean is an experienced SD consultant who occasionally dabbled in ABAP, but has never created a class parameter in his life!
\n<\/p>\n

We are in it together!<\/strong><\/p>\n

The interesting aspect of the book is that the two actually learn and feed off each other: Christine introduces to Sean topics such as web services, persistent objects and Business Object Layer programming. At the same time, Sean proves to Christine that not everything requires lengthy code enhancements (pricing routines, for example). In other chapters, he shows her how numbering ranges are defined. Just like in a real team environment, both consultants learn from each other. In most chapter projects, they have to weigh up enhancement options, making this process transparent to the reader. The latter is an important aspect of creating \u201cresponsible enhancements\u201d, as there is no silver bullet, no \u201cif A then implement B\u201d scenario. My book tries to do away with some of the black magic that enhancements can sometimes being shrouded in.<\/p>\n

I picked scenarios and example projects of varying degrees of difficulty which are based on my own experiences in the field, such as<\/p>\n