尤尼佳proj_xp.docVIP

SAP PORTALS July 11, 2002 10:00 a.m. CDT Coordinator Good morning, and welcome to the Project Experience Do’s and Don’ts conference call. All participants will be able to listen only until the question and answer session of today’s call. At this time, I would like to introduce your moderator for today, Ms. Paula Gist, the I-Consultant in Integration Platform RRG from SAP Labs. Ma’am, you may begin when ready. P. Gist Good morning everyone, and thank you for joining the call. Our presenter for today is Michael Schuhmacher. Michael is a member of the integration platform rig for SAP AG Europe, and Michael has been with SAP for approximately four and a half years. His topic today is Project Experience Do’s and Don’ts. Mike’s presentation will be approximately 30 minutes, leaving 30 minutes for QA. If you haven’t had an opportunity to download … as of yet, please go to service.SAP.com, SAP Portal, products, business Intel, business information warehouse. I would like to welcome Michael Schuhmacher to the call. Hello, Michael. M. Schuhmacher Hello, everybody. A warm welcome from my side for this day’s presentation. It’s about do’s and don’ts. I call it Project Experiences, and today the presentation came out of the experiences we have done during our reviews at the customer sites. I wanted to split up the different points into success factors, how I called it which our project procedure related issues or recommendations and some do’s and don’ts in the technical implementation, which means more data modeling data flow related. Let’s go to page three and start with the success factors. The outcome of the business grouping phase should be a complete business blueprint documentation. That’s why in your projects, it’s really helpful to create complete documentation for this phase, which means the angular requirements have to be documented. There should be a design document and furthermore, a technical specification. Let’s go more into detail of these bus