Identify when a ChaRM document moves between two states

To identify when a ChaRM document moves between two states, follow these steps. Our example will identify when a normal change request moves from In Development to To Be Tested.

Create an action definition

To create an action definition that identifies when a normal change request moves from In Development to To Be Tested, follow these steps in SAPGUI on your ChaRM system.

  1. Run transaction CRMC_ACTION_CONF. The Conditions for actions: Change screen is displayed. Click Change tool button. to enter Display Mode.

  2. Click Technical Names, and in the screen’s top left-hand pane, double-click the Technical Name of the action profile you wish to modify. The following screen is displayed.

  1. Click Action Definitions in the header. The following screen is displayed.

  1. In the Action Profile list, double-click the Action Profile chosen in Step 2. The following screen is displayed.

  1. Double-click Action Definition in the Dialog Structure hierarchy. The following screen is displayed.

  1. Click Change tool button. to enter Change Mode, and then click New Entries. The following screen is displayed.

  1. Complete the screen fields as follows. You will need the PROCESSTYPE value from your text document.

Action Definition tab

Field Description
Action Definition

ZLC_<PROCESSTYPE>_STATUS_<From Status>_<To Status>

Example: ZLC_SMMJ_STATUS_DEV_TBT

Description LiveCompare: Move from In Development to To Be Tested
Processed At Processing When Saving Document
Schedule Automatically Checked
Delete After Processing Checked
Changeable in Dialog Checked
Executable in Dialog Checked

Action Description tab

Field Description
Description Tricentis LiveCompare ChaRM integration. Automatic invocation to run when a normal change document moves from In Development to To Be Tested.

  1. Double-click Processing Types in the Dialog Structure hierarchy. The following screen is displayed.

  1. Click New Entries. The screen changes to the following.

  1. Select the first cell in the Permitted Processing Types of Action table, and select F4.

  2. Double-click Method Call in the Restrict Value Range (1) dialog. The New Entries: Overview of Added Entries screen looks like this.

  1. In the Settings Method Call section, select the Method field and select F4.

  2. Double-click ZLC_CALL_AUTO in the Type of filter in BADI implementation (1) dialog. The New Entries: Overview of Added Entries screen looks like this.

  1. Copy the contents of the Action Definition field to the clipboard. Add the following entry to the text document that will be used to populate the /ICORP/CHARM_003 table.

ACTION (Auto): <Copied value>

  1. Click Save tool button.. The following dialog is displayed.

  1. Click Tick button. to add the request to a transport.

  2. Click Exit tool button. to close the window.

Update the action profile to include the new action

The next step is to update the SMMJ_ACTIONS action profile to include the ZLC_SMMJ_STATUS_DEV_TBT action. This can be done by carrying out the following steps:

  1. Run transaction CRMC_ACTION_CONF. The Conditions for Actions: Change screen is displayed.

  1. Click Technical Names and double-click SMMJ_ACTIONS in the Action Profile hierarchy.

  1. Click Create tool button. in the right-hand pane and select the description for the ZLC_SMMJ_STATUS_DEV_TBT action (LiveCompare: Move from In Development to To be Tested).

  2. Click Save tool button.. The following dialog is displayed.

  1. Click Tick button. to add the request to a transport.

Set conditions for the action

To configure the ZLC_SMMJ_STATUS_DEV_TBT action so that is invoked when a change request moves from the In Development state to the To be Tested state, follow these steps in SAPGUI on your ChaRM system.

  1. Click New window tool button. or use /o to open a new SAPGUI window.

  2. In the new window, run transaction SE16 and display table TJ30. The following screen is displayed.

  1. In the Data Browser: Table TJ30 Selection Screen, enter <Action Profile Technical Name>HEAD in the STSMA field.

Example: SMMJHEAD

  1. Click to display a table similar to the following.

Use the STMA, ESTAT and TXT30 field values to identify the From and To statuses for your action.

Example

Status STMA ESTAT TXT30
From SMMJ E0002 In Development
To SMMJ E0004 To Be Tested

  1. Return to the Condition for Actions: Change screen. In the right-hand pane, select LiveCompare: Move from In Development to To Be Tested in the Action Definition column.

Add a schedule condition

Schedule conditions determine whether an action should be scheduled for processing. The action is only run if the schedule conditions are satisfied. To create a schedule condition that checks whether a normal change document has an initial status of In Development, follow these steps.

  1. Select the Schedule Condition tab, and click Edit Condition. The following screen is displayed.

  1. Enter a name for the condition in the Name field.

Example: ZLC_InDevelopment

  1. Click the Condition Definition field to edit it. The following dialog is displayed.

  1. In the Expression 1 field, select Container > CRM Service Process > Methods > User Status.

  2. In the Operators field, select Equals condition..

  3. Enter <ESTAT value><STMA value>HEAD in the Constant field.

Example: E002SMMJHEAD

  1. Press Enter and click Tick button.. The Conditions for Actions: Change screen looks like this.

  1. Click Save tool button.. The following dialog is displayed.

  1. Click Tick button. to add the request to a transport.

Add a start condition

Start conditions are checked before an action is executed. The action is only run if the start conditions are satisfied. To create a start condition that checks whether a change moves to a status of To Be Tested, follow these steps.

  1. In the Conditions for Actions: Change screen, select the Start Condition tab and click Edit Condition. The following screen is displayed.

  1. In the Name field, enter a name for the condition.

Example: ZLC_ToBeTested

  1. Click the Condition Definition field to edit it. The following dialog is displayed.

  1. In the Expression 1 field, select Container > CRM Service Process > User Status.

  2. In the Operators field, select Equals condition..

  3. Enter <ESTAT value><STMA value>HEAD in the Constant field.

Example: E004SMMJHEAD

  1. Press Enter and click Tick button.. The Create Parameter Condition screen looks like this.

  1. Click Save tool button.. If prompted, add the request to a transport.

  2. Click Save tool button.. in the Conditions for Actions: Change screen to save your changes.

Next: Run a ChaRM action from the Actions menu