The idea is to know what documents (Customer Input Template, Configuration Guide, etc) SAP proposes must exist in each level of a Business Process Structure (SOLAR01) for instance, at Business Process Level, Process Step Level, etc.
The short answer is - No. there are really no hard and fast rules. Which Document Type each project ends up using, in whatever Tab are subject to following factors, to name a few:
Now, some Philosophizing talk
(a) Is SAP handed methodology - Global Template Roadmap or ASAP Impelemtnation Roadmap etc. - followed completely, in letter and spirit ? Or is it a case of own methodology using a mix of SAP terms with consulting firm specific approach ?
(b) At which stage of the Project is SolMan being introduced - is it a case where most documentation is already done and now needs to be loaded back to SolMan retrospectively Or, is it a fresh, ground-up Project offering scope to define the way everyone will agree to?
(c) What sort of documents does the implementation team intend handing over to Application Management team later ?
(d) Are Blueprint & Config Guide documents supposed to be 'generated' out of Solution Manager - if so, the constituent documents that would make them up will have to be thought through more diligently and captured at right levels
Well, if your project is as fresh as frost clearning grass, try following some suggested practices/checklists from SAP, loaded as accelerators within Roadmap concerned:
(a) Go to transaction RMMAIN
(b) Choose 'No Project' and select the relevant Roadmap that yuo are expected to follow
(c) In the 'structure view' of Roadmap, place cursor on the highest node [e.g. ASAP Implementation (V 3.7 Jun 2007)] and Goto Accelerator.
(d) This would list ALL Accelerators provided by SAP for the Roadmap
(e) Find accelerators with 'Solution Manager' as a term and explore each link - you may eventually find some URLs and documents.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.