Project Migration from 7.0 to 7.1

[former_member330094]

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

[Former Member · Accepted solution]

Hi Adrian,

The only option for projects is to transport it, but you have to be

careful. The transports of projects, as far as I know will not cause

in problem between the two different solmans because it doesn't changes

anything in the basis component. You have to be careful about any other

content you transfer via transport request between systems in different

version.

The following two notes may be helpful to clarify the risks involved.

1090842 - Composite note: Transport across several releases;

556734 - FAQ Transport: Setup and further information

specialy the question 5:

"5. Are transports possible between systems with different Support

Package versions?"

kind regards, Fabricius

[former_member330094 · Accepted solution]

Hi All,

@Invyctus, you're right. The warnings are viewable in stms (enqueued transport) and are about difference of releases and component versions. Did you tried it before?

@Fabricius. Thanks for the notes. In this case we're moving from sap_basis 7.0 to 7.1. The note says, the transport is posible, but inconsistences can appear.

Regards,

Adrian

[former_member330094 · Accepted solution]

Hi All!

Ok, I finally did the import. I checked tables contained in the transport request and they matched with solman 7.1, so I finally imported projects using option ignore component mismatches. So far, it's working ok.

Now, I can say it's possible to migrate project from 7.01 to 7.1 using transport requests.

Thanks all.

Adrian

Edited by: Adrian Bazzini on Feb 1, 2012 1:33 PM

[former_member330094]

Solved

[Former Member]

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 <===

___________________________________________________________________________________________

[Former Member]

Hi Marc,

See the SAP Note Note 312962 - Termination in the transport after import.

I´ve had the same problem, but it was a isolated problem with a project.

Regards

[prakhar_saxena]

Hi

I am not sure why you are nt going for an upgrade

if you were doiong upgrade the entire project with structure will be available for without any issues

but if you are going the other way as you have mentiond only way is to move via tp

well it could be better that you upgrade the existing one to 7.1(old solman) and then move the request to new 7.1 if you dont want to use the older one.

Hope it helps

Regards

Prakhar

[former_member330094]

Hi Prakhar,

Thanks for your answer. Business needs lead to us to make a clean installation, that's because we aren't doing the upgrade.

Did you tried that? Importing a 7.0 project into a 7.1 installation? (I know tp can import unconditionally, but just to be sure that it won't break the entire project configuration). At the moment, I didn't found other way to import/export project from solman.

Regards,

Adrian

[Former Member]

Were you succesful in your attempt ? I am also in a similar situation.

Can you please share how you have proceeded?

[Former Member]

Prakhar has kind of answered that question here.

http://forums.sdn.sap.com/thread.jspa?messageID=10841072#10841072

To quote him from that thread:

When you transport a project, all project data created in SAP Solution Manager is transported:

u25CF Header data (general data, scope)

u25CF Project-specific information such as project documentation, project team member assignments, and status assignments

u25CF Cross-project information such as general documentation

u25CF Project structure and its assignments


http://help.sap.com/saphelp_sm71_sp01/helpdata/en/45/51fbdbd4941803e10000000a1553f7/frameset.htm

[former_member330094]

Hi All

Thanks for your posts.

@Invycktus

Thanks for the clarificationm, but my problem isn't the procedure. My question is about the difference of versions.

@Jacobgeorge74

I didn't tried yet. I only exported project from sm70, copy transport request files to sm71 and started import. When the warnings appeared, I stopped the process.

Regards,

Adrian

[Former Member]

I may have misunderstood this. What warnings did you get? Ideally there should be standard kernel/system difference warnings but nothing else. Since you are moving to a different system, expect the regeneration of connections to be a standard house keeping task.