cancel
Showing results for 
Search instead for 
Did you mean: 

Bidder gets "no authorization for the action" when creating response to RFx

Former Member
0 Kudos

Hi,

When the bidder tries to post a response to RFx in SRM7.0, it gives an error message "no authorization for the action".

What could be the possible cause of this error?

i have already gone through this link:

The note mentioned here is not needed incase of SRM 7.0. And for the BADI i am not sure which ICC BADI to deactivate.

Kindly suggest.

Regards,

Mithun

Accepted Solutions (0)

Answers (2)

Answers (2)

ricardo_cavedini
Active Contributor
0 Kudos

Hello,

Sample code provided by SAP of BBP_DOC_CHANGE_BADI, implementation BBP_ICC_QUOT_CHANGE for BUS2202, can cause this issue.

This implementation is active by default.

You can just deactivate this implementation.

Manual steps of note 1303125 gives more information about this sample code.

It says:

The following implementation would be deleted manually.

Go to transaction SE18

open BAdi BBP_DOC_CHANGE_BADI

open implementation BBP_ICC_QUOT_CHANGE

click on change

click on deactivate

Otherwise, note 1435554 is relevant to this topic as well.

Kind regards,

Ricardo

Edited by: Ricardo Cavedini on Aug 9, 2010 11:28 PM

pedro_santos6
Contributor
0 Kudos

Hello All,

I have the same problema, and the badi BBP_ICC_QUOT_CHANGE is desativated and have the badi BBP_DOC_CHANGE_BADI activated to object type BUS2202.

When I try to create a quotation, the system show me the message "No authorization for the action".

I´m in SRM 7.0 with SP 08.

Any idea?

Rgs,

Pedro Marques

Former Member
0 Kudos

Do a security trace and find out which authorization object is being checked for which you don't have authorization.

Hope this helps.

-Bakulesh

Former Member
0 Kudos

Pedro

We had same issue and are also on SRM 7 SP08.

Once we deactivated BBP_ICC_QUOT_CHANGE, issue was fixed for us.

Nikhil

Former Member
0 Kudos

In my case, there is an active implementation of BBP_ICC_QUOT_CHANGE BADI somehow. And that was the reason of the error. You could try to see if that BADI implementation is active. If so, it has to be deactivated.