User mapping

[Former Member]

Hi all,

How to setup user mapping in portal 7.0?.

did anyone encounter false conflicts in compliance calibrator,if yes, how was it resolved.?

Does anyone of you have list of criticial transactions and what should not be given in production.

Thank you,

[Former Member · Accepted solution]

Hi,

Please see below. User mapping in portal 70, for ldap configuration check sap help

Link: [http://help.sap.com/saphelp_nw04/helpdata/en/09/c5ee407552742ae10000000a155106/frameset.htm]

and list of critical transactions check the below

SOX- Critical Transactions

TCode

Risk Description

CA87

Mass Replace Work Center

CAT6

Human Resources

CL04

Delete Class

F.34

Credit Limit Mass Changes

F.80

Mass Reversal of Documents

F044

Vendor Archiving

FI12

Change House Banks/Bank Accounts

IP30

Run Date Monitoring

LN08

Number range maint.: LVS_LENUM

MMPV

Close Periods

MMRV

Allow Posting to previous Period

PA20

Display HR Master Data

PA30

Maintain HR Master Data

PA70

Fast Entry

PA97

Compensation Administration - Matrix

PFCG

Role Maintenance - System integrity, stability at risk

RZ04

Maintain SAP Instances

SA38

ABAP Reporting -Can run programs not protected appropriately

SARA

Archiving Management - Should be restricted to Archive Admin

SCC1

Client Copy - Special Selections

SCC4

Client Admin. - System stability & integrity at risk

SCC5

Delete Client - System stability at risk

SCC6

Client Import - System stability & integrity at risk

SCC9

Remote Client Copy - System stability & integrity at risk

SCCL

Local Client Copy - System stability & integrity at risk

SE01

Transport Organizer - System stability & integrity at risk

SE11

Data Dictionary Maint. - System stabiltiy & integrity at ris

SE13

Maintain tech tables settings - System stabilitiy at risk.

SE16

Data Browser - Exposure to confidential information

SE37

Function Builder

SE38

ABAP Editor - System stabiltiy & integrity at risk

SM01

Lock Transactions - System stabiltiy at risk

SM02

System Messages - Should be restricted to System Admins only

SM30

Table Maintenance - System integrity & stability at risk

SM49

Execute OS commands - System stability at risk

SM50

Work Process overview - System stability at risk

SU01

User Maintenance - Should be restricted to User Admins only

SU02

Profile Maintenance - System stability and integrity at risk

SU03

Maintain Authorizations

SU05

Maintain Internet user

SU10

User Mass Maint - System stabilty at a very high risk

SU20

Authorization Object fields

SU21

Authorization Objects

SU24

Maintain Assignment of Authorization Objects

SU25

Profile Generator Upgrade and First Installation

[jurjen_heeck]

> Does anyone of you have list of criticial transactions and what should not be given in production.

1- How would you ever know a list given on a forum is complete? I've glanced over the list provided and since it is so short it must be incomplete. SE16 has a new brother called SE16N with similar risk. All the query tools are missing from this list as well.....

2- Security is about a lot more than (dis)allowing transactions. Some transactions in the list already provided are only dangerous in combination with too wide underlying authorizations. Even worse, if the underlying authorizations are too wide, disallowing the transaction will not help at all.