SAP Solution Manager 7.2 – CDC (Cross Database Comparison) configuration

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:

Continue reading “SAP Solution Manager 7.2 – CDC (Cross Database Comparison) configuration”

SAP Solution Manager 7.2 – possible errors during activating projects in CHaRM

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“.
Continue reading “SAP Solution Manager 7.2 – possible errors during activating projects in CHaRM”

SAP Solution Manager 7.2 (CHaRM) – restrict the transaction types when creating an RfC with Web UI

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.

SSFS (Secure Storage in FileSystem) configuration for BRTOOLS

To increase the security of database connections, SAP Kernel 7.20 Patch Level 100, introduces a new method for the secure saving of the SAP database user or SAP database password. This method stores data for connection to the database in so-called SSFS (Secure Storage in FileSystem). For more information, see SAP Notes: 1622837, 1639578 and 1764043.

To activate SSFS please use the following steps:

  1. Create the appropriate folder: /oracle/SID/security/rsecssfs/data and /oracle/SID/security/rsecssfs/key
  2. Check or create the user brt$adm in the database:
    • SQL> create user brt$adm identified by <your password>
    • SQL> grant sapdba, sysdba, sysoper to brt$adm;
  3. The initial password shall be changed to the actual password using brconnect…
    • brconnect -u SAPSR3/PASSWORD -c -f chpass -o ‘BRT$ADM’ -p ‘<your password>‘ -s brtools
  4. Now we can test it:
    • brconnect -u // -c -f check
Continue reading “SSFS (Secure Storage in FileSystem) configuration for BRTOOLS”

SAP Java – changing instance name after refreshing the system with production data

In the following scenario, we’ll focus on changing the instance name (SID). The data of the SAP Java test instance will be replaced with data from the production system. The database refresh process itself will be the subject of a separate article.

At this moment, we will focus on the steps that should be taken after such a refresh of the database, on the server where we have the JAVA instance running. Let’s assume that:

  • test Java instance name is “TST”, host: test01, instance numbers: J47 and SCS46;
  • the name of the production JAVA instance is “PRD”, host: prod01, instance numbers J47 and SCS46;
  • before refreshing, the TST system was embedded on NetWeaver 7.4, while the production system was already in NetWeaver 7.5;
  • the TST instance has been overwritten with data from the PRD system.
Continue reading “SAP Java – changing instance name after refreshing the system with production data”