note 03 07 transaction se16 risk and control

3
7/21/2019 Note 03 07 Transaction SE16 Risk and Control http://slidepdf.com/reader/full/note-03-07-transaction-se16-risk-and-control 1/3  Seite 1 von 3 NOTE M  ARCH 2007 Transaction SE16 –risk and control The transaction code SE16 in combination with critical authorizations allows some highly critical steps within a SAP® system. For this example you call the transaction code SE16,  and enter the table name TGSB  to the selection field. After selecting one special entry via double click, you will then get e.g. the following window displayed: The table fields are currently protected against maintenance. [This is represented by the grey colour]. In this next view the debugging function is activated via corresponding entry of /h  to the command line [/h  – enter ]. In the next step the string CODE is entered to the Field name  and EDIT to Field contents.  After that the Pencil  Button is activated and the settings are saved.  At this moment an additional authorization check based on the object S_DEVELOP for activity 02 [replace/change] is executed.

Upload: writeme670

Post on 07-Mar-2016

220 views

Category:

Documents


0 download

DESCRIPTION

Transaction SE16 Risk and Control

TRANSCRIPT

Page 1: Note 03 07 Transaction SE16 Risk and Control

7/21/2019 Note 03 07 Transaction SE16 Risk and Control

http://slidepdf.com/reader/full/note-03-07-transaction-se16-risk-and-control 1/3

 

Seite 1 von 3

NOTE M ARCH 2007

Transaction SE16 –risk and control

The transaction code SE16  in combination with criticalauthorizations allows some highly critical steps within a SAP®system.

For this example you call the transaction code SE16,  andenter the table name TGSB  to the selection field. Afterselecting one special entry via double click, you will then gete.g. the following window displayed:

The table fields are currently protected against maintenance.[This is represented by the grey colour].

In this next view the debugging function is activated viacorresponding entry of /h to the command line [/h – enter ].

In the next step the string CODE is entered to theField name

 and EDIT to Field contents. After that the Pencil Button is activated and the settings aresaved. At this moment an additional authorization check based on theobject S_DEVELOP for activity 02 [replace/change] isexecuted.

Page 2: Note 03 07 Transaction SE16 Risk and Control

7/21/2019 Note 03 07 Transaction SE16 Risk and Control

http://slidepdf.com/reader/full/note-03-07-transaction-se16-risk-and-control 2/3

 

Seite 2 von 3

 After saving of the adjustments, and running of the functionF8, the corresponding field entries are opened formaintenance.

 A test change is executed and saved

This event is logged within the SysLog [SM21].

The event ID is  A19 change of field content for  A14 program,line, and event.

But you will not be able to trace the former setting of the field.

Page 3: Note 03 07 Transaction SE16 Risk and Control

7/21/2019 Note 03 07 Transaction SE16 Risk and Control

http://slidepdf.com/reader/full/note-03-07-transaction-se16-risk-and-control 3/3

 

Seite 3 von 3

This is also valid for the transaction codes based on SE16 that

have a table directly assigned, like e.g.:

SE16RFCDESSECUSE16T000SE16TXCOMSECUSE16USR40SE16USRACLSE16USRACLEXTSE16V_T599RSE16W3TREESSE16WWWFUNCSE16WWWREPSSE16_ANEASE16_ANEKSE16_ANEP

SE16_ANLASE16_ANLCSE16_ANLPSE16_ANLZSE16_BKPFSE16_BSEGSE16_BSIDSE16_BSIKSE16_BSISSE16_ECMCASE16_ECMCTSE16_KNA1SE16_KNB1SE16_LFA1SE16_LFB1

SE16_MARASE16_MARCSE16_RFCDESSECUSE16_SKA1SE16_SKB1SE16_T000SE16_T807RSE16_TCJ_CHECK_STACKSE16_TCJ_CPDSE16_TCJ_C_JOURNALSSE16_TCJ_DOCUMENTSSE16_TCJ_POSITIONSSE16_TCJ_WTAX_ITEMS

SE16_TXCOMSECUSE16_USR40SE16_USRACLSE16_USRACLEXTSE16_V_T599RSE16_W3TREESSE16_WWWFUNCSE16_WWWREPS