ChaRM functionality: Control UI objects via authority objects coming with Support Package 7 (and available via note 1724697 with Support Package 5-6)

Change Request Management customers and consultants who knew SAP Solution Manager 7.0 know that there the information about solution, project, test management, SAP Notes (at that times called the HotNews functionality) and documents was contained in a separate context tab.

Via right-click it was possible to execute functionality like adding, deleting projects, solutions, business processes and so on…

In Change Request Management 7.10 Web UI, these functionalities have been moved to separate assignment block (Solution, Project, and so on).

In the ‘old world’ it was possible to control the right-click executions via the authority object.

The authority was controlled in the old world via the authority object SM_CHO_CO.

In the Web UI, this has not been possible until now. With the new flexible functionalities liek assign and decouple transport request you might have a stronger need to restrict these functionalities to certain roles….

Possible Use-cases could be:

Not everyone is allowed to…

– add/delete documents

– check-in/check-out a solution (Change Manager only f.e.)

– reassign project assignment (this is maybe decided only by the Change Manager)

– decouple/assign transport requests (only Administrators are allowed to do that. So they automatically sync with the relevant developer and change manager what)

With Support Package 7 SAP delivers functionality to control the UI objects (push buttons f.e.) via authority object. The new authority object is SM_FIELDS.

SAP delivers in the standard roles this authority object with

PR_TYPE = ‘*’

UI_OBJECT = ‘*’

That means nothing changes first in your running system. If you want to restrict the usage of UI objects you have to think about what UI objects are allowed to be used in which role.

You can check out SAP note 1724697 for further information.

Check out thread http://scn.sap.com/community/it-management/alm/solution-manager/blog/2012/07/11/editabilityvisibility-of-ui-objects-dependent-from-the-user-status how to do that!

Assignment Block	UI Object key	UI Object Name
Details	PROJECT_ID	Project, Solution
Details	IBASE_COMPONENT	Reference Objects
Details	MAINPROJ	Project Cycle
Details	REASSIGN	Change Project Assignment
Scope	SCOPE	Scope
Transport Management	RELEASE_REQU	Release Transport
Transport Management	CREATE_REQ	Create Transport Request
Transport Management	CREATE_TASK	Create Task
Transport Management	APPR_CRIT_OBJ	Approve Critical Objects
Transport Management	RELEASE_COPY	Create Test Transport
Transport Management	ASSIGN_TRA	Assign Transport Request
Transport Management	DECOUPLE_TRA	Decouple Transport Request
Transport Management	RELEASE_COPY	Release Transport of Copies
SAP Notes	ADD_NOTE	Add SAP Note
SAP Notes	DELETE_NOTE	Delete a SAP Note
Documents	ADDDOCU	Add a Document
Documents	DELETEDOC	Delete a Document
Projects	ADDPROJECT	Add Project
Projects	DELETEPROJ	Delete Project
Projects	ADDPROJOBJ	Add Structure Object
Solutions	SOLN	Add Solution
Solutions	DELETESOLN	Delete Solution
Solutions	CANCHKI	Cancel -> Request Check-In
Solutions	CACHKC	Cancel -> Request Check-Out
Solutions	CHKINOUTI	Check-In/Out -> Check-In
Solutions	CHKINOUTC	Check-In/Out -> Check-Out
Solutions	REQCHKI	Request -> Check-In
Solutions	REQCHKC	Request -> Check-Out
Test Mangement	ADDTESTDOC	Add
Test Management	DELTESTDOC	Delete

So how to proceed.

1.) Analyze your business need

2.) If you have one, define beforehand which role should have which authorities in respect to the user status (where you have to customize the UI control method)

So, hope that helps you,

Michael