Authorization Opportunity Status

[Former Member]

Hello,

we would like to set authorizations on an assignment block within the opportunity.

"When the status of a Opportunity is changed to a specific value only the responsible employee and users on the same org. level and above should be able to change the ITEM assignment block.

The ITEM assignment block must be visible to all."

Suggestions how to authorize

-depending on status of the oppty, if the item assignment block is read only or editable

- or how to leverage the org. model for authorzations

would be appreciated.

Thanks

Bernd

[Former Member · Accepted solution]

Hi Bernd,

I would do the following to fullfil the requirements:

Check if the user is playing "resp employee" partner function on the opportunity. If so, no further check is required.

If not, derive org units and parent org units of "resp employee" partner. And if any these org units contain the user, no further check is required. Otherwise make item assignment block is read only.

Pros: More flexible & easy to do

Cons: Depending upon size of org model/employees, performance may be slowdown. We have experienced performance issues on the org model read/query. May be you should try to use buffering tricks to avoid performance issues.

• There may be other best alternatives available. Let's see what experts say.

Thanks

Paparao Undavali

[robert_kunstelj]

Consider implementing CRM_ORDER_AUTH_CHECK badi (for allow some users to change document depending any scenario you like), or CRM_ORDER_FIELDCHECK (where you can block changes in specific field groups of the document).

Hope that this may help you a little more.

[Former Member]

Also use B_USERSTAT & B_USERSTAT_T authorization object in PFCG role to user.

Define and assign auth. key and assign it to the role under above auth. object. So that particular user would be able to see the statuses he is auth for.

Regards,

Nikhil

[Former Member]

Hi Bernd,

Technically I would say these are good approaches.

1. To prevent particular users from Editing the Assignment Block ->

We can, hide the EDIT button for the item assignment block for the users who should not edit

the block.

Coding: Code can be implemented in the IF_BSP_WD_TOOLBAR_CALLBACK~GET_BUTTONS

method of the assignment block of IMPL class and make the button enabled or disabled based

on the logic.

ls_button-enabled = 'X'.

2. To prevent the user from totally seeing the assignment block at all ->

We can dynamically remove some views from being shown for particular users.

Coding: Code can be implemented in the method DETACH_STATIC_OVW_VIEWS of the IMPL class of the overview page.

IF employee = ''XXX'.

* detach the view

ls_viewid-viewid = 'BT111H_OPPT/ItemsList' .

APPEND ls_viewid TO rt_viewid.

ENDIF.

Regards,

Masood Imrani S.