nc roles

5/28/2018 NC roles

1/6

SAP Knowledge Base Article

Symptom

You use Change Request Management to control your software distribution you meet errors and/or warnings when changing the status of a ChaRM

l Status was reset by system: Message no. SOCM_ACTION_LOG 097l Not all tasks for request released: TK 593

l Not all test transports have been imported: CHM1_ACTION_LOG 046l Unable to successfully complete import into production system: Message no. SOCM_ACTION_LOG 009

And the ChaRM document cannot move to next status.

Environment

l SAP Solution Manager 7.0l SAP Solution Manager 7.1

Cause

In ChaRM PPF actions are used to change the status of the crm documents, but ChaRM also uses SOCM actions and condition checks.

The errors and warning that you see in the ChaRM documents are configured in spro point Make Settings for Change Transaction Types (sm34: AISMMJ transaction type:

See the error messages in se91 for message SOCM_ACTION_LOG.

When you execute a PPF action in the ChaRM document with method HF_SET_STATUS this is the sequence of steps done:

Example: you execute action Pass Normal Change to Test SMMJ_TO_BE_TESTED_MJ for a SMMJ document, this action moves the document f

0. Check conditions of the initial status E0002, all checks must fulfilled (this is done by the PPF action Checks Consistency SMMJ_CHECK_STAT

1820635 - How to analyze errors when changing the status of a ChaRM document

Version 7 Validity:03.03.2014 - active Language English

5/28/2018 NC roles

2/6

MT Message Type possible values

l Information status transition will be performed with an information message.l Cancel status transition will be terminated with a warning message, and the user status will be shifted back to the value in column User Stat

last status of the document (new feature in 7.1).l Error status transition will be performed with an error message.l Warning status transition will be performed with a warning message.

1. Execute actions for target status E0004

2. Check conditions for target status E0004, all checks must fulfilled

3. Execute late actions for E0004 (defined in spro point Determine Execution Time of Actions")

5/28/2018 NC roles

3/6

So the TOC creation and release is done after checking all conditions for E0004 are checked and ok.

4. Since Solution Manager 7.1 SP07 ChaRM will check also the late conditions (spro point Define Execution Time of Consistency Checks)

For target status E0004 there are no late conditions for example.

If any of the conditions checked are not ok then you get an error or/and a warning and depending on the message type selected ChaRM document ca

Resolution

These are the steps for analyzing a change document:

1. Get the transaction type of this document in se38: crm_order_read

5/28/2018 NC roles

4/6

with this you will know the action and conditions executed for this transaction type:

2. If the issue is with the transport requests TR go to table se16: /TMWFLOW/TRORDHC and enter the correction number in the ORIGINATOR_KEY

Here there are several fields really interested:

- TASKLIST: tasklist associated to this correction, M* for normal corrections, H* for urgent corrections.

- TRORDER_NUMBER: transport requests associated to this correction

- CTS_ID

- TRFUNCTION: K workbench request, W customizing request, T for transport of copies TOC

3. Check the number of TRs associated to the document, how many transport requests are associated to the document?

For normal corrections you can have several K, W and T entries, ChaRM will check the results of the release and import actions of the all transport remanaged systems when you are trying to move the status of the normal correction.

For urgent correction you can have several K and W, ChaRM will check the results of the release and import actions of the all transport request in theurgent correction.

4. Go to table se16: /TMWFLOW/TRACK and enter the associated transport request in the OBJ_NAME field:

5/28/2018 NC roles

5/6

Table /TMWFLOW/TRACK in your Solution Manager system is recording the results of the release and import actions of the transport request in the

Pay always attention to STEP tp Step and STATUS columns.

S Successful

F Error

R Repaired

Every time you execute an action in a ChaRM correction document, normal or/an urgent correction, or in the task list, this table is checked in order tocreated from the ChaRM document or included in the CTS project- IMG project of this ChaRM project.

If you want to move a SMHF correction to Production status and the involved transport requests do not appear like successfully imported into the proderror indicating this.

This does not mean that maybe the import is really done or the import has a different tp status in the managed system, however until w

ChaRM is like this import is not done or it is not successful.

So, you need to ensure that at any time the track table is correctly update with the real tp status information for the release and the import tp comman

5. In case /TMWFLOW/TRACK is not showing the correct information for the involved transport request run report /TMWFLOW/REP_DATA_READ fthe TMS transport directory and get the status of the transport requests. See note 1546452for details about how to use this report.

By default you dont need to worry about the update of the track table as this is an automatic process that is done when you trigger from ChaRM, fromaction like create ToC, release, import, in the TMS of the managed system.

So, this update, if all is correct, is done automatically.

Only in the case that you find errors in a correction document indicating that the TOC or transport request is not released or imported and you think thitrack table content in se16.

If one entry is missing or the status is F failed then you should go to the managed system to check the TR logs directly.

Also report like /TMWFLOW/CMSSYSCOL2 (used in the reporting job SM:TMWFLOW_CMSSYSCOL) reads these ALOGs files.

6. Ensure that you have applied note 1786704ChaRM: problem of schedule import jobs out of ChaRM if want to run the import job from TMS directly

7. If your managed systems and SAP Solution Manager system are in different time zone ensure you checked note 1982649- ChaRM: obsolete trac

5/28/2018 NC roles

6/6

WORKAROUND

You always have the workaround to go to managed development system to /nspro_admin: look for the IMG project linked to the ChaRM project and gopen the CTS project to allow TR creation, release and import action manually from /nstms, then you can run your release and imports manually fromupdate table /TMWFLOW/TRACK by running reports /TMWFLOW/REP_DATA_READ or /TMWFLOW/CMSSYSCOL2.

Keywords

Normal, urgent, correction, request for change, change request, SDMJ, SMMJ, SDHF, SMHF

Header Data

Product

References

This document refers to:

CSS SAP Notes

Released On 03.03.2014 10:00:27

Release StatusReleased to Customer

Component SV-SMG-CM Change Request Management

Priority Normal

Category How To

Product Product Version

SAP Solution Manager SAP Solution Manager 7.0

SAP Solution Manager 7.1

1982649 ChaRM: obsolete tracking data was used during change documen

1816988 Master Note for Change Request Management 7.10, SP9

1786704 ChaRM: problem of schedule import jobs out of ChaRM1726917 Master Note for Change Request Management 7.10, SP7







907768 General note for Change Request Management ST 400

nc roles

Documents