This website is not affiliated with, sponsored by, or approved by SAP AG.

Limiting access to old posting documents

SAP Security

Moderators: thx4allthefish, Snowy, jurjen

Limiting access to old posting documents

Postby andrestone » Sat Feb 27, 2010 4:12 am

I would like to restrict (using authorization) access to view old posting documents created before 2010. All organization data (company code, chart of accounts) were not changed, so there is no option to use common know authorization objects... also I could not archive all of the documents, as some users still need easy access to them. Any input really appreciated.

andrestone
 
Posts: 4
Joined: Sat Feb 27, 2010 4:07 am

Re: Limiting access to old posting documents

Postby Al. » Mon Mar 01, 2010 1:54 am

Hi Andre,

I spotted this on ITToolbox but it seems that you don't have any answers yet.

First of all, what is the background to this requirement? It is a "want to have" or is it legally required?

Generally this will be difficult to achieve fully through standard mechanisms. The most common way of dealing with this situation is to perform a copy into another client/system and then archive the docs in your production system. Anyone who needs access to the historical information is granted an appropriate login into the backup system until the point at which the data is no longer required.

More recently I have seen the SAP SLO (system landscape optimisation) team reallocate these docs to a new company code in your existing system. You can then grant access to these docs based on their new company code.
http://www.turnkeyconsulting.com/
Al.
 
Posts: 3031
Joined: Tue Feb 25, 2003 5:35 am
Location: London

Re: Limiting access to old posting documents

Postby andrestone » Fri Mar 05, 2010 5:01 am

Business logic is quite simple: CFO does not want all of the users to be able to see all accounting documents from previous years... only few should be able to see them... ...
andrestone
 
Posts: 4
Joined: Sat Feb 27, 2010 4:07 am

Re: Limiting access to old posting documents

Postby Al. » Mon Mar 08, 2010 1:04 am

As it is not an important (i.e. legal) requirement then in my opinion your best approach is to copy the data to another client and then archive.
The costs of supporting another system that you may already have in your landscape will likely be less than changing standard SAP transactions and reworking your roles to meet this strange requirement.
http://www.turnkeyconsulting.com/
Al.
 
Posts: 3031
Joined: Tue Feb 25, 2003 5:35 am
Location: London


Return to SAP Security

Who is online

Users browsing this forum: No registered users and 7 guests




This website is not affiliated with, sponsored by, or approved by SAP AG.