Restricting the user not to release the PR through ME54.

[Former Member]

Hi,

I will explain our current logic of PR workflow.

1. PR Individual Release.

2. Workflow is activated with User Exit which will create a work item with some logic and releasing the PR through ME54.

3. Release Strategy is based on the Cost Center Responsbile person, and his HR Master Data hierarchy and Signing Authority value.

System will pick up the Release Code based on the Cost Center Responsible person and checks his Signing Authority value, if the PR line item value is not met, system will pick up the second level by checking the Cost Center Responsible person's HR Master Data and finds his/her Boss and checks for hi/her Signing Authority Value and it goes on up to the highest level in the HR hierarchy.

Now, the issue is, one Cost Center Responsible person will have 15K as value and Other person may be having 100K as value. Both the cases, the release code would be 01, whereas the 15K value person can go and release the 100K value PR as the both cases are release code 01 only.

This is not happening through workflow, as user manually going and releasing through ME54 transaction. We cannot block the authorisation to run ME54 as it is called background while releasing through Workflow.

Can any one have idea how to restrict via system not to use the transaction : ME54. Your as usual support/help in this regard is highly appreciated.

Thanks,

Babu.

[Former Member · Accepted solution]

Hello,

Did you ever get an answer to your problem? In effect I have the same situation and need a solution: the individual has both requisition creation and requisition approval capability and I want to prevent the person from approving his own requisitions versus removing their ability to create requisitions. It seems ME54/ME54N does not have a user exit available. Have you a solution to your problem?

Thank you.

Wil Dunn

[Former Member · Accepted solution]

Hi Wilford

I am not very sure about this but we can try...cant we take user id as one of the characteristics and then we can restrict a user with the allowed value.

regards

Yogesh

[Former Member · Accepted solution]

Hi Yogesh,

I am not clear on what you are saying yet. Even if user id is a characteristic, how (where) would ME54N transaction use it?

Regards,

Wil

[Former Member · Accepted solution]

Hi,

If you have several starategies, each one depending different value ranges

(such as 1 to 1000 release strategy 1, 1001 to 10000 release strategy 2, etc.). then you can allocate different release codes to each

So that

A P req for 100 will be released by codes 01 or 02,

A P req for 9000 will be released by release codes 03 or 04 etc.

So you control who does the release by using different release strategies for different value ranges.

In the above situation a user with release code 01 is ONLY involved in the release of P reqs up to 1000 and plays no part in any that are over that value.

Surely this would work for you?

Steve B

[Former Member · Accepted solution]

Hi Steve,

I understand what you are saying but that is not my issue. Manager X has $100 approval authority and also authority to create purchase requisitions. Manager X creates a requisition for $10 and the Workflow automatically sends it to another person for approval, BUT, manager X knows the requisition number and uses ME54N to release his own requisition. This is what I need to prevent but see no way for ME54N to stop it.

Wil

[Former Member · Accepted solution]

Hi,

I would simply have a report that shows where the person authorising a requisition is the person that created it.

It is far better to get your staff to behave correctly than to try to turn the SAP system into a "Police Officer".

Surely a manager should do as they are told? And with a daily report of those who aren't behaving you can "hit" them when they break the rules.

If you try preventing the access to ME54N then you will also stop them from releasing via workflow because this is going to use the same function.

I would rather trust and control my users than modify the SAP system to stop people from breaking the most basic rules.

Steve B

[Former Member · Accepted solution]

Hi Steve,

Personally, I agree with you 100% in Trust and Professionalism but unfortunately it seems our auditors behind the Sarbanes O banner want absolute assurance that an individual cannot approve their own requisition or Purchase order. If the system cannot do it, then they insist upon 'separation of responsibilities', i.e. create or approve documents but NOT both. Thus, the reason I'm looking for the prevention capability in approvals.

Thanks for your help.

Wil

[Former Member · Accepted solution]

Hi,

I would consider a small modification (user exit)to ME54N to check the userid of the creator against the userid of the releaser. that way you can safely let people use ME54N becauise whatever they do they can only release other user's requisitions.

I don't like modifications at all but in cases like this they do have a role to play.

Steve B

[Former Member · Accepted solution]

A user exit entry was my original thought but I can not find a predefined user exit for ME54N. Do you know of one or are you suggesting "go make your own".

Thanks again.

Wil

[Former Member · Accepted solution]

Hi,

If there isno user exit (and that is probably the case here) then you will have to modify the code instead.

I never like recommending such a modification but if it is controlled and provides vital functionality that is not over complex then the positives outweight the negatives.

Steve B

[Former Member · Accepted solution]

Hi Wil,

Did you ever get an answer to your problem?

I have exactly the same problem as you have: Prevent users from approving their own requisitions due to SOX-regulations

It seems ME54N does not have a user exit available. How did you solve your problem ?

best regards

Anders

[Former Member]

Hi Sachendra singh

Thanks for the reply. I don't think, it can be controlled through Authorisation. I cannot control by Plants, Release Codes, Groups etc., Also I can not remove ME54 as it is called by background while released through workflow item.

Regards,

Babu.

[Former Member]

Hi,

I think it can be checked by authorisations control T.Code PFCG.

Regards,

Sachendra singh