Skip to Content
Technical Articles

ChaRM 4-Eyes Principle Control Partner Function – Solution Manager 7.2

Overview

The Purpose of this Blog post is to enhance Partner Consistency check using 4 eyes principal function in ChaRM to improve Change Management Process to meet the SOX compliance.

In order to strengthen and streamline charm process and Customer requirement,  implemented 4-Eyes Principle Control Partner Function consistency checks.

Below table shows current process  and  After changes,   post  implementing 4-Eyes  Principle Control Partner Function consistency checks

Partner Function  SAME_USER for 4 Eyes principal

Specifies the business partner to which the system compares the business partner of the current user (defined in SY-UNAME). If the two business partners are the same, the condition is not fulfilled.

Dependencies

This function is only available in change request management. A business partner must be assigned to the user. The condition SAME_USER  must be assigned to the transaction type (ZMHF in our case)

Case Study

Tester and developer should not be the same business partners, Developer field must be disabled once business partner inserted and saved.

 

Prerequisites

  • Determine Partner functions  ( Developer and tester ) on which consistency check needs to enable
  • Create and assign  custom consistency check (ZSAME_PARTNER)  for Partner
  • Specify partner assignment and checks for determined partners
  • Disable Developer field in for the transaction type ZMHF
  • Add Error text message in message class

 

  1. Check the partner functions of Developer and tester

Go to IMG activity  SAP Soluiton manager -> Change control management ->  Partner Determination procedure -> Define status ->  Dependent partner function assignment – > Select Transaction Type

refer user status field for partner function –  In our case I  have to determine E005 Sucessfully tested and E002  in Development  partner status

 

2.Create and assign custom consistency check (ZSAME_PARTNER)  for partners

Go to IMG activity  SAP Soluiton manager > Change control management > Change request management Framework – > Make settings for Change Transaction Types->Assign Consistency Checks” and create custom check ZSAME_PARTNER( copy from standard SAME_PARTNER)  for ZMHF status.
Then, go to “Specify Partner Assignment and Check”, in the same activity.  create ZSAME_PARTNER by copying SAME_USER . as shown in below screen shots (update sequence, application area and message number accrodingly)
Assign ZSAME_PARTNER against each user status  E0005, E0004, E0011 in may case,
Assign Application area ZRTS_CHARM ( this content error message which user will get in case partner condition not met.
Add user status in column  User Status set at cancelation  ( if partner  condition not met then change document stauts will be reset as per provided value)

Save.

In next step ‘Define execution time of consistency checks’ here I assigned check in  E005 – sucessfully tested status of change document-. e.g. consistency will be checked when Change document will save in sucessfully status.

Save

3. Specify partner assignment and checks for determined partners

Go to Specify partner assignment and checks for determined partners tab in same screen,
Assign User status, functions  in current and 4 eyes table cloumn as shown in below screen.

in the table on the right:

The first column in the table is the status

The second column in the table is the partner function that the current business partner will be assigned to when save is clicked and the status becomes the first column.

The third column in the table is used for determining if partner functionsu2019 business partners are the same when the document is saved and the status becomes the first column. For example, the Tester (SDCD0002) equals the Developer (SDCD0001) when the status is Confirmed (E0005).

 

 

4.Disable Developer field in for the transaction type ZMHF

Disable developer field so that Developer cannot change parnter later on while changing Change document status to sucessfully tested.

Go to IMG activity  SAP Soluiton manager > Change control management > Transactions-> partner determination procedure -> Define partner determination procedure

Uncheck developer  in changeble column — add minimum and maximum developer can be assosiate to one change document.
Save

 

 

 

5. Add Error text message in message class.

Update the error text which user will get in case developer try to move Change document status to sucessfully test,

GO to SE91- -> select message class( in my case I have custom message class ZRTS_CHARM

Save

Activate  ZSAME_PARTNER  in consistency checksGo to IMG activity  SAP Soluiton manager > Change control management > Change request management Framework – > Actions Change request management -> consistency checks–> Implement Consistency checks in change request management

Create consistency check  here I created Z_Check_Condition, Assing ZSAME_PARTNER
and activate
Save

 

Once activated check  in change document, I  can see error while moving change document stats from business test to sucessfully tested, becuase developer and tester as same ID/ partner.

 

 

 

Hope this blog post will help to implement  4 eyes principal..

1 Comment
You must be Logged on to comment or reply to a post.
  • Hi Digendra Singh

    Thanks for taking time to do this Article.

    I have a question.. you say “Create custom check ZSAME_PARTNER( copy from standard SAME_PARTNER)”.  But I can’t find the standard SAME_PARTNER, only SAME_USER.   Might this be because of my version Solman 7.2 SP09?

    Regards and Thanks
    Henry