Systems with identical SID
Functional scope
Basically, the System ID, short SID, is a unique identification characteristic of an SAP system managed by Conigma and in the standard case it is not possible to create two or more systems with the same SID. However, it is possible to manage systems with identical SID with Conigma by creating the systems with a different SID or alias. If, for example, two systems with the SID "G00" exist, they would have to be created with a different SID, e.g. "GP0" and "GP1".
Prerequisites
To manage two or more systems with identical SIDs, these systems must have different installation numbers. You can look up the installation number using certain transactions SLICENSE or by choosing System -> Status in SAP GUI. In addition, the following parameters must be maintained under the node "Root -> Galileo Group AG -> Conigma Suite -> Conigma CCM ->TMS Interface -> Manage double SIDs" in the Conigma configuration using transaction /GAL/CONFIG_EDITOR and then distributed to all systems managed by Conigma:
Allow deviating SIDs: This parameter with a Boolean data type always activates the use of deviating SIDs. To activate it, double-click the parameter in the tree structure and select the system-specific value "ABAP_TRUE" in the drop-down box on the "Values" tab in edit mode. The change must then be saved.
Allowed SIDs: This parameter is used to make known the SIDs that may actually occur twice. An XML transformation of the table type "/GAL/CCM_TT_SYSID" is expected as the value. You can either use the illustration below or contact your Conigma contact person for help.
To write the changes to a transport request, proceed as follows. Right-click on the "Manage double SIDs" node above and select the menu item "Transport subtree". In the dialog box for querying the data types to be transported, select only the last entry "Client-independent values (-> Workbench)" and confirm the by clicking "OK". Finally, the standard transport request selection dialog is displayed. Please select an existing workbench request and confirm your entry with the corresponding button or the [ENTER] key. Any warning messages regarding the default consolidation target can be ignored.
Configuration of an SAP System with a Different SID
If the prerequisites described above are fulfilled and the changed configuration settings are distributed among all managed SAP systems, SAP systems can be created with a different system ID. Please note that the SID can only be specified differently for systems that have been announced in the configuration editor. As already mentioned, it is also important that you create all systems in Conigma with a different SID and not with the original SID for systems with identical SIDs.
When you create the system, enter a previously defined value as the system ID, choose the corresponding settings in the "Architecture" and "Transport usage" areas, and enter the RFC connection to the target system. If you confirm the entry with [ENTER] or save your settings, a query dialog is displayed with the message that the stored SID does not match the system information of the specified RFC connection, which can be confirmed with the "Yes" button.
Once the SAP system has been successfully created, it can be integrated and used in your Conigma processes like any other system in Conigma.
Planned changes
In import containers, the original SID of a system with an alias SID is currently still displayed when it is used as the import target. The behavior is known and will be corrected in one of the next releases. The display is particularly confusing if several systems are supplied with alias SID and identical original SID via the import container, see screenshot below of an import container that was supplied to two different systems with the name G00. To clarify which system is displayed in the overview of the import container, the RFC connection used can be viewed in the detailed information for the import job on the "General" tab.