在看ITPUB的時候，無意中找到"潛龍勿用"的博客，從博客主人的資料看，作者Ryan是一個SD顧問，他的這篇文章是關於SAP的SD模塊實施的一些經驗總結，我看了其中的內容，覺得相當的好，雖然我不是學習SD的。所以我在此轉載了。作者是從實施顧問的角度來看問題，這對我這個PP Key User理解SAP實施是有幫助的。
原文地址：
http://gqlny.spaces.live.com/blog/cns!9E1B98E7AB455851!2455.entry
As per my experience and understanding, following points which I learnt from GFAU rollout may contribute to a successful rollout project. These points listed below doesn't work as a SD specific guideline, it pretty much may be regarded as experience sharing.
1. Template knowledge transfer and customer customized solution
As far as I'm concerned, usually we are likely to build up the questionnaires from standard SAP view, but customer maybe have customized many add-ons based on SAP standard functions. So those customer specific solutions, on which should be put more effort for discussion. The more information we get, the easier we can tackle surprises on following phases. Especially for those highly customized system by customer, like GFAU. Both customers and SAP team were bombarded by heavy email communication during realization due to lack of enough global template knowledge.
2. Fit/Gap analysis
Elaborate the template to local customers, and try to note down their local requirements in detail whatever it makes sense or not. Afterwards, all those information different from template can be translated in to GAP list. From time to time, the point which is ignored on this phase, may be raised again on system realization, as customer sometimes is not quite sure what's their exact requirements. It may involve group discussion from different departments. Finally, double check with local key user to minimize the GAP, and stick to it.
3. Output forms
The Form format is also a key point for SD. It may involve some of followings in one project, order confirmation, delivery note, goods issue slip, normal invoice, proforma invoice, credit and debit memo, etc. During GFAU realization, we spent big chuck of time on discussing the layout and testing . So it's better to have customer prepare the format in advance, latter we can spend less time polish the layout.
4. SD customizing list
During my last project, before the knowledge transfer, I built up a customizing list which contains almost all SAP standard functions used by customer, for example, sales order types, item categories, pricing procedure, partner determination, billing types and output types, etc. Since not all of them can be implemented in China, it speed up the knowledge transfer by marking China relevant items directly in the list instead of navigating in SAP. And it's easier to discuss based on one Excel book.
5. Issue list and report
From project management point of view, in order to avoid email overload and miscommunication, the approach for issue raise and status report should be discussed and finalized at the beginning. Also it helps to put both customer and SAP team into the same picture.
One more point, it makes more sense to understand customer's business process from his/her point view instead of sticking to SAP standard solution, which can prevent us from missing some points. That's all what I learnt from my previous project experience. Hope it helps.