Transporting Project

Hello Friends
we have created the entire project in solution manager and now we want to shift the whole project to production server how is that possible
Note
Presently we have configured Development Server of Solution Manager with
Development & Quality Servers (only one server diff clients)
R3 & CRM
now we want to transfer all the settings that we have done on quality server of R3 & CRM to production server
but through solution manager only
it is possible through client copy or transport request or migrate the whole server or any other way
please let me know
regards
Neha Shah

Hi,
As i had mentioned earlier, i had posted this similar message with OSS, and following is the reply i received, and i will be testing soon.
there is a transport functionality for all types of project available.
Please start transaction SOLAR_PROJECT_ADMIN, select the implementation
project and push the button transport Project.
Please ensure that your Solution Manager runs on the latest Support
Packages otherwise it could be that some documents will be not
transported.
I hope that this information will help to solve the issue.
Hope this helps.
Cheers,
Chetan

Similar Messages

Transporting projects from Dev. system to Prod. system

We have created a number of projects in our development system and now want to move a few of the project to our production system.
Is there a way to transport these projects to the production system
Regards
Don

Good Day......
I have used "the truck" and everything seemed to work ok. Transport was created and we migrated the transport to the production Solution Manager system.
When I tried to open the project in Project Admin/Solar01 I got the following message.
"The specified structure does not exist"
Any thoughts........
As well, is there a way to include all of the project documentation within the transport.
Regards
Don

Transporting Projects in v12

We are getting ready to begin the upgrade process to v12 from 11.5. We have a number of plant metrics up and running in 11.5 that we'd like to continue to transport individually through our server landscape. All the metrics are in the same server folder with the plant name and metric number specified in the template/transaction/irpt file name.
Should we move each metric into its own folder prior to migration to help identify them as individual projects for transport purposes?
Thanks in advance,
David

Thanks, Udayan. I probably shouldn't have used the word 'metric'. I was just using the term to refer to graphs of plant performance with data coming out of SAP and the plant's PI data historian.
The templates for all the graphs are in the same v11.5 folder, like so:
Lighthammer
Illuminator
    Templates
      Metrics
          ING001Query.xml
          ING001SPCChart.xml
          ING002Query.xml
          ING002SPCChart.xml
          (and so on)
and we will want to be able to transport graph ING001 separate from graph ING002. I'm assuming, once migrated to v12, they have to be in separate "projects" in order to be transported separately and I wasn't sure if, for migration purposes, items I wanted in separate projects could be in the v11.5 folder.

Transport Projects

hello,
I have SolMan 3.20 and want to transport my project into new Solution Manager.I create a transport request, using Progect-->Transport and moove it into new SolMan. The structure of the project appeared but there are no project documentation in new SolMan. How can I transport doc`s?!

Hi hav u chkd this note....shd solve u r prb
Note 823347 - SOLAR_MIGRATION: Project documents missing after migration
In addition,
Note 990179 - SOLAR_MIGRATION: Test notes and documents
Note 644123 - Migration of Solution Manager data from 2.1/2.2 to 3.1/3.2
Regards
Prakhar

Transporting Projects in SolMan

Hi,
I have a simple question regarding the transporting of project templates between SolMan systems.
I understand that it is a best practice to have the source and target system at the same patch level when performing this task.
Does anyone know if it is this process is backwards compatibile? In other words, is there a risk if I am transporting to a target system that is at a high patch level? (NW70 EHP1 SP20 --> NW7- EHP1 SP22).
Is there an OSS note that addresses this issue for NW70? I haven't found a note newer than 603336.
Thanks,
Bill

Hi William,
Please refer Note Note 1090842 - Composite note: Transport across several releases . Ideally target system should be equal patch level . If it is lower , then it would be complex and probably you cannot . If it is higher, we can have a try I guess . But you may need manual modification , some times.
Regards,
Nibu Antony

Transports - Project

Hi All
I had a question regarding transport requests. When I get a transport request prompt , there is a place to enter Project .
Has this anything to do with Project Systems . And is it true that I can select a project only when my company implements Project systems or it has nothing to do with PS.
Thanks

Hello Christina,
This project has nothing to do with PS module.
Go through this link to understand about projects in transport
http://help.sap.com/saphelp_nw04/helpdata/en/4a/a528372e026b52e10000009b38f936/content.htm
Regards,
Praveen

Solman project transport from one server to another

Hi All,
i have a small query , regarding project management . I have a Template project with some manually designed tamplate inside that. and test case created.
Now i want to move this project with all config. , selected template and test case from one server my another solman server.
I am hoping transport icon given below in solar_project_admin will work for me . please confirm me and let me know if other options too available . can i use solar_migration for this activity ??
please suggest all possible way for export (transport) this project from one server to another.
Thanks
gyanP

Unfortunately, transaction SOLAR_MIGRATION is not released to be used in the Solution Manager 4.0/7.0 and therefore is not supported.
See also the PDF-document: 'SAP Solution Manager - Content Transfer'
which can be found at:
http://service.sap.com/solutionmanager
-> Media Library
-> Technical Papers
Besides the "Transport Project" functionality in SOLAR_PROJECT_ADMIN for projects and the transport of testpalns from transaction STWB_2 there is no other function available/supported at the moment.
you have to make sure that you have in the source system the corrections from the notes:
for Projects:
1147186 Unreleased documents are not transported
1119462 Problems transporting projects
1134578 Document types missing when transporting projects
For Testplans/testpackages:
1224283 Test plan incomplete after transport
1246383 Transport connection for test documents in test plan

Solar_project_admin to transport whole project

We have some documentation in Solution Manager (in transaction "solar02"). It is version 3.1 we are using.
We have to transport Documentation of project "smart" to a newer Solution Manager(version 3.2). However project "smart" exists aso on newer Solution Manager system but can be overwritten.
I am pritty new in Solution Manager.
I wander if transport function (track icon) can be used in transaction "solar_project_admin" to transport whole project to transport files and then import them to newer Solution Manager

Hi,
check this
http://sap.ittoolbox.com/groups/technical-functional/sap-solution-manager/where-are-uploaded-office-documents-physically-stored-in-sap-2647587?cv=expanded
as per above link u can try with option
1.
use Tcode - SOLAR_PROJECT_ADMIN
1. Select the project in the project overview.
2. Choose the Transport Project pushbutton or Project ® Transport.
3. Specify the transport scope in the following dialog box. To transport the project without project documentation, reset the With Notes flag. The project documentation is transported by default.
4. Specify a transport request or create a new one.
5. Save your entries.
Regards,
Ravi

Error while approving change document(TR lost project code)

Hi All,
I am having issue in change document approval, when we are approving change document for unit testing or if release management approving change for pre-production or production approval, we are getting error, I started coming from last two days only,\
when I did detail analysis, in all transports project code related to change document, disappear
although if I create new change document, project code appear,
Do we have way to solve this issue?, I even not able to decouple the transport from change document, it giving error, do we have way where we can resync change document and transport?
Dinesh

Hi All,
Do anyone have some solution for this issue?, it is bigger than I thought, I can check it impacted all systems, and all transports, all transports seems to issue they lost project code in it we rollover maintenance cycle last week and this problem started from their, we put charm master note and few other charm fixes(notes) last week,
this problem not coming any new change document, but all change document created before rollover impacted
Dinesh

Problem in moving project from Old Sol Man 3.1 to New Sol Man 4.0

Hi All,
I am trying to move a project from solution manager 3.1 version to a new solution manager 4.0 version. I followed the below steps:
1.Slected and transported the project using solar_project_admin tcode and created the transort requests in the old sol man version 3.1.
2.Copied the cofile and datafiles from old sol man and kept in trans directory of new Sol man 4.0 version at OS level.
3.Imported the requests into the new Sol Manager 4.0 successfully
4.When I tried to open the imported project it told me to run the "solman_log_comp_mgr program" to convert the project to the central logical components. I just did it and it went well.
I can see the project and do see the document types but no document names and getting all sorts of error messages when I tried to open these documents. Also I dont see the logical components under system landscape.
Before importing, I just have configured servers/hosts, databses and all the components of system landscapes in the new solution manager.
I request you to help me solve this issue. I also would like to know whether i followed proper procedures that i listed above? If not please suggest what procedures I should have follwed.
Thanks in advance.
Aravind Serikar

Hi Aravind,
to transport a project from 3.1 to 4.0 I would not use SOLAR_PROJECT_ADMIN to "migrate" a project. There for we developed SOLAR_MIGRATION there you can transport system landscape info, also you can transport projects. You should only transport system landscape info if in 4.0 SMSY is EMPTY. To transport projects you have only to specify your project and define a local folder. In this folder we store a few important information. Then all information will be collected in a batch job and automatically exported. Then you have to copy the data file and the cofile into the new trans folder. BUT do NOT forget the i-file. In the folder cofiles you will find a i-file, because we export knowledge warehouse content. This file is important, if you forget it you will get a return code 8. You do NOT have to add the files in the import buffer, we will do this automatically. To import the project, you have to call SOLAR_MIGRATION in SolMan 4.0 there you have to select import, then specify the folder with the few important information. We upload the info and start the import. That is it
Regards,
uDo

Syncing a project in QA...

The SolMan project creates its own IMG (say Project A), but I have replaced this with an existing IMG (Project B) on the dev system.
Now I add a QA system in the SolMan landscape. How does one ensure that Project B would get synced on the QA system.
In fact, using SOLAR_PORJECT_ADMIN and then going to System Landscapes > IMG Projects, the IMGs shown under Development System and Quality Assurance System are different.
Development System shows Project B ( the replaced one from the dev system) and the Quality Assurance System shows Project A (the original IMG created by SolMan).
This seems to be a strange situation, but the IMG was already created on the dev and Sol Man introduced later into the landscape.
Any suggestions, ideas, comments are welcome ...

Thanks Prakhar.. appreciate your quick response.
I had already transported Project B from dev to quality and had done the replacement in the same way that you have just suggested (replacing Project A by Proejct B in SolMan).
However, I am not sure if this arrangement will ensure that the dev and QA are always in sync. What has you experience been so far on this? Or point to any links on sdn, smp etc.?

Project Migration from 7.0 to 7.1

Hi Experts,
We are performing a clean installation of SM7.1. We already have another SM 7.0 instance which will be replaced by this new one (this is not an upgrade project, it's a clean installation).
Is there any way to transport project & documentation created in 7.0?
We tried creating transports request from solar_project_admin, but in the import phase so many warnings appears because versions.
Please advice if its normal, or if exists a workaround.
Regards,
Adrian

Hey,
we also face the same problem. We want to transport our projects from a SolMan 7.0 to a new SolMan 7.1 System.
When i import my transport into the target system (7.1) using option ignore component mismatches I always runs into RC8 (error in Post-import method SDOK_FILE_TRANSFER_AFTER_IMP). Did you have the same probleme? How to solve that? Thanks!
Here is the Log:
Post-import method SDOK_FILE_TRANSFER_AFTER_IMP started for SAPH L, date and time: 20120214141725
Start of processing for request XXXXXXXXX, time 14:17:25
Message 705: (SAPKPROTP Error: Could not open Transport File for reading)
Start of recovery for logically motivated categories
End of restoring for logically motivated categories
Start of indexing
39 documents were reserveed for indexing for document class SOLARGNSRC
End of indexing
Errors occurred during post-handling SDOK_FILE_TRANSFER_AFTER_IMP for SAPH L
SDOK_FILE_TRANSFER_AFTER_IMP belongs to package SDOK
The errors affect the following components:
     BC-SRV-KPR-DMS (Document Management Services)
Post-import method SDOK_FILE_TRANSFER_AFTER_IMP completed for SAPH L, date and time: 20120214141725
Post-import methods of change/transport request XXXXXXXXX completed
       Start of subsequent processing ... 20120214141725
       End of subsequent processing... 20120214141725
   Execution of programs after import (XPRA)
   End date and time : 20120214141725
   Ended with return code: ===> 8 <===

Moving Project from one solman to another

Hi Friends
Can anyone help me in moving the project prepared in one solution manager to different solution manager.
We have got solution manager and is productive and another is training and we are going to upgrade our productive solution manager 4.0 to 7.0 but before that we need to move the project into training solman.
can any one suggest me what could be the procedure.
Waiting for your precious response
Thanks and Regards

Hello,
There is an option of project transport.........in solman.....so u can create a transport request for the project you had created..........and then import this transport request into the solman system u want to.....
If both your solmans are not linked thru the TMS,then u got to manually copy the Data and CO-files...just consult basis guys for this........
U find the option of transport project in tcode SOLAR_PROJECT_ADMIN... There is an icon just below on the left......u should use that to transport the project....basically u will be prompted for the transport request...this transport has to be imported into the solman system u want.....
Inspire ppl by rewarding.........
Regards,
Anand

Difference in Transport Request in SOLAR_PROJECT_ADMIN & Quality Gate

Hi
I want to ask about how Quality Gate works in an Implementation Project??
How a quality manager role comes in action?? how a project is transported into landscape??
What is the difference in creating transport request from SOLAR_PROJECT_ADMIN and creating Transport request from Quality Gate Management in Change Management Workcenter???
Please guide
Thanks & Regards
Sidra

Hi,
check this
http://sap.ittoolbox.com/groups/technical-functional/sap-solution-manager/where-are-uploaded-office-documents-physically-stored-in-sap-2647587?cv=expanded
as per above link u can try with option
1.
use Tcode - SOLAR_PROJECT_ADMIN
1. Select the project in the project overview.
2. Choose the Transport Project pushbutton or Project ® Transport.
3. Specify the transport scope in the following dialog box. To transport the project without project documentation, reset the With Notes flag. The project documentation is transported by default.
4. Specify a transport request or create a new one.
5. Save your entries.
Regards,
Ravi

Document statuses of migrated project not gettign displayed

Hi Gurus,
We migrated the project using 'Solar_Project_Admin'. All documents get populated correctly. But the problem is staus of documents are not getting migrated. Where as the status scemas were traported before project. So, all the status scemas for dcouemnt types are available in migrated server. Even the migrated project shows attached statuse scemas to document type.
Eventhough the status is not getting displayed.
Please guide me if I missed out any step.
Thanks & Regards,
Vrushali

Hi Gurus.
I am transporting project with SOLAR_PROJECT_ADMIN and all documents that are in status RELEASED are transported, but documents in status IN PROCESS are not.
Any idea?
thx

Transporting Project

Similar Messages

Maybe you are looking for