Thursday, June 5, 2008

SAP standard components

SAP system landscape may contain according IT Scenarios and IT Practices various different scenarios as described in Master Guides.


  • SAP application components (SAP APO, SAP ERP, SAP R/3, SAP R/3 Enterprise,

SAP CRM, SAP SCM, SAP SRM, SAP SEM)

  • SAP components for industry solutions (IS) (SAP Banking, SAP Discrete Industries,

SAP High Tech, etc. – around 20 different IS)

KW, SAP MDM, SAP Exchange Infrastructure, and SAP Mobile Engine.

Since release 2004s of SAP NW there are used within installation and design of architecture so called (SW installable blocks) building blocks so called „usage types“* and “standalone engine” and “clients” e.g:

    • Application Server ABAP (AS ABAP) - [usage type]
    • Application Server Java (AS Java) - [usage type]
    • Development Infrastructure (DI) - [usage type]
    • Enterprise Portal (EP) - [usage type]
    • Process Integration (PI) - [usage type]
    • Gateway - [standalone engine]
    • Search and Classification (TREX) - [standalone engine]
    • SAP Content Server 6.30 - [standalone engine]
    • SAP GUI 6.40 - [client]
    • Mobile Infrastructure Client - [client]
    • SAP technological components (SAP Solution Manager, SAP Marketplace Connector)
    • SAP XApps (SAP xApps for Mobile Business, SAP XEM, SAP XPD, SAP XRPM)
    • SAP Solutions for Electronic Marketplaces (SAP MarketSet)
    • add-ons specific solutions for different countries(SAP HR-CEE, CCIS, C-CEE, HR-CIS)

  • Support components for different solutions (ABC Connector, BackWeb Infocenter, SAP

PLM Recipe Management, SAP Records Management, SAP Workforce Management)

  • SAP front-end components (SAP GUI, SAP ITS, SAP IGS)
  • Plug-ins (SAP Plug-Ins, SAP Solution Tools Plug-Ins)
  • Other components (SAP Kernel)


*usage type - An installed and correspondingly configured part of an SAP NW system that provides key capabilities for a system landscape.
- It specifies the intended purpose of a system.
- It is the result of the configuration of the underlying installed software units and the configuration of the underlying functional units.
Examples include business intelligence, process integration, and enterprise portal.

No comments: