cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

"Pain and Anguish"

Former Member
0 Likes
204

I think this is a more apt name for the tasks undertaken by the team formerly known as 'security and authorisations'.

It has a better ring to it, defines more clearly what we are about and avoids any silly expectations that we will actually help the user even if they have an SU53 and trace.

Start as you mean to go on... " Hello David Berry, Pain and Anguish how can I annoy you?" as a telephone greeting seems pretty clear to me...

Definately a Dogbert moment.

I vote to have S&A changed to P&A

Simples...

Cheers

David

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Likes

I have seen all sorts of strange things but the most unusual of them in this regard is a customer who does not have security hanging under project management, or basis, or finance, or audit... but as "Security and Purchasing".

The purchasing chef has a fetish and hobby with secirity issues, so does not let any wishy-washy through the "gateway".

It is absurd, but seems to work better than average.

Cheers,

Julius

Former Member
0 Likes

It does sound odd at first glance but we always say that security don't own the roles - they are owned by the business and, if this person is keeping a good eye on the purchasing side of things that sound excellent. Almost like an ongoing remediation manager; all they need now is the Finance manager to take a share of the work and that must equate to one heck of a safe system

Former Member
0 Likes

The finance and particularly controllers simply don't get access until they have provided at least three different concepts (or at least transaction codes) to achieve the same thing and then purchasing decides which one is best.

In the end, finance reporting is driven by logistical events not manual journal entries.

Has it's pros and cons (eg. make sure you dont become a bottle-neck or a scape-goat).

Cheers,

Julius

Former Member
0 Likes

The most painful moments are the ones when user starts talking of FIELD LEVEL authorization , even through knowing SU24 or SUIM .

I want this field to be viewed by Mr. X and not by Mr. Y and that really KILLS ......

Then as a functional guy you start digging the code for enhacements and finally conclude is it ABAP that is driving Roles .....

Cheers ,

Dewang

Ask a Question
Top Q&A Solution Author