ABAP New Features PDF

An Overview of the
New Features in ABAP

Agenda
Horst Keller
Knowledge Architect, SAP AG
© SAP AG 2006, SAP TechEd ’06 / CD200 / 2

Regular Expressions
Shared Objects
Simple Transformations
Checkpoints
ABAP Editor
ABAP Debugger
ABAP Unit
Memory Inspector
Enhancement Framework
Preview of Next Release
Regular Expressions
Shared Objects
Checkpoints
ABAP Editor
ABAP Debugger
ABAP Unit
Memory Inspector
Learning Objectives
As a result of this lecture, you will have an

overview
of many of the new ABAP features available with SAP
NetWeaver 04 and SAP NetWeaver 2004s
of the new ABAP features coming with the follow-up release

Regular Expressions
Shared Objects
Checkpoints
ABAP Editor
ABAP Debugger
ABAP Unit
Memory Inspector
Improved Text Processing With REs
Regular Expressions (Regexes, REs) are more powerful than

traditional SAP patterns (SEARCH txt FOR pat, IF txt CP pat)
Well understood
– Developed by mathematician Kleene in the 1950s
Powerful
– Highly focused special purpose language
– Many common text processing tasks turn into
simple one-liners
Standardized and widely used Stephen C. Kleene
Image © U. of Wisconsin
– Made popular by Unix tools: grep, sed, awk, emacs

– Built into some languages like Perl and Java;
add-on libraries available for many others
– Early Unix de-facto standard formalized in PCRE and POSIX
ABAP supports POSIX regular expressions as of Release 7.00

Regular Expression Terminology
Regular expressions are built from

Literals
a b c 1 2 3 ä à ß , / = …
Special operators (metacharacters)
. * + ? \ ^ $ ( ) [ ] { }
Prepending \ turns operators into literals
REs match or represent sets of text strings

Match
RE matches text if complete text is represented by RE
REs are commonly used for searching text

Text to be searched may contain one or more matches Search
Usually interested in left-most, longest match contained in text

Regular Expressions Quick Check
What is the main difference betweens file system wildcards

like *.jpg and regular expressions?
files: * = sequence of characters

REs: * = general repetition, requires specification
of what should be repeated;
sequence of characters becomes .*
How are SAP patterns
pat pat+ *pat p#*t
written as regular expressions?
pat pat. .*pat p\*t

Regex Reference Chart (1)
Name Operator Matches

Literals a literal character
\* turn special operator * into literal character *
Wildcard . any character
Repetitions r* zero or more repetitions of r
r+ one of more repetitions of r
r{m} exactly m repetitions of r
r{m,n} at least m and at most n repetitions of r
r? optional r, i.e., zero or one repetition of r
Alternatives r|s either r or s
Sets [abc] any literal character listed
[âbc] any literal character NOT listed
[a-z] any literal character within range listed (can be combined
with above)
Classes [:alpha:] any letter, including non-latin alphabets
(to be used [:digit:] [:xdigit:] any digit 0-9/hex digit 0-9A-F
within sets) [:alnum:] [:word:] [:alpha:] plus [:digit:]/same plus '_' character
[:upper:] [:lower:] any uppercase/lowercase character
[:space:] [:blank:] any whitespace character/blank or horizontal tab
[:punct:] [:graph:] any punctuation/graphical character
[:print:] [:cntrl:] any printable/control code character
[:unicode:] any Unicode character above ASCII 255

Regex Reference Chart (2)
Name Operator Matches

Abbreviations \n \t \a newline/tab/bell character
\w \W equivalent to [[:word:]] and [^[:word:]]
\d \D equivalent to [[:digit:]] and [^[:digit:]]
\s \S equivalent to [[:space:]] and [^[:space:]]
\u \U equivalent to [[:upper:]] and [^[:upper:]]
\l \L equivalent to [[:lower:]] and [^[:lower:]]
Anchors \A \z begin and end of buffer (i.e., text to search)
^ $ begin and end of line (buffer separated into lines by \n chars)
\< \> begin and end of word
\b either begin or end of word
\B inside of a word, i.e., between two \w's
Quote \Q … \E interpret quoted sequence as literal characters
Back references () group subexpression and save submatch into register
\1 \2 \3 … matches contents of n-th register
(?: ) group subexpression, but do not store in register
Look-ahead r(?=s) matches r iff r is followed by s
r(?!s) matches r iff r is NOT followed by s
Cuts (?>r) do not backtrack for left-most longest match once r has
matched

Searching for Matches with FIND
New addition REGEX to the FIND statement:
FIND
[{FIRST OCCURRENCE}|{ALL OCCURRENCES} OF] REGEX regx
IN text
[{RESPECTING|IGNORING} CASE]
[MATCH COUNT mcnt]
[RESULTS result_tab].
Detailed match information is available with RESULTS addition.

FIND returns left-most longest match within text.

Replacing Matches with REPLACE
New addition REGEX to the REPLACE statement:
REPLACE
[{FIRST OCCURRENCE}|{ALL OCCURRENCES} OF] REGEX regx
IN text WITH repl
[{RESPECTING|IGNORING} CASE]
[REPLACEMENT COUNT mcnt]
[RESULTS result_tab].
Search works exactly as in FIND.

Grouping and Submatches
Parentheses structure complex expressions

Define scope of operators
tick*tock* (tick)*(tock)* (ticktock)*
Store submatches for later reference

very
– Submatches easily available with FIND additions useful
– Groups numbered left-to-right, can be nested
– No upper limit on number of groups
– Can refer to submatches within pattern and replacement
Non-registering parentheses (?:…) do not store submatch
(?:tick)*(?:tock)*
– Increased performance over ( )

Example: Match-Based Replacements
The replacement string can refer to submatches of match being

replaced
DATA: html TYPE string,

repl TYPE string,
regx TYPE string.
html = `<title>This is the Title</title>`.
repl = ì`.
CONCATENATE repl '(?![^<>]*>)' INTO regx.
REPLACE ALL OCCURRENCES OF REGEX regx

IN html WITH $0`.
$0 contains complete match
$1,$2, ... contain submatches
Result: <title>This is the Title</title>

Classes for Regular Expressions
ABAP Objects provides two classes for using REs

Regex CL_ABAP_REGEX
– Stores compiled automaton for RE pattern
– Should be reused to avoid costly recompilation
CL_ABAP_REGEX
– Offers simplified syntax and disabling of
submatches a*b
– Can be used in FIND and REPLACE statements
instead of textual pattern
Matcher CL_ABAP_MATCHER
– Main class for interaction with REs
– Stores copy of text to process (efficient for CL_ABAP_MATCHER
strings, costly for fixed-length fields)
___ $0
– Links text to regex object and tracks matching ___
___
and replacing within text

Matcher Class Reference Chart (1)
CL_ABAP_MATCHER Instance Methods
find_next( ) find next unprocessed match
replace_found( new ) replace match found by new *)
replace_next ( new ) find and replace next unprocessed match
get_match( ) return match information (MATCH_RESULT) *)
get_submatch( n ) return n-th submatch *)
get_offset( [n] ) return offset of current (sub)match *)
get_length( [n] ) return length of current (sub)match *)
find_all( ) return all remaining matches
replace_all( new ) replace all remaining matches
*) throws exception if no current match stored

Matcher Class Reference Chart (2)
CL_ABAP_MATCHER Class Methods
create( pattern text ) create and return matcher object
matches( pattern text ) returns abap_true if pattern matches text
contains( pattern text ) returns abap_true if text contains pattern

match
get_object( ) returns matcher object containing match

information about last matches( ) or
contains( ) invocation

Creating Regex Objects
There are two ways of setting up objects for RE processing
DATA: regex TYPE REF TO cl_abap_regex,

matcher TYPE REF TO cl_abap_matcher.
Using CREATE
CREATE OBJECT regex EXPORTING pattern = 'â*'

ignore_case = abap_true.
CREATE OBJECT matcher EXPORTING regex = regex
text = text.
Using factory method
matcher = cl_abap_matcher=>create( pattern = 'â*'

text = text ).

Example: Pattern Matching
Checking the format of an Email address:
PARAMETERS email TYPE c LENGTH 30 LOWER CASE

default 'shai.agassi@sap.com'.
DATA matcher TYPE REF TO cl_abap_matcher.
matcher = cl_abap_matcher=>create(
pattern = `\w+(\.\w+)*@(\w+\.)+(\w{2,4})`
ignore_case = 'X'
text = email ).
IF matcher->match( )IS INITIAL.

MESSAGE 'Wrong Format' TYPE 'I'.
ELSE.
MESSAGE 'Format OK' TYPE 'I'.
ENDIF.

Regular Expressions
Shared Objects
Checkpoints
ABAP Editor
ABAP Debugger
ABAP Unit
Memory Inspector
Data Access without Buffering
DB
User X
Session

Data Access with Buffering by Copy
Common data
retrieved from DB
DB
Common
Data
User X
Session

Common data
retrieved from DB and
DB aggregated
User X
Session

Common data
retrieved from DB and
DB aggregated for
each user session
Common Common Common

Data Data Data
User X User Y User Z

Session Session Session

DB
User X
Session

Common data
retrieved from DB
DB
Common
Data
User X
Session

Common data
retrieved from DB,
DB aggregated
User X
Session

Shared Memory (SHM) Common data

Common retrieved from DB,
Data aggregated,
DB
copied (EXPORT) to SHM
Common
Data
User X
Session


Common retrieved from DB,
Data aggregated,
DB
copied (EXPORT) to SHM,
and copied (IMPORT) to
each user session
Common Common Common

Data Data Data


Data Access with in Place Buffering

Common retrieved from DB
Data directly into SHM
DB
User X
Session


Data directly into SHM,
DB
aggregated in place
User X
Session


Data directly into SHM,
DB
aggregated in place
accessed copy-free by
other user sessions


Areas and Area Instances
Shared Objects memory Shared Memory

Part of the shared memory Shared Objects Memory
Shared Objects areas

Area Area
Organizational units
I
Defined at design time n I
s I n
t n s
Shared Objects area instances a s t
n t a
Content stored at runtime c a n
e n c
Identified by unique name c e
e

Working with Area Instances
Attach for write Instance

Fill the contents Root


Commit changes


Commit changes
Attach Reader1


Commit changes
Attach Reader1
Attach Reader2


Commit changes
Attach Reader1
Attach Reader2
Detach Reader1


Commit changes
Attach Reader1
Attach Reader2
Detach Reader1
Detach Reader2

Additional Features
Versioning
Auto-Build (e.g. at 1st Read-Attach)
Transactionality
Propagation
Client Dependency
Displacement
Customizable Memory- and Lifetime Restrictions
Multi-Attach to different areas at once
Shared Objects Monitor

Regular Expressions
Shared Objects
Checkpoints
ABAP Editor
ABAP Debugger
ABAP Unit
Memory Inspector
ABAP / XML Mapping: Simple Transformations
ABAP in
new aver XML
Data We
Net 04 Doc
XS
LT
LT
XS
Simple
Transformations … .. ….
…. … ..
.. …. …. ..
… …. .. .. Network
XSLT
XS
DB
LT
LT
XS
… .. ….
…. … ..
.. …. …. ..
HTML / Text

ABAP / XML Mapping Languages
XSLT (since 6.10)

works on canonical XML representation of ABAP data (asXML)
builds DOM for source side
arbitrarily complex transformations
Simple Transformations (since NetWeaver 04)

only for ABAP ↔ XML
only linear transformations (no DOM)
speedup over XSLT: 10 – 30; “unlimited” size of data
reversible (one program for both directions)
Both
symmetric: no generation of ABAP code / XML schemas
integrated in workbench (maintenance / transport)
integrated in ABAP: CALL TRANSFORMATION

Simple Transformations: Expressive Power
Anything that can be done with ...

accessing each node in the data tree
any number of times
accessing each node in the XML tree
at most once,
in document order (with "lookahead 1" on XML source)
... which includes (any combination of) ...
renamings (e.g.: structure-component / element names)
projections (omission of sub-trees)
permutations (changes in sub-tree order)
constants (e.g.: constant values, insertion of tree levels)
defaults (for initial / special values)
conditionals (e.g.: existence of sub-trees, value of nodes)
value maps
covers most data mappings in practice

Simple Transformations: Program Structure
Programs are XML templates

literal XML with
<Customers>
interspersed instructions
<tt:loop ref="CUSTTAB">
declarative, straightforward
semantics <LastName>
<tt:value ref=
Data tree access by
node references "NAME.LAST"/>
instructions access data by </LastName>

simple “reference expressions” </tt:loop>
all named children of a data node </Customers>
are accessible by name
tables are accessible as a whole
(all lines or none)

Simple Transformations: Example
<?sap.transform simple?>
<tt:transform
xmlns:tt="http://www.sap.com/transformation-templates">
<tt:root name="table"/>
<tt:template>
<TABLE>
<tt:loop ref=".table">
<ITEM> DATA: itab TYPE TABLE OF i,
<tt:value /> xmlstr TYPE xstring.
</ITEM> DO 3 TIMES. APPEND sy-index TO itab. ENDDO.
</tt:loop> CALL TRANSFORMATION z_simple_table
</TABLE> SOURCE table = itab
</tt:template> RESULT XML xmlstr.
</tt:transform> CALL FUNCTION 'DISPLAY_XML_STRING'
EXPORTING xml_string = xmlstr.

Regular Expressions
Shared Objects
Checkpoints
ABAP Editor
ABAP Debugger
ABAP Unit
Memory Inspector
system state Checkpoints in ABAP
normal termination
consistent state
program flow

Checkpoints in ABAP
unexpected
behavior
system state
normal termination
consistent state
program flow

Checkpoints in ABAP
unexpected
: assertion
behavior
system state
system state
runtime
error
normal termination
normal termination
consistent state consistent state
program flow program flow
find cause of error in shorter time

Checkpoints in ABAP
: assertion
system state
system state
undetected
error
runtime
normal termination
normal termination
error
consistent state consistent state
program flow program flow
find more errors enhance program correctness

Checkpoints in ABAP
ASSERT - Statement:
ASSERT ID group
SUBKEY subkey
FIELDS dobj1 dobj2 ...
CONDITION log_exp.
BREAK-POINT - Statement:
BREAK-POINT ID group.
LOG-POINT - Statement:
LOG-POINT ID group.

Checkpoints in ABAP
Activation method
dynamic, while system is running
Activation granularity
Logical „checkpoint groups“
Compose „variants“ from
Checkpoint groups, variants,
All checkpoints in programs, function groups, classes
Extract checkpoint groups from programs, function groups,
classes, packages, development components
User, server
Assertion mechanism
Abort, debug or protocol

Checkpoints in ABAP
ABAP checkpoints support developers in writing

correct code
Activated in SAP development systems ( abort, protocol )
Code instrumented with checkpoints is easier to

support and maintain
Can be activated on the fly in productive systems ( activation
for dedicated user, server )
No activation, no performance loss !!!

Regular Expressions
Shared Objects
Checkpoints
ABAP Editor
ABAP Debugger
ABAP Unit
Memory Inspector
New ABAP Editor
Modern Editor control

with syntax coloring
and many additional
features
Automatic syntax check!

Editor Features - Outlining
See Start / End / Middle

of language block
Collapse/Expand Block
Collapse same type

blocks
Collapse Comments
User defined
“Outlining Regions”
See current scope
See collapsed text

Editor Features - Templates
User and language

dependent
Expandable by Ctrl +
Enter
Built in runtime tags (Date

Time, Clipboard Content,
Document Name)
Interactive tags
Suggested by Code Hints
Extract template from

selected text
Surround by template

Editor Features - Code Hints
Code Hints
Suggest valid
keywords
and recently used
identifiers
Runs automatically as
you type
For templates
shortcuts
For misspelling from

auto correction
dictionary
Customizing of
suggestions

Editor Features - Clipboard
Clipboard Ring
Extended Paste Menu
Normal and block format
Multiple Clipboard
Formats:
Paste in MS Outlook
with syntax
highlighting
Paste in MS Word with
syntax highlighting
Copy/Cut Append to
clipboard
Insert Special
Unicode or ASCII format

support

Editor Features - Current Scope
Highlight of current scope

tags in source
Highlight current scope

on outline margin
See current code

hierarchy in status panel
See current brackets

highlighted in source
See mismatching
brackets highlighted in
error color

Editor Features - Extended Find/Replace
Incremental search
History of search/replace
items
Mark all occurrence with

bookmark
Search in collapsed text
Saving of search
parameters between
sessions
Use of regular expression

Editor Features - Edit Functions
Block Selection
Mistyping Correction
Auto Brackets
Keyword Case correction
Auto Indent
Caps Lock correction
Smart Tab
Surround Selection
Format After Paste
Line operations
Sort Lines
Change Case
Indent/Unindent
AutoSave
…
Editor Features - Quick Info in ABAP Debugger
Quick Info for

variables on
hovering
Quick Info for

variables by Ctrl-
Shift-Space
Customizing of
quick info

Regular Expressions
Shared Objects
Checkpoints
ABAP Editor
ABAP Debugger
ABAP Unit
Memory Inspector
Classic Debugger – Current Status
Classic Debugger
Technology
Debugger and debuggee run in the same (internal) session
Debugger dynpros placed “in-between”
Consequences
Not all ABAP code can be debugged (no conversion / field exits)
Not free of side effects (F1, F4 help, list output)
Implementation of new features not always straight-forward
No chance to use modern UI techniques (no ABAP allowed in the debugger !)
A new ABAP debugger technology

Goals – New ABAP Debugger
Higher productivity for development & support
using ABAP Debugger
More robust debugger architecture (no side effects)
Possibility to implement new features (e.g. a diff tool for

internal tables) faster and with less risks
More flexible & extensible state-of-the-art debugger UI
Use two separated sessions for the

debugger and the application

New ABAP Debugger, Two Process Architecture
The New Debugger is attached to an “external session”
Session 1 - Debuggee Session 2 - Debugger
ABAP VM
Debugger Engine
/h
UI

New ABAP Debugger – GUI
11
Process
Process Informations
Informations
22
Control
Control Area
Area 33
Source
Source Code
Code Informations,
Informations,
System
System Fields
Fields
44
Desktops
Desktops
55
Tools
Tools

New ABAP Debugger – Customizing the GUI
Enlarge
Enlarge Size
Size 1.
1. Close
Close Tool
Tool
Reduce
Reduce Size
Size 2.
2. New
New Tool
Tool
3.
3. Replace
Replace Tool
Tool
4.
4. Full
Full Screen
Screen
5.
5. Maximize
Maximize Horizontally
Horizontally
6.
6. Exchange
Exchange
7.
7. Services
Services of
of the
the Tool
Tool

New ABAP Debugger – Tools, Breakpoints, Watchpoints

Regular Expressions
Shared Objects
Checkpoints
ABAP Editor
ABAP Debugger
ABAP Unit
Memory Inspector
ABAP Unit – What Should I Know ?
What is ABAP Unit?

ABAP Unit is the ABAP framework for module/unit tests.
What is an Unit?
An unit can be considered as a non-trivial, accessible code portion
(method, function or form) where a given input or action causes a verifiable
effect. Ideally it is the smallest code part which can be tested in isolation.
How does an ABAP Unit test looks like?

The ABAP Unit tests are realized as methods of a local class
(with the addition “FOR TESTING”).
This local class is part of the class, function group or program you want to
test.

ABAP UNIT – What Should I Know ?
Why is the test class part of the productive code?

ABAP Unit tests and the linked production code are in sync
In a productive system the ABAP Unit tests are not part of the
productive program load.
(-> No performance or security drawbacks)
Which services are provided by ABAP UNIT?

ABAP Unit provides a service class CL_AUNIT_ASSERT, which contains
static methods (e.g. ASSERT_EQUALS) to compare e.g. strings or internal
tables in order to verify test results.

ABAP UNIT – Example for Test Class
PROGRAM z_abap_unit.
CLASS test_sflight_selection CLASS test_sflight_selection IMPLEMENTATION.

DEFINITION DEFERRED. METHOD setup.
CLASS demo DEFINITION CREATE OBJECT demo_ref.
FRIENDS test_sflight_selection. APPEND 'LH' TO test_carrids.
PUBLIC SECTION. APPEND 'UA' TO test_carrids.
METHODS get_carrier_flights APPEND 'AA' TO test_carrids.
IMPORTING carrier TYPE string. ENDMETHOD.
PRIVATE SECTION. METHOD test_get_carrier_flights.
DATA sflight_tab TYPE TABLE OF sflight. DATA: act_carrid TYPE string,
ENDCLASS. msg TYPE string,
sflight_wa TYPE sflight.
CLASS demo IMPLEMENTATION. LOOP AT test_carrids INTO test_carrid.
METHOD get_carrier_flights. CONCATENATE 'Selection of' test_carrid
SELECT * FROM sflight 'gives different airlines'
INTO TABLE sflight_tab INTO msg SEPARATED BY space.
WHERE carrid = 'LH'. demo_ref->get_carrier_flights( test_carrid ).
ENDMETHOD. LOOP AT demo_ref->sflight_tab INTO sflight_wa.
ENDCLASS. act_carrid = sflight_wa-carrid.
cl_aunit_assert=>assert_equals(
CLASS test_sflight_selection act = act_carrid
DEFINITION "#AU Risk_Level Harmless exp = test_carrid
FOR TESTING. "#AU Duration Short msg = msg
PRIVATE SECTION. quit = cl_aunit_assert=>no ).
METHODS: test_get_carrier_flights IF act_carrid <> test_carrid.
FOR TESTING, EXIT.
setup. ENDIF.
DATA: demo_ref TYPE REF TO demo, ENDLOOP.
test_carrid TYPE string, ENDLOOP.
test_carrids TYPE TABLE OF string. ENDMETHOD.
ENDCLASS. ENDCLASS.

ABAP UNIT – Example for Test Execution and Result

Regular Expressions
Shared Objects
Checkpoints
ABAP Editor
ABAP Debugger
ABAP Unit
Memory Inspector
Memory Inspector: Motivation
What is the Memory Inspector ?

Tool to analyze dynamic memory consumption
Why do we need the Memory Inspector ?

Increasing usage of dynamic memory objects, like
Internal Tables Strings
Class Instances (Objects) Anonymous Data Objects
Increasing number of long-running transactions
T1 T2 T3 T4 T1

Memory Inspector: Features Summary
In ABAP Debugger
TopN-Consumer-Lists
– Aggregation of types (class/data)
– Find References
Memory consumption overview
In Stand-Alone TA
Analyzing memory snapshots
Comparing memory snapshots
– Growth of memory objects in different views
Available in Release 6.20 ( SP 29, Sept.2003 )

Memory Inspector: GUI

Regular Expressions
Shared Objects
Checkpoints
ABAP Editor
ABAP Debugger
ABAP Unit
Memory Inspector
Adapting SAP Software
One of the advantages of SAP software is the

possibility to adapt the software to own
requirements and the possibility of keeping
the adaptations during upgrade.
Ways of adaptation:
Customizing
Enhancement new concept!
Modification

Evolution of SAP Enhancement Technology
Application
User Business
Exits Transaction
Events
Form
Industries
routines
Workbench
Filters
Classes
Business
Add Ins
Function
modules
Customer Kernel based
Exits Business
Add Ins
Kernel

Components of new Enhancement Framework
Enhancement options (in original system):

Part of a development object that can be enhanced
Can be explicitly defined or implicitly available
Are organized and documented in Enhancement Spots
Examples are
– BAdIs
– Parameter Interfaces of Functiongroups or Methods
– Components of Classes/Interfaces
– ABAP statements ENHANCEMENT-POINT, ENHANCEMENT-SECTION
– …
Enhancements (in follow-up system):

Switchable by Switch Framework
Support automatic Upgrade
Are organized and documented in Enhancement Implementations
Offer multilayer support

Multilayer Support of Enhancements
Core Development
Original Object
Application Development
Enhancement 1 Enhancement 2
Add On Development
Enhancement 11 Enhancement 12 Enhancement 01
Customer Development
Enhancement 121 Enhancement 201
Enhancement 001

Enhancement Spot Editor (Original System)
Organization of Predefined Enhancement Options (Source Code

Enhancements & BAdIs)
Integrated in Object Navigator (SE80)
Tab Properties & Objects common for all Enhancement Spots
Tab 3 dependent on enhancement technology: BAdIs or Source
Code Enhancements

Enhancement Implementation Editor (Follow-up System)
Organization of Enhancements
Integrated in Object Navigator (SE80)
Tab Properties & Objects common for all enhancement types
Tab 3 dependent on enhancement technology: e.g. BAdI-
Implementation or Source Code Enhancements
Enhancement Browser (Original and Follow-up System)
Tool to Search for

Enhancement Spots
Existing Enhancement Implementations
Enhancement Implementations to be adjusted after upgrade

Implicit and Explicit Enhancement Options
Features of explicit enhancement options

Defined by developer
More stable
Few changes in definition to expect
Only at valid source code locations
Target-oriented
Organized by Enhancement Spots
Features of implicit enhancement options

Defined implicitly
Enhancement of „arbitrary“ objects
No enhancement spots for management necessary

Example 1 - Source Code Enhancements
Modification-free enhancement of source code

either by
Explicit Enhancement Options
– Explicit enhancement options can be defined in source code.
– They are organized by Enhancement Spots.
Implicit Enhancement Options
– Implicit Enhancement options are available at common enhancement
places.
– Examples:
- Begin/End of Include
- Begin/End of Method/Function Module/Form Routine
- End of a structure
- End of Private/Protected/Public Section of a local class
- ...

Explicit Enhancement Options in Source Code

Enhancement by Source Code Plug-In Technology
ENHANCEMENT 1.
PROGRAM p1. WRITE ’Hello
Paris’.
WRITE ‘Hello World’. ENDENHANCEMENT.
ENHANCEMENT 2.
ENHANCEMENT-POINT ep1 SPOTS WRITE ’Hello
s1. London’.
ENDENHANCEMENT.
..
..
..
ENHANCEMENT 3.
ENHANCEMENT-SECTION ep2 WRITE ’Enhanced’.
SPOTS s1. ENDENHANCEMENT.
WRITE ’Original’.
END-ENHANCEMENT-SECTION.
Source Code Plug-Ins

Example 2 - Class/Interface Enhancements
Implicit Enhancement Options allow adding of:

optional parameters to existing methods
methods
events and event handlers
references to interfaces
Exits to existing methods
– Pre-Exit – Called at the beginning of a method
– Post-Exit – Called at the End of a method

Example 3 – New BAdIs
A new BAdI is an Explicit Enhancement Option

that:
is a predefined anchor point for Object Plug-Ins
has a well-defined interface in contrast to Source
Code Plug-Ins and is therefore more stable to changes
in the original coding
is integrated into ABAP language and has much better
performance than classic BAdIs

Usage of New BAdIs
Classic BAdI New BAdI

DATA: bd TYPE REF TO if_intf.
DATA: flt TYPE flt.
DATA bd TYPE REF TO badi_name.
CALL METHOD cl_exithandler=>
get_instance GET BADI bd FILTERS lang = `D`.
EXPORTING
exit_name = `BADI_NAME` CALL BADI bd->method
CHANGING EXPORTING x = 10.
instance = bd.
flt-lang = `D`.
CALL METHOD bd->method
EXPORTING
x = 10
flt_val = flt.

Integration of new BAdIs into ABAP Runtime
BAdIs are represented by a reference to BAdI-Handles:

DATA bd type ref to badi_name.
GET BADI bd FILTER f = 5.
If there are two implementations of badi_name that are selected for

the filter value f=5, this yields:
badi_name
bd
Inst1 Inst2 Object Plug-Ins
Cl_imp1 Cl_imp2
Regular Expressions
Shared Objects
Checkpoints
ABAP Editor
ABAP Debugger
ABAP Unit
Memory Inspector
Disclaimer
This preview is a preliminary version and not subject to your

license agreement or any other agreement with SAP. This document
contains only intended strategies, developments, and functionalities
of the SAP® product and is not intended to be binding upon SAP to
any particular course of business, product strategy, and/or
development. Please note that this document is subject to change
and may be changed by SAP at any time without notice. SAP
assumes no responsibility for errors or omissions in this document.

ABAP Language Preview – Enhanced Expression Enabling
As of next Release:
You can use computational expressions, functional methods and
built-in functions in expression positions:
– Logical expressions: a + b < oref->meth( )
– Method call parameters: oref1->meth1( oref2->meth2( ... ) )
You can use numerical expressions in numerical positions:

– Examples: DO abs( n ) + 1 TIMES.
READ TABLE itab INDEX lines( itab ) – 1 ...
You can use functional methods in functional positions:

– Examples: FIND|REPLACE REGEX oref->get_regex( ... ) IN ...
READ TABLE itab FROM oref->get_wa( ... ) ...

ABAP Language Preview – Decimal Floating Point Numbers
As of next Release:
New data types for decimal floating point numbers (based on IEEE-
754r):
– decfloat16: 8 bytes, 16 digits, exponent -383 to +384
– decfloat34: 16 bytes, 34 digits, exponent -6143 to +6144
Exact representation of decimal numbers within range (no rounding
necessary as for binary floating point numbers of type f).
Range larger than f!
Calculation accuracy like p!
Supported by new generic type decfloat, new Dictionary types,
new rounding functions round and rescale, new methods in
CL_ABAP_MATH, and new format options in WRITE [TO].

ABAP Language Preview – Internal Tables
As of next Release:
Dynamic WHERE condition:
– LOOP At itab ... WHERE (cond_syntax) ...
Secondary keys for internal tables:
– Secondary key definition:
TYPES itab TYPE ... TABLE OF ...
WITH {UNIQUE HASHED}|{{UNIQUE|NON_UNIQUE} SORTED}
KEY keynamei COMPONENTS comp1 comp2 ...
– Key specification for key access:
... WITH [TABLE] KEY keynamei COMPONENTS ...
– Key specification for index access:
... USING KEY keynamei ...
Boosting internal table performance
Real key access to standard tables
Index access to hashed tables

ABAP Language Preview – Class Based Exceptions
As of next Release:
Resumable exceptions:
– Raising a resumable exception
RAISE RESUMABLE EXCEPTION TYPE cx_class.
– Resuming (continue processing behind RAISE):
TRY.
...
CATCH cx_class BEFORE UNWIND.
...
RESUME.
ENDTRY.
Retry:
– Retrying (continue processing behind TRY):
TRY.
...
CATCH cx_class.
...
RETRY.
ENDTRY.

ABAP Development Preview – Packages
As of next Release:
Role of Packages:
– Packages encapsulate repository objects
– Reusable components must be published in package interfaces
Operational Package Concept:
– A "server package" has to expose everything that is meant for public
usage in an interface.
– A "client package" has to be allowed to use that interface.
– A "client package" has to declare the usage of that interface.
– Package checking is integrated into the ABAP compiler and ABAP
runtime and package violations are treated as ‘first order errors’.
Enhancement of ABAP Objects:
– CLASS cls DEFINITION OPEN WITHIN PACKAGE
– PACKAGE SECTION

ABAP Development Preview – ABAP Editor
As of next Release:
Code Completion:
– Suggests valid
keywords and
valid identifiers
– Invoked explicitly
by pressing special
key combination
– Autofilters result
by typed prefix
Entities completed include …
– Variables, including structures and components
– Types (including ABAP Dictionary), classes
– Methods, attributes, constants, events
– Functions
– Subroutines
– Formal parameters and exceptions of methods, functions, and subroutines
– Database tables
– Keywords
Completion suggestions may be inserted …
– Verbatim as shown
– As pattern with parameters prefilled
(CALL METHOD, CALL FUNCTION, PERFORM, …)

ABAP Development Preview – Refactoring
As of next Release:
Refactoring of ABAP programs:
– Renaming of local & global elements
– Code Extraction (convert marked code into procedure)
– Deletion of superflous declarations
– Create GET/SET-methods ...

ABAP Development Preview – Class Builder
As of next Release:
Source code based editing of global classes:

ABAP Testing Preview – ABAP Debugger
As of next Release:
New Dynpro analysis tool
New Web Dynpro analysis tool
Simple Transformation Debugging
Automated Debugging: Debugger Scripting
Layer Debugging
– Define your active software
- Packages
- Free-style expressions
– Dynamically assign your „system code“
– Layer-step through code
Miscellaneous:
– Upload of Internal Tables
– Table View: view and configure sub-components of embedded structures
– Changing long fields
– Call Stack of the internal session of the caller

ABAP Testing Preview – Coverage Analyzer
As of next Release:
Code Coverage
measured on statement
level
Condition Coverage for
logical expressions
Coverage of empty
branches
Statement results
visualized using new
ABAP Edit Control
Integrated to ABAP
Unit

ABAP Testing Preview – Runtime Analysis
As of next Release:
Controls based UI
(like ABAP Debugger)
Multiple Tools on
Customizable
Desktops
More flexible and
powerful Analysis
Tools
Trace Data stored on
Database (Server and
Platform independant)
Cross
System/Release Trace
Comparison

ABAP Connectivity Preview – bgRFC & LDQ
As of next Release:
directly
tRFC
bgRFC
Sequencing:
Processed by Type “T” or Type “Q”
Scheduler Serialization:
RFC Protocol
qRFC
LDQ
No-Send Sequencing:
Scenario Type “Q”
Serialization:
XML or binary

ABAP Connectivity Preview – Alternatives to tRFC & qRFC
As of next Release:
Optimized alternatives for tRFC, qRFC, and qRFC No-Send:
bgRFC (Background RFC)
– CALL FUNCTION IN BACKGROUND UNIT oref (TYPE REF TO IF_BGRFC_UNIT)
– Remote Function Calls are recorded, and execution takes place at a later point in
time, which is controlled automatically by a scheduler process.
– The execution scales with O(n*log(n)), i.e. linear-logarithmic, which is determined
by the I/O system only.
– The inbound procedure is executed at the caller system and serves for load-
balancing purposes.
– The outbound procedure is executed at the receiver system and serves for de-
coupled, remote system environments with load-balancing at the receiver.
LDQ (Local Data Queue)
– Persistency layer to provide first-in first-out (queue) access to data.
– Receiver actively pulls data from such a queue, similar to a mailbox.
– Access is locally within one SAP system.
– The data model of LDQ is absolutely de-coupled from any RFC database tables.

ABAP Connectivity Preview – Quality of Services
As of next Release:
RFC Communication
– Binary asXML serialization replaces the different RFC serialization concepts, e.g.
“xRFC”.
- Available for ABAP Application Server, Java Application Server, and
SAP NetWeaver RFC SDK
– SAP NetWeaver RFC SDK replaces the classic RFC SDKs for ASCII and Unicode.
- Homogeneous handling of all RFC parameter types.
- Compatible with all backend system variants R/3, mySAP, …
- Classic RFC SDKs are still maintained.
RFC-based SAP J2EE Connectivity

– SAP Java Resource Adapter compliant with JCA 1.5 replaces the direct usage of
the SAP JCo API.
- Supports stateful connections and callback connections.
- Provides shareable client connections for increased robustness and scalability .
- SAP JCo API within SAP J2EE is still maintained.
– IDoc class library for SAP J2EE simplifying the handling of SAP IDocs.

Regular Expressions
Shared Objects
Checkpoints
ABAP Editor
ABAP Debugger
ABAP Unit
Memory Inspector
THANK YOU FOR YOUR
ATTENTION !
QUESTIONS – SUGGESTIONS – DISCUSSION

Feedback
Please complete your session evaluation.
Be courteous — deposit your trash,

and do not take the handouts for the following session.
Thank You !

Further Information
Public Web
www.sap.com
SAP Developer Network:
http://www.sdn.sap.com/sdn/developerareas/abap.sdn
SAP Help Portal: http://www.help.sap.com
ABAP Keyword-Documentation
Transaction ABAPHELP, always the first source of information
Related Workshops/Lectures at SAP TechEd ’06

All lectures and workshops about ABAP

Copyright 2006 SAP AG. All Rights Reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information
contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,
Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned
are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications
may vary.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose
without the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended
strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited
to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use
of these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use
of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party
Web pages.

ABAP New Features PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ABAP New Features PDF

Uploaded by

Copyright:

Available Formats

An Overview of the

New Features in ABAP

© SAP AG 2006, SAP TechEd ’06 / CD200 / 2

As a result of this lecture, you will have an

© SAP AG 2006, SAP TechEd ’06 / CD200 / 5

Regular Expressions (Regexes, REs) are more powerful than

– Made popular by Unix tools: grep, sed, awk, emacs

ABAP supports POSIX regular expressions as of Release 7.00

© SAP AG 2006, SAP TechEd ’06 / CD200 / 7

Regular expressions are built from

Prepending \ turns operators into literals

REs match or represent sets of text strings

REs are commonly used for searching text

Usually interested in left-most, longest match contained in text

© SAP AG 2006, SAP TechEd ’06 / CD200 / 8

What is the main difference betweens file system wildcards

files: * = sequence of characters

pat pat+ *pat p#*t

written as regular expressions?

pat pat. .*pat p\*t

© SAP AG 2006, SAP TechEd ’06 / CD200 / 9

Name Operator Matches

© SAP AG 2006, SAP TechEd ’06 / CD200 / 10

Name Operator Matches

© SAP AG 2006, SAP TechEd ’06 / CD200 / 11

New addition REGEX to the FIND statement:

Detailed match information is available with RESULTS addition.

© SAP AG 2006, SAP TechEd ’06 / CD200 / 12

New addition REGEX to the REPLACE statement:

Search works exactly as in FIND.

© SAP AG 2006, SAP TechEd ’06 / CD200 / 13

Parentheses structure complex expressions

tick*tock* (tick)*(tock)* (ticktock)*

Store submatches for later reference

Non-registering parentheses (?:…) do not store submatch

© SAP AG 2006, SAP TechEd ’06 / CD200 / 14

The replacement string can refer to submatches of match being

DATA: html TYPE string,

html = `<title>This is the <i>Title</i></title>`.

REPLACE ALL OCCURRENCES OF REGEX regx

Result: <title>Th<b>i</b>s <b>i</b>s the <i>T<b>i</b>tle</i></title>

© SAP AG 2006, SAP TechEd ’06 / CD200 / 15

ABAP Objects provides two classes for using REs

© SAP AG 2006, SAP TechEd ’06 / CD200 / 16

CL_ABAP_MATCHER Instance Methods

find_next( ) find next unprocessed match

replace_found( new ) replace match found by new *)

replace_next ( new ) find and replace next unprocessed match

get_match( ) return match information (MATCH_RESULT) *)

get_submatch( n ) return n-th submatch *)

get_offset( [n] ) return offset of current (sub)match *)

get_length( [n] ) return length of current (sub)match *)

find_all( ) return all remaining matches

replace_all( new ) replace all remaining matches

*) throws exception if no current match stored

© SAP AG 2006, SAP TechEd ’06 / CD200 / 17

CL_ABAP_MATCHER Class Methods

create( pattern text ) create and return matcher object

matches( pattern text ) returns abap_true if pattern matches text

contains( pattern text ) returns abap_true if text contains pattern

get_object( ) returns matcher object containing match

© SAP AG 2006, SAP TechEd ’06 / CD200 / 18

There are two ways of setting up objects for RE processing

pat pat+ pat p#t

pat pat. .pat p\t

ticktock (tick)(tock) (ticktock)*