2136149 - Empty Roadmap After Transport
2
SAP Note Header Data Symptom You have transported a roadmp from one system to another. But if you open the transported roadmap, there is no structure in it. Other Terms Roadmap transport, no structure, empty Reason and Prerequisites Prerequisites for the symptom described here: l The error occurs in a roadmap. l The roadmap has been imported into the current source system by transport request from initial original system. A transport request of the type "Relocation" was not used, but rather a "Transport of Copies" or a "Workbench Request". Cause of the symptom: l The structure elements in roadmaps are transportable objects of the type SHI3. Transportable objects have an original system that controls the system in which these objects can be changed. The original system is the system in which the objects were created. When you create an object, this is automatically set by the system and also for the structure elements in roadmap. l The system in which your roadmap was originally maintained transports your roadmap to the current system. However, the original system of the structure elements is not adjusted to the new system. l This adjustment can occur automatically if the roadmap is transported from the initial original system to the new system using a transport request of the type "Relocation". l However, the transport function in transaction RMDEF does not provide this relocation option but always generates a transport of copies/Workbench Request automatically. If you want to further process the transported roadmap in the new system, the roadmap must also be subsequently transported into this system using a relocation transport to ensure that the original system for the roadmap is adjusted to the new system. Relocation transport To move the project from the initial original system to the new system, proceed as follows (see also the Transport Organizer documentation): l Create a relocation transport in the initial original system in the Transport Organizer. To do this, select the "Relocation of Objects Without Package Change" option and, as the target system, enter the system in which you want to further process the project. l In the relocation transport, include the objects from the transport of copies that was already created for your project using transaction SOLAR_PROJECT_ADMIN. l Export the relocation transport in the initial original system. l Import the relocation transport into the new system. This adjusts the original system of the transported structure elements to the new system and allows the project to be further processed there in future. Solution Relocation transport To move the roadmap from the initial original system to the new system, proceed as follows (see also the Transport Organizer documentation): l Create a relocation transport in the initial original system in the Transport Organizer. To do this, select the "Relocation of Objects Without Package Change" option and, as the target system, enter the system in which you want to further process the project. l In the relocation transport, include the objects from the transport of copies that was already created for your roadmap using transaction RMDEF/ report RM_TRANSPORT. 2136149 - Empty roadmap after transport Version 1 Validity: 27.02.2015 - active Language English (Master) Released On 27.02.2015 09:51:07 Release Status Released for Customer Component SV-SMG-IMP-RDM Roadmap Functionality Priority Correction with medium priority Category Program error
-
Upload
aliciacgsof -
Category
Documents
-
view
3 -
download
2
description
You have transported a roadmp from one system to another. But if you open the transported roadmap, there is no structure in it.
Transcript of 2136149 - Empty Roadmap After Transport
-
SAP Note
Header Data
Symptom
Youhavetransportedaroadmpfromonesystemtoanother.Butifyouopenthetransportedroadmap,thereisnostructureinit.
Other Terms
Roadmap transport, no structure, empty
Reason and Prerequisites
Prerequisites for the symptom described here:
l The error occurs in a roadmap.
l The roadmap has been imported into the current source system by transport request from initial original system. A transport request of the type "Relocation" was not used, but rather a "Transport of Copies" or a "Workbench Request".
Cause of the symptom:
l ThestructureelementsinroadmapsaretransportableobjectsofthetypeSHI3.Transportableobjectshaveanoriginalsystemthatcontrolsthe system in which these objects can be changed. The original system is the system in which the objects were created. When you create an object, this is automatically set by the system and also for the structure elements in roadmap.
l Thesysteminwhichyourroadmapwasoriginallymaintainedtransportsyourroadmaptothecurrentsystem.However,theoriginalsystemofthe structure elements is not adjusted to the new system.
l Thisadjustmentcanoccurautomaticallyiftheroadmapistransportedfromtheinitialoriginalsystemtothenewsystemusingatransportrequest of the type "Relocation".
l However, the transport function in transaction RMDEF does not provide this relocation option but always generates a transport of copies/WorkbenchRequestautomatically.Ifyouwanttofurtherprocessthetransportedroadmapinthenewsystem,theroadmapmustalsobesubsequentlytransportedintothissystemusingarelocationtransporttoensurethattheoriginalsystemfortheroadmapisadjustedtothenew system.
Relocation transport Tomovetheprojectfromtheinitialoriginalsystemtothenewsystem,proceedasfollows(seealsotheTransportOrganizerdocumentation):
l Create a relocation transport in the initial original system in the Transport Organizer. To do this, select the "Relocation of Objects Without Package Change" option and, as the target system, enter the system in which you want to further process the project.
l In the relocation transport, include the objects from the transport of copies that was already created for your project using transaction SOLAR_PROJECT_ADMIN.
l Export the relocation transport in the initial original system.
l Import the relocation transport into the new system. This adjusts the original system of the transported structure elements to the new system and allows the project to be further processed there in future.
Solution
Relocation transport
Tomovetheroadmapfromtheinitialoriginalsystemtothenewsystem,proceedasfollows(seealsotheTransportOrganizerdocumentation):
l Create a relocation transport in the initial original system in the Transport Organizer. To do this, select the "Relocation of Objects Without Package Change" option and, as the target system, enter the system in which you want to further process the project.
l Intherelocationtransport,includetheobjectsfromthetransportofcopiesthatwasalreadycreatedforyourroadmapusingtransactionRMDEF/ report RM_TRANSPORT.
2136149 - Empty roadmap after transport
Version 1 Validity: 27.02.2015 - active Language English (Master)
Released On 27.02.2015 09:51:07
Release Status Released for Customer
Component SV-SMG-IMP-RDM Roadmap Functionality
Priority Correction with medium priority
Category Program error
-
l Export the relocation transport in the initial original system.
l Import the relocation transport into the new system. This adjusts the original system of the transported structure elements to the new system andallowstheroadmaptobefurtherprocessedthereinfuture.
Important: Ifyousubsequentlytransporttheroadmapusingarelocationtransport,theroadmapinthetargetsystemisoverwrittenandallchangesmadesincethelastroadmapimportarelost.
Iftheroadmapinthenewsystemhasalreadybeenchanged,donotsubsequentlyperformtherelocationtransport.Inthiscase,adjust the original system manually as described below using the report RSOLAR_ROADSTRUCT_SET_SRCSYSTM.
Manual adjustment of the original system
Ifyoucannotperformarelocationtransportasdescribedabove,youcanalsoadjusttheoriginalsystemofyourroadmaplocallyinthesysteminwhich you want to further process the roadmap/ transport to another system.
Unlike a relocation transport, in this case the original system is adjusted in this system only and not in the initial original system of the Roadmap.
YoucanadjusttheoriginalsystemforyourRoadmapusingthereportRSOLAR_ROADSTRUCT_SET_SRCSYSTM.
If the report RSOLAR_ROADSTRUCT_SET_SRCSYSTM is not yet available in your system, use transaction SNOTE to implement this note in your system. This creates the report in your system. After that maintain the follwoing text symbols and Selection Texts in your report.
SymTextdLenmLen
001OriginalsystemChanged2345
NameText
LANGUAGELanguageKey
NEW_SYSTNewOriginalSystem
P_DEVCNewPackage
ROADTEXTRoadmapName
1. Use transaction SE38 to run the report RSOLAR_ROADSTRUCT_SET_SRCSYSTM.
2.EntertheRoadmapwhoseoriginalsystemyouwanttoadjust,andalsotheneworiginalsystem(andnewpackagenameifyouwant).
3. Execute the report.
Oncethereportiscompleted,youcanmakechangesinyourRoadmapagainorYoucantransportfurthertoanothersystem.
Validity
Correction Instructions
Software Component From Rel. To Rel. And Subsequent
ST 710 710
Correction Instructions
Software Component Valid from Valid to Number
ST 710 710 1861637
![GGG European Biomethane Roadmap final€¦ · 5 2050 Energy Roadmap COM (2011) 885 final] 6 Roadmap to a Single European Transport Area COM(2011) 144 final (28.03.2011) Page 10 of](https://static.fdocuments.net/doc/165x107/5f209763ee497c5e280fe75f/ggg-european-biomethane-roadmap-final-5-2050-energy-roadmap-com-2011-885-final.jpg)
