Re: It depends....

[ Follow Ups ] [ Post Followup ] [ Message Board ]

Posted by [IP Address: 152.163.206.206] 'John A. Jarboe' on August 22, 2001 at 16:58:47 EST:

In Reply to: need info about background transactions in SAP posted by [IP Address: 152.163.206.206] 'tim fisher' on August 22, 2001 at 10:00:31 EST:

If you mean by Background transactions those performed byt he calling transaction as a CALL TRANSACTION command then the answer is probably, If you mean background meaning as a batch job in the background ( clasic SAP definition) then the answar is, it depends.
Authorization to execute activites in SAP are controlled with the ABAP statement AUTHORITY-CHECK. If the code contains it and the conditions are correct for the code to encounter the statement, then the user has to have that access regardless of how it is called. Many cases exist wher the "calls" go to other code that checks the same security as the calling code, so the answer in many cases is Yes. but you can find instances where it is not.

: I am involved on an SAP security project (first project - yelp) at the moment and the issue of backgound transactions has come up - i.e if someone is authorised to use a transaction, do they automatically get access to all the background txns associated with the original txn?

: I would also appreciate any more information that people can supply (where to look etc) about the whole issue of background transactions in general.

: thanks for any help you all can give

: regards
: TIM.

Follow Ups:

Post a Followup

Name:
E-Mail:
Subject:
Message: : If you mean by Background transactions those performed byt he calling transaction as a CALL TRANSACTION command then the answer is probably, If you mean background meaning as a batch job in the background ( clasic SAP definition) then the answar is, it depends. : Authorization to execute activites in SAP are controlled with the ABAP statement AUTHORITY-CHECK. If the code contains it and the conditions are correct for the code to encounter the statement, then the user has to have that access regardless of how it is called. Many cases exist wher the "calls" go to other code that checks the same security as the calling code, so the answer in many cases is Yes. but you can find instances where it is not. : : I am involved on an SAP security project (first project - yelp) at the moment and the issue of backgound transactions has come up - i.e if someone is authorised to use a transaction, do they automatically get access to all the background txns associated with the original txn? : : I would also appreciate any more information that people can supply (where to look etc) about the whole issue of background transactions in general. : : thanks for any help you all can give : : regards : : TIM. : :

[ Follow Ups ] [ Post Followup ] [ Message Board ]