topic Help required SARA in Application Development and Automation Discussions

Help required SARA

Former Member — Fri, 14 Nov 2008 22:35:48 GMT

Hi All,

we have a requiremnet where we need to give authorization for SARA T-Code but need to disable the actions write and delete buttons in that screen(that we get when when we execute SARA Tcode).

Thanks in Advance

Reagrds

Anand

Re: Help required SARA

Former Member — Sat, 15 Nov 2008 03:12:13 GMT

Hi,

tcode SARA itself is build to do archive process, which is :

- write to archive file

- delete data from system that is completely stored in archive file during write process.

if you wish to disable two core function of SARA, so why you assign SARA to that user ?

if you wish your user only able to READ archived data, you can using SARI (archive information system) or ask your ABAP to create Z-program to read data from archive. But there is SAP standard program which is able to read both archived data or non-archived data (live data) in a single transaction code.

rgds,

Alfonsus Guritno

Re: Help required SARA

Former Member — Sat, 15 Nov 2008 13:26:11 GMT

Hi Gurinto,

Thanks for the info.

you are right we want the user to read only and donot do any write and delete activities.

can you please expalin the below statement and can you please provide the standard program.

"But there is SAP standard program which is able to read both archived data or non-archived data (live data) in a single transaction code"

Aannd

Re: Help required SARA

Former Member — Sun, 16 Nov 2008 08:40:44 GMT

> can you please expalin the below statement and can you please provide the standard program.

> "But there is SAP standard program which is able to read both archived data or non-archived data (live data) in a single transaction code"

Like Alfonsus said. There are also more than just one program for this, as many wil offer the option of reading it's own application data, plus (only) the archived object data which relates to that application.

An example of this is transaction SCU3 - read table change logs. Many other transactions also have a check-flag called "Include archived data".

Of course the "online" availability of the archived data will also depend on which archiving tools you use.

Cheers,

Julius

Re: Help required SARA

Former Member — Sun, 16 Nov 2008 18:12:57 GMT

Hi All,

I too have the same requirement,i.e after executing SARA user should be able to do read. the write and delete,management actions should be deactivated.

"THE USER SHOULD BE ABLE TO READ AND SHOULD NOT BE TO DO OTHERS"

please help me in how can i achive this????

Rgds

rajesh

Re: Help required SARA

Former Member — Sun, 16 Nov 2008 18:40:44 GMT

What has not been mentioned yet, is to restrict object S_ARCHIVE to display activities only.

That should normally do the trick, regardless of the transaction - although some tcodes are designed to be "change only" so the user might not be able to start the tcode or use it, even although they are authorized for S_TCODE.

Cheers,

Julius

Re: Help required SARA

Former Member — Sun, 16 Nov 2008 18:43:34 GMT

Hi Julius,

The S_ARCHIVE was already restricted to 03(display),but still the user is able to do the write and delete actions

Anand

Re: Help required SARA

Former Member — Sun, 16 Nov 2008 19:16:21 GMT

Which release are you on?

On release 7.00 there are checks on S_ARCHIVE but it looks like an all or nothing check on '01' AND '02' AND '03'.

The expected administrator type checks (for scheduling the archiving jobs etc, as well as S_PROJECT, etc.... are there as well. For proceeding further to DB tables, it checks DB15 etc...

Note that it is possible to navigate into SARA from many other transactions. So if there is a loop-hole around S_ARCHIVE, then you should report it to SAP.

Cheers,

Julius

Re: Help required SARA

Former Member — Mon, 17 Nov 2008 01:40:35 GMT

Hi,

But there is SAP standard program which is able to read both archived data or non-archived data (live data) in a single transaction code

...an example is transaction FB03. But not all SAP standard program will able to do the same way. Maybe you should ask your ABAP to create transaction which have option for reading live data only, archived data only, or both data (live + archived data) in a single screen.

If your goal is to restrict, say user A is able to write/delete/read and user B is only read, than you should assign SARA to user A's role with suitable authorization; and assign Z-transaction I have explained above to user B. We have done it, and using this method we are restricting who is able to write/delete/read and who is read only.

hope it help you.

rgds,

Alfonsus Guritno

Re: Help required SARA

Former Member — Mon, 17 Nov 2008 21:26:24 GMT

You can navigate into SARA from other transactions and it is used as a parameterized transaction my many others.

Using S_ARCHIVE (see the documentation in SU21) to check the authority for the requested documents appears to be the better solution in my opinion.

Cheers,

Julius