Solution : https://service.sap.com/sap/support/notes/198140 (SAP Service marketplace login required)
Summary :
This SAP Note delineates the processes involved in reassigning systems to new installation numbers, either within the same or a different customer number. Essential steps include creating or updating installation requests, and managing license keys and developer keys accordingly. Changes in installation number require new license keys and involve deleting old license data. For Business Objects systems, existing licenses must be verified, though no new keys are allocated. Key aspects include system, developer, and object key management, reassignments within corporate functions, and contacting SAP contracts for procedures. Recommendations are provided for handling procedure changes through SAP Service Marketplace and necessary authorizations for system data maintenance.
Key words :
'reassigning sap business suite systems' section, component xx-ser-sapsmp-sscr, reassigning sap business suite systems, reassigning sap business objects systems, reassign sap business objects systems, component xx-ser-likey, access sap service marketplace, system number customer hardware key, relevant sap contracts department, installation number system id
Related Notes :
| 1566573 | Most common SAP BusinessObjects license key related issues |
| 1251889 | License key request for SAP BusinessObjects |
| 1237057 | ABAP system renamed im SLD |
| 1073356 | Effects of an AS ABAP system move on SLD data |
| 870871 | License key installation |
| 836348 | License key: "This system's system number is ..." |
| 816861 | |
| 105132 | Reserving namespaces |
| 94998 | Requesting license keys and deleting systems |