on 03-18-2008 5:09 PM
Hello All,
Please can you help with transaction SA_PROJECT_UPGRADE, the case is as follow:
STEP 1
- Template project is created including process structure and documents, template is activated
- Implementation project: is created derived from template project.
- In Template project: Change in pocess node made: added an new process node
- Run SA_PROJECT_UPGRADE with checked box "New Version of Original" and chosen project: Implementation project
- Implementation project: the yellow boxes appears on the appropriate place and button "adjust to original" is used.
So far, so good
STEP 2
- Implementation project: a new process node is added, project is saved
- Run SA_PROJECT_UPGRADE with checked box "'Current Version in Project" and chosen project: Implementation project
- Template project: no changes are visible in SOLAR01 or SOLAR02
- In SOLAR01: settings -> User specific -> box checked "Dislay changes made in project"
So far, NOT good.
Resume:
- using transaction SA_PROJECT_UPGRADE from Template -> Implementation Project works according documentation
- using transaction SA_PROJECT_UPGRADE from Implementation Project -> Templates does not work according documentation
Does anybody recognise this?
Or do I oversee something?
System: SSM 4.0 updated to SP13
Thanks in advance
Rutger Koppelaar
Not sure if you can run SA_PROJECT_UPGRADE to check for changes made to the Implementation Project.
Functionally understand that the Implementation Project is typically for local markets/roll-outs. What that means is... if a new node is added, those changes are available within that project only. Those are "local" requirements specific to the Implementation project.
It's also important to understand the kind of Global attribute you assigned to the requirements/BPH within the Template Project. If you chose "Standard Partial", and even if you make changes to the node, you can only view them by running a comparison against the Template project and not from the "Implementation project".
In summary, any changes you make locally within the Implementation Project will remain local.
I hope that helps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ramesh,
Thanks for your answer, probably you're close to whats possible...but here I take the text of the SAP Library:
"If you execute this program in comparison mode 'Current Version in Project' it compares the current structure and business content of your Solution Manager project with it's original state that it had, when the node was copied to the project from a template or from BPR, and flags these nodes in the project. You can view the details of these changes in a dialogue on the tabs of transaction SOLAR01 and SOLAR02. The purpose of this mode is to roll back the improvements done in a rollout project to the template project to enhance it."
This text suggest that what my customer wants, should be possible...so it should be a bi-directional compare and not single directional compare
Any more suggestions?
Thanks in advance,
Rutger
Dear Rutger,
First of all, I appreciate your description of the problem in a step-wise fashion; it makes it lot easier to comprehend and respond.
Till date, there is no facility for proper 'Roll back', as admitted by SAP in other documentation. I'll try to search for that document/link where I read that and get back to you if I find it soon. If it's only in PDF format, can I send you by email instead ?
The text you have quoted from SAP help:
"...The purpose of this mode is to roll back the improvements done in a rollout project to the template project to enhance it."
(unfortunately) only means that it helps you 'identify' the changes you have in Implementation Project and thus manually introduce some/all of those in the Template Project, if you deem fit.
I wish SAP would do something about this in future releases/ support packs.
While on this Template -> Implementation Project topic, may I also alert you to a couple of other points here:
1) Please read SAP Note 603336 which explains limitations of Template approach
2) Within a Template Project, any actual changes to the document does not offer itself as a 'change' while doing comparison on Implementation Project. In other words, after a given Scenario and all its associated documentation are copied into an Implementation project, if a given document at a given node needs to be edited, it's better to create a new document and upload it in Template Project than to open & change the same document. If the same document is edited, the Compare and Adjust cannot see that as 'difference'.
Regards,
Srini
Hi Rutger,
Kindly open the PDF file on the following link:
https://websmp201.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700006829462005E
In slide 29 of 42, there is a clear mention in the 'Note!' box.
Of course, the above file is dated 24.11.2005 - however, in my knowledge and experience with SolMan so far, nothing seems to have changed.
Regards,
Srini
Hello Srini,
Thanks for reaction, to answer your question regarding the document text I quoted, you can find it on:
start transaction SA_PROJECT_ UPGRADE -> in the mainscreen there are two buttons: Execute and Program Documentation
-> push Program Documentation and the helptext appears which includes the texts I quoted.
1) I also read the note 603336 you mentioned; it seems that you're right that there is no automated support of the feedback from Implementaiton Project to Template project.
2) the point you mentioned regarding the visibility of changes documents, I already read it in the documentation, but still it's a pity that this functionality isn't available. maybe an
opportunity for SAP!!
Regards,
Rutger
Hello Srini
Thanks for the link to the PDF, yes I read it and in slide 29, I found the note box....Ok, now I know there is no automated support.
Do you have any experience with a proper procedure to handle a lot of content in the implementation projects backwards to the Template project?
Thans for your support!
Kind regards,
Rutger
Hello Rutger,
Thanks for your kind acknowledgement and generous award of points. That's a great encouragement indeed.
As regards my own experience, I have used/consulted on Template based approach a few times, but on each occassion, the objectives of Global Template team was clear and therefore achievable. In other words, the rollout projects were clearly told about the significance of keeping the Template up-to-date and where the system failed, clear business commuication came to rescue.
(1) Usually, the central pool of people who define Global Template would take complete ownership of Process design; therefore, no changes to structure of core processes are expected in Roll Outs
(2) Template Structure itself can have a few folders (Processes/ Process Steps) that are like 'Place Holders' for local, country specific usage - e.g. in a Business Scenario called Procure to Pay, under a Process called Invoice Processing, create a folder called 'Country Specific Process elements' - make the Attribute there as 'Local' and thus ensure that the Rollout implementation team include all their country specific documentation for Invoice Processing against/under that folder and not tamper with any other. This ensures that the Global Team does not have to Roll In any functionality defined in those folders - since they are absolutely local.
(3) I do agree, however, that despite whatever efforts, there will be brain-waves/ new ideas during roll out projects that the Global team should not miss out on. We can perhaps create specific documentation types that the Implementatio project should use whenever they upload 'fresh' documents that the Global Team should make note of, possibly with a Custom Status called 'For Global Team's attention' [Only in Test Cases, it may be difficult to avoid the value of 'Released']
Periodically, the Global Template team can use Reporting function (SOLAR_EVAL) and look for all such documents (filtering on those Document Types alone). As and when they introduce the documents into their Project, they can change the status of the document to other custom status(es) like "Global Team has reflected this" or "Thanks, for rollout proect only".
The benefit this can offer is perhaps a report at the end of Implementation Project as to what contributions did it make in terms of documents for "Roll In".
For 'Structure' related changes, there is perhaps no such easy way, apart from SA_PROJECT_UPGRADE - perhaps setting the variant to only show 'Structure' changes alone.
This is just an idea and I'd be glad to know if you have any other ideas as well.
Warm regards,
Srini
Hi Rutger (& all others watching this thread),
I would like to make certain corrections to one of the points posted by me:
-
2) Within a Template Project, any actual changes to the document does not offer itself as a 'change' while doing comparison on Implementation Project. In other words, after a given Scenario and all its associated documentation are copied into an Implementation project, if a given document at a given node needs to be edited, it's better to create a new document and upload it in Template Project than to open & change the same document. If the same document is edited, the Compare and Adjust cannot see that as 'difference'.
-
On the above point, I have now see better/different results with my recent work; not sure if this is version/ support package specific.
Environment:
SolMan 4.0
SAP_BASIS - Release 700 Level 0013
SAP_ABA - Release 700 Level 0013
ST - Release 400 Level 0014
-
Assumption: Both the Template and Implementation Projects are in the same SolMan instance and not a case where the Template is being transported into another instance!
-
Findings (please bear with this verbose description; one day I intend creating a Blog instead, to list all these points):
(1) In General Documentation Tab of Template Project, any changes made is instantly visible in General Documentation Tab of the Implementation project - not even dependent on running SA_PROJECT_UPGRADE transaction
If you indeed run this transaction - in foreground or background, and later check the Implementation Project, it would not highlight that node as having undergone any change. However, if you double click the document itself, you'd be pleasantly surprosed that it opens the most updated version you maintained in the Template Project. No need for 'Compare and Adjust'.
(2) In Test Cases Tab - any change you make to Test Document in Template Project is again instantly available for the Implementation Project that had inherited the document, provided no manual changes were done to that document in the Implementaiton Project directly. Again, no need to run SA_PROJECT_UPGRADE transaction or the subsequent 'Compare and Adjust' function
2a) If, however, the Test Document was altered in Implementation Project subsequently, the chain gets broken (in my understanding so far), and any subsequent changes made in Template Project does not become 'instantly' visible in Implementation Project - the two behave as though they are different documents
In such a case, if you desire to 'restore' the supremacy of Template Project's contents, run SA_PROJECT_UPGRADE transaction, and after the background job finishes, visit Implementation Project concerned. The node where the Documents differ is not highlighted (unfortunately). However, if you are aware of that node, and hit 'Compare and Adjust' button the ensuing Window does tell you with a # sign on the right hand panel that the Document has indeed changed in the original. You can 'adjust' that and save.
Once this is done, and also you vow to not change the document in Implementation Project directly, the link between the two is kind of re-established. Any subsequent alterations you make in the Test Case at Template Project would be instantly visible from Implementation Project, as before !
I have tried to explain precisely what I experiemented and found. I hope this works consistently
The ways in which Document linkages are established and pointers to KW object IDs work is rather inscrutable for me, without ABAP support.
I'll update any further findings here.
Please keep a watch.
Thanks and regards,
Srini
Hello Srini,
Thanks for your investigations into this subject. I've tried to follow your steps and my findings are as follow:
Step 1
- Create new Testdocument in Template project tab Test Cases, save project.
- Run SA_PROJECT_UPGRADE in Implementation project and after a while the "change sign" becomes visible
- I adapt the change via button "adjsut to original", so both Template project and Implementation project are equal.
Step 2
- I updated the content of the Test document in the Template project and changed the status of the document, and save.
- Go to the Implementation project and open in change modus the same document, my updates done in the template original were
NOT visible in the document of the Implementation project.
- Push the button "adjust to Original" and in the right panel of the screen the # sign indicates a change of the document, I adjusted
the document.
- Then all updates of the document are visible, including the status change.
My findings according Step1 and Step 2 suggest that changes in the template original are not visible WITHOUT running SA_PROJECT_UPGRADE.
Beaware of that the default route always is: From Template to Implementation Project, SSM is not able to handle updates From Implementation Project to Template Project, unfortunately.
System version: SSM 4.0, SP13.
Kind regards,
Rutger
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.