Tag Archive | note
March 6, 2014  

SAP: Mass deletion of roles – using a standard program

Mass changed in role management is never easy and usually no standard solutions for it exists. Before I found the standard approach I always used and LSMW or eCatts – But a standard “out of the box” solution is always better!

SAP note 313587 explains the process

It’s easy – and only takes the below steps to complete.

  1. Open the suggested sourcecode in the file Z_DEL_AGR.txt
  2. Create a report with the suggested code
  3. Create a transport
  4. Add the roles you want to delete to a transport
  5. Delete the roles using the report
  6. Release the transport to the other systems
  7. Done! all roles in the transport have now been removed from the systems :)

 

 

February 24, 2014  

SAP: Table Access Management

A small change with big effect fra SAP has come in the area of table security.

SAP standard solution for table security has always been to group tables into authorization groups, which users then where granted access to using object S_TABU_DIS. Thereby granting access to all tables in the authorization group. For many years this has been the only standard solution for management of table authorizations.

A clear disadvantage has always been; what criteria should the table groups be based on? Criticality? Business area? Or something else? Regardless, management of the table groups means spending many resources on management of the table structure.

SAP’s solution is the introduction of security management on table name basis. So instead of grouping tables in authorization groups and then granting access to them, SAP has now made it possible to utilize S_TABU_NAME and directly assigning access to a specific table.

FANTASTIC!

See SAPs description in the below link or OSS note 1481950

http://help.sap.com/saphelp_nw73/helpdata/en/4c/a0ac7a68243b9ee10000000a42189b/frameset.htm

“To also protect tables that are not assigned to an authorization group, you can also use the authorization object S_TABU_NAM. It is integrated into the authorization check of the central function module VIEW_AUTHORITY_CHECK. In this case, the system first checks S_TABU_DIS. If this authorization check is not successful, the system also checks S_TABU_NAM.”