Professional Documents
Culture Documents
Version 2.0
02.04.2001
SAP AG
Neurottstr. 16
D-69190 Walldorf
Copyright
Copyright 2001 SAP AG. All rights reserved.
Neither this document nor any part of it may be copied or reproduced in any form or by any
means without the prior written consent of SAP AG.
The information contained in this document is subject to change or revision without prior
notice.
Contents
1 GLOSSARY ............................................................................................................... 4
1 Glossary
CRM
Customer Relationship Management.
Object Type
The object type is the meta information about the data. A synonym for object type is object
class, e.g. the definition of business partner is an object type.
Object
An object is an entity of an object type. It exists of methods and attributes. E.g. business
partner # 123356 is an object of object type business partner.
Attribute
An attribute is the smallest unit processed by an application, like number or string values.
Authorization object
An authorization object is a logical object used to protect functionality or data in the CRM
system.
Authority check
2 General Design
1. The CRM online scenario authorizations will be configured by using the R/3 basic
standard tools. The check of authorizations will be done in the programs by using
the ABAP ‘Authority-Check’ command in the implementation.
2. In the CRM Mobile scenario SAP introduces a flexible technology which allows to
model the customer requirements on authorization without doing changes to the
code. Authorization maintenance is done by using the Authorization Management
Tool (AMT). More information regarding the Mobile technology is provided in the
CRM Mobile Authorization concept functional description.
In a later release SAP will provide a download facility to download the available
authorization information from the online system to the mobile client.
Level Description
1 The (business) object type is protected with regards to one or a
combination of the five standard activities (create, change, display,
delete, permit). The authorization is checked by starting a program
processing the business object.
2 The (business) object type is protected depending on an attribute
value (i.e. order type). The authorization is checked as soon as the
(business) object is processed. The authorization object itself could
contain more than one attribute (e.g. order type and credit card).
3 The business object type is protected depending on an attribute and
by an organizational unit. This could be configured for a single
organizational unit e.g. sales organization, sales office or sales group.
4 The business object instance (e.g. sales order #123456789) is
protected by an authorization check.
The following figure describes how the levels of authorization protect (business) object
data in the system.
In the table below you can find the authorization objects available in CRM 2.0C.
More detailed documentation of these objects is available within the online system
documentation (Transaction SU21; Object class CRM for CRM Components and
AAAB for Business Partner).