This article describes the process of updating the CIM model and CR Content (Component Repository Content) in SLD (System Landscape Directory). But what is SAP CR Content? It is an integral part of SLD whereby SAP stores information about its components. This information is used, for example, by SAP Solution Manager to prepare the entire process of updating the SAP products, which we use. Therefore, SAP recommend use always the latest version of SAP CR Content.

Generally CDC is a tool, which You use to compare data sources with a complex structure or hierarchy. You can do this across different systems to check whether the data in the source and target systems is consistent, for example, whether updates in the source system have been correctly replicated to the target system. 

Link to documentation: https://help.sap.com/doc/saphelp_sm72_sp03/7.2.03/en-US/1e/d6fc8b7f204a289db763833525d89a/frameset.htm

In the below article I will describe the errors I encountered while working with CHaRM in SAP Solution Manager and I will present to You their solutions.

ChaRM -> Change Request Management

SAP ChaRM is a tool delivered with SAP Solution Manager that manages activities performed during a change in design and testing the procedure to move from final promotion to the production system. It allows you to track
change requests and transport requests in the change management system across the entire business solution.

Discussed list of errors :

1. “Make an entry in field ‘Configuration Item'”.
2. „Transport track of source system SID~ABAP/XXX does not include a production system”.
3. “No consolidation system” lub “No export system“.

W poniższym artykule opiszę błędy jakie napotkałem podczas pracy z CHaRM w SAP Solution Manager oraz przedstawię Wam ich rozwiązania.

ChaRM -> Change Request Management

Tak z grubsza SAP ChaRM to narzędzie dostarczane wraz z SAP Solution Manager, które zarządza działaniami wykonywanymi podczas zmiany od projektu przez testowanie do ostatecznego wgrania na system produkcyjny. Umożliwia śledzenie żądań zmian, zleceń transportowych w systemie zarządzania zmianami w całym rozwiązaniu biznesowym. Na to wszystko może być dodatkowo nałożone workflow oparte na zatwierdzaniu zmian, które przenoszone są transportami między systemami.

Omówiona lista błędów:

1. “Make an entry in field ‘Configuration Item'”.
2. „Transport track of source system SID~ABAP/XXX does not include a production system”.
3. “No consolidation system” lub “No export system“.

During using the SM_CRM or CRM_UI transaction to create a new change document (RfC) sometimes You can see long list of different types of transactions:

How can we limit the list – for example only to the ZMMJ type? Follow these steps:

1. In SPRO transaction, navigate to: SAP Reference IMG > SAP Solution Manager > Capabilities (Optional) > Change Control Management > Transactions > Define Transaction Types.
2. Find the Transaction Type to be disabled, e.g. SMAD (at the bottom of the screen You can find “Position…” button – use it to search).
3. Select the line and in the column: “Inactive” select the appropriate option from the list:

4. Proceed in the same way with other types of transactions, which You want to disable.

Podczas używania transakcji SM_CRM lub CRM_UI do tworzenia nowego dokumenty zmiany (RfC) wyświetla nam się dość długa lista różnych typów transakcji: