1CD Contents

1.1 Disclaimer
Although the authors of this work have tested the code samples that accompany
the book, we can make no guarantee to their use in your SAP system. We
cannot be held responsible for any damage done by installing them. We
strongly encourage you to always implement the code samples in a sandbox
system first to analyze any impact that they might have.
Support for this code will be provided on a best effort basis. The authors will
strive to answer questions about the source code, although we obviously are not
in a position to offer production critical support levels.

1.2 Contents
This CD contains several things. First, we have an electronic copy of the
original version of the book. As discussed in the Introduction of the book, there
are some major functional changes even between NetWeaver 7.0 and 7.0
Enhancement Package 2. With the electronic version of the first edition, you
can also refer back to the state of ABAP development on many points based
upon NetWeaver 7.0, allowing the new text to focus on 7.0 Enhancement
Package 2.
There are also two directoriesSAPlink and Transportsthat contain the files
for importing the source code examples and demos. The installation procedures
for this import will be discussed slightly later, under Installation Options.
There are also two directoriesData and University Photoswith supporting
content. The Data directory contains the university sample data, discussed in
Chapter 4, as well as Crystal Reports Templates and Flex and Xcelsius project
files, discussed in Chapters 16 and 20.The University Photos folder contains
images used in various reports and web applications throughout the sample and
demo applications.

1.3 Release Level

The code container here was developed on two different release levels. Code on
the CD referred to as Version 1 (V1 or VER1) comes from the original version

of this book and was developed on NetWeaver 7.0 SP10. The target platform
for installing these code samples would be a NetWeaver 7.0 with at least SP10.
Although the vast majority of the samples would function properly on any
support package level of NetWeaver 7.0, there were some enhancements to
Web Dynpro and Adobe Forms Integration that are only available with this
support package level.
The ideal system to install this version of the code samples into is the SAP
NetWeaver 7.01 ABAP Developer Edition; at the time of this printing, it is
available for download from SDN: http://www.sdn.sap.com/irj/scn/downloads.
Code on this CD that is named with Version 2 (V2 or VER2) is from the
current revision of the book and was developed using NetWeaver 7.0
Enhancement Package 2. It contains advanced features that will not function on
older release levels. At the time of printing, SAP was preparing a NetWeaver
7.0 Enhancement Package 2 developer edition for SDN, but it had not been
released yet. Hopefully by the time you hold this book in your hands, this
newer trial version will be available.

1.4 Installation Options

The source code that we deliver here is available in two different formats. First,
we offer all source code as a transport file. The SAP transport mechanism was
designed for delivery of code from SAP to customers and through a customers
own landscape, but not necessarily for the type of delivery we are doing.
Therefore, before you import these transport files, we must stress certain points.
First, the objects contained in this transport were created in the custom name
range (typically Z and Y named objects). Therefore, it is conceivable that we
would deliver an object with a name that you have already used. In this
situation, your object will likely be overwritten. Once again, please first import
this transport in some non-critical sandbox system to make sure that none of
your own development items are lost.
Another factor to consider is that by transporting these objects, your system
will see them as foreign objects. Therefore, if you need to change them, you
will first need to change their transport group assignment or use the
modification assistant.
There are further reasons why importing the code samples into the SDNprovided developer edition system is the best option. In addition to avoiding the
possibility of overwriting anything important, the objects will be delivered
thinking NSP (the system ID for the trial system) is the home location, because

we did our development on the same system imageallowing full editing of

the objects. Lastly, there is already a document available on SDN that details
how to import the transport files into the trial edition:
https://weblogs.sdn.sap.com/pub/wlg/6380.
The second format is a new option based upon the open source project, SAPlink
(http://code.google.com/p/saplink/). SAPlink is a tool that was developed by the
ABAP community for the easy exchange of development objects. It exports
development objects into an XML file. This solution has the advantage that you
can still view the source of the objects from the XML file, yet have an easy way
to import the objects into your system. All objects are delivered into the local
private package and are inactive.
The only downside to SAPlink is that it as yet does not include plugins to
support all possible ABAP development objects. We have exported as many
object types as were supported at the time of printing of this CD.
We have the Slinkee and Nugget files for the development objects on this CD;
however, to use them, you will need to download the latest version of SAPlink
and all of its plugins from the SAPlink project page.
One important note to consider, regardless of which import mechanism you
choose, has to do with the MDM related objects. The MDM code samples will
only import into your system if you have the MDM ABAP API add-on installed
in your system. Without the add-on (which is only available from the Service
Marketplace to customers who are licensed for MDM), these objects will not
compile and can lead to import errors during the transport process. These errors
are unavoidable and can be ignored. For this reason, we have created two
different transport files for each version of the code.
For Version 1, Transport File NSPK950337 contains all objects including
MDM ones. Transport File NSPK950338 contains the 7.0 based Version 1 code
without MDM. Likewise NSPK950339 has all the Version 2, 7.02 based code
samples, and NSPK950340 has the same objects minus the MDM ones.