cancel
Showing results for 
Search instead for 
Did you mean: 

How do I copy a template project to a template project with document links?

Former Member
0 Kudos

Hello Experts!

I am trying to copy a template project to a template project and keep the documents as Links (not copies or reference copies).

I have tried going to SOLAR_PROJECT_ADMIN and selecting template project A and copy project. This takes me to RSPROJECTCOPYSOLAR. Here there is an option to check or uncheck Documents. I have tried both and regardless if the box is checked or not the documents are copied as reference copies.

The only way I have found that has worked is to create a new project in SOLAR_PROJECT_ADMIN (Project B). Then go to SOLAR_O1 in business scenarios, on the Structure Tab select source project. Then add the scenarios from project A. When I click Copy I have the options to 'Refer to Documents', 'Copy Documents', or 'Ignore Documents'. I select Ignore Documents. After the background job is complete then I open 2 sessions in Solution Manger. In the 1st session I go Project A (SOLAR_02) and select a document to Copy (one or many). In the 2nd session I open project B and in the appropriate location Insert the document as a Link.

Do you know of a more effecient way to copy a template project to a template project and keep the documents as Links?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

The note 1236369 which explain a little about the report

SM_FOLDER_NO_REFCOPY, says the following:

"You can use the report "SM_FOLDER_NO_REFCOPY" to enter the technical

names of folders whose documents should not be copied in the table

"IWBSETTING"."

So technically, when copying a project, you'll use this report to add

in the tab "IWBSETTING" the technical names of the folders whose

documents you don't want to be copied, so you can still edit them in

the source by the copy project.

Regarding the technical name of the folders, the following rule applies

for storing documents in Knowledge Warehouse folders:

for PROJECTS:

With the exception of template projects, the system stores all documents

in a folder with the technical project name when you create them.

In template projects, the system stores all documents, with the

exception of project documents, in folder SOLAR00. Project documents are

stored in a folder with the technical project name.

for SOLUTIONS:

The system stores all documents in a folder with the technical name of

the solution when you create them.

Check the note 913175 as reference.

So if you wants to copy for example the project ZTEMP01, which is a

template project, firstly you should run the report

"SM_FOLDER_NO_REFCOPY" via SE38 transaction and add the technical name

"SOLAR00" which is the technical name of the folder where template

project's documents are stored.

Please try this process with your test project and check if the

resulting project will allow you to edit the documents directly in the

source.

It should help you in this case.

Kind Regards,

Fabricius

Former Member
0 Kudos

Thank you Fabricius! We tried this in our sandbox environment and it worked successfully and created document links when the project was copied.

Now we have encountered another issue with the copy project functionality. It seem that the 'Desired behaviour at later version comparison' is not working. When we crated the copy we selected radio button 'Adjust target project to origninal of the source project'. Later we tested by making changes to the source project - add new document, transactioin and end user role. Then ran the sa_project_upgrade on project B. We didn't see any of the yellow warning symbols on project b and the compare and adjust icon is not even enabled. Have you seen anything like this? If not I can start a new thread about this on the forum.

Thanks for you assistance,

Lori

Former Member
0 Kudos

We found another option to use with the project copy. Desired behavior at later version comparison radio button should be selected for Adjust target project to source project. This allows changes to the source project to be copied to the target project using SA_PROJECT_UPGRADE.

Answers (0)