Clear working for different users

Conigma CCM provides a powerful concept for the variable display of all information required for the respective user. This makes working with Conigma CCM extremely efficient and reduces the training effort of users.

Within the framework of this concept, not only can the tree structure be adapted in Customizing, but also the depth of information displayed on the individual objects themselves.

You will find four examples of this in the following.

Administrator and Key-User

The figure above shows a representation of all elements that are typically useful for a Conigma CCM administrator and power user. The information depth for the individual objects is relatively high. In this example, 13 tabs can be displayed / edited for a Change.

The following table describes all essential elements of this tree structure.

Project and release development	Typically, various customer-specific views are customized here. In this example there are 3 views. My Changes by Status: all Changes to which the current user is assigned in any role (directly or via a user group) Changes by project structure and status: Changes are grouped by project structure elements (= freely maintainable attribute trees that allow multiple assignments of changes, e.g. business processes, SAP modules, affected SAP system lines, affected organizational units,...) Changes by release and status: Changes grouped by existing releases (in this example by maintenance and development/project release)
Import Monitor	Here you have direct access to the import containers.
Configuration	Conigma CCM Implementation Guide with all options required for customizing (similar to transaction SPRO in SAP ECC),
Reports	Access to numerous pre-configured Conigma CCM reports.
Favourites	Users can assign the views they use most frequently and the objects that are currently or permanently being processed to this subtree.
Search results	Result of the last object search.

Release manager

The figure above shows a typical view for the Release Manager role. Here no direct access to the import monitor or to the Conigma CCM customizing is possible. Otherwise, this view is no different from that of the Conigma CCM Administrator and Power User.

Developer / Customizer

Different information is often relevant for the typical SAP developer or SAP Customizer (sometimes also called "Functional Consultant").

The figure above shows an example of a developer view that only displays the changes to which the user John Developer is assigned. This is only displayed for a specific section of the development process Status Interval New to Development Completed.

Testers

As a rule, a subject tester has completely different information needs than the persons named in the examples described above.

The figure above shows all Changes to which a specific person is assigned as a subject tester. On the Changes itself you see only 5 tabs relevant for the tester. In this example, this tester has two changes that are waiting for approval. One Change was already ready for approval once and was rejected. Another has already been approved and is waiting to go live.

The example for the tester-specific representation of Conigma CCM views shows the power of the tool: As soon as a user is assigned to the Tester group (and has no admin role), the pure approval view is displayed when calling Conigma CCM. This is only one of the numerous possibilities for the determination of views in Conigma CCM.