Ansicht
Dokumentation

Software Maintenance Process (SMP) Authorizations ( RELNGG_31H_SMPAUTHORZTNS )

CL_GUI_FRONTEND_SERVICES - Frontend Services   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Short text

Software Maintenance Process (SMP) Authorizations

Description

This note describes how to implement SMP authorizations for release 1.3A and later versions of the IS-Software (IS-SW) product. No SMP authorizations were implemented for release 1.2B and earlier versions of the IS-SW product.

Delivered authorization profiles

S_SMP Authorization profile for all SMP activities (included

in SAP_ALL and SAP_NEW)

S_SMP_EX1 Authorization profile for SMP example 1 (see below)

S_SMP_EX2 Authorization profile for SMP example 2 (see below)

S_SMP_EX3 Authorization profile for SMP example 3 (see below)

Authorization Objects Field Possible Values
V_SMPA_VAR variant user defined
V_SMPA_FUN smp_funct rels - release
delt - delete
pend - suspend
decl - decline
V_SMPA_TCD tcd OK29, OK31, OK32
V_SMPA_ACT variant user defined
actvt 01 - create
02 - edit
03 - display
06 - delete
59 - distribute (connect)

Authorization check used in each process

Process V_SMPA_VAR V_SMPA_FUN V_SMPA_TCD V_SMPA_ACT
Execute selection X X
process (OK31)
Process order due X X
list (OK32)
Maintain profile/ X X
variant (OK29)
Customize
OK28

Standard authorization profile for all SMP activities (S_SMP)

A user:

• can execute all variants in the selection process (OK31)

• can use all functions in the order due list (OK32)

• can use all transactions

• can maintain all variants (OK29)

The standard authorization profile looks like this:

Authorization Object Field Given Values Auth. Name
V_SMPA_VAR variant * V_VAR_ALL
V_SMPA_FUN smp_funct * V_FUN_ALL
V_SMPA_TCD tcd * V_TCD_ALL
V_SMPA_ACT variant * V_ACT_ALL
actvt *

Authorization Profile for Example 1 (S_SMP_EX1)

A user (s_smp_ex1):

• can execute all variants in the selection process (OK29)

• can use all functions except delete in the order due list (OK32)

• can use all transactions

• can only display all variants (OK29)

Authorization profile S_SMP_EX1 looks like this:

Authorization Object Field Given Values Auth. Name
V_SMPA_VAR variant * V_VAR_ALL
V_SMPA_FUN smp_funct pend, rels, decl V_FUN_NODEL
V_SMPA_TCD tcd * V_TCD_ALL
V_SMPA_ACT variant * V_ACT_DISP
actvt 3

Authorization Profile for Example 2 (S_SMP_EX2)

A user (s_smp_ex2):

• cannot execute selection process (OK31)

• can use all functions in the order due list (OK32)

• can only use transactions (OK29) and (OK32)

• can change or delete only variants C++ and SWP01 and display and
  connect all other variants (OK29)

Authorization profile S_SMP_EX2 looks like this:

Authorization Object Field Given Values Auth. Name
V_SMPA_VAR variant doesn't matter
V_SMPA_FUN smp_funct * V_FUN_ALL
V_SMPA_TCD tcd OK29, OK32 V_TCD_TWO
V_SMPA_ACT variant C++, SWP01 V_ACT_EX2_1
actvt 02, 06
V_SMPA_ACT variant * V_ACT_EX2_2
actvt 03, 59

Authorization Profile for Example 3 (S_SMP_EX3)

A user (s_smp_ex3):

• can only execute variants C++ and SWP01 (OK31)

• can use all functions in the order due list (OK32)

• can use all transactions

• can only maintain and display variants C++ and SWP01 (OK29)

Authorization profile S_SMP_EX3 looks like this:

Authorization Object Field Given Values Auth. Name
V_SMPA_VAR variant C++, SWP01 V_VAR_TWO
V_SMPA_FUN smp_funct * V_FUN_ALL
V_SMPA_TCD tcd * V_TCD_ALL
V_SMPA_ACT variant C++, SWP01 V_ACT_EX3
actvt 02, 03, 06, 59

Tips

• V_SMPA_VAR is relevant only if OK31 is in V_SMPA_TCD.

• V_SMPA_FUN is relevant only if OK32 is in V_SMPA_TCD.

• V_SMPA_ACT is relevant only if OK29 is in V_SMPA_TCD.

• In V_SMPA_ACT, if actvt only has the value of 01, then it does not make sense to specify a variant.

• If one variant in a profile cannot be executed, then the profile
  cannot be executed.

Damage caused to data by errors

Software/hardware requirements

Installation information

Effects on System Administration

Effects on Customizing

Effect on batch input

Changes to the Interface

Changes in procedure

Procedure for removing dataset errors

Dependent functions

Planning

Further notes

ROGBILLS - Synchronize billing plans   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 8540 Date: 20240520 Time: 200727     sap01-206 ( 51 ms )