SAP ChaRM My Inbox setup on SAP SolMan 7.2 SP12+

Scenario: Installing and using My Inbox Fiori app on Solution Manager 7.2 SP12+ system.

Step 01:

Install the latest patch of the below-mentioned add ons on the solution manager system

UIX01CA1 – Release 200
IW_PGW – Release 100

As of SP13, the below version of the above components are compatible.

Step 02: 

SM30 > maintain /IWPGW/V_TGW_FAC table entry

Step 03: 

SM30 > maintain /IWFND/V_COCCOL , Add entry to /IWFND/V_COCCOL table.

Step 04: Create 2 RFCs

RFC 01: Type 3 TRUSTED RFC:  LOCAL_<Client_Number> ( My client is 300, hence LOCAL_300)

Try the Remote Logon and make sure the logon is successfull. You would need to have S_RFCACL authorization object maintained to use local Trusted RFC logon.

RFC 02: Type G HTTP Connection to External Serv RFC: SM_MY_INBOX_G

Path Prefix: /sap/opu/odata/sap/AI_CRM_GW_CM_TGW_TCM_PROVIDER_SRV

Use HTTP port & Target Host (solman host) and make sure connection test is working.

Create a service user TASKGATEWAY as a copy of SOLMAN_ADMIN and maintain that user in the RFC.

Connection Test

Step 05 : 

Create 2 Local System aliases;

ZTCM_<SID>_GW — with Type 3 RFC

ZTCM_<SID>_GW2 — with Type G RFC

Step 06 : 

Add TASKPROCESSING service

Tcode /n/iwfnd/maint_service > Add Service

Add the other Alias (Type 3)  for the below 5 services;

AI_CRM_GW_CM_TGW_TCM_PROVIDER_SRV
AI_CRM_GW_CM_TGW_TCM_CD_CRO_UI_SRV
AI_CRM_GW_CM_TGW_TCM_CD_SMART_SRV
AI_CRM_GW_CM_TGW_TCM_CD_WLO_UI_SRV
AI_CRM_GW_CM_TGW_TCM_RFC_SMART_SRV

Step 07:

Activate SICF services related to fiori inbox

Step 08:

https://SOLMANHOST:PORT/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html?sap-client=<CLIENT_NUMBER>?scope=CUST

Add the Catalog & Groups ( suggested to create own Catalog as a copy of X-SAP-UI2-CATALOGPAGE:SAP_FND_BC_MANAGER_T )

I created something like below and renamed the App title;

Create a Group and assign the Catalog object

Create a PFCG role Z:SM_CHARM_MY_INBOX and assign the Catalog & Group; generate role and assign to users;

Some of the Authorization Objects I used in this role are as below;.

At this point, you would have the Fiori app available on launchpad. However this App has not been linked to the ChaRM world yet !

Step 09:

Next part is configuring the Change Request (ZMCR…) and Change Document ( ZMMJ, ZMHF…etc) tasks/actions  in the my inbox app;

For Change Request  proceed as below; maintain the workflow ID and decision keys

SPRO >

For Change Documents, there are 2 parts;

1. Standard PPF actions:  Below standard PPF actions are supported out-of-box when you maintain the Action settings

a. Approve the import of urgent changes into the production system or reset the change document to the status “In Development”.
b. Approve the preliminary import of normal changes or change the status of the change documents
c. Approve or reject the critical objects in the transport requests of change documents
d. Approve the allowlist objects in the transport requests of change documents

These action definitions already have the Parameter maintained in the action settings; as long as the Partner is the ‘Current processor’ for the Approval step, then these Actions would be available in My Inbox app.

2. For Custom Actions, we need to add the Class and redefine the methods to make them available in My Inbox ( you would need a Developer Key !)

For example, I want to add ‘Set to Successfully Tested’ action in normal Change to the My inbox app;

Switch to change mode and add a new entry.

Enter task definition ID: ZAI_CRM_CM_ZCC_APPROVAL and task provider class: ZCL_AI_CRM_NC_APPR_P.

Open SM30 in view AIC_CRM_CM_COMTC (Task Gateway Provider Configuration).

In change mode, create a new entry with the following values:
Task Definition ID: in this example, ZAI_CRM_CM_ZCC_APPROVAL
Active: true
Smart UI: true (default). If you use Cloud UI, set Cloud UI to true and Smart UI to unknown.

To implement the task provider class that you just created, open transaction SE24 (ABAP Class Builder).
Enter the task provider class that you just created, for example, ZCL_AI_CRM_NC_APPR_P, and select Create.
In tab Properties, declare superclass: CL_AI_CRM_CM_COM_TCM_CM_PPF_P

In tab Methods, redefine method IF_AI_CRM_CM_COM_TCM_PROVIDER~GET_TASK_DEFINITION_DESCR
This generates the text that is shown in the Fiori MyInbox UI.

METHOD if_ai_crm_cm_com_tcm_provider~get_task_definition_descr.

task_definition_description = super->get_task_definition_descr( short_form ) && ‘Regular Change'(001).

ENDMETHOD.

Activate the Class and Method.

Now come back to Action Definition and maintain the below ( in my case I want to add Successfully Tested related action)

With the Custom action, one important point you would need to keep in mind that, the Action would be only available in the My Inbox when the Action needs to be executed by the Current Processor SDCD00004- Current Processor partner function. So you would need to perform below Current Processor assignment based on the status of the document.

In this customizing activity, you define which business partner in which source business partner function is assigned as a business partner with a specific target business partner function.

The target business partner function should be the Current Processor (SDCD0004). The source Partner Function could be any of the already available Partner Functions in the document. For my example, since I want Tester should have the My Inbox feature available for the status ‘To Be Tested’; I would map Source Partner Function as SMCD0002 and Target as SDCD0004 for status E0004 ( To Be Tested)

Hope this helps!

Vivek Hegde

www.better-alm.com