SAP Solution Manager will be discontinued at the end of 2027.

System requirements for SIVIS Suite

Requirement	Details
SAP software components and packages	SAP BASIS 700 - Support Package Level 31 SAP BASIS 701 - Support Package Level 16 SAP BASIS 702 - Support Package Level 16 SAP BASIS 710 - Support Package Level 19 SAP BASIS 711 - Support Package Level 14 SAP BASIS 720 - Support Package Level 8 SAP BASIS 730 - Support Package Level 12 SAP BASIS 731 - Support Package Level 12 SAP BASIS 740 - Support Package Level 7
System performance	Processor: Minimum sufficient for SAP system release Recommended: In addition, the computing power of 2 x Dual Core 3 GHz or higher
Disk space on the database	For the installation 8 GB At least 4 GB growth per year for the current data stocks In connection with the Extension Manager, very large data sets can be created, for which you must expect an increased growth per year.
External disk space on the SAP application server/ network drive	For data synchronization - import and export: 2 GB For project download - simple backup: 4 GB
Adjust SAP system parameters	rsdb/obj/buffersize SIVIS makes increased use of ABAP shared buffers. So that SIVIS can work without problems and does not hinder any other programs in their work, the profile parameter which is responsible for the size of the buffer in the source system should be adjusted accordingly. Set to at least 256 MB. rsdb/obj/large_object_size 60 MB for the biggest object.

1. No additional client required.
2. Lower initial setup costs.

1. Mixing of user administration and business processes.
2. More critical in audits and reviews.

1. The system landscape is small.
2. Clear organizational and technical protection mechanisms exist.
3. No separate client can be operated.
   

Migrating the system

1. Prepare new central system.
   
1. Check if the correct SIVIS Suite main transport version is available.
1. Make sure the main transport is imported into the new central system.
   
2. You can download the SIVIS Suite transport files from here: https://support.pointsharp.com/
   
2. Check transport logs.
   
3. Ensure that the version corresponds to the previous central instance.
2. Copy technical users from your old system.
   

   

   The following table shows default SIVIS Suite users and roles. They can vary from your system.

   User	Description	Roles
   SIVIS_BATCH	Job user, in all systems (user type system).	SSI_S_BATCH____ADM_GLOB_ALL SSI_S_REMOTE___ADM_GLOB_ALL SSI_S_BW_BATCH_ADM_GLOB_ALL (only for BW systems)
   SIVIS_DIA	If menu maintenance or Fiori for functions has been activated -> only for development systems (user type service). Otherwise, create a trusted RFC connection with registered user!	SSI_S_RFC______ADM_GLOB_ALL SSI_S_MENU_RFC_ADM_GLOB_ALL SSI_S_F4_VALUE_DIS_GLOB_ALL SSI_S_ROLE_____ADM_GLOB_ALLL
   SIVIS_DOCKER	For SIVIS Web, only in SIVIS central system (user type service).	SSI_S_DOCKER___ADM_GLOB_ALL
   SIVIS_F4_DIA	If remote value help for functions and packages has been activated (user type service):	SSI_S_F4_VALUE_DIS_GLOB_ALL SBW_BW_ENDUSR__EXE_GLOB_TEMPL (only for BW system)
   SIVIS_RFC_PM	For Password Manager Only in SIVIS central system (user type system) if SIVIS RFC connections are used.	SSI_S_RFC______ADM_GLOB_ALL SSI_S_PW_MNG___EDT_GLOB_ALL
   SENTL_ADM	For Emergency Manager (Emergency RFC Admin) In all systems (user type system).	SSI_EMG_RFC____ADM_GLOB_ALL
   SENTL_BACK	For Emergency Manager (Emergency RFC back user) In all systems (user type service)	SSI_EMG_BACK___ASG_GLOB_ALL

3. Maintain RFC connection.
   
1. Connect to the satellite/destination systems.
2. You need one back-connection for each destination system.
   
4. Copy and schedule relevant background jobs from your old system.
   

   

   The following table shows default SIVIS Suite job and program names. They can vary from your system.

   Job name	Program name	Variant	User
   SIVIS_DISPATCHER	/SIAM/V_DISPATCHER	CUS&DEFAULT	SIVIS_BATCH
   SIVIS_DISPATCHER_TIME	/SIAM/V_DISPATCHER		SIVIS_BATCH
   SIVIS_SENDER	/SIAM/C_TASK_SEND	CUS&DEFAULT	SIVIS_BATCH
   SIVIS_EXECUTOR_SYSID_CLNT	/SIAM/RM_TASK_EXECUTE		SIVIS_BATCH
   SIVIS_STAT_COLLECTOR	/SIAM/C_STAT_COLLECT		SIVIS_BATCH
   SIVIS_BACKUP_DAILY	/SIAM/C_PROJECT_DOWNLOAD		SIVIS_BATCH
   SIVIS_BACKUP_WEEKLY	/SIAM/C_PROJECT_DOWNLOAD		SIVIS_BATCH
   SIVIS_AU_IMP_SYSID_CLNT	/SIAM/C_IMPORT		SIVIS_BATCH
   SIVIS_AU_CONFLICT_CHECK	/SIAM/A_CONFLICT_CHECK		SIVIS_BATCH
   SIVIS_IMP_RG_SYSID	/SIAM/C_IMPORT		SIVIS_BATCH
   SIVIS_ASS_UPDATE_TRACE_DATA	/SIAM/AS_REF_MON_CALCULATOR	Only project number	SIVIS_BATCH
   SIVIS_ASS_JOB_HIT_PREPARE	/SIAM/AS_JOB_HIT_PREPARE		SIVIS_BATCH
   SIVIS_SENTINEL_CLEANUP	/SIAM/S_LOGIN_CLEANUP	CLEANUP	SIVIS_BATCH
   SIVIS_SENTINEL_CONTROL	/SIAM/S_LOG_READ_ACTIVE	Only project number	SIVIS_BATCH

5. Prepare the migration of the SIVIS project.
   
1. Create a file repository that the old and the new server have access to.
2. Ensure both systems can read and write from that file repository.
   
6. Create a project download on the old system.
   
7. Upload the data to the new system.
   
8. Maintain destination connections in the project settings.
   
1. Check that all RFC connections are working correctly.
   
2. Distribute the generation settings to all destination systems.
   
9. Import new license.
   
1. Download the information token with transaction /N/SIVIS/ACTIVATION to the new system.
2. Send it to your SIVIS Consultant or create a ticket via https://support.pointsharp.com/.
3. After you received a new license key, use again transaction /N/SIVIS/ACTIVATION with option Upload license.
4. Select the license and click Activate license.
   
10. Optional - Adjust SIVIS Web.
    
1. In case SIVIS Suite is used, the address to the new SAP server has to be adjusted accordingly.
   You can do this in SIVIS Web > Settings > Connected systems.
2. Activate the ICF nodes on the new central system.
   
11. Optional - Migrate custom development and exits.
    
1. Identify all custom development artifacts on the old central system.
2. Prepare a transport request for these artifacts and migrate it to the new server.