0

New Concepts

Contents:
 Personalization
 Enhanced Name Ranges
 Namespaces
 New Terminology

 SAP AG 1999

© SAP AG D446AW 2-1

0.2
New Concepts: Unit Objectives

At the conclusion of this unit, you will be able to:

 Describe the personalization options of R/3

 List the advantages of prolonged names in
ABAP
 Describe the new Namespaces
 List the new names in the ABAP Workbench

 SAP AG 1999

© SAP AG D446AW 2-2

0.3
New Concepts: Overview

Good Bye
Enhancements
and Modifications
1 12 1 Course Overview

BAPIs
1
New Concepts
0
9 1

2 3
News in ABAP
ABAP Objects Workbench

ABAP Language

4
Graphical Query
8

Tools
7 5
Screen Objects 6 Logical Databases

ABAP Dictionary

 SAP AG 1999

© SAP AG D446AW 2-3

0.4
Personalization Levels

Enterprise:
 Enterprise structure
 Business processes
TOP-DOWN configuration

User role User roles:

configuration  Area menus
 Role-based menus
 Transaction variants
Area Role-based menus Transaction
Role-based
menus menus variants Personal
configuration:
Personal configuration  Favorites
 Links
 Desktop links
Favorites Links Desktop

 SAP AG 1999

 The SAP System adjusts itself to the user's style of working: When the system is started, the users
are only offered functions that are typical in their daily work. There is no unnecessary navigating
through functions that are not used. In the past, user menus could be called in the Session Manager
or in the dynamic menu in R/3. With Release 4.6A, the role-based menu is output in the form of a
tree for each user.
 When you select a function, it is started in the same session. This function replaces the role-based
menu. The role-based menu appears again automatically when you leave a transaction or when you
start a new session.
 In the maintenance screen for activity groups (Transaction PFCG), the administrator can combine the
menu structure for an activity group consisting of transactions, reports, and Internet/Intranet links to
a user menu. You can choose any structure and description for the functions contained.
 The enterprise menu is no longer available with Release 4.6A.

© SAP AG D446AW 2-4

0.5
Description of the Work Center

Which
Which programs?
programs?

Required
Required menus?
menus?

Required
Required authorizations?
authorizations?

Which
Which colleagues?
colleagues?

Area menu
Role-based menu
 SAP AG 1999

 Typical questions at a work center are:

 What function should be performed at this work center?
 Which menus are needed?
 What authorizations do the users need?
 Which users are involved here?
 The goal of personalization is to answer these questions in the R/3 System.
 The tools provided by R/3 for this purpose are area menus and activity groups.
 We will now see how these tools can be used to adapt the work center to the user's needs as
effectively as possible.

© SAP AG D446AW 2-5

0.6
Area Menus

 Options:
Define as start menu
Add to activity groups
Integrate old report trees
 Consist of:
Transactions
References to other area menus
Executable programs
Lists created by programs

 SAP AG 1999

 Area menus were also included prior to this release. They can contain:
 Transactions
 References to other area menus
 Executable programs (new)
 Lists created by programs (new)
 From this release onwards, you can include programs in area menus that create lists directly.
 You can assign users an area menu as their start menu. These users no longer see the complete SAP
menu when they log onto R/3, but only the menu items that they require. By integrating the report
trees, users obtains a complete view of their work environment.
 Area menus can also be linked to activity groups.

© SAP AG D446AW 2-6

0.7
Area Menus: Objects

 Transactions
Sample menu
Transaction 1  ABAP programs that create lists
Transaction 2  SAP queries
 Sub-tree
Item 1  Different types of reports
Item 2 Related lists
 Area menu
 Node 2  References to area menus
 Node 3

First report
ABAP report
Other report

 SAP AG 1999

 In contrast to previous releases, area menus are displayed in tree form starting with Release 4.6. This
gives the user a clearer overview of the available options.
 The objects that can be included in the area menu are listed in the right part of the graphic.

© SAP AG D446AW 2-7

0.8
Creating Area Menus

Create
Create

Name
Name of
of the
the
Area Menu Maintenance area menu
area menu

Area menu Favorites

Favorites management

 Tools --> ABAP Workbench

--> Development --> Other tools --> Area menus
 SAP AG 1999

 Use Transaction SE43 to create an area menu. You can call this transaction with the given path.
 Assign a name in the corresponding customer namespace and create the area menu.
 You can include the area menus in your list of favorites in the GUI for faster editing at a later time.

© SAP AG D446AW 2-8

0.9
Maintaining Area Menus: Important Functions

 Insert entry:
 one level down
Edit Area Menu
 at same level
 Change entry
 Delete entry
Sample menu
Transaction 1
Transaction 2 Area type
 Sub-tree
ABAP report Report Writer
Item 1 SAP query Research
Item 2 TA with variant Report notes

 Area menu ABAP report

 Node 2 Report
 Node 3 Variant

Transaction code

Generate automatically

 SAP AG 1999

 You build area menus by creating entries in the tree structure. Position the cursor and choose the
corresponding icon for insertion at the same level or one level down. In the popup window that now
appears, choose a description and the corresponding transaction code.
 You can also insert reports (objects that create lists, such as ABAP programs, queries, and so on)
 You can no longer store lists in report trees as of Release 4.6A. Report trees have been integrated in
the new area menus.
 With List--> Save --> Report tree you can store lists for the program. Since the lists are stored
program-specifically, you can display them in the corresponding area menus.

© SAP AG D446AW 2-9

0.10
Area Menus: Migration of Earlier Techniques

Earlier area menus

Menu 1 Menu 2 Menu 3 New area menus
Transaction
Transaction11
Transaction Sample menu
Transaction22
Sub-tree Sub-step Transaction 1
Sub-tree Sub-step11
Sub-step Transaction 2
Area
Areamenu
menu Sub-step22
 Sub-tree
Sub-step 1
Sub-step 2
Earlier report trees  Area menu
Info
Infocatalog
catalog  Node 2
First report  Node 3
ABAP report
Other report First report
List 1 ABAP report
List 1 Other report

 SAP AG 1999

 During an upgrade, existing area menus are automatically migrated to the new structure. You can
make further entries in these new area menus.

© SAP AG D446AW 2-10

0.11
Role-Based Menus

Role-based Authorization
menus profiles

Role-based Authorization
menus profiles

 SAP AG 1999

 With Release 4.6, SAP has implemented user-oriented R/3 operations. When the R/3 application is
started, a tree structure appears in the initial screen containing the entries the user needs for his daily
work.
 These role-based menus go beyond the scope of the area menus. Only the menu structure can be
defined for area menus. You can define them as you like for role-based menus. They also use the
functions of the Profile Generator.
 By using specific role-based menus you can set the following individually:
 Menu structure
 Profiles
 User assignments
 The term "activity group" is synonymous in R/3 with "role-based menu." You can edit activity
groups using the Profile Generator.

© SAP AG D446AW 2-11

0.12
Activity Groups: Work Steps

SAP menu
Office
Logistics Create activity group
Accounting
Human resources
Information systems Build menu
Tools
ABAP Workbench
Accelerated SAP Maintain authorizations
Administration
...
Data coll. WB WB
Assign users
WEB development
...

 SAP AG 1999

 Before you create your own activity groups, you should evaluate the predefined workplace examples
that SAP delivers in Release 4.6A. You can use these workplace examples just as they are delivered
in the SAP System.

 Delivered activity groups should not be changed. You can combine several activity groups to form a
composite activity group. which may also include activity groups delivered by SAP.

© SAP AG D446AW 2-12

0.13
Creating Activity Groups

Create activity group

SAP Easy Access Build menu
Create menu
Maintain authorizations

Favorites Assign users

SAP menu
Office
Logistics
Accounting Activity group maintenance
Human resources
Information systems
Tools
ABAP Workbench Activity group
Accelerated SAP Description
Administration
...
Data coll. WB WB Display Change Create
WEB development

 SAP AG 1999

 To create an activity group, choose the appropriate button on the initial R/3 screen.
 Assign a name for the activity group in the customer namespace and press Create. The system
displays the maintenance screen for activity groups.
 The activity group naming conventions are defined as follows:
 SAP* delivered by SAP
 Rest customer namespace

© SAP AG D446AW 2-13

0.14
Activity Groups: Build Menu

Create activity group

Build menu
SAP menu
Maintain authorizations
 Office
Assign users
 Logistics
 Accounting
 Human resources  Single entries
 Information systems Transaction
 Tools Report
 ABAP Workbench

Web address
Accelerated SAP
 Administration  From other menus:
...
from SAP menu
Data coll. WB
 WEB development from activity group
... from area menu

 SAP AG 1999

 There are several ways to build the menu for your activity group. You can copy sub-trees and menu
entries from
 the SAP menu
 another activity group
 an area menu
 You can also maintain single entries. These can be
 a transaction code
 a report in which a transaction code is automatically generated
 a hyperlink (e.g. web address or a path on the local machine)
 You cannot maintain single entries if it is a composite activity group.

© SAP AG D446AW 2-14

0.15
Activity Groups: Maintain authorizations

Maintain authorization data and generate profiles Create activity group

Build menu
Change authorization data Maintain authorizations

Assign users

 List of authorization objects

 Proposed values for authorizations
 Individual maintenance of authorizations
 Deactivation of authorization objects
 Insertion of further authorization objects

Generate profile

 SAP AG 1999

 The system determines the authorization objects used in the given transactions. The assignment of
single authorization objects for a transaction using Transaction SU22 provides the basis for this
determination.
 Transaction SU22 also specifies for the particular authorizations whether or not:
 there must be a check
 there are default values
 Using these default values makes maintaining authorizations much simpler. You only have to
maintain authorizations marked with the yellow icon. If you do not do so, full authorization is
automatically given.
 In the last step, a profile is generated from your entries. The system proposes a name T-<number>,
which you can change here, but not later on. Enter a meaningful name.

© SAP AG D446AW 2-15

0.16
Activity Groups: Assign Users

Create activity group

User Build menu

Maintain authorizations

Assign users
TESTUSER Mr. User Test

Add
Add user
user

Adjust
Adjust user
user master
master

Adjust user

 SAP AG 1999

 Next assign the relevant users to the activity group.

 Once you have assigned the users, you must adjust the user master profiles accordingly. The profile
that was created is automatically assigned to the given users.
 A user can be assigned to more than one activity group. Each time you change an activity group, you
must also adjust the user masters again.

© SAP AG D446AW 2-16

0.17
Using Delivered Activity Groups

User

User

STONE Mike Stone

TESTUSER User Test

Adjust user
 SAP AG 1999

 SAP delivers more than one hundred preconfigured activity groups. Choose the one most suitable for
the particular work center and assign the users. Adjust the user master records.
 You can change activity groups delivered by SAP. However, these changes are lost during an
upgrade. We therefore recommend that you copy the delivered activity groups and adjust the copy.

© SAP AG D446AW 2-17

0.18
Name range Extension I

 Important Name range extensions in ABAP Dictionary

Maximum
Object Type Old name length
new name length
Tables 16 10
Table fields 16 10
Database views 16 10
Structures 30 10
Structure fields 30 10
Domains 30 10
Data elements 30 10
Search helps 30 —

 SAP AG 1999

 As of Release 4.0, SAP provides development namespaces for Repository objects, which can be
reserved and used exclusively by SAP partners and customers (see below).
 To extend the old namespaces, the object names were extended, meaning that all existing
applications which themselves manage and process Repository object names need to make
adjustments. You also need to consider that as a result of adding namespace prefixes, object names
can contain slashes "/" (even in the first position).

© SAP AG D446AW 2-18

0.19
Name range Extension II

 Other important name range extensions

Maximum
Object Type Old name length
new name length
Development classes 30 4
Programs 30 8
Function Groups 26 4
Transactions 20 4
Logical databases 20 3

 SAP AG 1999

 See also the following notes

 0016466 Customer namespace for SAP objects
 0038781 Partner name space SAP objects
 0084282 Development namespaces for customers and partners
 0089898 Extending namespace in 4.0: Effects
 0105132 Reservation of namespaces as of R/3 Rel.4.0
 0150451 Setting up development namespaces
 and notes referenced therein.

© SAP AG D446AW 2-19

0.20
Name spaces

/PARTNER/RSTUVL /COMPANY/FBLGPU
/namespace/object_name

/SAPALE/ZRETURN /1BCDW/JKTELOIS

 Used to uniquely identify development objects

 Variable object name length possible (maximum 10 character
name space prefix)
 Name spaces begins and ends with a “/” character - no more
than two “/” allowed
 Second character in name space cannot be a number (name
spaces in the range /0. . ./ to /9. . ./
are reserved by SAP for generated objects)

 SAP AG 1999

 Name spaces are identifiers assigned exclusively by SAP, which enable SAP customers, SAP
partners and SAP to develop R/3 components and products on the basis of R/3 applications without
the risk of name conflicts (when delivering to external R/3 systems or importing external products
into internal systems).
 To ensure that a name space can be used exclusively by its owner, the name space identifier can only
be used as a prefix in the object name if the name space is maintained in the name space table in the
system, and has a valid development license.
 External systems (for example, customer systems of the SAP partner to whom the name space
belongs) into which objects with a prefix were imported, only allow changes to name space objects if
a repair license was entered. This is a repair license that the name space owner has received from
SAP and can pass on to customers, if necessary.
 Objects in the ABAP Workbench are assigned to a name space by placing the reserved name space
prefix in front of the object name.
 The name space identifier begins and ends with a "/" (as a delimiter), is a maximum of 10
characters and is included as part of the new extended name lengths. For example, using the name
space /EXAMPLE/ you can create a program with the name /EXAMPLE/PROGRAM.
 Objects in your name space can be assigned to either local (a development class beginning with $)
or test development classes (a development class beginning with T) or they must belong to
development classes which start with the name space prefix.

© SAP AG D446AW 2-20

0.21
System change options

 SAP AG 1999

 The system change options define whether Repository objects and client-independent Customizing
objects are globally modifiable. If they are globally modifiable, you can specify for each software
component or namespace whether it can be modified.
 To reach the system change option, you can use the organizer tools (transaction SE03). Alternatively,
you can reach it from the Transport Management System (Transaction STMS) by choosing Overview
 Transport Routes  Environment  System change option.
 For each R/3 System, the customer can define whether the objects contained in the namespaces and
name ranges may be changed.
 To enable objects to be changed, the R/3 System must not be globally locked to changes.
 To set the system change option, you require administration authorization in CTS. This authorization
is normally S_CTS_ADMIN.
 If you want to change objects in your customer name range, select the Modifiable column in the
Customer name range line. This customer name range includes, for example, all reports beginning
with Z or Y.
 If local or private objects are to be created or edited in your R/3 System, the name range Local
objects must be set to Modifiable.

© SAP AG D446AW 2-21

0.22
Changes to Basis Terminology

Old name Name in 4.0 Name in 4.6

ABAP/4 ABAP
ABAP/4
ABAP Workbench
Development Workbench
ABAP/4
ABAP Objects
runtime environment
Object Browser Repository Browser Object Navigator

Function Library Function Builder

ABAP/4 Editor ABAP Editor

ABAP/4 Dictionary ABAP Dictionary

 SAP AG 1999

© SAP AG D446AW 2-22

0.23
New Concepts: Unit Summary

You are now able to:

 Describe the personalization options of R/3
 List the advantages of prolonged names in
ABAP
 Describe the new Namespaces
 List the new names in the ABAP Workbench

 SAP AG 1999

© SAP AG D446AW 2-23

 New Concepts Exercises

Unit: New Concepts

Topic: Creating a development class

For correct development you need a development class.

1-1 Create a development class.

1-1-1 The development class should be named ZD346AW_##. (## = group
number).
1-1-2 Assign the development class to the instructor’s Change request.

0.24

© SAP AG D446AW 2-24

 Exercises

Unit: Personalization
Topic: Create and enhance area menus, create user
roles

At the conclusion of this exercise, you will be able to:

Create an area menu that you will use as initial screen for the rest
of the training course. This area menu will contain all the entries
you need for working efficiently during the course. This includes
both the transactions specific to this course and all the
transactions of the ABAP Workbench.

Only some R/3 functions will be actively used at a work center.

The user should therefore only see a small selection of the
transactions of the complete R/3 menu.

1-1 How do I create an area menu?

1-1-1 Which transaction / menu path can be used to create area menus? Include
the transaction in your list of favorites.
1-1-2 Create an area menu called ZD346AW_##. Adhere to the naming
convention (## = group number).

1-2 Create a folder "Application programs" in the structure you created.

1-2-1 Create entries for the following topics that you will use during the training
course:
Transaction BC425_##.
1-2-2 Create another folder named "Development" and include the following
transactions: SHD0, SPRO, PFCG, SE80.
1-2-4 Enter the area menu you created as the start menu in your user fixed values.
What does your start menu look like when you start a new session?
1-2-5 Check your results.

© SAP AG D446AW 2-25

 2-1 Create a user role.
2-1-1 Which transaction can be used to create a user role? How can you get there
quickly?
2-1-2 Create a user role named ZD346AW_## (## = group number).
2-1-3 Include the area menu you created in the user role.
2-1-4 Create a new folder. Insert the program SAPBC425_BOOKING_## here.
It is not the aim of this training course to fully explain the
SAP authorization concept. In this exercise we will simply
create a menu that can be used as a user-specific menu,
without maintaining the profile.

2-1-5 Maintain the authorization data: Assign full authorization for the displayed
sub-trees.
Assign full authorization by selecting the corresponding
traffic light icon for the relevant sub-tree.

2-1-6 Insert authorization object S_CARRID in the authorizations manually.

Assign the following authorization here:
Actions All
Airline Everything except
for U*
2-1-7 Assign your user this user role. Adjust the user master records.
2-1-8 Check your results. What options do you now have to start transactions?
The changes take effect immediately. Create a new session to
see the changes in the initial menu. Check your user in the
user maintenance screen (SU01).

0.25

© SAP AG D446AW 2-26

 New Concepts Solutions

Unit: New Concepts

Topic: Creating a development class

1-1-1 Create a development class called ZD346AW_##.

 On the main R/3 screen, choose Tools -> ABAP Workbench -> Overview ->
Object Navigator.
 On the menu, choose Workbench -> Other Objects.
 On the Other Tab screen, click on Development Class and enter ZD346AW_##.
 Click on the Create icon.
 Type in the Description for the object, choose ZIDE as the transport layer and
choose BC as the Application Component. Save your work.

1-1-2 Assign the development class to the Change Request given by your
instructor.
 On the Change Request screen, click on the Create icon.
 Type in the Description for the object and click on Save.
 Click on the green arrow on the Change Request screen.
 On the Object Navigator screen, click on the list drop down box and choose
Development Class. Click on the Display icon to see your development class.

© SAP AG D446AW 2-27

 Solutions

Unit: New Conepts

Topic: Creating area menus

1-1 You can create an area menu by choosing the following menu path in the SAP
menu:
Tools  ABAP Workbench  Development  Other tools  Area menus
1-1-1 Alternatively you can choose Transaction SE43. Choose the menu path
System  User profile  Expand favorites to include the transaction in
your list of favorites.
1-1-2 Enter area menu name ZD346AW_## and press Create. Adhere to
the naming convention (## = group number).

1-2 Create the folder ‘Application Programs’ using the corresponding pushbutton or
menu entry.
1-2-1 Enter the transaction code SE80 in the right column: After you confirm your
entry by pressing Enter, the short text for the transaction is displayed.
1-2-2 Create another folder ‘Development’. Insert transactions SE11, SE31,
SHD0, SPRO, PFCG in the list.
1-2-3 Position the cursor on the root node and choose Insert. Enter transaction
code S001 and set attribute "Reference". Complete the entry.
1-2-4 Choose the menu path System  User profile  Own data to define the
area menu as start menu. You can no longer go to the SAP menu.
1-2-5 Create a new session. If you choose "SAP Menu", the menu you defined as
start menu is displayed.

2-1 Creating a user role (activity group).

2-1-1 Choose the corresponding pushbutton "Create menu" in the initial screen or
the entry in the area menu you created or choose transaction code PFCG.
2-1-2 Create an activity group named ZD346AW_## an (## = group number).
Give it a short description and maintain the description of the activity group.
2-1-3 Include the area menu you created in the activity group.
2-1-4 Create a new folder. Insert the program SAPBC425_BOOKING_## by
choosing the pushbutton "+Report".

© SAP AG D446AW 2-28

 2-1-5 Maintain the authorization data: Choose the appropriate tab title. Choose
"Change authorization data". A list with a tree-like structure appears. The
individual sub-trees have a yellow traffic light. Give full authorization for
the displayed sub-trees by selecting the traffic light and confirming the next
modal dialog box.
2-1-6 Insert authorization object S_CARRID by choosing pushbutton "+Manual".
The object appears in an appropriate sub-tree which now has the attribute
"manual". Expand the sub-tree and maintain the field values:
Field name or data class Values
Action *
Airline A to T*
V to Z*
Save the authorizations. Copy the profile name. Generate the profile.
2-1-7 Choose tab title "User". Enter your user D346AW-##. Save your entry.
Adjust the user master records by selecting the right pushbutton.
2-1-8 Create a new session. You can now toggle between the user menu and the
SAP menu.

© SAP AG D446AW 2-29