Sap Basis Intro
-
Upload
gyanendr-singh -
Category
Documents
-
view
309 -
download
3
Transcript of Sap Basis Intro
-
8/2/2019 Sap Basis Intro
1/38
1
HCC 2006 ERP Technology 79
Introduction to the SAP BasisTechnologies
Background Jobs
Andr Faustmann
Ronny Zimmermann
Ma debur 07.03. 09.03.2005
HCC 2006 ERP Technology 80
OverviewOverview
Background Jobs
Introduction
Job Steps
Start Conditions Background Jobs
Job Defining
Job Monitoring
-
8/2/2019 Sap Basis Intro
2/38
2
HCC 2006 ERP Technology 81
OverviewOverview
Background Jobs
Introduction
Job Steps
Start Conditions Background Jobs
Job Defining
Job Monitoring
HCC 2006 ERP Technology 82
Motivat ion for Back ground ProcessesMot ivat ion for Back ground Processes
Reduction of workload that runs on the dialog processes
The long running transaction or programms, that blocks the dialogprocess for users will now run at the background
Background processes facilitate a plan of single or periodicallyrecurring activities in the SAP system
Notes: Parameter rdisp/wp_no_btc defines the number of background
processes of an instance There is no minimum number on the background processes,
HOWEVER minimum 2 are necessery by the application of transportmanagement system
-
8/2/2019 Sap Basis Intro
3/38
3
HCC 2006 ERP Technology 83
Background JobBackground Job
A background job consists of oneor more steps
A step could be:
ABAP Program
external command
external program
A background job is alwayshandled by exactly onebackground process
Priorities of BackgroundJobs:
1. Class A with target server2. Class A w/out target server
3. Class B with target server
4. Class B w/out target server
5. Class C with target server
6. Class C w/out target server
Background Jobs arereleased by:
Defined start point oftime
Events
HCC 2006 ERP Technology 84
Procedure of Back ground JobProcedure of Back ground Job
Dispatcher
Database
Scheduling Tables Data tables
XXX XXX XXX XXX
XXX XXX
XXXXXXXXXXXXXXX
Dispatch
Job1 A ... ... ...
Job2 C ... ...
Dialogprocess
Back-ground
process 1
Back-ground
process 2
Central Instance Background Instance
Dispatcher
DispatchDialogprocess
Back-
groundprocess 1
Back-
groundprozess 2
Back-ground
process n
M
August04
D M D F S S
1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
3 0 3 1
M
August 04
D M D F S S
1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
3 0 31
Job Scheduler runs everyrdisp/btctime seconds on
each instance
-
8/2/2019 Sap Basis Intro
4/38
4
HCC 2006 ERP Technology 85
Job StepJob Step
ABAP Report: When ABAP report doesnt have selection screen, then only report
itself will be declared
If theres one (or more) selection screen available, then one optionmust be declared
External Command: An external command will be defined in system by SAP system
administrator
External command will be maintained in transaction SM69, whichmeans that all executed programs and all belonging parameters will besaved
Definition in SAP system builds the mechanism of SAP authorizationconcepts
External Program: An arbitrary (undefined) program on operation system level will be
executed.
HCC 2006 ERP Technology 86
Star t Condi t ions for Back ground JobsStar t Condi t ions for Back ground Jobs
Time based
Prompt start once or periodical
at periodical executionexceptions are feasible
To a Point of Time once or periodical
at periodical executionexceptions are feasible
Upon a certain working daysin a month once or periodical
Event based
After an event once or periodical
with or w/out parameter
After a background job
status independent At switching the operation mode
(e.g. Day / Night)
Parameter rdisp/btcnamedefines the instance for eventprocessing
M
August04
D M D F S S
1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30 31
-
8/2/2019 Sap Basis Intro
5/38
5
HCC 2006 ERP Technology 87
Event mainta inersEvent mainta iners
There are two types of events: SAP-Events should not be modified or deleted
User-Events created and maintained by system administrator
Remarks for Events: Events are maintained with transaction SM62
Events can be specified with parameters
There are three options to release events:1. With transaction SM64 for test purposes
2. In ABAP-Code by using function BP_EVENT_RAISE
3. At operating system level via the programs sapevt
Profile parameter rdisp/btcname commits which SAP instancesystem is responsible for the event handling
HCC 2006 ERP Technology 88
Def ine Back ground Jobs (1)Def ine Back ground Jobs (1)
Steps to define background jobs:1. Assign job names
2. Commit priority and target server (optional)
3. Define job step
4. Add further job step (optional)
5. Commit start conditions
6. Save job definition
7. Release job
Background jobs associate with transaction SM36
All mentioned steps can also be accomplished with job wizard
For re-use of defined job steps, copy background jobs
-
8/2/2019 Sap Basis Intro
6/38
6
HCC 2006 ERP Technology 89
Sta tusSta tus eineseines Background JobsBackground Jobs
planned
released
ready
aktive
cancelfinish
Job is saved (with or w/outstart conditions)
Job complete released andwaits for options given by jobdispatcher
Job selected and waits forexecution conducted by abackground process
Job executed by a backgroundprocess
Job ended
successfully
Job cancelled
with failures
HCC 2006 ERP Technology 90
23:00Server 2CJob7
23:00Server 1BJob6
23:00CJob5
23:00CJob4
23:00AJob3
23:00CJob2
23:00Server 1CJob1
ScheduledTarget ServerClassName
Server 1
Server 2
D-WP
D-WP
B-WP
B-WP
B-WP
D-WP
D-WP
D-WP
B-WP
B-WP
Workload BalancingWorkload Balancing
-
8/2/2019 Sap Basis Intro
7/38
7
HCC 2006 ERP Technology 91
In te r fac ingIn te r fac ing
BAPI
RFC
OLE Automation
HCC 2006 ERP Technology 92
BAPI
Business Application Programming Interface
RFC
Remote Function Calls
OLE Automation Object Linking and Embedding
Direct database access
Read only
Batch Input
EDI
Programming InterfacesProgramming Interfaces
-
8/2/2019 Sap Basis Intro
8/38
8
HCC 2006 ERP Technology 93
BCBC
BO BO BO
BC
BO BO
BAPI BAPI BAPI BAPI BAPI BAP I BAPI
Client-
Component
BAP I BAP I
Client-
Component
BAPI
ALE
Business Application Programming Interface (BAPI)Business Application Programming Interface (BAPI)
HCC 2006 ERP Technology 94
Basis
Pre defined Business Objects
Consisting of object structure
Example: customer order
Access methods
Example: Customer_order_create
Stored in Business Object Repository (BOR)
BAPIBAPI
-
8/2/2019 Sap Basis Intro
9/38
9
HCC 2006 ERP Technology 95
Connction of external programs
Distributed scenarios
Internet applications
Workflow applications
UsageUsage
HCC 2006 ERP Technology 96
Pros
Easy to handle
No change on SAP system necessary
Well defined interfaces
Cons Depends on SAPs developments
Up to now only few BAPIs available
Pros and ConsPros and Cons
-
8/2/2019 Sap Basis Intro
10/38
10
HCC 2006 ERP Technology 97
R/3 System
ABAP Program ABAP Program
RFC interface
R/3 System External System
ABAP-Program
External
Programm
RFC interface RFC interface
...
CALL FUNCTION XY
EXPORTING...
IMPORTING...
...
FUNCTION XY.
ENDFUNCTION.
Remote Function CallsRemote Function Calls
HCC 2006 ERP Technology 98
Synchronous RFC
Calling program waits until function call was executed and returned requiredresults
Asynchronous RFC
Calling program runs parallelly and independently with remote function
Programmer is responsible for processing of results
Availability of system must be assured
Transaktionaler RFC
Different functions are assigned to a transaction
Runs as LUW
Availabiliy of system may be not valid
VariantsVariants
-
8/2/2019 Sap Basis Intro
11/38
11
HCC 2006 ERP Technology 99
Pros
All ABAP function can be employed
Simple and flexible handling
Cons
ABAP knowledge required
Changes inside system
Pros and ConsPros and Cons
HCC 2006 ERP Technology 100
Frontend SAP System
PC Program
PC Program
SAP GUIABAP Program
Function moduleOLE
serv
er
Function module
Function module OLE
client
OLE AutomationOLE Automation
-
8/2/2019 Sap Basis Intro
12/38
12
HCC 2006 ERP Technology 101
For integration of office applications
Availability of OLE functions in R/3-Sytem as types specifiedindependently from programming languages
Methods, attributes, parameters
R/3 can be client or server
OLE EmploymentOLE Employment
HCC 2006 ERP Technology 102
R/3 as OLE client
Desktop application is called from ABAP Program
OLE statements are transferred as RFCs via SAPGUI to PC
SAPGUI converts RFC to OLE call
R/3 as OLE server R/3 funktions are called via OLE from Desktop
Call is sent to dispatch SAP automation server
Conversion of call to RFC
Return of results via SAP automation server
OLE Client and ServerOLE Client and Server
-
8/2/2019 Sap Basis Intro
13/38
13
HCC 2006 ERP Technology 103
Pros
Simple integration of office applications
No change to R/3 is necessary as long as no self programmed OLEservers are applied
Cons
Proprietary access
Microsoft Office
SAPGUI
Pros and ConsPros and Cons
HCC 2006 ERP Technology 104
OverviewOverview
Backup, Restore and Recovery
Excursion Oracle
Backup
Restore and Recovery
Hardware and Software in HCC Magdeburg
-
8/2/2019 Sap Basis Intro
14/38
14
HCC 2006 ERP Technology 105
OverviewOverview
Backup, Restore and Recovery
Excursion Oracle
Backup
Restore and Recovery
Hardware and Software in HCC Magdeburg
HCC 2006 ERP Technology 106
DBMS Archi tectureDBMS Archi tecture
-
8/2/2019 Sap Basis Intro
15/38
15
HCC 2006 ERP Technology 107
Processes in OracleProcesses in Oracle
HCC 2006 ERP Technology 108
Oracle Memory StructuresOracle Memory Structures
-
8/2/2019 Sap Basis Intro
16/38
16
HCC 2006 ERP Technology 109
TablespaceTablespace ConceptConcept
HCC 2006 ERP Technology 110
1
2
3
4
/origlogA
/origlogB
/mirrlogA
/mirrlogB
Online Redo Log
Wri t ing f rom Data and Log Fi lesWri t ing f rom Data and Log Fi les
/sapdata1...
/sapdata6
DBWR -> all 3 sec. LRU Blocks
CKPT -> all changed Blocks
8KB
Database buffer pool Redo log buffer
5000 5200
before after
LGWR at commit, buffer 30% voll
...
ARCH
Control Files
/oraarchOffline Redo Log
-
8/2/2019 Sap Basis Intro
17/38
17
HCC 2006 ERP Technology 111
OverviewOverview
Backup, Restore and Recovery
Excursion Oracle
Backup
Restore and Recovery
Hardware and Software in HCC Magdeburg
HCC 2006 ERP Technology 112
BackupBackup Why?Why?
16. Januar 2003
Data lost + Downtime!
External factors (Fire, Water, Rats...)
Physical failures (Hardware breakdown)
Operational failures (Delete tables from database, ...)
System failures (Bringing in support packages, ...)
A proper backup avoids data lost and minimize systemdowntime!
-
8/2/2019 Sap Basis Intro
18/38
18
HCC 2006 ERP Technology 113
How does backup w ork?How does backup w ork?
1. File-Backup database
2. File-Backup SAP-Executables
3. File-Backup operating system
For an Offline-Backup !
SAP Systems based on some reasons will not be turned off!
A database in which a normal backup data runs where the saveddatabase is inconsistence and can not recovered!
The safety device is no longer employed for a restore!
HCC 2006 ERP Technology 114
MethodsMethods
Backup-Methods
Export (logical) Data safety (physical)
online offlineSaving the database
contents andstructures
DB online
Migration, datatransport, data re-organisation
Saving table spaces
DB online and inARCHIVELOG mode
Recovery until the lastclosed transaction
Saving Tablespaces
DB offline and inNOARCHIVELOG mode
Recovery until the lastsavings
-
8/2/2019 Sap Basis Intro
19/38
19
HCC 2006 ERP Technology 115
Procedure of Onl ineProcedure of Onl ine --BackupBackup
Transakt
ionen
Begin backup, table space in backup mode
End backup, table space in normal mode
Redo Log Files
HCC 2006 ERP Technology 116
Procedure of Onl ineProcedure of Onl ine --Backup I I .Backup I I .
Transactions
Backup DB-Files
Begin Backup End Backup
Check point
Bevor backup:Time stamps of check points will be written in theheader of database file
During backup:Transactions and check points goes along thebackups, where all saved objects refer to the check points of timewhen backup started
After backup:Time stamps and check points will be written againin the header of database files
-
8/2/2019 Sap Basis Intro
20/38
20
HCC 2006 ERP Technology 117
SAP Database Back up ToolsSAP Database Back up Tools
Control file Data files Online redo log files Offline redo log files
BRBACKUP BRRESTORE BRACHIVE
BACKINT
Tape Tape
LOG LOG
HCC 2006 ERP Technology 118
Log Sequence Num ber (LSN)Log Sequence Num ber (LSN)
Each redo LOG file consists an LSN
LSN will be serially, uniquely numbered which is for recovery verymeaningful
Online Redolog
116
Current log sequence number = 116
Redo Log File, that is currently online
115
114
113 112
Oldest online log sequence number = 115
Redo Log File, that was lastly archived
When the online backup is starting, the number of the last archivedredo log files must be recorded. This number defines the beginning ofarchived redo log files. All older archived redo log files are notimportant for the currently running backup.
-
8/2/2019 Sap Basis Intro
21/38
21
HCC 2006 ERP Technology 119
115
115
Offl ine Redo Log Fi leOff l ine Redo Log Fi le
Online Redo Log Files
115
115
115
115
/oraarch
ARCHIVED
SAVED
COPIED
DELETED
Tape
Tape
Offline redo log file will be savedtwice
HCC 2006 ERP Technology 120
Consistenc y Onl ineConsistenc y Onl ine--DBDB --BackupBackup
All database files are saved exactly with time stamp of the last checkpoints at the beginning of backup
All accumulated redo log files during the backup are saved
A control file is saved
Parameter files of DB are saved
Generated log-files during the backup are saved
Good chances for recovery
-
8/2/2019 Sap Basis Intro
22/38
22
HCC 2006 ERP Technology 121
OverviewOverview
Backup, Restore and Recovery
Excursion Oracle
Backup
Restore and Recovery
Hardware and Software in HCC Magdeburg
HCC 2006 ERP Technology 122
SAP Database Back up ToolsSAP Database Back up Tools
Control file Data files Online redo log files Offline redo log files
BRBACKUP BRRESTORE BRACHIVE
BACKINT
Ultrium Tape Ultrium Tape
LOG LOG
-
8/2/2019 Sap Basis Intro
23/38
23
HCC 2006 ERP Technology 123
Restore and Recovery Scenar iosRestore and Recovery Scenar ios
There are different scenarios of restore and recovery:
Partial Restore and Complete Recovery
Database Reset
Point in Time Recovery (Full Restore and Incomplete Recovery)
Full Restore and Complete Recovery
HCC 2006 ERP Technology 124
Exam ple: The CrashExam ple: The Crash
-
8/2/2019 Sap Basis Intro
24/38
24
HCC 2006 ERP Technology 125
Example: Par t ia l Restore and Complet e RecoveryExample: Par t ia l Restore and Complet e Recovery
HCC 2006 ERP Technology 126
Example: Database ResetExample: Database Reset
-
8/2/2019 Sap Basis Intro
25/38
25
HCC 2006 ERP Technology 127
Example: Point in Tim e RecoveryExample: Point in Tim e Recovery
HCC 2006 ERP Technology 128
Example: Ful l Restore and Complete RecoveryExample: Ful l Restore and Complete Recovery
-
8/2/2019 Sap Basis Intro
26/38
26
HCC 2006 ERP Technology 129
Hold back and re lax !Hold back and re lax!
What to do when database doesn't work anymore? Do not take any immediate decision
Study the problem calmly and in-depth
Formulate a way out strategy
Before data refining:Discover what could solve the problem
Is there enough discs space to save and restore data?
Is an hardware extension potentially important?
Are the data systems and system assembly alright?
Are backups available?
Are offline redo log data available?
Perform a complete saving of defected database
HCC 2006 ERP Technology 130
OverviewOverview
Backup, Restore and Recovery
Excursion Oracle
Backup
Restore and Recovery
Hardware and Software in HCC Magdeburg
-
8/2/2019 Sap Basis Intro
27/38
27
HCC 2006 ERP Technology 131
Secur ing hardw are in HCC MagdeburgSecur ing hardw are in HCC Magdeburg
HP Surestore 10/180 180 Ultrium-Tapes with each 200 GB capacity
10 Ultrium-Drives (approx. 70 GB pro hour)
4 Brocade-Switchs (Fiber glass connection maschine Roboter)
5 Bridges (Connection from drives (each 2 pro bridge))
1 Monitoring computer
Manage independently the tapes in the library
HP Surestore 20/700 Last disassembly 700 Ultrium-Tapes with each 200 GB capacity
20 Ultrium-Drives (approx. 70 GB pro hour)
4 Brocade-Switchs (Fiber glass connection maschine Roboter)
1 HP Blade Runner (Transform fiber glass to the drives)
1 Monitoring computer
HCC 2006 ERP Technology 132
Secur ing sof tw are in HCC MagdeburgSecur ing sof tw are in HCC Magdeburg
HP-Dataprotector 5.0 Enable saving, managing and recovering from UNIX-Backups
Online-Extension: Integration of SAP Systems; HP Dataprotector takeover BACKINT the controll of SAP DB-Tools
Comfortable monitoring and reporting
HP Ignite Problem: UNIX-Protection from HP Omniback for a bootable restore of a
maschine is unneeded
Enable saving, managing and recovering from operating systems (HP-UX 11.00, HP-UX 11.11, HP-UX 11.23)
Installation from servers with help of image data as pull-off system froma ready configured system
-
8/2/2019 Sap Basis Intro
28/38
28
HCC 2006 ERP Technology 133
HCCHCC--Team in Act ionTeam in Act ion
HCC 2006 ERP Technology 134
Requi rementsRequi rements -- in HCC Magdeburgin HCC Magdeburg
Each SAP System must be saved at least once a week
Offline redo logs of each SAP systems must be saved daily
Offline redo logs must be saved optional to the system load hourly
Data system of the machines must be saved one a week
Backups will be kept save every 4 weeks
-
8/2/2019 Sap Basis Intro
29/38
29
HCC 2006 ERP Technology 135
Pro Syst emPro Syst em in HCC Magdeburgin HCC Magdeburg
DatabaseData Files ~116 GB (IDES) (25 GB 245 GB)
Online Redo Log Files 240 MB (bis 6.x 80 MB)
Control File bis 20 MB
DB Profiles einige KB
Offline Redo Log Files 60 MB (bis 6.x 20 MB)
UNIX
SAP Executables ca. 500 MB
UNIX 6 GB 70 GB
Ignite 1 1.5 GB
HCC 2006 ERP Technology 136
In HCC Magdeburg ... (St andIn HCC Magdeburg ... (St and JanuarJanuar 2005)2005)
74 UNIX-Systems
108 SAP Systems (R/3 Release 4.6C, 4.70 (Enterprise), Retail, BW 3.10 /SEM 3.20, APO 3.10, WAS 6.20, SAP Solution Manager 3.10, SAP CRM4.0, SAP BW 3.50 / SEM 3.50)
108 Systems with offline redo logs with each two protections
20 Drives
450 Tapes with 200 GB disk space = 90 TB
Retention period 4 weeks
Protection in different Pools
Cyclus: 7 days + offline redo logs after emergence
Consider the Physics!
-
8/2/2019 Sap Basis Intro
30/38
30
HCC 2006 ERP Technology 137
PhysicsPhysics
Protection for BRARCHIVE should not wait for too long, otherwisearchiver stuck threats (in 51 minutes ORAARCH can be full)
A drive should not only responding to the directly connected maschine,cos switches could be overloaded
More backups can be parallel executed
When switches are surely free then a backup can be splited at moredrives (big IDES systems)
10 drives are used for BRBACKUP and UNIX-protections
10 drives are used exklusively for BRARCHIVE protection
HCC 2006 ERP Technology 138
Pro tec t ion and Vo lumesProtec t ion and Volumes
Continuous backups and independent redo log files of archive-indexfull stand Kontinuierliches Backup der Redo Log Files in Abhngigkeit vom
Fllstand des Archiv-Verzeichnisses
Continous backups and independent redo log files from full stand ofarchive-indexes
Daily backup for all redo log files
Weekly onlie-backup for all SAP-databases beween 9 pm and 2 am(approx. 10TByte/Week is equivalent to 1.4 Tbyte/Day)
Weekly protection for SAP data, DB data and operating system data(executables, configuration, etc.) (approx. 1225 Gbyte/Week isequivalent to approx. 175 Gbyte/Day)
Weekly Ignite-protection all servers (approx. 175 Gbyte/Week)
Total volume of all savings: approx. 50 Tbyte (is equivalent to 4 weeksstorage time)
-
8/2/2019 Sap Basis Intro
31/38
31
HCC 2006 ERP Technology 139
Real izat ionReal izat ion
Backup plan for online protection consistency Backup plan for UNIX-protections
Script, that initiates offline redo log protection towards index full stand
Script, that saves daily the SAPARCH-indexes of all R/3-Systems
Pools for different protection specifications
Monitoring and Reporting
Backup-Plan
HCC 2006 ERP Technology 140
Rout ineRout ine--TasksTasks
Are backups executed?
Are archive-index emptied?
Is a band jammed? Why?
Do drives must be cleared?
Are tapes in a pool full?
Do tapes need to be changed, due to aging?
Regular restore and recovery-exercises!
.
.
.
-
8/2/2019 Sap Basis Intro
32/38
32
HCC 2006 ERP Technology 141
Repositories
R/3 Repository
ABAP Dictionary
HCC 2006 ERP Technology 142
Definition Meta-IS where all meta information which are relevant for system
development are storedProcess models
Data models
Programs
WorkflowsTables
...
RepositoriesRepositories
-
8/2/2019 Sap Basis Intro
33/38
33
HCC 2006 ERP Technology 143
Definition Meta-IS where all meta information which are relevant for system
development are storedProcess models
Data models
Programs
Workflows
Tables
...
RepositoriesRepositories
HCC 2006 ERP Technology 144
Meta-Information system for Transactions
Consists of ABAP programs
Meta InformationDescription of semantics of tables, views and ABAP programs
Business Objects
Encapsulated business objects including access methodsData strutures (in ABAP dictionary)
Relational database tables
Views
The R/3 RepositoryThe R/3 Repository
-
8/2/2019 Sap Basis Intro
34/38
34
HCC 2006 ERP Technology 145
Two level domains
Table SPFLI
MANDT CONNIDCARRID ... ...AIRPFROM AIRPTO ...
Domain S_AIRPID
Data element S_FROMAIRP Data element S_TOAIRP
The ABAP DictionaryThe ABAP Dictionary
HCC 2006 ERP Technology 146
User Management
Basics
Privilegs, Roles and Profiles
-
8/2/2019 Sap Basis Intro
35/38
35
HCC 2006 ERP Technology 147
Hundreds or thousands of users are working at one system With different
Tasks
Intentions
Requirements regarding data safety and security
OnThousands of data fields
User managementUser management
HCC 2006 ERP Technology 148
Privileges rule the rights to access to data fields Select, insert, update, delete
Data fields are offered by dynpros
Dynpros implement steps of transaction
Transactions are called through SAP Easy Access Menu
Direct input of transaction codes
...
PrivilegesPrivileges
-
8/2/2019 Sap Basis Intro
36/38
36
HCC 2006 ERP Technology 149
User name
NOT developxx
Naming conventions necessary
Password
No distinction of upper and lower case input
Length between 3 and 8 characters
All characters including numbers, space and special symbols areaccepted
First three characters may not include space and the must not beidentical
DDIC, PASS and SAP* are not accepted
The first three characters must be different from user name
Password may not begin with ! or ?
Password can be changed anytime, but only once a day
User IdentificationUser Identification
HCC 2006 ERP Technology 150
User groups Organizational collection of users, e. g.
All users of a department
All participants of a lecture
Profiles
Collection of privilegesAll privileges of a manager
All privileges of a clerk
Roles Collection of menu options
User and Privilege StructuresUser and Privilege Structures
-
8/2/2019 Sap Basis Intro
37/38
37
HCC 2006 ERP Technology 151
User
Iscopyof
Usergroup
ProfileRole
Access
object
Privileg
Data ModelData Model
HCC 2006 ERP Technology 152
Privileges Roles
Profiles
User
Assignments
User Maintenance (Version 1)User Maintenance (Version 1)
-
8/2/2019 Sap Basis Intro
38/38
HCC 2006 ERP Technology 153
Roles
Generateprofile
Assignusers
User Maintenance (Version 2)User Maintenance (Version 2)
HCC 2006 ERP Technology 154
Application Service Providing
Services of ASP
Service Level Agreements
Service Levels
Service Level Reporting