Vous êtes sur la page 1sur 20

Integration of SAP

European Microsoft
SharePoint Conference
2007

February 12th to 14th, 2007


Convention Center
Hotel Estrel, Berlin, Germany
Agenda
Teams on the Use Case

Current environment

Requirements for a new platform

Prototyping with MOSS 2007

Requirements of CRM Portal

Technologies for SAP integration

CRM-Portal and functions

Detailed view on implementation steps


Teams on the Use Case

Project responsibility Customer Assessment and review


MOSS specific consulting Support in planning and
MOSS customizing and designing
development Carry out Hands-On
Management of Support Workshops
by MS CS Added Value: newest
Information directly from
MICROSOFT the manufacturer
Consultant Consulting
Services
Current environment

Many department
Microsoft
Enterprise
IT-Strategy
specific Agreement
applications
Standardization

Utilization of existing licenses


Project specific SAP
WIKIs a.o (ERP, HR, SRM, Utilization of existing (in-house)
BW, Portal 5.0) knowledge

User friendly GUI (intuitive)


Hyperwave
(for the intranet)
Process oriented interfacing
Requirements for a new platform

Document Management Integration Teamsupport

Long lasting ERP Systems (SAP) Information Portals


Document Lifecycle Databases (MS SQL, Process support
Management MySQL, Oracle) through workflows
Flexible search Fileservices on central Project oriented
through storage (NetApp) authorizations based
heterogeneous Online Libraries on Active Directory
sources Full integration of
Different standard
Web-based access in interfaces ( e.g. IXOS multiple team
a from Linux through Archive) calendars into
NT to XP client individual calendars
environment MS Project integration
(with SAP integration)
Prototyping with MOSS 2007
Arguments for MOSS 2007
The Client Office System 2007 is perfectly integrated
Client integration Saving centralized is as easy as locally
Use of forms and metadata is as easy as possible

Visual Studio 2005 is a standard development environment for us


Visual Studio It is always easy to find affordable external partners with Visual Studio 2005
2005 know-how

The layout of sites can easily be designed to our needs


Easy design tool Predefined layouts for teams and individuals for everybody

Active Directory groups can be maintained by end-users for their belonging


Active Directory (done today for file server access)
integration Existing groups can be used for authorizations within MOSS 2007

Connectability to Nearly all other applications can be integrated in processes and workflows
third party Weaknesses can be overcome by integrating third party applications (e.g.
OpenText for additional document management features)
applications
Prototyping with MOSS 2007
Steps for decision
Technical
Use cases evaluation
Definition based on Functional
current system availability check
Evaluation on based on for the
current system by current system and
users the prototype

Prototyping Use cases


Low budget Evaluation on
prototyping based prototype by users
on use cases and with support of
add-ons specialists
Prototyping by
Merentis with
support of Microsoft
Prototyping with MOSS 2007
Work Items
Customer Contact Management
Workflow for Proposal Management and Order Initiation
Relationchip Interface to SAP Order Management
Management This is a Final Solution an not just a prototype

Versioning
Document Web based Classification
Client (MS Office) based Classification
Management Looking for weak points

SAP Integration
MS Office Integration (Workflow)
Integration Integration of Storage, Company Wikis
Integration of existing AD User Groups for Authorization
Prototyping with MOSS 2007
Technical Evaluation
Current System MOSS 2007

100%
90%
80%
70%
60%
50%
40%
General requirements for SAP integration

Data exchange and process-integration


Office 2007 Server and Clients for data-entries but SAP is the leading system

All business relevant data have to be transfered to SAP

Changed data in SAP have to be pulled back to MOSS2007

SAP managed data (incl. archive), have also to be accessable through MOSS 2007

The process-flow has to integrate SAP and MOSS 2007 at any stage
Case requirements CRM portal
Technical needs for SAP integration
Online data-access (customers, contacts) from MOSS
into SAP

Managing records (e.g. edit/add contacts) in Portal

Synchronize data between MOSS and SAP

Handling process(es) in Portal (request for


quotation, proposal,..)

Trigger process in SAP (e.g. proposal) and track result of


SAP
Existing technologies for SAP-Integration

Core RFC (SAP Reading some data from common data-tables of SAP or
calling some RFC-functions
dot.net connector)

Soap Calling functions via Netweaver

Comfortable data-access for the realized business-


Duet objects from office-clients

IFrame-WebPart (e.g. SAP EP iViews)


MOSS WebParts SAP-WebPart (implementing web based SAP
transaction-dialogs

3rd Party IQL-Studio


Reasons for decision of IQL-Studio
Server and service based interaction with SAP meta-data repositories
(with and without Netweaver)

Complete function and data-access including APPEND-Structures, Queries, BAPI


using Dot.NET Framework 2.0

Support for multi-system environment (Development, Training, Prod.)

Encapsulated development of SAP and SharePoint/Office-Team

Testing and Debugging cross-plattform (VS2005 through TC:SE37)

Automated code- and documentation generated with Plug-In for VS2005


integrating sap data-access
Displaying
Customer and
contact-data in
multiple views
Displaying details of
the contacts with
marketing-flags
Adding and Editing
Customer and
Contact data
Handling projects as
InfoPath-files and
other related
documents in an
document-library
with special policies
and categories
Triggering SAP-Backend
InfoPath-Formular with
multiple views for the
steps of project:
Customer enquiry
Calculation
Quotation
Order
Confirmation
Reading data from the
portal lists and SAP
within the infopath
combo-boxes
Generating e-mails to
give information of next
step to the defined
ressources
Triggering SAP BAPI to
generate quotation in
SAP
Implementation steps data-access
Creating Sites with BDC (business-data-
catalog) and ListElements for view, edit and
MOSS2007: add records (customers, contacts, details)

Generating Business Entity via Designer


IQL- CustomerMasterData
Designer:

Modifying generated Code to fit our needs.


VisualStudio
2005:
Implementation steps SAP-backend
Developing InfoPath-Formular with multiple views
Integrating formular into the document-libraries and
MOSS2007: CRM-Portal using Forms-Server

Generating Business Entity via Designer based on


IQL- existing BAPI GenerateQuotation
Designer

Modifying generated Code to fit our needs.


VisualStudio
2005:
Alternative scenarios for the Office System
E.g. existing Enterprise Agreement or need for an Office Upgrade
With less focus on 3rd Party Integration
Microsoft
MS Office 3rd Party
Office
SharePoint Application
System 2007
Server 2007 Integration
(Client)

E.g. strong need for a Portal Solution and a high focus on


3rd Party Integration
Microsoft
MS Office 3rd Party
Office
SharePoint Application
System 2007
Server 2007 Integration
(Client)
We thank you for your attention

ATLAS ELEKTRONIK GmbH MERENTIS GmbH


Jasper Bhaumick Thorsten Fiedler
Executive Director / CIO Senior Manager Consulting

Tel. +49 (0) 0151 - 14 80 55 94 Tel. +49 (0) 172 566 98 64


eMail: jasper.bhaumick@atlas.de eMail: tfiedler@merentis.com

Vous aimerez peut-être aussi