Idea
Usage of SAP NetWeaver
(ABAP) as middleware server, complete web server, highest stability, infinite scalability, Load balancing, Additional application server, Extra SAP Netweaver server, unbeatable performance, no middleware slowing down integration, only (anyway) needed
posting are done directly, full ABAP functionality, complete programming language, SAP data structures and data directly available, All SAP techniques are directly applicable
Open standards (Web Service, XML, XSLT,...)
Opportunity for using other front-ends
Microsoft Office, MS Excel, MS Outlook
Web browser, Portals
Release-independent, real web
services instead of proprietary, hard
to maintain SAP RFC connections
SAP Inbound & SAP Outbound
Calling SAP from outside (Inbound)
SAP triggers calls and sends data (Outbound)
Central monitoring
Documentation
Configuration & development
Installation
Own authorisation object
Authorisation by service
Storing all transaction data
only header data for logging
original transaction data
archiving with own archiving object
SAP is finally open
Open standards usage
Technical superiority
(performance, stability)
Universal applicable,
flexible extensible
ideal also for SME
Functional range comparable with large,
expensive solutions from well-known vendors
future-proof
No expensive middleware
No expensive integration projects
No expensive release changes
Integration design predetermined
Automatic, central monitoring
Simple option to reduce license costs
MS Sharepoint integration
Portal integration
BI integrationen
Excel spreadsheet integration
Excel web service integration
SAP list distribution
SQL queries
packed into a web service, from MS Excel, from any other environment
IDOC/EDIFACT/ANSI... integration
Connecting third-party-systems
POS integration
Production systems
Billing systems
Connection JAVA applications
Integration of .NET applications
Metastorm BPM integration
xHTML forms with workflow
functionality
