NOTE MARCH 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,
NOTE FEBRUARY 2007

Transaction code SE16N - risk and control

The transaction code SE16N [report RK_SE16N] offers some options for table maintenance activities, if the corresponding authorizations are assigned as well.
But together with this risk, SAP® provides an integrated control that can be used for review.
First of all we have to understand how the maintenance activities can be executed:
1. Call the transaction SE16N.
NOTE NOVEMBER 2006

Rollenmenüdesign - Redundanzvermeidung

Sofern Rollen aus verschiedenen Transaktionen und ggfs. auch verschiedenen Rollen zusammengestellt werden, besteht ein Problem in den auftretenden Redundanzen innerhalb des Benutzermenüs.
Um dies zu vermeiden besteht die Möglichkeit eine Redundanzvermeidung zu aktivieren. Ergänzend besteht die Möglichkeit Menüeinträge sortieren zu lassen.
NOTE OCTOBER 2006

How to adapt authority-check in reports

The procedure concerning the integration of an authority check
to an ABAP/4® report is  basically as described.
In this example a SAP standard program is copied
into the customer name space, and modified to
meet the company specific needs.

1. Copy the SAP Standard program into
the customer name space:
The original program is the report RSUSR003,
the name of the copy in this case e.g. is ZZ_RSUSR003.
NOTE SEPTEMBER 2006

How to add an authorization object to a
customer created transaction code


Call the transaction SU24 / SU22 to start the maintenance.

The transaction in this example currently consists of only one
authorization object (S_TCODE) and is not listed
in the table USOBT_C yet.

Select the transaction you want to maintain.
 
NOTE AUGUST 2006

Table of content for an authorization concept -
with additional focus on HR

1.    Target / Scope
2.    Premise
2.1.    Protection of Data being transmitted across state and
           international borders 
           [Non-violation of local  and export laws]
3.    Function structure
NOTE JULY 2006

The matching authorization


It is of no importance whether the matching authorization results from a profile in a role or a manually created profile. That means that the origin of a matching authorization is of no relevance.

I. Our first test case for a better understanding.
The following authorization is required for a successful pass of the authority-check:

for authorization object     F_LFA1_APP
NOTE JUNE 2006

The authorization check for dialog users
Short introduction to the basic mode of operation

One has to deal with the following three steps.

I.
The user enters a transaction code like for example FK01.

Initially SAP® checks if the called transaction code is valid (comparison with table entries in table TSTC), it is also evaluated if the transaction code is locked (via SM01 e.g.)
NOTE MAY 2006

Der Expertenmodus zur Profilgenerierung

Über die Drucktaste Expertenmodus kann aus verschiedenen Bearbeitungsmodi gewählt werden.

1.    Profil und Berechtigungen löschen und neu anlegen
        Bei Auswahl dieser Option werden sämtliche vorhandenen
        Informationen gelöscht, alle getätigten Einstellungen gehen verloren.
NOTE APRIL 2006

Eine Frage, die einem Prüfer im SAP® FI hin und wieder gestellt wird, lautet:

In welchem Paragraphen steht eigentlich genau, dass es keine Lücken in den Belegnummern für die Finanzbuchhaltung geben darf?

Gleich vorweg – einen solchen Paragraphen gibt es nicht.
Die Gesetzgebung hat generelle Anforderungen formuliert, ohne dabei
explizit auf konkrete technische Anforderungen oder Sachverhalte einzugehen.
Alles andere wäre in unserer Zeit der kurzen Innovationszyklen und der
‹ Previous
Showing 61 - 70 of 72.
Next › Last »