Docstoc

ADM130_610_Col22 - BASIS

Document Sample
ADM130_610_Col22 - BASIS Powered By Docstoc
					ADM130 E-Commerce Administration




                                               ADM130



          ADM130
           E-Commerce Administration




           THE BEST-RUN E-BUSINESSES RUN SAP

    SAP AG© SAP AG 2002
           2002




System R/3, CRM, EBP
2002, Q2
50055596
  Copyright



       Copyright 2002 SAP AG. All rights reserved.
       No part of this publication may be reproduced or transmitted in
       any form or for any purpose without the express permission of
       SAP AG. The information contained herein may be changed
       without prior notice.




        SAP AG 2002




Notes on Trademarks:
  Some software products marketed by SAP AG and its distributors contain proprietary software
  components of other software vendors.
  Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint®, and SQL Server® are registered
  trademarks of Microsoft Corporation.
  IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®,
  AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.
  ORACLE® is a registered trademark of ORACLE Corporation.
  INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks
  of Informix Software Incorporated.
  UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
  HTML, DHTML, XML, and XHTML are trademarks or registered trademarks of W3C®, World
  Wide Web Consortium, Massachusetts Institute of Technology.
  JAVA® is a registered trademark of Sun Microsystems, Inc.
  JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for
  technology developed and implemented by Netscape.
  SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow,
  WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo, and
  mySAP.com are trademarks or registered trademarks of SAP AG in Germany and several other
  countries all over the world. All other products mentioned are trademarks or registered trademarks of
  their respective companies.
Duration, Target Group, Prerequisites

          Duration:
              Five days
          Target group:
              Persons responsible for regular operation of an SAP E-Commerce
              Lösungen: Internet Sales or Enterprise Buyer
              System Administrators
              E-Commerce Basis Consultants
              IT Manager
          Prerequisites:
              Essential:
                  SAPTEC (or SAP50 mySAP Basis Technology)
                  ADM100 (or BCtcc Technical Core Competence) - strictly
                  recommended!
              Recommended:
                 Detailed Knowledge in SAP System Administration, Database
                 Knowledge, Basic Knowledge E-Commerce Scenarios, Basic
   
                 Knowledge Windows NT
       SAP AG 2002
Course Objectives



                  At the conclusion of this course, you
                  will be able to:

                       Configure the SAP Systems and the
                       Middleware
                       Perform tasks within System Administration
                       Perform basic Monitoring of the Data Flow of
                       Aplication Objects
                       Perform Technical Monitoring of the System
                       Landscape with its Components




   SAP AG 2002
Course Contents



            Preface

 Unit 1     mySAP Technology             Unit 6   Role Management

 Unit 2     Configuring Internet Sales   Unit 7   Interface Monitoring

 Unit 3     Configuring EBUYER           Unit 8   System Monitoring

 Unit 4     System Administration        Unit 9   Backup Scenarios

 Unit 5     Software Logistics

                                         Appendix Installation Scenarios
                                                  Transaction Codes




    SAP AG 2002
Further Documentation



                  For additional information about
                  mySAP go to URL:
                     service.sap.com/e-commerce




   SAP AG 2002
  mySAP Technology


                      1. mySAP Technology              7. Interface Monitoring



                      2. Configuring Internet Sales    8. System Monitoring



                      3. Configuring EBUYER            9. Backup Scenarios


                                                       Appendix Installation Scenarios
                      4. System Administration
                                                                Transaction Codes


                      5. Software Logistics



                      6. Role Management


       SAP AG 2002




(C) SAP AG                                    ADM130                                     1-1
  mySAP Technology


                      Contents
                         mySAP Technology
                         Internet Transaction Server
                         J2EE Application Server
                         Business Connector
                         Plug-Ins



                      Objectives
                      At the end of this unit, you will be able to:
                         Describe the architecture of mySAP Role of the ITS
                         Describe the J2EE Application Server
                         Describe the Business Connector
                         Decribe the Benefits of Plug-Ins




       SAP AG 2002




(C) SAP AG                                       ADM130                       1-2
  mySAP Components


               mySAP Components
  mySAP ComponentsmySAP Components



                                                   mySAP Components Components
     mySAP Components



                                                               mySAP

                                                   Internet Transaction Server
                                mySAP Components




                                                   J2EE Appl. Server


                                                   Business Connector


                                                   Plug-In Technology




                    SAP AG 2002




(C) SAP AG                                                          ADM130       1-3
  What is mySAP?


                                                                               Only a fraction of the
                                                          R/3               integration possibilities
                            The Internet, or 'the
                                                                                    is shown here...
                            rest of the world'


       Other
      software                             Marketplace
                                                                                   Laptop or
                                                                                 PDA (handheld)

    New business partner                                                            Field staff
                                                         R/3:
                                                        FI/CO       R/3:
                                             BW                     SD
       Only                                                  R/3:
      require                                                HR
      browser
                                          CRM                                             R/3
                                                     Legacy     APO
                                                    software
                                                                                        Other
    Customer                                                                           software

        SAP AG 2002
                       TM
                                                Your company                        Business partner



  SAP offers customers a tailored, highly -integrated, and open software landscape.
    Tailored: SAP offers many different mySAP components that cover the full range of modern
    business functions.
    Highly -integrated: Data from a mySAP environment is consistent beyond system borders and can
    be called using various standard interfaces.
    Open: The interfaces used in the mySAP.com environment are either industry or technical
    standards (such as RosettaNet or XML) or SAP standard interfaces (for example, Business
    Application Programming Interfaces (BAPIs)). Using these interfaces, you can transfer data in
    many different ways (for example, http://www.rosettanet.org).

  Although only a few integration possibilities are illustrated in the graphic, the basic principle is clear:
  Use the available interfaces to not only link the applications within your company, but also to
  communicate directly with business partners, marketplaces, field sales representatives, and
  customers.




(C) SAP AG                                          ADM130                                                1-4
  Components with an SAP Basis




      SAP R/3 Business Applications (FI, HR, …)
      SAP Enterprise Buyer Professional (SAP EBP)
      SAP Customer Relationship Management (SAP CRM)
      SAP Business Warehouse (SAP BW)
      SAP Advanced Planner & Optimizer (SAP APO)
      SAP Knowledge Warehouse (SAP KW)
      SAP Strategic Enterprise Management (SAP SEM)
      SAP Corporate Financial Management (SAP CFM)




       SAP AG 2002




  All the listed components are based on an SAP Basis System.




(C) SAP AG                                   ADM130             1-5
  Common mySAP.com Technology


                                                                      Industry
              SEM      APO        EBP           Plug-Ins
                                                                      solution


                                                                               “classic R/3"

                                                  Central
                  BW            CRM            Applications               HR
                                              with/without HR


                              ABAP etc. (Cross-Application)



                               SAP Web Application Server
                             (formerly known as SAP BASIS)


                       A common basis for all mySAP.com products
       SAP AG 2002




  mySAP.com Technology (formally known as SAP Basis) forms the technical foundation for almost
  all of the current mySAP.com components. The abbreviations used above represent the following
  components:
     SEM: Strategic Enterprise Management
     APO: Advanced Planner and Optimizer
     EBP: Enterprise Buyer Professional
     BW: Business Information Warehouse
     CRM: Customer Relationship Management
     HR: Human Resources

  You can find more information about these products from the individual training courses for the
  components (see the Knowledge & Training section in the SAP Service Marketplace) and by using
  their names as aliases in the SAP Service Marketplace, such as http://service.sap.com/BW.




(C) SAP AG                                   ADM130                                             1-6
  Component SAP R/3

  SAP R/3 System consists of
  application functionality including:

                                                   Financials
                                                   (FI, CO, …)
                                                   Logistics
                                                   (MM, SD, PP, PM, …)
                                                   Human Resources
                                                   (HR)
     Financials
     Logistics
                                                   Industry Solutions:
     Human Resources
                                                      Some are included
                                                      in the standard software
                                                      Others are installed by
 Releases:                                            additional transports
 R/3 4.6C - Application 46C, Basis 4.6C               called add-ons
 R/3 Enterprise - Application 4.7, Web As 6.20

       SAP AG 2002




(C) SAP AG                                ADM130                                1-7
  Component SAP R/3 with IACs




                                                                Internet Application
   Web browser access                                           Components (IACs)
                                                                delivered with the
                           Web                                  Internet Transaction
                           Server
                                                                Server (ITS) extend
                                                                some of the SAP R/3
                                                                business functionality
                                                                to provide easier-to-use
                                                                access from a Web
                                                                browser

    Financials

    Logistics - SD                   IAC - Online Store

    Human Resources - HR             IAC - ESS




        SAP AG 2002




  All mySAP.com components can be accessed from a Web browser using the Internet Transaction
  Server (ITS).




(C) SAP AG                                   ADM130                                            1-8
  Component EBP


                                                          Enterprise Buyer
    SAP EBP                                               Professional (EBP)
                                                              Extends Logistics - MM
                                                              Provides intercompany
                                                              applications and technology
                                                              for business-to-business
                                                              procurement, including:
                                                                   Product catalog
                                                                   Shopping basket
                       SAP R/3                                     Workflow
                                                                   Administrative functions
                       Financials
                       Logistics - MM                         Includes document
                       Human Resources
                                                              interchange technology
                      Releases:
                                                              provided by SAP Business
                      EBP 3.0 - CRM 3.0,                      Connector for XML
                      Web As 6.10                             translation services
       SAP AG 2002




  The Enterprise Buyer Procurement (EBP) component enables procurement transactions to be
  conducted between companies.
  Component EBP can either be coupled to a backend SAP System or run as a standalone system.
  For further information, go to http://service.sap.com/EBP .




(C) SAP AG                                  ADM130                                             1-9
  Component CRM


                                                             Customer Relationship
    SAP CRM                                                  Management (CRM)
                                                                 Extends Logistics - SD
                                                                 Provides applications
                                                                 and technology to
        SAP R/3                                                  maintain customer
                                                                 relationships in sales
                                                                 and service
                                                                 Supports CRM
                                                                 scenarios including:
                        SAP R/3
                                                                       Mobile clients
                        Financials                                     Internet sales
                        Logistics - SD
                        Human Resources
                                                                       Call center
                      Releases:                                        solutions
                      CRM 3.0 - CRM 3.0,
                      Web As 6.10
       SAP AG 2002




  Component CRM consists of the CRM Middleware Server (SAP Basis System plus CRM
  functionality) and interface technology for mobile clients, Internet business, and so on.
  Optionally, component CRM includes components EBP, BW, and APO.




(C) SAP AG                                    ADM130                                          1-10
  Internet Transaction Server


                    Internet Transaction Server
  Internet Transaction ServerTransaction Server
     Internet Transaction Server


                                                                          mySAP Components


                                                                          Internet Transaction Server Server
                        Internet




                                                                                        Internet Transaction
                                            Internet Transaction Server




                                                                          J2EE Appl. Server


                                                                          Business Connector


                                                                          Plug-In Technology




                            SAP AG 2002




(C) SAP AG                                                                                ADM130               1-11
  ITS Software Components




                                                                       DIAG
   ISAPI
   NSAPI                            TCP/IP
                          WGate




                                                      AGate
   CGI
                                                                       RFC
                                    ITS


       SAP AG 2002




  The ITS consists of the WGate (W = Web) and the AGate (A = application). The WGate
  communicates with the HTTP server, and the AGate communicates with the R/3 application servers.
  Connecting to the HTTP server:
    - CGI - Common Gateway Interface: General interface for communication between the HTTP
       server and the executable program on the same computer
    - ISAPI - Internet Server API: Interface developed specifically for Microsoft's Internet
       Information Server for dynamic link libraries (DLL) on the same computer
    - NSAPI - Netscape Server API: Interface developed specifically for Netscape's Enterprise
       Server for DLLs on the same computer.
  Connecting WGate and AGate:
    - TCP/IP, or more precisely: HTTP - Hypertext Transport Protocol: HTTP is used here only
       for internal communication. The Web browser cannot connect directly to the AGate
  Connecting to the SAP R/3 System:
    - DIAG - Dynamic Information and Action Gateway (= SAP GUI protocol): To call R/3
       transactions. The R/3 System cannot distinguish between a normal SAP GUI user and the ITS.
       An R/3 application can make this distinction by calling the function module ITS_PING.
    - RFC - Remote Function Call: To call R/3 function modules




(C) SAP AG                                  ADM130                                           1-12
  Virtual ITS




                 ISAPI




                            WGate




                                             AGate
                 NSAPI                                DIAG
                                    TCP/IP
                      CGI
     HTTP
                                    ITS                RFC
                                                                 R/3
     server                         DEV                          DEV




                  ISAPI
                            WGate




                                             AGate
                  NSAPI                               DIAG
                                    TCP/IP

     HTTP
                      CGI
                                    ITS                RFC
                                                                 R/3
     server                         QAS                          QAS


       SAP AG 2002




  Several virtual ITS servers can operate independently from each other on one Windows server to
  minimize hardware requirements and response times.
  For Example, several (virtual) ITS instances may be required to separate test systems from
  development systems.




(C) SAP AG                                   ADM130                                                1-13
  ITS Admin Tool - A Special Virtual ITS




                                                                  ABC

                                            HTTP                  ITS                  DEV




                                                                  FGH

                                            HTTP                  ITS                  QAS

                 Browser


                                                                  ADM

                                            HTTP                  ITS
  URL to start the
  Admin Tool:
  http://.../scripts/wgate/admin/!
       SAP AG 2002




  Functions in the ITS Admin Tool
    Overview - Overview of all the virtual Internet Transaction Servers on one page
    - Hits, hits/sec, turn-around-time, sessions and workthreads
    <vITS> - Details of each virtual ITS
    - Control - Start and stop the ITS and Web servers
    - Performance - Detailed display
    - Configuration - Performance settings, service files, log functions, debugging, registry
    - Security - NT security (files) and communication (WGate to AGate, AGate to R/3)
    - Utilities - Flush logs and clear templates cache
    - View Templates
    - View Logs
    System View - Overview of NT server
    Administration - Admin tool user management




(C) SAP AG                                    ADM130                                            1-14
  Components of an ITS Service



  http://pc12/scripts/wgate/abcd/!




                                          WGate




                                                           AGate
                                                                     DIAG
                  HTTP             CGI            TCP/IP
                                                                      RFC
                                                                               R/3
      Web                HTTP                                               application
    browser              server                    ITS                        server




                                                                     HTML
                          MIME                     Service
                                                                   Business
                         objects                    files
                                                                   templates
       SAP AG 2002




  A service the Internet Transaction Server provides for Internet users consists of:
    - Administering logon information to the SAP R/3 System (name of system and user details)
    - Running a transaction in SAP R/3 System or calling a function module or report
    - Converting SAP R/3 data (screens or lists) to HTML pages
  When a service is started, an SAP GUI or RFC session is internally started:
    - The ITS assigns the HTTP requests for a service to the correct session
    - A user context corresponds to each session in the SAP R/3 System
    - A session ends when the service ends (by logoff or timeout in ITS)




(C) SAP AG                                   ADM130                                             1-15
  Parameters in Service Files




                      Selection of SAP R/3 System
                      Selection of SAP R/3 System

                      Logon to the SAP R/3 System
                      Logon to the SAP R/3 System
                             (implicit/explicit)
                              (implicit/explicit)

         EasyWebTransaction, ITS Flow Logic,
         EasyWebTransaction, ITS Flow Logic,
          WebRFC or ITS Administration Tool
          WebRFC or ITS Administration Tool

                        ITS-Specific Parameters
                         ITS-Specific Parameters


       SAP AG 2002




(C) SAP AG                         ADM130           1-16
  Service Parameters: Selection of SAP R/3 System



      Load balancing across
      the message server                                                       SAP R/3 System
                                                                                   “DEV”
      ~messageServer s01
      ~systemName    DEV                                            s01 (MS)
      ~loginGroup    SPACE                       AGate

                                                   ITS
      Direct selection of
      application server
                                                                    s02 (00)              DB

      ~appServer           s03
      ~systemNumber        00
                                                  AGate

      Example of using                              ITS             s03 (00)

      SAProuter
      ~routeString
      /H/gateway/S/3299/H/s03/S/3200

       SAP AG 2002




  As the AGate logs on like a normal GUI user, all the different options of the SAP GUI logon can be
  used.
  The SAProuter can also be used between the AGate and SAP R/3 System.
  The ITS automatically generates an error message if not all of the parameters contain values.




(C) SAP AG                                    ADM130                                             1-17
  EWT, ITS Flow Logic, WebRFC or ITS Admin Tool



                                                      SAP R/3
                                       System Help
                                                           SAP R/3
       WGate
                                DIAG         System Help

               TCP/IP           DIAG           Carrier name:
                                       100       Lufthansa
                                                                      EasyWeb
                                              200                    Transaction

                                                           R/3
                        AGate


    ITS
                                 RFC
                                             BAPIs and (any) other
                                                 RFC-enabled            ITS
                                RFC            function modules      Flow Logic
      Admin
        ITS

      Tool




                                 RFC                Special
                                               WebRFC-enabled         WebRFC
                                RFC
                                               function modules

       SAP AG 2002




(C) SAP AG                                       ADM130                            1-18
  Service Parameter: ~xGateway



     EasyWebTransaction          ~xGateway          sapdiag
     DIAG                        ~transaction       <tcode>
     ITS generates HTML


     ITS Flow Logic              ~xGateway          sapxginet
     RFC                         ~initialTemplate   <template>
     ITS generates HTML
     (no longer recommended)

     WebRFC                      ~xGateway          sapxgwfc
     RFC                         _function          <fmodule>
     R/3 generates HTML


     ITS Admin Tool              ~xGateway          sapxgadm
     Without link to SAP R/3
       SAP AG 2002




(C) SAP AG                     ADM130                            1-19
  Service Parameters: ITS-Specific


     Generation of the HTML pages
         ~theme          99                   Selection of templates
         ~URLmime        /sap/its/mimes       Path to MIME objects for URLs
         ~exitURL        /BC440/home.html     URL after service is completed
         ~runTimeMode    pm                   Selection of system templates


     Administration of logon data
         ~timeOut        5                    Max. time between two dialog steps
         ~cookies        1                    Data buffering of explicit logon
         ~userTimeOut    60                   Maximum duration of buffering


     Parameters for creating URL
         ~hostunsecure   s34                  Name of HTTP server
         ~portunsecure   1080                 Port for HTTP
         ~hostsecure     s34                  Name of HTTP-S server
         ~portsecure     443                  Port for HTTP-S


       SAP AG 2002




(C) SAP AG                           ADM130                                    1-20
  ITS Administration Monitoring


                                             Main
                                             Main
                             ITS Instance
      Overview                                           Admin                 System View
                               Specific


                                Control                  Control                  Process

                              Performance             Performance                 Memory

                             Configuration           Configuration              Disk Status

                                Security                Security

                                                                              Administration
                                Utilities                Utilities

                            View Templates           View Templates           Change Password


                               View Logs               View Logs                 User Mgt
       SAP AG 2002




  ITS administration allows you to monitor ITS instances individually or as a group.
     To monitor or perform administration tasks on an individual ITS instance, choose an instance from
     the list of defined instances.
     To monitor all instances together, use the overview function.
  When you set parameters in the global service file, they become the default values for the entire
  virtual ITS. If an individual service specifies its own value for a particular service parameter, this
  overrides the global value. If an individual service specifies no value for a particular service
  parameter, the value in the global service file applies.
  Choose the ITS instance you want to configure. Choose Configuration → Global Services.
  Choose the parameter and make your changes:
     Default SAP R/3 System - Specifies SAP R/3 system used when you start a service. You can
     specify either load balancing or a single application server.
     Default R/3 user - Specifies default user when an ITS service logs on to the R/3 System. You can
     define client, user, and password.
     All settings - Lists all global service parameters.
  ITS administration automatically updates values in the global service file (global.srvc). You do not
  have to restart the virtual ITS to activate your changes.




(C) SAP AG                                     ADM130                                              1-21
  J2EE Application Server


                  J2EE Application Server
  J2EE Application Server Application Server
     J2EE Application Server


                                                                   mySAP Components


                                                                   Internet Transaction Server
                      J2EE

                                         J2EE Application Server




                                                                   J2EE Application Server
                                                                                 J2EE Application Server
                                                                   Business Connector


                                                                   Plug-In Technology




                          SAP AG 2002




(C) SAP AG                                                                          ADM130                 1-22
  What is Java?




      Language                      APIs                     Editions: J2SE, J2EE
          Simple                        Networking               Java 2 Standard
                                                                 Edition (J2SE)
          Object Oriented               Distributed
                                        Computing (RMI)          Java 2 Enterprise
          Secure
                                                                 Edition (J2EE)
                                        Transaction
          Architecture
                                        handling (JTA)
          Neutral
                                        Security (JAAS)
          Interpreted
                                        Naming and
          Multithreaded
                                        Directory (JNDI)
          Dynamic

       SAP AG 2002




  Simple: Java is a simple language. Although Java is superficially similar to C and C++, Java gained
  its simplicity from the systematic removal of features from C and C++. These features include
  multiple inheritances, go to statements and pointers. Java completely removes the memory
  management load from the programmer, since Java has automatic garbage collection.
  Architecture Neutral, Interpreted: The Java Compiler generates bytecodes, an architecture neutral
  intermediate format. The Java Virtual Machine (JVM) interprets Java byte code. There are many
  implementations of the JVM on different hardware and operating system platforms.
  Multithreaded: Java has built-in support for threads. This enables programs to respond to many
  things happening simultaneously (for example an applet displaying animation and sound, while
  scrolling and downloading).
  Dynamic: Classes are linked-in as required and can be downloaded at runtime from across networks
  (for example, transport and run applets over the Internet).
  Networking: Java has an extensive library of routines for copying easily with TCP/IP protocols like
  HTTP and FTP. This makes creating network connections much easier than in C or C++. Java
  applications can open and access objects across the net via URLs with the same ease as when
  accessing a local file system.
  Distributed Computing: Distributed computing is possible through Remote Method Invocation
  (RMI). RMI calla methods of objects located on remote servers. The location is transparent to the
  client.
  Services and APIs are organized in three editions: J2SE (Java 2 Standard Edition), J2EE (Java 2
  Enterprise Edition), and J2ME (Java 2 Micro Edition).




(C) SAP AG                                    ADM130                                             1-23
  The Concept


                               Compiler &           Executable
                                 Linker                File

                  Sourcecode                                                           PC
   Compiled
   Programs                                                                          MAC
                                                                                      Unix
                                                                 Interpreter
                        Sourcecode                                                     PC
   Interpreted
   Programs                                                                           MAC
                                                                                      Unix
                                      Compiler

                      Sourcecode                                      VM               PC
   Java                                           Byte-
   Programs                                       code                VM              MAC
                         .java File              .class File          VM              Unix

       SAP AG 2002




  Compiled Programs (C, C++, Pascal)
    The compiler checks the source code for syntax errors. A code is generated that can be executed
    on a specific platform
    + very fast, as only one compilation is necessary
    - Platform dependent

  Interpreted programs
    The interpreter reads the source code at the execution time of the program and generates
    executable statements for the recent platform
    + faster development
    - Slower execution
    - Syntax errors appear at runtime

  Java: Bytecode and virtual machines
    The source code is compiled into Java Bytecode, an intermediate format. This Bytecode can be
    executed afterwards by a Java virtual machine on any operating system.
    + platform independent
    - Slower execution




(C) SAP AG                                       ADM130                                          1-24
  Architecture for Distributed Business
  Applications (1)




      Web Browser
      Web Browser                          Application Server
                                           Application Server                          Databases
                                                                                       Databases




          Clients                         Business Services                              Data
        SAP AG 2002




  The architecture for distributed business applications is usually divided into several tiers. Each tier
  has certain tasks.
  The presentation tier contains the graphical user interface. In many cases, the presentation tier is
  implemented as a web browser.
  The business logic tier contains most of the business logic. Often, this tier is divided into two tiers:
  one for the actual business logic and one for the presentation logic.
  The data tier typically contains one or more databases that store the application data.




(C) SAP AG                                       ADM130                                                 1-25
  Architecture for Distributed Business
  Applications (2)

                      Presentation Server
                      Presentation Server   Application Server
                                            Application Server



    Web Browser
    Web Browser                                                  Databases
                                                                 Databases




        Clients                 Business Services                 Data
       SAP AG 2002




(C) SAP AG                            ADM130                                 1-26
  R/3 Architecture – Technology View

  Presentation
      Tier

                                     SAP GUI
                                     SAP GUI         SAP GUI
                                                     SAP GUI

  Application
                              Application
     Tier                                                        Gateway
                                Server



                                                    Dispatcher

                                         Work-         Work-         Work-
                                        process       process       process




  Database
    Tier                                 Database Management System




       SAP AG 2002




  The architecture of an R/3 System is an example of a three-tier architecture. On the database tier,
  there is one database system. The application tier is made up of several application servers and one
  message server. There are several SAP GUIs on the presentation tier.
  The applications based on a R/3 Basis system can have various structures. The technological basis
  does not enforce a certain type of separation of concerns.




(C) SAP AG                                        ADM130                                            1-27
  J2EE Application Components
                                                                 J2EE Server
                                 Web Container

       Browser                                            EJB Container
         Pure
         Pure                            JSP
                                         JSP
         HTML
         HTML

         Java
          Java                        Servlets
                                      Servlets
         Applet
         Applet

                                                                  EJB
                                                                  EJB
       Desktop
        Java
        Java
      Application
      Application
                                                  RMI
    Other Device        http

        Java
        Java
      Application
      Application


                                                                                               Enterprise
    Client-Side                    Server-Side             Server-Side
                                                                                              Information
   Presentation                    Presentation           Business Logic
                                                                                   JDBC         System
        SAP AG 2002




  The Java 2 Platform, Enterprise Edition (J2EE) is a specification of an architecture for distributed business
  applications based on Java Technology. The J2EE architecture consists of three tiers: the client tier, the middle
  tier, and the backend tier. On the backend tier, there may be file systems, database servers, or existing
  enterprise information systems. On the client tier, there can be several clients, such as Web browsers, Java
  applications, and hand held devices. The clients handle the user interface. On the middle tier, there is one
  middle tier server (J2EE server). The middle tier server plays the central role in the three-tier architecture. It
  handles requests from clients, contains and executes the business logic of the applications, accesses data from
  the existing systems in the backend tier, and returns the results to the clients. The business logic is
  implemented as Enterprise JavaBeans (EJB) components (also referred to as enterprise beans). The enterprise
  beans run in an EJB container, which is part of the J2EE server. The communication between the J2EE server
  and the J2EE clients is primarily based on Web standards, namely HTTP, HTML, and XML. The J2EE server
  may use JavaServer Pages (JSP) and Java servlets to generate HTML pages or XML data. JSP pages and
  servlets run in a web container, which is part of the J2EE Server. Within the HTML pages that are sent to the
  Web browser, Java appletsmay be embedded. These applets are downloaded and executed by the browser.
  All J2EE products are required to support the J2EE specification. An applications written for the J2EE
  platform will run on any J2EE-compatible server. The J2EE SDK is a reference implementation of a J2EE
  server provided by Sun Microsystems. This J2EE server provides an operational definition of the J2EE
  platform and can be used by developers to verify the portability of an application.
  There are three types of J2EE application components: applets, web components (servlets and JSP pages), and
  Enterprise Java Beans (EJBs). Enterprise beans and web components are deployed, managed, and executed on
  a J2EE Server. HTML pages and applets are also deployed and managed on a J2EE server, but are loaded and
  executed on a client machine. There may also be standalone Java applications that communicate with the J2EE
  server or directly with the backend tier.




(C) SAP AG                                           ADM130                                                     1-28
  Applets



                                  Applet = „small application“
      Browser
                                      Downloaded from server by browser
        Pure
        Pure
        HTML
        HTML                          Running within browser
                                      Displaying its UI within an HTML page
        Java
         Java
        Applet
        Applet                    Facts
                                      Mostly graphics-based components for
                                      user interaction
                                      Applets are typically small in size
                                      because they are loaded over the
                                      network
                                  Examples
                                      Bidding component for online
                                      auctioning
                                      Administration tools
    Client-Side
   Presentation
       SAP AG 2002




  An applet is a Java class that can be embedded within an HTML page and is downloaded and
  executed by a web browser. It differs from an application in the way it is executed. An application
  can be started directly, which means that its main method is executed. An applet runs in the
  environment of a web browser, so it is not started directly by typing a command. There must be an
  HTML file that tells the browser what to load and how to run it. During the lifecycle of an applet, the
  browser calls certain methods of the applet. For example, the browser calls the paint method of the
  applet´s class to display the applet.
  Information on applets can be found at http://java.sun.com/docs/books/tutorial/applet/.




(C) SAP AG                                     ADM130                                               1-29
  Applet Example

  Hello World Example


      HTML File - displayed in the Browser
         <html>
         <applet code=HelloWorld.class width=100 heigth=100>
         </applet>
         </html>



      Applet's class - Implementation on the Server
         import java.awt.*;
         import java.applet.*;


         public class HelloWorld extends Applet {


             public void paint(Graphics g){
                 g.drawString("Hello World!", 25, 25);
             }
         }

       SAP AG 2002




  The applet´s class must extend the class java.applet.Applet, which is a subclass of the class
  java.awt.Panel.
  Applets are graphical in nature. The browser displays the applet as part of an HTML page. The
  browser calls the paint method of the applet´s class to display the applet. The browser calls the paint
  method whenever the applet needs refreshing. The paint method requires an argument, which is an
  instance of the class java.awt.Graphics. The argument is always the graphics context of the panel
  that makes up the applet.




(C) SAP AG                                      ADM130                                               1-30
  Java Server Pages



                                                            JavaServer Pages (JSP)
       Web Container                                        combine the power of
                                                            HTML/XML and Java to create
                             EJB Container
                                                            dynamic web content (HTML
             JSP
             JSP                                            and XML pages)
                                                            Under the hood, JSP pages are
           Servlets
           Servlets                                         converted into servlets.
                                                            JSP technology separates the
                                    EJB
                                    EJB                     user interface from content
                                                            generation, so that the layout
                                                            can be maintained by web
                                                            designers
                                                            The dynamic content within a
                                                            JSP page is provided by
                                                            scripting elements, actions and,
       Server-Side          Server-Side                     custom tags, as usually used by
       Presentation        Business Logic                   HTML
       SAP AG 2002




  A JSP page is a text-based document that describes how to process a HTTP request to create a HTTP
  response. A JSP page consists of fixed template data, intermixed with directives, actions, scripting
  elements and possibly custom tags. The dynamic content is provided by the scripting elements, the
  actions, and custom tags.
  JSP pages are translated into servlets. The semantic model underlying JSP pages is that of a servlet.
  A JSP page describes how to create a response object from a request object, possibly creating and /
  or using in the process some other objects, typically JavaBeans.
  Information on Java Server Pages can be found at:
     http://java.sun.com/products/jsp/
     http://java.sun.com/products/jsp/docs.html




(C) SAP AG                                     ADM130                                              1-31
  JSP Examples: Scriptlets



      Java code can be inserted directly in HTML code




       SAP AG 2002




  This diagram shows a simple JSP page which consists of HTML code with a scriptlet inserted. out is
  one of the implicit objects that are always available for use within scriptlets and expressions, without
  being declared first. out is an object that writes into the output stream.
  Scriptlets are always placed within <% and %> characters.




(C) SAP AG                                      ADM130                                                1-32
  Java Servlets



                                                              Servlets are Java classes
         Web Container                                        which functionally enhance
                                                              web servers. Web clients can
                               EJB Container
                                                              address servlets via an URL.
                JSP
                JSP                                           Servlets are executed by a
                                                              servlet (web) container within
              Servlets
              Servlets
                                                              a web server.
                                                              Servlets interact with web
                                       EJB
                                       EJB                    clients via the HTTP/HTTPS
                                                              request response paradigm.
                                                              Servlets can be used to
                                                              dynamically generate HTML
                                                              pages .



         Server-Side           Server-Side
         Presentation         Business Logic
       SAP AG 2002




  Servlets can be used to control the processing flow in a web application
  Servlets can access resources including Enterprise JavaBeans, Company ERP systems
  and Databases
  Servlets run within servlet containers associated with the web server
        A container provides the network services over which HTTP requests and responses are sent, it
        decodes requests, and formats responses
        It provides lifecycle management and resource pooling
        It implements session tracking functionality based on cookies and URL rewriting
  For example: a client invokes a servlet by submitting an HTTP request to the web server. This
  request is passed on to the servlet container. The servlet container invokes the servlet, passing a
  request object. The servlet extracts the submitted information from the request object (identity of the
  remote user, HTML form parameters and so on), performs the operations it was programmed for
  (for example, posting an order), and finally returns a response object.




(C) SAP AG                                      ADM130                                               1-33
  Java Servlets

  Hello World Example




       SAP AG 2002




  Typically, the class javax.servlet.HttpServlet is used as super class. The most important methods are
  the doGet and doPost method of that class. These methods must be implemented to handle HTTP
  GET requests and HTTP POST requests, respectively.
  The doGet and doPost method take two arguments: one represents the HTTP request and the other
  represents the HTTP response.
  In the example, the servlet generates a HTTP response that consists of a dynamically generated
  HTML page. The HTML page is generated by several println statements.
  You can implement a division of labor between components by forwarding the request to another
  servlet or JSP when the current servlet has finished processing. You can use the forward() method of
  the javax.servlet.RequestDispatcher interface for that purpose. More information on request
  dispatching can be found at http://java.sun.com/docs/books/tutorial/servlets/communication/request-
  dispatcher.html.




(C) SAP AG                                     ADM130                                              1-34
  Java Servlets Comparison



      Servlets are just like CGI programs or other server extensions
      Servlets advantages
           Servlets are platform and server independent
           They place a comparatively small load on server resources
           They can be loaded dynamically by a web server
           They can access all Java functionality




       SAP AG 2002




  Servlets are assumed to replace Common Gateway Interface (CGI) programs and proprietary server
  extensions such as the Netscape Server API (NSAPI) or Microsoft´s ISAPI. They do not require
  creation of a new process for each request. Multiple servlets can run simultaneously within the server
  process.




(C) SAP AG                                     ADM130                                              1-35
  Enterprise Java Beans


                                                       Enterprise Beans
                                                           An enterprise bean is a component
       Web Container                                       that implements a business task
                             EJB Container                 (for example availability check) or
                                                           a business entity (for example
             JSP
             JSP                                           purchase order).
                                Session Bean
                                Session Bean           EJB Container
           Servlets
           Servlets
                                                           Each enterprise bean runs in an
                                                           EJB container.
                                                           The container can use services, for
                                 Entity Bean
                                 Entity Bean               example:
                                                                Transaction management
                                                                Database connection pooling
                                                                Security
       Server-Side          Server-Side                         Persistency
       Presentation        Business Logic                       Remote access
       SAP AG 2002




  The Enterprise JavaBeans architecture is an architecture for component-based distributed business
  applications. An Enterprise JavaBean component (Enterprise Bean) is a component that implements
  a business task or a business entity. Each entity bean runs in an EJB container.
  Enterprise bean developers usually do not have to concentrate on transaction and state management
  details, DB connections, security, persistency, and other minor programming. The bean developer
  relies on the EJB container, which provides these services. The bean developer can concentrate on
  the business logic.
  Enterprise beans execute within an EJB container, which in turn executes within an EJB server. Any
  server that can host an EJB container and provide it with the necessary services can be an EJB
  server.
  The EJB architecture facilitates division of labor between experts in the different involved areas of
  expertise by defining six roles in the development and deployment life cycle (for Example, EJB
  provider, deployer, EJB container provider and so on).
  An enterprise bean is a body of code that contains fields and methods to implement modules of
  business logic. You can think of an enterprise bean as a building block that is used alone or with
  other enterprise beans to execute business logic on the J2EE server. There are three kinds of
  enterprise beans: session beans, entity beans, and message-driven beans.




(C) SAP AG                                     ADM130                                              1-36
  J2EE Container and Standard Services

                                                             Containers provide runtime support
                                                             for the application components
        Web Container
                                                                  Provide APIs for application
                                EJB Container                     components to access standard
                                                                  services
                JSP
                JSP
                                                                  A container for each application
                                   Session Bean
                                   Session Bean                   component type
             Servlets
             Servlets
                                                             Standard Services include:
                                                                  HTTP, HTTPS

                                    Entity Bean
                                                                  RMI-IIOP
                                    Entity Bean
                                                                  JDBC
                                                                  Java Naming and Directory
                                                                  Interface (JNDI)

        Server-Side            Server-Side                        Java Transaction API (JTA)
        Presentation          Business Logic                      Java Message Service (JMS)

                                                      JDBC        Java API for XML Processing
 http
         SAP AG 2002                                             (JAXP)



  Each application component is executed in a container. The container provides APIs for the application
  components to access standard services.
  Remote Method Invocation (RMI) enables you to create distributed applications by invoking methods on
  remote Java objects. Remote means that the calling object and the called object are running in different JVMs,
  possibly on different hosts. The location of the remote object is transparent to the client.
  JDBC API: Java Interface to SQL databases is independent of any particular DBMS. This can be used to open
  connections to a particular database, execute SQL statements or process results of database queries.
  A directory-enabled application is an application that uses a naming or directory service. Directory-enabled
  Java applications and applets, like any other program running on the network, can use the directory to store and
  retrieve attributes of directory objects. For example, a Java mail client program can use the directory as an
  address book for retrieving the addresses of mail recipients. A Java mail transfer agent program can use it to
  retrieve mail routing information. A Java calendar program can use it to retrieve user preference settings.
  A web component can demarcate transactions using the JTA UserTransaction interface. A web component may
  only start a transaction in its service method. A transaction that is started by a servlet or JSP page must be
  completed before the service method returns. That is, transactions may not span web requests from a client.
  There are two kinds of transaction demarcation for EJBs: container-managed transaction demarcation and
  bean-managed transaction demarcation. For each EJB, the deployment descriptor contains the information on
  which kind of transaction demarcation has been chosen.
  JMS provides a common way for Java language programs to access messaging systems. Products that
  implement JMS supply a provider that implements the JMS interfaces.
  The Java API for XML Parsing (JAXP) provides basic functionality for reading, manipulating, and generating
  XML documents using DOM, SAX, and XSLT.




(C) SAP AG                                         ADM130                                                    1-37
  Web Applications




                                      Utility
             Servlet
                                      Class

          JSP Page                 Static
                                 Document

                                                                 Configuration of the Java
             Deployment Descriptor                              Application, to be maintained
                                                                    by the administrator


                       WAR File



       SAP AG 2002




  A web application may consist of:
    Servlets
    Java Server Pages
    Utility Classes (incl. Java Beans)
    Static Documents (HTML pages, style sheets, images, sounds, etc.)
    One XML Deployment Descriptor web.xml (contains configuration and deployment information)
  A web application can be packaged into a WAR (web archive) file.
    A WAR file is a special JAR file that contains a web application
    Extension .war
  A WAR file can be deployed into a J2EE server.
  The structure of web applications is described in the Java Servlet Specification.
  The deployment descriptor is an XML file that contains configuration and deployment information
  for the web application contained in the WAR file. For example, it contains
    Information about the servlet names and its class files
    Mappings between servlets and URL pattern
    Security constraints
    Declaration of external dependencies (e.g. declaration of references to enterprise beans)
    Declaration of JSP tag libraries




(C) SAP AG                                  ADM130                                            1-38
  The Most Famous J2EE Servers



  J2EE Servers
           SAP J2EE Engine
           Weblogic (BEA)
           Websphere (IBM)
           Iplanet (Netscape/Sun)
           JRun (Allaire)
           Oracle 9 iAS (Oracle)
           Inprise (Inprise/Borland)
           JBOSS
           ….
  JSP/Servlet Engine (Web Container)
           Tomcat (Apache Foundation, Open Source)


       SAP AG 2002




  There are over 30 Java Web Application Servers on the market. The Java application servers differ
  in:
     - Version (1.1 or 2.0) of the J2EE specification
     - How completely they support the J2EE specification
     - Whether they have passed the Sun J2EE Compatibility Test Suite
  Certified OS Platforms for the SAP J2EE Engine are:
     - Windows NT 4.0
     - Windows 2000
     - Sun Solaris 8
     - Linux RedHat 6.2
     - The server works fine on any other platform with an appropriate Java Environment, although it
       is not tested
  System Requirements for the SAP J2EE Engine
     Minimal hardware requirements:
     - 64 MB of RAM
     - 45 MB free hard disk space
     Minimal software requirements:
     - J2SE 1.3 (JDK 1.3) or higher
     Other requirements
     - An IP address (static address or assigned dynamically)
     - It is not necessary to uninstall previous versions of SAP J2EE Engine




(C) SAP AG                                    ADM130                                             1-39
  SAP J2EE Engine Architecture:
  Dispatcher and Server

                   Clients                             SAP J2EE Engine J2EE server
                                                       consists of 2 components:
                                                        Dispatcher
  Dispatcher                                                Handles all incoming requests
                           Load
                           Load
        Receiver
        Receiver                                            Load balancing
                         Balancing
                         Balancing
                                                        Server
         Parser
         Parser                                             J2EE functionality


                                                       Both contain:
     Server                                                 Managers
                                                            (thread, memory, ...)
                   Services
                   Services
                                                            Services
                                                                 Core (log, deploy, ...)
                                                                 Optional (http, ejb, ...)
                   Manager
                   Manager




       SAP AG 2002




  Dispatcher Node:
  The main function of a dispatcher node is to receive requests from clients and distribute them to the
  server nodes in the cluster. On the dispatcher nodes run services providing for the communication
  between the nodes in the cluster as well as for the communication between the client and the
  dispatcher. Each dispatcher node has connection to each server node in the cluster. The introduction
  of dispatcher nodes in EnterpriseBeans Server cluster is aimed at reducing response time and
  providing for load balancing.
  Server nodes:
  The main function of server nodes is to process client requests, which are then returned to the
  dispatcher node. Each server node has connection to all other server and dispatcher nodes in the
  cluster. This connection however is transparent to the client, which has no direct connection to the
  server nodes in the cluster, but communicates with the dispatchers.
  Managers:
  These modules facilitate the management of the Java virtual machine e.g. thread management,
  memory management etc. Generally they are not distributed in the cluster. Each node has its own
  managers.
  Core Services:
  These modules contain the basic functionality of EnterpriseBeans Server 4.0. They are distributed in
  the cluster. Some of them run only on server or only on dispatcher nodes.




(C) SAP AG                                     ADM130                                              1-40
  SAP J2EE Engine Standalone Installation

                                                                    Visual
                 Client       Client         Client
                                                                 Administrator


     Machine 1


           Dispatcher1



             Server1


                                                Java Virtual Machine (java.exe)




  Standalone installation runs in a single Java virtual machine, containing
  dispatcher and server
        Higher performance for small number of requests (no TCP socket
        communication)
        Less scalability than cluster installation

       SAP AG 2002




  As alternative to cluster installation, SAP J2EE Engine supports standalone installation.
  In this scenario, one dispatcher node and one server node run in a single Java VM. Additional nodes
  cannot be added.
  Advantages of standalone over cluster:
    Smaller memory footprint: Only a single Java VM is running (as opposed to at least 2)
    Easier administration: Start/stop in a single step
    Fast dispatcher-server communication: No inter-process communication is required
  Disadvantages of standalone:
    Scalability and availability impact:
     - Server application problem can kill the entire server
     - No way to bypass resource limitations of a single VM




(C) SAP AG                                    ADM130                                              1-41
  SAP J2EE Engine Cluster Installation (Example)
  SAP J2EE Engine
        Cluster                                                               Visual
                          Client         Client             Client
                                                                           Administrator


             Machine 1                      Machine 2

                      Dispatcher1                     Dispatcher2




               Server1         Server2            Server3        Server4




                 Java Virtual Machine (java.exe)

    SAP J2EE Engine Cluster = group of independent nodes, managed as independent
    system
    Cluster Nodes can have one of 2 different types of nodes:
                  Dispatcher (communication, load balancing)
                  Server (J2EE functionality)
       SAP AG 2002




  An SAP J2EE Engine cluster consists of 1..n dispatcher nodes and 1..m server nodes. At least one
  server node and one dispatcher node must be present. The total number of cluster nodes (n+m) is
  limited to 64.
  Each cluster node (= cluster element) is identified by a unique ID (cluster element ID).
  Each cluster element runs in a separate Java VM (such as java.exe) and can be placed on a separate
  machine.
  Dispatchers receive incoming client requests (HTTP, RMI, ...) from, for example, browsers and
  client applications and delegate them to the appropriate server node. All client communication is
  done via dispatchers.
  Server nodes host servlets, JSPs, EJBs, and provide the actual J2EE functionality.




(C) SAP AG                                         ADM130                                         1-42
  SAP Java Connector (JCo)



                                      JAVA Application

                                        JCO Java API

                                     Middleware Interface

                      SOAP Middleware                   RFC Middleware

                                                             JNI Layer

                                                            RFC Library
                              HTTP

                                                                     RFC

                         HTTP Port                             RFC

                                        SAP System


       SAP AG 2002




(C) SAP AG                                     ADM130                      1-43
  Java Technology Stack and mySAP Components

                                        Java is used for Webifying

   Java                                   Business                     CRM         Enterprise
                                                          EBP
                               IPC                                     Internet
   Applications                           Connector      Catalog                   Portal 5.0
                                                                       Sales 3.0



            SAP Java Basis


              EJB                                     EJB
     J2EE




              Servlet/JSP



              Java VM



              OS


       SAP AG 2002




  Internet Sales does not use Enterprise Java Beans, as the Business Logic is implemented in the CRM
  System by BAPIs. Internet Sales does use some Java Beans as Java Classes (for example, that are
  used for the structure of orders).
  Current Java products shipped as Java applications:
    IPC
    Business Connector
  These applications do not use J2EE components such as EJB, JSP, or servlets.
  Also, SAP plans to integrate SAP Web Application Server and SAP J2EE Engine.




(C) SAP AG                                   ADM130                                             1-44
  Summary: Multi-Tier C/S Architecture and Java
 Presentation                          Presentation Logic                            Application Logic
 Database
                                                       SAP GUI for HTML       DIAG
                                                                                             Transactions
                                                                                                              ABAP
                                                                  HTML                       Screens
                                                     EWT
                                                           HTML Business

                                       ITS                     HTML
                                                                              RFC
                                                     ITS                                      Function
                                                                                                              ABAP
                                                     Flow HTML Business                       module
                               NSAPI
             HTTP                                    Logic                            SAP
                               ISAPI                        Flow Logic
                                                                                      Application Server
                       Web     CGI
                      Server
                                                Busi-             HTML                              ABAP
                                                ness              ABAP
                               HTTP SAP Web Server
    Web                             Application Pages           Java Script
  Browser                           Server


                               HTTP                               HTML                         Function
                                                                              RFC                             ABAP
                                                     JSP,                                      module
                                       JSP                         Java               SAP
                                                     Servlets
                                       Server                                         Application Server


                                                     Java         HTML                 Enterprise           Java
                               HTTP                  Server
                                       Java          Pages,        Java                Java Beans
                                       Application   Servlets
       SAP AG 2002                    Server




  A Java servlet is a server-side program that services HTTP requests and returns results as HTTP
  responses.
  A Java Server Page (JSP) contains HTML and Java code. When a user requests a JSP file, the JSP
  server first invokes a corresponding servlet. If the servlet does not already exist, the server generates
  one. The servlet output is then returned to the Web browser.
  A Java Application Server can house presentation logic (JSP and servlet) and application logic
  (Enterprise Java Beans).
  Java Connector (JCo) supports Java – ABAP communication.




(C) SAP AG                                              ADM130                                                       1-45
  Business Connector


                 Business Connector
  Business ConnectorBusiness Connector
     Business Connector


                                                        mySAP Components


                                                        Internet Transaction Server
                                   Business Connector




                                                        J2EE Appl. Server


                                                        Business Connector Connector
                                                                      Business

                                                        Plug-In Technology




                       SAP AG 2002




(C) SAP AG                                                               ADM130        1-46
  What is the SAP Business Connector?




                                           SAP
                                           SAP
                                          System
                                          System


                                              SAP
     SAP                               Business Connector
                 XML
     BC
                                                                    HTML
    SAP                                                                      Web-
                                                                              Web-
    SAP                                 Internet/HTTP
   System                                                                   browser
                                                                            browser
   System
                             XML                       HTML/
                       XML                              XML
                       Interface           XML                    Web
                                                                  Web
                                                                Content
                                                                Content
                      Non SAP
                      Non SAP                  Web
                                               Web              Server
                                                                 Server
                       System
                       System                 Appli-
                                              Appli-
                                             cations
                                             cations


       SAP AG 2002




  The SAP Business Connector is a basis technology that supports the development of application
  scenarios for Electronic Commerce.
  The SAP Business Connector represents an open bi-directional interface to business partners in the
  Internet (R/3 to R/3, R/3 to non-R/3).
  The SAP Business Connector allows synchronous and asynchronous communication via the
  exchange of SAP-defined XML documents.
  Generic interface for all message types:
    The Business Connector can invoke any RFC enabled function module.
    Any function module can call the Business Connector.
    The Business Connector supports all IDoc message types.
  Release independence:
    The Business Connector supports all SAP R/3 System kernel releases down to 3.1H.
    R/3 Systems with different releases can be connected without additional development effort on
    application level.
  Plattform independence:
    The Business Connector implementation is 99% JAVA.




(C) SAP AG                                    ADM130                                              1-47
  System Integration Technologies between SAP
  Systems


         SAP                                  SAP                                 SAP
         System             sRFC              System                              System
                            aRFC
                            tRFC
                            qRFC

                                                 RFC              BC HTTP BC RFC




                                                                   BC HTTP BC
                             Idoc                          Idoc
                            ALE                            ALE




                         Batch Input
                       Call Transaction
                         Direct Input



       SAP AG 2002




  RFC is available for SAP R/3 Systems as of Release 2.1A. For the R/2 System, RFC is available as
  of Release 5.0D with limitations regarding error handling and data volume. These limitations have
  been eliminated with Release 5.0H. SAP plans to implement these corrections from version 5.0H on
  all releases as of 5.0D.
  There are four types of RFCs:
     Synchronous RFC: sRFC
     Asynchronous RFC: aRFC
     Transactional RFC: tRFC
     Queued RFC: qRFC




(C) SAP AG                                   ADM130                                             1-48
  System Integration Technologies: SAP to External
  systems
  External System                                                                           External System
                                                    SAP
      (Client)                                                                                  (Server)
                                                                                    sRFC
                      sRFC                                                          aRFC
   RFCLIB             tRFC                                                          tRFC
                      qRFC                                                          qRFC




                                                                                     Converter
                       Converter




                                                                                       ALE
                         ALE
                                         Idoc                             Idoc
                                                                 ALE      RFC
                                          RFC ALE




                                                                                     Subsystem
                       Subsystem




                                                                                        EDI
                          EDI




                                         Idoc                             Idoc
                                                  ALE            ALE
                                          FTP                             FTP

       XML            HTTP                 RFC                      RFC   BC                HTTP   XML




                                                                                 DCOM CC
                       DCOM CC




      COM                                                                                          COM




                                                                                   MTS
                         MTS




            DCOM                            RFC                    RFC                     DCOM
     Client                                                                                        Client


                                   Batch Input                   Export
                              Call Transaction
       SAP AG 2002                Direct Input




  The Business Connector is not shown in this diagram, but is also used between SAP Systems and
  external systems to route RFC communication over the Internet.




(C) SAP AG                                              ADM130                                              1-49
  Business Connector Architecture


                                  Internet
                                                            XML/HTML through
                                                            HTTP(S)


                           XML Coder/Decoder

                           Flow    (Mapping , Routing )

                          RFC Coder/Decoder
                                                            RFC
                                                            tRFC



                                 IDoc             BAPI
                                                         SAP R/3    SAP R/3



         SAP AG 2002




  SAP Business Connector plays two roles:
    It acts as an RFC-Client for calls to an SAP system. These calls may originate from a browser,
    another SAP BC, or a third-party product.
    It acts as an RFC-Server for outbound calls from an SAP System. It makes information and
    services of the Internet available for applications inside SAP Systems.
  On the client side, the Business Connector converts RFC calls into XML documents and transfers
  them over the Internet/Intranet using the HTTP(S) protocol.
  On the server side, the Business Connector converts XML documents into RFC calls.
  The communication between SAP BC and an SAP system itself is always synchronous. That means
  that an outgoing tRFC call from an SAP system is processed immediately in SAP BC.




(C) SAP AG                                   ADM130                                            1-50
  Static routing: SAP to SAP communication



                      T20                       T21




              RFC listener                    SAP server


             inbound map


             remote server                   outbound map

       SAP AG 2002




(C) SAP AG                   ADM130                         1-51
  Creating Outbound Maps




                                                                        T21
                                                                       BAPI_1

                                     outbound map (=service)
                                     service name       bookinglist
         Internet                    interface          BC635_00
                                     SAP system         T21
                                     function module    BAPI_1




       SAP AG 2002




  An Outbound Map:
    Can be generated for a specific function module and a specific SAP System
    Is a service which can be invoked remotely
  To create an Outbound Map make an RFC lookup of the function you want to call from the system
  where you want to call it.
  Create a map of type ‘SAP BC SAP’ and save it.




(C) SAP AG                                  ADM130                                           1-52
  Creating an RFC listener inside SAP BC



          RFC destination
    destination         SAPBC635
    Gateway host        iwdf5020
    Gateway service     00
    program ID          SAPBC




                                 T20

                                       GW
                                                                  RFC listener
                                      SAPBC               SAP system          T20
                                                          Gateway host        iwdf5020
                                                          Gateway service     00
                                                          program ID          SAPBC

       SAP AG 2002




  An RFC listener is a connection from the Business Connector to a specific gateway of an SAP R/3
  System.
  It is important that you specify the same gateway host as you use for the RFC-Destination setup in
  the SAP system.
  You can configure several threads. The maximum number of threads that will be used in parallel is
  ten. This means that SAP BC can handle up to ten incoming requests for one program ID in parallel.
  To interpret an RFC call SAP BC must know the data types and structures used in the interface of the
  function module. It performs a lookup call to the R/3 DDIC.
  An external RFC server is not notified in case an SAP application server is shut down. This can lead
  to undesired behavior when the application server is started again because the listener will not be
  reached. SAP BC issues an RFC_PING call to the gateway host every ten minutes to check whether
  the host is up. It keeps pinging until the server is up again. The listener is then restarted.




(C) SAP AG                                    ADM130                                             1-53
  Creating a remote server in SAP BC




                T20                                         T21


                              remote server
                      alias        SAPBC_remote
                      host         10.18.115.205
                      port         5555
                      user         Administrator
                      pwd          ********




       SAP AG 2002




  A remote server can be another SAP Business Connector.




(C) SAP AG                                         ADM130         1-54
  Static routing: Using an Inbound Map




                 T20                                                      T21


                                          static routing




                                      inbound map
                 in
                             SAP server      T20
                             function module BAPI_1                     out
                             remote server SAPBC_remote
                             interface           BC635_00
                             service             bookinglist




       SAP AG 2002




  Application passes no target information
     If a certain call should be sent to only one receiver, it is easiest to set up an Inbound Map.
     No additional information for routing needs to be present.
  The Inbound Map is derived from the fact that the call is inbound for SAP BC.
  An Inbound Map acts as a point of entry for one specific message type (or function call) that comes
  in from one certain system.
  The only purpose of the Inbound Map is to route the call to another local or remote service that will
  process it.




(C) SAP AG                                     ADM130                                               1-55
  Example: XML representation of an IDoc




       SAP AG 2002




  This is an example of an order IDoc displayed in XML format by the SAP Business Connector.




(C) SAP AG                                  ADM130                                             1-56
  Plug-In Technology

  Plug-In Technology Plug-In Technology



                                                               mySAP Components
      Plug-In Technology




                                                               Internet Transaction Server
                                          Plug-In Technology




                                                               J2EE Appl. Server


                                                               Business Connector

                                                               Plug-In Technology Technology
                                                                               Plug-In



                                 SAP AG 2002




(C) SAP AG                                                                      ADM130         1-57
  Plug-Ins and Add-Ons




             BTEs are
             in R/3 SP
             from 4.0B




  The R/3 Plug-in is installed as an add-on in the R/3 System.
       SAP AG 2002




  Most Plug-Ins are Add-Ons.
  Add-Ons are enhancements to the SAP R/3 standard software with additional functions.
  Add-Ons are developed on the basis of R/3 Core releases in special Add-On systems.
  Add-Ons consist of:
    Newly developed additional objects
    Additional specific customizing
    Modified SAP R/3 System core objects with functionality to meet additional requirements (they
    are not basis objects but only objects from the SAP R/3 System application components, such as
    FI or MM)
  Add-On functionality is based on and integrated into SAP R/3 System core application components.
  Because neither the kernel nor basis objects are modified, Add-On objects use SAP R/3 System
  Basis interfaces and are not generally DB or OS specific.
  (Exception: IS-Oil ships a C program for temperature conversion.)




(C) SAP AG                                   ADM130                                            1-58
  R/3 Plug-In Technology: Transfer Technology



  Initial data transfer

      Initial installation
      New company code/new plant




          components                                         components
      •   Financials           PI                         • SAP APO • SAP CRM
      •   Logistics                                       • SAP BBP • SAP SEM
      •   Human Resources                                 • SAP BW



        SAP AG 2002




Initial data transfer is used, when:
   The customer setup a new component
   The customer adds a new business unit

Run the initial transfer and enter information in the new system (for example, master data)..




(C) SAP AG                                      ADM130                                          1-59
  R/3 Plug-In Technology: Transfer Technology



  Delta data transfer (event-driven)

         Changes (master and transaction data)
         New objects



                                    Event
         components                                             components
     •   Financials          PI                             • SAP APO • SAP CRM
     •   Logistics                                          • SAP EBP • SAP SEM
     •   Human Resources                        Event       • SAP BW


  Real-time data transfer:      SAP APO, SAP EBP, SAP CRM
  Periodic data transfer:       SAP BW
          SAP AG 2002




Delta data transfer is used in the production system to exchange current data.:
  APO ATP-Check: Synchronous data exchange
  APO, CRM, EBP: Near-realtime data exchange. The data is first sent to a queue and then sent
  immediately to the application.
  BW: Periodic data transfer




(C) SAP AG                                    ADM130                                            1-60
  R/3 Plug-In Technology: Add-On R/3 Plug-In


  The online data transfer takes place using exits that have
  been programmed as enhancements to the core coding:
  primarily BTEs and business add  -ins



                                       Core coding,                      Plug-in coding,
          components                      tables                             tables

     •    Financial
     •    Logistics
     •    Human


  BTEs are components of the R/3 Support Packages in
  Releases 4.0B and later.

         SAP AG 2002




  ‘Exits’ are part of the core coding. They offer you the possibility to transfer data event-triggered
  from R/3 to the Plug-in and from there, of course, to the mySAP.com application.
  Coding can be triggered by events built in SAP R/3 Support Packages for SAP R/3System Release
  4.0B and higher.




(C) SAP AG                                     ADM130                                               1-61
  R/3 Plug-In Technology: Transfer Technology


      Messaging: RFC (remote function call)
             BW: tRFC (transactional RFC)
             APO, BBP, CRM: qRFC (queued RFC)



      tRFC
             Transactions are always performed as a whole.
             Should the system crash during an update, the data is rolled back


      qRFC
             An extended tRFC that strictly adheres to the specified processing sequence




       SAP AG 2002




(C) SAP AG                                  ADM130                                     1-62
  Two Plug-in versions: PI & PI-A


      PI contains all plug-ins (for example PI 2000.1)
      PI-A contains only the plug-ins for BW and EBP (for example PI-A
      2000.1)

                  Advanced Planner    Business         Business to     Customer
                     & Optimizer     Information        Business      Relationship
   mySAP.com                         Warehouse         Procurement    Management
   Components
                    APO 3.0A         BW 2.1C            EBP 3.0       CRM 3.0



   PI 2001.1           APO-CIF        BW-BCT           B2B-PRO-PI      CRM-R3A
   3.1H - 4.6C



                                                    B2B-PRO-PI
    PI-A 2001.1                       BW-BCT        EBP 3.0 (3.1 I)
    PI-A 2000
    3.1H – 4.5B                                     EBP 2.0B (3.1I)
                                                    EBP 1.0B (3.1)



        SAP AG 2002                                                                            3.1x




  The PI 2000.1 (SAP R/3 Release 4.0B and higher) and the PI-A 2000.1 (for SAP R/3 3.1H until
  4.5B) are non-modifying Plug-ins.
  SAP R/3 Releases 3.1H + 3.1I: The PI 2000.1 modifies objects in the SAP R/3 core coding.




(C) SAP AG                                         ADM130                                        1-63
  R/3 Plug-In Release Strategy


      New “ND-Release” => new R/3 Plug-in release (around every 6 months)
      The distribution of the new R/3 Plug-in changes the maintenance for the
      previous PI release

               PI 99          PI 2000.1             PI 2000.2              PI 2001.1
             3.1H – 4.6B      3.1H – 4.6C           3.1I – 4.6C            3.1I – 4.6C
             APO 2.0A         APO 3.0A               APO 3.0A               APO 3.0A
             BBP 2.0A          BBP 2.0B              EBP 2.0                EBP 3.0
             BW       2.0A     BW    2.0B            BW     2.1C            BW     2.1C
             CRM 2.0A          CRM 2.0B              CRM 2.0C               CRM 3.0
             SEM 1.0B          SEM 1.0B

              PI-A 99        PI-A 2000.1          PI-A 2000.2            PI-A 2001.1
             3. 0F – 4.5B     3.1H – 4.5B           3.1I – 4.5B            3.1I – 4.5B
             BW       2.0A     BW 2.0B               BW 2.1C                BW 2.1C
                               BBP 1.0B*             BBP 1.0B**             BBP 1.0B***

                                            * for SAP R/3 3.1I: SAP BBP 2.0B/EBP 1.0
                                            ** for SAP R/3 3.1I: SAP BBP 2.0B/EBP 1.0 + EBP 2.0
                                            *** for SAP R/3 3.1I: SAP BBP 2.0B/EBP 1.0 + EBP 2.0 + EBP 3.0
       SAP AG 2002




  Use the most recent Plug-in if you want to use the most recent Release of the components.
  Plug-ins which are installed on systems with minimum Support Package Levels generally require
  manual implementation of a number of R/3 notes to work properly




(C) SAP AG                                      ADM130                                                       1-64
  Installation and Upgrade


                                    PI 2001.1                      PI-A 2001.1


                             PI 2000.2                      PI-A 2000.2


                        PI 2000.1                     PI-A 2000.1


                  PI 99                           PI-A 99

       Individual
        Plug-Ins


  (     An R/3 Plug-in can only be upgraded to the next higher plug-in!
  (     An upgrade from PI-A to PI is always possible, but not from PI to PI-A!
  (     A direct upgrade from a PI-A release to the next PI release (such as
        PI-A 2000.1 to PI 2000.2) is not possible.
         SAP AG 2002




  If there is an old individual plug-in inside (BW-BCT, etc.) you have to install the SAP R/3 Plug-in
  (to PI-A 99 or PI 99). After that you have to upgrade to the next higher SAP R/3 Plug-in Release (to
  PI-A 2000.1 or PI 2000.1)

  If there is an old R/3 Plug-in (for example, PI-A 99) inside, you have to upgrade the R/3 Plug-in (for
  example, to PI-A 2000.1)
  If you want to upgrade R/3 and R/3 Plug-in (for example,PI 99/4.01B to PI 2000.1/4.6B), please
  follow the following scenario:
      - Upgrade your R/3 system and keep the R/3 Plug-in Release (for example, PI 99/3.1H to PI
        99/4.6B).

      - Than upgrade your R/3 Plug-in Release (in this case from PI 99/4.6B to PI 2000.1/4.6B). For
        this upgrade use the installation/delta upgrade cd.

      - If you upgrade your R/3 Plug-in first you have to wait until the upgrade cd from the R/3 Plug-
        ins will be available, which is generally six weeks after the general availability from a new R/3
        Plug-in release.




(C) SAP AG                                       ADM130                                               1-65
  Unit Summary



                      You are now able to:

                         Describe the architecture of mySAP Role of the
                         ITS
                         Describe the J2EE Application Server
                         Describe the Business Connector
                         Decribe the Benefits of Plug-Ins




       SAP AG 2002




(C) SAP AG                              ADM130                            1-66
  Further Documentation



                      Additional information about mySAP Technology

                        BIT530 Business Connector
                        ITS070 SAP Internet Transaction Server
                        service.sap.com/r3-plug-in
                        service.sap.com/internet
                        service.sap.com/connectors
                        www.inqmy.com




       SAP AG 2002




(C) SAP AG                             ADM130                         1-67
                                                       Introduction: Exercise

                  Unit: mySAP Technology
                  Topic: Internet Transaction Server


                  At the conclusion of this exercise, you will be able to:
                  • Logon to a system using the ITS




                  You are an administrator responsible for the system configuration.




1-1   Log on using the Internet Transaction Server
      1-1-1 Log on to the EBP/CRM server using standard windows GUI. The instructor
             will give you the server name and system number.
             Client: 800
             User: ebp-##
             Pwd: init
      1-1-2 Call transaction SM04 (user list) to get a list of all users logged on.
      1-1-3 Note the terminal of your user.
      1-1-4 Logon with the webgui using the ITS.
             Start Internet Explorer on your computer. Type the following address (URL):
              http://<ITS-Host>.wdf.sap-ag.de:1080/scripts/wgate/webgui/!
             Your t instructor will provide you with the ITS-host.
            Use the same user as before.
      1-1-5 Call transaction SM04 (either through Windows- or webgui).
             Can you see your user being logged on again?
             Note the terminal of your user.
      1-1-6 Log off from your webgui. Close the internet explorer.




(C) SAP AG                                 ADM130                                      1-68
1-2   Log on using the Internet Transaktion Server using a user from a service file
      1-2-1 Log on with the webgui using the ITS.
             Start the Internet Explorer on your computer. Type in URL:
            http://<ITS-Host>.wdf.sap-ag.de:1080/scripts/wgate/isab2c/!
      1-2-2 Call transaction SM04 in your Windows GUI.
             Which user can be seen, who is logged in addition to you?




(C) SAP AG                                ADM130                                      1-69
                  Unit: mySAP Technology
                  Topic: Software Components and Plug-Ins


                  At the conclusion of this exercise, you will be able to:
                  • Identify the software components and Plug-ins for an SAP System




                  You are an administrator responsible for the system configuration.




2-1   Checking software components
      2-1-1 Log on to the CRM server using standard windows GUI (client 800).
            Determine which software components exist on this server.
      2-1-2 Log on to the SAP R/3 System, that is the backend for the CRM System in the
            first exercise. The instructor will provide you with the server name and system
            number.
            Client: 800
             User: back-##
             Pwd: init
             Determine which software components exist on this server.
             Can you see if any plug-ins are installed on this server?




(C) SAP AG                                ADM130                                         1-70
                                                         Introduction: Solutions

                  Unit: mySAP Technology
                  Topic: Internet Transaction Server


                  At the conclusion of this exercise, you will be able to:
                  • Log on to a system using the ITS




                  You are an administrator responsible for the system configuration.




1-1   Log on using the Internet Transaction Server
      1-1-1 Log on to the EBP/CRM server using standard Windows GUI. The instructor
             will give you the server name and system number.
             Start SAP Logon on your local computer. Choose NEW to create a new
             entry. Enter e.g. CRM as description. Enter the application server name
             and system number the instructor gave you.
             Logon with the following user:
             Client: 800
             User: ebp-##
             Pwd: init
      1-1-2 Call transaction SM04 (user list) to get a list of all users logged on.
      1-1-3 Note the terminal of your user.
             This is the name of your local PC where the SAPGUI was started.
      1-1-4 Log on with the webgui using the ITS.
            Start the Internet Explorer on your computer. Type in the following address
            (URL):
             http://<ITS-Host>.wdf.sap-ag.de:1080/scripts/wgate/webgui/!
             Your instructor will provide you with the ITS host.
             Use the same user as before.




(C) SAP AG                                  ADM130                                        1-71
      1-1-5 Call transaction SM04 (either windows- or webgui).
             Can you see your user being logged on again?
             You can see that your user is logged on again. If you haven´t logged off
             before, you are logged on twice.
             Note the terminal of your user.
             This is the hostname of the server, where the A-Gate of the ITS is running.
      1-1-6 Log off from your webgui. Close the Internet Explorer.
1-2   Log on using the Internet Transaction Server using a user from a service file
      1-2-1 Log on with the webgui using the ITS.
             Start the internet explorer on your computer. Type in URL:
              http://<ITS-Host>.wdf.sap-ag.de:1080/scripts/wgate/isab2c/!
            Logon to the system.
      1-2-2 Call transaction SM04 in your windows GUI.
             Which user can be seen, who is logged on in addition to you?
             You can see a user ITSGLOGAL, who is defined in the global service file of
             the ITS.




(C) SAP AG                                ADM130                                        1-72
                  Unit: mySAP Technology
                  Topic: Software Components and Plug-Ins


                  At the conclusion of this exercise, you will be able to:
                  • Identify the software components and Plug-ins for an SAP System




                  You are an administrator responsible for the system configuration.




2-1   Checking software components
      2-1-1 Log on to the CRM server using standard windows GUI (client 800).
            Determine which software components exist on this server.
             From the SAP Easy Access menu or any transaction, you can choose
             SYSTEM Status. In the SAP system status area, select the button for
             component information. Choose tab components.
             Here you can see the components SAP_Basis, SAP_ABA, and BBPCRM.
      2-1-2 Log on to the SAP R/3 system that is the backend for the CRM system in the
            first exercise. The instructor will give you the server name and system number.
            Client: 800
             User: back-##
             Pwd: init
             Determine which software components exist on this server.
             Perform the same as in the exercise above.
             You can see the components SAP_Basis, SAP_ABA, SAP_HR, and
             SAP_APPL.
             Can you see if any plug-ins are installed on this server?
             In the same window with the installed components you can see that the
             Plug-ins PI is installed.
             This information can also be obtained from transaction SAINT.




(C) SAP AG                                ADM130                                        1-73
  Configuring Internet Sales


                      1. mySAP Technology              7. Interface Monitoring



                      2. Configuring Internet Sales    8. System Monitoring



                      3. Configuring EBUYER            9. Backup Scenarios


                                                       Appendix Installation Scenarios
                      4. System Administration
                                                                Transaction Codes


                      5. Software Logistics



                      6. Role Management


       SAP AG 2002




(C) SAP AG                                    ADM130                                     2-1
  Configuring Internet Sales



                      Contents
                         SAP Solutions for CRM E-Selling
                         Connecting the Components
                         Business System Organization
                         APO, BW, and Content Server (Optional)


                      Objectives
                      At the end of this unit, you will be able to:
                         Describe the mySAP CRM
                         Connect the SAPMarkets Internet Sales components
                         Organize your business system for Internet sales




       SAP AG 2002




(C) SAP AG                                       ADM130                     2-2
  SAP Solutions for Internet Sales


                  SAPMarkets Internet Sales
  SAPMarkets Internet SAPMarkets Internet Sales
    SAPMarkets Internet Sales



                                                                        SAPMarkets Internet Sales Sales
                                                                                    SAPMarkets Internet
                      Sales




                                                                        Connecting the Components
                                            SAPMarkets Internet Sales




                                                                        Business System Organization

                                                                        APO, BW, and Content Server (Optional)




                            SAP AG 2002




(C) SAP AG                                                                              ADM130                   2-3
  SAP Solutions for Internet Selling

                               HTML generated by
                               Internet Transaction
                               Server                                     SAP R/3 OLTP


                                                                       Online
                                                                       Store
                                                                       TA WW20


                               Internet Middleware
 SAP Online Store




                                                               CRM                  SAP R/3 OLTP




                               Internet Middleware
 SAP Internet Sales
       SAP AG 2002




  SAP markets the following solutions for selling over the Internet:
     - SAP Online Store:
        Designed for customers who already use a production SAP R/3 System and want to establish an
        additional distribution channel using the Internet
        The only additional software required is SAP Internet Transaction Server (ITS)
     - SAP Internet Sales:
        Integral part of a complete Customer Relationship Management (CRM) system
        Enhanced functionality
        Freely definable interactive and visual design
  This unit deals with SAP Internet Sales. The SAP Online Store is the subject of course ECO690.
  SAPMarkets Internet Sales is a cutting-edge e-commerce solution for companies that wish to
  develop the Internet as a strategic sales channel. The SAPMarkets Internet Sales components enable
  your company to streamline and optimize all related Internet sales processes, reduce processing
  times significantly, cuts transaction costs, effectively establish customer contacts, and strengthen
  permanent customer relationships. This is achieved by the unique interplay between an open,
  striking, customer-friendly Internet frontend, and excellent deep reaching back-end business
  integration. Scenarios include selling directly to consumers and business partners, or indirectly via
  marketplaces or high-end reselling models along the supply chain and variations, including third
  parties.




(C) SAP AG                                     ADM130                                               2-4
  Internet Sales Scenarios




         B2C Scenario

                                         B2B Scenario



                                                                          Business via
  Steps in the Web Shop                                                   Marketplaces

                           Choose &                      Check
             Search        Configure       Order         Status


                      1              2              3             4



       SAP AG 2002




  This unit considers two business scenarios that are shipped with SAP Internet Sales 2.0B:
    - B2C - Business to Consumer
    - B2B - Business to Business
  The Web Shop regulates the execution of sales activities in either of the business scenarios.
  The process of purchasing products from the Web Shop using SAP Internet Sales can be divided into
  the following main steps:
    1) Search: Enter the Web Shop and select products
    2) Choose & Configure: Fill the shopping basket
    3) Order: Create a sales order
    4) Check status: Check the status of the sales order




(C) SAP AG                                   ADM130                                             2-5
  Internet Sales as a part of CRM




                                                               Face to
                                                                Face
                                                         Sales
                                                 M obile


                                                      CIC

                                              Intern                                     Customer
                                                    et Sa
                                                         les
                                                                      Internet




       SAP AG 2002




  SAPMarkets Internet Sales builds on the mySAP Customer Relationship Management solution.
  mySAP CRM supports all channels of interaction with customers, and its modules cover all
  customer-related areas in marketing, sales, distribution and service. mySAP CRM and SAPMarkets
  Internet Sales form an ideal basis for successfully implementing a multi-channel strategy. Regardless
  of whether your customers are visited by a sales representative, phone in their queries, or order
  products on the Internet, all information is passed on to the CRM system together as all touch points
  with the customers are synchronized. Key CRM components such as Marketing Management can be
  used for all kinds of interaction with customers, including over the Internet. SAP is setting standards
  with this unique combination of e-commerce and Customer Relationship Management, allowing
  your company to look after its customers personally and effectively.




(C) SAP AG                                     ADM130                                                 2-6
  CRM and Supply Chain Management (SCM)

                                          APO
                              BW

       Powerful Information                   Demand             Supply         Available
       Analysis                               Planning          Network            To
                                                                Planning        Promise



        Rich Business Content

       Upload via BW extractors           Integration via CIF for SAP OLTP
                                                                                      Plug-In
                                                                                          xx


        OLTP
                                                                      Non-SAP       Non-SAP
             SAP           SAP             SAP            SAP
                                                                       OLTP          OLTP


       SAP AG 2002




  SAPMarkets Internet Sales actively incorporates customers into supply chain management via the
  Internet. The ATP check (available to promise) in the SAP Advanced Planner and Optimizer (SAP
  APO) enables customers to retrieve real-time information on availability and delivery dates. The
  check can be run for production capacity and stocks in all warehouses and plants worldwide.
  Working with SAP APO means you provide binding information on your ability to deliver at the
  point in time when a customer submits a query via the Internet. This increases customer satisfaction,
  and you can effectively plan internal resource requirements , and deploy these resources more
  efficiently.
  The SAP Business Information Warehouse (SAP BW) is the central data warehouse of mySAP, and
  is responsible for collecting internal and external data, and preparing analyses and reports. Used in
  conjunction with SAPMarkets Internet Sales, SAP BW can be used for conducting marketing
  analyses and drawing up sales statistics. You can draw up bestseller lists for specific target groups,
  run multi-layered evaluations for sales figures, or conduct click-stream analyses of the Internet
  communication. The BW plays a key role in collecting and using business intelligence to focus on
  customers.




(C) SAP AG                                     ADM130                                                 2-7
  Technical Components in System Context

   Frontend                 Internet Middleware                  Application            Backend
                                                                 Middleware



                                                                                          R/3 OLTP
                                                                                           System




      Internet
      Customer

                                                                                             BW
                            CRM Internet Sales
                          SAP J2EE Engine   or       ITS

                           Web Server                   BC
                                                                       CRM
                               IPC          TREX       IMS                                  APO


       SAP AG 2002




  The SAP Index Management Service (IMS) is a tool for indexing all kind of documents that can be
  handled in the SAP R/3 or CRM environment. The IMS consists of two layers: the ABAP
  administration and the Search Server. The first layer contains all administration data for the IMS. It
  provides ABAP function modules for indexing and searching documents and administering the
  indexes. The second layer implements communication by remote function call (RFC) and provides
  an application programming interface (SAP Search Server API) for connecting different search
  engines.
  The TREX search engine offers the functionality of a standard text retrieval engine. It meets the SAP
  IMS Server API specification and is used in combination with the SAP IMS. TREX is used as a
  special purpose engine in the SAP R/3 System and e-commerce area. It provides advanced features
  for error-tolerant search and search by similarity. It is optimized for indexing mass data (for example
  in catalog scenarios or in an SAP R/3 System extended Help environment). TREX can index (and
  search) plain text and HTML documents in form of a file destination or text from memory.
  With the SAP Internet Pricing and Configurator (IPC) you can easily configure products, process
  product configurations, and determine their correct prices.




(C) SAP AG                                       ADM130                                               2-8
  Internet Sales: Efficient Load Distribution




      R/3               CRM
   Conditions                                     ...
   Configuration        Catalog                                                    Frontend
   Knowledge
                                                                                     100%
                                                       IPC
                                                   Index (IMS)

                                                 Web Platform
                                                    75%


                      Front Office
  Backend             Service 20%
  Execution
    4-5%

       SAP AG 2002




  SAPMarkets Internet Sales has been designed to give the high performance and fast response times
  you need for an effective e-commerce Web site. The solution typically runs on a distributed software
  platform to spread the processing load and prevent bottlenecks. The Internet front-end is entirely
  separate from the business logic back-end, so that changes to the look and feel of your browser-based
  applications need not interfere with the underlying business processes. The tight integration between
  SAPMarkets Internet Sales and your backend enterprise systems allows highly efficient one-step
  sales transactions, saving time and reducing administration overhead.




(C) SAP AG                                    ADM130                                                2-9
  Product Catalog


                                   Download catalog
                                   data to index
                                   Download
                                   multimedia objects

    Index Server                                               CRM
    TREX
    Web Server

                                                                             Download
                         Internet Transaction                                material masters
                         Server / SAPJ2EE Engine
                          generates HTML




   Web Browser                                           Backend SAP R/3
       SAP AG 2002




  The data for the Product Catalog are replicated on the Web server, so online access from the Web
  generates no load in the CRM system.




(C) SAP AG                                    ADM130                                             2-10
  Conditions and Configuration in Catalog




                                   Access to
                                   Pricing Data
         IPC                                                   CRM


                        ITS/SAP J2EE Engine                                  Download
                        generates                                            Pricing Data
                        HTML




                                                          Backend SAP R/3
   Web Browser

       SAP AG 2002




  The prices for the products that are maintained in the backend are loaded into the CRM or IPC, so
  Web users can configure products and find out prices without generating backend load.




(C) SAP AG                                    ADM130                                              2-11
  What Is Done Where?


                      SAP R/3     CRM         IPC      Index      Web
                                                       Server     Server

   Product master     Creation    Creation/   Access   Download
                                  download             from CRM

   Conditions         Creation    Creation/   Access
                                  download

   Catalog data                   Creation             Download

   Configuration  Creation                    Access
   knowledge base

   Multimedia                     Creation             Download Download
   documents                                           path names

   Business           Creation/   Creation/
   partners           upload      download

   Orders             Upload/     Creation
                      change

       SAP AG 2002




(C) SAP AG                               ADM130                            2-12
  Connecting the Components


                  Connecting the Components
  Connecting the components the Components
    Connecting the Components



                                                                    SAPMarkets Internet Sales
                     Connecting




                                                                    Connecting the Components
                                        Connecting the Components




                                                                                Connecting the Components

                                                                    Business System Organization

                                                                    APO, BW, and Content Server (Optional)




                          SAP AG 2002




(C) SAP AG                                                                          ADM130                   2-13
  Connecting the Components



                                               RFC
         Component


                                               Connections needed
                                               for upload, download,
                                               and reading data


                                                                        Component




       SAP AG 2002




  System connections must be configured to ensure that SAP Internet Sales can function technically.




(C) SAP AG                                    ADM130                                             2-14
  System Connection: CRM to SAP SAP R/3 OLTP




        RFC                    CRM                                     SAP R/3 OLTP
     Destinations




        SITE Definition
             and
        SMOFPARSFA



                                                       RFC



        SAP AG 2002




  Set up the logical system -needed for the SAP R/3 Plug-in. Use transactions BD54 (Define logical system) and
  SCC4 (Assign logical system).
  Connect the OLTP SAP R/3 System and the CRM.
     If a change is made in the OLTP SAP R/3 System, an RFC to the CRM Server is initiated through the SAP
     R/3 Plug-ins during the update. Conversely, when a CRM order is entered through the middleware, an RFC
     transports the data into the OLTP SAP R/3 System. Therefore you have to define RFC destination(s) on the
     CRM server and the OLTP SAP R/3 System.
  CRMCONSUM and SMOFPARSFA are the main parameter files of the CRM Server.
  Table CRMCONSUM contains the consumers (applications) that are to receive data from a source system.
  SMOFPARSFA contains all system control parameters, including the control information relevant to the R/3
  Adapter (Maintenance of SMOFPARSFA: Transaction R3AC6).
     - CRMCFSOLTP: The RFC destination of the OLTP SAP R/3 System for Customer Fact Sheets.
     - CRMCREDCHECK: The RFC destination of the OLTP SAP R/3 System for Credit Checks.
     - CRMCFSBW: The RFC destination of the BW System for Customer Fact Sheets.
     The parameters CRM_DEFAULT_DESTINATION (The RFC destination of the OLTP SAP R/3 System),
     CRM_DESTINATION_SFA_SERVER (The RFC destination of the CRM), and CRM_R3OLTP_ACTIVE
     (The OLTP SAP R/3 System release) are not used anymore and replaced by the site definitions.
     Site definition: Transaction SMOEAC (Middleware -> Administration -> Administration Console)
  If you want to use product availability information in the SAP R/3 System, define the destination of the SAP
  R/3 System in which the product availability information is checked. Add the following parameter to the table
  SMOFPARSFA:
     - PARSFAKEY: R3A_COMMON, PAR_NAME: CRM_DEFAULT_DESTINATION, PARNAME2:
         CRM_R3MATERIAL_AVAIL




(C) SAP AG                                        ADM130                                                   2-15
  Site IDs in the Middleware


         CRM transfers data to different Sites

              CRM



                                CRM (predefined)



          CDB                           Middleware            SAP R/3 OLTP
      (predefined)


              Mobile Clients (for Mobile Sales/Services)
       SAP AG 2002




  As of SAP CRM 3.0, OLTP SAP R/3 System has to be defined as a site, like the other systems of the
  distribution model. CRM and CDB sites are already predefined, so you only need to create the SAP
  SAP R/3 System site and Mobile client sites. Once you have created these sites, you have to define
  the distribution rules (subscriptions), which determine which data a site is to receive.
  You access to the site definition from the Implementation Guide or by Transaction code: SMOEAC
  (Middleware --> Administration -->Administration Console).




(C) SAP AG                                   ADM130                                             2-16
  Defining a new Site for the SAP R/3 System

  Administration Console




       SAP AG 2002




  Please note that RFC Destination for connection to OLTP SAP R/3 must be defined before
  performing R/3 Site definition.
  Define a new Site for the SAP R/3 System:
    - Choose object type in left screen as Sites
    - Choose Create icon
    - Type the name of the site and the description and choose the site type R/3
    - Choose site attributes next to site type
    - Enter the RFC destination for the site
  After defining the SAP R/3 OLTP and Mobile client sites, create subscriptions by subscription
  wizard. It should be done in the same screen like the site definition. Choose the object type as
  subscriptions and follow the subscription wizard instructions, which pop up when you choose create
  icon. This is necessary to enable uploading of the data from CRM to OLTP.
  With the Administration Console, create subscriptions for the publication All Business Partners
  (MESG) and All business transactions (MESG) and assign it to your OLTP sites. Please note that you
  need to create subscriptions for publications of type Simple intelligent (msg) and Simple bulk (msg),
  whose replication objects are assigned to site type R/3 in the BDoc Modeler and which you upload.
  Please refer to the Administration Console documentation for further information on how to create
  subscriptions. The business and condition objects that can be loaded from CRM to OLTP, or CDB to
  CRM, are available for viewing under SAP menu Middleware --> Data exchange --> Object
  management. See whether Upload mapping modules depend on the source and target systems for
  each object maintained.




(C) SAP AG                                    ADM130                                              2-17
  System Connection: SAP R/3 OLTP to CRM




                                 RFC
                                                                  RFC
             CRM                            SAP R/3 OLTP       Destinations




                                                               CRMRFCPAR
                                                              CRMCONSUM
                                                               (former table:
                                                              CRMPAROLTP)




       SAP AG 2002




  Up to PI 2000.1, the parameters in table CRMPAROLTP are used, in particular
  CRM_DEFAULT_DESTINATION for the correct RFC connection. As of PI 2000.2, check the
  entries in the tables CRMCONSUM and CRMRFCPAR; the table CRMPAROLTP will no longer be
  used for RFC specific settings. The table CRMCONSUM must contain the consumer application (for
  example, CRM). The RFC destination of the CRM server must be entered in the table CRMRFCPAR
  (note 430980).
  Table CRMCONSUM must contain the consumer application, generally CRM. Use Transaction
  SM30 to enter the CRMCONSUM entry. The message Choose the key from the allowed name space
  is normal. Confirm the message and save the entry if it does not exist.
     - CONSUMER: CRM
     - ACTIVE:          X
     - TEXT:            CRM
  Table CRMRFCPAR must contain the RFC destination of the CRM server. Check the following
  parameters in table CRMRFCPAR:
     - CONSUMER: CRM
     - OBJNAME: *
     - RFCDEST: (customer-specific: destination CRM server)
     - DOWNLOAD: *
     - INACTIVE: blank
     - DISCARDDAT: blank
     - USE_IN_Q: X
     - XML SEND: X
     - HOLD_DATA: blank
     - USE_IN_Q: X


(C) SAP AG                                 ADM130                                           2-18
  System Configuration of CRM




                      Dispatcher

                        Generates industry
                      template independent
    B-WP
                           objects in batch



             CRM                                    XML or Endian Conversion
                                                    Data word format example
                                                    31415926535 (decimal) = 5088FF07 (hex)
                                                    Little Endian format: 07 FF 88 50
                                                                          (low byte first)
                                                    Big Endian format: 50 88 FF 07
       SMOFPARSFA                                                       (high byte first)


       SAP AG 2002




  Generate the middleware with its industry template independent objects by using transaction SM36
  to scheduling report SMOG_AUTO_GENERATION2 in background. Generate the middleware with
  its industry template specific objects by scheduling report SMOG_AUTO_IND_GENERATION2 in
  background. Schedule both reports to run a second time (SAP Note 205266).
  To eliminate or minimize problems that occur during the data transfer between different operating
  and computer systems, an XML interface was implemented in the R/3 Adapter in addition to the
  binary transport, which has been used so far. This XML interface consists of an XML generating
  program on the OLTP-Plugin and an XML parser on the CRM. The generating program generates an
  XML document from the data stream to be sent to the CRM System and the XML parser converts
  this back into the original data stream. Except for the initial configuration, the mechanism is
  transparent and does not require further user activities.
  The XML format is at a disadvantage because the XML parser needs CPU time (which can be
  processed in parallel because no database access is made). If you do not want the XML conversion in
  a specially defined system landscape, then set parameter CRM_SEND_XML to blank in the CRM
  System, and set table CRMPAROLTP (PI 2000.1) or CRMRFCPAR (PI 2000.2) without XML in
  the SAP R/3 OLTP. In addition, parameter CRM_CONVERT_ENDIAN must be maintained
  correctly in the CRM System (see Note 0207264). You can do without the XML conversion under
  the following conditions:
     - The OLTP system infrastructure and the CRM system infrastructure must be homogeneous.
        Example: all OLTP application servers UNIX and all CRM application servers UNIX.
     - You must also make sure that no application servers with different operating systems are used
        in the future. The OLTP system infrastructure must be homogeneous. In the CRM System it is
        possible to limit the application servers permitted for the processing of the queues by setting a
        specific server group. The application servers of these group servers must be homogeneous.


(C) SAP AG                                     ADM130                                               2-19
  Types of Data Exchange



          CRM                                           SAP R/3 OLTP




  Different types of data exchange

         Loads to and from a CRM System :
             Initial data transfer: Business and customizing data
             Delta data transfer: Business data only
             Synchronization: Business and customizing data


       SAP AG 2002




  The following types of data transfer to and from the CRM System to the SAP R/3 Systems are
  distinguished:
    Initial data transfer (business data and customizing data): After the installation of the CRM
    Middleware all data needed (pre-defined objects) from an external system is loaded in bulk to the
    CRM System.
    Delta data transfer (business data only): Only delta information is loaded from the external
    system during normal operation. For example, when modifying customers on the external system,
    only the modifications are transferred to the CRM Middleware.
    Synchronization (business data and customizing data): By using the so-called request or the
    transaction Synchronize Objects the different datasets are synchronized via a data load. In contrast
    to the delta load for business objects, customizing data is not exchanged automatically.




(C) SAP AG                                     ADM130                                               2-20
  Architecture Initial Load
              CRM                                         SAP R/3 OLTP



                  Trigger Initial                     OLTP Trigger
                  Load                                Load



                          Inbound
                         Processing
                                           qRFC       Dialog Workprocess
                                                      Extract Data from DB


                         Validation

                                                      Send to Server
                         Outbound
                         Processing



         Units of                                                               Units of
         Measure                                                                Measure
       SAP AG 2002




  Initial load extractors are triggered from the CRM middleware. The dimensions, ISO codes, and
  units of measurement must be identical in the backend and in CRM.
  Steps in initial load process:
     1. The CRM transaction triggers an initial load by means of a qRFC call in the SAP R/3 OLTP.
     2. The RFCs are queued and processed in sequence (of exclusively dependent or independent
     objects).
     3. In SAP R/3 a function module (extractor module) is called, to extract the requested data
     according to the given filter criteria.
     4. A data container is created with the selected data, to be sent to CRM middleware server.
     5. The data is transferred by RFC in the form of tables to the CRM.
     6. In the CRM, the data container is transformed through a mapping into a Messaging BDoc.
     7. The BDoc is stored in the CRM database.
     8. Flow control processes the BDoc by means of services. Depending on the BDoc type, the
     middleware initiates the appropriate services
     9. When all blocks for these objects have been transferred, the CRM loads the next object.
  To make the initial load parallel, use parameter R3A_Common - MAX_PARALLEL_PROCESSES
  in table SMOFPARSFA (default value 5). The extractors set commits blockwise, so no runtime
  overflows should occur (rdisp/max_wprun_time).




(C) SAP AG                                  ADM130                                            2-21
  Object Filter

                      SAP R/3 OLTP




                                                    Filtering of Business,
                                               Customizing, and Condition
                                                                   Objects
                      CRM




       SAP AG 2002




  Using the Middleware --> Data Exchange --> Object Management (R3AC1, R3AC3, and R3AC5)
  you can make object-specific settings, such as defining filters. New, customer-defined exchange
  objects can also be defined here, provided you have already created a BDoc. There are three basic
  types of adapter exchange objects: Business objects are master data and transaction data that is
  usually predefined by SAP and changed only minimally by customers. Customizing objects are
  Customizing tables (T*-tables, for example, T100). Condition objects are condition tables for price
  evaluation.
  The object name and description are displayed in the Object Data group in the detail view. You can
  activate or deactivate objects by choosing the option Object Inactive. You can deactivate
  independent objects only if all other objects dependent on them have also been deactivated. Before
  starting initial data transfer, you should specify which objects are to be copied to the CRM Server.
  The transfer of objects is dependent on the scenario used (for example, for EBP only a very few
  objects are needed) and on the SAP R/3 Release. For example, objects in a mobile service scenario
  can be only copied as of SAP R/3 Release 4.5B. The data is stored in table SMOFOBJECT.
  Under Filter Settings you can set filters for a business object. For Customizing and condition objects
  the filters can be defined only using tables/structures and the table-related filter symbol. If you use
  more than one filter entry per object, filters to the same table field are linked with an OR. Filters to
  different table fields are linked by AND.
     - The filter condition VKORG = 0001, VKORG = 0002 results in a set that contains both the first
        and second sales organization.
     - The filter condition VKORG = 0001, VTWEG = 01 results in objects that fulfill both conditions
        at the same time.




(C) SAP AG                                      ADM130                                               2-22
  Initial Load



                                               1. Transfer of Customizing
                                               2. Initial Load of Business Objects
                                                  (such as material master data)




         CRM                                                    SAP R/3 OLTP




       SAP AG 2002




  To configure the CRM servers, use transaction R3AS. Perform the initial load of the Customizing
  objects. Set the parameters as follows:
     - Object class - Customizing
     - Download object - DNL_CUST*
  We recommend that you first check the load for a single object. For example, select the object
  DNL_CUST_UNITS and compare the tables T006 (OLTP SAP R/3) and SMOT006 (CRM).
  Start the initial load. You can either choose all defined business objects (More Selection Criteria, All
  Objects) or, under Customizing Objects, set a restriction on the object classes and objects.
    1. Choose Middleware → Data Exchange → Initial load → Start.
    2. In the group frame Object, enter the object class and the load object.
    3. If you set no restriction on the objects for the load, in the group frame More Selection Criteria
    select All Objects and perform the initial load.
    4. To start the load, choose Execute.
  In addition, the following steps must be performed (see installation guide):
     - Set up the organization model.
     - Set up the business objects business partner.
     - Set up the business objects product.
     - Set up the condition objects.
     - Match the order position types.
     - Match the product groups.




(C) SAP AG                                      ADM130                                                2-23
  Mapping of Tables


              CRM                                             SAP R/3 OLTP



  Table <Prefix>xyz                                                Table xyz




      GUIDs as primary keys                                SAP R/3 primary
                                                           key
      Tables are partly like those in
      OLTP SAP R/3
      Tables can have fewer fields
      than the related OLTP SAP R/3
      table
      Tables can have additional
      fields
       SAP AG 2002




  Generally, application tables in the CRM system have the prefix SMO.
  Some important development classes are:
     - SMOF (R/3 Adapter Service)
     - SMOG (CRM Middleware Repository Services)
     - SMOH (Replication & Realignment Service)
  Globally unique identifiers (GUIDs) serve as primary keys for all tables in the CRM database. They
  are necessary because normally the SAP R/3 key does not exist when a new record is created in the
  Mobile Sales system. A GUID is generated by an algorithm that uses as input data certain hardware
  information about the host computer, its current system time, and a randomly generated number. The
  GUID can be represented in various formats. For CRM, a 32-byte character sequence is used. It is
  globally unique in the sense that no two GUIDs produced either on different computers or at
  different times can be the same.
  For any table, its primary key is called SFA<table name without the prefix SMO>.
     - Examples: SFAKNA1, SFAMARA




(C) SAP AG                                   ADM130                                             2-24
  Monitoring the Initial Load




      Object dependencies are handled by the CRM
           Example: customers before sales documents
           Independent objects are downloaded at the same time
       SAP AG 2002




  Object dependencies are kept in table SMOFOBJPAR and are used to control the load order of
  objects during an initial load. To monitor the order, call transaction R3AM1 and choose Middleware
  → Monitoring → Data Exchange → Monitor Objects.




(C) SAP AG                                   ADM130                                             2-25
  Activating Delta Load in SAP R/3



                                                 Check these tables in SAP R/3

               SAP R/3 OLTP



                 TBE11
                 TBE11                 TBE31
                                       TBE31            CRMPAROLTP
                                                        CRMPAROLTP             CRMRFCPAR
                                                                               CRMRFCPAR

                To activate
               To activate             To activate
                                      To activate              To activate
                                                              To activate           To specify
                                                                                    To specify
              delta download
                delta load          delta download
                                       delta load           delta download
                                                               delta load             RFC
                                                                                       RFC
               for for R/3
                    SAP R/3          for each object
                                    for each object           for the client
                                                             for the client        destinations
                                                               you want to         destinations
                                                              you want to
                                                                download
                                                               download




       SAP AG 2002




  Activating a delta load in the SAP R/3 System:
     Before you can run a delta load to synchronize your data, this function must be active in your SAP
     R/3 System. Use the SAP data browser to check whether the tables TBE11, TBE31,
     CRMPAROLTP, and CRMRFCPAR contain the necessary entries. If any table entries are
     missing, enter them.
  Make sure that the event control is active in the OLTP System, table TBE11. Although the event
  control is delivered in the activated status, it is possible that it was deactivated for test purposes. If
  this is the case, you must activate the entry both for application indicator BC-MID and NDI. For this
  purpose, start Transaction SE16 (Release 3.x) or SM30 (Release 4.x) with table TBE11. Set the
  Active flag for BC-MID and NDI.
  Table TBE31 contains the subscribed event modules for individual business objects. You must carry
  out the check from the CRM server. Note: For certain data objects, TBE31 entries are not required or
  entered because the delta supply from the OLTP System for these objects is carried out via BADIs. If
  you have problems with the activation of the delta data, refer to the respective application
  component.




(C) SAP AG                                         ADM130                                              2-26
  Delta Load

                                           Employee
                                           (such as changes to material master)

         CRM                                                  SAP R/3 OLTP



                         Inbound                            Update function          Dialog
                                                            modules
                        Processing                                                   Program

                                                                                   Call Business
                         Validation
                                              qRFC         Event distributor       Transaction
                                                                                   Event (BTE)

                        Outbound
                        Processing
                                                             Result sender




       SAP AG 2002




  An in-house employee working online with a dialog program changes some data and thus generates
  delta data. The dialog program calls the update function modules and commits the change. The
  update module calls the business transaction event (BTE) and the subscribed result sender sends the
  data to the CRM middleware server. In contrast to the upload process, there is no additional CRM
  data for the result sender to send to the CRM middleware server. A new BDoc is created for the data
  received from the OLTP SAP R/3 and flow control is started to process the BDoc.
  Different applications (such as BW and APO) can also subscribe to the delta data. This is done by an
  entry in OLTP SAP R/3 table TBE31. Each event can be processed at several different times (by
  several applications using different function modules).
  Delta load is active for certain objects. Source code is implemented in an update task for a specific
  business object, and qRFC is triggered automatically.
  In the OLTP SAP R/3 System, ensure that event control (table TBE11) is active. Although event
  control is shipped activated, it may have been switched off for test purposes. If so, activate the
  entries with the application qualifier BC-MID and NDI. The update function modules call a BTE that
  starts the function module registered in table TBE31, which takes over the transfer to the CRM
  server.




(C) SAP AG                                    ADM130                                               2-27
  Upload using Site IDs in the Middleware

             CRM                                                    SAP R/3 OLTP


                                           Example:
                                          Sales Order




  CRM Server transfers data to different Sites
        CRM

                        CRM (predefined)



         CDB
                            Middleware           SAP R/3 OLTP
     (predefined)



           Mobile Clients (for Mobile Sales/Services)
       SAP AG 2002




  The delta loads allow a continuous synchronization of all predefined adapter objects (except
  customizing tables) between the SAP R/3 Systems and the CRM. Modifications are sent to the CRM
  Server immediately. Received data is processed automatically. qRFC is used for the serialization.
  Delta loads may also consist in loads from the CRM System to an SAP R/3 System. Upload is using
  the Site to transfer data to OLTP SAP R/3.
  As of SAP CRM 3.0, OLTP SAP R/3 System has to be defined as a site, like the other systems of the
  distribution model. Once you have created the sites, you then have to define the distribution rules
  (subscriptions), which determine which data a site is to receive. All of the objects have to be loaded
  to the CRM system first, even though you wish to load the data from the OLTP system to the CDB.
  There are two steps for loading the data:
     - The first step is from OLTP to CRM system applications component (site type CRM).
     - The second step is from CRM system to CDB.




(C) SAP AG                                     ADM130                                               2-28
  Internet Sales using the SAP J2EE Engine

  http://p12345.wdf.sap-ag.de:1080/b2b/b2b/init.do



                                    TREX
                                  Search      SAP                                        APO
                Web Server               IMS
                                  Engine     Gateway

                    SAP                                                                       RDBMS
    HTTP           J2EE                                       CRM
                   Engine           SAP J2EE Engine
                  Extension                                          CRM                 BW
                                  SAP J2EE SAP J2EE
                                    Engine   Engine
                                  Dispatcher Server                    RDBMS                  RDBMS


                      Product
                      Catalog                                                          R/3 OLTP
                       Files                 IPC
                                       Internet Pricing                                Plug-In
                                      and Configuration
                                                                                              RDBMS


       SAP AG 2002




  From CRM 3.0 onwards, Internet Sales uses Java Server Pages (JSP). Internet Sales Java Application
  runs on any JSP 1.1 and Java Servlet 2.2 compliant environment. SAP delivers the SAP J2EE
  Engine, a product from InQMy EngineTechnologies GmbH, which is compatible with J2EE (Java 2
  Enterprise Edition). To establish a connection between the Internet Sales Java Application and the
  CRM server the SAP Java Connector is required. The installation guide describes the installation and
  configuration for the SAP Internet Sales Java Application, Installation of the SAP J2EE Engine
  version 4.2.7, Installation of the SAP Java Connector 1.1, Configuration of the SAP J2EE Engine,
  and deployment of the SAP Internet Sales Web Application Components
  SAP Internet Sales 3.0 Java Application Components include software developed by the Apache
  Software Foundation (http://www.apache.org/). SAP Internet Sales 3.0 Java Application
  Components include library pushlets, a software developed under the GNU Lesser General Public
  License. The source code of the library pushlets can be obtained free of charge (except the costs of
  shipping and handling). SAP guarantees the support of the included open source libraries with
  exception of the struts-tags, which are not used by the SAP Internet Sales Application.
  The CRM Internet Sales Web Application Components consist of three Web Application archives.
  The configuration must be performed for the Web Application Components b2b.ear and b2c.ear,
  which have to be installed. For the Enterprise Application Archives b2b.ear and b2c.ear some
  context parameters have to be maintained. Configure the following SAP J2EE Engineconnection
  parameters by searching for the parameter name in the Deployment Tool. If the parameter name does
  not exist, you have to add this parameter manually to the file web.xml after the deployment.
  The CRM Web Application can be started with the following URL:
  http://<full_qualified_host>:<port>/<EAR>/<EAR>/init.do
  For example:
  http://p12345.wdf.sap-ag.de:1080/b2b/b2b/init.do


(C) SAP AG                                    ADM130                                              2-29
  Web.xml - Connection of SAP J2EE Engine
  and CRM Server

    File: <EAR-ROOT>\Web-inf\web.xml




       Internet Sales Middleware

    SAP J2EE Engine JCo


                                                               CRM




       SAP AG 2002




  Maintain the default language of the SAP Internet Sales Java Application:
    - language.isa.sapmarkets.com <language>, for example, en
  Maintain the parameters for the connection to the CRM server:
    - client.jco.sp.eai.core.isa.sapmarkets.com <SAP logon_client>, for example, 800
    - user.jco.sp.eai.core.isa.sapmarkets.com <SAP logon_user>, for example, weblogin. This user
       needs the role SAP_CRM_ISA_ITSLOGIN
    - passwd.jco.sp.eai.core.isa.sapmarkets.com <SAP logon_password>, for example test
  You can access the CRM server by entering the hostname or by using load balancing.
  Connection via application host:
    - ashost.jco.sp.eai.core.isa.sapmarkets.com          <hostname_CRMserver>, for example,
       host4711
    - sysnr.jco.sp.eai.core.isa.sapmarkets.com <systemnumber_CRMserver>, for example, 11
    Connection via message server (load balancing):
    - r3name.jco.sp.eai.core.isa.sapmarkets.com <SID_CRMserver>, for example, P30
    - group.jco.sp.eai.core.isa.sapmarkets.com <logon_group>, for example, PUBLIC
  Independent of the connection type (via application server or load balancing), a connection pool
  must be used in order to access the CRM server efficiently. The size of the connection pool is
  specified using the following parameter:
    - maxcon.jco.sp.eai.core.isa.sapmarkets.com <Maximal_size_of_SAP_connection pool> The
       value should be approximately twice the number of the concurrently working users.




(C) SAP AG                                   ADM130                                            2-30
  Connection of SAP J2EE Engine and
  CRM Server via EIS

  Connection using                               Property                 Value
                                                 ClientNumber             see SAP R/3 login
  the standard                                   UserName, Password       see SAP R/3 login
  EISConnector Service                           Language
                                                 ServerName               specific SAP R/3 system
                                                 SystemNumber             LS6, B20, CSN
                                                 MessageServerName        see SAP R/3 login
                                                 SystemName               group PUBLIC
                                                 GroupName
                                                 GatewayServerName    optionally
      Internet Sales Middleware                  GatewayServiceNumber


        SAP J2EE Engine
         EISConnector                                                   CRM

                                   JCo



       SAP AG 2002




  As the JCo is not an official standard, but only an SAP Implementation, SAP has implemented the
  EISConnector Service, which was defined by SUN to connect the JAVA Application to any ERP
  system. This Service Implementation is based again on the JCo, but offers another abstraction layer.
  The Parameters can be set alternatively (for example, with the SAP J2EE Engine Admin Tool).




(C) SAP AG                                     ADM130                                               2-31
  Web.xml - Connection of SAP
  J2EE Engine and IPC


    File: <EAR-ROOT>\Web-inf\web.xml




       Internet Sales Middleware

    SAP J2EE Engine JCo


                                                           Internet Sales Middleware

                                                                          IPC



       SAP AG 2002




  Maintain the parameters for the connection to the Internet Pricing & Configurator:
   - host.ipc.boi.eai.core.isa.sapmarkets.com            <IPC_hostname> the IPC Client connects to.
   - port.ipc.boi.eai.core.isa.sapmarkets.com            <IPC_client_port> that connects to the IPC
      server. The default port for the IPC is 4444.
   - type.ipc.boi.eai.core.isa.sapmarkets.com            <IPC_servertype> The value must be ISA.
   - encoding.ipc.boi.eai.core.isa.sapmarkets.com        <character encoding> This parameter is
      needed for the communication with the IPC server. The default value is UnicodeLittle. There is
      a corresponding parameter on the IPC server that should always have the same value.
   - dispatcher.ipc.boi.eai.core.isa.sapmarkets.com <dispatcher_status>, that is usage of
      dispatcher (true or false)




(C) SAP AG                                   ADM130                                             2-32
  IPC Architecture: Details


    IPC Remote                 IPC Monitor             <Application>
      Admin
       IPC Client                IPC Client               IPC Client




                           IPC Server Layer                                   IPC Dispatcher


                      TTE          SPE        SCE          PME

                      Buffer        Buffer    Buffer       Buffer


     IPC Base                        Database Layer                    IPC-TTE:
       Tools                                                             Transaction Tax Engine
                         CRM RFC Layer                 JDBC
                                                                       IPC-SPE:
                                                                         Sales Pricing Engine
      IPC Server
       Settings                               CRM DB Layer
      (XML File)                                                       IPC-SCE:
                                                                         Sales Configuration Engine

                                              CRM Database             IPC-PME:
                                                                         Product Modeling Environment
       SAP AG 2002




  The IPC Administrator lets you configure the database connection and provides default parameters
  and header attributes for documents created with the IPC. The IPC server is the computer where the
  Sales Configuration Engine (SCE) and Sales Pricing Engine (SPE) run.
  IPC dispatcher: Provides load-balancing facilities for IPC servers. The IPC dispatcher maps session
  requests from IPC clients to an available IPC server, whether it is the only server or one of many.
  The IPC dispatcher is active by default, even in a single-host installation. Each IPC server is
  dedicated to exactly one IPC dispatcher. The IPC server registers at its IPC dispatcher when it starts
  up. If you use the Internet Pricing and Configurator with CRM Online or Internet Sales, and have
  more than one IPC server, the IPC dispatcher manages IPC sessions to ensure an efficient
  distribution of sessions between the different servers. You can use the IPC dispatcher as delivered,
  but you can configure your installation to match your specific requirements.
  The IPC server and dispatcher now includes the RFC server functions that were provided by the IPC
  bridge in previous releases. ABAP code can call IPC server commands via RFC function calls on all
  platforms supported by JCo, not just on Windows computers.The RFC request is passed directly to
  the IPC server, which works on it without any string conversion, then IPC commands directly write
  their response to the output and table parameters of the RFC function.
  Set up a TCP/IP connections called IPC_RFC_DISPATCHER and IPC_RFC_SERVER_X (one for
  each IPC server).
  For all RFC destinations maintain: Program ID: <Name of RFC Destination>, Gateway Host: <Host
  of CRM>, Gateway Service: <Gateway of CRM>, Usually sapgw<SysNr.>
  Maintain the RFC destinations in table SMOFPARSFA, where the key is
  IPC_RFC_DISPATCHER, and parval1 is IPC_RFC_DISPATCHER.
  Maintain a few properties in dispatcher.properties in folder lib/properties
  rfcEnabled = true, rfcGateways = <servername>:<port>, rfcDispatcherProgId =
  IPC_RFC_DISPATCHER rfcServerCount = 2, rfcServerProgIdPrefix = IPC_RFC_SERVER_

(C) SAP AG                                             ADM130                                           2-33
  Web.xml - Connection of SAP J2EE Engine and
  IMS/TREX


    File: <EAR-ROOT>\Web-inf\web.xml




       Internet Sales Middleware

    SAP J2EE Engine JCo


                                                             Internet Sales Middleware

                                                                      IMS/TREX



       SAP AG 2002




  Maintain the parameters for the connection to the Index Management Server (of TREX):
   - useDynConnParam.ims.catalog.isa.sapmarkets.com
      If this value is set to true the logon parameters to the IMS server are requested from the CRM
      server
   You must maintain these parameters only if the above parameter is set to false:
   - gwhost.ims.catalog.isa.sapmarkets.com                <Gateway_Host>
   - gwserv.ims.catalog.isa.sapmarkets.com                <Gateway_Service>
   - tphost.ims.catalog.isa.sapmarkets.com                <Hostname_IMSserver>
   - tpname.ims.catalog.isa.sapmarkets.com                <program_name>, for example
      ims_server_admin.exe




(C) SAP AG                                    ADM130                                              2-34
  Definition of Search Server Relation



      Internet Sales
      Middleware




     Define
     search engine
     to be called



             TREX                            IMS



                                                       RFC                             CRM

        SAP AG 2002




  Two RFC destinations are required for connection IMS and CRM Server:
     - RFC Destination IMSDEFAULT with activation type = start for indexing documents.
     - RFC Destination IMSDEFAULT_REG with activation type = registration for searching documents.
  You can maintain the search server relation in CRM in transaction SRMO. In this transaction, a relation to an
  RFC destination is formed through the search server relation.
  Activating the Document Space
     - Activate the required document space in the IMG (Document Management Service Maintain indexing
         readiness).
     - Schedule report RSTIRIDX as a daily background job (transaction SM36). The report RSTIRIDX starts
         indexing the preselected documents. It also logs indexing errors in the productive system.
  The SAP Text Retrieval & Information Extraction Software is already configured on installation. The settings
  are adapted to a typical standard hardware configuration. If you consider that the performance of the system in
  the productive system is insufficient, you can change the initial settings
  The SAP communicates with the TREX computer via the installed RFC Destination. When the SAP Gateway
  is started on the TREX computer, several processes may be registered in the operating system to distribute the
  load (standard: two processes). To change the number of registered processes:
     - Edit the file sapservice.reg in the installation path (for example, Program Files\SAP\SAPTREX) in
         subdirectory tune.
     - For parameter Instances enter the new number of registered processes.
     - To activate the changed settings, you must update the registry and restart the SAP Retrieval Service and,
         execute the file reconfigure.bat in the installation path in subdirectory tune. The batch file carries out the
         following steps: a) stops the SAP Retrieval Service; b) updates the registry; c) starts the SAP Retrieval
         Service.




(C) SAP AG                                            ADM130                                                       2-35
  Web.xml - Connection of SAP J2EE Engine and
  Webserver


    File: <EAR-ROOT>\Web-inf\web.xml




       Internet Sales Middleware

    SAP J2EE Engine JCo


                                                            Internet Sales Middleware

                                                                     Webserver



       SAP AG 2002




  Maintain the parameter for the multimedia data (mimes):
   - mimes.core.isa.sapmarkets.com
      This value describes the URL to the mimes. It should point to the address containing the mimes.
      The format must be: http://<full_qualified_host>:<port>/<projectname>/
      for example, http://p12345.wdf.sap-ag.de:1080/b2b/
  Maintain the parameter for product catalog:
   - imageserver.catalog.isa.sapmarkets.com
      This value describes the URL to the documents replicated from CRM (for example, product
      images). Example of a URL: http://p12345.wdf.sap-ag.de:1080/
  Maintain the parameter for Web Auction:
   enable.auction.isa.sapmarkets.com
   This value describes describes the Web auction function, which can be activated or deactivated.
   Possible values: true or false
   If you do not use Web Auction functionality make sure that the value of this parameter is set to
   false.




(C) SAP AG                                    ADM130                                             2-36
  Connection of SAP J2EE Engine and IIS


         Connecting Microsoft Internet Information Server IIS
         and SAP J2EE Engine


         You use an ISAPI filter, an ISAPI extension and a separate
         configuration file to specify which requests will be forwarded to the
         SAP J2EE Engine


         Requirements:
              ISAPI filter InQMyProxyFlt.dll
              ISAPI extension InQMyProxyExt.dll
              Configuration file InQMyProxyFlt.ini containing custom request
              forwarding rules




       SAP AG 2002




  Installation steps
    - Copy InQMyProxyExt.dll, InQMyProxyFlt.dll and InQMyProxyFlt.ini to the \Inetpub\Scripts
       directory of MS IIS (for next releases any directory with execute permissions id okay),
    - Edit the InQMyProxyFlt.ini file and set your custom forward rules
    - prefix --> host : port (port number 80 is default and therefore optional)
    - For example: petstore --> www.InQMy.com:8080 will redirect requests that have prefix
       /petstore/* (like http://myIIS/petstore/) to http://www.InQMy.com:8080/petstore/*.
    - Configure MS Internet Information Server to load the ISAPI filter.
    - For the ISAPI extension no additional steps are necessary.
    - Use the Microsoft Management Console to configure IIS to load the ISAPI filter.

  Read the IIS Integration Newsletter regarding a detailed step by step description.




(C) SAP AG                                     ADM130                                       2-37
  Connection of Web Server and CRM Server

     Internet Sales Middleware

                                                    Needed for publication
          Web Server                                of multimedia objects

         Subdirectory                                         CRM




                                                              RFC
                                                               RFC
                                                           Destinations
                                                           Destinations
  FTP/
  HTTP
                                                                                    RFC


                                SAPFTP
                                SAPHTTP
       SAP AG 2002




  A catalog usually contains binary data such as images, audio files, and other MIME objects. Since
  the IMS cannot handle binary data, the MIME documents are replicated to the Web server into a
  special directory. For this purpose, the File Transfer Protocol (FTP) and HyperText Transfer
  Protocol (HTTP) are used.
  FTP and HTTP settings for publication:
     To make a product catalog available in the Web, it must be replicated on the IMS. This replicates
     all product information, texts, and the structure of the product catalog. Part of the replication is
     publication of the documents (images, audio files, and so on) in the product catalog. With this
     procedure, you can ensure the publication of necessary settings on the Web server and set up a
     connection to the CRM system.
  1. Set up RFC destinations SAPFTPA and SAPHTTPA; both RFC destinations must start the related
  programs:
     - SAPFTPA starts program SAPFTP.
     - SAPHTTPA starts program SAPHTTP.
     By running on the SAP R/3 System application server site, the reports, which replicate product
     catalogs, can run as background jobs.




(C) SAP AG                                      ADM130                                               2-38
  FTP and HTTP Processes

     The FTP port is used to physically access the file server for
     creating subdirectories and deleting depublished files
     The HTTP port is used to physically access the file server for
     transporting the published files
     The FTP and HTTP services are both provided by the Web server
     The directory to which the published documents are copied must
     be created below the Web server root directory




       SAP AG 2002




  2. Set up HTTP:
     The product catalog documents are transported to the Web server using HTTP. As a rule, the Web
     server makes the HTTP service available. In the HTTP root directory, create a subdirectory for
     publication of the documents. For HTTP access, you need read and write authorization.
  3. Set up FTP:
     The FTP ensures that subdirectories of the HTTP directory can be created and published
     documents deleted from it again. As a rule, the Web server makes the FTP service available. In
     standard installations, the FTP and the HTTP root directories on a Web server are not identical. To
     enable the FTP user to access the HTTP root directory, create a link to the HTTP directory through
     a virtual directory. For FTP access, you need read and write authorization. For logon in FTP, you
     need a user and a password. If you do not wish to restrict access authorization, use the user
     ANONYMOUS. In this case you need no password. Ensure that the FTP service is started on the
     Web server.




(C) SAP AG                                     ADM130                                              2-39
  Logon Parameters for RFC Destinations


     IMG Path: Master Data \\ Product catalog \\ Targets for document publishing
     IMG Path: Master Data Product catalog Targets for document publishing


                                                               Hostname is the name of the
                                                               computer where HTTP/FTP
                                                               server process is running

                                                               HTTP Directory is the directory
                                                               created for HTTP process

                                                               RFC destination as described

                                                               FTP username and password
                                                               as created

                                                               FTP directory is the virtual
                                                               directory created for FTP
                                                               process




       SAP AG 2002




  4. Set up the connection to the CRM system:
     To set up a connection to the CRM system, in Customer Relationship Management choose Master
     Data → Product Catalog → Set Targets for Publishing Catalog Contents and enter the following:
     - The virtual directory described in step 3 as the FTP directory.
     - The subdirectory described in step 2 as the HTTP directory.
     - The RFC destination SAPFTPA described in step 1 as the RFC destination.




(C) SAP AG                                  ADM130                                            2-40
  Internet Sales using the ITS


                                            Internet Sales Middleware


                                                            IMS/TREX




                                         Webserver                ITS           IPC


  http://p12345.wdf.sap-ag.de:1080/scripts/wgate/isab2c/!
                                                                      CRM




       SAP AG 2002




  The ITS is a possible Components that creates HTML-Pages within the middleware. The ITS should
  be used only if the Internet Sales System has been upgraded from Release 2.0. For completly new
  installations, the SAP J2EE Engine should be used. The ITS offer fewer possibilities than the SAP
  J2EE Engine (for example, no Web Auction possibilities).




(C) SAP AG                                    ADM130                                           2-41
  Connection of IPC and CRM Server



            Internet Sales Middleware

                                                                      CRM
  TCP/IP




                    Web Server
                    ITS WGate

                     ITS AGate          Readout                          RFC
                                                                      Destinations
                    IPC



                                     RFC




            SAP AG 2002




  In SAP Internet Sales, the connection between the IPC and the CRM server is indirect and occurs
  through the ITS module provider. To connect the IPC to the CRM server, set up the following RFC
  destination.
     - Set up a TCP/IP connection for the IPC Java server (parameter SAPCRM_SPC in table
       SMOFPARSFA). The RFC destination is a purely logical destination that cannot be tested in
       transaction SM59. It is determined by the ITS using data from the CRM. The ITS module
       provider loads this RFC destination during start of the service from the NT Service Manager.
       After loading, the ITS module provider can access the IPC functions through this RFC
       destination.
     - Activate Transaction SM59, choose TCP/IP connections and find the physical RFC destination
       from the previous step. In the maintenance screen of the RFC destination, the only important
       element is the entry Gateway. Here, the complete (!) IP address of your IPC server and the port
       you maintained in the IPC administrator should be listed (for example, ipcserv.my-
       company.com, 4444). It is important that you do not only enter ipcserv or something similar but
       the entire address. Do not enter the numeric IP address here.
     - The other two destinations SAPCRM_SPC_ITS and SAPCRM_SPC_SVC have no meaning for
       Internet Sales. The RFC destination SAPCRM_SPC_ITS is required for the CRM transaction
       CRMD_ORDER, to access the configuration within the IPC.
  Map logical RFC destinations to physical destinations. These destinations are available to all clients.
  Define a client-specific physical destination for each logical destination in each relevant CRM client.
  In table SMOFPARSFA, for each client and key, enter values for the parameter SPC -
  SAPCRM_SPC.




(C) SAP AG                                     ADM130                                                2-42
  Connection of IMS and CRM Server


              Internet Sales Middleware


                             ITS                                     CRM
                                             Re
                                                ad
  RFC                                              ou
                                                     t
                             IMS

                                                                        RFC
                                                                     Destinations
                      File         GW



                                                RFC
         Required
         for replication
         of Product Catalog


       SAP AG 2002




  The Index Management Service (IMS) is supplied from an initial load using transaction
  COMM_PCAT_IMS_INIT. In case of an update, a delta load can be started using transaction
  COMM_PCAT_IMS_UPD.
  Two RFC destinations are required:
    - RFC Destination IMSDEFAULT with activation type = start for indexing documents.
    - RFC Destination IMSDEFAULT_REG with activation type = registration for searching for
       documents.
    - In the SAP R/3 System, call transaction SM59. Create an RFC destination (IMSDEFAULT) of
       connection type T. Choose activating type Start. Under Start on, choose Explicit host. In the
       field Program, enter ims_server_admin.exe. Select the required option for Save as (host name
       or IP address). In the field Target host, enter the host name (and if necessary domain name) or
       the IP address of the Windows NT computer on which the IMS is installed. Choose Save. In the
       Destination menu, choose Gateway options. In the field Gateway host, enter the host name. In
       the field Gateway service, enter the gateway name sapgwXX. Choose Save.
    - Choose transaction SM59 and then Create. In the field RFC destination, enter the name
       IMSDEFAULT_REG. Choose connection type T. Choose Save. Choose activating type
       Registration. Enter the host with the registration program rfc_sapretrieval under Registration in
       the field Program ID (HOSTNAME.rfc_sapretrieval). Choose Save. In the field Gateway host,
       enter the host name (and domain name if required). In the Gateway service field, enter the name
       of the gateway sapgwXX.

  The RFC destination is a real RFC destination that can be tested in transaction SM59.




(C) SAP AG                                     ADM130                                               2-43
  Mobile Internet Sales (WAP)


                                                                         Firewall


       WAP                        HTTP




                       WAP                    Web                                     SAP
                      gateway                server                ITS               system


Mobile
phone



                      Standard
                      browser

       SAP AG 2002




  Users can log on to the SAP Internet Sales system using a WAP-enabled cellular phone or any other
  WAP-enabled frontend. This allows them to perform many purchasing activities completely
  independently of any docking station. The mobile applications are part of the standard system setup
  for SAP Internet Sales. You can either use your own WAP gateway or you can use a WAP gateway
  service from a telecommunications provider. If you have your own gateway, you can position it
  behind your firewall. This means that communication is via a dialup line as far as the WAP gateway
  (a secure connection going behind the firewall). Beyond this point, communication is via HTTP. If
  you are using a WAP gateway service, the dialup line stops outside your firewall with the less secure
  HTTP communication starting outside the firewall. You require a WAP-enabled mobile device, a
  WAP gateway and a WAP-enabled catalog that supports OCI. You must have configured your Web
  server to handle the MIME (Multipurpose Internet Mail Extensions) types required for WAP. If you
  have your own Web server, you define the MIME types using the Web server’s administration tools.
  In Microsoft IIS, you have to enter the types on the Properties page of your site on the tab card
  HTTP Headers. If you are not using your own Web server, inform the administrator or provider
  running the Web server.
  Features:
     Search for products in the Web catalog
     Shopping basket
     Ordering products
     Availability check/display
     Information on document status




(C) SAP AG                                     ADM130                                              2-44
  Mobile Internet Sales (PDA)




                                       Mobile device                         Web         SAP System
                                                                           gateway         (CRM)
                                          Built-in
                                         browser           Mobile                          Mobile
                                         (Internet          Engine                         Engine
                                         Explorer,       (Client side)                  (Server side)
                                         Opera, ...)




       SAP AG 2002




  Mobile Internet Sales on the basis of Personal Digital Assistants (PDAs) is an offline application that
  enables you to create, save, and transfer purchase orders to CRM Online using mobile devices.
  Mobile Internet Sales (PDA) enables your sales employees to enter orders without a connection to
  the SAP Internet Sales system. The mobile applications are part of the standard system setup for SAP
  Internet Sales. You require the Mobile Engine to use Mobile Internet Sales (PDA). The Mobile
  Engine is a platform-independent framework for mobile offline scenarios, that is available for all
  operating systems that support Java (JDK 1.1.4).
  Prerequisites: You have a mobile device (for example: PDA, palmtop, laptop) that supports JDK
  1.1.4, a Web browser and at least a three MB working memory, as well as the memory that is
  required for the application. You have installed the Mobile Engine.
  Features
    Catalog download
    Customer-specific prices in the Web catalog
    Product search in the Web Catalog
    Create purchase orders
    Save purchase orders
    Send and synchronize purchase orders (with CRM)
    Display the status of the purchase order
    Copy shopping baskets
  Example: Your sales employees use a PDA to enter purchase orders for their customers on-site. They
  search for the products that the customer has requested using the search function of the Web catalog
  and place them in the shopping basket. Afterwards they save the shopping basket. They send the
  saved purchase orders to the CRM system for execution the next time a connection is made with the
  system (for examle, using a mobile phone).


(C) SAP AG                                     ADM130                                               2-45
  Business System Organization


                 Business System Organization
                      Business System Organization
    Business System Organization



                                                                              SAPMarkets Internet Sales
  Business System Organization
                                               Business System Organization




                                                                              Connecting the Components


                                                                              Business System Organization
                                                                                         Business System Organization

                                                                              APO, BW, and Content Server (Optional)




                              SAP AG 2002




(C) SAP AG                                                                                    ADM130                    2-46
  Business System Organization




                         Let's browse the
                      catalogs and buy stuff!




       SAP AG 2002




(C) SAP AG                          ADM130      2-47
  Internet Sales Product Catalog

       Used for presenting products in the Web
       (Products are based on the product master data in CRM)
       Can be flexibly defined and are maintained in the CRM
       system
                 CRM




                                                       Beds


               ProductCatalog

                                                       Seats
        SAP AG 2002




   Creating a product catalog enables you to present and sell your products in the Web Shop or through
   other media. To create a product catalog, in your SAP R/3 System you must have created a material
   master and replicated this to the SAP CRM system. This product master is available to the CRM
   system. You can create a product catalog as follows.
1. Create a concept for your product catalog. This determines what kind of catalog it is.
2. Define the structure of the catalog. Create a catalog header and list a hierarchy of sections below it.
3. Characterize the products. This is important for effective presentation and fast searches in the Web
   Shop. If you want to, you can add new properties to the properties already defined in the CRM
   system to characterize your products.
4. Sort the products from the product master under the individual catalog areas. This is also an
   important criterion for orderly presentation of products in the Web Shop.
5. Activate the products to make them visible in the Web Shop.
6. To publish the catalog data in the World Wide Web, you must trigger a replication of the contents of
   the product catalog. Do this with a simple function. If you change the product catalog, trigger a
   change replication of the contents of the product catalog. You can also make changes to the already
   published contents of the catalog.
7. You can transport the product catalog data in XML format. For example, you can send the data to a
   business partner or a printing company.




(C) SAP AG                                       ADM130                                               2-48
  Different Models for Using a Product Catalog


   B2B Web Shop                                       One product catalog can be used in
                                                               more then one Web Shop

                          B2C Web Shop              B2B Web Shop


                                                                           B2C Web Shop




   For each Web Shop a separate
   product catalog can be defined
       SAP AG 2002




  Product catalogs in CRM are used for presenting products in the Web (in a Web catalog). For each
  Web Shop defined in Internet Sales, a separate product catalog can be created in the CRM system.




(C) SAP AG                                   ADM130                                             2-49
  Define a Product Catalog in a Web Shop



      Define a Web Shop for Internet Sales and
      enter product catalog information



              Shop:      Furniture           All you need for your home

                 Usage
                              B2B Scenario                       B2C Scenario


                 Product catalog

                  Catalog      4Living

                  Variant      English




       SAP AG 2002




  The Web Shop regulates the execution of sales activities for the business scenario (B2B or B2C) and
  contains just one variant of the product catalog.
  To create a Web Shop, call transaction CRM_SHOP and choose the menu tree Internet Sales →
  Maintain Web Shop.
  Your business helps you decide which business scenario to choose for your Web Shop. You can also
  use the same Web Shop for both business scenarios. In the product catalog area, you connect the
  Web Shop with a product catalog variant. With the transaction type you determine which order type
  (for example TA) to use for Internet Sales. This order type determines position type creation and
  partner determination. This is required so that an error-free order can be transported from CRM into
  the SAP R/3 System. The order numbers created in CRM must agree with the order numbers of the
  SAP R/3 System.
  You can set links from your homepage to your Web Shop with the following URLs:
     - In Business-to-Business Internet Sales:
        http://<host>/b2b/b2b/readshop.do?shopID=<shop>
        http://<Web-Server>/scripts/wgate/isab2b/!?~template=login_isab2b&shop=<shop>
     - In Business-to-Consumer Internet Sales:
        http://<host>/b2c/b2c/readshop.do?shopID=<shop>
        http://<Web-Server>/scripts/wgate/isab2c/!?~template=portal_b2c&shop=<shop>




(C) SAP AG                                    ADM130                                              2-50
  Replication of the Product Catalog

  Initial or
  Update Replication




     Internet Sales
     Middleware


               IMS

                      Catalog

         Web Server
                                                          CRM



       SAP AG 2002




  The product catalog contents replicated on the Index Server pass to the Web server and are available
  to the Internet Sales application. Multimedia objects are transferred from the product catalog to the
  Knowledge Provider content server and from there published on the Web server.
  To start initial replication, choose Master Data → Product Catalog → Initial Replication. After the
  replication, you receive a log of the results.
  If you have already released catalog areas for publication and then make changes, these changes are
  automatically stored in a working version. You can switch between the two versions, with read-only
  access to the published version. You can determine when to release the changed catalog contents for
  publication. This prevents you from inadvertently putting on the Web parts of the catalog that you
  have not yet fully maintained or given an editorial check.
  With change replication, you can replicate changed data from a chosen product catalog on the Index
  Server and publish changed documents from the Knowledge Provider Content Server to the Web
  Server. This ensures data consistency between product catalog data and the data in the Web catalog.
  You can choose a catalog and replicate its changes. The changes are marked in an internal table and
  then evaluated and processed. Changes are also recognized that are performed directly on the product
  master data.
  To start change replication, choose Master Data → Product Catalog → Update Replication.




(C) SAP AG                                    ADM130                                              2-51
  XML Export of a Product Catalog



                         XM
   Sending a                       L
   product catalog
                                            SAP
                                             SAP
                                          Business
                                           Business
                                          Connector
                                          Connector                        RFC


                                                                   CRM




       SAP AG 2002




  This function enables you to export variants of the product catalog, for example, to send to a
  business partner. The following data is recognized: catalog header (ID, short text, validity),
  categories (ID, reference category, short text, and long text), and products (ID, reference category,
  short text, long text, catalog position properties, and prices). No administrative or technical data is
  exported. At present, multimedia objects are not exported from the product catalog.
  You use the SAP Business Connector to send the mapped XML file. Mapping is the process of
  adapting the XML file to the target format of the receiver. For more information about mapping and
  the routing rules, see the integration guide that is installed with the Business Connector.
  The following sending options are available:
    - Storing the XML file in a file system by calling the SAP Business Connector
    - Send to an HTTP port by calling the SAP Business Connector
    - Send to FTP server by the routing rules of the Business Connector
    - Send to a B2B service by the routing rules of the Business Connector
    - Send to an SAP Marketplace by the routing rules of the Business Connector
  To start XML export, choose Master Data → Product Catalog → XML-Export.
  From Release 2.0C, a purchasing catalog, another type of product catalog is available. Using this
  purchasing catalog, you can export product hierarchies together with attributes and texts from the
  product catalog to requisite catalogs in XML format. To do this, create a purchasing catalog, which
  you export to the requisite catalog by XML format. A mapping of SAP's own XML schema to the
  requisite format takes place during the export.




(C) SAP AG                                      ADM130                                                2-52
  B2C Scenario: General Procedure




                              World Wide Web

        B2C Shop


                            CRM                                              SAP R/3 OLTP

                             Automatic creation of
                             a new Business Partner                            SAP R/3
                                                           Mapping             Customer
                             master record with
                             classification consumer                           Master record
  Order and
  register
  yourself                   Automatic creation of         Transfer            Sales Order
                             a new Sales Order




       SAP AG 2002




  A consumer enters your Web Shop, performs self-registration, and places a sales order.
  During self-registration, a business partner master record is created in the CRM system.
  After self-registration, the business partner master record is transferred automatically to the OLTP
  SAP R/3 System and mapped to a customer master record.
  The following description of the B2C scenario presupposes that the business partner number is the
  same in both systems. The business partner number need not be the same, but this makes the process
  easier to follow.
  In the description, the number assignment in the CRM system is internal and the number assignment
  in the OLTP SAP R/3 System is external. Other number assignments in the two systems are possible.




(C) SAP AG                                     ADM130                                             2-53
  Standard User in Service File



                                    Internet Sales Middleware

                                                              ITS Agate /
                                       Web Server
                                                            SAP J2EE Engine
                                                          Global.srvc/web.xml
                                                          ~login itsglobal
                                                          ~password ***
                                                          ~client    400
                                                          ~language DE

   SAP Internet Sales


                       CRM                                                SAP R/3 OLTP


                      Sales Order                 RFC User                  Sales Order




       SAP AG 2002




  The ITS uses the service parameters shown in the graphic to log on to the SAP R/3 System.
     - For login enter the SAP R/3 System user.
  When all parameter values are entered, the ITS logs on to the SAP System as soon as the user logs
  on, without asking the user for logon data.
  This kind of start is called implicit logon and is mainly designed for users who do not have their own
  SAP user names. For example, it is useful for Internet Sales scenarios where (initially) unknown
  Web users log on to the SAP System to order goods or services.
  In the SAP System, the different Web users cannot be distinguished, since they are all logged on
  with the same SAP user name. This also implies that they all have the same authorization.




(C) SAP AG                                     ADM130                                               2-54
  B2B Scenario: General Procedure

             B2B Web Shop




                          Only Internet users have access     World Wide Web




                           CRM                                                 SAP R/3 OLTP

         Create
         Internet user
         for contact                                         Mapping
                            Two Business Partners:                             One Customer
         person             Ordering party                                     with a maintained
                            Contact Person                                     Contact Person
   Order
                                                            Transfer
                            Automatic creation of                              Sales Order
                            a new Sales Order



       SAP AG 2002




  The scenario shown in the graphic describes how a new customer master (B2B customer) is created
  in the SAP R/3 System and is then transferred to the CRM system, where the customer master record
  is mapped to a business partner master record.
  In this case, the business partner number is the same in both systems.
  It is also possible to create the business partner in the role customer directly in the CRM system.
  In this example, the number assignment in the SAP R/3 System is internal and the number
  assignment in the CRM System is external..




(C) SAP AG                                      ADM130                                             2-55
  Flow Logic Interrogation for an Internet User




          Enter customer number
          and password:

             Cust. no.   200                      Internet Sales Middleware
             Password    **********

                                                                              ITS Agate /
                                                       Web Server
                                                                            SAP J2EE Engine
                                                                           FlowLogic:
                                                                           LOGIN_ISAB2B


   SAP Internet Sales



                 Logon to the CRM Server continues to be
                 with the User from the Global Service File
       SAP AG 2002




  All Web users with the same SAP user name log on to the CRM system through the service used. In
  the CRM system, the users cannot be distinguished at first.
  When the user of an Internet Application Component (IAC) is required to self-authenticate (for
  example, when the user finally orders products in the Web Shop), the user must enter an Internet user
  name (for example, a customer number) with the corresponding password.
  The interrogation for the Internet user is implemented at the appropriate place.




(C) SAP AG                                    ADM130                                              2-56
  Internet User: Dependence on Object Type


      SCUSTOM
      MANDT ID              NAME                ...
        400           199   Smith               ...
        400           200   Meier               ...                  SCUSTOMER
        400           201   SAP                                        (Flyer)
                                                ...
        400           202   Hendriks            ...

      BAPIUSW01
      MANDANT OBJTYPE                       OBJID PASSWORD                       Internet User
                                                                                        ...
          400          LFA1                    200        BDC3238AB8651EF                   ...
          400          KNA1                    200        AAAAGB12F4G5R6T                   ...
          400          SCUSTOMER               200        ALIK8675J11K1UZ                   ...
          400          SCUSTOMER               201        HGD234HDS134GFT                   ...
       SAP AG 2002




  Internet users are created for business objects. So there can be a customer with customer number
  200, a supplier with supplier number 200, and a applicant with applicant number 200, all in parallel.
  When creating an Internet user, the appropriate entry must exist in the master data table for the
  business object. Internet users are client-dependent.
  Since Release 2.0C, conversion of the Internet user maintenance to classical user maintenance is
  possible.
    - You can manage your Internet user using classical user maintenance (transaction code SU01).
       As a result, the development and utilization of userspecific functionality (for example,
       personalization and user specific authorization checks) are possible.
    - As it is compatible with Internet Service, you can still manage your Internet user like you did
       before by using Internet user maintenance (transaction code SU05).
    - If you already have a CRM system, you can change the Internet user maintenance in the usual
       way in Customizing. The type of user maintenance can be set in:
       SPRO --> Customizing of Customer Relationship Management under Scenarios --> Internet
       Sales --> set/adjust Internet User Administration.
    - Switch from existent SU05-User to SU01-User at login.




(C) SAP AG                                     ADM130                                               2-57
  Maintain Internet User



  Options:                                       Maintain Internet User
                                               User Edit Goto System Help

      Create
      Delete                                     ID:       200
      Rename                                     Typ:      SCUSTOMER
      Lock/unlock
      Initialize
           Password generated
           automatically
      Change password

                                               BAPIUSW01
                                                                        BFUSER_TYP
       SAP AG 2002




  To create an Internet user, call transaction SU05.
  For every business object maintained in table BFUSER_TYP, an Internet user can be created in table
  BAPIUSW01. Note that when you create an Internet user, the transaction does not automatically
  check whether the corresponding data exists in the master data table.




(C) SAP AG                                   ADM130                                             2-58
  Overview: Distribution of Data

                                 Internet Sales Middleware
                                                                                      Upload
                                    IMS           Product Catalog
                                                                                     Download

                                                                                     Upload and
                                    ITS / SAP J2EE Engine
                                                                                     Download


                                    IPC           Conditions




        CRM                                                         SAP R/3 OLTP

             Product Catalog   Business Partner                        Business Partner

                               Sales Order                             Sales Order

             Product Master                                            Product Master

                               Conditions                              Conditions



       SAP AG 2002




(C) SAP AG                                    ADM130                                           2-59
  APO, BW and Content Server (Optional)


             APO and Content Server (Optional)
                   APO and Content Server (Optional)
  APO andand Content Server (Optional)
   APO Content Server (Optional)



                                                                                          SAPMarkets Internet Sales
                                                 APO , BW and Content Server (Optional)




                                                                                          Connecting the Components


                                                                                          Business System Organization

                                                                                          APO, BW, and Content Server (Optional)
                                                                                                 APO, BW, and Content Server (Optional)




                               SAP AG 2002




(C) SAP AG                                                                                                ADM130                      2-60
  APO Availability Check




                          5
                          5                        Customer (Lille)

                                                                                  1 Enter customer order
                                                                                  1


                                                 SAP APO
                                4
                                4               Global ATP                2
                                                                          2          Check availability
                                          Confirmation for
                                               Spain
                                                          3
                                                          3
                                                 Create sales
                                                    order                 Sales (Nice)
                Plant (Madrid)




        SAP AG 2002




  Global Available To Promise (ATP) matches supply to demand on a worldwide scale, and gives your customers reliable
  delivery commitments by means of: real-time checks against the current production plan and sophisticated simulation
  methods, taking capacity constraints into account.
  This function enables the system to perform an availability check in the Internet Sales Web shop. The confirmed amounts
  are reserved in the APO system. When the sales order is saved in CRM online, the requirements are transferred to
  production or purchasing. The confirmed data and the delivery date with the available amount are shown to customers at
  item level at the following points:
      - B2B Internet Sales: When a product is transferred to the current transaction
      - B2C Internet Sales: When a purchase order is created
      This means that the availability check is only performed on request, which keeps the system’s performance as high as
      possible. The confirmed data and the delivery date with the available amount are shown to customers in the product
      details view.
  Availability Check in SAP APO, Planning in SAP R/3:
      If you carry out planning in the SAP R/3 System, you use this process to carry out availability check (ATP check) and
      transfer requirements to the SAP APO System. This process was effective until SAP CRM 2.0C. In this process the
      requirements in the SAP APO System are updated by the replicated sales order in the SAP R/3 System. In SAP CRM
      3.0 there is a new process that we highly recommend that you use.
  Availability check in the Web shop using the SAP R/3 System:
  If you do not have an APO you can execute availability checks in the Web shop using the SAP R/3 System. This is only a
  display of availability, the requests are stored during the saving of the SAP R/3 sales order. Once the sales order is
  replicated to the SAP R/3 System and saved there, it cannot be altered in CRM. There are limitations compared to APO:No
  delivery and transportation scheduling, no availability check for configurable products, no determination of alternative
  locations and products, information such as confirmed quantities and dates is not stored in database tables no way of calling
  up the information in CRM-transaction CRMD_ORDER, no temporary reservation after product is chosen (B2B),
  reservation only after order is created in SAP R/3.


(C) SAP AG                                               ADM130                                                           2-61
  APO Integration


                                                                               APO
                                         RFC
                                                                               Core
                                      Destinations
                                                                             Interface



                                                            SAP R/3 OLTP

         ATP
        Profile               CRM                          APO


                                                                            RFC
       RFC
    Destinations



                                               RFC
       SAP AG 2002




  Implementation steps:
    - Set up Application Link Enabling (ALE) connections between SAP R/3, CRM, and APO.
      Maintain parameter CRMAPOATP in CRM table SMOFPARSFA (RFC connection)
    - APO Core Interface (CIF) settings in SAP R/3 (Menu CIF):
       Target System & APO Release
    - Basic settings for integration in APO:
       Advanced Planner and Optimizer → Basic Settings → Integration → Business System Group
       → Maintain Business System Group
    - ATP Customizing in CRM. Define ATP profile and assign item category to it:
       Customer Relationship Management → Basic Functions → Integration of CRM and APO-ATP
       → Define ATP Profile
       Customer Relationship Management → Basic Functions → Integration of CRM and APO-ATP
       → Assign Item Category to ATP Profile
    - Global settings for availability check in APO:
       Demand profile
    - Create and activate CIF Integration Model in SAP R/3.
  For more information, see the installation guide.




(C) SAP AG                                ADM130                                         2-62
  BW Integration


               Operative CRM
                  System
         Planning             Execution                                               RFC
                                                                                   Destinations


        Analysis            Measurement
                                                                   SAP R/3 OLTP
              Data Warehouse
                   (BW)                                           BW                         RFC
                                          CRM




                         RFC
                      Destinations
                                                                RFC
       SAP AG 2002




  Today’s enterprises are confronted with complex processes and system landscapes. In order to
  remain competitive in rapidly changing markets against tough competition it is critical to somehow
  provide information available at different ends of a company to all employees and departments that
  need this information in order to monitor and optimize their business processes. In the center of our
  enterprise information flow scenario is the SAP Business Information Warehouse. The SAP Business
  Information Warehouse retrieves data from many of systems, serves reporting and operative
  information needs, and combines powerful technology with Business Content in order to supply a
  ready-to-go solution.
  Linkage between BW and CRM Server
     You have to set up an RFC destination between the CRM and the BW system. Then maintain the
     RFC destination with the following entry in table SMOFPARSFA:
     Key                Paramname        Paramname2 Paramval
     BWPARA1            BWRFC            BWA             <SID>CLNT<CLIENT>
     See also documentation in the Implementation Guide.

  Linkage between BW and OLTP SAP R/3 System:
    See documentation in the SAP Help Portal at the following address: http://helpportal.wdf.sap-
    ag.de:1080/. Path: New Dimension --> Business Information Warehouse --> Administrator
    Workbench --> Source System --> Data Extraction from the SAP R/3 Source Systems.




(C) SAP AG                                    ADM130                                                2-63
  Content Server

                                     Internet Sales Middleware




                                                                        Content Server
                                        Web Server
                                        ITS WGate



   SAP Internet Sales

                      Publication of the multimedia
                      objects in the content
                      server database                                        CRM




       SAP AG 2002




  To administer large numbers of documents in the product catalog, we recommend using the SAP
  Content Server. However, you can also administer documents without this installation.
  For full text and attribute searches, the components Index Management Service (IMS) and SAP R/3
  Gateway are installed. The SAP R/3 Gateway connects the SAP System via RFC. The IMS is not an
  executable application, but rather an open programming interface. The other SAP Knowledge
  Provider infrastructure components already use this interface. In order to use the Index Management
  Services, you need a locally installed search engine. The search engine must be acquired directly
  from the vendor. The SAP Knowledge Provider Content Server is accessed via HTTP. The interface
  was defined by SAP AG. If you want to integrate another Content Server into the scenario, the new
  server must fulfill the requirements of the interface specification. If data is stored on different
  servers, cache servers are used to facilitate access to the documents' contents, for example, if a
  document is to be displayed in a web browser. The cache server creates auxiliary copies of
  documents from the content server. This enables faster read access to the required documents.
  Network load is reduced, as no remote content servers need to be located. While cache servers fulfill
  a similar function to content servers, the amount of administrative work involved is small, and access
  protection is being preserved. The central document administration function in the SAP R/3 System
  ensures that out-of-date documents in the cache can no longer be accessed and that these documents
  are eventually deleted.
  For more information, see the installation and upgrade guides in SAPNet.
     - URL: http://service.sap.com/instguides. Choose Knowledge Warehouse SAP Knowledge
       Provider Server Infrastructure Components.




(C) SAP AG                                     ADM130                                              2-64
  Unit Summary



                      You are now able to:

                         Describe the SAP CRM E-Selling
                         Connect the SAPMarkets Internet Sales
                         components
                         Organize your business system for Internet sales




       SAP AG 2002




(C) SAP AG                              ADM130                              2-65
  Further Documentation



                      Additional information about Configuring
                      Internet Sales:
                         CR225 SAP IPC Admin/Technologie
                         CR800 SAP Internet Sales
                         service.sap.com/instguides
                         service.sap.com/crm




       SAP AG 2002




(C) SAP AG                              ADM130                   2-66
                                                         Introduction: Exercise

                     Unit: Configuring Internet Sales
                     Topic: RFC Connections


                     At the conclusion of this exercise, you will be able to:
                     • Describe the RFC connections that are necessary to connect the
                       different components within Internet Sales



                     You are an administrator responsible for the system configuration.




   1-1       Take a look at the connections between the CRM server and the backend system
             Do not perform any changes!
             1-1-1 Log on to the R/3 backend system. The instructor will provide you the
                   server name and system number.
                    User: back-##
                    Password: init
                    Client: 801
                    Which RFC connection is used to connect the R/3 backend system to the
                    CRM server? Which user is used for this RFC connection? Perform a
                    connection test.
                    The parameter CRM * gives you the name of the RFC destination (field
                    RFCDEST). It may be DTZ_801.
                    The user is named here. It may be CRMREMOTE.
             1-1-2 Log on to the CRM system. The instructor will provide you the server name
                   and system number.
                    User: crm-##
                    Password: init
                    Client: 801
                    Which RFC connection is used to connect the CRM server to the R/3
                    backend system? Which user is used for this connection? Perform a
                    connection test.




(C) SAP AG                                   ADM130                                         2-67
     1-2      Take a look at the RFC connections to the IPC.
             Do not perform any changes!
             1-2-1 Which RFC connection is defined for the connection from the CRM Server
                   to the IPC?
     1-3      Take a look at the IMS connection.
             Do not perform any changes!
             1-3-1 Which RFC connections are defined for the connection from the CRM
                   server to the IMS? What Type of RFC connections are these?
             1-3-2 What are these connections used for?
             1-3-3 Are these connections physical or just logical connection? Perform a
                   connection test.
             1-3-4 Which search server relations (Indexing and Searching) are dedicated to this
                   RFC connection.

     1-4      Take a look at the web server connection
             Do not perform any changes!
             1-4-1 Which RFC connections are defined for the connection from the CRM
                   server to the web server? What type of RFC connections are these?
             1-4-2 What are these connections used for.
             1-4-3 Perform a connection test.




(C) SAP AG                                  ADM130                                         2-68
                     Unit: Configuring Internet Sales
                     Topic: B2C Scenario


                     At the conclusion of this exercise, you will be able to:
                     • Explain the B2C scenario of Internet Sales and discuss the specific
                       functions



                     You want to test, if your configured scenarios are running without errors.




   2-1       Create a B2C Web shop.

             2-1-1 To access the product catalog with the browser, you have to create a Web
                   shop.
                    Choose transaction CRM_SHOP (Internet Sales → Maintain Web Shop)

                    Web shop:                  ZB2CSHOP##
                    Web shop group:            ##
                    B2C Internet Sales:        √
                    Catalog:                   PCSHOP801
                    Variant:                   VAR_EN
                    Transaction type:          ZIS
                    Sales Office:              0 50000612 (US Office Internet Sales)

                    Save your entries.

  2-2        Take a look at the visual design, procedures, and basic functionality of the B2C
             scenario for your Web shop.

             2-2-1 Enter the specified URL (http://<hostname: port>/b2c_801/admin) in your
                   Web browser and choose showcaches.jsp. Execute “Clear” for all entries.

             2-2-2 Enter the specified URL (http://<hostname: port>/b2c_801/b2c/init.do) in
                   your Web browser and call up the B2C scenario of Internet Sales.
                   Choose your Web shop ZB2CSHOP##.

                    Browse through the Catalog.
                    Search for product HT-1061 and check the results.
                    Go to the detail view to see additional information.

(C) SAP AG                                   ADM130                                             2-69
             2-2-3 Add this product to your shopping basket.
                    Your shopping basket should now contain one product.


             2-2-4 Check out your shopping basket.
                    Create a user by choosing Registration.

                    Form of address: Mr. or Mrs.

                    Last name: _____________________________________________

                    Town + postal code (5 numbers) : __________________________

                    Country: United States

                    Region: ________________________________

                    E-mail address: _____________________________________

                    Password (twice): ___________________________________

                    Save your entries.

                    Specify that you are going to pay by invoice.


                    The order data including the order number (Description) is now displayed.

                    Make a note of the order number because it is needed later on:

                    ____________________________________________________


   2-3       Check the entries in the CRM system.

             2-3-1 Log on to the appropriate CRM system.

             2-3-2 Check whether the sales order you created is in the CRM system. (The sales
                   order is also processed by the R/3 System.)
                   Choose transaction CRMD_BUS2000115 (Sales → Maintain Sales Orders)
                   Menu: Transaction → Other transaction

                    Enter the order number (Transaction no)


             2-3-3 Which user has created this data in the system? Who is this user?




(C) SAP AG                                   ADM130                                        2-70
             2-3-4 Check that the business partner master has been created in the CRM system.

                    Choose transaction CRMD_BUS2000115, go to tab General and search for Sold-
                    to party.
                    Or choose transaction BP (Master Data → Business Partner → Maintain
                    Business Partner).
                    Then choose Business Partner→ Open. Choose F4 in the Business partner field.
                    In the dialog box, enter the last name you used in exercise 1-1-2.

                    Make a note of the assigned business partner number because it is needed later on:

                    Business partner number: ______________________________


   2-4       Check the entries in the SAP R/3 system.

             2-4-1 Log on to the appropriate SAP R/3 system.

             2-4-2 Check whether the sales order you created is in the SAP R/3 system.
                    Choose transaction VA03 (Logistics→Sales and Distribution→ Sales→
                    Order→ Display)


             2-4-3 Check that the business partner master has been created in the R/3 system.
                    Choose transaction VD03 (Logistics→ Sales and Distribution→ Master
                    data → Business Partner → Customer → Display)




(C) SAP AG                                  ADM130                                          2-71
                     Unit: Configuring Internet Sales
                     Topic: B2B Scenario


                     At the conclusion of this exercise, you will be able to:
                     • Explain the B2B scenario of Internet Sales and discuss the specific
                       functions
                     • Work with Internet users


                     You want to test, if your configured scenarios are running without errors.




   3-1       Log on to the SAP R/3 system and create a customer master record for use in the
             B2B scenario.

             3-1-1 Create a customer master record:
                   Choose transaction VD01 (Logistics → Sales and Distribution → Master
                   Data → Business partners → Customer → Create → Sales and
                   Distribution)

                    Account group:           Sold-to party R/3 -->CRM
                    (not Sold-to party CRM --> R/3 or Sold-to party)
                    Sales organization:      3020
                    Distribution channel:    30
                    Division:                00

                    Maintain all the required entry fields in the customer master record. The
                    following fields are required entry fields in the general data view Address:

                    Title:             Company
                    Name:              Group_##
                    Search term 1/2:   Group_##
                    Street:            Baker Street
                    House number:      1
                    Postal code:       12345
                    City:              Boston
                    Country:           US




(C) SAP AG                                   ADM130                                           2-72
                    Create a contact person for your customer under the general data view
                    Contact persons.

                    Name:              Miller_##
                    First name:        John
                    Department:        Purchasing
                    Function:          Buyer

                    Click the Home Address and enter the home address for the customer.

                    Street:            Baker Street
                    House number:      1
                    Postal code:       12345
                    City:              Boston
                    Country:           US

                    Save the data.

   3-2       Log on to the CRM system and analyze the business partner master record created
             earlier in this unit.
             3-2-1 Take a look at the business partner master record that has been created.

                    Choose transaction BP (Master Data → Business Partner → Maintain
                    Business Partner).

                    Select the business partner you have just created.

                    Choose the Display button.

             3-2-2 Does the business partner have a relationship to another business partner?

                    Make a note of the business partner number of the contact person for your
                    customer (John Miller_##) because it is needed later on.

   3-3       To enable this contact person to login to your Web shop, create an Internet user for
             him (transaction SU05)

             Set the validity of the Internet user to one week. Save the Internet user and then
             change the password that was generated automatically to a password that is easier
             to remember.

             Make a note of the password.




(C) SAP AG                                   ADM130                                           2-73
   3-4       Create a B2B Web shop.

             3-4-1 Define your B2B Web shop. Now create a Web shop profile.
                    Choose transaction CRM_SHOP (Internet Sales → Maintain Web Shop).


                    Web shop:                         ZB2BSHOP##
                    B2B Internet Sales:               √
                    Catalog:                          PCSHOP801
                    Variant:                          VAR_EN
                    Transaction type:                 ZIS
                    Sales Office:                     0 50000612 (US Office Internet Sales)
                    Select:                           Enable Offer Creation
                    Partner function contact person: 00000015

                    Save your entries.

   3-5       Use your B2B Web shop.

             3-5-1 Enter the specified URL (http://<hostname: port>/b2b_801/admin) in your
                   Web browser and choose showcaches.jsp. Execute Clear for all entries.

             3-5-2 Enter the specified URL (http://<hostname: port>/b2b_801/b2b/init.do) in
                   your Web browser and call up the B2C scenario of Internet Sales.
                   Choose your Web shop ZB2CSHOP##.

                    Browse through the Catalog.

                    Enter the business partner number of the contact person and the password of
                    Internet user you created for the contact person. Click on Log on. Choose
                    the Web shop ZB2BSHOP##.

                    Search for product HT-1061 and check the results.

                    Go to the detail view to see additional information.


             3-5-2 Add this product to your shopping basket.
                    Your shopping basket should now contain one product.




(C) SAP AG                                   ADM130                                           2-74
             3-5-3 Check out your shopping basket.
                    The order data including the order number (Description) is now displayed.

                    Make a note of the order number, because it is needed later on:

                    ____________________________________________________


   3-6       Check the entries in the CRM system.

             3-6-1 Log on to the appropriate CRM system.

             3-6-2 Check whether the sales order you created is in the CRM system. (The sales
                   order is also processed by the SAP R/3 system.)
                    Choose transaction CRMD_BUS2000115 (CRM→ Sales Orders →
                    Maintain Sales Orders)
                    Menu: Transaction → Other transaction

                    Enter the order number (transaction no)
                    What is the status of your order?


             3-6-3 Which user has created this data in the system? Who is this user?



   3-7       Check the entries in the SAPR/3 system.

             3-7-1 Log on to the appropriate SAP R/3 system.

             3-7-2 Check whether the sales order you created is in the SAP R/3 system.
                    Choose transaction VA03 (Logistics→Sales and
                    Distribution→Sales→Order→Display)

                    Enter the order number (Transaction no).




(C) SAP AG                                   ADM130                                        2-75
                                                        Introduction: Solutions

                     Unit: Configuring Internet Sales
                     Topic: RFC Connections


                     At the conclusion of this exercise, you will be able to:
                     • Describe the RFC connections that are necessary to connect the
                       different components within Internet Sales



                     You are an administrator, who is responsible for the system
                     configuration.



   1-1       Take a look at the connections between the CRM server and the backend system
             Do not perform any changes!
             1-1-1 Log on to the SAP R/3 backend system. The instructor will provide you the
                   server name and system number.
                    User:      back-##
                    Password: init
                    Client:    801
                    Which RFC connection is used to connect the SAP R/3 backend system to
                    the CRM Server. Which user is used for this RFC connection? Perform a
                    connection test.
                    Call transaction SE16 in the SAP R/3 system and enter table
                    CRMRFCPAR and press button Table Contents.
                    Press button Execute.
                    The parameter CRM * gives you the name of the RFC-destination (field
                    RFCDEST). It may be DTZ_801.
                    Call transaction SM59. Open R/3 Connections. Search for the RFC
                    connection from table CRMRFCPAR.
                    Double click on the RFC connection.
                    The user is named here. It may be CRMREMOTE.
                    Choose the TEST CONNECTION button.




(C) SAP AG                                   ADM130                                        2-76
             1-1-2 Log on to the CRM system. The instructor will provide you the server name
                   and system number.
                    User:        crm-##
                    Password: init
                    Client:      801
                    Which RFC connection is used to connect the CRM server to the SAP R/3
                    backend system? Which user is used for this connection? Perform a
                    connection test.
                    Call transaction SMOEAC (Middleware→Administration→ Administration
                    Console) in the CRM system. Choose Sites as Object Type and click the
                    Display Objects button.
                    Choose the R/3 site (maybe CRM_DEFAULT_DESTINATION) and
                    display the Site Attributes. The name of the corresponding RFC
                    destination (field PARAMVAL) is displayed. It may be DII_801.
                    Call transaction SM59. Open R/3 Connections. Search for the RFC
                    connection.
                    Double click on the RFC Connection.
                    The user is named here. It may be CRMREMOTE.
                    Click the TEST CONNECTION button.

   1-2       Take a look at the RFC connections to the IPC
             Do not perform any hanges!
             1-2-1 Which RFC connection is defined for the connection from the CRM Server
                   to the IPC?
                    Call transaction SM59. Open TCP/IP Connections. Search for the RFC
                    connection IPC_RFC_DISPATCHER and IPC_RFC_SERVER_.

   1-3       Take a look at the IMS connection.

         Do not perform any changes!
             1-3-1 Which RFC connections are defined for the connection from the CRM
                   server to the IMS? What type of RFC connections are these?
                    Call transaction SM59 in the CRM system. Open TCP/IP Connections.
                    Search for the RFC connections IMSDEFAULT and
                    IMSDEFAULT_REG.
             1-3-2 What are these connections used for?
                    The connection IMSDEFAULT is required for the replication of
                    product catalogs.
                    The connection IMSDEFAULT_REG is required for searching
                    documents.




(C) SAP AG                                  ADM130                                       2-77
             1-3-3 Are these connections physical or just logical connection? Perform a
                   connection test.
                    They are physical connections.
                    Double click on the RFC connection.
                    Click the TEST CONNECTION button.
             1-3-4 Which search server relations (Indexing and Searching) are dedicated to this
                   RFC connection?
                    Call transaction SRMO in the CRM system. Click Tab RFC Destinations.
                    Here you can see the both search server IDs for the RFC destination
                    IMSDEFAULT with the dedicated search engine.



   1-4       Take a look at the Web server connection
             Do not perform any changes!
             1-4-1 Which RFC connections are defined for the connection from the CRM
                   server to the Web server? What type of RFC connections are these?
                    Call transaction SM59 in the CRM system. Open TCP/IP Connections.
                    Search for the RFC connection SAPFTPA and SAPHTTPA.
             1-4-2 What are these connections used for?
                    These RFC connections are needed for the replication of the MIME
                    Objects to the Web server.
             1-4-3 Perform a connection test.
                    Double click on the RFC connection.
                    Click the TEST CONNECTION button..




(C) SAP AG                                  ADM130                                         2-78
                     Unit: Configuring Internet Sales
                     Topic: B2C Scenario


                     At the conclusion of this exercise, you will be able to:
                     • Explain the B2C scenario of Internet Sales and discuss the specific
                       functions



                     You want to test, if your configured scenarios are running without errors.




   2-1       Create a B2C Web shop.

             2-1-1 To access the product catalog with the browser, you have to create a Web
                   shop.
                    Choose transaction CRM_SHOP (Internet Sales → Maintain Web Shop)
                    Choose Edit and then New entries.

                    Web shop:                  ZB2CSHOP##
                    Web shop group             ##
                    B2C Internet Sales:        √
                    Catalog:                   PCSHOP801
                    Variant:                   VAR_EN
                    Transaction type:          ZIS
                    Sales Office:              0 50000612 (US Office Internet Sales)

                    Save your entries.

  2-2        Take a look at the visual design, procedures, and basic functionality of the B2C
             scenario for your Web shop.

             2-2-1 Enter the specified URL (http://<hostname: port>/b2c_801/admin) in your
                   Web browser and choose showcaches.jsp. Execute Clear for all entries.




(C) SAP AG                                   ADM130                                             2-79
             2-2-2 Enter the specified URL (http://<hostname: port>/b2c_801/b2c/init.do) in
                   your Web browser and call up the B2C scenario of Internet Sales.
                   Choose your Web shop ZB2CSHOP##.

                    Browse through the Catalog.
                    Search for product HT-1061 and check the results.
                    Enter HT-1061 in the Find Product field and click the Go! button.

                    Go to the detail view to see additional information.
                    Click on the description.

             2-2-3 Add this product to your shopping basket.
                    Click the shopping basket icon.

                    Your shopping basket should now contain one product.
                    Choose the shop.basket button.

             2-2-4 Check out your shopping basket.
                    Choose Go to Check out
                    Create a user by choosing Registration.
                    Maintain the following values:

                    Form of Address: Mr. or Mrs.

                    Last name: _____________________________________________

                    Town + postal code (5 numbers) : __________________________

                    Country: United States

                    Region: ________________________________

                    E-mail address: _____________________________________

                    Password (twice): ___________________________________

                    Save your entries.

                    Specify that you are going to pay by invoice.
                    Select Invoice as payment method and choose more.
                    Select I accept the general terms and conditions and choose the Order
                    button.




(C) SAP AG                                   ADM130                                         2-80
                    The order data including the order number (Description) is now displayed.

                    Make a note of the order number, because it is needed later on:

                    ____________________________________________________


   2-3       Check the entries in the CRM system.

             2-3-1 Log on to the appropriate CRM system.

             2-3-2 Check whether the sales order you created is in the CRM system. (The sales
                   order is also processed by the SAP R/3 System.)
                   Choose transaction CRMD_BUS2000115 (Sales → Maintain Sales Orders)
                   Menu: Transaction → Other transaction

                    Enter the order number (Transaction no)
                    Choose the tab Status in the middle part of the right side.
                    The status should be Successfully distributed.
             2-3-3 Which user has created this data in the system? Who is this user?
                    Choose the tab Header Overview, where you can see the user who has
                    created the data.
                    It is the user, who is defined in the global service file of the ITS or in file
                    web.xml of the Java application server.

             2-3-5 Check that the business partner master has been created in the CRM system.

                    Choose transaction CRMD_BUS2000115, go to General tab and search for
                    Sold-to party.
                    Or choose transaction BP (Master Data → Business Partner → Maintain
                    Business Partner).
                    Choose Business Partner→ Open. Choose F4 in the Business partner field. In
                    the dialog box, enter the last name you used in exercise 1-1-2.

                    Make a note of the assigned business partner number because it is needed
                    later on:

                    Business partner number: ______________________________


   2-4       Check the entries in the SAP R/3 system.

             2-4-1 Log on to the appropriate SAP R/3 system.




(C) SAP AG                                   ADM130                                            2-81
             2-4-2 Check whether the sales order you created is in the SAP R/3 system.
                    Choose transaction VA03 (Logistics → Sales and Distribution → Sales →
                    Order → Display)

                    Enter the order number (Transaction no).
                    Choose SEARCH

             2-4-3 Check that the business partner master has been created in the SAP R/3
                   system.
                    Choose transaction VD03 (Logistics→ Sales and Distribution→ Master
                    Data→ Business Partners→ Customers→Display→ Sales and Distribution)
                    Enter the business partner number.
                    Choose Continue.




(C) SAP AG                                  ADM130                                          2-82
                     Unit: Configuring Internet Sales
                     Topic: B2B Scenario


                     At the conclusion of this exercise, you will be able to:
                     • Explain the B2B scenario of Internet Sales and discuss the specific
                       functions
                     • Work with Internet users


                     You want to test if your configured scenarios are running without errors.




   3-1       Log on to the SAP R/3 system and create a customer master record for use in the
             B2B scenario.

             3-1-1 Create a customer master record:
                   Choose transaction VD01 (Logistics → Sales and Distribution → Master
                   Data → Business partners → Customer → Create → Sales and
                   Distribution)

                    Account group:          Sold-to party R/3 -->CRM
                    (not Sold-to party CRM --> R/3 or Sold-to party)
                    Sales organization:     3020
                    Distribution channel:   30
                    Division:               00

                    Maintain all the required entry fields in the customer master record. The
                    following fields are required entry fields in the general data view Address:

                    Title:             Company
                    Name:              Group_##
                    Search term 1/2:   Group_##
                    Street:            Baker Street
                    House number:      1
                    Postal code:       12345
                    City:              Boston
                    Country:           US




(C) SAP AG                                   ADM130                                           2-83
                    Create a contact person for your customer under the general data view
                    Contact persons.

                    Name:              Miller_##
                    First name:        John
                    Department:        Purchasing
                    Function:          Buyer

                    Click the Home Address button and enter the home address for the
                    customer.

                    Street:            Baker Street
                    House number:      1
                    Postal code:       12345
                    City:              Boston
                    Country:           US

                    Save the Data.

   3-2       Log on to the CRM system and analyze the business partner master record created
             earlier in this unit.
             3-2-1 Take a look at the business partner master record that has been created.

                    Choose transaction BP (Master Data → Business Partner → Maintain
                    Business Partner).

                    Select the business partner you have just created.

                    Choose the Display button.

             3-2-2 Does the business partner have a relationship to another business partner?
                    Choose Goto → Relationships.

                    Make a note of the business partner number of the contact person for your
                    customer (John Miller_##) because it is needed later on.

                    Yes. The business partner has a relationship to another business
                    partner (contact person John Miller_##).




(C) SAP AG                                   ADM130                                           2-84
   3-3       To enable this contact person to log in to your Web shop, create an Internet user for
             him (transaction SU05).
             Call up transaction SU05. Enter the business partner number of the contact
             person in the ID field and BUS1006 in the Type field.
             Click on the Create icon.

             Set the validity of the Internet user to one week. Save the Internet user and then
             change the password that was generated automatically to a password that is easier
             to remember.
             Click on the Change password button and enter your new password twice.

             Make a note of the password.



   3-4       Create a B2B Web shop.

             3-4-1 Define your B2B Web shop. Now create a Web shop profile.
                    Choose transaction CRM_SHOP (Internet Sales → Maintain Web Shop).
                    Choose Edit and then New entries.


                    Web shop:                          ZB2BSHOP##
                    B2B Internet Sales:                √
                    Catalog:                           PCSHOP801
                    Variant:                           VAR_EN
                    Transaction type:                  ZIS
                    Sales Office:                      0 50000612 (US Office Internet Sales)
                    Select:                            Enable Offer Creation
                    Partner function contact person: 00000015

                    Save your entries.

   3-5       Use your B2B Web shop.

             3-5-1 Enter the specified URL (http://<hostname: port>/b2b_801/admin) in your
                   Web browser and choose showcaches.jsp. Execute Clear for all entries.




(C) SAP AG                                    ADM130                                           2-85
             3-5-2 Enter the specified URL (http://<hostname: port>/b2b_801/b2b/init.do) in
                   your Web browser and call up the B2C scenario of Internet Sales.
                   Choose your Web shop ZB2CSHOP##.

                    Browse through the Catalog.

                    Enter the business partner number of the contact person and the password of
                    Internet user you created for the contact person. Click on Log on. Choose
                    the Web shop ZB2BSHOP##.

                    Search for product HT-1061 and check the results.

                    Enter HT-1061 in the Product Search field and click the Go! button.

                    Go to the detail view to see additional information.
                    Click on the description.

             3-5-2 Add this product to your shopping basket.
                    Choose Create purchase order in the middle part of the screen and press
                    Go!.
                    Then click the shopping basket icon.

                    Your shopping basket should now contain one product.

             3-5-3 Check out your shopping basket.
                    Choose Order now.
                    The order data including the order number (Description) is now displayed.

                    Make a note of the order number because it is needed later on:

                    ____________________________________________________


   3-6       Check the entries in the CRM system.

             3-6-1 Log on to the appropriate CRM system.




(C) SAP AG                                   ADM130                                        2-86
             3-6-2 Check whether the sales order you created is in the CRM system. (The sales
                   order is also processed by the SAP R/3 system.)
                    Choose transaction CRMD_BUS2000115 (CRM→ Sales Orders →
                    Maintain Sales Orders)
                    Menu: Transaction → Other transaction

                    Enter the order number (transaction no)
                    What is the status of your order?
                    Choose the tab Status in the middle part of the right side.
                    The status should be Successfully distributed.


             3-6-3 Which user has created this data in the system? Who is this user?
                    It is the user, who is defined in the global service file of the ITS or in file
                    web.xml of the Java application server..


   3-7       Check the entries in the SAP R/3 system.

             3-7-1 Log on to the appropriate SAP R/3 system.

             3-7-2 Check whether the sales order you created is in the SAP R/3 system.
                    Choose transaction VA03 (Logistics→Sales and
                    Distribution→Sales→Order→Display)

                    Enter the order number (Transaction no).

                    Click SEARCH




(C) SAP AG                                   ADM130                                            2-87
  Configuring Enterprise Buyer


                      1. mySAP Technology              7. Interface Monitoring



                      2. Configuring Internet Sales    8. System Monitoring


                      3. Configuring Enterprise
                                                       9. Backup Scenarios
                         Buyer


                                                       Appendix Installation Scenarios
                      4. System Administration
                                                                Transaction Codes


                      5. Software Logistics



                      6. Role Management


       SAP AG 2002




(C) SAP AG                                    ADM130                                     3-1
  Configuring Enterprise Buyer



                      Contents
                         SAP Solutions for SRM
                         Connecting the Components
                         Business System Organization
                         One-Step Business and Marketplaces (Optional)


                      Objectives
                      At the end of this unit, you will be able to:
                         Describe the mySAP SRM
                         Connect the SAPMarkets Enterprise Buyer components
                         Organize your business system for Enterprise Buyer




       SAP AG 2002




(C) SAP AG                                       ADM130                       3-2
  Enterprise Buyer Scenarios


                   Enterprise Buyer Scenarios
                      Enterprise Buyer Scenarios
  Enterprise Buyer Buyer Scenarios




                                                                          Enterprise Buyer Scenarios
                                                                                       Enterprise Buyer Scenarios
    Enterprise Scenarios




                                                                          Connecting the Components
                                             Enterprise Buyer Scenarios




                                                                          Business System Organization

                                                                          One-Step Business and Marketplaces (Optional)




                            SAP AG 2002




(C) SAP AG                                                                                ADM130                          3-3
  ‘Classic’ Procurement Scenario

                                                                                    Sourcing

                                Employee

                                   • Browse through online catalogs
                                   • Create shopping basket
                                   • Place order or save basket
                                   • Check status



   • Receive product                                  Manager                • Approve or reject
   • Check invoice                                                             requirement coverage
                                                                               request

                                 Employee

                                      • Receive purchase order
                                      • Confirm goods delivery
                                        or service performed
                                      • Create invoice
                                                         Vendor


   Execution                                                                        Buying
       SAP AG 2002




  The diagram illustrates a short form of the ‘classic’ procurement scenario in the context of employee
  self-service. SAPMarkets Enterprise Buyer also offers functions for professional purchasers, such as:
     - Component planning for maintenance orders
     - A professional purchasing environment
     - Bid invitations and reverse auctions
  In addition, the software can be opened to the outside world through the use of virtual marketplaces
  (for example, for publishing public bid invitations or to find new vendors/business partners).
  SAPMarkets Enterprise Buyer is more than just an employee self-service scenario. It covers all
  aspects of Internet-based procurement.
  SAPMarkets Enterprise Buyer (SAPM EBP) is part of the solution mySAP SRM.
  Backend systems for use with SAPM EBP are enterprise resource planning (ERP) systems, such as
  SAP R/3. Multiple backend systems can be used, including non-SAP systems.
     If SAP R/3 Systems are to serve as backend systems, they must have Release 3.1 or higher.
     The backend systems provide online transaction processing (OLTP).
  To optimize performance and efficiency, the EBP system and the backend OLTP system(s) are
  connected using Business Application Programming Interfaces (BAPIs).




(C) SAP AG                                     ADM130                                                 3-4
  Procurement of Indirect Materials



  Indirect or MRO materials (Maintenance, Repair, and
  Operations) are not an integral part of the production
  process.
      Office supplies
      Machine parts
      Facilities spending
      Professional services
      Training and education
      Travel services
      ...



  Characterized by high-volume, low-dollar transactions!
       SAP AG 2002




  “Indirect procurement is fairly simple. Customers normally install procurement software that tracks
  procurement rules and hosts an internal catalog. Orders from that catalog are sent out over the
  Internet to the appropriate suppliers, and then the buyer waits for delivery. But the direct world is
  much more complicated...“
  Source: Morgan Stanley Dean Witter Internet Research, 2000




(C) SAP AG                                     ADM130                                                3-5
  Application Scenarios 1/2




                 Requisition Approval Ordering Goods    Invoice  PO/Invoice Payment Accounting
                                               Received Received Match

 Indirect
 Procurement



                      Planning   Requisition Operational PO Creation Order       Delivery and
                                             Sourcing                tracking    Follow-up

 Direct
 Procurrement




       SAP AG 2002




  Indirect Procurement is the process of purchasing non-strategic goods (for example goods not
  directly linked to the value chain). It is often called MRO (maintenance, repair, and operations)
  procurement. Requirements are generally generated ad-hoc by users. Users are all employees in an
  enterprise, not just professional buyers. Examples of commodities are office materials, work
  clothing, or IT equipment.
  Direct Procurement is the process of procuring material or services that are planned (direct material),
  as opposed to unplanned (where the requirement arises from manual input in the e-procurement
  application). A requirement for direct materials is usually planned by MRP (Material Requirements
  Planning) or APS (Advanced Planning and Scheduling) systems, and transferred to Procurement in
  the form of a requisition.




(C) SAP AG                                      ADM130                                                3-6
  Application Scenarios 2/2




                Create Plant   Search
                Maintenance    for       Ordering    Goods    Invoice       PO/Invoice Payment Accounting
                Order          Materials             Received Received      Match

 Component
 Planning


                Initiate   Initiate   Create     Submitt     Evaluate   Select
                RfQ        to Bid     Bid        Bid         Bids       Suppliers

 Request for
 Quotation


               Maintain    Create     Import Rationalize Mapping        Maintain    Search    Export
               Schema      Content

 Catalog
 Content
 Management
        SAP AG 2002




  Component Planning is the process of creating and managing plant maintenance orders with
  Enterprise Buyer. Plant Maintenance Orders will be created in the SAP R/3 PM System. The user
  has access to Enterprise Buyer catalogs and can assign the right material from the catalog to the plant
  maintenance order. After that the purchase order will be released by the SAP R/3 PM System. New
  components can be added to a plant maintenance or service order manually by using catalogs
  provided by external suppliers or from an internal catalog.
  Request for Quotation (RfQ) is the process of publishing a request for a proposal for specific goods
  or services either publicly or privately to a restricted set of potential suppliers. Suppliers can view the
  RfQ and submit responses to it. The buyer is able to view and compare the different proposals and to
  select the winning proposal.
  Catalog Content Management is the process of managing the flow of content that supports
  procurement activities. Most usually, content revolves around suppliers and product data (often in
  the form of a searchable catalog). Depending on the sophistication of the procurement processes,
  synchronization of back-end master data with on-ramp and marketplace content is required.




(C) SAP AG                                          ADM130                                               3-7
  EBP Implementation Scenarios



     Enterprise Buyer Professional can operate in different scenarios

  Implementation scenarios



          Classic


                 Extended Classic


                       Standalone


                               Decoupled



       SAP AG 2002




  The classic scenario:
  You implement Enterprise Buyer and one or more ERP systems. All Materials Management is
  mapped in the ERP system.
  The extended classic scenario:
  The purchase order is created locally within Enterprise Buyer. If the data in the shopping cart is
  insufficient to generate a complete purchase order, the data is supplemented manually within
  Enterprise Buyer before being transferred to the backend system. The purchase order in Enterprise
  Buyer is the leading purchase order. Goods receipts (confirmations) and invoices can be pre-entered
  in Enterprise Buyer.
  The decoupled scenario:
  Requirement coverage requests for materials and services are directly processed further, and
  purchase orders are placed, in the Enterprise Buyer system. The follow-on documents for the
  purchase orders are also created in the Enterprise Buyer system (confirmation, goods receipt, service
  entry, and invoice).
  You can continue to procure production materials and services using the Materials Management
  functions in your ERP system.
  The standalone scenario:
  You have no Materials Management in your ERP system and are using the Materials Management
  functions in the Enterprise Buyer system for all procurement.




(C) SAP AG                                     ADM130                                               3-8
  ‘Classic’ Scenario


                                 Enterprise Buyer                    Backend-System


                                       Shopping cart
                                          created



                                                                        Release 3.1
                                     Workflow approval
                                                                        Releases n.n


                                       Goods receipt                      Non-SAP
                                     (vendor, employee)                   backend
                                                                           system


                                        Invoicing/
                                     workflow approval



                                                                      Follow-on Documents
                                                                     (confirmation, invoice)
                                                                    are always posted in the
                             Global Business
                                 Partner
                                                Product Master   corresponding backend system
       SAP AG 2002




  You implement Enterprise Buyer and one or more Backend systems (SAP or Non-SAP). All
  Materials Management is mapped in the ERP system. All materials management documents (such as
  purchase orders, goods receipts, service entry sheets, and invoices) exist in the Backend system.




(C) SAP AG                                     ADM130                                           3-9
  ‘Extended Classic’ Scenario


                                   Enterprise Buyer                    Backend-System



                                        Shopping cart
                                           created




                                       Purchase Order                     Purchase Order

  Message to vendor
  XML, e-mail, fax
                                         Confirmation                      Goods Receipt



                                            Invoice                            Invoice

                                                                        Follow-on Documents
                                                                       (confirmation, invoice)
                                                                      are always posted in the
                              Global Business
                                  Partner
                                                  Product Master   corresponding backend system
       SAP AG 2002




  This scenario is an extension of the classic scenario, which continues to exist. The complete
  procurement process takes place locally. Communication between Enterprise Buyer and the backend
  system is via RFC. The purchase order is created locally in Enterprise Buyer.
  If the data in the shopping cart is insufficient to generate a complete purchase order, the data is
  supplemented manually within Enterprise Buyer before being transferred to the backend system. The
  purchase order in Enterprise Buyer is the leading purchase order. The plant is the criterion used for
  splitting shopping cart items into different purchase orders. This is because the purchasing
  organization is determined in the backend system on the basis of the plant. Goods receipts
  (confirmations) and invoices can be pre-entered in Enterprise Buyer.
  The following take place in the Enterprise Buyer system:
  Search for source of supply, pricing, tax determination, and commitments are updated in the backend
  system, account assignment and budget check are performed against the backend system.
  Data for the Business Information Warehouse is updated partly from Enterprise Buyer and partly
  from the backend system. Purchase order data is updated from the Enterprise Buyer; goods receipt
  and invoice data is updated from the backend system.
  This process does not support purchase orders based on limit shopping carts or services, or
  procurement card functions. These require a local invoice.




(C) SAP AG                                       ADM130                                            3-10
  ‘Standalone’ Scenario


                                  Enterprise Buyer                         Backend-System



                                        Shopping cart
                                           created



                                      Workflow approval                      Release 3.1
                                                            Only checks      Releases n.n
                                                            and posts in
  Message to vendor                                            FI/CO          Non-SAP
                                     Purchase order -
  XML, e-mail, fax                  complete/incomplete                       backend
                                                                               system

                                        Goods receipt
                                      (vendor, employee)



                                         Invoicing -
                                      Workflow approval


                              Global Business
                                                 Product Master
                                  Partner
       SAP AG 2002




  The customer does not have a productive Materials Management system and wants to handle the
  entire process locally within the Enterprise Buyer, integrating only to an accounting system.
  Accounting processes (including FI, CO, and AM) must still be handled by a backend system. All
  validations and approvals are handled directly within Enterprise Buyer rather than in a backend
  system. This is possible by incorporating Material Management functions into the application that
  will have its own product master. Migration tools are provided to bring Material Master data from
  SAP backend systems into the application product master.
  A shopping cart or requirement coverage request (RCR) is created locally and can, depending on
  how the system has been configured, be further processed locally to create a purchase order. An
  added benefit is increased performance due to the fact that fewer RFC calls are necessary to the
  backend system.




(C) SAP AG                                      ADM130                                           3-11
  ‘Decoupled’ Scenario


                                  Enterprise Buyer                     Backend-System



                                        Shopping cart
                                           created



                                      Workflow approval                   Release 3.1
                                                                          Releases n.n

  Message to vendor                  Purchase order -                       Non-SAP
  XML, e-mail, fax                  complete/incomplete                     backend
                                                                             system

                                        Goods receipt
                                      (vendor, employee)



                                         Invoicing -                  The follow-on documents
                                      Workflow approval
                                                                     (confirmation, invoice) are
                                                                    alwaysposted in the system
                              Global Business
                                                                         wherethe purchase
                                                 Product Master            order is posted
                                  Partner
       SAP AG 2002




  You have a productive Materials Management backend system, but want to handle parts of the
  process locally and other parts within the Materials Management system. This means that specific
  shopping basket items create Purchase Orders or requisitions with all follow-on processes in the
  backend Materials Management, while others are processed locally.
  For example, office supplies could be processed locally while all items for plant maintenance goods
  are processed in the backend system This makes sense if you have already defined your
  communication interface to your supplier (for example, EDI-Interface).
  The requirement requests for non-production materials and services are processed directly in the
  EBP System, where the purchase orders are also created. If data for the purchase orders is missing,
  you use the Materials Management functions to complete the purchase orders. The follow-on
  documents (general receipt and service confirmation and invoice) are also created in the EBP system.
  Using the Materials Management functions in your ERP system, you continue to purchase
  production goods and services.
  A further advantage of this scenario is that you can continue to use existing communications
  interfaces in the backend system and to generate the purchase orders from there.
  Where there are several backend systems, you can define how backend systems are determined using
  Customizing.




(C) SAP AG                                      ADM130                                             3-12
  Technical Components

     Software         Scenario
     Component
                      Indirect    Direct              Component       RfQ    Catalog Content
                      Procurement Procurement         Planing                Management
     EBP 3.0          X               X               X               X      X

     SAP ITS          X               X               X               X      X
     4.6D/6.10
     SAP BC           (X)             (X)             (X)             (X)    (X)

     Catalog +        (X)             (X)             (X)             (X)    (X)
     Servlet
     Engine
     SAP APO          -               (X)             -               -      -

     SAP BW           (X)             (X)             (X)             (X)    (X)

     SAP R/3          (X)             (X)             (X)             -      -
     OLTP



       SAP AG 2002




  This diagram gives an overview of mySAP SRM and the components of its scenarios. Please note
  that there are software requirements for each component which are not explicitly mentioned in this
  documentation. They are documented in the relevant installation guides. All related implementation
  guides can be obtained from service.sap.com/instguides.




(C) SAP AG                                    ADM130                                             3-13
  Business-Warehouse-Based Reporting 1/2


                                                                                aggregated data
    SAP Business Information                                                    infocubes
    Warehouse offers efficient
    reports and an integrated sight
    on business processes




       Enterprise Buyer for operative                          other ERP-systems for backend-
       procurement processes                                   processes: Finance, ...




       SAP AG 2002




  In addition to strategic sourcing a major component of professional purchasing is the analysis of your
  purchasing/procurement activities to support strategic decision-making.
  The tool for these purposes in connection with SAP components is SAP Business Information
  Warehouse.
  SAP BW is an end-to-end data warehouse of internal and external company-specific data that is
  summarized to give you effective, real-time decision support information.
  SAP BW extracts data from processes throughout your enterprise and converts the data into
  meaningful information.
  SAP BW is a ready to go solution, preconfigured for mySAP.com environment. At the same time,
  additional non-SAP data sources can be included with ease (for example, from archives, legacy
  systems, or external providers).




(C) SAP AG                                     ADM130                                              3-14
  Business-Warehouse-Based Reporting 2/2

  All Reports are delivered as
  MS Excel queries...




                 ...and as HTML queries
       SAP AG 2002




  SAP Business Information Warehouse is used for both operational and strategic analysis. SAP
  delivers comprehensive Enterprise Buyer-specific reports and InfoCubes that can be extended
  individually.
  Through pre-delivered data extractors, queries, and business content (metadata) covering all
  application areas, SAP BW has the fastest implementation times, greatly contributing to its lowest
  total cost of ownership
  BW provides the reporting environment that can answer such questions as:
     - What materials are we purchasing most often, and how many suppliers do I have for any
        particular material?
     - Which suppliers are the best for on-time delivery, order fulfillment, unit price, and so one?
     - Which suppliers are the most reliable for order quotation vs. goods receipt vs. invoice
        verification?
     - Which suppliers provide the most attractive quotations?
     - Where in my global organization can I reduce waste by streamlining my MRO purchases?
     - How much are my internal organizations (for example, cost centers) spending on MRO items?
        And what items are they purchasing?
     - What are my individual employees purchasing, and how much are they spending?
     - How are our purchasing patterns changing over time? Are we spending more or less, are we
        buying different items, and are we buying from the same or different suppliers?




(C) SAP AG                                    ADM130                                             3-15
  Technical Components in System Context

   Frontend             Internet Middleware        Application   Backend
                                                   Middleware


     Internet
      Vendor
                         Enterprise Buyer
      Vendor's
     Web Server
                                                      EBP        R/3 OLTP
                       Web Server      ITS    BC
     Internet
     Customer         Catalog Server


                                                                   BW

     Internet
     Employee



                                                                   APO
     Intranet
     Employee

       SAP AG 2002




(C) SAP AG                               ADM130                             3-16
  Connecting the Components


                  Connecting the Components
  Connecting the components the Components
    Connecting the Components



                                                                    Enterprise Buyer Scenarios
                     Connecting




                                                                    Connecting the Components
                                        Connecting the Components




                                                                                Connecting the Components

                                                                    Business System Organization

                                                                    One-Step Business and Marketplaces (Optional)




                          SAP AG 2002




(C) SAP AG                                                                          ADM130                          3-17
  IMG for EBP Implementation




                      Enterprise Buyer Professional Edition
                           Implementation Guidelines


                                                             ...
                                 Subitems



                                             Documentation



                                                             Activity


       SAP AG 2002




  To introduce the mySAP SRM, use the Implementation Guide (IMG). It tells you how to perform the
  necessary settings.
  To access the IMG, call transaction SPRO. You can find the settings presented in this unit under the
  entry Enterprise Buyer Professional Edition.
  Customizing comprises settings from various theme areas. This unit focuses on the area of Basis
  administration.




(C) SAP AG                                      ADM130                                            3-18
  Connecting the Backend Systems


                                                                                    RFC
                                                              SAP R/3 OLTP       Destinations




        RFC
                                     EBP                                           Logical
     Destinations
                                                                                   Systems

                                                RFC
                                                              ERP                   RFC
       Logical                                                (other system)
                                                                                 Connections
       Systems




                                                                                   Logical
                                                                                   Systems

       SAP AG 2002




  Basic settings:
     Create RFC destinations on the EBP system (transaction SM59):
     - One for each backend system (in an SAP R/3 System, for each client used)
     - One locally on the EBP system, that points to the EBP system
     Create EBP component RFC user <SU01> in the backend SAP R/3 System:
     - Create the remote logon user for the EBP system: user type background user or system (as of
         Release 4.6x) with authorization SAP_ALL and SAP_NEW.
     Create logical systems (transaction BD54) and allocate clients (transaction SCC4):
     - One for each backend system (in an SAP R/3 System, for each client used)
     - One locally on the EBP system, that points to the EBP system
  Note that RFC destination and logical system have the same name (with the same capitalization).
  The SAP convention is <SID>CLNT<client> (for example, T42CLNT400).
  It is also possible to establish the connection to Non-SAP Systems as Backend with SAP Business
  Connector.




(C) SAP AG                                    ADM130                                             3-19
  Business Connector Integration



                                                                                   Listener



                                                                                   SAP
                                                                                 Business
        RFC                                                                      Connector
                                      EBP                                          optional
     Destinations
                                                          RFC




       SAP AG 2002




  To set up the connection between the Business Connector and EBP system, proceed as follows:
  1. On EBP system set up TCP/IP connections to the Business Connector using transaction SM59.
  Define one connection for each document type you wish to transfer. Name the connections as shown
  in table). If you have opted for implementation, with one Business Connector for several clients, you
  have to choose unique client-dependent connection names (naming convention:
  <CLIENTNUMBER>EBPBC<NAME>). You define only one default connection for all documents
  to be transferred from EBP. Any of these special cases require changes to the shipped RFC
  destination Customizing settings.
  2. Define an SAP Server linked to EBP system using the BC Server Administrator. Name this server
  EBP. The user that is used by the Business Connector to log on to EBP must have the necessary
  permissions and, for security reasons, have the type system user.
  3. For every RFC destination you define add one RFC listener to the EBP. The listeners and
  destinations must have identical names.
  4. Customize RFC destination settings on EBP system. Choose the shipped settings by using the
  standard implementation (one Business Connector for one client). In the other above-mentioned
  special case, configure the predefined RFC destinations. (IMG: Enterprise Buyer professional
  edition - Technical Basic Settings ->Assign RFC Destinations Dependent on Scenarios). Change
  the RFC destination names to the names of destinations (and the listeners) you have chosen above. If
  you want to use the default scenario (one destination and one listener for all documents), you have to
  define the default destination and delete all the other destinations.
  For details, refer to the SAP Business Connector Integration Guide, Configuring an RFC Listener in
  SAP Business Connector Server.




(C) SAP AG                                     ADM130                                               3-20
  Assign RFC Destinations dependent on Scenario



                  Scenario <->
                     RFC                                       EBP
                  Destinations




       SAP AG 2002




  In IMG, choose Enterprise Buyer Professional Edition → Technical Basic settings → Assign RFC
  Destinations dependent on Scenario
    1. Under Enterprise Buyer scenario choose a scenario.

    2. Under RFC destination choose an RFC destination that has already been defined.
  In this activity, you assign existing RFC destinations to Enterprise Buyer scenarios. The assignment
  affects:
       • XML communication with the SAP Business Connector

       • Connection of the SAP Document Converter to Enterprise Buyer

  The standard destinations are delivered. You only change them if you want to use other destinations
  (for example, if you require client-specific RFC destinations).

  Standard settings: The scenario entries are for the connection of the SAP Business Connector to
  Enterprise Buyer, with the following exception: The Printconversion entry is for connection of the
  SAP Document Converter and the PostScript format of attachments for purchase orders.




(C) SAP AG                                     ADM130                                              3-21
  Definition of the Web Server




        Enterprise Buyer Middleware



                                                                                 TWPURLSVR


       WebServer
                                  ITS AGate
       ITS WGate

                                                                EBP

                                  Reference




       SAP AG 2002




  In order that the URLs for the various transactions such as BBPPU99 (Shop [in earlier releases
  Create Shopping Basket]) can be generated correctly, you have to make some entries in table view
  TWPURLSVR.(transaction SM30):
     - LogSystem: Name of the Enterprise Buyer logical system, for example AX4CLNT000.
     - Web server: Domain of the ITS server including the port, for example pgaec.wdf.sap-
       ag.de:1080.
     - (Web server) Log: HTTP or HTTPS, for example.




(C) SAP AG                                    ADM130                                            3-22
  Logon Screen in EBP




    EBP Logon
                                                Internet Sales Middelware



                                                    WebServer                 ITS AGate
                                                    ITS WGate
                                                                        Global.srvc
                                                                        ~login        x76its
                                                                        ~password     ***
                                                                        ~client       400
                                                                        ~language     DE


       SAP AG 2002




  The ITS user in the Enterprise Buyer system must be created as a dialog user. Maintain the ITS user
  in the service file global.srvc through ITS Admin or Studio. First, maintain the ITS user in Enterprise
  Buyer as user type Dialog. Assign this user the roles SAP_EC_BBP_CREATEUSER and
  SAP_EC_BBP_CREATEVENDOR. In global.srvc add logon name and password. After a successful
  logon, you continue to work with your own user in the system. Using transaction SE80, define the
  client of the component system in the ~client parameter in the service files BBPstart, BBPvendor,
  BBPat3, BBPat04, and BBPmainnew. If the client is not defined in these service files, add parameter
  ~client=XXX to the Enterprise Buyer start URL.
  If you do not want to define the ITS dialog user (login and password) in the ITS global service files,
  you have to define it in the following service files: BBPat03, BBPat04, and BBPmainnew. You
  maintain the login information using the ITS admin instance or SAP@Web Studio. If you define the
  user using Notepad or transaction SE80, the password is not encrypted. Some companies may regard
  this as a security problem, since the user is a dialog user.




(C) SAP AG                                     ADM130                                               3-23
  Catalog Access




           Catalog 1
        Catalog 1


                                                                                      Define
                                                                                     Catalogs



                        Open Catalog
                          Interface
                                                                EBP

        Catalog n




        SAP AG 2002




  In the Enterprise Buyer system, define all your catalogs and enter the data required to address each
  catalog (this data is the call structure). As this data is catalog specific, you must get in touch with the
  supplier of the catalog and request the data.
  To connect to Enterprise Buyer, the catalog must support the SAP open catalog interface (OCI). For
  a description of OCI and a list of suppliers, look in the SAP Service Marketplace under alias /spp.
  If you plan to implement another logic for the transfer of catalog data in your Enterprise Buyer
  system, you can use the Business Addon EBP_CATALOG_TRANSFER.




(C) SAP AG                                       ADM130                                                  3-24
  Catalog Scenarios Supported by Enterprise
  Buyer
    1                                                                             2
         External supplier owns catalog                                                 Content broker/Marketplace

     • Supplier updates                                                           • Multi-supplier catalog
       catalogs         C                                                         • Maintained and hosted by
                                                                                    external catalog broker
                        C                                           Company boundary                                                  C
                            Ac
                               c   es
                                        sv
                  C                          ia
                                                Int                                                                        C              C
                                                    er                                                                           C
                                                         ne
                                                            t       Procurement                                                  DB
                                                                     world-wide
                                                                                                                             C
                                                                                                                 et
                                                                                                             er n                         C
                                                                                                          Int
                                                                                                     v ia
                                                                                                 s
                                                                                          c   es
                                                                                       Ac

    3
          Catalog hosted by
          company (intranet)
                                                                         C            DB                      4
     • Purchasing department
                                                                             C
                                                                     C                                                Internal catalog
       maintains catalog
     • Content is provided   C
       by suppliers                                                                                            • Purchasing from own
                                                          C                                                      stock (within company
                                                                                                                 boundary)
                                                                C
         SAP AG 2002




  One of the main advantages of using Internet-based procurement software is the integration with
  online catalogs, enabling easy location of products.
  It is generally possible to allow specific employees specific views on particular catalogs (for
  example, access restricted to product category ‚office materials’).
  SAP supplies a catalog management tool (Emerge from Requisite Technology).
  SAP Enterprise Buyer supports the following catalog scenarios:
     1: You access the vendor catalog directly from SAP Enterprise Buyer via the Internet. The vendor
     is responsible for setting up the catalog and maintaining its contents.
     2: Using the Internet, the purchaser accesses a catalog that combines the offerings of several
     suppliers. The catalog broker is responsible for setting up the catalog and maintaining its contents.
     Catalogs (for example, industry-specific catalogs) can be located on marketplaces.
     3: The catalog is within the firewall. The company-specific catalog combines the offerings of
     several vendors. The catalog may be updated, for example, by the vendor accessing his part of the
     catalog.
     4: Internal order processing is dealt with using SAP EBP. A catalog also uses internal master data.




(C) SAP AG                                                           ADM130                                                               3-25
  Certified catalogs for E-Procurement


   Catalogs and Content
   Catalogs and Content                 Supplier with own
                                        Supplier with own
   Provider
   Provider                             catalog
                                        catalog
       Enigma                              Dell
       Innop (ZicZac)                      Grainger
       jCatalog                            Abele
       Wessendorf                          MicroWarehouse
       Surplex.com                         (Inmac)

       Tec 2b                              HP

       Requisite                           Compaq

       Intershop                           Hahn & Kolb

       Heiler                              Kistenpfennig

       Cacontent                           Kaiser + Kraft

       IPS                                 Transtec

       Poet                                Bechtle

       Wallmedien (catone)                 Vodafone

       Labworld-online
       SAP AG 2002




(C) SAP AG                     ADM130                       3-26
  Define Catalogs




       SAP AG 2002




  In IMG, choose Enterprise Buyer Professional Edition → Master Data → Define catalogs.
  For each catalog, maintain at least the following entries:
     - CatalogID: Unique indicator for each available catalog. The description is shown in the F4 help
       for the catalogs.
     - Description: The user sees this short text in the list of available catalogs.
     - Business Partner: Unique indicator for a business partner in the SAP System.
     - Purchasing Organization: Responsible purchasing organization. If the catalog content comes
       from only one vendor, enter the vendor and the purchasing organization that is responsible for
       this vendor. Then positions that are taken over from the catalog into the shopping basket are
       always allocated to this vendor.
  There is a call structure for each catalog, with entries:
     - Parameter name
     - Value
     - Field type (for example, URL, SAP field, fixed value, and return URL)
     - HOOK_URL remains empty (it is generated dynamically)
  Support of Java catalog UI: The catalog can be opened within the application itself so that employees
  do not have to view the catalog in a separate window unless they want to. If catalogs are to be
  opened in the application itself, maintain the Internal Call Structure. If catalogs are to be opened in a
  separate window, maintain the Catalog Application Call Structure.




(C) SAP AG                                      ADM130                                                3-27
  Attribute Maintenance in the Organizational Units



         Root Organizational Unit              Example:
                                               Boardof Directors

                                               Examples:
             Organizational Unit (O)           Departments, groups,
                                               or project teams

                  Attributes for EBP
                         BSA                   Examples: Company,              Organizational
                         BUK                   code, plant, catalogs,          Structure
                         CAT                   document type
                         WRK
                           .
                            .
                            .
                            .


                      Users (US)               Example: Employees
                                               and managers




       SAP AG 2002




  In the attributes, maintain the catalog ID (attribute CAT) for the organizational units that can order
  from this catalog (transaction PPOMA_BBP). Any user in this organizational structure inherits the
  attribute and can access the catalog.
  A user with the group role SAP_BBP_STAL_ADMINISTRATOR is authorized to create new users
  and to place them in an organizational structure. This occurs only in the Web.
  The organizational structure forms the hierarchy in which the various organizational units of an
  enterprise are arranged according to tasks and function.
  A root organizational unit is the unit at the highest level of an organizational structure. When you
  build up organizational structures, you build them from the root organizational unit down. You start
  by creating the root organizational unit.
  An organizational unit represents any type of organizational entity found within a company, for
  example, subsidiaries, divisions, departments, or special project teams. Organizational units and
  other objects make up organizational plans.
  Each user attribute represents a value that is stored under a particular name within the organizational
  structure.




(C) SAP AG                                      ADM130                                               3-28
  Catalog Callup


                                                                            Data
                                                                            base
      Catalog

                                                         ITS                   EBP



                      2
                      2                 1
                                        1                                                The XML data is
     Request with                    URL + parameters                                  passed to the SAP
    URL + parameters                                                                  Business Connector
                                                            5
                                                            5                        for mapping purposes
                             3
                             3       HTML form containing
    HTML form containing                the (XML) data
                                                                           SAP
       the (XML) data                                                    Business
                                                                         Connector
                                                                          optional



                 Internet
                 Browser
                                 4
                                 4
  Employee                  submit

       SAP AG 2002




  When a user selects a catalog and chooses Go, the purchasing application redirects the browser to the
  catalog with the parameters described in the outbound section. The user then sees the homepage of
  the catalog in his or her browser.
  The catalog generates an HTML form that is sent to the browser. If the user chooses Submit, the
  form is sent to the ITS. The user then sees the Enterprise Buyer application in his or her browser.
  Since the Enterprise Buyer Release 2.0 the interface can also process XML input. To enable it to do
  so, you must install the SAP Business Connector (BC) on the receiving side. BC is used as a
  mapping tool for Enterprise Buyer.
  If XML is used, the XML data is transferred to the browser in HTML form in an input field with the
  name ~xmlDocument. The content of the generated XML file is expected to be bound to the input
  field ~xmlDocument as a string encoded in base 64. The encoding can be done directly on the server
  side or on the client side.




(C) SAP AG                                     ADM130                                               3-29
  Content Management

            Content                       Content                           Content              Catalog
            Import                       Staging &                          Export               System
                                          Release
                                                                           Business
                                                                           Connector
                            Enterprise
                              Buyer       Product Catalog
                                             Definition
               Business
               Connector                                                               Content
                                                   Staging                   XML
                            Import
                                                   Cockpit                  Mapping
                            Cockpit

                              XML-
                 XML                                  Category
                              DB
                Syntax
  Content       Check
                                           Product
                XML           Rules                      Condition
               Mapping
                              Filter          Duplicate check;
                             Mapping        Correction; Approval
                             Preview



                                                Master Data

                                           SAP         SAP         SAP
                                         Backend     Backend     Backend

         SAP AG 2002




  Using the content load workbench, system administrators can import external catalogs and map the
  external category and attribute structures to the internal structures. Before the data can be passed to
  the product workbench, the mapping of the imported product data must have been completed.

  External product catalog data or product catalogs are uploaded into the Enterprise Buyer system
  using an XML-based interface. The incoming XML documents are processed using the SAP
  Business Connector (SAP BC). Supported XML schemata are mapped to the EBP/CRM schema.
  The following standards are supported: BMEcat 1.01, xCBL 3.0, eCx XML 2.0. After mapping, the
  data is transferred via RFC (remote function call) to the Enterprise Buyer system.

  Prerequisites:
  You have been assigned the role SAP_EC_BBP_CONTENT_MANAGER
  You have defined the number ranges for materials and services using internal number assignment.
  You have defined the standard product schemata you want to us (for example, UN/SPSC, RosettaNet
  or eClass).
  You have specified whether you want imports without errors to be transferred automatically to the
  product master, whether you want to transfer attachments to the product master, how you want to
  handle missing vendor and attribute mapping
  You have specified the product hierarchies to which you want to be able to map product categories.
  You have defined whether you want products to be saved as active or inactive when a catalog load is
  imported.




(C) SAP AG                                           ADM130                                                3-30
  Mobile Procurement Scenario

      Analyze                                                                       Sourcing

                               Employee

                                  • Search in online-catalog
                                  • Create shopping cart




      • Cost center
       analyze/                    Purchaser/          Manager               • Inbox
                                                                             • Approve or refuse
       reports                     Manager                                    requisition




                                                • Ask for status
                                                         Employee


      Execution                                                                     Buying
       SAP AG 2002




  A short form of the ‘classic’ procurement scenario in the context of employee self-service.
  The vendor can also be involved. After receiving the goods, the vendor posts the invoice. The
  invoice can be checked and released. The invoice is then passed directly to the FI backbone.




(C) SAP AG                                     ADM130                                              3-31
  Mobile Scenarios



                WAP                       HTTP
  Mobile                  WAP
  Phone                  Gateway



                                          online/
           Browser/                       offline
             Java                                       Internet
            Plug-In
                                                      Transaction
                                                         Server
                                                                               Enterprise Buyer




               Web                        HTTP
            browser -
        ‘classic’ scenario




       SAP AG 2002




  Users can log on to the Enterprise Buyer system using a WAP-enabled cellular phone or any other
  WAP-enabled front end. This allows them to perform many procurement tasks completely
  independently of any docking station. These mobile applications are part of the standard system
  setup for Enterprise Buyer professional edition. Managers can approve shopping carts while on
  business trips far away from the office. The start URL for the mobile scenarios is:
  http://<host>.<domain>:<port>/scripts/wgate/wapbbpstart/!?~language=<language>
  You can either use your own WAP gateway or you can use a WAP gateway service from a
  telecommunications provider. If you have your own gateway, you can position it behind your
  firewall. System administrators can access important user administration functions via a mobile
  telephone with WAP capability, for example when they are temporarily away from their system
  environment. These functions exist to support users that have system logon and authorization
  problems (forgotten password, user locked due to excessive incorrect passwords entered, user
  validity period expired). The functions include displaying user data, locking and unlocking users,
  resetting passwords and creating and changing users. Mobile user management is not intended as a
  replacement for the Web application maintaining users. Users that want to carry out user
  administration via a mobile telephone have to be assigned either the system administrator role
  (SAP_EC_BBP_ADMINISTRATOR) or a role containing the MiniApp WAPBBPUSER.
  The Mobile Engine provides a platform-independent framework for the three new offline mobile
  scenarios for Enterprise Buyer. Mobile devices such as palmtop computers, Personal Digital
  Assistants (PDAs), and laptops use the Mobile Engine to run business applications offline. The three
  new scenarios are shop, inbox, and plant maintenance. Once the user has maintained the necessary
  data in the mobile device, it can be synchronized with any SAP system via a standard Internet
  connection. A mobile device is required with any Web browser and, operating system with Java VM
  1.1.4 and ~3 MB memory.


(C) SAP AG                                    ADM130                                              3-32
  Business System Organization


                 Business System Organization
                      Business System Organization
    Business System Organization



                                                                              Enterprise Buyer Scenarios
  Business System Organization
                                               Business System Organization




                                                                              Connecting the Components


                                                                              Business System Organization
                                                                                         Business System Organization

                                                                              One-Step Business and Marketplaces (Optional)




                              SAP AG 2002




(C) SAP AG                                                                                    ADM130                          3-33
  Prerequisites for the Initial Download


                      Report EBP_PRODUCT_SETTINGS_MW




                                             automatic

      SITE Definition                                                                    CRMRFCPAR
           and                                                                           CRMCONSUM
      SMOFPARSFA                                                                         (former table:
                                                                                        CRMPAROLTP)




                              EBP                                    SAP R/3 OLTP



       SAP AG 2002




  In IMG, choose Enterprise Buyer Professional Edition → Master Data → Products →
  deactivate/reactivate CRM specific data in Enterprise Buyer System.
  If only EBP is used (not EBP and CRM), use this program to set up the EBP system for the transfer
  of materials from SAP R/3 to the product master in the EBP system. Besides adapting the necessary
  middleware settings automatically, this program also regenerates the corresponding code (runtime:
  30 to 60 minutes). The program sets all business objects, except MATERIAL, to inactive in
  middleware object management and sets all customizing objects, except DNL_CUST_PROD0 and
  DNL_CUST_PROD1 to inactive in middleware object management. Furthermore it sets all
  condition objects to inactive in middleware object management and flags the following tables as
  inactive in middleware object management for the object MATERIAL: MARC, MLAN, MVKE,
  STXH, STXL. In Addition it flags the following tables as inactive in middleware object management
  for the customizing object DNL_CUST_PROD1: T179, T179T and sets the parameter in table
  SMOFPARSFA. That mean in detail: changes the parameter CRMGENERAL, LOG_LEVEL to T;
  changes the parameter FLOW, FLOWTRACE_ACTIVE to X; changes the parameter
  DEVSYSTEM, DEVSYSTEM to X; changes the parameter R3A_COMMON,
  CRM_VERSION_ACTIVE, SYNCHRONOUS_CALL, 1.2 to X . In table SAPFAPPL the EBP
  application will be set to active and the CRM application to inactive. It deactivates the field Division
  in the product master. This program also allows to specify whether you are using the service product.
  Use SMOEAC to specifies the SAP R/3 backend systems. If you later want to use CRM in addition
  to EBP, you can use this program to undo these settings.
  To specify the Enterprise Buyer system for the delta load log on to the SAP R/3 backend system and
  verify and, if necessary, add entries in tables CRMCONSUM and CRMRFCPAR as described in
  SAP Note 337703. To ensure correct filtering of the object MATERIAL, you must insert an entry
  into table CRMPAROLTP :CRM_FILTERING_ACTIVE, MATERIAL, User: CRM, Parval1 - X.


(C) SAP AG                                      ADM130                                               3-34
  Initial Load of Material Master Data




       1. Transfer of Customizing

       2. Initial Load of MATERIAL and                                              Uses qRFC and
          SERVICE_MASTER Data                                                       Middleware
                                                                                    Functions


       SAP AG 2002




  First, perform the initial download of the Customizing objects:
    - Choose Middleware → R/3 Adapter → Initial Download → Start (R3AS)
    - Object class CUSTOMIZING
    - Download objects DNL_CUST_BASIS3, DNL_CUST_PROD0, DNL_CUST_PROD1 and
        DNL_CUST_SRVMAS
  Perform the initial download of the materials:
  To start the download for materials and for the service master (if required), call transaction R3AS
  and specify object MATERIAL or object SERVICE_MASTER as appropriate and the Source Site
  (SAP R/3 backend system) and Destination Site (Enterprise Buyer system).
  Delta download:
    - Delta events are set automatically after the initial download has taken place, so no extra action
       is needed.




(C) SAP AG                                     ADM130                                               3-35
  Initial Load of Vendor Master Data




             1. Transfer of Customizing

             2. Initial Load of Vendor Master Data

                 EBP                                               SAP R/3 OLTP




                                          Synchronous
                                          Function Calls



       SAP AG 2002




  To use existing master records for vendors, you must replicate the vendor master records from the
  backend system. The following prerequisites must be met:
    - Backend system: The vendor must be assigned to a purchasing organization.
    - Enterprise Buyer system: The organizational structure must be in place. The organizational plan
       must include an organizational unit that the vendor can be assigned to and each purchasing
       organization must belong to an organizational unit
  Call transactions BBPGETVD and BBPGETVC to replicate the data to the Enterprise Buyer system.
  You can change the data after replicating it. However, you should not copy over any vendors, since
  your changes are overwritten as a result.
  BBPGETVD - Specify whether:
    - The Enterprise Buyer system is to assign numbers from the internal number range for business
       partners for the vendors to be copied.
    - The vendor numbers are to be copied from the backend system. If the number already exists in
       the Enterprise Buyer system, the system assigns a number internally for the vendor.
       In this case, configure the internal number range so that it does not overlap with the number
       range in the backend system.
    - Before the system performs the data replication, it informs you of any possible problems (such
       as missing purchasing organizations).
  BBPGETVC - Use this transaction to copy additional data for the vendor from the backend system,
  such as the payment terms.
  BBPUPDVD - Here you can adapt the vendor data in the Enterprise Buyer system, should the master
  data in the backend system be different from the replicated data.




(C) SAP AG                                    ADM130                                             3-36
  ALE Configuration

                                        Used for for example,
                                        Invoices, Goods Receipt




                                                 EBP             SAP R/3 OLTP


                       BAPI              ALE Definition
                                         1. Create distribution model
                                         2. Set data filter
                                         3. Generate partner agreement
                                         4. Distribute model view to
                                            backend systems
                       EBP
       SAP AG 2002




  Determine ALE settings so that Enterprise Buyer can communicate with:
    - Component Material Management (MM) in the backend system. This is only necessary if you
      want to book goods receipt documents and invoices in the backend system.
    - Components Financial Accounting (FI) and Controlling (CO) in the backend system.
  Essential steps for ALE distribution model (transaction BD64):
    - Create the model (enter model name, backend systems, BAPIs).
    - Determine the data filter.
    - Generate partner agreement.
    - Distribute the model to all participating backend systems.




(C) SAP AG                                 ADM130                                          3-37
  ALE Distribution Model




       SAP AG 2002




  As the following Enterprise Buyer applications use the ALE mechanism, you also have to define the
  ALE settings:
    - Confirmation of materials
    - Invoicing
    - Financial Accounting posting for procurement cards
    - Commitment posting from purchase orders

  The IMG documentation gives the BAPIs and message types to be set up.




(C) SAP AG                                   ADM130                                             3-38
  Determining the Backend Systems
                                                                             SAP R/3 OLTP




         BBP_BACKEND_DEST
                                                                             SAP R/3 OLTP




                                                                             SAP R/3 OLTP



                              EBP
                                                                             ERP
                                                                             (other system)
  Input                                              SAP
     Name                                          Business
     Logical System                                Connector
     System Type                                     optional


       SAP AG 2002




  Next, define your backend systemand decide whether sales orders and the follow on documents
  (confirmations of goods receipt/service entry and invoices) are to be created locally in the EBP
  system.
     - In IMG, choose Enterprise Buyer Professional Edition → Technical Basic settings → Define
        backend systems
  In this step, you specify:
     - The backend system(s) which with you work.
     - Whether purchase orders and their subsequent documents confirmations, goods receipts/service
        entry sheets, and invoice are to be created locally in the Enterprise Buyer System.
  Specify:
     - Name and description (free form entry) of the system.
     - The RFC destination for the system.
     - Type and release level of the backend system.
     - Select local, if the system is your local Enterprise Buyer System and purchase orders and their
        subsequent documents are to be created there.
  If you are using one backend, you must maintain at least two systems (local and backend systems).
  Otherwise, the system will behave as if you are using standalone mode and you will be unable to
  post goods receipts against the backend (this is hard coded).




(C) SAP AG                                    ADM130                                              3-39
  Spooler


             User saves                       Spooler/
             document                     Abstraction layer



                                                                    Dispatcher
                                                              (finds suitable driver)



                                                                     Driver
                                                          (for each backend system)



                                                            BAPI



       EBP



                                                              SAP R/3 OLTP
       SAP AG 2002




  Depending on the release, the business processes in the backend system can be realized over
  different BAPIs. The abstraction layer encapsulates in the backend system the BAPI calls that are
  necessary to create the backend documents from requirement coverage requests. Here the abstraction
  layer accesses the following sources of information:
     - Dispatcher: this function module evaluates the Customizing and determines the driver to be
       called, the backend system to be communicated with, and the release of the backend system.
     - Driver: For each supported release and abstraction layer, there is a driver function module that
       calls the BAPIs in the backend system.
     - Spooler: The spooler regulates the transfer of requirement coverage requests, service entry
       sheets, and invoices from Enterprise Buyer into the backend system. If errors occur during the
       transfer (for example, because the backend system is not available) the spooler serves as wait
       queue for the requirement coverage requests. The spooler tries then at regular intervals to access
       the backend system and transfer the documents.




(C) SAP AG                                     ADM130                                               3-40
  Backend Coupling: Transfer Logic Stage 1




       Shopping Basket
                                                                          Workflow
       • Item 1 - Cell Phone
                                                                           Workflow
       • Item 2 - Pencil
                                                                          (Rule based
       • Item 3 - Car Adapter Kit Phone
                                                                           decision)
       • Item 4 - Fitting Pump

                                                                           Approval



                      Determination of target system



                 Additional,     Product Category   Target System
                                 Communication      ERP 1 (R/3 Rel.3.1)
                  customer
                                 Spare Parts        ERP2 (R/3 Rel. 4.5)
                specific rules
                                 Office             Local
                (Bus. Add In)    ...




              EBP
       SAP AG 2002




  If you decide to work with several backend systems, then for each product category you need to
  specify the backend system to be used for booking the relevant documents.
  In IMG, choose Enterprise Buyer Professional Edition → Technical Basic settings → Define
  Backend System for Product Category.
  You can also enter the product category generically (for example, office).
  In the requirement coverage request position stands the product category. The follow-on document
  (for example, purchase order) for the position is created in the system that you enter here for the
  product category.
  To implement another logic for determining the backend system, you can use the Business Addon
  BBP_DETERMINE_LOGSYS.




(C) SAP AG                                                  ADM130                                 3-41
  Backend Coupling: Transfer Logic Stage 2


                                                                                                               Requisition

      Workflow                                         Transfer Logic                                          Cell Phone (item 1)
                                                                                                               Adapter Kit (item 3)


                                                              Packaging
         Workflow
                              ERP 1
        (Rule based           • Item 1
                                                             ERP 2                      Local
                                                             • Item 4                   • Item 2
         decision)            • Item 3
                                                                                                               ERP 1
         Approval
                                             Determination of target objects                                   Reservation

                                                                                                               Fitting (item 4)
                                                   Product Category     Organisational Unit   Target Object
                             Additional,           Communication        Service               Requisition
                                                   Communication        Headquarter           Purchase Order
                              customer
                                                   Spare Parts          Factory               Purchase Order
                            specific rules
                                                   Spare Parts          Service               Reservation
                            (Bus. Add In)          Office               * (everybody)         Purchase Order   ERP 2
                                                   ...




                          Local (Procurement - Standalone)
                           Purchase Order: Pencil (item 2)




                  E
       SAP AG 2002 BP




  Define objects to be created according to purchasing group and category ID. In IMG, choose SAP
  Enterprise Buyer Professional Edition → Define objects in backend system (PR, RES, PO).
     - If you create your MM documents in a backend system, determine which document is created in
        the backend system for a requirement coverage request position. You can create a purchase
        requisition, a purchase order, or a reservation.
  Enter an organizational unit and/or a product category (for example, office supplies, and hardware).
  The organizational unit contains the purchasing group that is responsible for purchasing products in
  this category. You can enter the product category generically (for example, office*). The backend
  system is determined by the product category in the requirement coverage request position. In the
  position stands also the organizational unit.
  To implement another logic for the creation of documents in the backend system, you can use the
  Business Addon EBP_TARGET_OBJECTS.
  Choose the procurement type:
     - For materials available in sufficient quantity in the warehouse stock for the due date,
        reservation, otherwise external procurement.
     - For inventory-managed materials, always reservation, independently of available stock.
     - Always external procurement. A reservation is not made. You must determine the form of
        external procurement.




(C) SAP AG                                                   ADM130                                                                   3-42
  Set Control Parameters



  Control parameters for the documents
  creation, for example, orders, reservations by
  synchronous BAPI call


          EBP_CONTROL_TAB

          CLEANER_...
          SPOOL_...




                                    EBP                                          SAP R/3 OLTP



        SAP AG 2002




  In IMG, choose Enterprise Buyer Professional Edition → Technical Basic settings → Set Control Parameters.
  Perform these steps only for scenarios where you create the MM documents in the backend system.
  You only perform this step if you create Materials Management documents in the backend system. You
  specify:
     - Information about the spooler.
     - Information about the update frequency.
        Documents in the backend system are updated asynchronously. You can only further process the
        requirement coverage request in the Enterprise Buyer system after the update has been made.
        The system checks at set intervals whether the backend documents have been created. If so, the system
        updates the requirement coverage request. Then the requirement coverage request can be further
        processed. If not, the system checks after the next interval whether the documents have been posted.
  The system checks at the entered interval whether the backend documents have been created. If they have, the
  requirement coverage request is updated, and the requirement coverage request can be processed further. If not,
  the system checks after the next interval whether the documents are booked.
  The possible key fields for the spooler are:
     - SPOOL_JOB_USER: User name under which the spool job runs
     - SPOOL_LEAD_INTERVAL: Lead interval in seconds
     - SPOOL_MAX_RETRY: Number of tries by the spooler
        (Time to next try = Lead interval * Number of previous tries squared)
  The key fields for the update interval are:
     - CLEANER_INTERVAL: Interval length in seconds
     - CLEANER_JOB_USER: User name under which the job runs




(C) SAP AG                                         ADM130                                                   3-43
  Batch Transfers


                                Push (spooler)

                                Pull
                                (clean_reqreq_up,
                                bbp_get_status_2)
                 Batch Jobs
                      EBP                                     SAP R/3 OLTP


      Update tables in EBP with purchasing documents that
      have been created in backend system
           Report CLEAN_REQREQ_UP
      Update tables in EBP with follow-on documents that have been
      created in backend system
           Report BBP_GET_STATUS_2


       SAP AG 2002




  The requirement request can only be processed further in the backend after the corresponding
  documents have been created there. The spooler is the one who transfers the shopping basket data to
  the backend. The cleaner is a report that checks if all data has been transferred correctly to the
  backend and if so it will delete obsolete table entries in EBP and maintain the numbers of the created
  documents.
  To start the CLEANJOB execute report START_CLEANER (in <SA38>). This report schedules the
  job CLEAN_REQREQ_UP in the time interval you entered in the control parameter in customizing
  (time unit is seconds). Stop the CLEAN_JOB with a report called STOP_CLEANER. If the
  parameter CLEANER_INTERVAL is not set in customizing, you can also periodically schedule
  CLEANJOB manually.
  If you are having problems with the CLEANJOB you can schedule it manually. Leave the
  Cleaner_Interval blank and schedule a job that starts the program CLEAN_REQREQ_UP on a
  periodical basis. You will not need to restart the CLEANJOB after rebooting the system.
  The program BBP_GET_STATUS_2 retrieves new information from the backend system, such as
  the purchase order number. after conversion from the purchase requisition. The program
  BBP_GET_STATUS_2 has to be scheduled at least as a daily job in the EBP system. For
  demonstration purposes, you can schedule it every five minutes to have a sooner update.
  Schedule Reorg Jobs: There are a number of jobs that must periodically run in a live SAP R/3
  installation, for example, to delete outdated jobs or spool objects. As of Release 4.6C, you can easily
  schedule these jobs automatically as follows: Call Transaction <SM36>, press Schedule Reorg Jobs.
  See note 16083 for details and comments.




(C) SAP AG                                      ADM130                                               3-44
  Trigger for Printing




       SAP AG 2002




  In IMG, choose Enterprise Buyer Professional Edition → Application Specific Basic settings → Set
  Output Actions and Output Format → Define Actions for Purchase Order Output.
  Make the settings for output of the following procurement documents: Purchase orders and Purchase
  contracts. You can set up the following output media:
     - Print
     - E-mail
     - Fax
     - XML (this output medium is currently not available for contracts)
  For the output media fax, printer, and e-mail, you can select your own form provided that you have
  created your own form via the SAP Menu Tools --> Form Printing --> Smart Forms. If you do not
  want to use your own form, you can adopt the standard settings. This corresponds to action
  determination with simple determination technology for procurement documents. Enterprise Buyer
  automatically opens the action profile for the purchase order (application BBP_PD procurement
  document). You should only process this profile at the start point in the IMG of Enterprise Buyer
  professional edition.




(C) SAP AG                                   ADM130                                             3-45
  Business Partner




       SAP AG 2002




  You can create and manage a number of addresses for a business partner. This can be done using
  various roles, such as purchasers for vendors or external addresses or as the system administrator. All
  addresses/address types are saved with the business partner. You can only add standard addresses to
  the system via master data maintenance (Business Partner --> Manage Business Partner).
  Professional purchasers can:
    - Search for business partners and their addresses.
    - Change, display or add business partner addresses.
    - Select from all addresses assigned in the organization model and system for an address type.
    - Enter an address in the business document that differs from that in business partner master data
       and use the ‘c/o‘ field for the alternative name of the business partner. This address is used only
       once for this transaction and is not saved in the master data.
    - If you want to use an address for a business partner on a long-term basis that does not exist in
       the master data, you should enter the address using the Edit Addresses application. You should
       enter the alternative name in the ‘c/o‘ field and enter further data in the other address fields.
       Later, you can assign this address to a business document using the search help.
  System administrators can set the following addresses for their own company (purchasing side):
    - Ship-to address
    - Invoice recipient address (you can make default settings for the Invoice Recipient Address and
       the Ship-to Address via the attribute ADDR_BILLT and ADDR_SHIPT at all levels of the
       organizational model).




(C) SAP AG                                      ADM130                                               3-46
  Message Exchange by XML


                                        SAP
                                      Business
                                      Connector

                                          Sales Order
                 Sales Order                                     Customer order
                                      Order Confirmation

                                         Deli
                                              very
                                                   Note
                 Confirmation                                       Delivery




                  Invoice              Inbound Invoice        Invoicing Document

                                      Outbound Invoice



                       EBP                                               Vendor
       SAP AG 2002




  Data can be exchanged in XML format between Enterprise Buyer Professional edition and vendor
  systems. Data can be exchanged either directly using EBP XML or via a public/private exchange.
  This documentation deals only with the former case. The data is transferred between the vendor
  system and the SAP Business Connector via HTTP (or FTP), and between the Business Connector
  and the Enterprise Buyer system via RFC. The graphic illustrates the data exchange between the
  Enterprise Buyer system and external systems. The following prerequisites apply to EBP XML data
  exchange:
    - The SAP Business Connector has been installed
    - BC package SAP-EBP has been installed
    - BC package SAP-EBP Customizing has been installed
    - The connection between Enterprise Buyer and the SAP Business Connector has been defined in
       Customizing (both in Enterprise Buyer and on the Business Connector)
  XML format can be used to send a message from Enterprise Buyer to a vendor system that contains
  an invoice for ordered goods or services. The following documents can be sent in XML:
    - Purchase order: When creating a purchase order from Enterprise Buyer, a message can be sent
       in XML to the vendor system. A sales order is then created in the vendor system.
    - Order acknowledgment: A message can be sent in XML to confirm the entry and acceptance of
       an order from the vendor system to Enterprise Buyer.
    - Shipping notification: A message can be sent in XML to confirm a delivery from the vendor
       system to Enterprise Buyer.
    - Incoming invoice: A message can be sent in XML from the vendor system to Enterprise Buyer
       that contains an invoice for the ordered goods or services.
    - Outgoing invoice: A message can be sent in XML from Enterprise Buyer to the vendor system
       that contains an invoice for the ordered goods or services.


(C) SAP AG                                   ADM130                                          3-47
  Application Customizing




          Further
        Customizing




                                                                    EBP




       SAP AG 2002




  Beside the settings presented so far, the most important activities for application Customizing are as
  follows:
    - Start the application monitor (ensures that any errors occurring in Enterprise Buyer are
       displayed in the application monitor)
    - Define number range for materials management documents
    - Determine transaction type
    - Determine account assignment category
    - Enter tax code
    - Define workflows
    - Define reasons for rejection of incoming invoice
    - Status tracking for sales order
    - Procurement cards
    - Specify the organization model
    - ...




(C) SAP AG                                      ADM130                                               3-48
  EBP and CRM in one System




                                              Client 100         Client 200
                                                  EBP                CRM
       SAP R/3 OLTP

                SAP R/3 OLTP                        EBP/CRM Server                                  SAP R/3 OLTP
              SAP R/3 OLTP




                           Client 100
                             EBP/CRM


                                                                             SAP R/3 OLTP
                       EBP/CRM Server

        SAP AG 2002




  EBP 2.0 and 3.0 are delivered with the SAP CRM. On account of this fact, the question arises whether it is possible to use
  EBP and CRM in a single system and even with one client. Since the CRM/EBP system supports all SAP R/3 Releases as
  of Release 3.1H, problems occur due to the different types of links of the objects customer, vendor, plant and materials or
  products. If EBP and CRM are operated with the same client, they use a common business partner master, that is,
  customers and vendors as well as plants must be distributed to the CRM/EBP system. Depending on the type of
  maintenance of the corresponding relationship in the SAP R/3 backend system, either several business partners for one and
  the same SAP R/3 object would be created (in this case, CRM/EBP customers would basically have 2 identical business
  partners available for selection) or from in fact independent objects a single business partner would be created, however, in
  the latter case data would be lost. Furthermore EBP and CRM use different strategies regarding distribution of data. While
  CRM only supports one backend system, EBP can support multiple backend systems. That is, from the backend system to
  the CRM/EBP system and vice versa, whereas the CRM/EBP system only allows a download to the CRM/EBP system on
  account of the several supported backend systems. This could result in inconsistent data. Due to the different backend
  linkage types also a uniform Customizing is not possible. Thus, the common use of a client is not possible due to the
  backend linkage, provided that it is a single and for both applications identical backend system. The above-described
  problems do not occur when different clients are used, however, the administration of this system and of the different ITS
  links will become complicated within short time. Also mutual influences regarding the performance cannot be excluded.
  Thus, the formal recommendation of SAP is as follows: For EBP 2.0 use a separate system for EBP and CRM. For EBP
  3.0: Independent of the constellation, a customer can always run EBP and CRM in a single system, however, use two
  different clients in the system. If the multiple backend functionality is used in the EBP system, it is absolute necessary to
  use two clients. If EBP and CRM run against different backend systems (or clients within a system), also two different
  clients must be used. If EBP and CRM run against exactly one backend system (both using the same one), they can also be
  used together in a single client in a productive way. If you intend to use CRM and EBP in a single system, consult the
  product management of one of the two components. (see also note 217003)




(C) SAP AG                                               ADM130                                                           3-49
  Summary: Distribution of Data
                                      EBP Middleware
                                                                              always

                                                                              possible

                                Requisite Catalog Product Catalog


                                                  ITS




                                               synchr.
                                              BAPI Call
                      Shopping Basket                          Order (MM)

                                                               Invoice (FI)
                                              ALE
                      Order (local)                            Commitments (CO)

                      Master Data                              Master Data
                                               qRFC
       SAP AG 2002               EBP                               SAP R/3 OLTP




(C) SAP AG                               ADM130                                     3-50
  One-Step Business and Marketplaces


                 One-Step Business and Marketplaces (Optional)
             One-Step Business and Marketplaces
    One-Step Busines and Marketplaces
  One-Step Business and Marketplaces (Optional)
                                                          One-Step Business and Marketplaces (Optional)



                                                                                                          Enterprise Buyer Scenarios


                                                                                                          Connecting the Components


                                                                                                          Business System Organization

                                                                                                          One-Step Business and Marketplaces
                                                                                                                     One-Step Business and Marketplaces
                                                                                                                                         (Optional)
                                                                                                                                              Optional)




                                    SAP AG 2002




(C) SAP AG                                                                                                                ADM130                          3-51
  The Idea of One-Step Business




           Buying
           Buying           Search                        Register             Selling
                                                                               Selling


                                    Select              Offer




          Buyer                                                                Seller

                                     Buy                 Sell

                              Operational                 Operational
                                                          Operational
                              Operational                                   Collect
                  Receive      Systems
                                Systems                    Systems
                                                            Systems
                             (Financials &
                             (Financials &               (Financials &
                                                         (Financials &
                               Logistics)
                               Logistics)                  Logistics)
                                                           Logistics)

                                             Transact


       SAP AG 2002




  Buyers and sellers can buy and sell in one step using the mySAP SRM and CRM solutions.




(C) SAP AG                                   ADM130                                        3-52
  Public and Private Exchange

                                                   Buyer
                                                   Buyer                         Seller
                                                                                 Seller


     The “Old World”
          Individual connections to
          business partners
          Different technologies
                                                             Exchange
          (EDI, Edifact, FAX, XML, …)
          Interface must always be            The “New World”
          maintained
                                                    A single connection to all
          Technology cannot be ignored              business partners

      Buyer
      Buyer                      Seller
                                 Seller             Marketplace provider provides
                                                    technology, search functions,
                                                    applications, and security
                                                    mechanisms
                                                    Enables individual procurement
                                                    through the Marketplace




       SAP AG 2002




(C) SAP AG                                ADM130                                          3-53
  One-Step Business



         Buyer System                                                     Seller System
                                         Exchange




        Buy Side Solution                                                 Online catalog
                                          Business                        Shop System
                                          Directory
                                           (Search
                                          Suppliers)
    a            b                                                              b           a




                     SAP BC            Business Document               SAP BC
                      (XML)                Exchange                     (XML)
                                       (Exchange example
                                            PO/SO)
     ERP                                                                                   ERP



         SAP AG 2002




  In the Enterprise Buyer bidding scenario, you need the SAP Business Connector (BC) to transfer
  data using FTP or HTTP. BC can also be used to transfer:
     - Purchase orders
     - Order acknowledgments
     - Shipping notifications
     - Invoices
     - Catalog data
  XML export: The user can send invoices by XML export to external business partners. For this, the
  system administrator must maintain in Customizing the organizational plans for the business partners
  and their communication data.
  XML import: To import data over the Internet, you need BC. The data is transferred by FTP or
  HTTP from the vendor system to the BC, and by RFC from the BC to Enterprise Buyer.
  To ensure that blocked orders are only valid for a certain time, set the validity period for blocked
  orders in Customizing of the sales transaction at header level in field Gültigk.dauer.
  To give the status rejected to all orders whose validity has expired, so that they can be deleted or
  archived, execute report CRM_STATUSSET_REJECTED.




(C) SAP AG                                    ADM130                                              3-54
  One-Step Business Process Flow

                      Buyer
                       Buyer                    Exchange
                                                 Marketplace                 Seller/Catalog
                                                                              Seller/Catalog

              Create shopping basket      Search Business Directory for          Search Catalog
                in Enterprise Buyer        one-step business partner


                                                                              BC polls Seller mailbox
               Save shopping basket                                              on Marketplace


                PO is created and
                                                                           BC gets order as IDoc XML
             ORDERS IDoc is generated
                                                Seller mailbox at
                                                  mySAP.com
                 BC receives PO as                                             BC sends IDoc to R/3
                  ORDERS IDoc


                                                                             IDoc processing creates
                BC sends IDoc XML
                                                                                   sales order
                  to Marketplace


             BC polls Buyer mailbox and                                   Successful sales order creation
                 receives IDoc XML                                           generates ORDRSP IDoc
                                                Buyer mailbox at
                                                  mySAP.com
               BC sends IDoc to R/3                                         BC receives ORDRSP IDoc



              IDoc processing updates                                          BC sends IDoc XML
                  Purchase Order                                                 to Marketplace



       SAP AG 2002




  Example:
    - In the Enterprise Buyer system, a buyer wishes to fill a shopping basket with products from the
      CRM product catalog. The buyer views the CRM product catalog, puts the required products
      into the CRM shopping basket, and orders them.
    - The CRM shopping basket is saved as a blocked sales order in the CRM system (sales order
      with delivery block), and has a specific validity period, which you can define in Customizing
      for the sales transaction. The sales order is not confirmed or transferred into the backend
      system. An availability check takes place for the sales order.
    - The shopping basket items are transferred through the OCI to Enterprise Buyer. Configuration
      data can also be transferred. The buyer then sees the items in the Enterprise Buyer shopping
      basket. The reference number for the sales order is displayed in the basic data for the items.
    - The buyer orders the shopping basket and it goes through the approval process.
    - Once the shopping basket has been approved, the purchase order is created in Enterprise Buyer.
      The reference number for the sales order is also displayed in the purchase order.
    - The purchase order is sent to the vendor by XML. The CRM system interprets the incoming
      message, and the sales order status is set from blocked to released. The vender sends an order
      confirmation back to the buyer.




(C) SAP AG                                         ADM130                                                   3-55
  One-Step CTO: Business Process Details


     EBP                                  Internet Sales               CRM              IPC


                  1. Access catalog
                                                    2. Configure




                                                    3a. Get quote
         4. Transfer quote by XML-OCI                                             3b. Create
                                                    3c. Return ID                 quote
         (items, quote ID,
         characteristic valuation)

         5a. Order the quote by XML                                         5b. Create SO
         (using quote ID)                                                   by status change




       SAP AG 2002




  CRM XML inbound interface
    - Changing the status of a shopping basket from Quotation to Order creates sales order.
  A quotation is a shopping basket with status Quotation.
    - If a quotation is changed to an order, the pricing stays unchanged.
    - Reservations are possible.
    - The validity date is calculated dynamically: Validity date = Date of last change + Validity
       period
  CRM Customizing
    - To enable quotations, call transaction CRM_SHOP and activate Enable offer creation.
    - To set the validity period for quotations, call transaction SPRO and choose CRM →
       Transactions → Maintain Transact. Types → Cust. Header.
    - To set status Rejected for invalid quotations, run report CRM_STATUSSET_REJECTED.
  Enterprise Buyer Customizing
    - To transfer characteristic valuation via basket item long text, call transaction SPRO, choose
       EBP → Products → Define Catalog → Call structure, and set OCI_VERSION = 2.0 (fixed
       value).
    - If XML-OCI or XML order outbound interface is used, install BC.




(C) SAP AG                                     ADM130                                                 3-56
  ‘One World‘ with Enterprise Buyer

 Intranet                                                                                    Internet

    Backend
    Backend
    system 1
    system 1                                                                          Suppl. 1 Market-
                                                                                      Suppl. 1 Market-
                                                                                               place(s)
                                                                                               place(s)
        Backend
        Backend                         Sourcing/negotiation
        system n
        system n                       for indirect AND direct                           Suppl. n
                                                                                         Suppl. n
                                                                               ch
                        Ex                    materials!                     ar
                          ec
                            uti                                            se
                                  on                             l og
                                         Enterprise Buyer
                                                             Cata
                                                                                             Suppl. 1
                                                                                             Suppl. 1
       APO
       APO                                                                                            Market-
                      Demand                                 Tendering (public/                       Market-
     (SCM)
      (SCM)                                                             non-public)
                                                                                                     place(s)
                                                                                                      place(s)
                                                                                             Suppl. n
                                                                                             Suppl. n
                                                                 Co
                                   s                      tra       n
                               ti c                          ct(
                            aly Central purchasing system        s)
                         An                                                               Suppl. 1
                                                                                          Suppl. 1
                                       AND communication hub
         Business
          Business                        for the Internet!
         Warehouse
         Warehouse                                                                     Suppl. n
                                                                                       Suppl. n




       SAP AG 2002




(C) SAP AG                                     ADM130                                                            3-57
  Unit Summary



                      You are now able to:

                         Describe the mySAP SRM
                         Connect the SAPMarkets Enterprise
                         Buyer components
                         Organize your business system for
                         SAPMarkets Enterprise Buyer




       SAP AG 2002




(C) SAP AG                              ADM130               3-58
  Further Documentation



                      Additional information about Configuring
                      Enterprise Buyer:
                         ERP210 Enterprise Buyer Configuration
                         CT205 Requisite Catalog Installation
                         ERB240 Requisite Catalog and Product
                         Content Workbench Configuration and
                         Maintenance
                         service.sap.com/instguides
                         service.sap.com/e-procurement




       SAP AG 2002




(C) SAP AG                              ADM130                   3-59
                                                                                 Exercise

                     Unit: Configuring Enterprise Buyer
                     Topic: Communication Configuration

                     At the conclusion of this exercise, you will be able to:
                     • Check the configuration
                     • Check the distribution model
                     • Schedule backend jobs



                     Your technical team members have installed the SAP EBP system
                     and it is ready to be configured and customized. In this exercise,
                     you will perform the necessary configuration steps required to
                     establish communication between the EBP Component and the
                     backend SAP R/3 System.
   1-1       DO NOT PERFORM ANY CHANGES!
             Log into the CRM/EBP component system from the SAP GUI:
             User: EBP-##
             Password: init
             Client: 800


   1-2       DO NOT PERFORM ANY CHANGES!
             Receive the name of your RFC destination that is used for data transfer to the SAP
             R/3 backend system.
             What is the SAP R/3 version of your backend?


   1-3       DO NOT PERFORM ANY CHANGES!
             Locate the RFC destination defined for the backend SAP R/3 system that will be
             connected to the SAP EBP system and answer the following questions:
             Which type of RFC destination must be used if the backend is an SAP R/3 system?
             Which user and client are used by the EBP system to log into your backend?
             Test the connection to the backend SAP R/3 system.
             Which SAP R/3 system is reached with this RFC connection?




(C) SAP AG                                   ADM130                                         3-60
   1-4       DO NOT PERFORM ANY CHANGES!

             Configuration of the logical system.


             1-4-1 View the logical system definition in the SAP EBP component.
                    What is the logical system of your client?
                    What are the settings for Changes and transport for client specific objects?



   1-5       DO NOT PERFORM ANY CHANGES!

             Check the distribution model for sending IDocs between the EBP component and
             the backend SAP R/3 System..
             1-5-1 Which BAPIs are distributed in distribution model B2B_IDES.



   1-6       DO NOT PERFORM ANY CHANGES!

             Check the control parameter definitions.


             1-6-1 Set the control parameters that facilitate the communication to the backend
                   SAP R/3 system(s).
                    Check the values for the control parameters:
                    CLEANER_INTERVAL:                   30
                    CLEANER_JOB_USER:                   CRMREMOTE
                    SPOOL_JOB_USER:                     CRMREMOTE
                    SPOOL_LEAD_INTERVALL:               300
                    SPOOL_MAX_RETRY:                    10


                    Why don´t you have to supply parameters for the cleaner job
                    (CLEANER_INTERVAL, CLEANER_JOB_USER)?
                    How can the necessary actions be performed as well?




(C) SAP AG                                   ADM130                                          3-61
   1-7       DO NOT PERFORM ANY CHANGES!

             Locate the scheduled backend jobs for the SAP EBP component.
             1-7-1 Using the job overview, view the jobs that are running in the EBP
                   component.
                    What jobs are currently running (or listed) for your client?
                    Which job is used to check whether all data has been transferred correctly to
                    the backend system, and will delete obsolete table entries in EBP and
                    maintain the numbers of the created documents?


                    Which job retrieves new information from the backend system, such as the
                    purchase order number after it was converted from a purchase requisition
                    and goods receipt document numbers and quantities?




(C) SAP AG                                   ADM130                                          3-62
                     Unit: Configuring Enterprise Buyer
                     Topic: Process Overview

                     At the conclusion of this exercise, you will be able to:
                     • Perform the procurement process of SAP EBP



                     In this exercise you will walk through some of the processes.




   2-1 Create a shopping basket that will contain one item.


                          Log onto client 800 of the SAP EBP System from the
                          browser:
                          User ID: BUYER-##
                          Password: Init
                          Client: 800


                          Change your password.



             Create a new shopping basket.
   2-2       Choose Requisite Inhouse. Search for PC Installation, add one item to your
             shopping cart and order this item from the catalog.


   2-3       Enter a name for your shopping basket.
             Order your shopping basket.
   2-4       Check the status of your shopping basket.
             Record the type of document and the document number that was created for each
             line item by viewing the history of each item.



(C) SAP AG                                   ADM130                                       3-63
   2-5       Perform the goods receipt using the browser.
             Select your purchase order within Confirm Goods Receipt .
             Enter any description and choose Confirm to confirm the goods receipt.
   2-6       Check the status of your shopping basket using the browser.
             Take a look at the history of your shopping basket.
             Which document has appeared now additionally? (This may take some minutes,
             because the JOB GET_STATUS_800 must run to transfer the data)
             Log off.


   2-7       In your SAP R/3 backend system, take a look at your purchase order.


                          Log on to the SAP R/3 System with the SAPGUI.
                          User ID: BACK-##
                          Password: Init
                          Client: 800
                          Change your password.


             Call transaktion ME23N display purchase order (Logistics→Materials
             Management→Purchasing→Purchase Order→Display)
                Select your purchase order.


   2-8       Take a look at the goods receipt document in SAP R/3 backend system.
             Call Goods Receipt for Purchase Orders, transaction MIGO (Logistics→Materials
             Management→Inventory Management→Goods Movement→Goods Receipt→For
             Purchase Order→Purchase order known)
             In the input field where goods receipt is shown, change to display.
             Enter your purchase order number and choose Enter.
                Take a look at the document info.
                Which FI documents have been created additionally?




(C) SAP AG                                    ADM130                                   3-64
                    Unit: Configuring Enterprise Buyer
                    Topic: Define Catalogs

                    At the conclusion of this exercise, you will be able to:
                    •   Connect a catalog to the SAP EBP System



                     In this exercise you will connect this catalog to the SAP EBP
                    system.




                    NOTE: Throughout these exercises, the <##> designation refers
                          to your group number.

                         A majority of these exercises are case sensitive.




   3-1       Define a catalog in SAP EBP/CRM with the Catalog ID ISA##, and catalog name
             ‘Internet Sales ##’ using the following technical details:
                         Log onto your client of the SAP EBP/CRM component from
                         the SAP GUI:
                         Client: 800
                         User: EBP-##


                   Start the transaction SPRO.
                   Choose the SAP Reference IMG button.
                   Search for Enterprise Buyer Professional → Master Data → Define
                   Catalogs and start the customizing transaction.
                   You can know define a new catalog.
                   Use ISA## for the Catalog ID.
                   Use INTERNET SALES ## for the field Cat.name.
                   Select your catalog and choose Catalog application call structure.




(C) SAP AG                                  ADM130                                      3-65
             Maintain following entries exactly as stated below for the Call Structure of your
             Catalog. (Important: The call structure is case sensitive!)
              SEQ.              Name                Contents                          Contents
              Number
              10                                    http://<ITS-Server>.wdf.sap-      URL
                                                    ag.de:1080/scripts/wgate/isab2
                                                    b/!?~template=login_isab2b&~
                                                    language=en&shop=<B2B-
                                                    Webshopname>
              20                USERID              <Your Internet user ID for the    Fixed value
                                                    contact person from the chapter
                                                    configuring internet sales >
              30                PASSWORD            <Your Internet user password      Fixed Value
                                                    for the contact person from the
                                                    chapter configuring Internet
                                                    Sales >
              35                OCI_VERSION 1.0                                       Fixed Value
              40                HOOK_URL                                              Return URL
              50                ~OkCode             ADDI                              Fixed Value
              60                ~target             _top                              Fixed Value
              70                ~caller             CTLG                              Fixed Value


                     Save your entries.


   3-2       Assign this catalog to your user within the organizational unit
             Call transaction PPOMA_BBP.
             Select the searchoption User-->Search Term in the upper-left subscreen.
             Enter user BUYER-##.
             Double click on your user from the search results in the lower-left subscreen.
             Double click on your user in the organizational unit in the upper-right subscreen
             (the row with the portrait icon).
             Select the tab Attributes within the Details for position User.
             Look for the parameter Catalog and double an entry; afterwards you can enter your
             new catalog ID from the entry help.
             Select the red light to reactivate the scenario.
             Save.
             DO NOT CHANGE ANY OTHER SETTINGS!




(C) SAP AG                                     ADM130                                            3-66
   3-3       Check if your user has Access to the Catalog.


                          Log onto your client of the SAP EBP System from the
                          browser:


                          User ID: buyer-##
                          Client: 800



             Important: Use the same language as in 3-1 for the produkt catalog definition.
             Create a new shopping basket.
             Check if your catalog appears in the selection.




(C) SAP AG                                    ADM130                                          3-67
                     Unit: Configuring Enterprise Buyer
                     Topic: One-Step Business

                     At the conclusion of this exercise, you will be able to:
                     • Perform the procurement process of SAP EBP with an Internet
                       Sales Catalog


                     In this exercise you will walk through some of the processes.




   4-1       Create a shopping basket that will contain one item.


                          Log onto client 800 of the SAP EBP System from the
                          browser:
                          User ID: BUYER-##
                          Client: 800



                Create a new shopping basket


   4-2          Search in the ISA## catalog for the Speed Mice and add this item to your
                shopping basket.
                Get a quotation for your shopping basket. Note down the quotation number,
                because it is needed later on.
                Transfer your quotation.


   4-3          Order your shopping basket.
                What is the shopping basket name?

   4-4          Check the status of your shopping basket.
                What type of document has been created?


   4-5          Logon to the CRM Server and check the status and type of the created business
                object (use Transaktion Maintain Sales Order, CRMD_BUS2000115).


(C) SAP AG                                    ADM130                                        3-68
                                                                                  Solutions

                       Unit: Configuring Enterprise Buyer
                       Topic: Communication Configuration

                       At the conclusion of this exercise, you will be able to:
                       • Check the Configuration
                       • Check the distribution model
                       • Schedule backend jobs



                       Your technical team members have installed the SAP EBP system
                       and it is ready to be configured and customized. In this exercise,
                       you will perform the necessary configuration steps required to
                       establish communication between the EBP component and the
                       backend SAP R/3 System.
   1-1       DO NOT PERFORM ANY CHANGES!
             Log on to the CRM/EBP component system from the SAP GUI:
             User:       EBP-##
             Password: init
             Client:     800


   1-2       DO NOT PERFORM ANY CHANGES!
             Call transaktion SPRO and click the SAP REFERENCE IMG button. In IMG,
             choose Enterprise Buyer Professional Edition → Technical Basic settings →
             Define backend systems.
             Receive the name of your RFC destination that is used for data transfer to the SAP
             R/3 backend system.
             Note the entry defined as SAP R/3 system (DII_800)
             What is the SAP R/3 version of your backend?
             It is version 4.6C.




(C) SAP AG                                     ADM130                                       3-69
   1-3       DO NOT PERFORM ANY CHANGES!
             Locate the RFC destination defined for the backend SAP R/3 system that will be
             connected to the SAP EBP system and answer the following questions:
             Call transaction SM59 (RFC destinations).
                    Which type of RFC destination must be used if the backend is an SAP R/3
                    system?
                    Within the category SAP R/3 connection you can find the RFC-
                    connection to SAP R/3 systems.
                    Which user and client are used by the EBP system to log on to your
                    backend?
                    Double click on the RFC-connection and you find the user that is used
                    for this connection. This may be the user CRMREMOTE.
                    Test the connection to the backend SAP R/3 system.
                    Choose Test Connection button.
                    Which SAP R/3 system is reached with this RFC connection?
                    Choose Remote Logon button. You can see in the new window for which
                    system the login has been done.

   1-4       DO NOT PERFORM ANY CHANGES!

             Configuration of the logical system.


             1-4-1 View the logical system definition in the SAP EBP component.
                    What is the logical system of your client?
                    Select transaction SPRO→ SAP Reference IMG.
                    SAP Implementation Guide → Enterprise Buyer Professional Edition →
                    Technical Basic Settings → ALE Settings (Logical System) →
                    Distribution (ALE) → Sending and Receiving systems → Logical Systems
                    → Define Logical System
                    Here you can see all logical systems that are known to your system.
                    Select transaction SPRO→ SAP Reference IMG.
                    SAP Implementation Guide → Enterprise Buyer Professional Edition →
                    Technical Basic Settings → ALE Settings (Logical System) →
                    Distribution (ALE) → Sending and Receiving Systems → Logical Systems
                    → Assign Client to Logical System
                    Double click on client 800.
                    Here you can find the logical system that is assigned to your client
                    (DTZ_800)



(C) SAP AG                                   ADM130                                        3-70
                    What are the settings for ‘Changes and transport for client specific objects’?
                    It is ‘automatic recording of changes.'




   1-5       DO NOT PERFORM ANY CHANGES!

             Check the distribution model for sending IDocs between the EBP component and
             the backend SAP R/3 system..
             Select Transaction SPRO→ SAP Reference IMG.
             SAP Implementation Guide → Enterprise Buyer Professional Edition →
             Technical Basic Settings → ALE Settings (Logical System) → Distribution (ALE)
             → Modeling and Implementing Business Processes → Maintain Distribution
             Model and Distribute Views
             1-5-1 Which BAPIs are distributed in Distribution Model B2B_IDES.
                    The BAPIs are ACC_GOODS_MOVEMENT, ACLPAY, BBPCO,
                    BBPIV, MBGMCR, WMMBXY and ALEAUD.

   1-6       DO NOT PERFORM ANY CHANGES!

             Check the control parameter definitions.


             1-6-1 Set the control parameters that facilitate the communication to the backend
                   SAP R/3 system(s).
                    Select transaction SPRO→ SAP Reference IMG.
                    SAP Implementation Guide → Enterprise Buyer Professional Edition →
                    Technical Basic Settings → Set Control Parameters
                    Check the values for the control parameters:
                    CLEANER_INTERVAL:                   30
                    CLEANER_JOB_USER:                   CRMREMOTE
                    SPOOL_JOB_USER:                     CRMREMOTE
                    SPOOL_LEAD_INTERVALL:               300
                    SPOOL_MAX_RETRY:                    10


                    Why don´t you have to supply parameters for the cleaner job
                    (CLEANER_INTERVAL, CLEANER_JOB_USER)?
                    How can the necessary actions be performed as well?
                    To start the CLEANJOB, you can execute report START_CLEANER (in
                    <SA38>). This report schedules the job CLEAN_REQREQ_UP in the
                    time interval you entered in the control parameter in customizing (time
                    unit is seconds). Stop the CLEAN_JOB with a report called


(C) SAP AG                                   ADM130                                           3-71
                    STOP_CLEANER. If the parameter CLEANER_INTERVAL is not set in
                    customizing, you can also schedule CLEANJOB manually periodically.



   1-7       DO NOT PERFORM ANY CHANGES!

             Locate the scheduled backend jobs for the SAP EBP component.
             1-7-1 Using the job overview, view the jobs that are running in the EBP
                   component.
                    Call transaction SM37.
                    Enter * for job name and * for User name, select SCHED., deselect
                    FINISHED and choose the button EXECUTE.
                    What jobs are currently running (or listed) for your client?
                    There are two jobs: BBP_GET_STATUS_800 running every fifth minute
                    and CLEANJOB running every two minutes.
                    You can get job details by double clicking on the job.
                    Which job is used to check whether all data has been transferred correctly to
                    the backend system, and will delete obsolete table entries in EBP and
                    maintain the numbers of the created documents?
                    CLEANJOB


                    Which job retrieves new information from the backend system, such as the
                    purchase order number after it was converted from a purchase requisition
                    and goods receipt document numbers and quantities?
                    BBP_GET_STATUS_800




(C) SAP AG                                   ADM130                                          3-72
                     Unit: Configuring Enterprise Buyer
                     Topic: Process Overview

                     At the conclusion of this exercise, you will be able to:
                     • Perform the procurement process of SAP EBP



                     In this exercise you will walk through some of the processes.




   2-1 Create a shopping basket that will contain one item.


                            Log on to client 800 of the SAP EBP System from the
                            browser:
                            User ID: BUYER-##
                            Password: Init
                            Client:800


                            Change your password.



             Create a new shopping basket.
             Select Shop.
   2-2       Choose Requisite Inhouse. Search for PC Installation, add one item to your
             shopping cart and order this item from the catalog.
             Select the Tab Catalog.
             Select the catalog RequisiteInhouse (Rel 2.6).
             In your new catalog window select Product Index and look for PC Installation
             in the category Electronics.
             With a click on it you get details. Select it and choose Add selected item to Cart.
             Choose Order Items. The item is in your shopping basket.



(C) SAP AG                                    ADM130                                         3-73
   2-3       Enter a name for your shopping basket.
             Enter a name in the shopping basket name field and write it down.
             Order your shopping basket.
             Choose Order.
   2-4       Check the status of your shopping basket.
             Select Check status. Click on the Item button for your shopping basket. Click
             on the Details button.
             Record the type of document and the document number that was created for each
             line item by viewing the history of each item.
             Select the tab History. You can find the shopping basket and a purchase order.
             (You might have to wait a minute for the CRM server to get the information
             from the backend system.)
   2-5       Perform the goods receipt using the browser.
             Select your purchase order within Confirm Goods Receipt.
             Select Confirm Goods Receipt . Click on the Create Confirmation button for
             your shopping basket.
             Enter any description and confirm the goods receipt by choosing Confirm.
   2-6       Check the status of your shopping basket using the browser.
             Select Check Status.
             Click on your shopping basket. Click on the Item button for your shopping
             basket. Click on the Details button.
             Take a look at the history of your shopping basket.
             Select the Tab History.
             Which document has appeared now additionally? (This may take some minutes,
             because the JOB GET_STATUS_800 must run to transfer the data)
             The new document is a Goods Receipt.
             Note the document number.
             Log off.




(C) SAP AG                                   ADM130                                       3-74
   2-7       In your SAP R/3 backend system, take a look at your purchase order.


                          Log on to the SAP R/3 System with the SAPGUI.
                          User ID: BACK-##
                          Password: Init
                          Client: 800
                          Change your password.


             Call transaction ME23N display purchase order (Logistics→Materials
             Management→Purchasing→Purchase Order→Display)
                        Select your purchase order.
             From the menu, choose purchase order→ Other purch. order and enter the
             number of your purchase order.
   2-8       Take a look at the goods receipt document in SAP R/3 backend system.
             Call Goods Receipt for Purchase Orders, transaction MIGO (Logistics→Materials
             Management→Inventory Management→Goods Movement→Goods Receipt→For
             Purchase Order→Purchase order known)
             In the input field where goods receipt is shown, change to Display.
             Enter your purchase order number and choose Enter.
                        Take a look at the document info.
                        Which FI documents have been created additionally?
                        Choose the FI DOCUMNTS button..
             The created FI documents are listed.




(C) SAP AG                                   ADM130                                    3-75
                    Unit: Configuring Enterprise Buyer
                    Topic: Define Catalogs

                    At the conclusion of this exercise, you will be able to:
                    •   Connect a catalog to the SAP EBP System



                     In this exercise you will connect this catalog to the SAP EBP
                    system.




                    NOTE: Throughout these exercises, the <##> designation refers
                          to your group number.

                         A majority of these exercises are case sensitive.




   3-1       Define a catalog in SAP EBP/CRM with the Catalog ID ISA##, and catalog name
             ‘Internet Sales ##’ using the following technical details:
                         Log on to your client of the SAP EBP/CRM component from
                         the SAP GUI:
                         Client: 800
                         User: EBP-##


                   Start the transaction SPRO
                   Choose SAP Reference IMG button.
                   Search for Enterprise Buyer Professional → Master Data → Define
                   Catalogs and start the customizing transaction.
                   You can know define a new catalog.
                   Choose Change and New Entries.
                   Use ISA## for the Catalog ID.
                   Use INTERNET SALES ## for the field Cat.name.
                   Choose Enter
                   Mark your catalog and choose Catalog application call structure.
                   Choose New Entries
(C) SAP AG                                  ADM130                                    3-76
                     Maintain following entries exactly as stated below for the call structure of
                     your catalog (Important: The call structure is case sensitive!)
              SEQ.                Name              Contents                          Contents
              Number
              10                                    http://<ITS-Server>.wdf.sap-      URL
                                                    ag.de:1080/scripts/wgate/isab2
                                                    b/!?~template=login_isab2b&~
                                                    language=en&shop=<B2B-
                                                    Webshopname>
              20                  USERID            <Your Internet user ID for the    Fixed value
                                                    contact person from the chapter
                                                    configuring Internet Sales >
              30                  PASSWORD          <Your Internet user password      Fixed Value
                                                    for the contact person from the
                                                    chapter configuring Internet
                                                    Sales >
              35                  OCI_VERSION 1.0                                     Fixed Value
              40                  HOOK_URL                                            Return URL
              50                  ~OkCode           ADDI                              Fixed Value
              60                  ~target           _top                              Fixed Value
              70                  ~caller           CTLG                              Fixed Value


             Save your entries.


   3-2       Assign this catalog to your user within the organizational unit
             Call transaction PPOMA_BBP.
             Select the searchoption User -->Search Term in the upper-left subscreen.
             Enter user BUYER-##.
             Double click on your user from the search results in the lower-left subscreen.
             Double click on your user in the organisational unit in the upper-right subscreen
             (the row with the portrait icon).
             Select the tab Attributes whithin the Details for position User.
             Look for the parameter Catalog and double an entry; afterwards you can enter your
             new catalog ID from the entry help.
             Choose the F4 help and select the catalog you just have defined.
             Select the red light to reactivate the scenario.
             Save.
             DO NOT CHANGE ANY OTHER SETTINGS!




(C) SAP AG                                     ADM130                                            3-77
   3-3       Check if your user has Access to the Catalog.


                            Log on to your client of the SAP EBP System from the
                            browser:


                            User ID: buyer-##
                            Client: 800



             Important: Use the same language as in 3-1 for the product catalog definition.
             Create a new shopping basket
             Select Shop.
             Check if your catalog appears in the selection.
             Choose the input help for catalogs to check if your catalog appears in the list.




(C) SAP AG                                      ADM130                                        3-78
                     Unit: Configuring Enterprise Buyer
                     Topic: One-Step Business

                     At the conclusion of this exercise, you will be able to:
                     • Perform the procurement process of SAP EBP with an Internet
                       Sales Catalog


                     In this exercise you will walk through some of the processes.




   4-1       Create a shopping basket that will contain one item.


                          Log on to client 800 of the SAP EBP System from the
                          browser:
                          User ID: BUYER-##
                          Client: 800



             Create a new shopping basket
             Select Shopping Basket → Create.


   4-2       Search in the ISA## catalog for the Speed Mice and add this item to your shopping
             basket.
             Select your catalog and Choose Go.
             Choose Enter to log on to the catalog with the given user.
             Select the area Accessories and place the Speed Mice in your shopping basket.
             Get a quotation for your shopping basket. Note down the quotation number,
             because it is needed later on.
             Choose Get Quotation and write down the number.
             Transfer your quotation.
             Choose the Transfer Quotation button.
             The item appears now in your Enterprise Buyer shopping basket.
   4-3       Order your shopping basket.
                        Choose Order.

(C) SAP AG                                   ADM130                                        3-79
             What is the shopping basket name?
             The name is generated by the system containing user name and time.

   4-4       Check the status of your shopping basket.
             What type of document has been created?
             Select Check status. Choose details. Select the tab History. You can find the
             shopping basket and a purchase requisition.
   4-5       Logon to the CRM Server and check the status and type of the created business
             object (use transaction Maintain Sales Order, CRMD_BUS2000115).
             Log on to the CRM server from the internet sales exercise with user CRM-##
             in client 801.
             Choose CRM→ Sales Orders → Maintain Sales Orders
             Menu: Business transaction → Open
             Enter the order number (Transaction no).
             Select the tab Status. You can see that the document is not yet distributed to
             the SAP R/3 backend system.
             Choose Status button. The document is just a quotation that may later on be
             converted into a sales order.




(C) SAP AG                                   ADM130                                          3-80
  System Administration


                      1. mySAP Technology              7. Interface Monitoring



                      2. Configuring Internet Sales    8. System Monitoring



                      3. Configuring EBUYER            9. Backup Scenarios


                                                       Appendix Installation Scenarios
                      4. System Administration
                                                                Transaction Codes


                      5. Software Logistics



                      6. Role Management


       SAP AG 2002




(C) SAP AG                                    ADM130                                     4-1
  System Administration



               Contents
                        Web server and IST administration
                        Sap J2EE Engine administration
                        SAP Bussiness Connector
                        administration
                        Requisite Catalog administration
                        IPC, IMS administration


               Objectives
                        At the end of this unit, you will be able to:
                        To administer IST, Web server, SAP J2EE engine,
                        SAP BC, Requisite Catalog, IPC and IMS



         SAP AG 2002




(C) SAP AG                                        ADM130                  4-2
  EBP/CRM Architecture Overview

   Frontend             Internet Middleware              Application   Backend
                                                         Middleware


     Internet
      Vendor
                         Enterprise Buyer                              R/3 OLTP
      Vendor's
     Web Server
                                                            EBP
                                                            EBP
                       Web Server        ITS       BC
     Internet
     Customer         Catalog Server

                                                                         BW
                        CRM Internet Sales
     Internet
     Employee                          SAP J2EE Engine

                       Web Server        ITS       BC
                                                            CRM
                                                            CRM
     Intranet              IPC          TREX      IMS                    APO
     Employee

       SAP AG 2002




(C) SAP AG                                 ADM130                                 4-3
  System Administration


                 ITS and Webserver
                                                      ITS and Webserver and Webserver
  ITS and Webserver ITS and Webserver

                                                                     ITS
      ITS and Webserver



                                                      SAP J2EE Engine

                                                      Business Connector
                                  ITS and Webserver




                                                      Requisite Catalog Administration

                                                      Internet Pricing & Configurator

                                                      Index Management Service/TREX


                                                      CRM Server Admin. and Error Handling
                      SAP AG 2002




(C) SAP AG                                                              ADM130               4-4
  Web Server Administration - Microsoft

  Microsoft Internet Information Server




                                                  Virtual Web Server Instance “ADM”



                                               Start Menu
                                               Start Menu
                                                   Start->Programs->Administrativ Tools
                                                    Start->Programs->Administrativ Tools
                                                   ->Internet Service Manager
                                                    ->Internet Service Manager
                                               Possible Tasks per Virtual Instance:
                                               Possible Tasks per Virtual Instance:
                                                   Start/Stop Instance
                                                   Start/Stop Instance
                                                   Port Configuration
                                                   Port Configuration
                                                   Access Configuration
                                                   Access Configuration
   Virtual Web Server Instance                     Create/Change/Delete Instances
                                                   Create/Change/Delete Instances
   for System TZ0

       SAP AG 2002




  Web server administration is performed using the Internet Information Server Management Console
  (Start --> Programs --> Adminstrative Tools --> Internet Service Manager).
  All virtual Web sites are listed.




(C) SAP AG                                  ADM130                                             4-5
  Identify ITS Admin Instance URL

  Microsoft Internet Information Server




                                                  Use right mouse->Properties->Advanced
                                                  to identify ITS Admin Instance URL and Port




       SAP AG 2002




  Each virtual web server has an assigned port.
  The diagram shows the virtual web server ADM on host iwdf8600 which is configured on port 1080.
  Additionally, the host header name igadm8600.wdf.sap-ag.de is specified in the Advance Multiple
  Web Site Configuration.
  The URL to access this web server is: http://igadm8600.wdf.sap-ag.de:1080.




(C) SAP AG                                  ADM130                                             4-6
  Internet Information Server - Logs




                                        Error messages and warnings: Use Windows Event
                                        Error messages and warnings: Use Windows Event
                                        Viewer
                                        Viewer
                                            Check System and Application EventLog
                                            Check System and Application EventLog
                                        Log Directory:
                                        Log Directory:
                                            %SystemRoot%\system32\Log files\W3SVC
                                            %SystemRoot%\system32\Log files\W3SVC



       SAP AG 2002




  The web server error messages are not forwarded to an SAP System.
  The web server generates error messages in the Windows Event Viewer. Messages can be created in
  either:
     The System Event Log
     The Application Event Log
  Additionally, the web server writes error messages to directory:
  %SystemRoot%\system32\Log files\W3SVC (%SystemRoot% is for example C:\WINNT)




(C) SAP AG                                  ADM130                                             4-7
  ITS Administration Server Logon

                                                                     ITS Admin Instance URL




                                        Generic URL to launch logon screen:
                                        Generic URL to launch logon screen:
                                             http://<hostname.domain>:<port>/scripts/wgate/admin/!
                                             http://<hostname.domain>:<port>/scripts/wgate/admin/!
                                        Default User: itsadmin/init
                                        Default User: itsadmin/init
                                        Possible Tasks per Virtual ITS Instance:
                                        Possible Tasks per Virtual ITS Instance:
                                             Start/Stop Wgate and/or Agate
                                             Start/Stop Wgate and/or Agate
                                             SAP Logon Parameters (user, client, logon group, …)
                                             SAP Logon Parameters (user, client, logon group, …)
                                             Monitor Performance
                                             Monitor Performance
                                             View Traces/Log Files
                                             View Traces/Log Files
                                             Create/Change/Delete ITS users
                                             Create/Change/Delete ITS users
       SAP AG 2002




  The main tool for the SAP ITS and Web server administration is the Web-based ITS Administration
  tool.
  This tool can be started by calling the Web page:
  http://<server>:<port>/scripts/wgate/admin/!
     Example: http://igadm8600.wdf.sap-ag.de:1080/scripts/wgate/admin/!
  This tool enables you to:
     Start or stop several ITS servers.
     Modify the ITS configuration.
     Monitor the ITS servers.




(C) SAP AG                                  ADM130                                                 4-8
  Virtual ITS Instance Restart




                                                                Select Control




                                                                      Choose to Restart AGate




    Restarting the Agate is also possible by restarting the service: “ITS Manager – SID”

       SAP AG 2002




  Several ITS instances can be installed on the same host.
  The ITS Administration Tool (ITS instance ADM) can be used to start and stop all other ITS
  instances running on the same host. In our example, ITS instances ADM and TZ0-800 are installed.
    The entry ITS Manager – TZ0-800 refers to the AGATE of instance TZ0-800.
    The entry W3SVC/4 refers to the WGATE of instance TZ0-800.




(C) SAP AG                                   ADM130                                              4-9
  ITS Parameters


                                                               MaxSession:
                                                               Max. # connections to R/3 System
                                                               MaxWorkThreads:
                                                               Max. # processing threads
                                                               MinWorkThreads:
                                                               Min. # processing threads at ITS start

                                                               TimeoutPercentage:
                                                               When all sessions are full, timeout is
                                                               reduced to this % of time in service file
                                                               IncAGates:
                                                               Increment # AGates running by this
                                                               number when last WGate is full
                                                               MaxAGates:
                                                               Max. # AGates allowed to run on
                                                               system
                                                               MinAGates:
                                                               Starting # AGates on system
                                                                    WGate parameters used in very high
                                                                    load situations when server has a lot
                                                                    of memory (> 2 GB RAM)
   Select ITS Instance->Configuration->Performance


       SAP AG 2002




  The ITS Administration instance can also be used to configure ITS parameter.
  For a detailed description of the parameters refer to the ITS Tuning Guide (downloadable from
  www.saplabs.com/its).
  Also refer to SAP note 375065 (ITS configuration parameters).




(C) SAP AG                                    ADM130                                                    4-10
  ITS Log Files




                                       Use administrative instance to view log files
                                       Use administrative instance to view log files
                                       Directory:
                                       Directory:
                                           <ITS Drive>:\Program Files\SAP\ITS\2.0\<SID>\logs
                                           <ITS Drive>:\Program Files\SAP\ITS\2.0\<SID>\logs



       SAP AG 2002




  Housekeeping of the Web server log files can be adjusted using tab Properties - Web Site on the
  virtual instance.




(C) SAP AG                                    ADM130                                                4-11
  Administration Overview - Group Monitoring


        The summary information includes:
                 Available resources on the machine
                 Relative resource usage by individual ITS instances




       SAP AG 2002




  The ITS administration function provides group monitoring capability.
  Use this procedure to obtain cumulative information about all ITS instances running on the server.
  In the main frame, choose overview to see summary information for all ITS instances. Each group is
  represented as a line item along with system indicators. The summary information includes:
    Available resources on the machine.
    Relative resource usage by individual ITS instances.
  To branch directly to performance details for a particular ITS instance, click on an instance in the
  ITS column.




(C) SAP AG                                     ADM130                                              4-12
  Control ITS Instance


      The control interface provides easy access to starting and
      stopping an ITS instance
           Restart - Stops and restarts the ITS instance
           Refresh - Updates and redisplays the information




       SAP AG 2002




  Use this procedure to start or stop any ITS instance (except the instance running ITS administration).
  Before stopping an ITS instance, you need to know whether there are currently sessions running it.
  To check this, use the current performance function.
  The control frame provides command buttons for restarting and refreshing the ITS instance. If an
  instance is currently running, a green light is on. If not, a red light appears.
  If you enable or disable tracing for the WGate component, you must restart the WGate to activate
  your changes. For all other components, your changes take effect immediately (without restart).
  You cannot stop the ITS instance that runs ITS administration.




(C) SAP AG                                     ADM130                                               4-13
  ITS User Maintenance




                                                                               User specified:
                                                                               • Login
                                                                               • Password


             Global.srvc
                                                                                    Login
                                                                                   Context


         MyServices.srvc

       SAP AG 2002




  This function allows you to control access to ITS administration by setting up users and assigning
  different levels of access to the ITS instances installed. To manage users in user management, you
  must log on with the main administration account itsadmin.
  In user management, you can:
     Add new users
     Change existing users
     Reset passwords
     Delete users
  When adding new users,specify a user name and an initial password, which can be modified by the
  user.
  You can give users access to any ITS instance with either administrator or view-only authorization.
  When users log on, they see only those ITS instances to which they have access.
  All ITS administration user information is maintained in the registry, which can only be viewed by
  the itsadmin account.




(C) SAP AG                                    ADM130                                              4-14
  System Administration


                 SAP J2EE Engine               ITS and Webserver
  SAP SAP J2EE Engine Engine



                                               SAP J2EE Engine
      J2EE Engine SAP J2EE




                                                                      SAP J2EE Engine

                                               Business Connector
                             SAP J2EE Engine




                                               Requisite Catalog Administration

                                               Internet Pricing & Configurator

                                               Index Management Service/TREX


                                               CRM Server Admin. and Error Handling
                   SAP AG 2002




(C) SAP AG                                                      ADM130                  4-15
  EBP/CRM Architecture Overview

   Frontend             Internet Middleware              Application   Backend
                                                         Middleware


     Internet
      Vendor
                         Enterprise Buyer                              R/3 OLTP
      Vendor's
     Web Server
                                                            EBP
                                                            EBP
                       Web Server        ITS       BC
     Internet
     Customer         Catalog Server

                                                                         BW
                        CRM Internet Sales
     Internet
     Employee                          SAP J2EE Engine

                       Web Server        ITS       BC
                                                            CRM
                                                            CRM
     Intranet              IPC          TREX      IMS                    APO
     Employee

       SAP AG 2002




(C) SAP AG                                 ADM130                                 4-16
  Starting the SAP J2EE Engine

               Client
                                 Start:

            Dispatcher
                                   1. Dispatcher             SAP J2EE Engine
                                   2. Server
      Server            Server
        1                 2




        SAP AG 2002




  The server startup procedure depends on the installation type (cluster or server).

  Cluster:
  • First start the dispatcher by choosing
    Start Program Files In-Q-My AppServer Dispatcher
    (or execute <In-Q-My-Root>\cluster\dispatcher\go.bat)
  • Then start all servers by choosing
    Start Program Files In-Q-My AppServer Server
    (or execute <In-Q-My-Root>\cluster\<server-name>\go.bat)

  Stand-alone:
  • Start the stand-alone server by choosing
    Start Program Files In-Q-My AppServer Stand Alone Server
    (or execute <In-Q-My-Root>\cluster\alone\go.bat)

  Startup problems are reported in the server console.

  Dispatcher and Servers can be implemented as services.




(C) SAP AG                                      ADM130                                 4-17
  SAP J2EE Engine Server Configuration




      Four methods to configure the server:
             Administration Tool (GUI)
                                                                                        Client

             Telnet
             Server console                                                         Dispatcher


             Properties files
                                                                              Server             Server
                                                                                1                  2



      Properties files:                                          Startup        Properties
                                                                                       Files
             Low level configuration (ports, logging)
             Configuration by properties files                               SAP J2EE
             needs no running server                                         Engine



       SAP AG 2002




  SAP J2EE Engine Application Server contains a web server (http). If you are already running
  another http server on port 80, you have to change the http port number of SAP J2EE Engine.
     Use the Administration Tool after starting the server.
     Edit the http service properties file (preferred) Port=80.
  http service properties file: properties:
     Cluster: <In-Q-My-Root>\cluster\dispatcher\services\http\properties
     Stand-alone: <In-Q-My-Root>\alone\services\http\properties
  SAP J2EE Engine uses several other ports (for example, for remote administration), bean data
  replication in a cluster or load balancing. Depending on other installed software or the OS
  configuration, there may be port conflicts that prevent the SAP J2EE Engine from starting. You can
  individually configure every port SAP J2EE Engine uses. Port numbers are configured in properties
  files:
     …\http\properties or …\managers\settings\ClusterManager.properties
     Search for xxxxPort=1234 definitions, e.g. JoinPort=2077, OpenPort=2055, OpenCPort=1055
  Port Settings in a Cluster Setup:
     Manager ports: <In-Q-My-Root>\cluster\dispatcher\managers\settings\…
     Ports of services (like http): <In-Q-My-Root>\cluster\dispatcher\services\<service-name>\…
  Port Settings in Stand-alone Setup:
     Manager ports: <In-Q-My-Root>\alone\managers\settings\…
     Ports of services (like http): <In-Q-My-Root>\alone\services\<service-name>\…




(C) SAP AG                                    ADM130                                                      4-18
  Visual Administration Tool


     Login to the SAP J2EE Engine




       SAP AG 2002




  Use the Administration Tool to administrate (and configure) a running cluster or server. You can
  administrate local and remote servers. Start the Administration Tool by choosing
  Start Program Files In-Q-My AppServer Administrator
  (or execute <In-Q-My-Root>\admin\go.bat).
  Log in using an user name with administrator authorization.
  Log on to the server (connect to dispatcher node):
    Use name or IP of remote server or localhost for local server.
    Change port if not default.
    Choose transport protocol:
    - No layer: use Java RMI / P4
    - HTTP Tunneling: Allows communication through proxies and firewalls
    - SSL: Provides privacy over the Internet using cryptographic security
    All settings (except of the password) are saved for later use.




(C) SAP AG                                    ADM130                                                 4-19
  Cluster, Managers, and Services




                                                                                         .
                                                                                         .
                                                                                         .




                                                                                         .
                                                                                         .
                                                                                         .


       SAP AG 2002




  Use the Visual Administration Tool to administrate the dispatcher node or individual servers in a
  cluster configuration. The two configurable groups to be administered are: Managers and Services.
  Managers for the SAP J2EE Engine:
     ClusterManager: Manages the communication between nodes in the cluster.
    Properties (not available through GUI)include the JoinPort: Port on which dispatcher/server listens
    for connections; OpenPort: Through this port, connections between cluster elements are
    established; and the ClusterElementId: Unique identification number of this cluster element
     IpVerificationManager: Manages list of hostnames to allow or deny access to the corresponding
     node. Properties: HostsFileName: managers/ipverify/hosts.txt
     LogManager: Easy to use non-distributed system for recording occurred events
     MemoryManager: Stores information about the level of memory usage
      Properties: 64MB < MaxMemory < Physical Memory
     ThreadManager: Starts and manages threads in the Java Virtual Machine
     Properties: MinThreadCount < MaxThreadCount < OS maximum
  Services for the SAP J2EE Engine
     Security Service: Provides user and group management
     DBPool Service: Creates and stores DB connections so that they can be reused.
     EISConnector Service: Manages communications between SAP J2EE Engine and EIS.
     Monitor Service: Allows for obtaining information about system current status.
     Log Service: Provides a distributed system for recording significant events (log messages:
     emergency (0) to debug (7)).
     Deploy Service: As the core service, it manages the deployment of J2EE applications on the
     corresponding containers and across the cluster.
     EJB Service:Manages all Enterprise Java Beans, session beans / entity beans.


(C) SAP AG                                     ADM130                                              4-20
  Service Administration




             Three general tabs for every service



             Several services have an additional runtime configuration tab



                 Services with runtime options for example
                      Crypt, DBPool, Deploy, EISConnector, EJB, HTTP, Monitor,
                      Naming, and Security




       SAP AG 2002




  Properties:
    Configuration of services properties
    Same as properties file in the folder corresponding to the service
  Control descriptor:
    General settings
    Security
    Distribute
    Properties, Additional
  Log Viewer:
    All significant events that occure in a service are written to corresponding log files
  Runtime:
    Configuration of service dependent runtime options




(C) SAP AG                                      ADM130                                       4-21
  Security Service




       SAP AG 2002




  Control the Security Service manages Users and Groups. You can add and change Users that can log
  on to the SAP J2EE Engine.
  Non-visual (automatic) group configuration is possible:
    Define groups in <In-Q-My-Root>\tools\usertool.xml
    Use <In-Q-My-Root>\tools\usertool.bat to add groups defined in the xml file to
    the running server




(C) SAP AG                                   ADM130                                           4-22
  DBPool Service




        SAP AG 2002




  The DBPool Services creates and stores DB connections so that they can be reused. It Uses JDBC drivers to
  communicate with databases.

  General tab:
    Pool name: The name of the database pool, used during deployment
    Database URL: JDBC driver specific connection string
    User/Password: user and associated password used to connect
    Use Add Driver to add additional JDBC drivers
    Assign driver name (driver factory class)
    Choose .jar file containing driver and support files
  Additional tab:
    Configure driver specific properties
    Connection Pooling properties
    Default number of connections
    Initial number of connections (at pool creation time)
    Maximum number of connections
    Expire timeout (the time in seconds after which an unused connection will be removed from the pool)
    Expire thread (the time in seconds at which threads are started, to check for expire timeout)
    It is recommended that Connection Pooling is not used when the driver in use supports pooling itself

  Non-visual (automatic) configuration of DBPool service is possible with DBTool:
    Define pools and drivers in <In-Q-My-Root>\tools\dbtool.xml
    Use <In-Q-My-Root>\tools\dbtool.bat to add the information defined in the xml file to the
    running server



(C) SAP AG                                        ADM130                                                   4-23
  EISConnector Service




                              Property                           Value
                              ClientNumber                       see R/3 login (“Client”)
                              UserName, Password                 see R/3 login
                              Language
                              ServerName                         a specific R/3 server
                              SystemNumber                       for example, B20, CSN
                              MessageServerName                  see R/3 login
                              SystemName                         for example, PUBLIC
                              GroupName                          use group instead of above
                                                                 server definition
                              GatewayServerName                  optionally
                              GatewayServiceNumber
       SAP AG 2002




  The EISConnector Service manages communications between the SAP J2EE Engine and Enterprise
  Information Systems (EIS). This service uses the J2EE Connector Architecture. The J2EE Connector
  Architecture describes how Enterprise Information Systems (EIS) can be integrated in a J2EE server.
  It is part of the J2EE 1.3 specification. EIS vendors must provide a Resource Adapter for their
  systems.
  Installation:
     First install SAP Java Connector (JCo). The EISConnector Service is an J2EE 1.3 Abstraction
     Layer for the Jco.
     Use the Visual Administration Tool to add the SAPAdapter.rar file to EISConnector service.
     Configure the Logon Parameters (like hostname, username, and password) according to your SAP
     System.




(C) SAP AG                                    ADM130                                             4-24
  Log Service


  Every Service has
  a Log Tab


   #     Log level         File                       Note
   0     Emergency         EMERGENCY.log              system is unusable
   1     Alert             ALERT.log                  action must be
                                                      taken immediately
   2     Critical          CRITICAL.log
   3     Error             ERROR.log
   4     Warning           WARNING.log
   5     Notice            NOTICE.log                 normal but
                                                      significant events
   6     Info              INFO.log
   7     Debug             DEBUG.log

        SAP AG 2002




  The Log Service is responsible for storing messages associated with a particular service.




(C) SAP AG                                     ADM130                                         4-25
  HTTP Service




       SAP AG 2002




  The HTTP Service handles requests received from Web clients over the HTTP protocol.
    Supports HTTP 1.1 specification
    Supports virtual hosts
  Cluster settings
    HTTP Port
    SSL (Secure Socket Layer) Port for HTTPS
  Server settings
    Hostname (primary host)
    Additional virtual hostnames (Note: All added virtual hosts must be registered with local or global
    DNS Servers, in order to be located when such a host is requested)
    Hostname values
    - Hostname
    - FQDN (Fully Qualified Domain Name)
    - IP address (dotted quad notation)
  Properties tab
    Common Log Format
    - Called CLF
    - Apache server log file format
    - Many analysis tools available
    Use cache: Cache requested files (performance)
    Directory list: Enable or disable directory browsing (security)




(C) SAP AG                                     ADM130                                              4-26
  Deploy Service


  Necessary for Deployment of new Java Applications




       SAP AG 2002




  The Deploy Service manages the deployment of J2EE applications on the corresponding containers
  and across the cluster. It allows direct deployment of applications .ear files.
  The Deployment Tool is discussed in the Software Logistics Chapter.




(C) SAP AG                                  ADM130                                           4-27
  Monitor Service


  Necessary for Monitoring the SAP J2EE Engine




         Runtime tab provides information about the current
             status of cluster elements, their workload
                    and response time behavior

       SAP AG 2002




  The Monitoring service delivers Monitoring Information for controlling of the SAP J2EE Engine.
  The Monitoring itself is discussed later in unit System Monitoring. Start the agent with
  “monitor.bat”.

  Dispatcher and server nodes monitors:
    Thread Monitor
    Memory Monitor

  Dispatcher nodes only monitors:
    Connections Monitor
    Ports Monitor

  Server nodes only monitors:
    HTTP Monitor
    Session Monitor




(C) SAP AG                                   ADM130                                            4-28
  Non-Visual Administration



      Dispatcher or Server Console




       SAP AG 2002




  Administer local servers with console:
   Use the dispatcher or server console
   Type man for a command overview
   Default command groups: ADMIN and SYSTEM
   Use add <groupName> to activate other groups

  Administer remote servers with telnet:
   Connect to the dispatcher node
   telnet <hostname or IP> <portnumber>
   Default port is 2323 (configured through telnet service properties file)
   Same commands as with console shell
   One additional command: JUMP <ClusterElement ID>




(C) SAP AG                                     ADM130                         4-29
  System Administration


                 Business Connector
                                                        ITS and Webserver
  Business ConnectorBusiness Connector
     Business Connector



                                                        SAP J2EE Engine

                                                        Business Connector Connector
                                                                      Business
                                   Business Connector




                                                        Requisite Catalog Administration

                                                        Internet Pricing & Configurator

                                                        Index Management Service/TREX


                                                        CRM Server Admin. and Error Handling
                       SAP AG 2002




(C) SAP AG                                                                ADM130               4-30
  EBP/CRM Architecture Overview

   Frontend             Internet Middleware              Application   Backend
                                                         Middleware


     Internet
      Vendor
                         Enterprise Buyer                              R/3 OLTP
      Vendor's
     Web Server
                                                             EBP
                                                             EBP
                       Web Server        ITS       BC
     Internet
     Customer         Catalog Server

                                                                         BW
                        CRM Internet Sales
     Internet
     Employee                          SAP J2EE Engine

                       Web Server        ITS       BC
                                                             CRM
                                                             CRM
                                                             CRM
     Intranet                                               Server
                           IPC          TREX      IMS                    APO
     Employee

       SAP AG 2002




(C) SAP AG                                 ADM130                                 4-31
  SAP BC Administration Tool




                                    Generic URL to launch BC Administrator screen:
                                    Generic URL to launch BC Administrator screen:
                                         http://<hostname>:5555
                                         http://<hostname>:5555
                                    Default User: Administrator/manage
                                    Default User: Administrator/manage
                                    To start the SAP Business Connector Server:
                                    To start the SAP Business Connector Server:
                                         Choose Start
                                         Choose Start    Programs
                                                         Programs      SAP BC
                                                                        SAP BC    SAP Business Connector Server
                                                                                  SAP Business Connector Server
                                    To shut down the server:
                                    To shut down the server:
                                         Open the Server Administrator if it is not already open.
                                          Open the Server Administrator if it is not already open.
                                         Select Shutdown on the navigation panel.
                                          Select Shutdown on the navigation panel.
   Navigation Panel
                                         Select whether you want the server to wait before shutting down or to
                                          Select whether you want the server to wait before shutting down or to
                                         shutdown immediately.
                                          shutdown immediately.
                                         Choose Shutdown.
                                         Choose Shutdown.
       SAP AG 2002




  The Server Administrator is an HTML-based utility used to administer the SAP Business Connector
  Server. It allows you to monitor server activity, manage user accounts, make performance
  adjustments, and set operating parameters. You can run the Server Administrator from any browser-
  equipped workstation on your network (the Server Administrator is a browser-based application).
  To start the SAP Business Connector Server:
  Choose Programs SAP BC SAP Business Connector Server from the windows start menu.
  To shut down the server:
    1. Open the Server Administrator if it is not already open.
    2. Select Shutdown on the navigation panel.
    3. Select whether you want the server to wait before shutting down or to shutdown immediately.
  Wait for active, non-administrator sessions to complete. Specify the number of minutes you want the
  SAP Business Connector Server to wait before shutting down. It then begins monitoring user activity
  and automatically shuts down when all non-administrator sessions complete or when the time you
  specify elapses (whichever comes first). Shutdown immediately: the server and all active sessions
  terminate immediately.
    4. Choose Shutdown.
  Before you shutdown or restart the server, you can view the sessions that are currently active:
  Select Statistics on the navigation panel and choose tab page server stats. In section General, select
  the value in Seats/Limit field.




(C) SAP AG                                      ADM130                                                            4-32
  SAP BC Administration

       SAP BC Configuration file:
             sapbc\server\config\server.cnf
             Most parameters can be set with the Server Administrator
             Certain parameters can only be set by editing the server.cnf file
       SAP BC Logs
             Directory: sapbc\server\log, to find the Log Files choose:
                  Statistics     Logs (Audit, Error, Server, Session, Stats)
                  Settings      logging   loglevel 1 .. 10 (default is 4)
       SAP BC is implemented as service “Webmethods Server”
             SAP BC Directory <drive:>\sapbc\Server
             Set startup type of service to automatic
       Command line tool to start the server:
             Windows:          bin\server.bat –switch
       Check whether BC is running
             Connect to BC administration tool using web browser client
             BC is not running if the following error messages occur:
             "Cannot open the Internet site http://mysap02:5555"
             "A connection with the server could not be established"

       SAP AG 2002




  Every SAP Business Connector Server is installed with a predefined user account called
  Administrator. By default, this user is the only one who can perform administrative tasks with the
  System Administrator. The predefined password assigned to the Administrator user account is
  manage. Change this password immediately after installing the SAP Business Connector Server.
  To start the Server Administrator:
  1. Start your browser.
  2. Point your browser to the host and port where the SAP Business Connector Server is running.
     If the server is running on the default port on the same machine where you are
     If you just installed the SAP Business Connector Server, you can use the following default
     alues:(case sensitive)
              User Name: Administrator
              Password: manage




(C) SAP AG                                         ADM130                                          4-33
  SAP BC: Web Automation Settings


      Web Automation settings control how the SAP BC handles outbound http
      requests. Set the web automation defaults:
          Select Settings on the navigation panel
          Select tab page General Settings
          Choose Edit these Settings
          Set the Web Automation parameters
          Choose Submit
      Important Parameters:
          Max Redirects: Number of times to allow a request to be redirected before the
          server returns an I/O exception to the client (standard after installation: 5).
          Timeout: Number of seconds the server waits for a response from the target
          server before retrying the service or returning a timeout error to the client
          (standard after installation: 3 minutes)
          Type: Number of times the server retries a service that has timed out before
          returning an exception to the client (standard after installation: 0).
          Session Timeout: Number of minutes you want the server to wait before
          terminating an idle session (standard after installation: 10 minutes)

       SAP AG 2002




  The Web Automation parameters control how the server presents and processes outbound HTTP and
  HTTPS requests (requests that the SAP Business Connector Server issues on behalf of a client). The
  parameters control behavior such as how long the server waits for a response, how many times it
  retries a failed request, and so forth. A developer can override some of the server’s Web automation
  defaults at run time.
  The Max Redirects parameter specifies the number of times that the SAP BusinessConnector Server
  allows a request to be redirected (i.e., automatically sent to another URL) by the target server. If a
  request exceeds the specified number of redirections, the SAP Business Connector Server
  immediately returns an I/O exception.
  The Timeout parameter specifies the length of time the server waits for a response from a target
  server. If the SAP Business Connector Server does not receive a response in the allotted time, it
  retries the request up to the number of times specified by the Retries parameter. When it exceeds the
  number of allowed retries, it returns an exception.
  The Retries parameter specifies the number of times the server reissues a request that has timed out
  (one from which it did not receive a response within the time period specified by the Timeout
  parameter). Set Retries to a value greater than zero if you want the server to retry (reissue) timed-out
  requests.
  Session Timeout parameter is used to specify the length of time you will allow an idle session to
  remain active (in other words how long you want the server to wait before terminating an idle
  session).




(C) SAP AG                                      ADM130                                               4-34
  System Administration

  Requisite Catalog Administration Administration
   Requisite Catalog Administration
             Requisite Catalog Administration
                                                                                 ITS and Webserver
                       Requisite Catalog




                                                                                 SAP J2EE Engine
                                              Requisite Catalog Administration




                                                                                 Business Connector


                                                                                 Requisite Catalog Administration
                                                                                                 Requisite Catalog Administration

                                                                                 Internet Pricing & Configurator

                                                                                 Index Management Service/TREX


                                                                                 CRM Server Admin. and Error Handling
                             SAP AG 2002




(C) SAP AG                                                                                         ADM130                           4-35
  EBP/CRM Architecture Overview

   Frontend             Internet Middleware              Application   Backend
                                                         Middleware


     Internet
      Vendor
                         Enterprise Buyer                              R/3 OLTP
      Vendor's
     Web Server
                                                            EBP
                                                            EBP
                       Web Server        ITS       BC
     Internet
     Customer         Catalog Server

                                                                         BW
                        CRM Internet Sales
     Internet
     Employee                          SAP J2EE Engine

                       Web Server        ITS       BC
                                                            CRM
                                                            CRM
     Intranet              IPC          TREX      IMS                    APO
     Employee

       SAP AG 2002




(C) SAP AG                                 ADM130                                 4-36
  Java Server and Requisite

  Servlet Engine for Web Server:
             JRun Pro
             WebSphere
             Servlet Exec
             Servlet Engine SAP J2EE Engine
             Any others that support Java Servlet API 2.1




       SAP AG 2002




  The software will run on a single server that is supporting both the database and the web server. For
  optimal performance, a two-tier configuration is recommended, with one server running the database
  and another server running the web server and java servlet engine.
  The components provided in the Requisite Installation CD-ROM are as follows:
    - ReadMe file (.txt and HTML)
    - Catalog application server (Java jar file), application images, configuration files, and HTML
       templates
    - Database install scripts
    - SqlServer 7.0 Inet JDBC driver
    - Oracle JDBC Thin Drivers
    - Online HTML help for the Catalog Engine and eContent Manager
    - Installation Guide




(C) SAP AG                                     ADM130                                              4-37
  Requisite Online Catalog in ECManager Mode




      Generic URL to launch Administrator screen:
      Generic URL to launch Administrator screen:
          http://<hostname.domain>/requisite/sap/login.htm
          http://<hostname.domain>/requisite/sap/login.htm
      Default User: author/author (ECManager)
      Default User: author/author (ECManager)
      Default User: guest/guest (BugsEye)
      Default User: guest/guest (BugsEye)
      JRun servlet engine is implemented
      JRun servlet engine is implemented
      as Windows NT service
      as Windows NT service
      Typical Administration Tasks:
      Typical Administration Tasks:
          Examine log information
          Examine log information
          Adjust paramters
          Adjust paramters
          Configure data loading
          Configure data loading




       SAP AG 2002




  Use the requisite Web Administration Tool to Administer the content of the catalogs, users, and so
  on.
  The database is started and stopped using external tools.




(C) SAP AG                                    ADM130                                              4-38
  System Administration

    Internet Pricing & Configurator
                                                    Internet Pricing & Configurator

                                                                                      ITS and Webserver

                                                                                      SAP J2EE Engine
  Internet Pricing & Configurator
                                  Internet Pricing & Configurator




                                                                                      Business Connector

                                                                                      Requisite Catalog Administration


                                                                                      Internet Pricing & Configurator
                                                                                                        Internet Pricing & Configurator
                                                                                      Index Management Service/TREX


                                                                                      CRM Server Admin. and Error Handling
                                 SAP AG 2002




(C) SAP AG                                                                                              ADM130                            4-39
  EBP/CRM Architecture Overview

   Frontend             Internet Middleware              Application   Backend
                                                         Middleware


     Internet
      Vendor
                         Enterprise Buyer                              R/3 OLTP
      Vendor's
     Web Server
                                                            EBP
                                                            EBP
                       Web Server        ITS       BC
     Internet
     Customer         Catalog Server

                                                                         BW
                        CRM Internet Sales
     Internet
     Employee                          SAP J2EE Engine

                       Web Server        ITS       BC
                                                            CRM
                                                            CRM
     Intranet              IPC          TREX      IMS                    APO
     Employee

       SAP AG 2002




(C) SAP AG                                 ADM130                                 4-40
  IPC Service Manager



                                                                   Control and watch
                                                              IPC Server Service and
                                                             IPC Data Loader Service




       SAP AG 2002




  By default, IPC consists of the following services:
    - SAP IPC Server
    - SAP SPC Loader Service
    They are visible under:
    - IPC service manager
    - NT service manager
  They can also be controlled from the NT service manager.




(C) SAP AG                                   ADM130                                    4-41
  IPC Administration




                                              Launch the IPC Administrator from the
                                              Launch the IPC Administrator from the
                                              Windows Start menu as shown
                                              Windows Start menu as shown
                                              IPC Administration is used for:
                                               IPC Administration is used for:
                                                   Creating database tables
                                                   Creating database tables
                                                   Specifying the default databases to be used
                                                   Specifying the default databases to be used
                                                   The default connection parameter
                                                   The default connection parameter
                                                   The frequency of pricing updates
                                                   The frequency of pricing updates
                                                   The default data specification
                                                   The default data specification

       SAP AG 2002




  Start the Internet Pricing and Configurator Administrator by choosing
  Start Programs SAP Internet Pricing and Configurator Administrator.
  The Internet Pricing and Configurator Administrator:
    Allows you to configure the database connection to the IPC.
    Allows you to configure the pricing component of the IPC.
    Provides default parameters and default header attributes for documents created with the IPC. You
    can select the default values that are required.
    Allows you to supply parameters for the server component of the IPC.
  The IPC registers itself at the gateway of the CRM System.
    Default RFC destination name is IPC
  As of 2.0C, IPC is integrated in SAP CRM database.




(C) SAP AG                                    ADM130                                             4-42
  IPC Administrator - Server

                                                                         IP port used for the
                                                                         client/server
                                                                         communication
                                                                         of the IPC

                                                                         Log file of the IPC Server


                                                                         Settings for remote
                                                                         administration of the
                                                                         IPC server;
                                                                         default password is
                                                                         IPC




       SAP AG 2002




  You can use the IPC Administrator to configure your database connection to the IPC.
  It is possible to configure the pricing component of the IPC.
  You can provide default parameters and default header attributes for the documents created with the
  IPC.
  You can use the IPC Administrator to supply parameters for the server component of the IPC. If you
  use the IPC in a local (stand alone, non-internet) environment you do not need to set any server
  parameters.




(C) SAP AG                                    ADM130                                             4-43
  IPC Administrator - Database

                                                                        Create database
                                                                        scheme on
                                                                        empty database
                                                                        (IPC Data Loader
                                                                        download
                                                                        needed
                                                                        afterwards!)

                                                                         Settings to
                                                                         access
                                                                         the IPC
                                                                         database

                                                                         IPC database
                                                                         supports
                                                                         client fields
                                                                         in pricing
                                                                         tables;
                                                                         IPC Server
                                                                         runs against
                                                                         one client!

                                                                         IPC Server
                                                                         runs against
                                                                         one database
                                 Login is necessary when using different active database
       SAP AG 2002




(C) SAP AG                       ADM130                                                4-44
  IPC Administrator - Pricing Parameters

                                           Settings for the
                                           buffering of pricing
                                           data (database records
                                           might been read only
                                           every 24 hours with the
                                           default settings)

                                           Implement Java package
                                           where the user exits for
                                           pricing




       SAP AG 2002




(C) SAP AG                    ADM130                                 4-45
  System Administration

  Index Management Service/TREX Service/TREX
     Index Management Service/TREX

                                                                               ITS and Webserver

                                                                               SAP J2EE Engine
                     Index Management




                                                                               Business Connector
                                               Index Management Service/TREX




                                                                               Requisite Catalog Administration

                                                                               Internet Pricing & Configurator


                                                                               Index Management Service/TREX
                                                                                         Index Management Service/TREX

                                                                               CRM Server Admin. and Error Handling
                                     SAP AG 2002




(C) SAP AG                                                                                       ADM130                  4-46
  EBP/CRM Architecture Overview

   Frontend             Internet Middleware              Application   Backend
                                                         Middleware


     Internet
      Vendor
                         Enterprise Buyer                              R/3 OLTP
      Vendor's
     Web Server
                                                            EBP
                                                            EBP
                       Web Server        ITS       BC
     Internet
     Customer         Catalog Server

                                                                         BW
                        CRM Internet Sales
     Internet
     Employee                          SAP J2EE Engine

                       Web Server        ITS       BC
                                                            CRM
                                                            CRM
     Intranet              IPC          TREX      IMS                    APO
     Employee

       SAP AG 2002




(C) SAP AG                                 ADM130                                 4-47
  Index Management Service

     Schedule report RSTIRIDX as a daily
     background job
     The report RSTIRIDX starts indexing
     and deindexing the chosen
     documents and logs indexing errors
     in the productive system.
     The selected recipient can read the
     contents of the report via
     transaction SO01.
     If an error occurs, it should be
     verified in the application log and in
     the IMS monitoring.
     Choose transaction SKPR07
     to check errors in the KPRO IMS
     Monitor


    Choose Problem cases



  Choose Marked Documents


       SAP AG 2002




  A list of documents that are marked for indexing or deindexing is displayed. The following
  information with respect to the marked documents is available:
     Client
     Name of the index category (GUID of 32 characters)
     Document class
     Document language
     Type of procedure (I = Indexing, D = Deindexing)
     Number of documents marked for this index category
  If you want to get details about the marked documents, select the corresponding entry from the list
  and choose Appearance.
  If an error occurred while indexing or deindexing a document, it will be marked once again for the
  same procedure. If the same error appears several times, this error possibly does not allow any
  indexing or deindexing at all. These documents should be selected from the list of marked
  documents and deleted.
  Documents that could not be indexed or deindexed the very first time (including those documents
  that were manually deleted from the list of marked documents) will be handled as problem cases. If
  you want to get a list of these problem cases, choose Problem cases in transaction SKPR07 and
  choose Enter.




(C) SAP AG                                    ADM130                                              4-48
  System Administration

    CRM Server Admin and Error Handlling
                           CRM Server Admin and Error Handling
  CRM Server Adminand Error Handling


                                                                                                       ITS and Webserver

                                                                                                       SAP J2EE Engine
                                                                 CRM Server Admin and Error Handling




                                                                                                       Business Connector

                                                                                                       Requisite Catalog Administration

                                                                                                       Internet Pricing & Configurator

                                                                                                       Index Management Service


                                                                                                                          and Error Handling
                                                                                                       CRM Server AdminAdmin and Error Handling
                                                                                                               CRM Server
                                              SAP AG 2002




(C) SAP AG                                                                                                               ADM130                   4-49
  EBP/CRM Architecture Overview

   Frontend             Internet Middleware              Application   Backend
                                                         Middleware


     Internet
      Vendor
                         Enterprise Buyer                              R/3 OLTP
      Vendor's
     Web Server
                                                            EBP
                                                            EBP
                       Web Server        ITS       BC
     Internet
     Customer         Catalog Server

                                                                         BW
                        CRM Internet Sales
     Internet
     Employee                          SAP J2EE Engine

                       Web Server        ITS       BC
                                                            CRM
                                                            CRM
     Intranet              IPC          TREX      IMS                    APO
     Employee

       SAP AG 2002




(C) SAP AG                                 ADM130                                 4-50
  Middleware versus System Administration


                                        All monitoring done
                      Download          on a daily basis
                      administration
                                                         R/3 Basis System
        All business tasks necessary to                  Administration
        operate the Mobile Sales / Mobile
        Service system on a daily basis

                                       Troubleshooting
             Replication                                      Network
             administration                                   administration
                                       Errorhandling
                                                       (Customizing)


                Middleware Administration            System Administration

                                   No clear dividing line
                                   between the two areas
       SAP AG 2002




(C) SAP AG                                  ADM130                             4-51
  Maintain Middleware Parameters

                                                             To activate middleware traces,
                                                             set parameters:
                                                                 FLOWTRACE_ACTIVE


                                                             Use Transaction SMWT to
                                                             monitor middleware traces
                                                             See also SAP note 207264




       SAP AG 2002




  Use transaction R3AC6 to maintain middleware Parameters. This transaction helps to analyze data
  communication errors between the components.
  To activate middleware traces, set the following parameter:
  Key                 Paramname                         Paramval
  FLOW                FLOWTRACE_ACTIVE                  X

  Use transaction SMWT to monitor middleware traces.
  Create background job for Reorganization (MW_REORG).
  Depending on the selected level for tracing and logging, the system writes many entries into internal
  tables. This job triggers reports for reorganization of log data and trace data.
  Log on to the CRM server. Start transaction SM36. Enter the following entries:
    - Name: MW_REORG
    - Steps: ABAP-Program Name SMO6_REORG
    - Variant SAP_MW_REORG
    - Start-Date: Date/Time Once a day
  Starting SMO6_REORG with variant SAP&_MW_REORG will delete all entries older than seven
  days.




(C) SAP AG                                     ADM130                                              4-52
  Scheduling Reports - CRM




    CRM


                       Dispatcher


             D                            B




        SAP AG 2002




  The middleware server requires some jobs to automatically process messages that are stored in
  internal queues and one more for properly handling the statistic updates. Follow the instructions to
  create the required system events and schedule the jobs.
  This job makes some preparations for the updating of statistics. It should always run one day before
  the updating of statistics is scheduled. The updating of these statistics applies only to the oracle
  database environment (see note 162956). You do not need to run this job if you use a database other
  than oracle. Name: MW_STATISTICS, Steps: ABAP-Program, Name smo6_maint_statistic, Variant
  (No variant), Start-Date: Approx. one day before the updating of statistics is scheduled.
  The initial load of an object normally performs the activation of delta events automatically. You
  have to activate the delta events manually only if you need the delta events but have not performed
  the initial load of an object (for example, SALESDOCUMENT).
  1. Choose Middleware --> Data Exchange Delta load from OLTP R/3Set up delta load.
  2. Choose Display-->Change button to switch to change mode
  3. Choose New Entries, then Object Class SALESDOCUMENT, Destination CRM_AX5_100 (that
  is, the RFC destination of the OLTP System).
  4. Save the entries. The message Table TBE31 has been adjusted in OLTP system confirms the
  action if it was successful.
  All realignment functions are asynchronously processed with any corresponding messages in the
  flow. Therefore the Replication & Realignment module works with five internal queues (Three for
  extraction, one for realignment and one for subscription checking). For processing the entries in
  these queues the Queue Demon has to run in the background. It is client-independent and calls
  the required function modules via RFC destinations that have been created during configuration in the IMG.




(C) SAP AG                                        ADM130                                                  4-53
  Scheduling Reports - EBP




   EBP



                      Dispatcher


             D                         B




       SAP AG 2002




  RSPPFPROCESS: To have your purchase orders transferred to the vendors, schedule this report to
  run at regular intervals.
  BBP_GET_STATUS_2: This report updates shopping carts. To ensure that information on the status
  of purchase requisitions, purchase orders, and reservations is up-to-date, schedule this report to run
  daily in the Enterprise Buyer system.
  START_CLEANER and CLEAN_REQREQ_UP: Updating of documents (purchase requisitions,
  purchase orders, and reservations) is executed asynchronously in the backend system. You can only
  process the shopping cart in the Enterprise Buyer system only after the update has been carried out.
  At the interval defined by you in Customizing, the system checks whether the documents have been
  updated and if you can further process the shopping cart. You need to run report
  START_CLEANER for this. The report schedules the job CLEAN_REQREQ_UP at the interval
  entered. If you have not defined an interval in Customizing, you schedule CLEAN_REQREQ_UP
  periodically.
  BBPERS: If you use ERS (evaluated receipt settlement) for local purchase orders for which
  confirmations exist, you have to start BBPERS.
  BBP_DELETE_LOCAL_ACCOUNT: This report updates account assignment tables and deletes
  those account assignment objects that are no longer valid (when the expiry date has passed).




(C) SAP AG                                     ADM130                                               4-54
  Additional Information



                      URLs and SAP notes:
                        ITS, note 375065
                        IPC, note 338528
                        IMS, note: 317576
                        http://www.saplabs.com/its
                        http://service.sap.com/crm
                        http://service.sap.com/connectors




       SAP AG 2002




(C) SAP AG                             ADM130               4-55
  System Administration: Unit Summary



                      You are now able to:
                         Perform Web server administration
                         Perform SAP J2EE Engine administration
                         Perform ITS administration
                         Perform SAP BC administration
                         Perform Requisite Catalog administration
                         Perform IPC and IMS administration




       SAP AG 2002




(C) SAP AG                              ADM130                      4-56
                                                                                 Exerscise

                  Unit: System Administration
                  Topic: Administering the different Components


                  At the conclusion of this exercise, you will be able to:
                  • Describe and administer the different components of the system
                    landscape



                  You are an administrator, who is responsible for the System
                  configuration.



1-1   ITS Administration


      1-1-1 Start the ITS Administration Tool (for the ITS of the CRM Server of the EBP
            scenario) using the Internet Explorer.
             Enter URL
             http://<ITS-Server>.wdf.sap-ag.de:1080/scripts/wgate/admin/! and log in.
             User: itsview
             Password: only
      1-1-2 Check which ITS instances exist and which of them are currently available.
      1-1-3 Check the configuration of the ITS.
             Which parameter defines the number of maximum sessions?
             Which value is set for this Parameter?
             How many sessions are open right now?
      1-1-4 Which SAP system is configured in the global services?
      1-1-5 Which default user is configured in the global services?


1-2   Requisite catalog administration
      DO NOT PERFORM ANY CHANGES
      1-2-1 Start the requisite catalog administration tool using the Internet Explorer.
                 The instructor will provide the username, password and URL.
                 Log on in ECManager mode.
      1-2-2 Check the User Login Log.


(C) SAP AG                                ADM130                                           4-57
1-3   Internet Pricing Configurator
      DO NOT PERFORM ANY CHANGES


      1-3-1 Start the IPC Remote Admin tool using Windows Terminal Server.
             Log on to the Windows Terminal Server (http://wts.wdf.sap-ag.de:1080)
             using the Internet Explorer. Select CORP Walldorf.
             Choose Training -->IPC Remote Admin.
             Choose Start--> Programs -->SAP Internet Pricing and Configurator
             -->Reset IPC.
             Choose Start--> Programs -->SAP Internet Pricing and Configurator
             -->Remote Administrator to Start the Remote Administrator and log on to the
             IPC.
                 Host:                <CRM Internet Sales Middleware Host>
                 Port:                4444
                 Encoding:            UnicodeLittle
                 Pwd:            <The Instructor will provide you a Password, the
                                 standard Password is IPC>
      1-3-2 Check the Configuration of the IPC. Which Database is used to get the Pricing
            Data for the IPC. What is the Host for this Database. Which Type of Database is
            it.


1-4   SAP J2EE Engine admintool
      DO NOT PERFORM ANY CHANGES


      1-4-1 Start the SAP J2EE Engine Remote Admin tool using Windows Terminal
            Server.
             Logon to the Windows Terminal Server (http://wts.wdf.sap-ag.de:1080)
             using the Internet Explorer. Select CORP Walldorf.
             Choose Training -->IPC Remote Admin.
             Choose Start--> Programs --> InQmy --> InQmy admin to start the Remote
             Administrator and logon to the SAP J2EE Engine.
             Choose Connect --> login
             The instructor will provide the username and password.
             Host:           <CRM Internet Sales Middleware Host>
             Port:           3011


      1-4-2 Check the most important Services of SAP J2EE Engine.
             Are there any logs available for the services http or deploy?



(C) SAP AG                                   ADM130                                    4-58
1-5   CRM Server
      1-5-1 Log on to the Internet Sales CRM Server
      1-5-2 Check the Middleware Parameters:
             Is the Flow Trace set active?




(C) SAP AG                                   ADM130   4-59
                                                                             Solutions

                  Unit: System Administration
                  Topic: Administering the different Components


                  At the conclusion of this exercise, you will be able to:
                  • Describe and administer the different components of the system
                    landscape



                  You are an administrator, who is responsible for the System
                  configuration.



1-1   ITS Administration


      1-1-1 Start the ITS Administration Tool (for the ITS of the CRM Server of the EBP
            scenario) using the Internet Explorer.
             Enter URL
             http://<ITS-Server>.wdf.sap-ag.de:1080/scripts/wgate/admin/! and log in.
             User: itsview
             Password: only
      1-1-2 Check which ITS instances exist and which of them are currently available.
            Choose overview to display all ITS instances that can be controlled from
            the ADM instance.
      1-1-3 Check the configuration of the ITS.
             Which parameter defines the number of maximum sessions?
             Choose <ITS-Instance>→Configuration→Performance.
             The parameter is named maxsessions.
             Which value is set for this Parameter?
             It is set to 400.
             How many sessions are open right now?
             Choose <ITS-Instance>→Performance→Performance Summary
             Here you can see how many sessions are used.




(C) SAP AG                                ADM130                                         4-60
      1-1-4 Which SAP system is configured in the global services?
             Choose <ITS-Instance>→Configuration→Global Services→ Default R/3
             System.
             Here you can see the name and system number of the Application Server.
      1-1-5 Which default user is configured in the global services?
             Choose <ITS-Instance>→Configuration→Global Services→ Default R/3
             User.
             Here you can see the client is set to "800", the User is "itsglobal".


1-2   Requisite catalog administration
      DO NOT PERFORM ANY CHANGES
      1-2-1 Start the requisite catalog administration tool using the Internet Explorer.
             The instructor will provide the username, password and URL.
             Log on in ECManager mode.
      1-2-2 Check the User Login Log.
             Choose Administration→User Login Log.
             If you click SEARCH without any restrictions, you can see any entries in
             the log file.


1-3   Internet Pricing Configurator
      DO NOT PERFORM ANY CHANGES
      1-3-1 Start the IPC Remote Admin tool using Windows Terminal Server.
             Log on to the Windows Terminal Server (http://wts.wdf.sap-ag.de:1080)
             using the Internet Explorer. Select CORP Walldorf.
             Choose Training -->IPC Remote Admin.
             Choose Start--> Programs -->SAP Internet Pricing and Configurator
             -->Reset IPC.
             Choose Start--> Programs -->SAP Internet Pricing and Configurator
             -->Remote Administrator to start the Remote Administrator and log on to the
             IPC.
                 Host:                <CRM Internet Sales Middleware Host>
                 Port:                4444
                 Encoding:            UnicodeLittle
                 Pwd:             <The Instructor will provide you with a password, the
                                  standard password is IPC>
      1-3-2 Check the configuration of the IPC. Which database is used to get the pricing
            data for the IPC. What is the host for this database? Which type of database is
            it?
             Choose database. You can see that the IPC uses the database of the CRM
             System.
(C) SAP AG                                   ADM130                                        4-61
1-4   SAP J2EE Engine admintool
      DO NOT PERFORM ANY CHANGES


      1-4-1 Start the SAP J2EE Engine Remote Admin tool using Windows Terminal
            Server.
             Log on to the Windows Terminal Server (http://wts.wdf.sap-ag.de:1080)
             using the Internet Explorer. Select CORP Walldorf.
             Choose Training -->IPC Remote Admin.
             Choose Start--> Programs --> InQmy --> InQmy admin to start the remote
             administrator and log on to the SAP J2EE Engine.
             Choose Connect --> login
             The instructor will provide the username and password.
                Host:              <CRM Internet Sales Middleware Host>
                Port:              3011
      1-4-2 Check the most important Services of SAP J2EE Engine.
             Go to services and look for admin, http, log, deploy, and so on.
             Are there any logs available for the services http or deploy?
             Choose the service and select tab log viewer and select all as logtype.


1-5   CRM Server
      1-5-1 Log on to the Internet Sales CRM Server
      1-5-2 Check the Middleware Parameters:
             Choose Middleware→ Settings → Maintain Middleware Parameters
             (transaction R3AC6).
             Is the Flow Trace set active?
             Yes, the Flow Trace is active (Parameter
             FLOW/FLOWTRACE_ACTIVE=X)




(C) SAP AG                                   ADM130                                    4-62
  Software Logistics


                      1. mySAP Technology              7. Interface Monitoring



                      2. Configuring Internet Sales    8. System Monitoring



                      3. Configuring EBUYER            9. Backup Scenarios


                                                       Appendix Installation Scenarios
                      4. System Administration
                                                                Transaction Codes


                      5. Software Logistics



                      6. Role Management


       SAP AG 2002




(C) SAP AG                                    ADM130                                     5-1
  Software Logistics



                      Contents
                         What content should be transported
                         How to transport different types of data
                         through complex system landscapes
                         How to integrate Add-On packages


                      Objectives

                      At the end of this unit, you will be able to:
                         Describe which data has to be exchanged
                         within a CRM system landscape
                         Describe what tools you use to patch
                         your system landscape


       SAP AG 2002




(C) SAP AG                                    ADM130                  5-2
  What is to be transported?




        What we will look at:
             Transporting own developments in CRM and/or SAP
             R/3
             Transporting ITS Services (IACs)
             Development with SAP J2EE Engine
             Transport of SAP Business Connector Settings
             Add-On and Patch integration




       SAP AG 2002




  This unit discusses the distribution of objects in the SAP R/3 System.
  In the SAP R/3 System, these objects can include settings made during Customizing, or in-house
  software developed by a customer for use with the SAP R/3 System. Such in-house software may
  need to be transported between different SAP R/3 Systems.
  The ABAP development environment provides tools to help the customer develop software
  in-house. Using these tools, several developers can work together on a software project involving
  one or more SAP R/3 Systems.
  For large-scale development projects that may run simultaneously at different locations, the
  administration of source code is a challenging problem.
  This problem is not limited to the SAP R/3 System environment; it is a typical issue arising during
  any major development project. The administration of source code requires:
     - Recording changes to the source code
     - Identifying the original and copies of the original
  This unit surveys the structure of the SAP R/3 System and discusses the solutions the SAP provides
  for logistics problems.




(C) SAP AG                                    ADM130                                               5-3
  Revision: Data Structure of an SAP R/3 System

                      Client 000                                        Client 999


                        Appl.                                                 Appl.
                        data                                                  data




                                          User




                                                                                               User
           Customizing                                            Customizing
                                                  ...
                              Client-independent Customizing



                                           R/3 Repository


       SAP AG 2002




  The SAP R/3 System consists of various data types.
  Certain types of data are only accessible from a particular client. Such data types include business
  application data (documents, material master records, and so on) as well as most Customizing
  settings. These settings:
     - Define the customer's organizational structures (distribution channels, company codes, and so
        on)
     - Adjust the parameters of SAP R/3 transactions to fit customer-specific business operations
  The client-dependent data is distinguished by an additional field in the tables descriptions, the field
  client.
  Client-dependent data types are closely interdependent. Thus, when application data is entered, the
  system checks whether the data matches the client's Customizing settings. If there are
  inconsistencies, the application data is rejected. Therefore, application data usually only makes
  business sense in its specific Customizing environment.
  In addition to client-dependent data, the SAP R/3 System can have other settings that, once defined,
  are valid for all clients. This data includes:
     - Client-independent Customizing, such as printer settings.
     - The SAP R/3 Repository, which contains all objects in the SAP R/3 Dictionary (tables, data
        elements, and domains), as well as all ABAP programs, menus, CUAs, and so on.
  In the case of client-independent settings, an ABAP report that was originally developed in a certain
  client may be immediately usable in another client.




(C) SAP AG                                       ADM130                                                5-4
  Data Structure of an CRM System


             Application Data is stored in tables with names
              different from those within SAP R/3 System




                              Application data, i.e. table
                                    “SMOKNA1”




                                                                              User
                                   Customizing                                       Client ###

                         Client-independent Customizing



                                       Repository


       SAP AG 2002




  The tables used for storing application data within CRM system are not named as in the SAP R/3
  System.
  These tables can differentiate between data from different source clients without using the client field
  in their table definition. Client-dependent application data (from the source systems) is distinguished
  in the CRM system by a special composite key that allows unique identification of all data stored
  within the CRM tables. This key is called Global Unique ID (GUID).




(C) SAP AG                                      ADM130                                                 5-5
  Standard SAP-System Landscape, for example
  SAP R/3 System


       R/3 DR3




                        R/3 QR3




                                        R/3 PR3


       SAP AG 2002




  Before the use of the full potential of SAP Solutions, a typical system landscape consisted of three
  systems: one for development work, one for quality testing, and one for production work.
  All development objects and customizing settings are transported using the Transport Management
  System (TMS). The TMS provides a stable and secure environment for administering changes to the
  systems and offers a version management.
  For new, more complex system landscapes, some other possibilities exist for transporting some
  settings and development objects.




(C) SAP AG                                    ADM130                                                5-6
  Transporting Changes within SAP R/3 and CRM




    R/3 DR3                           Development                 CRM DEV
                                     Transport of
                               Customizing & Development


    R/3 QR3                              Quality                  CRM QAS
                                        Assurance
                                     Transport of
                               Customizing & Development


    R/3 PR3                             Production                CRM PRD


       SAP AG 2002




  Developments within the SAP R/3 system and the corresponding CRM system are usually
  independent of each other.
     Transporting the changes from the SAP R/3 development system to SAP R/3 quality assurance
     system to SAP R/3 production system.
     Transporting the changes from CRM development system to CRM quality assurance system to
     CRM production system.
  Use the TMS for these transports .
  In exceptional cases, a development from the SAP R/3 System proves useful also for the CRM
  system (typically this is NOT a business related development, but more technical) and vice versa. In
  this case all developments are transported and afterwards they may also be transported into the
  complementary development system. Here you may apply necessary changes to the objects
  transported and then transport these through the second system landscape. This is not easy to do and
  should be used only in rare instances.




(C) SAP AG                                    ADM130                                               5-7
  Transporting IACs

   Publish HTML templates, service files, MIME objects, ... using SE80 and IACOR service




                                       publish
                                       manual
                                                     RFC   IACOR
      CRM DEV

     Transport




                                       Autopublish
      CRM QAS                                        RFC   IACOR



     Transport
                                       Autopublish




      CRM PRD                                        RFC   IACOR



        SAP AG 2002   IACOR = Internet Application Component Object Receiver




The following Internet Developments are valid from mySAP.com technology release 4.6C on:
  The Internet application is designed in the CRM system with the Web application builder (SE80)
  The Web application builder ensures the correct management of versions for Web developments
  The developments done with SE80 are published against the ITS (Wgate & Agate) using the IAC
  Object Replicator (IACOR)
  After transporting SE80 objects using transport requests these objects will be auto-published in their
  own transport step. This mechanism is called Auto-publish.
  Note: It is still possible to use SAP@Web Studio for developing IACs. These IACs have to be
  imported into the CRM development system, then transported to CRM quality assurance and again
  exported to SAP@Web Studio to be published against the ITS of QAS.

  The IACOR is an NT service which registers at startup as an RFC program on the CRM server
    Two RFC destinations are created :
  IACOR_<Wgate Host>_<SID>_WWW for publishing on Wgate
  IACOR_<Agate Host>_<SID>_ITS for publishing on Agate




(C) SAP AG                                           ADM130                                           5-8
  Creating an Internet Service




                                                   Create an ITS service and
                                                   Create an HTML Template




       SAP AG 2002




  To create an simple internet service using an HTML template, follow these steps:
     Call transaction SE80.
     Choose Internet Service from the drop down menu of the entry box in the upper left corner.
     Enter a name for the Internet Service you would like to create (for example, Zhello).
     Use the glasses to display your internet service and confirm the popup question with yes.
     In the following pop-up choose Web Application and choose a name a Start Template (for
     example, First).
     Assign the object to a development class.
     Right mouse click on Theme 99 then choose Create --> Template.
     Refer to standard theme 99 and choose HTML Template Name (for example, First).
     Assign the object to a development class.
     Double click on the name of your HTML template, to be found under Theme99 --> HTML Templ..
     Now you can edit the HTML template for example include a line between the body-tags:
        <h1><center>Hello world!</center></h1>
  Now you can publish your masterpiece by right mouse click on the object name and choosing
  Publish --> complete Service.
  If everything works, the browser on your desktop will be started and the corresponding site of the
  web server is called. A logon screen should be shown and you confirm. You see your HTML output.




(C) SAP AG                                   ADM130                                              5-9
  Publishing against the ITS using SE80




                                                                  Use the Publish function
    Right mouse click on object name
    opens the context menu




       SAP AG 2002




  You may still use SAP@Web Studio to build an publish web applications, but the newer and simpler
  way is to employ transaction SE80. Transaction SE80 offers much easier transport and publishing of
  development objects than other methods available.
  Transaction SE80 include two ways to publish objects to the ITS:
     Use the button "Publish"
     Use the context menu with a right click
     These options differ significantly!
     The Publish button only publishes the object on which you where currently working(to be seen in
     the work area of SE80).
     The context menu publish publishes the whole IAC with all its components if you choose the
     object name before right clicking.
  An IAC consists of several components. All these elements are stored within the system. By
  publishing the system creates some files that are taken by the IACOR service and then stored in
  different locations, depending on the object type. The most important object types are:
     Service files
     HTML Business Templates (for each screen)
     MIME objects
     Language ressource files
     Also see the appendix.




(C) SAP AG                                   ADM130                                             5-10
  IACOR – IAC Object Receiver




                                                     IacorAdmin.exe is found in the
                                                     “Admin” folder of the ITS directory




    Objects published from SE80 are shown in the IACOR Event Log



       SAP AG 2002




  The IACOR Admin tool is used to configure IACOR.
  You name the ITS against which the IACOR should publish and you configure the connection
  between the IACOR and one or more backend systems.
  IACOR uses the data you provide to connect to the named backend systems and to create RFC
  connections it (and the backend system/s) will use.
  If you publish from within SE80 you using RFC connections (visible in SM59) created from the
  outside by the IACOR Admin tool. You are not able to create these connections using SM59.
  The Admin tool consists of an overview, that shows all published objects for the connected ITS.




(C) SAP AG                                   ADM130                                             5-11
  Calling a Service from the Net, SE80 settings




                      check these settings            view the result by calling correct service




       SAP AG 2002




  Depending on your system patch level the necessary or possible entries in the fields found below
  Utilities --> Settings may differ.
  For example you may need to:
    Provide http:// at the beginning of the Web server‘s address (not shown in the graphic).
    Change (modify) the input field screen painter settings to take input as it is (concerning lower or
    upper case), because ITS does not understand upper case. This may depend on the ITS release.
  Please see the SAP Notes about ITS versions and patch levels for more information




(C) SAP AG                                      ADM130                                               5-12
  Development Environment for Java development


                     Java2 SDK
              InQMy J2EE Server                                    Local development
                                                                    Environment for
               SAP Java Connector
                                                                    every Developer
          Internet Sales Web Application
      Development Tool (for example Jbuilder)




                                     SAP J2EE Engine                  CRM QAS


             Deployment



                                    SAP J2EE Engine                   CRM PRD



       SAP AG 2002




  A complete local Development environment is necessary for every developer who wants to work on
  the Internet Sales Java Application.
  J2EE components are packaged separately and bundled into a J2EE application for deployment.
  Each component, its related files such as GIF and HTML files or server-side utility classes, and a
  deployment descriptor (DD), are assembled into a module and added to the J2EE application. A
  J2EE application is comprised of one or more enterprise bean, web, or application client component
  modules. The final enterprise solution can use one J2EE application or be made up of two or more
  J2EE applications, depending on design requirements A J2EE application and each of its modules
  has its own deployment descriptor. A deployment descriptor is an Extensible Markup Language
  (XML) text-based file with an .xml extension that describes a component’s deployment settings. An
  enterprise bean module deployment descriptor, for example, declares transaction attributes and
  security authorizations for an enterprise bean. Because deployment descriptor information is
  declarative, it can be changed without modifying the bean source code. At run time, the J2EE server
  reads the deployment descriptor and acts upon the component accordingly. A J2EE application with
  all of its modules is delivered in an Enterprise Archive (EAR) file. An EAR file is a standard JAR
  file with an .ear extension. In the GUI version of the J2EE SDK application deployment tool, you
  create an EAR file first and add JAR and WAR files to the EAR. If you use the command line
  packager tools, however, you create the Java ARchive (JARs) and Web Archive (WAR) files first
  and create the EAR. Each EJB JAR file contains its deployment descriptor, related files, and the
  .class files for the enterprise bean. Each application client JAR file contains its deployment
  descriptor, related files, and the .class files for the application client. Each WAR file contains its
  deployment descriptor, related files, and the .class files for the servlet or .jsp files for a JSP page.
  Using modules and EAR files makes it possible to assemble a number of different J2EE applications
  using some of the same components. No extra coding is needed; it is just a matter of assembling
  various J2EE modules into J2EE EAR files.

(C) SAP AG                                      ADM130                                                5-13
  Development Possibilities

                                                                    UI and Interaction Layer
        Changing/replacing JSPs
        Changing/replacing Actions                            Update
                                                               Update                  Basket
                                                                                       Basket
        Changing order of interactions                      BasketAction
                                                            BasketAction                JSP
                                                                                        JSP

        Adding customer written Business
        Objects                                                                       BO Layer
        Extending/Modifying Business Objects                    Basket
                                                                Basket


        Adding customer written Backend
        Objects                                                                      EAI Layer
        Extending/Modifying Backend Objects                   BasketCRM
                                                              BasketCRM

        Modifying existing RFCs (ABAP or
        Interface)
                                                                                            CRM
        BADI modification concept                        AddHeaderItemRfc
                                                         AddHeaderItemRfc

       SAP AG 2002




  The Interaction and Presentation Layer is realized using the STRUTS framework. There are basically
  two different types of modification, that can be performed in the layer: Ul related modifications and
  modifications in the action flow. Changes in the UI are often necessary in order to display additional
  data or to enter additional data. Such changes are usually not limited to the UI layer only.
  Any arbitrary data can be associated with a Business Object by using the extension Data mechanism.
  The Base Class of each Business Object provides this mechanism. This modification is used when
  you have to add some functionality to an existing Business Object, or you want to replace the
  functionality of an existing method with your own implementation. In either case you have to derive
  from the existing Business Object and extend/replace its functionality.
  Many Business Objects (for example, Basket) in the Business Object Layer have a corresponding
  Backend Object in the EAI layer. The functionality of a Backend Object is accessed via a well-
  defined Java Interface (for example, BasketBackend). The implementation of such an interface is
  backend dependent (for example, BasketCRM).
  Java source code is not delivered to the customer. Changes should be possible without changing
  applications source code.
  Only source code of JSP is supposed to be changed.
  Updates should not be affected by changes made by the customer.
  The CRM API is supposed to change.




(C) SAP AG                                     ADM130                                              5-14
  Structure of an Internet Sales Web Application
  ISA Structure of web archive (for example b2b)



  <root>                Root of web application
    <admin>             Some JSPs for administration purposes
    <auction>           Auction specific JSPs/Mimes
    <b2b>               B2B scenario specific JSPs/Mimes
    <catalog>           Catalog scenario specific JSPs/Mimes
    <ecall>             Customer Interaction Center specific JSPs/Mimes
    <ipc>               IPC specific JSPs/Mimes
    <mimes>             Application style sheet
    <WEB-INF>           web.xml: deployment descriptor; config.xml: Struts configuration
       <cfg>            Internet Sales specific configuration files
       <classes>        Internet Sales specific java classes
       <doc>            Legal statements regarding the usage of third party software
       <lib>            Internet Sales specific libraries (jar files)
       <logs>           Location of Internet Sales log files
       <tlds>           Descriptors for custom JSP tags

       SAP AG 2002




  Deployment is the process of copying J2EE components to J2EE servers.
  Process steps:
    Collect components
    - EJBs, Servlets, JSPs, html files, .gifs, ... go into .war file
    - EJBs, helper classes go into .jar file
    Specify properties for the components
    - Servlet/EJB relationships
    - URLs for servlet/JSP
    - Result: deployment descriptor in XML (J2EE server dependent)
    Put everything together in an enterprise archive (.ear)
    - .war, .jar, application.xml, Manifest.mf
    Copy to SAP J2EE Engine cluster nodes
    Deploy service of cluster nodes extracts archives
  Deployment (installation) of a web application consists of two steps:
    1) An application is packaged into a Web Archive (WAR) file.
    - The WAR file is runtime-independent.
    - WAR file is zipped filestructure containing the application.
    2) WAR file is installed on the server.
    - The installation of a WAR file is server specific.
    - After the deployment the deployed application becomes server specific (for example, in a server
       specific file structure).




(C) SAP AG                                        ADM130                                         5-15
  J2EE Deployment Overview



              Bean Provider             Assembler           Deployer              Administrator

      EJB
      EJB               J2EE            Assembling           Deploying            SAP J2EE Engine
                      Components        Components          Components
      JSP
      JSP
                                                                 EAR




                                                                                                    Application
                         JAR                                     EAR
                         JAR
     HTML
     HTML                                                                           Installed
                                                                                     Installed
                                            EAR
                                            EAR              Specifiy Cluster          EAR
                                                                                       EAR
                                                             Nodes
      .gif
       .gif                                                  Storage
                         WAR
                         WAR                                 Properties
       ...
        ...                                                  Security Roles
                                                                                        Server




                   Components.xml
                   Components.xml      assembler.xml
                                       assembler.xml         deployer.xml
                                                             deployer.xml




                                       Myproject.dpl
                                       Myproject.dpl

       SAP AG 2002




  The J2EE standard defines several roles for its users and also defines the specific job of such users.
  There are four roles:
     - Bean Provider
       This role is the programmer‘s part. It provides components for a J2EE environment
       independently from servers or environments.
     - Application Assembler
       The Assembler takes over components that were produced be the Beans Provider and binds
       them together into enterprise archive files. These are independant of the environment where
       they run.
     - Application Deployer
       Deployment is the job that brings defined enterprise archives together with a specific
       environment on a specific server.
     - Application Administrator
       The Administrator keeps the once installed application running and optimizes its behavior over
       time.
  In most cases, one person has more then one role and existing applications and components do not
  have the flexibility like as this model. However, applications can be written that do have this
  flexibility. Using a J2EE environment does not automatically guarantee independent use of
  application servers and mixing of different components from different vendors.




(C) SAP AG                                     ADM130                                                    5-16
  The Deploy Tool




       SAP AG 2002




  Specify the deployment destinations and assign security roles to actual existing users and user
  groups. For entity beans also the storage properties (mapping container managed fields to the
  database, specify connection pool, specify finder criteria) have to be maintained. In this example,
  there is no container managed entity bean, therefore there is no need to specify the storage properties.
  Make sure, that server and dispatcher are started. First connect the server in order to get the
  information about cluster nodes as well as user and user groups on the server. To connect the server
  select Deploy->Connect and then press Connect. For a local server installation the default entries
  should not be changed. In order to specify the deployment destinations, select Deploy ->Cluster
  Properties in the menu, and then the tab Cluster Info.
  In the cluster info tab it is possible to specify the destinations in the cluster onto which the
  application should be deployed. For our example nothing should be changed here. Now it is needed
  to map the security roles defined in the deployment descriptor to actually existing users or user
  groups on the server. Double-click the application root on the tree on the left side. Select the
  multiplier.jar entry and then the Multiplier Bean. In the User Mapping tab map the security role all
  to a user group (for example, root) from the server. Save the project and select Deploy->Deploy EAR
  in the menu in order to deploy the application to theserver.
  After successfully deploying the application, the status message is Deployed successfully. In case of
  errors, the error message and a detailed log is displayed. To access the application, type
  http://locahost/multiweb in your browser. The name multiweb corresponds to the name of your web
  component created within the J2EE Generator. Technically, this is an alias in the web server that
  points to the web archive.
  You should see the MultiplierBean within the EJBContainer and the web component multiweb
  within the servlet/jsp container. The name multiweb is the web root of the application.



(C) SAP AG                                      ADM130                                               5-17
  Jbuilder Integration




       SAP AG 2002




  The deployment is also possible with some development Tools.

  JBuilder Integration:
    - Installation
       Copy <In-Q-My-Root>\deploying\lib\deploy.jar to <JBuilder-Root>\lib
       Copy SAP J2EE EngineIntegration.jar to <JBuilder-Root>\lib\ext
       Restart Jbuilder
    - Deploy
       Right click on EAR group .ear file
       Choose SAP J2EE Engine Application Deployment Deploy
    - Deploy with same settings (Redeploy)
       Right click on EAR group .ear file
       Choose SAP J2EE Engine Application Deployment Redeploy




(C) SAP AG                                  ADM130                           5-18
  Transporting issues concerning the SAP BC




       SAP AG 2002




  The SAP Business Connector is a relatively isolated tool concerning its configuration. That means:
    You have one Business Connector for each related system (for example for CRM DEV, CRM
    QAS and CRM PRD).
    The configuration settings for the SAP Business Connector reside on file system level and are
    transported using standard file replication methods: ftp, drag & drop (copy & paste) or the package
    Tools of the SAP BC.
    There is no integration into SAP's transport system or software logistics.
    There is no version management (so keep backup versions).
  Handling of transporting issues related to the SAP Business Connector require a good management
  of versions. You must be able to tell old versions of configuration files apart from new ones.




(C) SAP AG                                    ADM130                                              5-19
  Package replication/publication



             During the Package-Replication...

                 SAP Business
                                          ...a Publishing Server copies a Package
                  Connector
                      Publisher                     SAP Business
                                                     Connector       ... to one or more
                                                       Subscriber    Subscribing Server.




                                                SAP Business
                          SAP Business           Connector
                           Connector              Subscriber
                             Subscriber




       SAP AG 2002




  Use package replication to copy packages from one SAP BC to another (publicate). This feature
  makes sense in a cluster environment, to replicate new or changed packages as fast as possible to
  other servers.
  During replication, a single SAP BC sends (publishes) a package to one or more receiving SAP BCs.
  The server where the package came from is called publisher and a receiving server are called
  subscriber.
  The subscriber receives the package in the inbox directory (sapbc/server/replicate/inbound). To
  activate the new package, the administrator has to install it on the subscriber.




(C) SAP AG                                      ADM130                                         5-20
  Plug-Ins modifying systems


                                                                       Industry
              SEM      APO         EBP            Plug-Ins
                                                                       Solution




                                                   Central
                  BW             CRM            Applications                HR
                                               with/without HR


                               ABAP etc. (Cross-Application)




                                      SAP BASIS (Basis)



       SAP AG 2002




  Technically speaking, SAP systems are all built on a common software infrastructure called SAP
  Basis. Since the beginning of 2001, it is also known as mySAP Technology.
  Using the development environment, SAP offers many different solutions for different business
  scenarios (for example, the classic Financials (FI) or Human Resources (HR) software).
  These classic applications, as well as other, newer applications, may be adapted for special
  requirements (for example, country specific laws or industry specific functions), using Add-Ons.
  These Add-Ons are available for a broad range of applications and special business scenarios.




(C) SAP AG                                    ADM130                                                 5-21
  Install Add-On using Transaction SAINT




     Transaction SAINT allows easy
     installation of Add-On developments




       SAP AG 2002




  SAP offers a wide range of add-ons that you can use to enhance your standard SAP System. These
  add-ons can be Industry Solutions, plug-ins, or customer-specific development projects. Many of
  these add-ons contain a small number of objects. You must take several import conditions into
  account.
  An operating system-based process for installing or upgrading these add-ons in an SAP System is
  complicated; so the transaction SAINT was developed. This transaction lets you install and upgrade
  add-ons directly from the SAP System. You do not need to access the operating system or restart the
  SAP System.
  The transaction SAINT checks the import prerequisites, such as the system release, the Support
  Package level of the individual software components, and whether other add-ons are being used.
  To simplify the import process, the complete installation is first put together in the customer system
  from the add-on installation package, any Support Packages that are needed, and any Conflict
  Resolution Transports (CRTs).
  The installation itself is a process that can be restarted, similarly to the import of Support Packages.




(C) SAP AG                                      ADM130                                                5-22
  Steps for applying an Add-On



  You need to follow these steps in order
  to install an Add-On to your system:

     Access the SAP Service Marketplace: http://service.sap.com/ocs
      Enter the appropriate download area (for example: Support
   Packages)
      Download the required patch
      Unpack the content of the package to /usr/sap/trans/EPS/in
      Call transaction SAINT
      Find the Add-Ons available for installation
      Choose "Continue" and follow the steps given in "Status/Remarks"
  For further information refer to the documentation given within
  transaction "SAINT", accessed by "Shift + F1" (including a step-
  by-step guide) and note 160168

       SAP AG 2002




(C) SAP AG                            ADM130                             5-23
  Installation and Upgrade


  Installation

  Checklist: Which SAP R/3 Plug-in is the right one for my customers?

  !    Which mySAP.com component (for example, APO, BBP, BW, CRM )
       is planned for which release (for example, BW 2.1C)?
  !    Is the SAP R/3 release current?
  !    Is the SAP R/3 Support Package level current?
  !    Has an SAP R/3 Plug-in already been installed?
       (=> Check: transaction BAOV (to 4.5B) or System Status (from 4.6B))


  Example:

  Status: SAP R/3 4.0B, SP level 15
  Goal: CRM 2.0C (=> PI 2000.2)
  Path: Install SAP R/3 SPs up to 38, install PI 2000.2


       SAP AG 2002




  The Plug-in CDs are delivered along with every mySAP component (APO, EBP, and so on).
  The Plug-in CDs are delivered along with the IS CDs for Release 4.6B and higher.
  New releases of SAP R/3 Plug-ins will be shipped automatically to customers with valid SAP
  component contracts.
  Download of the SAP R/3 Plug-ins from the Service Market Place is possible. Quicklink: R/3-Plug-
  in.




(C) SAP AG                                   ADM130                                            5-24
  Unit Summary



                      You are now able to:

                         Explain how changes to the repository or
                         customizing are transported in CRM and SAP
                         R/3
                         Publish IACs to an ITS, using SE80 and IACOR
                         Explain how SAP Business Connector
                         configuration settings are replicated
                         Name the tool to import Add-On development
                         into the system




       SAP AG 2002




(C) SAP AG                              ADM130                          5-25
  Appendix: IAC Object Replicator




                                         WGate




                                                                    AGate
             Web
           browser                 HTTP                      ITS


                            IACOR_<HOST>_<SID>_WWW        IACOR_<HOST>_<SID>_ITS




                                                   abcd.srvc     <b>`i`</b>        seats
         CRM DEV                                   test.srvc      `itab[i]`         seats

        using SE80
                                   MIME           Services       Templates          Texts
                                                      Database tables


        SAP AG 2002




IACOR functions:
  The IACOR is a NT service which registers at startup as an RFC program on the CRM server
  Two RFC destinations are created in the backend system (can be seen in SM59):
    IACOR_<Wgate Host>_<SID>_WWW for publishing on Wgate
    IACOR_<Agate Host>_<SID>_ITS for publishing on Agate




(C) SAP AG                                       ADM130                                      5-26
   Communication between SAP R/3 and IPC (2.0B)



                                                             IPC            IPC
             R/3 DEV                      qRFC
                                                            Loader

     Transport                       (for example,
                                      pricing data)
                                                             IPC            IPC
             R/3 QAS                      qRFC              Loader

     Transport                       (for example,
                                     pricing data)
                                                             IPC            IPC
             R/3 PRD                      qRFC              Loader

                                     (for example,
                                      pricing data)
       SAP AG 2002




  IPC configuration :
    Some major customizing changes in the pricing configuration (for example, change of the pricing
    procedure) require a new initial download to the IPC. This can only be done manually after
    importing the corresponding transport request in the target system.
    Most of the time, the configuration for pricing is automatically uploaded to the IPC with delta
    upload (qRFC). The information for conditions, material master data, and configurable products is
    part of the delta upload.




(C) SAP AG                                    ADM130                                             5-27
                                                      Introduction: Exercise

                  Unit: Software Logistics
                  Topic: IAC


                  At the conclusion of this exercise, you will be able to:
                  • Transport IAC developed with SE80




                  You are an administrator responsible for the system configuration.



1-1   Creation of IACs
      1-1-1 On the CRM server (client 800) log on using your ebp-## user.
      1-1-2 Call the object navigator
      1-1-3 Define the Web server and ITS against the IACs will be published for your user.
      1-1-4 Create an new internet service with the name Zworld##.
             Name the Start Template Zstart##.
             Choose the development class provided by your trainer. You are asked for a
             transport request. Create your own and use Service: Zworld## as short text.
             Note down the number of the request.
      1-1-5 Edit the zstart## template.
             Enter between <body>and </body> the text (e.g. Hello World). Don't put to
             much time into this work. Save.


1-2   Publishing and calling of IAC
      1-2-1 Right-click on the object name (Zworld##) and choose Publish --> Complete
            Service. Ignore the warning. IACOR tried to delete an older version of an object
            that does not exist.)
      1-2-2 Call the correct address in a browser window, ending with:
             "... scripts/wgate/ZWORLD##/!". On the following pop up, confirm the logon
             to the system.


1-3   Transporting and autopublishing
      1-3-1 Go to SE09 and look for your change request. Release it.



(C) SAP AG                                ADM130                                           5-28
      1-3-2 In SE80 delete your Internet service Zworld##. Create a new transport request
            for the deletion. Now try calling your service again as in 1.2. As the service
            does not longer exist you will get an error message.
      1-3-3 In transaction STMS go to the import queue of your system and choose: Extras
            --> other requests --> add. Name your transport number you noted down.
      1-3-4 Import the request containing your object (short text as in 1.1.5) using import
            single (Ctrl + F11) with the second and third option chosen.
      1-3-5 After import: in SE80 choose F8 or the execute service icon on your re-
            imported service Zworld##. The browser will be started automatically and after
            confirming system logon, the service is called successfully. Remember: you did
            not publish the service this time. The import did that for you!




(C) SAP AG                                ADM130                                         5-29
                  Unit: Software Logistics
                  Topic: Plug-Ins


                  At the conclusion of this exercise, you will be able to:
                  • Get Information about the newest version of Plug-Ins




                  You are an administrator responsible for the system configuration.



2-1   Information searching about plug-ins
      Go to http://service.sap.com/r3-plug-in.
      Either use your own user ID for the Service Marketplace or use "Walldorf / training" as
      user ID and password. Look for the date when the next Plug-In will be available.




(C) SAP AG                                ADM130                                         5-30
                                                         Introduction: Solutions

                  Unit: Software Logistics
                  Topic: IAC


                  At the conclusion of this exercise, you will be able to:
                  • Transport IAC developed with SE80




                  You are an administrator, who is responsible for the system
                  configuration.


1-1   Creation of IACs
      1-1-1 On the CRM server (client 800) log on using your ebp-## user.
      1-1-2 Call the object navigator
            Call transaction SE80
      1-1-3 Define the Web server and ITS against the IACs will be published for your user.
             Choose Utilities --> Settings. Choose Tab ITS.
             Select other Web server and enter the Web server for the ITS of your
             CRM Server.
             Select Publish to and choose your ITS from the drop down list.
      1-1-4 Create an new Internet service with the name Zworld##
             Name the Start Template Zstart##.
             Choose the development class provided by your trainer. You are asked for a
             transport request. Create your own and use for "Service: Zworld##" as short
             text.
             Write down the number of the request.
             Choose Internet Service using the drop down list box, type in Zworld## and
             use the glasses. If asked if you would like to create the object confirm with
             yes.
      1-1-5 Edit the zstart## template.
             Enter between <body>and </body> the text (e.g. Hello World). Don't put to
             much time into this work. Save.
             For example type "Hello world" (without "") in between bracketed tags.


1-2   Publishing and calling of IAC


(C) SAP AG                                ADM130                                           5-31
      1-2-1 Right-click on the object name (Zworld##) and choose Publish --> Complete
            Service. Ignore the warning. IACOR tried to delete an older version of an object
            that does not exist.)
      1-2-2 Call the correct address in a browser window, ending with:
             "... scripts/wgate/ZWORLD##/!". On the following pop up, confirm the logon
             to the system.
             Choose the Web Server's address noted above. Append "/zworld##/!".
             Confirm the logon to the system.
1-3   Transporting and autopublishing
      1-3-1 Go to SE09 and look for your change request. Release it.
             SE09, choose modifiable (default) and Display. Release (F9) first your task
             (with giving a documentation) than your request (again F9).
      1-3-2 In SE80 delete your Internet service "Zworld##". Create a new transport request
            for the deletion. Now try calling your service again as in 1.3.2. As the service
            does not longer exist you will get an error message.
            SE80: choose your service, right-click and choose delete.
             You have to begin deletion from bottom-up. so first delete the HTML
             template, then the service. Assign the deletion to a newly created transport
             request. Use the browser to call your service. As it does no longer exist you
             will not succeed.
      1-3-3 In transaction STMS go to the import queue of your system and choose: Extras
            --> other requests --> add. Name your transport number you noted down.
      1-3-4 Import the request containing your object (short text as in 1.1.5) using import
            single (Ctrl + F11) with the second and third option choosen.
      1-3-5 After import: in SE80 choose F8 or the execute service icon on your re-
            imported service Zworld##. The browser will be started automatically and after
            confirming system logon, the service is called successfully. Remember: you did
            not publish the service this time. The import did that for you!
             After import: in SE80 choose F8 or the execute service icon on your re-
             imported service Zworld##. The browser will be started automatically and
             after confirming system logon, the service is called successfully.




(C) SAP AG                                ADM130                                         5-32
                  Unit: Software Logistics
                  Topic: Plug-Ins


                  At the conclusion of this exercise, you will be able to:
                  • Get Information about the newest version of Plug-Ins




                  You are an administrator responsible for the system configuration.



2-1   Information searching about plug-ins
      Go to http://service.sap.com/r3-plug-in.
      Either use your own user ID for the Service Marketplace or use "Walldorf / training" as
      the user ID and password. Look for the date when the next Plug-In will be available.
      Go to http://service.sap.com/r3-plug-in, using "Walldorf / training" as user and
      password. Go to News & Events to see when the next Plug-In will be available. This
      may be R/3 Plug-In PI 2002.1, available in mid 2002.




(C) SAP AG                                ADM130                                         5-33
  Role Management


                      1. mySAP Technology              7. Interface Monitoring



                      2. Configuring Internet Sales    8. System Monitoring



                      3. Configuring EBUYER            9. Backup Scenarios


                                                       Appendix Installation Scenarios
                      4. System Administration
                                                                Transaction Codes


                      5. Software Logistics



                      6. Role Management


       SAP AG 2002




(C) SAP AG                                    ADM130                                     6-1
  Role Management



                      Contents
                         Transition to Role Concept
                         Role Templates
                         Central User Administration



                      Objectives
                      At the end of this unit, you will be able to:
                         Describe the transition path to using roles
                         Use standard roles
                         Create a test and production environment for CUA




       SAP AG 2002




(C) SAP AG                                       ADM130                     6-2
  Transition to Role Concept


                    Transition to Role Concept
                       Transition to Role Concept
  Transition to Role Concept Concept




                                                                           Transition to Role Concept Concept
                                                                                         Transition to Role
     Transition to Role




                                                                           Role Templates
                                              Transition to Role Concept




                                                                           Roles and Central User Administration




                             SAP AG 2002




(C) SAP AG                                                                                  ADM130                 6-3
  Roles versus Authorization Profiles


  What you (may) have:

  Collective authorization profile                            Z_POWERUSR

  Single authorization profile                    Z_FI_POWERUSR         Z_CO_POWERUSR


  What you need:
  Web Frontends require roles, traditional authorization profiles
  are ignored during Launchpad and menu generation

  Launchpad entries:                                    CUST007_WP_PWRUSR_0001
  composite role


                                        CUST007_FI_PWRUSR_0001         CUST007_CO_PWRUSR_0001
  Easy to configure:                         Transactions:                   Transactions:
                                                FD01...                         CO41...
  single roles


  Generated                                     T-51000002                     T-51000001
  authorization profiles
       SAP AG 2002




  For EBP it is necessary to work with roles. In former times many customers work with authorization
  profiles and have never used the profile generator.
     - Roles point to single transactions and usually do not directly contain authorizations.
     - Authorization profiles are generated automatically by the profile generator.
     - As of SAP basis release 4.6B, transaction SU02 is no longer in use.
  During logon, the users menu is generated from roles. The menu displayed in the SAPGUI for
  HTML only contains entries that are defined in roles. A user might have additional authorizations
  coming from a traditional authorization profile. In this case, he or she cannot call the respective
  transactions, since they are not displayed in the menu.




(C) SAP AG                                    ADM130                                              6-4
  Implementing the Role Concept

     Naming conventions:
          Single roles:
          [<organization>_]<component>_<function>_<org.unit>
          Example: CUSTOMER007_FI_GL_ACCT_MASTER_DATA_0001
          Composite roles:
          [<organization>_]WP_<function>_<org.unit>
          Example: CUSTOMER007_WP_COSTACCOUNTING_MANAGER_0001
     Process:
                                                                SAP CRM
          Perform a survey to identify required roles
                                                                               Create single role
          Create single roles
                                                                               Generate profile
                Create new roles on component systems
                                                                               Test authorizations
                Rename existing roles if necessary
                                                                               Delete old profiles
                Migrate authorization profiles to roles
                (transaction SU25, step 6)
                                                          ERP
                Use standard roles wherever you can
                                                                Create single role
          Generate authorization profiles
                                                                Generate profile
          Test authorizations and                               Test authorizations
          configure check indicators
                                                                Delete old profiles
          Delete old authorization profiles
       SAP AG 2002




(C) SAP AG                                    ADM130                                                 6-5
  Migration of Authorization Profiles to Single Roles


                                          Add S_TCODE
           Auth Profile                                                          Auth Profile
                                           using SU02
         Z_FI_POWERUSR                                                        Z_FI_POWERUSR
                                                                             (containing Tcodes)

                                                                            Create optimized role
                                                                                using SU25

       Create identical
         role using
                                                                              Single Role
            SU25
                                                                         ALLCUST_FI_POWERUSR

                                                                        Maintain open authorizations
                                                                             and add or remove
                                                                         transactions using PFCG

         Single Role                                                          Single Role
  CUST007 _FI_PWRUSR_0001                                               CUST007 _FI_PWRUSR_0001
                                       Add          Maintain open
                                   transactions     authorizations
                                   using PFCG        using PFCG

       SAP AG 2002




  There are two ways to convert a given authorization profile to a single role:
     - Create a single role using Optimized in transaction SU25. This allows automatic assignment of
        organizational structure and automatical creation of menu using transactions.
     - Create a single role using Identical in transaction SU25. All authorizations are kept as
        previously defined.
  After the single role is created, rename it to include the required identifiers for the logical system and
  to distinguish between single and composite roles.




(C) SAP AG                                       ADM130                                                  6-6
  Role Templates


                 Role Templates
                  Role Templates




                                               Transition to Role Concept
  Role Role Templates




                                               Role Templates
                                                        Role Templates
       Templates
                              Role Templates




                                               Roles and Central User Administration




                   SAP AG 2002




(C) SAP AG                                                      ADM130                 6-7
  Where to Get the Role Templates


      Role templates are
      part of the mySAP
      Workplace installation
      Role definitions can
      be displayed using
      report RSUSR070
      Check out role maps
      containing
           Technical role name
           Role description
      See Service Marketplace
      quicklink rolemaps




       SAP AG 2002




  To give you an overview of the roles delivered by SAP, program RSUSR070 outputs descriptions of
  the existing example jobs.
  To run the program, choose Tools → Administration → User maintenance → Infosystem → Roles →
  Roles by complex selection criteria → By role name, or call transaction S_BCE_68001418.




(C) SAP AG                                  ADM130                                            6-8
  Single Role Templates for SAPM EBP


             Employee
             Manager
             Secretary, Office Assistant
             Component Planner
             Purchaser
             Internal Dispatcher
             Accountant
             Administrator
             Bidder
             Vendor




       SAP AG 2002




  The technical names for the above roles are as follows:
    - Employee: SAP_EC_BBP_EMPLOYEE
    - Manager: SAP_EC_BBP_MANAGER
    - Secretary, Office Assistant: SAP_EC_BBP_SECRETARY
    - Component Planner: SAP_EC_BBP_PLANNER
    - Purchaser: SAP_EC_BBP_PURCHASER
    - Internal Dispatcher: SAP_EC_BBP_RECIPIENT
    - Accountant: SAP_EC_BBP_ACCOUNTANT
    - Administrator: SAP_EC_BBP_ADMINISTRATOR
    - Bidder: SAP_EC_BBP_BIDDER
    - Vendor: SAP_EC_BBP_VENDOR
  For further details, see the SAP Library for CRM/BBP.




(C) SAP AG                                 ADM130           6-9
  Single Role Templates for SAP CRM


     Role templates exist in the following
     areas:
          Business Transactions
          Internet Sales
          Service Interaction Center
          Marketing and Campaign Management
          Master Data
          Middleware
               CRM Middleware Administrator
               CRM IPC Admin
               CRM ITS Admin




       SAP AG 2002




  For further details, see the SAP Library for CRM/BBP.
  The CRM middleware administrator role is called SAP_CRM_MIDDLEWARE_ADMIN.




(C) SAP AG                              ADM130                                6-10
  Central User Administration

                          User Administration
  Roles and Central UserRoles and Central User Administration
   Roles and CentralAdministration



                                                                                                        Transition to Role Concept
                                                                Roles and Central User Administration




                                                                                                        Role Templates


                                                                                                                  Central User Administration
                                                                                                        Roles andRoles and Central User Administration




                                                   SAP AG 2002




(C) SAP AG                                                                                                               ADM130                          6-11
  Central User Administration


  How to test the configuration in a mySAP solution landscape

    Development, Quality                          One Master controls a
    Assurance and Production                      complete System Landscape
    have own CUA Master


      R3D             R3Q         R3P               R3D        R3Q         R3P




      CRD             CRQ         CRP               CRD        CRQ         CRP           CUA
      Master          Master      Master                                                 Master



       Advantages                                    Central Administration
                                                     System controls complete
             Simple test environment                 landscape

       SAP AG 2002




  Depending on your CUA configuration, different test scenarios exists.
  The CUA Master controls only SAP Systems of the same software logistics level.
  A test process could look like the following:
    - Have a separate CUA for every layer (DEV, QAS and PRD) of your solution landscape.
    - Some customers require that even DEV and QAS user administration be done from within one
       client in the production system. In this case, test the CUA in DEV and QAS in separate test
       clients instead of the leading clients.




(C) SAP AG                                   ADM130                                            6-12
  Central User Administration

      Prevent unwanted transports
           Configure customizing table PRGN_CUST
                In DEV systems prevent export of authorization profiles
                PROFILE_TRANSPORT = NO
                In all systems prevent import of user assignments with import of roles
                USER_REL_IMPORT = NO
           User Compare:
                Automatically compare user master records using a periodic
                background job scheduled using PFCG

      What must be transported?
                                                 Composite Role                Single Role
           Single roles / composite roles   CUST007_WP_PWRUSR_0001        CUST007_PWRUSR_0001

      What must not be transported?                                Composite Role
                                                              CUST007_WP _PWRUSR_0001

           User assignments

      What should not be transported?
                                                       Auth Profile
           Authorization profiles                       ZTRANS
       SAP AG 2002




(C) SAP AG                                  ADM130                                              6-13
  CUA and CRM/EBP




                                                         Self Service for User Creation and CUA
        EBP
                                                                      (Note 402592)




       Internet Sales Internet Users and CUA                     SAP CRM
                    (Note 395070)




       SAP AG 2002




  EBP in the Environment of a central user Administration (note 402592):
  If an EBP system is connected to a Central User Administration, up to now there was no standard
  procedure on how to proceed. The process is described in Note 312090. However, the process is
  based on certain preconditions (for example a replication of the organizational structure is
  required).Therefore, a simple solution is described here. You can apply this solution to operate an
  EBP system as a subsystem of a Central User Administration if the organizational structure is not
  transferred by an ALE replication from an HR system. This solution is available as of Release 3.0 of
  the EBP system. Note that you should either proceed as described in Note 312090 or as described in
  note 402592.
  Allowing not local user administration for Internet Sales (Note 395070):
  If a central user administration is active, you can only create Internet Users with Transaction Internet
  Sales -> Manage Internet Users for the B2B Internet Sales scenario if the central user administration
  runs on the CRM system. If the central user administration runs on another system, you cannot create
  Internet Users. The solution for a not local central user administration is contained in a Support
  Package of CRM Release 2.0C and in the CRM standard release 3.0.
  Minimal Authorizations for the Service Users (Note 424982)
  According to the online documentation strong authorizations should be assigned to the various
  service users that are used by the Central User Administration (CUA). This leads to a security hazard
  because the defined RFC destinations can be misused. This note describes how to use the new roles
  that are delivered with the support package. The composite role SAP_BC_USR_CUA combines the
  various roles for Central User Administration (CUA) service users. The composite role exists only
  for documentation purposes. The single roles contained within the composite role are assigned
  directly to the service users. The single roles do not have menu entries, only authorization data, as
  the service users cannot log on to the system with a dialog logon (Communication User Type) and
  cannot call any transactions.

(C) SAP AG                                      ADM130                                               6-14
  Further Documentation



                      For additional information about mySAP
                      components, check:
                        SAP Notes category:
                          BC-SEC-USR: CUA, Users, Authorization, Roles
                        URL:
                          service.sap.com/rolemaps




       SAP AG 2002




(C) SAP AG                             ADM130                            6-15
  Unit Summary



                      You are now able to:

                         Describe the transition path to using roles
                         Use standard roles
                         Describe a test and production environment
                         for Central User Administration




       SAP AG 2002




(C) SAP AG                              ADM130                         6-16
                                                            Introduction: Exercises

                  Unit: Role Management
                  Topic: Role Conversion and Comparison


                  At the conclusion of this exercise, you will be able to:
                  • Convert Authorization Profiles into Roles




                  You are an administrator responsible for the system configuration.




1-1   Create an old authorization profile
      1-1-1 Log on to the R/3 backend system of the Internet Sales CRM system.
             Start the Role Maintenance Tool (Profile Generator) and create a Role named
             Z_FI##.
             Select the transactions FD01, FD02, FD03 from the SAP menu (choose
             Accounting→ Financial Accounting→ Accounts Receivable→ Master
             Records→ Create/Change/Display).
             Create the authorization profile.
             In the next Screen for defining the organization Levels of the role enter 1000 as
             Company Code.
             Set the missing authorization fields to "*".
             Save your authorization Profile and note the name, as it will be needed later on.
             _____________________________________________________
             Generate the authorization profile.
      1-1-2 Display the created authorization profile using transaction SU02.
             Copy the authorization profile to a new profile named Z:FI:OLD##.
             Activate this authorization profile.
             This is your old profile you want to convert into a new role.




(C) SAP AG                                  ADM130                                         6-17
1-2   Role conversion
      1-2-1 Convert Z:FI:OLD## using SU25 (identical). Please note the name of the Role
            being generated.
             ______________________________________________________
      1-2-2 Convert Z:FI:OLD## using SU25 (optimized). Please note the name of the role
            being generated.


             ______________________________________________________
      1-2-3 Compare the menus of the two generated roles. What is the difference?




(C) SAP AG                              ADM130                                       6-18
                                                     Introduction: Solutions

                  Unit: Role Management
                  Topic: Role Conversion and Comparison


                  At the conclusion of this exercise, you will be able to:
                  • Convert Authorization profiles into roles




                  You are an administrator responsible for the system configuration.




1-1   Create an old authorization profile
      1-1-1 Log on to the R/3 backend system of the Internet Sales CRM system.
             Logon with your user back-##.
             Start the Role Maintenance Tool (Profile Generator) and create a role named
             Z_FI##.
             Call transaction PFCG. Enter the name of the new role and choose Create.
             Enter a description for your role and save.
             Select the transactions FD01, FD02, FD03 from the SAP menu (choose
             Accounting→Financial Accounting→Accounts Receivable→Master Records→
             Create/Change/Display).
             Select Tab Menu. Click From SAP Menu button in the Copy Menus area.
             Select the transaction and click the Transfer button.
             Create the authorization profile.
             Select the Authorizations tab.
             Click the Change authorization data button.
             In the next screen for defining the organization levels of the role, enter 1000 as
             Company Code.
             Set the missing authorization fields to "*".
             Just Perform a click on the top Yellow Traffic Light and execute.
             Save your authorization profile and note the name, as it will be needed later on.
             _____________________________________________________
             Generate the authorization profile.



(C) SAP AG                                  ADM130                                          6-19
      1-1-2 Display the created authorization Profile using Transaction SU02.
             Call transaction SU02. Enter the name of the authorization profile of your
             role. Choose Create work area for profiles.
             Copy the authorization profile to a new profile named Z:FI:OLD##.
             Choose Utilities→Copy and enter the new name.
             Activate this authorization profile.
             Display your profile Z:FI:OLD##. Choose Profile→Activate two times.
             Now you can see your profile being marked as Act (activated).
             This is your "old" profile you want to convert into a "new" role.
1-2   Role Conversion
      1-2-1 Convert Z:FI:OLD## using SU25 (identical). Please note the name of the role
            being generated.
             Call transaction SU25. Choose the Copy data from old Profiles button.
             Select your profile and choose Activity Group→ Create identical to profile.
             ______________________________________________________
      1-2-2 Convert Z:FI:OLD## using SU25 (optimized). Please note the name of the Role
            being generated.
             Call transaction SU25. Choose the Copy data from old Profiles button.
             Select your profile and choose Activity Group→Create optimized to profile.
             ______________________________________________________
      1-2-3 Compare the menus of the two generated roles. What is the difference?
             Choose transaction PFCG and display the roles one after the other.
             The identical role doesn´t have a menu, the optimal profile has a menu
             containing the transaction from the original authorization profile.




(C) SAP AG                                 ADM130                                      6-20
  Interface Monitoring


                      1. mySAP Technology              7. Interface Monitoring



                      2. Configuring Internet Sales    8. System Monitoring



                      3. Configuring EBUYER            9. Backup Scenarios


                                                       Appendix Installation Scenarios
                      4. System Administration
                                                                Transaction Codes


                      5. Software Logistics



                      6. Role Management


       SAP AG 2002




(C) SAP AG                                    ADM130                                     7-1
  Interface Monitoring


                      Contents
                         Monitoring qRFC Communication
                         Monitoring ALE
                         generic RFC Monitoring and Performance




                      Objectives
                      At the end of this unit, you will be able to:
                         Monitor qRFCs
                         Monitor ALE Communication
                         Monitor Performance Problems with RFC
                         Communication




       SAP AG 2002




(C) SAP AG                                       ADM130               7-2
  qRFC Monitoring


                 qRFC Monitoring
  qRFC Monitoring qRFC Monitoring




                                                qRFC Monitoring
     qRFC Monitoring




                                                      qRFC Monitoring

                                                ALE Monitoring
                               qRFC Monitorig




                                                Generic RFC Monitoring and Performance




                    SAP AG 2002




(C) SAP AG                                                       ADM130                  7-3
  Message Tracking - Overview

        Communication                Mobile Client xyz
           Station
                                         Outbound
                                          Queue
                              DCOM
                                         Inbound
                                          Queue
              qRFC

     Inbound          Outbound
      Queue            Queue
    Client xyz        Client xyz
                                                                  Inbound
                                                                               Proxy
                                                                   Queue
     Inbound          Outbound                                                 BAPI
                                                                    OLTP
     Adapter           Adapter
                                             Outbound
                                                      qRFC
       Synchronization                        Queue                          Business
         BDOC Flow                            R/3 Ad.                         Logic

           Messaging                         Inbound             Outbound
                                     R/3                 qRFC                 Send to
             BDOC                             Queue               Queue
                                   Adapter                                    Server
             Flow                             R/3 Ad.             OLTP

  CRM Server                                                     OLTP SAP R/3

       SAP AG 2002




  The red dots show places to monitor the various components.
  Note that the monitors for the data exchange with the mobile clients and for the inbound/outbound
  queues on the mobile client will be covered in course CR540 CRM Middleware for Mobile
  Scenarios.




(C) SAP AG                                    ADM130                                                  7-4
  Message Tracking - OLTP SAP R/3




                                  Inbound
                                               Proxy
                                   Queue
                                               BAPI
                                    OLTP
                                                                        System Log, Dump
                                                                           Analysis, ...
                                             Business
   qRFC Outbound                              Logic
   Monitor (SMQ1)
                                 Outbound
                                              Send to
                                  Queue
                                              Server
                                  OLTP



                                OLTP SAP R/3

      Standard SAP R/3 monitoring tools may be used to track processes
      on the OLTP SAP R/3 system

       SAP AG 2002




  The same qRFC monitoring tools used on the CRM Server can also be employed on the OLTP SAP
  R/3 System.
  If an object is not processed correctly within the OLTP SAP R/3 system, and an error condition is
  not returned via BAPI parameters, the SAP R/3 System has to be checked.




(C) SAP AG                                   ADM130                                              7-5
  Standard SAP R/3 Monitoring Tools


      Standard SAP R/3 monitoring tools: CCMS
      Short dump analysis

                                                          What happened?
             No. of dumps:                                ...
                                                          What can you do?
                                                          ...
               Today             1                        Error analysis
               Yesterday         0                        ...
                                                          ...



                                                          System log:
                                                          System log:
      Viewing system logs
                                                          From date/time
                                                          From date/time                 ...
                                                                                         ...
                                                          To date/time
                                                          To date/time                   ...
                                                                                         ...

                                                          User:
                                                          User:                    ...
                                                                                   ...
                                                          ...
                                                          ...
                                                          Reading:
                                                          Reading:
                                                          Number of records read: 124
                                                          Number of records read: 124
                                                          ...
                                                          ...
       SAP AG 2002




  The Computer Center Management System (CCMS) is used to administer multiple SAP R/3 System.
  The ABAP short dump analysis is called via transaction ST22.
  The system log may also provide important information to find errors in the system. The system log
  is viewed via transaction SM21.
  For further information, refer to standard SAP system administration course ADM100.




(C) SAP AG                                   ADM130                                              7-6
  Inbound and Outbound Queue Monitoring


                             Client Queue Name                 Destination                  Entries

                             800    ...                        ...                          ...
                             800    CRM_SITE_0000000002        CRM_SITE_ 0000000002         14
                       ...   ...    ...                        ...                          ...


          Cl.     Queue Name                ...    Status    1. Date   1. Time    NxtDate    NxtTim

         800      CRM_SITE_0000000002 ... Nosend             2.1.2001 7:31        5.1.2001 9:14



                      Cl.    User                  Function Module        ...    Date       Time

                      800    CONN_MSA_MSE          client_employee_write ...     2.1.2001   7:31
                      800    CONN_MSA_MSE          client_employee_write ...     3.1.2001   8:23
                       ...   ...                   ...                   ...     ...        ...

      Normal condition: no error entries in any queues
       SAP AG 2002




  The consistency of all distributed data and processes is guaranteed even if individual components of
  the integrated system are temporarily unavailable. All calls and data transports take place
  asynchronously via buffers (queues). If individual components cannot be accessed, no information is
  lost and no delays occur in the overall schedule. There are inbound and outbound queues.
  qRFC queues are displayed in three steps:
     After specifying one or more clients, queue names, and queue destinations, the transaction SMQ1
     or SMQ2 displays a list of all queues that match the specified values.
     Now it is possible to select particular queues of interest and view further details.
     From the detailed view on the selected queues, it is possible to display the queue entries by
     double-clicking the corresponding queue.
  System paths:
  Middleware -> Monitoring -> Queues -> Display Outbound Queues (SMQ1)
  Middleware -> Monitoring -> Queues -> Display Inbound Queues (SMQ2).
  The same qRFC outbound queue monitoring used on the CRM System can also be employed on the
  SAP R/3 System.
  If an object is not processed correctly within the SAP R/3 System, and an error condition is not
  returned via BAPI parameters, the SAP R/3 System has to be checked.




(C) SAP AG                                        ADM130                                           7-7
  Message Tracking - CRM Server


      qRFC Inbound                                    qRFC Outbound
      Monitor (SMQ2)                                  Monitor (SMQ1)


                       Inbound     Outbound
                        Queue       Queue
                      Client xyz   Client xyz
                                                                            qRFC Outbound
                       Inbound     Outbound
                                                                            Monitor (SMQ1)
                       Adapter      Adapter
                                                           Outbound
                         Synchronization                    Queue
                           BDOC Flow                        R/3 Ad.

                            Messaging                      Inbound
                                                   R/3
                              BDOC                          Queue
                                                 Adapter
                              Flow                          R/3 Ad.
                      CRM Server

       BDoc Monitor                Flow Control            qRFC Inbound
                                   Trace Monitor           Monitor (SMQ2)
       SAP AG 2002




(C) SAP AG                                      ADM130                                       7-8
  The Standard Queue Scheduler



       Display status of qRFC scheduler for all CRM clients




        Cl.      Status    Last Scheduler Update     ...   Oldest Queue           Old. St.

        100 INACTIVE       2001.01.02 11:37          ...   CRM_SITE_00000032      STOP
        800 INACTIVE       2001.01.02 10:02          ...   CRM_SITE_00000002      STOP
         ...   ...         ...                       ...   ...                    ...


                                                 Queue with the
                                                  oldest entry




       SAP AG 2002




  Display the status of the qRFC standard scheduler for all CRM clients via Middleware ->
  Monitoring -> Queues -> Display qRFC Scheduler Information (SMWMSCHEDULER). The number
  of entries in the queues with time information is given here.
  The Replication & Realignment queues possess their own Queue Demon to stop queues (course
  CR540 CRM Middleware for Mobile Scenarios).
  The scheduler as well as the R/3 queues (queue name R3A*) need to be activated. This is
  automatically done by the system when an initial load is started. The Scheduler is used for the
  processing of inbound queues only after the data is put into the queues.




(C) SAP AG                                  ADM130                                            7-9
  qRFC Queues Overview of all CRM Clients



       Mapping: site names to queue names
       (SMWMQUEUES)


      Client    Site Name      Queue Name                 Last Date     Last Time         Empty
                                                                                          queue
      800       Trainer        CRM_SITE_00000001
      800       Demo           CRM_SITE_00000002          03.01.2001 10:33
      ...       ...            ...                        ...        ...


                                                            Last queue
     Specified in the
                                                              entry
     Admin Console
                                   Used by
                                    qRFC




       SAP AG 2002




  The mapping of the site specified in the Administration Console, to the queue used by qRFC can be
  looked up under:
  Middleware -> Monitoring -> Queues -> Display Site Queue Information (SMWMQUEUES).
  The qRFC status display lists the information about each CRM client in a separate line. Each line
  contains the scheduler status and the last data/time, when the scheduler was started. Furthermore, the
  queue names and the status of the queues with the oldest entries are displayed. To view the content
  of the inbound queues for a specific client, select the corresponding row.
  Inbound and outbound queues are automatically created for Mobile Clients when the site is created
  in the Admin Console.
     R = Read CRM inbound queue
     W = Write CRM outbound queue




(C) SAP AG                                     ADM130                                               7-10
  Site Type Concept

 Every receiver instance is represented by an abstract site
 Every site belongs to a site type, for example, Mobile Client, SAP R/3


               Same                                                     Same
              site type                                               site types




     Site A             Site B             Site C             Site D              Site E




                                                                      Non-SAP
          Mobile Clients             SAP R/3 System
                                                                   Systems via XML
       SAP AG 2002




  In an SAP CRM System environment, decentralized components, known as sites have to be
  connected to the central component permanently or temporarily so that messages can be exchanged.
  A site is the smallest addressable unit in replication and realignment (not users). They are identified
  by a global identifier (GUID). Each site has a site type. Sites of the same type use the same adapter
  for exchanging data between the CRM Server and the sites. There is a range of site types available
  for connecting SAP components. The site type assignments influence the ability of systems to
  subscribe sBDocs (not allowed for Site R/3) and the flow definition for a particular context:
     Example: Object Customer
     - Source site type: CRM
     - Target site type: CDB
     - Flow context: sBDoc initial load
  Sites are created in the Administration Console, a middleware tool for the administration of the data
  exchange of sites (decentralized components). An SAP R/3 System is created for example as a site
  using the site type R/3. SAP provides a number of standard site types: CRM, CDB, R/3, Mobile
  client, External interface for XML and External interface for IDocs. You can create your own
  customer-defined site types. IMG > CRM > Middleware and related components > Communication
  Setup > Create New Site Types.
  Bulk replication:
  The simplest replication type is the bulk replication. Typical examples for bulk-replicated data are
 customizing data (the T* tables) or employee data. They are always replicated to the receiving sites,
 as they have no filter criteria on individual fields. Messaging BDocs can be of type simple bulk (msg)
 (no criteria fields, no realignment, example: BUPA_MAIN), sBDocs can be of type bulk(s) (no
 criteria fields, but with realignment).




(C) SAP AG                                     ADM130                                               7-11
  BDocs


        Mobile Clients                                        Non-SAP
                                                              System

                             BDoc
                            Messages              CRM            CRM Server
                                               Middleware



                                             BDoc Messages                     BW



                          Communication
                             Station
                                                                       SAP R/3
                                                                       System




       SAP AG 2002




  BDoc messages within the CRM Middleware are the largest unit of data that can be handled. They
  represent the standard format for data exchange between Mobile Clients and the CRM Server.
  Definitions of all BDoc types are contained in the BDoc repository.
  BDocs are used
    For messaging on the CRM System
    For synchronization of data: transfer to and from the Mobile Clients
    Within Mobile Clients.




(C) SAP AG                                  ADM130                                            7-12
  Comparison: BDoc versus IDoc



   Business Document                                  Intermediate Document
                                                                                        Control
                                                                                        Control
                                        BDoc                                             Data
                                                                                         Data
        tRFC or qRFC                                       Asynchronous                 Status
                                                                                        Status
        Usage in CRM for data exchange                     Usage in ALE and EDI
        Possibly complex data structures                   Consisting of
        both in transport and processing                       Control record
        Runtime objects, for example,                          Data record
        services generated from BDoc
                                                               Status record
        repository information
                                                           Message-oriented
        Internally created
                                                           Transfers all fields
        Uses delta field communication




       SAP AG 2002




  An Intermediate Document (IDoc) is a SAP standard format for data transfer between systems.
  IDocs are mainly used for Application Link Enabling (ALE) and for Electronic Data Interchange
  (EDI). They are not used for processing inside an application.
  Business Documents (BDocs) are used by the CRM Middleware to exchange data with Mobile
  Clients. BDocs are the central data structure to process business objects internally.
  In contrast to IDocs, for which the internal processing has to be implemented manually, the coding to
  process BDocs may be generated automatically.




(C) SAP AG                                     ADM130                                             7-13
  BDoc Categories

 Two types of data transfer:
                                                                           SAP R/3 System
    Messaging

                                                                                        SAP BW


                                                                              Non-SAP System

    Synchronization
                                                     Mobile Clients



                                                       Mobile Clients




                                               Mobile Clients
       SAP AG 2002




  BDocs can be categorized in three groups:
   Messaging BDocs (mBDocs):
   - Messaging BDocs are new with CRM 3.0.
   - They do not exist in the CDB and no exchange with Mobile Clients is possible.
   - They are the basis for flows and are passed to services and/or adapters for further processing.
     For example, a messaging BDoc is like an envelope, with data inside the envelope which CRM
     middleware cannot access, and data on the envelope which CRM middleware can access. Each
     application uses different address information. For example, sales orders can be routed
     according to the sales organization.
   - Between segments and database tables in the CRM Middleware but in the CRM Applications,
     Bdocs transport entire instances (gross data).
   Synchronization BDocs (sBDocs):
   - Synchronization Bdocs are based on data stored in the Consolidated Database (CDB), and are
     used for synchronizing mobile clients. They allow the full replication and realignment rules
     based on all data in the CDB to be applied. Synchronization Bdocs correspond to the Bdocs
     already available with CRM 2.0B/2.0C.
   - Mapping between of BDoc segments and CDB tables, previously called Write BDocs, transport
     changed fields (delta information, net data).
   - Can be assigned to messaging BDoc types (n:1 relationship).
   Mobile Application BDocs:
   - Mapping between segments and database tables on the Mobile Clients only, previously called
     Read and Query Bdocs.




(C) SAP AG                                   ADM130                                             7-14
  Messaging BDoc – Messaging Flow

                              Inbound
                              Inbound              Inbound
                                                   Inbound                   Inbound
                                                                             Inbound
                               Queues
                               Queues              Queues
                                                    Queues                   Queues
                                                                              Queues
                                                                         Inbound Adapter
                             R/3 Adapter          XIF Adapter             (Mobile Clients)
                                     mBDoc                mBDoc
                                                                                       sBDoc*
                                                                         Mapping Service
                                                                         mBDoc
                                                                                  SynchFlow
          Messaging Flow




                                                  CRM Service
                                                  (Validation)                 CRM DB


                                              Replication Service
                                                                         mBDoc
                           Outbound Adapter   Outbound Adapter             Mobile Bridge
                                                                                   sBDoc*
                                                                             SynchFlow
                              R/3 Adapter         XIF Adapter
                                                                 XML /
                              Outbound BAPI
                              Outbound            Outbound
                                                  Outbound                    Outbound
                                                                              Outbound
                                                                 IDocs
                               Queuesstructures
                               Queues              Queues
                                                   Queues                      Queues
                                                                               Queues
       SAP AG 2002




  The communication diagram and the BDoc exchange scheme combine to go down to the exact
  details how CRM communicates inside.
  CRM 3.0 has two kinds of data flow in the CRM Middleware, based on synchronization Business
  Documents (BDocs) and messaging BDSocs.
  Bdocs are basically data containers for passing data to and from different applications.
  Messaging Flow: Infrastructure for passing data to the CRM Application and for processing data
  from the CRM Application is called notifications.
  Inbound may be the result of a load from an external system or a mapping of synchronization BDocs
  to messaging Bdocs. They are passed to the validation service in the CRM Server. The validation
  service checks (‘validates’) the contents of a BDoc. In case of a successful validation the data will be
  stored in the CRM Database and an outbound processing is triggered. Messaging flow dispatches a
  change notification to subscribed consumers (for example, R/3, Mobile bridge).
  The inbound adapter (Mobile Clients) triggers the flow, while the flow starting at the R/3 adapter or
  the XIF adapter is triggered by the CRM Applications. Both the R/3 adapter and the XIF adapter
  perform the mapping from external formats into BDoc format.
  The outbound adapter is a generic adapter that calls the receiving sites based on the site types and the
  receiver list.




(C) SAP AG                                        ADM130                                             7-15
  Flow Definition for BDocs

  Flow Definition = Assignment of Flow to Application Function Modules




        SAP AG 2002




The complete definition a specific BDoc can be checked using transaction SMO8FD:
Middleware -> Message Flow -> Display and Check Flow Definitions
The messaging flow contexts:
  MI0 Validate (MI: Messaging flow Inbound): Synchronization inbound flow, XML adapter and R/3
  adapter pass data to the CRM database. For initial load from SAP R/3 System, the validate method is
  called before the notification method.
  MO1 Notification (MO: Messaging flow Outbound): Delta distribution of one instance to
  subscribed sites and additional consumers such as BW adapter or mobile bridge triggered by CRM
  Server Application.
  MO2 Notification (multiple): Delta distribution of more than one instance (multiple case) to
  subscribed sites and additional consumers such as the BW adapter.
  MO3 Initial Load: Method PROCESS_INITIAL_LOAD transfers gross data only from the CRM DB
  to the CDB. The initial load from external systems into the CRM database uses first the context
  validate followed by the context notification, but not initial load.
  MO4 Direct Send: Data extract starting at Admin. Console (from CRM to external sites R/3, XIF).
  Table SMW3FDSTD contains the SAP standard flow definitions in the form of flow contexts. The
  SAP standard flow definitions are controlled by context entries in the BDoc type-specific and
  customer-specific tables. Table SMW3FDBDOC contains flow definitions that are BDoc type-
  specific but not customer-specific. If you want to override the standard flow, make the same entries
  for the same contexts as in the standard flow table SMWFDSTD. Table SMW3FDCUST contains
  the customer-specific and BDoc-specific flow definitions in the form of flow contexts. These entries
  override the BDoc type-specific flow and the standard flow. Additional definitions (for example, for
  the validation service can be found in table SMW3BDOCIF).



(C) SAP AG                                    ADM130                                              7-16
  Error Handling Configuration



    Error: Bdoc                                     Message      Service   Site Action
    • Type                                          <BDoc Type> <Service> <Site> Mail
    • Service
    • Site

                               Is in Table?         yes
                                                             Message      Service Action
                                       no                    <BDoc Type> <Service> Mail



                               Is in Table?          yes
                                                                       Message     Action
                                        no                             <BDoc Type> Mail



                               Is in Table?          yes

                                        no
                                                                         Default Action

       SAP AG 2002




  The Central Error Handling Service (CES) is started by the Flow Control after receiving internal
  or external error conditions (for examole, if a service returns the error code E). Each service uses the
  CES for error handling. The information about the subsequent service is kept in the Flow Definition.
  Depending on the error segment information, the CES starts CES actions. This diagramm shows how
  error actions are determined by the Central Error Handling Service. In three tables, error actions can
  be specified in terms of the following:
     The BDoc type, service and site
     The BDoc type and service
     Just the BDoc type.
  In order to determine actions for an error that has occurred, the CES looks into the three tables
  starting with the most specific level up to the least specific level (the default action). It performs all
  actions found only in the first matching level. The order in which the matching error entries in the
  table are processed is determined by a preceding number. These numbers are specified when the
  error actions are defined.
  The transaction for configuring the error handling may be found at:
  Middleware -> Message Flow -> Error Handler Settings. (Transaction SMW00)




(C) SAP AG                                       ADM130                                                7-17
  Display BDoc Messages

 Step one: Select a BDoc message                                    Processing
                                                                   state of a Doc

                                                                                 Flow Context
                               2                                                   of a BDoc



         1
                               Display
                              MW Trace             Display the
                                                    data part


     Select a Bdoc                       Display the
       message                          classical part




       SAP AG 2002




  The function Display BDoc Messages lists all BDoc messages (transaction SMW01: Middleware ->
  Monitoring -> Message Flow). It displays:
     The BDoc ID and BDoc type, the BDoc state, the flow context, the queue name, the date and time
     when the BDoc message was sent
     The flow control trace, the data and error segments, the service in which the error occurred (last
     service reached), andthe recipient list.
     It also shows the succession of BDocs if a mobile scenario is in place: The Original BDoc
     represents the first sBDoc being created (S-1). S-1 is mapped into messaging BDoc M-2, which is
     written onto the CRM database by the validation service. M-2 is not displayed. The validation
     service then creates messaging BDoc M-3. M-3 is the Reference BDoc which represents the
     predecessor of the BDoc in display, synchronization BDoc S-4. If an error ocurrs while the M-2
     was processed by the validation service, only S-1 with the error information is displayed. The
     same applies if an R/3 adapter has created an mBDoc. The Original BDoc is M-1, which is
     displayed alone in validation service error case.
  Successfully processed messages appear with a green light, those still in progress with a yellow light,
  and those with a terminal error condition appear with a red light.
  If a message is in process and does not get processed within a reasonable amount of time, it is
  possible to restart the message, view the message content, or discard the message. A BDoc message
  may be processed in one of the following ways:
     Mark as deleted (note that deleting BDoc messages can cause data inconsistencies)
     Retry processing




(C) SAP AG                                     ADM130                                               7-18
  Bdoc Messages: Error Analysis

                                         Errors
               Errors                  within the
               of the                  middleware
              Receiver




       SAP AG 2002




  Use transaction SMW01 to display the reason for an error in the BDoc processing. Select the BDoc,
  then you choose the errors button. Any errors within the middleware are displayed. If the processing
  in the middleware did not result in an error nothing is displayed. In that case you have to choose the
  button receivers, as the error occured because the receiver had problems with processing the data.
  To display only the BDocs that had rrors, do not just choose E* as the selection criteria for the BDoc
  state in the initial screen of transaction SMW01. Instead choose a selection for each status E01, E02,
  E03, E04 or any combination thereof. The selection will be much faster on the database.




(C) SAP AG                                     ADM130                                               7-19
  Middleware Trace


                        Display
                      the details



           2


           1




                            Select the
                             object




       SAP AG 2002




  From Display BDoc Messages you can access the middleware trace.
  An alternative path is to the middleware trace with additional information is: Middleware ->
  Monitoring -> Message Flow -> Display Middleware Trace (SMWT).
  You need to perform settings in the table SMOFPARSFA in order to use the function Display
  Middleware Trace. Please see the SAP Library.
  The Display BDoc Message Summary function lists the same BDocs as Display BDoc Messages but
  grouped according to site, message type (E, A, W, S, and I) and BDoc type.
  An alternative path is to the Bdoc Message Summary is: Middleware -> Monitoring -> Message
  Flow -> Display BDOC Message Summary (SMW02).




(C) SAP AG                                 ADM130                                          7-20
  Middleware Trace



     SMWT - Internal technical information,
             just for SAP Support




       SAP AG 2002




  System path:
  Middleware -> Monitoring -> Message Flow -> Display Middleware Trace (SMWT).
  Monitoring information can be selected and filtered according to various criteria.
  Successfully processed messages appear with a green light, those still in process appear with a
  yellow light, and those with a terminal error condition appear with a red light.
  If a message is in process and does not get processed within a reasonable amount of time, it is
  possible to restart the message, view the message content, or discard the message.




(C) SAP AG                                     ADM130                                               7-21
  Hints for an Error Analysis (Load Example)


     Check Display BDoc Messages including the middleware trace information
     Check the outbound queue
     Check the table BDOC_TRACK in the SAP R/3 System
     Check the outbound queue of the SAP R/3 System
     Check the inbound queue of the CRM System

              CRM                                                SAP R/3
                                            Delta
                                            Load
                                                                     Data Upload to
         Outbound Queue
                                                                      Application
                              2.                                                      3.
              1.
                                           Status
                                        Information
          Inbound Queue                                             Outbound Queue

                              5.                               4.
       SAP AG 2002




   Possible error situation: A business object has been changed in a CRM Server Application, but the
   change (delta load) is not received in the SAP R/3 System.
   In case of errors or missing data updates in the target system, you may perform the following steps:
      Check Display BDoc Messages including the middleware trace information
      Check the outbound queue
      Check the table BDOC_TRACK in the SAP R/3 System (which shows information on the data
      handling of the SAP R/3 application)
      Check the outbound queue of the SAP R/3 System
      Check the inbound queue of the CRM System
   Furthermore, verify the RFC destination and the logical system assigned to your site (in the Admin
   Console) and the CRM Middleware parameter settings in the CRM System and the SAP R/3
   System (for example, CRMRFCPAR).




(C) SAP AG                                    ADM130                                               7-22
  Message Flow Statistics

      SAP R/3 kernel application statistics
                                                           Response Time         =
       Kernel

     BDoc type

                              Wait Time        +        CPU Time          +      Database Time



      Statistic monitor for BDoc types, sites and queues


                                                                Inbound processing
                            BDoc
                         BDoc
                      BDoc
                               BDoc
                                                                Outbound processing
                       BDoc



       SAP AG 2002




  The message flow statistics are launched via:
  Middleware -> Monitoring -> Message Flow -> Display Message Flow Statistics (SMWMFLOW).
  In order to activate Message Flow Statistics, choose Goto -> Activate Statistics. Here the Kernel
  application statistics and the Middleware message flow statistics can be activated individually.
  Further information on how to active the monitors can be found in the SAP Library.
  The time to process BDoc messages in the CRM Middleware can be displayed using the Message
  Flow Statistics for BDoc types, sites, and queues. This monitor shows the total execution time for a
  BDoc message, which consists of the time it was waiting in an inbound queue plus the processing
  time. The processing time is the sum of the time the BDoc spend in the inbound adapter and in the
  two Flows. This monitor displays either the average execution time for all BDoc messages of one
  type or the execution time for only one single BDoc message.
  The kernel application statistics provide the CPU time and the database time that was used to process
  all BDoc messages of a BDoc type. The response time includes the CPU time and the database time.
  Note that the database time also includes some CPU time, so that these two times not necessarily
  sum up to the response time (compare SAP note 351207). It is also possible to display the executed
  times for the various services that were called with the selected BDoc type by pressing the Per
  service button.
  The SAP R/3 kernel application statistic monitor requires definition of the standard CCMS batch
  jobs.




(C) SAP AG                                     ADM130                                              7-23
  CRM Middleware Portal




                                                      ■   Generation
                                                           ◆ BDoc type: structures
                                                           ◆ BDoc type: other runtime
                                                           objects
                                                           ◆ Replication objects
                                                           ◆ Publications
                                                           ◆ Missing database indices
                                                           ◆ Generation of flow
                                                           definitions
                                                      ■   Runtime information
                                                           ◆ R/3 Adapter status
                                                           information
                                                           ◆ R&R: queue demon
                                                           ◆ BDocs in the flow
       SAP AG 2002




  The Middleware Portal provides a uniform view to all important monitors displaying generation and
  runtime information.
  The Middleware Portal is launched via:
  Middleware -> Monitoring -> Central Monitoring -> Middleware Portal (SMWP).




(C) SAP AG                                   ADM130                                             7-24
  ALE Monitoring


                 ALE Monitoring
                  ALE Monitoring




                                               qRFC Monitoring
  ALE ALE Monitoring




                                               ALE Monitoring
                                                        ALE Monitoring
      Monitoring
                              Ale Monitoring




                                               Generic RFC Monitoring and Performance




                   SAP AG 2002




(C) SAP AG                                                       ADM130                 7-25
  Application Link Enabling




                                       Financial accounting
                                       Controlling (central)
                                       SOP (central)
                                       Information systems:
     PP                                     Inventory                   Sales, shipping, and
     Inventory                              Purchasing                  billing
     management                             Sales                       Purchasing of trading
     Sales, shipping, and              Purchasing (central)             goods
     billing (internal)                Reference system for             Inventory
     Purchasing (local)                master data and                  management
     PM                                control data                     Controlling (local)



                                    ALE
     SOP (local)




       SAP AG 2002
                        Distributed Business Processes


  The goal of the SAP ALE (Application Link Enabling) concept is to continue developing the
  architecture of SAP R/3 System in order to implement application networks comprising
  asynchronously coupled SAP applications without rigid ties to a central database.
  Each enterprise may have different reasons for distributing business processes. These reasons may be
  technical or business-related. Depending on enterprise's reasons, the design of its distributed
  architecture will look different compared to that of other enterprises.
  All architectures have a distribution that covers complex business processes between different
  systems or enterprises.
  ALE is the business process integration within the Business Framework.
  ALE allows flexible configurations through loosely coupled applications.




(C) SAP AG                                    ADM130                                             7-26
  ALE Example Scenarios




                                         Customizing data

       Financial accounting                                            Sales, shipping and
       Central controlling                                             billing
       Central SOP                          Master data
                                                                       Purchasing of trading
       Information systems:                  MATMAS                    goods
            Inventory                                                  Inventory
            Purchasing                                                 management
            Sales                        Application data
                                                                       Local controlling
       Central purchasing
       Reference system for
       master data and
       control data                                                          LS SALES


          LS T90CLNT090

       SAP AG 2002




  In SAP terms, a logical system is a client in a database. Messages are exchanged between logical
  systems.
  Customizing data synchronization includes, for example, organizational units (company codes,
  division, plant), units of measurement, and many other parameters that have to be set in the system.
  The Customizing settings have to be identical in certain areas in both systems before data can be
  exchanged.
  Master data distribution: Cross-system master data can be maintained centrally and then distributed.
  The final values are assigned locally. A view of the master data can also be maintained locally. In
  this case there is always one maintenance system for each view. The master data is transferred to a
  central SAP R/3 System and distributed from there. Support is available from the Shared Master
  Data (SMD) tool.
  Application data distribution: The application data is distributed between the systems, which are
  involved in the business processes and defined in the distribution model.




(C) SAP AG                                     ADM130                                              7-27
  IDoc Record Types: Data Container




                  Control record              IDoc ID
                                              Partner
                                              IDoc type and logical message
                                              External structure Control part


                  Data records

                      Control section              Application data




                  Status records                IDoc ID
                                                Status information




       SAP AG 2002




  Every IDoc in the SAP database consists of:
    One control record
    A set of data records, which form a segment tree
    A set of status records, the number of which grows over time
  The data to be exchanged between the two systems using the IDoc interface contains:
    IDocs (consisting only of one control record and multiple data records)
    Status information (consisting only of status records)




(C) SAP AG                                   ADM130                                     7-28
  Interfacing Technology: Asynchronous BAPI



      BAPIs can be called asynchronously by using IDoc technology



     System 1                                               System 2


                               Idoc                 Idoc
                                                                  SAP R/3,
                                                                  non-SAP



        Application                                 BAPI   BOR     Application




       SAP AG 2002




  Applications can call BAPIs synchronously or asynchronously. ALE functions, such as maintaining
  BAPIs in the distribution model and receiver determination can be used for both types of call.
  Note that BAPIs that are called synchronously should only be used to read external data, so that
  database inconsistencies are avoided if errors occur during data transfer.
  For example, the application in the external system calls a BAPI synchronously to create a FI
  document. By thoroughly checking the data in the external system, the application can use the
  functions of a two-phase commit. It is easier if the BAPI is called asynchronously because ALE error
  handling functions ensure data consistency. The documents are therefore duplicated in the system
  that was called.




(C) SAP AG                                    ADM130                                              7-29
  BAPI - ALE Integration

  - Receiver determination
  - Call of generated            Distribution
    function module                 model

                                                      IDoc       Segment filter


                                                                    Field                  Generated
                                 Data filter                     conversation
        Generated                                                                          function module
        function                                                                           (inbound)
        module(outbound)
                               BAPI -> IDoc
                                                                           Input
                               conversion                                                    BAPI -> IDoc
                                                     tRFC                  control
                                                                                             conversion
                                                        or
                               Segment filter          EDI
                                                                        Serialization
                                   Field
                                                                                                Call of
                                conversation                     IDoc
                                                                                                 BAPI
                              Version change                                                   function
                                                                                                module

                                 IDoc
                                                                        Application data
                                                                        and IDoc status      IDoc status
   Database            Link             Dispatch              Database                       determinatio
                                        control                           Simultaneous            n
                                                                             update
        SAP AG 2002




  BAPIs are implemented as asynchronous interfaces. You generate a BAPI-ALE interface for an
  existing BAPI and implement it in the ALE business process.
  If you transfer data asynchronously within ALE using a BAPI, the following process occurs:
     Instead of the BAPI, a function module of the generated BAPI-ALE interface is called in the
     calling system (client) and the data from the BAPI is transferred to the IDoc of the function
     module.
     This IDoc is sent to the calling system (server).
     The BAPI and the data from the IDoc are called in the calling system using another function
     module.




(C) SAP AG                                         ADM130                                                    7-30
  Transactional RFC (tRFC) Monitoring



     Caller       Function Module        ...   Date       Time Status text

     Training     swe_event_log_write ...      2.1.2001 7:31      Transaction recorded (LUW
     CRM          smo8_flow_restart   ...      3.1.2001 8:23      Field symbol has not yet be
     ...          ...                 ...      ...      ...       ...




                                                                          Detailed
                                                                          analysis




              Normal condition: no error entries
                                (Status text: Transaction executing)


       SAP AG 2002




  System path:
  Middleware -> Monitoring ->Transactional RFC -> Display Transactional RFC Requests (SM58).
  Executing transaction SM58 generates a selection screen, on which you can select the display period,
  user name, function, destination and status of transactional RFCs. Almost any combination (single or
  multiple values, ranges, and exclusions) of these parameters is possible.
  If a system or application exception is raised during the processing of a tRFC Logical Unit of Work
  (LUW), the target system returns this error back to the sending system. The status of this LUW is
  updated with the exception error message (red background color of status message).
  You obtain information about the caller, function module, target system, date, time, and status text
  (see diagramm). Additionally, you obtain information about the transaction ID, host, current
  transaction code, program, client, and number of attempts to establish the connection.




(C) SAP AG                                     ADM130                                             7-31
  Status Monitor for ALE Messages (4.6C)




       SAP AG 2002




  The status monitor displays the status of all IDocs available in the local client.
  IDocs can be displayed at the first level, sorted according to:
    Status values
    Logical systems
    Message type
  Instead of the message types, the associated business objects and BAPIs can be displayed. Messages
  without assignment to business objects are listed under the message type.




(C) SAP AG                                    ADM130                                            7-32
  Generic RFC Monitoring and Performance


                    Generic RFC Monitoring and Performance
    Generic RFC Monitoring and Performance
  Generic RFC Monitoring and Performanche




                                                                                                      qRFC Monitoring
                                                             Generic RFC Monitoring and Performance




                                                                                                      ALE Monitoring


                                                                                                      Generic RFC Monitoring and Performance
                                                                                                               Generic RFC Monitoring and Performance




                                                SAP AG 2002




(C) SAP AG                                                                                                              ADM130                          7-33
  Processing Modes



       Business documents in an SAP System can be processed in the
       following ways:
             By users working online in the system (= user interface)
             By background jobs
             Driven by interfaces to other systems (SAP or external)
                Batch input interface (transfer by file)
                RFC interface




       SAP AG 2002




  Online processing: Users logged on to SAP R/3 create or process documents in dialog mode, for
  example, at a call center, where calls from customers are entered as orders in SAP R/3.
  An example of background processing is delivery due list processing. During the night, customer
  orders are automatically analyzed in bulk and converted into deliveries. Typically, in background
  processing a program reads and creates documents using data already present in the system.
  Example of Batch Input processing: The data to be converted into SAP R/3 documents often already
  exists in electronic form, for example, as a file. Rather than have users manually enter this data, SAP
  R/3 enables you to transfer file data into SAP R/3 using programs that run in background processing
  via an interface. This is a special form of background processing that is often used as a
  communication interface between SAP R/3 and other systems. One example is accessing customer
  orders on non-local servers. One strategy is that the non-local servers send their data to a central
  server from which it is transferred to SAP R/3 using Batch Input.
  RFC interface processing: SAP Systems communicate with other data processing systems not just
  through files, but also directly using remote function calls (RFCs). RFCs exchanges can be between
  SAP Systems or between SAP systems and external systems. Using RFC, an external system can
  transfer data to, and trigger programs in, SAP systems. SAP systems can do the same in an external
  system. For example, the SAP R/3 System creates transport requests for stock movements and sends
  them via RFC to an external warehousing system. After executing the goods movements, the
  warehouse system triggers the necessary IDocs and ALE movements in the SAP R/3 System to
  confirm delivery.




(C) SAP AG                                      ADM130                                               7-34
  Remote Function Calls (RFCs)

      Remote function calls (RFCs) are used for:
             Communication between the SAP application layer and SAP GUIs
             Communication between two SAP Systems, or between an SAP System and an
             external system
             Starting processes in parallel within one SAP System
      There are 4 types of RFCs:
             Synchronous RFCs
                For communication between systems
                For communication between the SAP application layer and SAP GUIs
             Asynchronous RFCs
                For communication between systems
                For parallel processing
             Transactional RFCs
                For ‘safe’ communication between systems
             qRFC
                For specified processing sequence
       SAP AG 2002




(C) SAP AG                                  ADM130                                    7-35
  'Simple’ Transaction Step

  Presentation




                      Network
                                Application




                                               Network
                                                          Database
       Server                       Server                   Server
                                                                           User starts transaction
                                                                           Dispatcher receives request

                                      Wait time

                                      Roll in time

                                     Load time
                                     Processing time (1)
                Response
                time                                           Database time (1)


                                     Processing time (2)

                                                                Database time (2)

                                     Processing time (3)
                                                                           Rollout from work process
                                          Roll out time

                                                                             GUI displays result
       SAP AG 2002




(C) SAP AG                                    ADM130                                                   7-36
  Transaction Step with Synchronous RFC




                                                 Network
                      Network
  Presentation                  Application                  Database                     External
       Server                       Server                      Server                     System



                                      Wait, Roll in & Load time

                                      Processing time (1)                                  RFC start
                                                                    CPI/C Communication
                                      Program rolls out
                                      after RFC is started
                                     Roll out time
                Response                                                 RFC + CPIC
                time                                                     time
                                     Roll wait time
                                      = Program not in
                                      work process




                                     Roll in time                                           RFC end


                                     Processing time (2)


       SAP AG 2002




  For dialog steps with synchronous RFC, RFC+CPIC time is the runtime of the RFCs plus the time
  for setting up the connections. During a synchronous RFC, the ABAP program is rolled out from the
  work process. This time can be observed as roll wait time.
  For dialog steps with asynchronous RFC, RFC+CPIC time is the runtime for setting up the
  connections to the external system. No rollout occurs. The program continues the work after starting
  the asynchronous RFC.
  See also SAP Note 8963 in SAPNet.




(C) SAP AG                                      ADM130                                                 7-37
  RFC Monitoring : Statistical Records




                                                                                   Example:
                                                                                   Statistical record
                                                                                   with RFC
                                                                                   processing; see
                                                                                   multiple roll
                                                                                   processes,
                                                                                   RFC+CPIC time
                                                                                   and roll wait time
       SAP AG 2002




  Statistical Records (STAD)
  RFC+CPIC time can be found under time details in the single records. For dialog steps with
  synchronous RFC, RFC+CPIC time is the runtime of the RFCs plus the time for setting up the
  connections.
  There is one record per dialog/batch step. For RFCs an additional record is written at the end of the
  dialog/batch step where they occur if the RFC connection is closed. In case of registered external
  programs, the RFC connection may remain open beyond the end of the dialog/batch step. The RFC
  record is written after the connection is closed.
  Trouble-shooting:
    RFC+CPIC time >> Roll wait time indicates a problem during the communication between the
    systems. Check whether the reason is due to:
    - A slow network connection
    - No work process available in the receiver system
    If RFC+CPIC time ≈ Roll wait time, this indicates that the communication between the systems is
    fast. You may need to perform further performance analysis of the RFC function module in the
    receiver system.
    To see the RFC subrecords (as shown on the next slide), use the RFC button or scroll down.




(C) SAP AG                                     ADM130                                              7-38
  RFC Monitoring : Statistical Sub-Records (1)




       SAP AG 2002




  A separate RFC statistical record is created for every dialog step (or batch step) if remote function
  calls occur. In this record, all outgoing and all incoming RFC calls are noted (outgoing calls are
  client subrecords and incoming are server subrecords).
  In the RFC stat record details, you can see the individually called function modules and their report
  names. The task type R is also artificial, since RFC calls could be made from any other task type.
  Under Client destination subrecords, you get the summary of all calls per destination (for up to the
  stat/rfcrec number of destinations).
  Under Server destination subrecords, you get the summary of all incoming calls per destination (for
  up to the stat/rfcrec number of destinations). In the summary, you see the total number of calls for
  the destination, not only those that have detail entries in the record. If there are calls for more than
  stat/rfcrec destinations, you do not see the number of calls for destinations with no summary entry.




(C) SAP AG                                       ADM130                                                7-39
  RFC Monitoring : Statistical Sub-Records (2)



     Response time (all) = sum(calling times)

     Calling time = Rem exec time + wait for gateway time

     RFC+CPIC time = time spent for RFC/CPIC handling (including roll wait time)

     Roll wait time = time spent in roll context waiting for RFCs

     CPU time = sum(CPU usage) (on the server where the record is found)

     Calling time (client) = Rem exec time + (wait for) gateway time + network time

     Calling time (server) = Rem exec time + (wait for) gateway time

     Response time = Time spent in the executing work process + wait time


       SAP AG 2002




  Response time is the sum of response times of all collected RFC calls for the related dialog/batch
  step. For synchronous RFC, the single RFC response time is the total time from when the call was
  started until the result is returned. For asynchronous RFCs, the response time ends as soon as the
  receiver confirms reception of the data.
  The CPU and DB times are collected for all locally used CPU and DB times of the RFC calls. The
  wait time is the time until a free dialog work process is be allocated to process the calls.
  The remote CPU, DB, and wait times are not known by the sender, so you may see a significant gap
  between response time and the sum of the others in the case of synchronous RFCs.
  On the receiver side, an incoming RFC request is put in the dispatcher queue as soon as the RFC call
  data is transferred. From there on, the wait time is measured as usual by the dispatcher until the
  request is dispatched to a dialog work process.
  The calling time of the client (sender side) is measured in the client gateway and is computed as
  receiving time for the RFC request until it returns the result (for synchronous calls). The remote
  execution time is measured on the server side (receiver), and transferred back to the client to be
  stored in the client subrecord. A delay in the communication between both gateways would be seen
  as a time difference here.
  Calling time for the server record is measured at the server side gateway in the same way (that is, the
  difference to the remote execution time in the server record is the time spent in the server gateway
  and is usually 0 or very small).




(C) SAP AG                                      ADM130                                               7-40
  RFC Monitoring: RFC Destinations

  Transaction SM59




       SAP AG 2002




  RFC destinations are maintained with transaction SM59 or choosing Tools -> Administration ->
  Network -> RFC destinations. A double-click on a destination takes you to a detailed screen.
  Test Connection leads to response times or an error message (should be the first topic checked in
  case of trouble).
  Simple connection types (use F4 to get complete list):
    I: Connection to application server with same database
    3: Connection to SAP R/3 System
    T: Start an external program via TCP/IP
  Depending on the connection type, you get different options, for example:
  SAP R/3 System: Target host and System number
    External program via TCP/IP: Start or Registration
    External program via TCP/IP: Program (external program name), host
  Trouble-Shooting: Test response times by using button Test Connection .
  Recommendation for configuration: Use Load distribution instead of a single target host!




(C) SAP AG                                     ADM130                                                 7-41
  RFC Monitoring: Performance Trace




       SAP AG 2002




  To start the performance trace, enter transaction code ST05.
  The diagramm shows the SQL and RFC part of a performance trace of a transaction-SM66 dialog
  step. Before creating the trace, choose settings, deactivate the option Display only abbreviated
  information, and activate the option Display connection and status.
  In the upper part of the screen, you see the RFC trace record: pawdf085_CTP_24 p48212 Client
  SAPGUI_PROGRESS_INDICATOR. This provides us with the information that follows below.
  Sender: pawdf085_CTP_24 (local SAP R/3 instance)
     Receiver: p48212 (in this example: local PC)
     Function module: SAPGUI_PROGRESS_INDICATOR (sets the status message Connection to
     <instance>)
  In the lower part of the screen, you see the SQL trace records (for exampl,e accesses to table
  SWWHRINDEX): SELECT WHERE MANDT = ‚001‘ AND OBJID ...




(C) SAP AG                                    ADM130                                             7-42
  Troubleshooting: Incoming RFC Load (Problem)



        SAP GUI
        SAP GUI
                                                                          Online requests
        SAP GUI
        SAP GUI                                   Online                  may be blocked if
                                                  requests                RFC requests are
        SAP GUI
        SAP GUI
                                                                          not limited
        SAP GUI
        SAP GUI
                                                                        SAP R/3




  SAP R/3
  SAP R/3



                                                     RFC               Receiver (server)
                                                     requests

  Sender (client)


       SAP AG 2002




  Online requests may be blocked if asynchronous RFC requests are not limited. This may result in
  bad response times for online users. Therefore, it is necessary to control the incoming aRFC load on
  the receiver side
  On the receiver side for aRFC with an RFC server group specified, performance also depends on the
  available resources and the setting of the RFC resource parameters, depending on whether the call is
  performed synchronously or asynchronously (see SAP Note 74141).




(C) SAP AG                                    ADM130                                              7-43
  Troubleshooting: Incoming RFC Load (Monitoring)



      Work process monitor (SM50)
             Running reports SAPLARFC and SAPLERFC (aRFC and tRFC only)
             Access to tables ARFC (tRFC only)
             Work processes in status stopped, reason CPIC
      User Overview (SM04)
             Type: RFC
             Up to release 4.0: Terminal name APPC-TM
      Workload Monitor (ST03N): RFC Profile
      Statistical Records (STAD)
             Records with task type R
      TRFC Monitor (SM58)
             (tRFC only)

       SAP AG 2002




(C) SAP AG                              ADM130                            7-44
  Troubleshooting: Incoming RFC Load (Solution)


      Create a SAP R/3 instance dedicated for RFC requests
           if the number of incoming RFC calls is very high


      Use RFC resource management parameters (not used by Internet Sales or
      Enterprise Buyer):
           RFC server groups
           Set SAP R/3 parameters that limit the number of work processes used
           for RFC processing
           The SAP R/3 instance profile parameters for configuring aRFC
           resource management are the same as for tRFC




       SAP AG 2002




  If you expect a high incoming RFC/ALE load (as a rule of thumb > 10000 requests per hour), you
  should configure an SAP R/3 instance dedicated to RFC processing. Limit the number of work
  processes on the instance so that the CPU is not overloaded.
  If you expect a low volume of RFC load, use the SAP R/3 instance profile parameters to control the
  incoming RFC/ALE load.
  Preconditions for using RFC resource management parameters are:
     RFC server groups defined and used.
     If used together with ALE: Inbound dispatch mode = scheduled; Inbound processing mode =
     parallel.
     Kernel patches as prescribed in SAP Note 74141.
  To dynamically set RFC resource management parameters, use SAP program RSARFCD.




(C) SAP AG                                    ADM130                                             7-45
  Troubleshooting: Outgoing RFC Load (Monitoring)



      Work Process Monitor (SM50)
             Running reports SAPLARFC and SAPLERFC
             (aRFC and tRFC only)
             Access to tables ARFC (tRFC only)
             Work processes in status stopped, reason CPIC
      Workload Monitor (ST03N): RFC Profile
      Statistical Records (STAD)
             Records with high Roll wait time
      TRFC Monitor (SM58)
             tRFC only




       SAP AG 2002




(C) SAP AG                               ADM130              7-46
  Troubleshooting: High RFC Load



  Transaction code: ST03N




       SAP AG 2002




  To call the Workload Monitor, use transaction code ST03 or ST03N.
    Choose Clients for monitoring the outgoing load, Servers for monitoring the incoming load.
    Under Function modules, find performance data for specific RFC modules.
    Under Remote destination, find for example the incoming requests by destination.
  To perform troubleshooting, identify the sender program of the RFC load:
    To identify critical function modules and the sender system, use the RFC profile (ST03) or the
    Statistical Records Monitor (STAD/STAT).
    Function modules ARFC_DEST_CONFIRM, ARFC_DEST_SHIP, ARFC_RUN_NOWAIT and
    RFC_PING build the framework for tRFC processing. You need not analyze them in detail.
    To find the sender program, use Function builder (SE37) and the where-used list.




(C) SAP AG                                   ADM130                                            7-47
  Unit Summary



                      You are now able to:

                         Monitor qRFCs
                         Monitor ALE Communication
                         Monitor Performance Problems with RFC
                         Communication




       SAP AG 2002




(C) SAP AG                               ADM130                  7-48
  Further Documentation



                      Additional information about Interface
                      Monitoring
                         CR500 CRM Middleware Overview
                         BIT300 Application Link Enabling Technology
                         service.sap.com/ale
                         service.sap.com/crm




       SAP AG 2002




(C) SAP AG                              ADM130                         7-49
                                                     Introduction: Exercises

                  Unit: Interface Monitoring
                  Topic: Monitoring of qRFC Communication


                  At the conclusion of this exercise, you will be able to:
                  • Monitor qRFC Communication




                  You are an administrator responsible for the ystem configuration.




1-1   Your Instructor has deregistered the inbound queue of the Internet Sales CRM server,
      which is received from the backend R/3 System. He has also changed some
      Customizing to create some errors.
      1-1-1 Logon to the CRM server:
             Client :801
             User: CRM-##
             Check if the Inbound Queue is deregistered. Do not register the inbound Queue
      1-1-2 Create a customer master record in the backend R/3 system of the Internet Sales
            CRM server (As in the Exercise 3 of the Chapter Configuring Internet Sales)
             Log on to the R/3 System:
             Client: 801
             User: back-##


             Create the customer master record:
             Choose transaction VD01(Logistics → Sales and Distribution → Master Data
             → Business partners → Customer → Create → Sales and Distribution)

             Account group:        Sold-to party R/3 CRM
                                    (not Sold-to party CRM --> R/3 or
                                   Sold-to party )
             Sales organization: 3020
             Distribution channel: 30
             Division:             00




(C) SAP AG                                ADM130                                        7-50
             Maintain all the required entry fields in the customer master record. The
             following fields are required entry fields in the general data view Address:

             Title:                Company
             Name:                 qrfc_##
             Search term 1/2:      _##
             Street:               Baker Street
             House number:         1
             Postal code:          12345
             City:                 Boston
             Country:              US


             Save the customer master record and make a note of the number.

             ____________________________________________________

      1-1-3 In the CRM server check the inbound Queue. Try to find the entries
            corresponding to your customer. Which status do these entries have?
      1-1-4 Execute the two LUWs for your customer manually.
             Check the flow control trace for entries concerning your customer.
             Which messaging BDoc flow contexts have been processed?
            Display the corresponding BDoc. Are there any error messages available?
      1-1-5 Create another customer master record in the backend R/3 System of the
            Internet Sales CRM Server as well as a contact person.
             Name of the new Customer: qrfc2_##
             Create a contact person for your customer under the general data view contact
             persons.
             Create the customer master record:
             Choose transaction VD01(Logistics → Sales and Distribution → Master Data
             → Business partners → Customer → Create → Sales and Distribution)

             Account group:        Sold-to party R/3 CRM
                                   (not Sold-to party CRM --> R/3 or
                                   Sold-to party )
             Sales organization: 3020
             Distribution channel: 30
             Division:             00

             Maintain all the required entry fields in the customer master record. The
             following fields are required entry fields in the general data view Address:




(C) SAP AG                                ADM130                                            7-51
             Title:                Company
             Name:                 qrfc2_##
             Search term 1/2:      qrfc2_##
             Street:               Baker Street
             House number:         1
             Postal code:          12345
             City:                 Boston
             Country:              US

             Create a contact person for your customer under the general data view Contact
             persons

             Name:                 Smith_##
             First name:           John
             Department:           Purchasing
             Function:             Buyer

             Press the button Home Adress and enter the home adress for the customer.

             Street:               Baker Street
             House number:         1
             Postal code:          12345
             City:                 Boston
             Country:              US



             Save the customer master record and make a note of the number.

            ____________________________________________________
      1-1-6 In the CRM server check the inbound queue. Try to find the entries
            corresponding to your customer. Execute the LUWs for your customer
            manually.
             Look at your Business Partner Master Data. What is missing?
             Check the BDoc for entries concerning your customer.
             Display the corresponding BDos. Look at the error messages.
             Display the errors for the correspondig BDoc. Are there any error messages
             available?.




(C) SAP AG                               ADM130                                           7-52
                  Unit: Interface Monitoring
                  Topic: IDOC Monitoring


                  At the conclusion of this exercise, you will be able to:
                  • Monitor transmitted IDocs




                  You are an administrator, who is responsible for the System
                  configuration.


2-1   IDOC Monitoring
      2-1-1 Log on to the EBP/CRM Server.
             Client: 800
            User: ebp-##.
      2-1-2 Start the transactional RFC Monitor. Check if there are any Entries for any
            users. Do not log off.
      2-1-3 Create a shopping basket using the Browser.
             Client: 800
             User: buyer-##
             Create a new shopping basket (select Shop)
             Search in the Requisite catalog Requisite Inhouse for PC Installation in the
             category Electronics and add one item to your shopping cart. Decide to order
             this item from the catalog.
             Order your shopping basket.
             Check the status of your shopping basket.
             Perform the goods receipt using the browser.
             Enter any description and confirm the goods receipt.
             Immediatley perform some refreshes for the transactional RFC from the last
             exercise.
             You should see an entry for sending an IDOC to the R/3 backend system.
             Which caller is displayed for the RFC call?
            Attention! You have to be very quick to see an entry in transaction SM58.
      2-1-4 Start the IDoc Monitor.
             Which IDoc has been sent? What is the staus of the IDoc?
             Check if you can identify the data for the IDoc.

(C) SAP AG                                 ADM130                                         7-53
                 Unit: Interface Monitoring
                 Topic: RFC Monitoring


                 At the conclusion of this exercise, you will be able to:
                 • Monitor RFC Calls




                 You are an administrator, who is responsible for the System
                 configuration.


3-1   RFC Monitoring
      3-1-1 Start the Workload Analysis (ST03N) on your EBP/CRM Server. Choose
            observe only the last minutes. Choose to observe only the RFC Data.
            What is the average response time for RFC calls?
      3-1-2 Display the RFC profiles for clients.
             Locate the RFC call for creating a purchase order.




(C) SAP AG                               ADM130                                   7-54
                                                         Introduction: Solutions

                  Unit: Interface Monitoring
                  Topic: Monitoring of qRFC communication


                  At the conclusion of this exercise, you will be able to:
                  • Monitor qRFC communication




                  You are an administrator responsible for the system configuration.




1-1   Your Instructor has deregistered the inbound queue of the Internet Sales CRM system,
      where is receipt from the backend R/3 system. He has also changed some customizing
      to create some errors.
      1-1-1 Log on to the CRM system:
             Client :       801
             User:          CRM-##


             Check if the inbound queue is deregistered. Do not register the inbound queue.
             Call transaction SMQR (Middleware-->Administration -->
             Register/Deregister Queues).
             The type for the queue R3A* is set to U.
      1-1-2 Create a customer master record in the backend R/3 system of the Internet Sales
            CRM server (As in the exercise 3 of the chapter configuring Internet Sales)
             Log on to the R/3 system:
             Client: 801
             User: back-##
             Create a customer master record:
             Choose transaction VD01 (Logistics → Sales and Distribution → Master Data
             → Business partners → Customer → Create → Sales and Distribution)

             Account group:        Sold-to party R/3 -->CRM
                    (not Sold-to party CRM --> R/3 or Sold-to party)
             Sales organization:                  3020
             Distribution channel:                30
             Division:                            00

             Maintain all the required entry fields in the customer master record. The
(C) SAP AG                                ADM130                                         7-55
             following fields are required entry fields in the general data view Address:

             Title:                                Company
             Name:                                 QRFC_##
             Search term 1/2:                      QRFC_##
             Street:                               Baker Street
             House number:                         1
             Postal code:                          12345
             City:                                 Boston
             Country:                              US
             Save the record and note the customer number.
             ____________________________________________________

      1-1-3 In the CRM server check the inbound queue. Try to find the entries
            corresponding to your customer. Which status do these entries have?
             Select transaction SMQ2 (Middleware-->Monitoring-->Queues--> Display
             Inbound RFC Queues). You can see one entry named
             R3AD_CUSTOME<Customernumber>, that have the status ready.
      1-1-4 Execute the LUW for your customer manually.
             Select transaction SMQ2. Select the entries concerning your customer.
             Select the entries and choose Edit--> Execute LUW.
             Check the BDoc entries concerning your customer. Which messaging BDoc
             flow contexts have been processed?
             Select transaction SMW01. Limit the display to the last minutes. You can
             see entries for your customer (it is not so easy to really identify your
             customer). The flow contexts MIO (Validation) and M01 (notification) have
             been processed.
             Display the errors for the corresponding BDoc. Are there any error messages
             available?
            Select your BDOC and click the ERRORS and RECEIVERS buttons. No
            error messages should be displayed.
      1-1-5 Create another customer master record in the backend R/3 system of the Internet
            Sales CRM server as well as a contact person.
             Name of the new customer: qrfc2_##
               Create a contact person for your customer under the general data view
               Contact persons.
               Create a customer master record:
               Choose transaction VD01 (Logistics → Sales and Distribution → Master
               Data → Business partners → Customer → Create → Sales and
               Distribution)

                Account group:                            Sold-to party R/3 -->CRM
                                                           (not Sold-to party CRM --> R/3 or
                                                          Sold-to party)
                Sales organization:                       3020
                Distribution channel:                     30
                Division:                                 00

(C) SAP AG                                ADM130                                            7-56
                Maintain all the required entry fields in the customer master record. The
                following fields are required entry fields in the general data view Address:

                Title:                            Company
                Name:                             QRFC2_##
                Search term 1/2:                  QRFC2_##
                Street:                           Baker Street
                House number:                     1
                Postal code:                      12345
                City:                             Boston
                Country:                          US


                Create a contact person for your customer under the general data view
                Contact persons.

                Name:                                     Miller_##
                First name:                               John
                Department:                               Purchasing
                Function:                                 Buyer

                Click the Home Address button and enter the home address for the
                customer.

                Street:                                   Baker Street
                House number:                     1
                Postal code:                              12345
                City:                                     Boston
                Country:                                  US

            Save the data.
      1-1-6 In the CRM server check the inbound queue. Try to find the entries
            corresponding to your customer. Execute the two LUWs for your customer
            manually.
             Select transaction SMQ2. Select the entry concerning your customer. Select
             the entries and choose Edit-->Execute LUW.
             Look at your business partner master data. What is missing?
             Select transaction BP (Master Data --> Business Partner --> Maintain
             Business Partner). Enter the customer number from the R/3 backend and
             choose Display. Choose tab Relationship. There is no contact person
             maintained for your business partner.
             Check the BDoc for entries concerning your customer.
             Display the corresponding BDoc. Look at the error messages.
             Select transaction SMW01. Limit the display to the last minutes. There are
             a incompleted entries with an error for the step BUPA_MAIN and
             BUPA_REL.
             You can see entries for your customer with errors (it is not so easy to really
             identify your customer). The flow contexts MIO (Validation) have not been
             processed successfully.

(C) SAP AG                               ADM130                                           7-57
             Display the errors for the corresponding BDoc. Are there any error messages
             available?
             Select your BDoc and click the ERRORS and RECEIVERS buttons. You
             can find the error message: For object BU_PARTNER , number range
             interval XX does not exist if you select the earliest BUPA_MAIN MBDOC
             and choose the ERROR button.




(C) SAP AG                               ADM130                                        7-58
                  Unit: Interface Monitoring
                  Topic: IDOC Monitoring


                  At the conclusion of this exercise, you will be able to:
                  • Monitor transmitted IDocs




                  You are an administrator responsible for the System configuration.



2-1   IDOC Monitoring
      2-1-1 Log on to the EBP/CRM server.
             Client:         800
            User:           ebp-##.
      2-1-2 Start the transactional RFC monitor. Check if there are any entries for any users.
             Select transaction SM58 (Middleware-->Monitoring-->Display Transactional
             RFC Requests). Display entries for any user. There are no current entries.
            Do not log off.
      2-1-3 Create a shopping basket using the Browser.
             Client: 800
             User:     buyer-##
             Create a new shopping basket (Select Shop)
             Search in the Requisite catalog Requisite Inhouse for PC Installation in the
             Category Electronics and add one item to your shopping cart. Decide to order
             this item from the catalog.
             Order your shopping basket.
             Check the status of your shopping basket.
             Perform the goods receipt using the browser.
             Enter any description and confirm the goods receipt.
             Immediately perform some refreshes for the transactional RFC from the last
             exercise.
             Select the window where transaction SM58 - Transactional RFC monitor
             has been started and perform a refresh.
             You should see an entry for sending an IDoc to the R/3 backend system. Which
             Caller is displayed for the RFC Call?


(C) SAP AG                                 ADM130                                         7-59
            Attention! You have to be very quick to see an entry in transaction SM58.
            The caller of the displayed IDoc is WF-BATCH.
      2-1-4 Start the IDoc Monitor.
             Which IDoc has been send? What is the status of the IDoc?
             Select transaction BD87. Select the created IDocs of the actual day. You
             can see IDocs of the message type MBGMCR and the status 03, meaning
             data passed to port ok.
             Check if you can identify the data for the IDoc.
             If you double click on the IDoc number you can diplay all data of a selected
             IDoc. If you know the time your IDoc was sent, you can try to find your
             IDoc.




(C) SAP AG                                ADM130                                     7-60
                 Unit: Interface Monitoring
                 Topic: RFC Monitoring


                 At the conclusion of this exercise, you will be able to:
                 • Monitor RFC Calls




                 You are an administrator responsible for the system configuration.



3-1   RFC Monitoring
      3-1-1 Start the workload analysis (ST03N) on your EBP/CRM Server. Choose
            observe only the last minutes. Choose to observe only the RFC data.
             What is the average response time for RFC calls?
            Select transaction ST03N. Choose the last minutes load (15 minutes) within
            the detailed analysis. Choose the task type RFC. Here you can find the
            response time of RFC requests that have been processed by your
            applications server.
      3-1-2 Display the RFC profiles for clients.
             Choose in the left part of the screen: Service engineer
             Choose RFC Profile--> RFC Clients Profile.
             Locate the RFC call for creating a purchase order.
             There is a function module named BAPI_PO_CREATE.




(C) SAP AG                               ADM130                                       7-61
  System Monitoring


                      1. mySAP Technology              7. Interface Monitoring



                      2. Configuring Internet Sales    8. System Monitoring



                      3. Configuring EBUYER            9. Backup Scenarios


                                                       Appendix Installation Scenarios
                      4. System Administration
                                                                Transaction Codes


                      5. Software Logistics



                      6. Role Management


       SAP AG 2002




(C) SAP AG                                    ADM130                                     8-1
  System Monitoring



                      Contents
                         Monitoring mySAP Technology components
                         without SAP Basis Systems
                         Monitoring mySAP Technology components
                         with SAP Basis Systems
                         Core Business Process Monitoring


                      Objectives
                      At the end of this unit, you will be able to:
                         Understand the tools for monitoring the different
                         components
                         Integration of the different monitoring tools
                         Build a monitoring infrastructure




       SAP AG 2002




(C) SAP AG                                       ADM130                      8-2
  Architecture Overview

   Frontend             Internet Middleware              Application   Backend
                                                         Middleware


     Internet
      Vendor
                         Enterprise Buyer                              R/3 OLTP
      Vendor's                                                          System
     Web Server
                                                            EBP
                                                            EBP
                       Web Server        ITS       BC
     Internet
     Customer         Catalog Server

                                                                         BW
                        CRM Internet Sales
     Internet
     Employee                          SAP J2EE Engine

                       Web Server        ITS       BC
                                                             CRM
     Intranet              IPC          TREX      IMS                    APO
     Employee

       SAP AG 2002




(C) SAP AG                                 ADM130                                 8-3
               Components Without SAP Basis Systems

                    Components Without SAP Basis Systems
                                                           Components Without SAP Basis Systems
     Components Without SAP Basis
 Components Without SAP Basis Systems

                                                                                Components Without SAP Basis Systems




                                                                                                                       Components Without SAP BasisSystems
                                                                                                                             Components Without SAP Basis
                                                                                                                                                          Systems

                                                                                                                       Components With SAP Basis Systems

                                                                                                                       Special Monitors

                                                                                                                       Appendix




                                                            SAP AG 2002




(C) SAP AG                                                                                                                                ADM130                8-4
  Architecture Overview

   Frontend             Internet Middleware              Application   Backend
                                                         Middleware



                         Enterprise Buyer



                       Web Server        ITS       BC

                      Catalog Server



                        CRM Internet Sales
                                       SAP J2EE Engine

                       Web Server        ITS       BC


                           IPC          TREX      IMS


       SAP AG 2002




(C) SAP AG                                 ADM130                                8-5
  General Operating System Tool for Windows:
  PERFMON

                                                             Example
                                                           Windows NT
                                                           server with
               Time for network transfer                     ITS and
                                                           Web server
             ITS response time

        SAP response time
                                                             Red
                                                            Red         CPU time (total)
                                                                       CPU time (total)
     Transaction starts                                      Blue       CPU time (ITS AGate process)
                                                            Blue       CPU time (ITS AGate process)
                                                             Green
                                                            Green       CPU time
                                                                       CPU time
                                                                        (MS Web server process)
                                                                       (MS Web server process)
                                                             Yellow
                                                            Yellow      Bytes received
                                                                       Bytes received
                                                             Light blue Bytes sent
                                                            Light blue Bytes sent




       SAP AG 2002




  Perfmon is a Windows standard tool for measuring CPU consumption, network load and time and
  other information, such as paging rate or disk queue length. Is is a useful tool for all Microsoft based
  parts of the internet and application middleware. For example SAP Note 203845 describes how to
  analyze ITS and a Web browser during a Web transaction using PERFMON.
  You cannot use Perfmon in combination with PCanywhere to make useful performance
  measurements. The CPU and network load of PCanywhere is quite high and will falsify the results.
  To start Perfmon on a Windows NT computer, choose Start → Run and enter perfmon.
  The performance data can be stored in a file for delayed analysis.




(C) SAP AG                                      ADM130                                                 8-6
  General Operating System Tool: SAPOSCOL


                                                     Central Monitoring System

                                                                                  RZ20
        Component
        Without
        SAP Basis

             SAPOSCOL
                                     Data
                                   transfer
             - CPU
             - Paging
             - Swap space
             -…                                                                  OS07




       SAP AG 2002




  SAPOSCOL and RFCOSCOL are necessary to monitor mySAP.com subcomponents (without SAP
  Basis System) at the operating system level.
  SAPOSCOL is a stand alone program available for almost all operating system platforms, which
  determines operating system data like CPU idle/used or paging rates and stores this data in a shared
  memory segment of its host. SAPOSCOL runs only once per host (normally as a service for NT).
  The data of SAPOSCOL can be analyzed by using the local SAP system or transferred to a central
  monitoring system (CMS).
  There are two ways to transfer SAPOSCOL data:
    Besides installation of SAPOSCOL you have to install a stand-alone gateway and a program
    called RFCOSCOL. An RFC destination (type TCPIP) points from CMS to the stand-alone
    gateway starting RFCOSCOL directly. RFCOSCOL transfers SAPOSCOL data to CMS on
    demand. For more information, see SAP Note 202934.
    The functionality of RFCOSCOL and the stand-alone gateway can be replaced by using an agent
    program called SAPCCMSR.
    To make SAPOSCOL data available in CMS, run transaction AL15 once to define a remote
    SAPOSCOL destination. Afterwards, you can select the remote destination in the operating system
    monitor for remote systems (transaction OS07).
    SAPOSCOL data can be seen in the alert monitor (transaction RZ20) in CMS. Using a gateway,
    the setup procedure is described in SAP note 210890. Using an agent, the SAPOSCOL data is
    directly available in the monitor All Monitoring Contexts of the monitor collection SAP CCMS
    Technical Expert Monitors.




(C) SAP AG                                    ADM130                                               8-7
  Principle of SAP CCMS Agents


                                             CMS



                                          RFC                              JAVA
               SAPOSCOL

        Process
         Process                              Agent
                                              Agent                        JAVA
                                                                         Interface
                                                     Data
               External                             Supplier
                                          Data
             Components                  Supplier

                                                                      SAP Instance
                                   External                              Monitoring
                                   Software                               Segment

                              Log File
                                                         Alert File




       SAP AG 2002




  Agents are independent executable processes with RFC-capable interfaces and an interface to the
  shared memory.
  A CCMS agent communicates with the CMS using RFC. As an RFC Server, it offers access to the
  data in its monitoring segment. For example, this access is, used in the monitoring transaction RZ20.
  The agent creates the local configuration files and the RFC destination in the central system itself
  during its registration. As an RFC client, it sends data proactively to CMS, in order to place in a
  cache to allow faster display, or to trigger auto reaction methods.
  Agents allow you to:
    - Include mySAP.com components that are not available through any ABAP interfaces, such as
       an Internet Transaction Server (ITS).
    - Include components that are not part of the SAP environment.
    - Make available several connection routes to a shared memory segment.
    - Optimize reading and writing of data from a performance point-of-view.
  The following components are also already integrated into the agents:
    - Log file agent for generic checking of log files and reporting of problems in the monitoring
       architecture
    - RFCOSCOL for remote access to SAPOSCOL data (used, for example, by ST06 and OS07)
    - Network Data
       Configuration of the Network environment (Interfaces, DNS Configuration)
       Network Metrics (such as the length of time taken for a DNS address resolution)
    - DLL and Java interfaces for connecting additional components into a central monitoring
       environment.




(C) SAP AG                                     ADM130                                               8-8
  SAPCCMSR and SAPOSCOL



                                                    SAP / Non-SAP Instance


                                                  SAPOSCOL                processX

      Central Monitoring                                                   processX
                                          dev_proc
           System
                                                                          processY

                                                                         Application
                      RZ20                       SAPCCMSR


                                                                            Log




       SAP AG 2002




  There are three types of agents available: SAPCM3X, SAPCCM4X, and SAPCCMSR.
  SAPCM3X
    Allows the central monitoring of mySAP.com instances of SAP R/3 Release 3.X through the
    CCMS monitoring architecture (3.X systems have no CCMS monitoring architecture of their
    own). Please follow SAP Note 308061.
  SAPCCM4X
    Improves the monitoring of SAP R/3 Systems from SAP R/3 Basis Release 4.X or higher. This
    agent provides a additional way of linking to the monitoring information in the shared memory of
    a mySAP.com instance. Access in this way is therefore independent of the performance status of
    the monitored application server. For further information, see SAP Note 322075.
  SAPCCMSR
    Monitors components on which there is not an active mySAP.com instance (such as log files,
    stand-alone database, or operating system components). This agent is displayed on the slide.
    All agents can transfer SAPOSCOL data via RFC to CMS. All agents have a logfile adapter. They
    can analyze logfiles to find specific strings and to transfer those logfile rows to CMS.
    Detailed information about installation of agents can be found in SAP Note 209834 and in service
    marketplace http//service.sap.com/systemmanagement -> System Monitoring and Alert
    Management in the document CCMS Agents: Features, Installation, and Usage .




(C) SAP AG                                   ADM130                                              8-9
  Remote Operating System Monitor



                                                      Detailed log information
                                                      Detailed log information




                                    Detailed operating
                                     Detailed operating
                                    system information
                                     system information

                                                                     Detailed alert information
                                                                     Detailed alert information




       SAP AG 2002




  SAPOSCOL information transferred by SAPCCMSR can be displayed and analyzed centrally in
  CMS using transaction RZ20. Detailed information is shown for:
  File systems: Freespace / Percentage used
    - CPU: Utilization
    - Paging: Page in / Page out
    - OS-Collector: SAPOSCOL running?
    - Network: time for naming resolution, and so on
    - If the logfile adapter is configured, the matching lines of the monitored logfiles are shown. In
        the example above, the logfile dev_rout is analyzed for search pattern failed.
    - Process monitoring: SAP Note 451166 describes how to configure SAPOSCOL to monitor the
        existence and CPU and memory consumption of single processes. For example, the existence of
        the process java.exe located on a non-SAP host could be checked.
  CCMSR is especially designed for components without SAP instances. You can use it for various
  components of the Internet middleware.




(C) SAP AG                                    ADM130                                              8-10
  ITS Overview

                            Middleware
  Frontend                                                                         Component
                                                                                    System

    Web                    Web Server
  Browser               HTTP        ITS                    ITS AGate                   R/3
                       Server     WGate




                                                            Service and
                                                           template files



                      Monitoring techniques:
                        Use ITS admin tool
                        Central monitoring of AGates using RZ20
                        Perfmon
       SAP AG 2002




  Running Perfmon on the computer with the ITS allows you to analyze performance problems due to:
     - Response time ITS (measured with PERFMON)
     - Network load (PERFMON)
     - Response time SAP (measured with transaction STAD/STAT in the SAP backend system)
  To exclude performance problems due to CPU, memory bottlenecks, or to the outgoing network, you
  must run PERFMON on the computer with the ITS.
  For a detailed example, see SAP Note 203845.
  The performance behavior of the ITS-Agate process should be checked regularly. This is be done
  either using the Web based ITS administration tool or by setting up central monitoring of ITS.




(C) SAP AG                                   ADM130                                          8-11
  ITS Administration Instance (1)

                                                             Web based ITS
                                                              Web based ITS
                                                           administration tool
                                                            administration tool




                                                       Current performance
                                                       Current performance




       SAP AG 2002




  The ITS Admin instance (Performance view) gives you an overview of the current situation of the
  ITS. Information is available for current as well as historical sessions.
  Choose Overview. All ITS instances with session and thread information are displayed
  Select the ITS instance you want to monitor. Choose Performance. This function offers several
  options:
    - Performance summary - For details on Agate runtime information. You can analyze the time
       distribution.
    - Performance details – For information about worker threads and SAPGUI for HTML
       connected to the ITS
    - Performance history - To monitor cumulative performance over a length of time. The tool
       prompts you for the desired time interval and graph type (if you like a graph display). You can
       specify averages (the average value for each time interval displayed) or peaks (the maximum
       value for each interval).
    - Choose view performance log or view performance graph. If you chose view performance
       graph, you see averaged or maximum values for session usage, workthread usage, and hits per
       second.
    - User Sessions – User overview
  For more information, refer to the ITS Administration Guide or the help file directly included in the
  performance section.




(C) SAP AG                                     ADM130                                               8-12
  ITS Administration Instance (2)

  ITS log file directory:
        <ITS installation directory>\2.0\<virtual ITS>\logs\

  ITS Performance history: file performance.log




      Evaluate historic bottlenecks and critical situations, like:
             High load situations (hits/sec, available work threads and user sessions,
             high turnaround times, ...)
             Hardware bottlenecks (CPU load, memory load, disk space problems,
             and so on)

       SAP AG 2002




  For each AGate instance, the following details are displayed:
    - Visible from left to right in the graphic: Time stamp, the AGate, available sessions, maximum
       number of sessions, available work threads, maximum number of work threads, hits/sec,
       turnaround time, hits, uptime, ITS user CPU %, ITS kernel CPU %, total physical memory,
       available physical memory, total virtual memory, and available virtual memory
    - Not visible in the graphic: Memory load %, total disk space, free disk space




(C) SAP AG                                    ADM130                                             8-13
  Central Agate Monitoring



        Central Monitoring System                                                            ITS
                                                                         SAPCCMSR
                                                                         SAPCCMSR
                                       RZ20
                                                          C                   DLL
                                                                              DLL
                                                       RF

                                                                                   AGate
                                                     RF
                                                        C
                                                                                             ITS
                                                                         SAPCCMSR
                                                                         SAPCCMSR
                                                                              DLL
                                                                              DLL



                                                                                   AGate


       SAP AG 2002




  The Agate of ITS can be monitored centrally by CMS while using the SAPCCMSR agent. On the
  one hand, SAPCCMSR can transfer operating system information delivered by SAPOSCOL located
  on ITS host. On the other hand, a shared library can be linked to SAPCCMSR. This library connects
  to the shared memory segment of the Agate to pull monitoring information. The agent while using
  RFC transfers the monitoring data to CMS. For ITS configuration, see SAP Note 418285.
  In CMS a new rule based monitor must be defined which is described in SAP Note 418285. This
  monitor shows detailed information about the ITS admin instance (status, sessions, workerthreads,
  registry, processes, and so on)
  Performance problems in the ITS are reported in the ITS log files. Hardware bottlenecks on the
  computer where the ITS runs are reported by the tool SAPOSCOL.
  ITS log files can be accessed:
     - From the ITS Admin instance
     - From the CCMS Alert Monitor RZ20.
  SAP note 452797 describes two tools which expand the ITS monitor in transaction RZ20. These
  generic tools are able to:
     Start the browser with a well-defined URL: This tool is used to start the ITS administration tool
     directly out of the CCMS alert monitor.
     Display the content of files located on the ITS host: This tool is used to display the global services
     file for instance. The SAPCCMSR agent transfers the file information.




(C) SAP AG                                       ADM130                                                8-14
  Business Connector


                                                                           Web based BC
                                                                            Web based BC
                                                                         administration tool
                                                                          administration tool




                                                  Monitor BC log files.
                                                   Monitor BC log files.
                                        Physically located in \sapbc\server\logs.
                                        Physically located in \sapbc\server\logs.
       SAP AG 2002




  The SAP Business Connector (BC) Server uses log files to maintain an audit trail of services it
  executes and errors that occur. These files contain a historical trace you can use to diagnose
  application failures, analyze server performance, and trace server-related events.
  The audit log (<drive>:\sapbc\Server\logs\audit.log) maintains an audit trail for all services that the
  server executes. For each service, the server adds two records that contain information about the
  service. When it begins execution, it records a timestamp of when execution began. When the
  service terminates, it records a timestamp of when the service terminated. You can use this log to
  determine all services requested from the server and which client requested each service.
  The error log (error.log) maintains information about all errors and exceptions that have occurred in
  the SAP BC system. You can use this log for debugging problems with services.
  The Server log (server.log) maintains information about the version of the SAP BC Server.
  The session log (session.log) maintains information about all sessions in the SAP BC system. The
  SAP BC Server creates a session when a SAP BC client connects to the server to execute services.
  Each record in the Session Log includes a timestamp of when a user established a connection with
  the SAP BC Server.
  The statistics log (stats.log) maintains statistical information about the consumption of system
  resources. You can use this information to determine the cause of performance problems on your
  server.
  The transaction log (txin.log, txout.log) maintains information about inbound and outbound
  guaranteed delivery transactions. The server writes a record for each critical operation it performs for
  a guaranteed delivery transaction. Use these logs in conjunction with the appropriate job store
  (inbound or outbound) to determine more information about a guaranteed delivery transaction.




(C) SAP AG                                      ADM130                                               8-15
  Central Business Connector Monitoring



          Central Monitoring
                                                           Business Connector Host
               System

                                RZ20
                                                                          BC
                                                                          BC

                                                                      Jmon-API
                                                                      Jmon-API

                                             RF
                                                C


                                                              SAPCCMSR
                                                              SAPCCMSR




       SAP AG 2002




  The Business Connector can be monitored centrally by installing an Add-On package. A Jmon API
  included in the package enables Business Connector to read from and write to the shared memory of
  the SAPCCMSR agent. SAPCCMSR transfers the monitoring data to CMS.
  The setup of central monitoring for the Business Connector is quite simple. After installing the
  package, the administrator has to customize which components of the Business Connector should be
  monitored using the common Web based administration tool. The setup of the Jmon-API, the start of
  the corresponding data suppliers, and the installation of the SAPCCMSR agent will be done
  automatically.
  In CMS, a new monitor has to be set up to display the monitoring information of Business
  Connector. At operating system level, the existence of the Java VM is checked (process monitoring
  done by SAPOsCol). Besides detailed performance information of Business Connector, the
  connection state to the SAP systems and the listeners configured are checked. Furthermore, error
  messages are displayed.
  The Add-On package will be available in Service Marketplace http://service.sap.com/connectors.
  Enter the Business Connector part and check the download area.




(C) SAP AG                                   ADM130                                            8-16
  Remote Monitoring for IPC (1)




               IPC
                IPC
        administration tool
         administration tool




       SAP AG 2002




  The IPC Service Manager is used for starting and stopping IPC services. By default, IPC consists of
  the following services:
     - SAP IPC Server
     - SAP IPC Dispatcher
     - You can also use NT service manager to control the services
  The IPC Remote Server Monitor can be used to test server response, display the server log file, and
  so on. To start the IPC Remote Server Monitor, choose Start → Programs → SAP Internet Pricing
  and Configurator → Monitor.
     - For a remote connection, enter the hostname of where IPC Server is running.
     - For a local connection, enter the localhost.
  As of IPC 3.0, the IPC dispatcher is a (stripped down) IPC Server. It offers all the system commands
  of every IPC server. You can connect to it with the monitor (just enter host, port, and password in the
  login dialog), retrieve statistics, and check worker thread state.




(C) SAP AG                                     ADM130                                               8-17
  Remote Monitoring for IPC (2)




                                                                                          Log
                                  Test

                                                                 Ping




               Stats




       SAP AG 2002




  The Remote Debugger is currently able to:
    - Test the server's responsiveness by sending it a number of pings.
    - Display extensive server statistics including number of active server threads, number of
       active/removed sessions, average response time, free memory (only useful with some VMs),
       timeout settings and more.
    - Display permanently updating information about the server's worker threads, the threads that
       handle all connections.
    - Display system information about the server in XML format including the contents of all
       property files, all system properties (incl. classpath, java VM version), the exception log file,
       open SCE configs, and so on.
    - Display the last n lines of the server log file.
    - Change the server's timeout parameters while it is running.
    - Restart or stop the server.
    - Show graphical histories of the most important server statistics.
    - Connect to any server session (that is fool the server into thinking that the Monitor's requests
       come from another session).
    - Get information about all IPC commands that the server knows, including their complete API.
    - Execute commands or command sequences.
    - Show a Dispatcher's registration history (3.0 or later).
    - Show statistical information of a Dispatcher and all its servers (3.0 or later).
  For more information, see the IPC Debug Guide (file debug_guide.html in
  <drive>:\Program Files\SAP\ipc\doc\spc).




(C) SAP AG                                      ADM130                                                8-18
  Remote Monitoring for IPC (3)


                                               Various administrative
                                                Various administrative
                                               commands:
                                                commands:
                                               ••Ping
                                                  Ping
                                               ••System info
                                                  System info
                                               ••Logfile
                                                  Logfile
                                               ••Monitoring
                                                  Monitoring
                                               ••Server (re)start
                                                  Server (re)start




       SAP AG 2002




  Various administrative tasks can be executed under Commands .
    Ping: Ping will send a number of pings to the server. A ping is a very small command that will
    receive a very small response. It is useful for testing how responsive a server is.
    System Information: This command (menu only) requests system information from the server.
    Show Logfile: This command will display a number of lines from the server's log file.
    Show Statistics: Displays server statistics.
    Watch: Shows the graphical history window. With this method, the monitor will query the server
    for its statistics in regular intervals and show a graphical overview of the results.
    Connect To Session: This command connects to any of the IPC Server's active sessions. The
    server will answer the monitor's commands as if they would come from the given session
    Execute Commands: Opens a dialog that lets you enter commands and their parameters, execute
    the commands, and check their results.
    Worker Threads: Can be selected in the Command menu. This command will open a dialog
    where the status of all worker threads is regularly updated.
    Stop Server: Stops the IPC server.
    Restart Server: Restarts the IPC server.




(C) SAP AG                                   ADM130                                            8-19
  Monitoring an IPC Dispatcher

            Dispatcher is a normal IPC server now
            All commands (statistics, log file, worker threads) are available
            Different: Session timeout is one minute
            (monitoring sessions will timeout soon)




        SAP AG 2002




  As of IPC 3.0, the Monitor is able to display information about a dispatcher and all the servers it
  knows in a single table. Connect to the dispatcher instead of to a server, and select
  Dispatcher/Servers.
  The Server Overview shows the state of the dispatcher and all servers that it currently knows (up,
  down, deaf = not responding until timeout), as well as some performance data (average response
  time in microseconds, commands executed until now, currently open sessions). Click on a line to
  show full server statistics.
  The dispatcher keeps an internal log of everything that happened on every server (only the last 20
  actions are kept). The Monitor’s dispatcher menu can be used to view the last actions on a certain
  server or of all servers (if you don’t select a server). This is easier to read as the whole dispatcher log
  file.
  Please note that servers connect/disconnect dynamically. This means that if a server goes down it
  will be marked down for a while and then just vanish from the table. You need to remember how
  many servers are supposed to be registered at a given dispatcher.




(C) SAP AG                                       ADM130                                                  8-20
  Application Log: Monitoring Index Management
  Service
     Choose transaction SLG1 to check the application log for an error which
     might occur during indexing or deindexing



   Enter SDOK in field Object



   Enter indexing in field
   Sub-object




       SAP AG 2002




  The application log allows you to check the details of an error that occurred during indexing or
  deindexing.
  An error might occur if a document that was marked for indexing could not be found. Another error
  source might be a wrong document language that is not supported by the Index Management Service
  or the search engine in use.
  Additional checks through application log
    The application log allows you to check the details of any error that occurred during indexing or
    deindexing.
     - Call transaction SLG1.
     - In field Object enter the name SDOK.
     - Insert INDEXING in field Subobject.
     - Choose Enter.
    For example, errors can occur if:
     - A document that was marked for indexing cannot be found.
     - A document is in a language that is not supported by the Index Management Service or the
       search engine.




(C) SAP AG                                    ADM130                                             8-21
  Index Management Service / SAP Search Engine (I)

                                                           To analyze indexing problems,
                                                            To analyze indexing problems,
                                                              call transaction SKPR07.
                                                               call transaction SKPR07.

                                                               For a list of documents
                                                                For a list of documents
                                                             that could not be indexed
                                                              that could not be indexed
                                                               or deindexed, in frame
                                                                or deindexed, in frame
                                                           Extras choose Problem cases.
                                                            Extras choose Problem cases.

                                                                For document details,
                                                                 For document details,
                                                             choose Marked documents.
                                                              choose Marked documents.




       SAP AG 2002




  To analyze indexing problems, start transaction SKPR07.
  For a list of documents that could not be indexed or deindexed, in Extras choose Problem cases.
  For document details, choose Marked documents.
  On the Tools tab page, enter a physical information object classes (PHIO class) to be indexed
  (display format) and press the Diagnosis button in the application tool bar. A list of check results is
  displayed. To start the index generation, press the Trigger process button.
  Press SSR Monitor to jump into the search server monitor (transaction SRMO).




(C) SAP AG                                      ADM130                                                8-22
  Index Management Service / SAP Search Engine (II)



                                                                 Checking settings
                                                                 Checking settings
                                                               and RFC connection
                                                                and RFC connection
                                                              with transaction SRMO
                                                              with transaction SRMO




       SAP AG 2002




  Checking the Settings
    - Choose the tab page RFC destinations.
       Two RFC destinations are listed for the search server relation, one for the action I (index) and
       one for action S (search).
    - Select the entry for the RFC destination for action I.
    - Under Search Machine Settings, choose Connection test.
  For further analysis, you can set and analyze trace level for IMS Module Provider. See SAP Note
  340044.




(C) SAP AG                                      ADM130                                               8-23
  Central IPC/IMS Monitoring




         Central Monitoring System

                       RZ20                                            IPC/IMS Host
                                                      RFC
                                                                      SAPCCMSR
                                                                      DLL       DLL


                                                                                    IPC


                                                                          IMS




       SAP AG 2002




  In the future, the IPC and the IMS can be monitored centrally in CMS while using the SAPCCMSR
  agent. On the one hand, SAPCCMSR can transfer operating system information delivered by
  SAPOSCOL. On the other hand, a shared library can be linked to SAPCCMSR. These libraries
  connect to the IPC and the IMS to pull monitoring information. The agent while using RFC transfers
  the monitoring data.
  A heartbeat of both programs is shown in CMS .




(C) SAP AG                                   ADM130                                             8-24
  Requisite Catalog / Allaire JRun


      Frontend                                        Middleware

                                Web Server                 Catalog Server


                                                          JRun Servlet Engine
         Web
       Browser                 Web Site     JRun                 Requisite
                                                                BugsEyeTM




                                                                  Oracle
                                                                  RDBMS


                                                                        Transfer database
                                                                         Transfer database
                                                                       log via SAPCCMSR
                                                                        log via SAPCCMSR
                                                                          agent to CMS
                                                                           agent to CMS
       SAP AG 2002




  The Requisite BugsEyeTM catalog consists of Java software and Web pages that are executed inside
  a Java servlet runtime environment. The servlet engine is Allaire JRun. In addition, for data storage
  the catalog uses an Oracle RDBMS including a ConText cartridge.
  The JRun software consists of the servlet engine and a Web server extension that transfers requests
  between the client and the servlet engine.
  To check if the servlet engine is running, run the following script:
        http://<Server_name>/servlet/SimpleServlet
     You should see the message This is output from SimpleServlet.
  The errors reported by the underlying Oracle database into the alert logfile, can be transferred to
  CMS by using the SAPCCMSR agent.




(C) SAP AG                                     ADM130                                              8-25
  Allaire JRun

                                                            JRun writes different logs
                                                             JRun writes different logs
                                                            of JRun for monitoring
                                                             of JRun for monitoring
                                                            performance, traffic, and errors
                                                             performance, traffic, and errors
                                                            To change the location
                                                             To change the location
                                                            of the JRun logs, use
                                                             of the JRun logs, use
                                                            the Java Settings panel
                                                             the Java Settings panel




                                                     A. Bolloni




                                                                   Types of log file:
                                                                    Types of log file:
                                                                      Event
                                                                       Event
                                                                      System.out
                                                                       System.out
                                                                      System.err
                                                                       System.err


       SAP AG 2002




  JRun logs can be very useful, especially for debugging and performance and traffic measuring.
  JRun creates a separate log file for each JRun server. The settings are stored by default in
  <jrun_rootdir>/logs with the naming syntax {jrun.server.name}-<log_file_type>.log.
  The default installation of JRun creates the following log files in directory <jrun_rootdir>/logs:
    - admin-err.log
    - admin-out.log
    - admin-event.log
    - default-err.log
    - default-out.log
    - default-event.log
  For more information about monitoring and logging JRun, see the white papers:
    - JRun Advanced Configuration Guide
    - Developing Applications with JRun (Chapters 36–37)
  They are available at http://www.macromedia.com




(C) SAP AG                                      ADM130                                                 8-26
  SAP J2EE Engine Monitoring



                                                                       SAP J2EE Engine
                                                                        SAP J2EE Engine
                                                                      administration tool
                                                                       administration tool




       SAP AG 2002




  SAP J2EE Engine is delivered with a powerful administration tool, which is used for local and
  remote administration.
  In SAP J2EE Engine root directory, start the Visual Administrator by calling program go.bat. You
  need a valid user account for login (the default user account is Administrator with password ‚‘).
  SAP J2EE Engine writes different log files, depending on the level of severity. The log range is from
  INFO (simple information) to EMERGENCY (system is unusable).
  The Log Viewer tab in SAP J2EE Engine Application Server Visual Administrator displays the
  messages stored in the log files for a selected service, manager, server node, dispatcher node, or the
  whole cluster. The log messages can be displayed by type, in ascending or descending order, by date
  and time, caller, user, client IP, and cluster ID.
  The monitoring system collects data from specified server components, and reports general
  information and statistics about the cluster nodes and its components. Make sure that you are in
  Cluster view mode. To view the dispatcher or server general information, select the corresponding
  monitor node from the Components pane. The right pane of the Runtime tab displays the general
  information. There is information available for:
     - HTTP Service performance (server)
     - User sessions (server)
     - Thread performance (server and dispatcher)
     - Memory consumption (server and dispatcher)
     - Connections (dispatcher)
     - Ports (dispatcher).




(C) SAP AG                                     ADM130                                               8-27
  Central SAP J2EE Engine Monitoring

          Central Monitoring
                                                             SAP J2EE Engine Host
               System



                                 RZ20
                                                                  SAP J2EE Engine

                                                                       Jmon-API

                                               RF
                                                  C

                                                               SAPCCMSR




       SAP AG 2002




  SAP J2EE Engine can be monitored centrally by using the SAPCCMSR agent. A Jmon API enables
  SAP J2EE Engine to write to the shared memory of the SAPCCMSR agent. SAPCCMSR transfers
  the monitoring data to CMS.
  By default, SAP J2EE Engine does not report performance information to a central monitoring
  system. Under Cluster -> Server ->Services -> monitor, switch daemon.CCMS.mode to on to activate
  performance reporting.
  With SAP J2EE Engine 4.3.x, almost all information available in the stand-alone administration tool
  is passed to the central monitoring system.
  For more information about SAP J2EE Engine monitoring, see the SAP J2EE Engine Administration
  Manual.




(C) SAP AG                                    ADM130                                             8-28
   Components With SAP Basis Systems

              Components With SAP Systems
  Components With SAP Systems
                                    Components With SAP Systems

                                                                                          Frontend and Infrastructure
                             Components With SAP Systems




                                                                                          Components Without SAP Basis Systems
                                                           Components Withe SAP Systems




                                                                                                                 BasisSystems
                                                                                          Components With SAP SAP Basis Systems
                                                                                                 Components With

                                                                                          Special Monitors

                                                                                          Appendix




                                             SAP AG 2002




(C) SAP AG                                                                                                   ADM130               8-29
  Components With SAP Basis Systems

   Frontend                    Internet Middleware                     Application              Backend
                                                                       Middleware



                                                                                                  R/3 OLTP
                                                                                                   System
                           Steps to perform:
                                                                              EBP
                                                                              EBP
                              Define CMS
                              Include remote systems
                              Define properties variants
                              Setup monitors                                                         BW
                              Customize thresholds
                              Customize methods
                              Transport variants
                              Further customizing                             CRM
                                                                                                    APO


        SAP AG 2002




  Components with SAP Basis Systems can be included directly into a central monitoring environment using the
  CCMS alert monitoring architecture. This unit gives a brief overview on how to use the CCMS alert monitor
  transaction RZ20 in general.
  All components with SAP Basis Systems can be monitored on their own. In all components detailed standard
  transactions like SM59 (RFC connections), BD87 (IDoc processing) or ST03/ST03N (Workload analysis) are
  available. In such a complex server landscape it is more helpful to get a central overview first (for example,
  system availability, and transaction specific response times ...) and to use the system specific analysis
  transactions afterwards in case of troubles.
  There are some questions to answer and some steps to process on the way of setting up a central monitoring
  environment:
     - Which system (central monitoring system CMS) can host the central monitor? It should be a system with
        high availability and high basis release (4.6C is the lower limit). In a CRM 3.0 scenario, the CRM system
        itself with underlying SAP Basis 6.1 is an optimal central monitoring system.
     - Which component systems should be monitored? Setup RFC connections from CMS to these component
        systems and use agents for systems with/without SAP Basis.
     - Which component system details are of central monitoring interest? What should be their threshold
        values? Define own monitors in CMS for these details.
     - Customize threshold values and adapt analysis and auto-reaction methods for your own monitors
        (described later in this chapter). Put all customizing in containers called monitor variants and transport
        the variants to the component systems.
     - In the component systems adapt the imported variants and setup necessary monitoring environment (e.g.
        SAPConnect, special ALE monitors...).




(C) SAP AG                                          ADM130                                                   8-30
  Entering Transaction RZ20




                                                          SAP Monitor Collections:
                                                           SAP Monitor Collections:
                                                          --Immediately usable
                                                             Immediately usable
                                                          --Non-changeable
                                                             Non-changeable
                                                          --Copy-Template
                                                             Copy-Template


                                                          SAP Monitors:
                                                           SAP Monitors:
                                                          --Different predefined
                                                             Different predefined
                                                            views on the same
                                                             views on the same
                                                          --Immediately usable
                                                             Immediately usable
                                                          --Non-changeable
                                                             Non-changeable
                                                          --Copy-Template
                                                             Copy-Template




       SAP AG 2002




  The CCMS alert monitor consists of two transactions:
     - The alert monitor itself is transaction RZ20.
     - Global customizing settings for the alert monitor are set in transaction RZ21.
  SAP delivers the alert monitor with a sample of useful monitor collections and monitors. These
  monitors are stable copy templates and cannot be changed. After copying, the copied monitor can be
  adapted to customer needs.
  Enter transaction RZ20. The entrance screen shows the available monitor collections (for example
  SAP CCMS Monitor templates). Choose the plus icon. Under the collection there are several
  monitors (for example Entire System). There is only one physical CCMS alert monitor. Monitor in
  thiscontext means a special part of the CCMS alert monitor. For example, Entire System shows the
  complete SAP system whereas Database only the parts relating to database issues represents.
  You can use the SAP monitors directly. Select the monitor that shows the part of the SAP system
  that is important for your administrative work.
  The SAP monitors only display local monitoring data. If data coming from remote systems should be
  displayed, you have to set up your own monitors.
  Transaction RZ21 is for global customizing of the alert monitor. Definition of remote systems,
  analysis, and auto-reaction methods are done there.




(C) SAP AG                                   ADM130                                             8-31
  CCMS Alert Monitor


                                                                    Start of analysis method
                                                                    Start of analysis method


                                                                              All tree nodes
                                         Monitoring tree elements




                                                                           Represent one physical
                                                                           or logical object
                                                                           Summarize alerts and
                                           Monitoring objects              propagate to higher
                                                                           nodes




                                                                           Receive data and may
                                                                           create alerts
                                           Monitoring attributes           Use data for analysis
                                                                           alerts




       SAP AG 2002




  The CCMS has an object-based monitoring architecture that simplifies the task of monitoring a set of
  SAP Systems. This monitoring architecture integrates information from the entire SAP environment
  and uses this data stream to present an easy-to-manage overview of the condition of the SAP
  Systems and their environment. The information is displayed in a tree-based structure.
  All nodes of the tree-based structure are called Monitoring Tree Element (MTE).
  The information measured is combined with monitoring attributes. Monitoring attributes are the leaf
  nodes of the tree. They represent physical characteristics or messages related to a monitoring object.
  For example, the monitoring object Program Buffer has the monitoring attributes Buffer Hit Ratio or
  Swaps. All inner nodes are only for information to find the right leaf node.
  The Alert Monitor has two views:
     - Current status shows the present situation of the system.
     - Open alert shows the situation of the system in the past. This view is useful for analyzing any
       problems that occurred since the last system monitoring run.
  For each monitoring attribute, alerts are displayed if configurable threshold conditions are met. To
  view alerts, select a MTE and choose Display alerts. You see all alerts of this MTE and all MTEs
  under the selected one. For example if you work with the monitor Entire System and select the alerts
  of the top MTE (<SID>) you see the alerts processed for the whole system.
  To analyze a problem situation, you can start an analysis tool for a specific attribute. To do this,
  select a tree element and choose Start analysis method.
  The SAP system is delivered with all the tool assignments required to monitor your system.
  However, you can maintain additional tool assignments and threshold conditions.




(C) SAP AG                                      ADM130                                              8-32
  Monitoring Remote SAP Systems Centrally



     Central Monitoring System                                    SAP Instance >= 4.X
                                                 RFC

                      Dispatcher                                              Dispatcher

                  RZ20                                                                     RZ20




                                                                       Shared Memory
                Shared Memory




                                                 RFC
                                                              SAPCCM4X
       SAP AG 2002




  The CCMS alert monitor is able to monitor remote systems centrally. It is possible to set up a central
  monitoring system (CMS) which shows the situation of the system landscape in one view. If
  something goes wrong in a remote system, you can directly jump from CMS into the remote system
  for further analysis.
  From the technical point of view, the data that is displayed by RZ20 is stored in a shared memory
  segment of each SAP instance. The shared memory segment can be read out by CMS via an ABAP
  RFC call or by connecting to the SAPCCM4X agent.
  To include a remote SAP system into CMS enter transaction RZ21 in CMS and choose Technical
  infrastructure --> Create remote monitoring entry. Enter the <SID> of the remote system. If CMS is
  of release 4.6C or higher you can enter two RFC connections which must be created in transaction
  SM59:
  One for pulling the performance data from the remote system. Enter a communication user (type
  System or CPIC) with the appropriate password into the RFC connection. In CMS you can enter
  RZ20 and monitor performance data from the remote system without log on.
  One for analysis actions done in the remote system. Do not enter a user into the RFC connection,
  choose Actual user instead. If an administrator of CMS wants to analyze something in the remote
  system in case of trouble, he or she has to log on using a valid user account.
  Choose Save. The remote system can now be included in own monitors.
  If the remote system is of Release 3.1x, an agent has to be installed on each application server of the
  system. SAP note 308061 describes how to install the agent called SAPCM3X.
  Systems without SAP Basis can be included using the agent SAPCCMSR which was described
  earlier in this unit.




(C) SAP AG                                      ADM130                                               8-33
  Creating Own Monitor Sets and Monitors

                                                 1. Activate
                                                  1. Activate
                                                 maintenance function
                                                  maintenance function



                                                                      2. Select ‘create’
                                                                       2. Select ‘create’




   Note: SAP monitors
    Note: SAP monitors
   and monitor sets
    and monitor sets
   should not be changed!
    should not be changed!

       SAP AG 2002




  If you want to create your own monitors that show special characteristics of your system landscape,
  you have first to create an own monitor set. In CMS start transaction RZ20 and choose Extras >>
  Activate maintenance function. All necessary icons like Create, Change, and Copy appear.
  Select Create. You can now create your own monitor set. You can copy a SAP monitor into your
  monitor set and change the monitor.
  If you want to create your own monitor, position on your monitor set and select Create.




(C) SAP AG                                    ADM130                                              8-34
  Creating own Monitor Sets and Monitors




                                                                    Add new node



                                                                    Monitor Name



                                                                     Virtual Node


                                                                   Rule Node with
                                                                   Rule Parameters

                                                                   Existing MTEs of
                                                                   Known Systems




       SAP AG 2002




  There are two ways to create your own monitor:
    - Under Selectable MTE you can directly select any MTE of all known systems (CMS and all
       known remote systems) by marking the checkbox. All MTEs under the marked MTE are
       selected implicitly.
    - Building a Static monitor means selecting MTEs directly. This is the easiest way to set up an
       own monitor. The disadvantage is that may be the monitor must be adapted after some more
       remote systems are included into CMS.
    - You can add a rule node by choosing Create nodes. Do not select MTEs directly. Describe with
       fixed rules which MTEs you want to see. The monitor is always up to date, because the rules
       are updated while opening a monitor.
    - For example, there is a rule CCMS_DEFINE_R3_SYSTEMS with parameter <ALL>. This rule
       determines and inserts a node for all actually known SAP systems.
       With the rule CCMS_GET_MTE_BY_CLASS you can select a special group of MTEs, for
       example all nodes of the group R3DialogResponseTime. In conjunction with the rule
       CCMS_DEFINE_R3_SYSTEMS, you can easily build a monitor that shows all MTEs for dialog
       response times for all SAP systems included in CMS.
       This technique is called rule based monitor.
    You can combine static and rule based monitor techniques. You can also include virtual nodes to
    obtain a better-structured monitor.
    You should build monitors in CMS that show exactly these parts of your system landscape which
    are crucial for your productive business.




(C) SAP AG                                   ADM130                                            8-35
  Example: Central Syslog

                                                               Central syslog:
                                                                Central syslog:
                                                               --Syslog information of all
                                                                 Syslog information of all
                                                                 systems and instances
                                                                  systems and instances




       SAP AG 2002




  The diagram shows an easy rule-based monitor that shows all syslog entries of all included SAP
  systems. The rule CCMS_GET_MTE_BY_CLASS together with the parameters <ALL> for
  R3Systems and R3Syslog for MTEClass selects all syslog messages grouped by system areas (Basis
  system, database, and so on). The monitor is always up to date. Selecting the open alerts of the top
  MTE means selecting all syslog alert messages of your system landscape.




(C) SAP AG                                     ADM130                                              8-36
  Properties Variants




   Properties Variant:
   Properties Variant:

   Container for:
   Container for:
    MTE properties
     MTE properties
     Threshold settings
     Threshold settings
        for example: What is the threshold
         for example: What is the threshold
               for dialog response time?
                for dialog response time?
     Method assignment
     Method assignment
        for example: What is the auto reaction,
         for example: What is the auto reaction,
               if dialog response time
                if dialog response time
               threshold is exceeded?
                threshold is exceeded?
     Created/activated in transaction RZ21
     Created/activated in transaction RZ21

       SAP AG 2002




  The next steps required to set up central system monitoring are to customize your monitors. The
  customizing settings can be stored in a property variant of the CCMS alert monitor. Working with
  properties variants has two advantages :
  The alert monitor can be switched from one variant to another. This means all threshold values and
  all automatisms are switched with one click. For example during the day you want to get a
  notification if dialog response time is above 2s. During nighttime dialog response time is out of
  interest, the threshold may be 10s and you don‘t want to get a notification. The two monitor
  behaviors for thresholds and automatisms can be stored in two properties variants and switched
  manually or automatically if the properties variants are combined with operation modes using
  transaction RZ04.
  The customizing setting can be transported to remote systems. After import there is no need to
  customize the complete alert monitor there.
  To create a properties variant start transaction RZ21 in CMS and choose Customizing --> Variants --
  > Create. Enter a variant name and a description. Select Save.
  To activate a properties variant choose Customizing --> Variants --> Activate. All settings
  concerning this variant are activated. All customizing settings done from now on are stored in the
  variant activated.
  Important: Before starting threshold and method customizing, create and activate your variant!




(C) SAP AG                                    ADM130                                             8-37
  Customizing the Monitor: Thresholds

                                                    <SID>
                                                     <SID>



                                                                                        Thresholds can
                                                                                         Thresholds can
                              <hostX>_<SID>_<no>
                               <hostX>_<SID>_<no>
                                                                <hostY>_<SID>_<no>
                                                                 <hostY>_<SID>_<no>      be set for each
                                                                                          be set for each
                                                                                          performance
                                                                                           performance
                                Operating System                  Operating System         monitoring
                                                                                            monitoring
                                 Operating System                  Operating System
                                                                                            attribute
                                                                                             attribute
                        CPU                                                      CPU
                         CPU                                                      CPU




                                                                                                                 Properties Variant Y
                                                                                          Properties Variant X
                      Utilization
                       Utilization                                    Utilization
                                                                   Threshold values
                                                                   green <-> yellow
           Attribute Group ‘CPU_Utilization’                        yellow <-> red



                            Thresholds definable for the group


              Setting thresholds via attribute groups reduces
               Setting thresholds via attribute groups reduces
           administrative work drastically! Several hundred MTEs!
            administrative work drastically! Several hundred MTEs!
       SAP AG 2002




  After setting up monitors for your system landscape, check the threshold values for the monitoring
  attributes included in your monitors. SAP delivers standard threshold settings for the whole CCMS
  alert monitor. The standard thresholds can be too high or too low resulting in never creating alerts or
  always creating alerts. You have to commit yourself to appropriate thresholds for your technical
  environment.
  Thresholds can be set for each monitoring attribute. Some monitoring attribute appear several times
  in the alert monitor. For example each application server has the monitoring attribute
  CPU_Utilization. In case of many SAP instances, all MTEs CPU_Utilization are merged in an
  attribute group. Instead of customizing each MTE you can set threshold values for the attribute
  group. The thresholds are valid except a MTE has its own thresholds.
  You should start to adapt thresholds via attribute group customizing. This simplifies administrative
  work drastically.
  Enter your monitor and position at a monitoring attribute for which you want to adapt thresholds.
  Choose Properties. Under the folder PerformanceAttribute you can see the actual threshold settings.
  Click Change. Now you can change the threshold for green -> yellow, yellow -> red, red -> yellow
  and yellow -> green. Click Save.
  You have changed the thresholds of the attribute group of your MTE in combination with the active
  properties variant. If the threshold customizing is finished, properties variant can be transported to
  remote SAP systems.




(C) SAP AG                                             ADM130                                                                           8-38
  Methods


                                     MTE
                                      MTE




                      MTE                                  MTE
                       MTE                                  MTE




               MTE
                MTE




                              MTE
                              MTE
      MTE
       MTE
                      Data Collection Method
                       Data Collection Method             What collects the data?
      MTE              Auto-reaction Method
                        Auto-reaction Method              What is done in case of an alert?
       MTE
                         Analysis Method
                          Analysis Method                 How to analyze an alert?




       SAP AG 2002




  Tree tools (or methods) with different tasks can be attached at each MTE.
  The monitoring transaction RZ20 is a data consumer, which means it only displays values measured
  by data suppliers in a structured manner. RZ20 does not measure itself. The MTE entry Data
  Collection Method determines which data supplier is responsible for delivering data.
  If a threshold condition is met for an MTE, you can define an automatic reaction. The MTE entry
  Auto-reaction Method determines what should be done automatically in case of a YELLOW or RED
  alert, regardless if someone is monitoring the RZ20 display or not.
  The display of Transaction RZ20 can also be used for dispatching. If you notice an alert on the RZ20
  display, you do not have to know the transaction code or the report name that helps to analyze the
  situation. The MTE entry Analysis Method determines which SAP R/3 functions should be executed
  to analyze the situation.
  The MTEs in the CCMS monitor are pre-defined with standard methods. However, you can define
  your own methods or change the assignment in the MTEs to suit your needs.




(C) SAP AG                                    ADM130                                              8-39
  Example: Analysis Method




                                                    Mark the MTE, start the
                                                    Mark the MTE, start the
                                                      analsysis method
                                                       analsysis method




                  Analysis method is started
                  Analysis method is started
                     (in this case ST06)
                      (in this case ST06)
       SAP AG 2002




  In case of alerts, transaction RZ20 guides the administrator to SAP R/3 functionality which helps to
  investigate the problem. This SAP R/3 functionality is called Analysis method, which can be defined
  for each MTE.
  SAP delivers standard monitoring templates set up with lots of predefined Analysis methods. You
  can use these methods directly, or change the method assignment or define new Analysis methods.
  Analysis methods run manually, started by the administrator. Therefore, dialog transactions can also
  be used. An Analysis method can be:
  A dialog transaction
     - An ABAP report
     - A function module
     - An URL.
  The analysis method helps you analyzing an alert situation. Position on a MTE and click Start
  analysis method. You are dispatched into the analysis method. In the example of the slide an alert
  occurs at page-in rates. The analysis method dispatches you in the operating system monitor
  (transaction ST06).
  The methods assigned to an MTE are shown if you position on the MTE and click Properties. Select
  the folder Methods.




(C) SAP AG                                    ADM130                                              8-40
  Definition of Analysis Methods: Example

   RZ21: Method definitions
   RZ21: Method definitions
         Display overview
         Display overview




       SAP AG 2002




  Methods can be defined and maintained using Transaction RZ21. To display a list of all methods
  defined, select Method definition, and choose Display Overview. To define a new method, choose
  Create. To maintain a defined method, choose Edit data.
  This example shows the definition of an Analysis method for controlling batch jobs. It is the dialog
  transaction SM37. The name of the Analysis method is ZSM37.
  Transaction SM37 is a dialog transaction. Therefore, under Control, Manually executable only has to
  be selected.
  A method has to be released before is can be used in the alert monitor RZ20. In the example above,
  the method is released for Analysis method.
  A method can be assigned directly to an MTE or to a group of MTEs (MTE class).




(C) SAP AG                                    ADM130                                              8-41
  Example: Automatic E-Mail Notification




       SAP AG 2002




  Program SAPMSSY8 periodically checks if the data provided by the data suppliers fulfils the
  threshold conditions for YELLOW or RED alerts set for the MTEs. If this appears, SAPMSSY8 can
  initiate an action defined as Auto-reaction method for these MTEs.
  Auto-reaction methods run automatically, without user interaction. Therefore, no dialog transactions
  can be used. An Auto-reaction method can be:
     - An ABAP report
     - A function module that has the interface shown in the sample function module
        SALT_TOOL_REFERENCE_MODULE. For function modules, static parameter values can be
        passed.
  Methods can be defined and maintained using Transaction RZ21. To display a list of all methods
  defined, mark Method definition, and choose Display Overview. To define a new method, choose
  Create. To maintain a defined method, choose Edit data.
  You can set up an auto-reaction method that sends an e-mail in the case of an alert. The name of the
  copy template auto-reaction method is CCMS_On Alert _Email, and it stands for the execution of the
  function module SALO_EMAIL_IN_CASE_OF_ALERT. The content of the e-mail is exactly the
  alert content shown in Transaction RZ20. The setup of this method is described in SAP note 176492.




(C) SAP AG                                    ADM130                                              8-42
  Central Auto Reactions and Push Technology



                                                            SAP Instance >= 4.X

                                                                       Dispatcher



             SAP Web AS 6.x
                                               h         SAPCCM4X
                                           pus

                      Dispatcher            R FC
                                                            Non-SAP Basis Host
                                              pu
                                                sh
                                           RF                      Component
                                              C
                                                        SAPCCMSR



       SAP AG 2002




  In earlier releases and in an SAP system auto-reactions are always processed in the same
  components as the triggered alert occurs.
  If the central monitoring system is located on a SAP Web Application Server 6.10 (your
  CRM 3.0 system) or higher, the agents can transfer the local alert information to the central
  monitoring system and raise an event. The auto reaction is started by an event-triggered
  batch dispatcher directly. This means, for example, that mail notifications or scripts can be
  started immediately and centrally from the CEN if errors occur. This makes it much easier
  for you to configure auto-reactions.
  SAP Note 429265 describes how to set up central auto reactions.




(C) SAP AG                                  ADM130                                          8-43
  Assigning Methods: Principles

                                                       <SID>
                                                        <SID>




  Methods can                   <hostX>_<SID>_<no>              <hostY>_<SID>_<no>
                                                                                      Methods definable
                                 <hostX>_<SID>_<no>              <hostY>_<SID>_<no>
                                                                                      Methods definable
  be passed to
  lower levels           Operating System                         Operating System
                                                                                        for each node
                                                                                         for each node
                          Operating System                         Operating System




                      CPU                                                         CPU
                       CPU                                                         CPU




                                                                                                                       Properties Variant Y
                                                                                                Properties Variant X
                 Utilization
                  Utilization                                                Utilization
                                                                               Utilization
                                                                         Collecting method
                                                                          Collecting method
                                                                        Auto-reaction method
                                                                         Auto-reaction method
                      MTE Class ‘CPU_Utilization’                         Analysis method
                                                                           Analysis method


                 Methods definable for the group


                             Assigning methods via MTE classes reduces
                             Assigning methods via MTE classes reduces
                                   administrative work drastically!
                                    administrative work drastically!
       SAP AG 2002




  Methods can be assigned to MTEs in three ways:
   - A method can be assigned directly to an MTE. To do this, go into the alert monitor and mark
      the desired MTE. Choose Properties and select the folder Methods. Select Method assignment.
      Three folders for data collection, auto-reaction, and analysis are displayed. In the area Method
      allocation, a method can be directly assigned to an MTE under Method name.
   - A method can be assigned by choosing Use method from higher-level node (MTE). This means
      that methods can be passed from higher to lower level MTEs. For example, if all MTEs in a
      subtree should use the same analysis method, you can assign this method to the highest MTE of
      the subtree and pass the method down on all lower levels.
   - A method can be assigned by choosing Use MTE class method assignment, which is the normal
      setting. MTEs with the same physical or logical content are grouped together in MTE classes.
      For example, all MTEs CPU_Utilization are assigned to the MTE class CPU_Utilization
      independent of the SAP application server. Instead of assigning all of these MTEs a method
      individually, the assignment can be done once to the MTE class and is active for all MTEs
      within the class where no direct assignment is set. This simplifies the Customizing of the
      monitor in the same manner like attribute groups concerning thresholds.
   - The assignment of methods to MTE classes in on a per-variant basis. This means that the
      assignment can change if you switch to another properties variant.




(C) SAP AG                                            ADM130                                                                                  8-44
   Special Monitors

            Special Monitors




                                                  Frontend and Infrastructure
                               Special Monitors
  Special Monitors




                                                  Components Without SAP Basis Systems
                    Special Monitors




                                                  Components With SAP Basis Systems
                      Special Monitors




                                                  Special MonitorsMonitors
                                                            Special
                                                  Appendix




                                SAP AG 2002




(C) SAP AG                                                          ADM130               8-45
  Availability Check


                                                           RFC connection
                                                           RFC connection

       Central Monitoring System

                                                         Component System


                                                               Dispatcher




                  CCMSPING                                   Message Server
                                                             Message Server




       SAP AG 2002




  Within the scope of central monitoring environment, the CCMS alert monitor can display the
  availability of other SAP Systems.
  The availability check is done by the executable CCMSPING, which pings the message servers of
  the remote systems and transfers the message server information to CMS. CCMSPING can run on
  any server. CMS must have at least basis release 4.6C.
  The configuration, which is described in detail in SAP Note 381156, is quite simple, because there
  is no need to configure RFC connections from CMS to the remote systems.
  CCMSPING can check as many SAP systems as specified.




(C) SAP AG                                    ADM130                                              8-46
  Result: Availability Monitor



                                                                Per system an
                                                                 Per system an
                                                               availability node
                                                                availability node




                                                               Per instance an
                                                                Per instance an
                                                               availability node
                                                                availability node
                                                                  if desired
                                                                   if desired



       SAP AG 2002




  The system availability monitoring is not automatically activated but must be explicitly configured
  for systems whose availability should be displayed centrally. SAP note 381156 describes how to
  activate the availability check.
  The availability monitor can be found in transaction RZ20. After configuration and activation,
  choose the monitor Availability: Selected Systems in the SAP monitor set SAP CCMS Monitor
  Templates.
  After activation each remote system has one global availability MTE and, if desired, MTEs for each
  instance.




(C) SAP AG                                    ADM130                                              8-47
  Transaction-Specific Monitoring

     Customizing table
     Customizing table                Transaction codes of core
                                       Transaction codes of core
       ALTRAMONI
        ALTRAMONI                         business process
                                           business process




                                                           Transaction-Specific
                                                            Transaction-Specific
                                                              Dialog Monitor
                                                               Dialog Monitor




       SAP AG 2002




  Since SAP Release 4.6B it is possible to create a monitor which shows transaction specific response
  times. You are able to monitor BBP transactions per client or per system. The setup of the
  transaction specific monitor is described in SAP note 308048.
  For each transaction which should be monitored you have to create an entry in table ALTRAMONI.
  Enter the transaction that you want to monitor with a meaningful monitoring object name of your
  choice in table ALTRAMONI by using SE16. SAP recommends that you enter the same name for
  the MTE class and the monitoring object. This makes it easy for you to select by client or transaction
  in the monitor definition. Specify client or * for all clients. Enter the System ID as <CURRENT>.
  Save the entry.
  Call transaction RZ20. You can find the Transaction-Specific Dialog Monitor in the SAP monitor set
  SAP CCMS Monitors for Optional Components (in case of an SAP Release 4.6b, the monitor have to
  be created manually). After five minutes the first MTEs will appear.
  You should activate the transaction specific monitor in the remote systems. In CMS you can build a
  central monitor by using the rule GET_MTE_BY_CLASS with MTE class ContextR3DialogFocus.




(C) SAP AG                                     ADM130                                              8-48
  CCMS ALE Monitor




       SAP AG 2002




  In SAP monitoring set SAP CCMS Monitors for Optional Components you can find an ALE monitor
  template ALE/EDI. This monitor shows outbound and inbound Idocs, change pointers, and the
  transactional RFC queue.
  The ALE monitor shows ALE information about all Idocs and as an example for MATMAS Idocs.
  For the ALE monitor the data collection runs in batch mode. Prerequisite is that the CCMS alert
  monitor batch tool dispatcher is activated otherwise all MTEs of the ALE monitor are white. You
  can activate batch tool dispatching starting transaction RZ21. Choose Technical infrastructure ->
  Method execution -> Activate background dispatching.
  For detailed Idoc analysis, use transaction BD87.




(C) SAP AG                                   ADM130                                            8-49
  Creating Own ALE Monitoring Objects (1)

                                                                Start transaction
                                                                 Start transaction
                                                              BDMO -> Create/activate
                                                              BDMO -> Create/activate
                                                                monitoring object
                                                                 monitoring object




                               Select ‘New entries’;
                               Select ‘New entries’;
                                Activate and save
                                 Activate and save
                                 your new entry
                                  your new entry
       SAP AG 2002




  If you want to monitor individual Idoc types, you can create your own ALE monitoring objects.
  Enter transaction BDMO and select at Create/active monitoring objects. Choose New entries. You
  can enter the monitoring object name. Mark Active and save your settings. Now you have to define
  which Idoc type stand behind your monitoring object.




(C) SAP AG                                   ADM130                                             8-50
  Creating Own ALE Monitoring Objects (2)




                                                                      Select IDoc type for
                                                                       Select IDoc type for
                                                                      inbound/outbound.
                                                                       inbound/outbound.
                                                                       You can select the
                                                                        You can select the
                                                                         partner system
                                                                          partner system

   Activate your
   Activate your
     settings
      settings




       SAP AG 2002




  Go back to the entrance screen of BDMO. Select your new monitoring object and click Change
  monitoring object. Select the IDoc type you want to monitor for outbound/inbound direction. You
  can also specify the wait time for status changes and the partner system. Save your settings.
  On the entrance screen of BDMO, choose Monitoring object -> Start all. A new monitoring object is
  created which can be used in rule based monitors.




(C) SAP AG                                   ADM130                                            8-51
  Creating Own ALE Monitors




       SAP AG 2002




  It is easy to set up a rule-based monitor for your ALE monitoring object. Select the rule
  CCMS_GET_MTE_BY_CLASS with parameter ALEfGr:<object name> for the MTEClass. As a
  result, only information concerning your Idoc selection is displayed.
  You should create ALE monitors in all systems that are involved in ALE. Afterwards, you can create
  a central ALE monitor in CMS showing all ALE information in one screen using the rule
  CCMS_GET_MTE_BY_CLASS. For the parameters R3System and MTEClass, choose a proper
  combination for each remote system.




(C) SAP AG                                   ADM130                                             8-52
  TRFC and QRFC Monitoring

                                                                    Transaction RZ20
                                                                     Transaction RZ20
                                                                 Monitor Communications
                                                                 Monitor Communications

                                                                   Database Tables
                                                                    Database Tables
                                                               ARFCSSTATE, ARFCRSTATE
                                                               ARFCSSTATE, ARFCRSTATE


                                                               Outbound queue monitoring
                                                                Outbound queue monitoring
                                                                    Queues per client
                                                                    Queues per client
                                                               Numer of queue entries (opt.)
                                                               Numer of queue entries (opt.)
                                                                    Queue age (opt.)
                                                                     Queue age (opt.)




                                                                Inbound queue monitoring
                                                                 Inbound queue monitoring
                                                                   Scheduler monitoring
                                                                   Scheduler monitoring
       SAP AG 2002




  Communication between the CRM server and the system landscape is mainly done by tRFC and
  qRFC. It is crucial to monitor the communication status regularly.
  In transaction RZ20, choose the monitor Communications, which is located in the monitor set SAP
  CCMS Monitor templates. This monitor shows basic tRFC information. Importing a basis support
  package can expand the information. The support package is available since SAP release 4.5b.
  Further details are described in SAP Note 441269.
  After installing the support package in an CRM system, the following information is shown:
    Status of the database table ARFCSSTATE, which stores information of outgoing tRFC calls.
    Status of the database table ARFCRSTATE, which stores information of incoming tRFC and
    qRFC calls.
    Status of outbound qRFC queues, which are grouped by queue name and client.
    Status of inbound qRFC queues, which are grouped by queue name and client.
    Status of the outbound and inbound queue scheduler.
  The queue information is refreshed every 15 minutes. Instead of reporting the same error message
  several times, a particular error message is reported only once per queue, until an administrator
  completes the message.
  The data shown in Communications can be customized. You can choose:
    Which queues are grouped together.
    Which queues a monitored.
    If the number of queue entries and the queue age (age of the oldest entry of the queue) is
    displayed.




(C) SAP AG                                    ADM130                                             8-53
  Configuring qRFC Monitoring




       SAP AG 2002




  QRFC monitoring is delivered with SAP standard customizing, which is automatically active after
  installation of the appropriate support package. Nevertheless, you can copy the SAP default settings
  and adapt them to your needs.
  To change qRFC monitoring customizing, start transaction RZ21 and choose Technical
  Infrastructure -> Configure qRFC Monitoring.
  The SAP standard view cluster maintenance shows on the first level the owner of the qRFC
  customizing package. You can copy the SAP customizing, change the copied version and set the
  Active flag to your customizing.
  The second level shows the queue groups of the package. A queue group groups qRFC queues of
  your choice. Please enter a meaningful name to the queue group, because the queue group name is
  displayed in the CCMS alert monitor under Inbound or Outbound Queues.
  The default settings of a queue group can be changed. For instance, analysis or autoreaction methods
  can be assigned directly to the corresponding MTEs of the queue group. Furthermore, assigning an
  exit function module can expand the monitoring data. SAP delivers the two function modules
  SALK_CRM_QRFC_QUEUE_ENTRIES (number of queue entries) and
  SALK_CRM_QUEUE_AGE (age of the oldest entry of the queue). These function modules could
  have high resource consumption, if the underlying database tables are extremely large.
  The queues assigned to a certain queue group are displayed on the third level. The queues can be
  named by an asterisk at the end of the queue name. The monitoring of queues could also be switched
  off.
  The level of alerts propagated in the CCMS monitoring architecture can be changed on the fourth
  level.




(C) SAP AG                                    ADM130                                              8-54
  Special EBP Monitors (1)




                                 Special EBP monitors
                                  Special EBP monitors
                                   for Web access or
                                    for Web access or
                                       via SAPGUI
                                        via SAPGUI
       SAP AG 2002




  SAP delivers EBP with a special monitor set SAP B2B Procurement – Monitors. The set contains
  monitors for varios parts of the EBP process. You can use the monitors via SAPGUI using
  transaction RZ20 or via Web using the bbpstart service; both show the exact same information. In
  case of an error, check it with the Web based tool.
  The monitors show only messages in case of an alert.
  The monitoring information is client dependent. Make sure, that you are logged in your EBP client.
  If you like to see EBP information cross client, you have to adapt the monitor definition accordingly.




(C) SAP AG                                     ADM130                                               8-55
  Special EBP Monitors (2)




       SAP AG 2002




  The Approval monitor shows:
    - Starting conditions: Error in start conditions
    - Approver assignment: Error assigning possible processors
    - Other errors: Approval processes with miscellaneous errors.
  The Component Planning monitor shows:
    - Backend application errors: Error in backend system while transferring components.
    - Spooler communication errors: Communication error while creating orders.




(C) SAP AG                                   ADM130                                        8-56
  Special EBP Monitors (3)




       SAP AG 2002




  The Confirmation monitor shows:
    - Backend goods receipt errors: Confirmations with goods receipts containing errors.
    - Backend service entry errors: Services that could not be updated in the backend system.
    - Local errors: Confirmations that led to errors in the SAP B2B Procurement system.
    - IDoc communication errors: Confirmations with IDocs containing errors.
    - Spooler communication errors: Confirmations with communication errors in spooler.
  The Invoice monitor shows:
    - Backend invoice errors: Error in the backend system while creating invoices.
    - Backend commitment errors: Error in the backend system while determining commitment for
       an invoice.
    - Local errors: Error while creating invoices in the SAP B2B Procurement system.
    - IDoc communication errors: Communication error (IDoc) while creating invoices.




(C) SAP AG                                 ADM130                                          8-57
  Special EBP Monitors (4)




       SAP AG 2002




  The Procurement Card monitor shows:
    - Backend application errors: Error while updating data in the backend system
    - IDoc communication errors: Communication error while updating data in the backend system
  The Purchase Order monitor shows:
    - Backend application errors: Application error while updating purchase orders in the backend
      system.
    - IDoc communication errors: Communication error while updating purchase order in the
      backend system.
    - Local errors: Error while creating a purchase order in the SAP B2B Procurement system.
    - Output Errors: Error while issuing purchase order
    - Planing System errors: Error while creating a purchase order from the planning system
    - Transfer communication errors: Communication error transferring purchase order to the
      planning system.




(C) SAP AG                                   ADM130                                            8-58
  Special EBP Monitors (5)




       SAP AG 2002




  The Bid Invitation monitor shows:
    - Backend application errors: Application error in PLM system
    - Communication errors: Communication error with PLM system
    - Local errors: Local error in bid invitation
    - Output errors: Error issuing bid invitation
    - Planing System errors: Error calling by the planning system




(C) SAP AG                                 ADM130                   8-59
  Special EBP Monitors (6)




       SAP AG 2002




  The Shopping Basket monitor shows:
    - Backend application errors: Shopping baskets that could not be created in the backend system.
    - Spooler communication errors: Shopping baskets that led to problems in the SAP B2B
      Procurement system.
    - Local errors: Shopping baskets that led to problems in the SAP B2B Procurement system.
    - Not transferred to backend: Shopping baskets that were not transferred to the backend.
  SAP note 395699 is useful for the Shopping Basket .
  The User Administration monitor shows:
    - User create errors: Error while creating users.
    - User change errors: Error while changing passwords.




(C) SAP AG                                    ADM130                                            8-60
  Special CRM Monitor



                                                                      qRFC Information
                                                                       qRFC Information




                                                                        Replication &
                                                                        Replication &
                                                                        Realignment
                                                                         Realignment




       SAP AG 2002




  The CRM Middleware Alert Monitoring was implemented based on the CCMS Alert Monitoring
  infrastructure. It can be found under the SAP CRM Monitor Templates monitor sets with the name
  CRM. The monitor is delivered by Support Packages. For further information, refer to SAP note
  437187.
  The monitor shows qRFC information (if the corresponding support package has been installed) as
  well as information related to replication & realignment (SAP CRM Mobile Sales).




(C) SAP AG                                   ADM130                                            8-61
  Business Process Monitoring at a Glance



              s
         Alert
        Logs

                                                                 ?
                                                CRM
                                             Middleware
                                                                                    SAP APO

                                                                                  SAP BW
                                                 RZ20




                                                JRun             Business
                              ITS             Requisite          Connector              R/3
      Web Server             AGate            Catalog            SAP J2EE              OLTP
      ITS WGate
                                               Server             Engine               Server




       SAP AG 2002




  The aim of a Monitoring Architecture should be:
     - To cover all components needed by core business processes.
     - To recognize bottlenecks and potential sources of error early.
     - To see as much information as necessary but as little as possible.
     - To have at first glance a maximally logical presentation of the key information.
     - To have access to detailed information and analysis tools on demand.
  For SAP R/3 System based components and interfaces, this is covered by a suitable configuration of
  the R/3 Alert Monitor (transaction RZ20).
  For other components, you must use individual methods like agent SAPCCMSR, as described earlier
  for components without an SAP Basis System.
  It is important to filter the information. For example, the log file adapter of CCMS agents can search
  through log files for critical error messages.




(C) SAP AG                                     ADM130                                               8-62
  Appendix




                                     Frontend and Infrastructure
 Appendix Appendix
                     Appendix




                                     Components Without SAP Basis Systems


                                     Components With SAP Basis Systems
             Appendix
                         Appendix




                                     Special Monitors

                                     Appendix
                                         Appendix




                      SAP AG 2002




(C) SAP AG                                              ADM130              8-63
  Example: The EBP Process




                                                                             1
                                                                             1
                                                                                   Start EBP
                                                                                    Start EBP




                                                                              2
                                                                              2
        Send to           5                                                       Fill shopping
         Send to          5
        Marketplace                                                               basket from
         Marketplace
                                                                                      catalog
                                                                      3
                                                                      3
                                               4
                                               4
                              Send to R/3
                               Send to R/3                     Save
                                                                Save
                              Backend
                               Backend                      shopping
                                                             shopping
                              System
                               System                         basket
                                                               basket

       SAP AG 2002




  The EBP process shown in the graphic triggers the following chain of events:
    - Steps 1-3: Requisition and approval. An employee enters a purchase requisition. If the
      requisition is below a given threshold, the requisition is approved automatically. Otherwise, the
      manager must approve it manually. For a very expensive purchase, the next level of
      management may also need to approve it.
    - Step 4: Purchase order. After approval, the requisition is converted into a purchase order. EBP
      adds and verifies the necessary supplier data.
    - Step 5: Transmission to supplier and sales order confirmation. Depending on the supplier, the
      purchase order is transmitted to the supplier using XML, EDI, email, or fax. The employee can
      track the order status in EBP. If a link is given to the logistics service provider system, the order
      can also be tracked. Optionally, the supplier confirms the sales order.




(C) SAP AG                                      ADM130                                                 8-64
  1. Start EBP

                                                                                         1
                                                                                         1
                                                                           Start EBP




    Component         Monitoring tool Items                Useful parameters
                                                           (method, MTE class,...)
    Web server        External Web   Check availability,
                      monitor        Response time,
                                     Test logon
    ITS               RZ20           Availability,         ITS*
                                     Sessions,
                                     Workthreads,
                                     Operating system      See SAP Note 418285
                      ITS Admin      Log files
                                                           SAPCCMSR
                                     ITS monitor
    EBP server        RZ20           Availability,         CCMSPing, Availability_MA_Class
                                     Core transactions     Customizing table ALTRAMONI
                                     tRFC                  CCMS_tRFC_Context
                      ST03N          Workload




       SAP AG 2002




(C) SAP AG                             ADM130                                                8-65
  2. Fill Shopping Basket from Catalog

                                                                       Fill shopping   2
                                                                                       2
                                                                       basket from
                                                                           catalog




    Component         Monitoring tool Items                Useful parameters
                                                           (method, MTE class,...)
    Web server        External Web   Check availability,
                      monitor        Response time,
                                     Test logon
    Example:          External Web   Check Servlet
    Requisite         monitor        URL                   SAPCCMSR
    Catalog server    By hand        JRUN log files
                                     Oracle alert log
                                     Operating system




       SAP AG 2002




(C) SAP AG                             ADM130                                              8-66
  3. Save Shopping Basket

                                                                               4
                                                                             Save        3
                                                                                         3
                                                                              Save
                                                                          shopping
                                                                           shopping
                                                                            basket
                                                                             basket

    Component         Monitoring tool Items                Useful parameters
                                                           (method, MTE class,...)
    Web server        External Web   Check availability,
                      monitor        Response time,
                                     Test logon
    ITS               RZ20           Availability,         ITS*
                                     Sessions,
                                     Workthreads,
                                     Operating system      See SAP Note 418285
                      ITS Admin      Log files
                                                           SAPCCMSR
                                     Performance
    EBP server        RZ20           Availability,         CCMSPing, Availability_MA_Class
                                     Security,             SECURITY*
                                     Response time,        See SAP Note 441269
                                     q/tRFC                CCMS_tRFC_Context
                                     Core                  Customizing table ALTRAMONI
                                     Transactions
                      ST03N          Workload

       SAP AG 2002




(C) SAP AG                             ADM130                                                8-67
  4. Send to R/3 Backend System

                                                                          Send to R/3        4
                                                                                             4
                                                                           Send to R/3
                                                                           Backend
                                                                            Backend
                                                                            System
                                                                             System


    Component         Monitoring tool Items                Useful parameters
                                                           (method, MTE class,...)
    Web server        External Web   Check availability,
                      monitor        Response time,
                                     Test logon
    ITS               RZ20           Availability,         ITS*
                                     Sessions,
                                     Workthreads,
                                     Operating system      See SAP Note 418285
                      ITS Admin      Log files
                                                           SAPCCMSR
                                     Performance
    EBP server        RZ20           Availability,         CCMSPing, Availability_MA_Class
    R/3 OLTP server                  Security,             SECURITY*
                                     Response time,        See SAP Note 441269
                                     tRFC,                 CCMS_tRFC*
                                     Core transactions     CCMS_qRFC*
                      ST03N          Workload              Customizing table ALTRAMONI
                                     RFC
       SAP AG 2002




(C) SAP AG                              ADM130                                                   8-68
  5. Send to Marketplace

                                                                                        5
                                                                                        5
                                                                       Send to
                                                                        Send to
                                                                      Marketplace
                                                                      Marketplace



    Component         Monitoring tool Items           Useful parameters
                                                      (method, MTE class,...)
    BBP Server        RZ20           Availability,    CCMSPing, Availability_MA_Class
    R/3 OLTP Server                  Security,        SECURITY*
                                     Response time,
                                     tRFC,            CCMS_tRFC_Context
                                     Core             Customizing table ALTRAMONI
                                     Transactions
                      ST03N          Workload
                                     RFC
    Business                         Logfiles         Alias /Connectors in Service
    Connector                                         Marketplace
                                                      SAPCCMSR




       SAP AG 2002




(C) SAP AG                              ADM130                                              8-69
  Further Documentation



                      For additional information about mySAP
                      Technology system monitoring, check:
                        SAP Notes category:
                             XX-SER-TCC, BC-CCM-MON
                        URLs:
                            service.sap.com/crm
                            service.sap.com/ebp
                            service.sap.com/technology
                            service.sap.com/systemmanagement




       SAP AG 2002




(C) SAP AG                             ADM130                  8-70
  Unit Summary



                      You are now able to:

                         Understand the tools for monitoring the
                         different mySAP Technology components
                         Integrate the different monitoring tools
                         Build a monitoring infrastructure




       SAP AG 2002




(C) SAP AG                               ADM130                     8-71
                                                                             Exercises

                  Unit: System Monitoring
                  Topic: Monitoring using the Alert Monitor (RZ20)


                  At the conclusion of this exercise, you will be able to:
                  • Monitor the different Components of your implemented SAP solution




                  You are an administrator responsible for the system configuration.




1-1   Creating a monitor set.
      1-1-1 Log on to your EBP system (client 800). Start transaction RZ20. Create a
            monitor set ADM130-## (##: group number).
1-2   Optional: Availability monitor
      1-2-1 Check the configuration of the availability monitor.
             Start transaction SE16. Select the table entries of table CSMNSDIC where
             AVCHECK = ‘X’. Check if these entries are also in table CSMSYS.Start
             transaction SM59. Search RFC connection CCMS_SYSTEM_PING_DEST
             (type TCP/IP) and perform a connection test.
      1-2-2 Enter transaction RZ20. Start the SAP monitor Availability: Selected Systems of
             monitor set SAP CCMS Monitor Templates. Which systems are checked? What
             are the thresholds for triggering a yellow/red alert for the MTE Instance
             Availability?
             Go back to the entrance screen of transaction RZ20. Copy the availability
             monitor to your monitor set.
1-3   Optional: ITS Monitoring
             Activate maintenance function in transaction RZ20 by choosing Extras ->
             Activate maintenance function.

             Position to your monitor and click Change.

             Position at the top node of your monitor (e.g. the name of the monitor) and click
             Create nodes.

             Choose Virtual nodes and click Continue.

             Enter ITS and click Continue.

             Position at the ITS node of your monitor and click Create nodes.
(C) SAP AG                                ADM130                                          8-72
             Choose Rule node and click Continue.

             Select the rule CCMS_GET_MTE_BY_CLASS and click Continue.

             Enter <CURRENT> for the parameter R3System and ITSavailH for the
             parameter MTEClass.

             Click Continue.

             Position at the ITS node of your monitor and click Create nodes.

             Choose Rule node and click Continue.

             Select the rule CCMS_GET_MTE_BY_CLASS and click Continue.

             Enter <CURRENT> for the parameter R3System and ITSurlH for the parameter
             MTEClass.

             Click Continue.

             Click Generate monitor.


1-4   Optional: SAPCCMSR Agent
      1-4-1 Start transaction RZ21. Select Technical Infrastructure -> Overview of
             Segments. Is there an agent registered at your system? Whats the name of the
             RFC connection used for data collection? Whats the name of the host monitored
             by SAPCCMSR?
             Search for this RFC connection in transaction SM59 (hint: the type of the RFC
             connection is TCP/IP). Perform a connection test.
             Open the monitor All Monitoring Contexts in the SAP monitor set SAP CCMS
             Technical Expert Monitors. Are there MTEs showing information from the host
             monitored by SAPCCMSR?
      1-4-2 Create a new rule based monitor in your monitor set showing the SAPCCMSR
            information Files_of...
1-5   ALE Monitoring
      1-5-1 Log on to your SAP backend system. Start transaction BDMO. Check the
            situation of ALE monitoring: Is there an active monitoring object that displays
            information about the IDoc MBGMCR? What’s the name of the monitoring
            object?




(C) SAP AG                               ADM130                                          8-73
      1-5-2 Log on to your Internet Sales/EBP system. The ALE information should be
            monitored centrally there.
             Start transaction RZ20. Create a new rule based monitor in your monitor set
             which shows the ALE information of the MBGMCR IDocs of your EBP
             system.
             Hint. Use the rule CCMS_GET_MTE_BY_CLASS. The MTE class name is
             ALEPfGr:<name of the monitoring object determined in the previuos
             exercise>.


1-6   SLA - transaction specific monitoring
      1-6-1 Log on to your SAP backend system. Start transaction SE16. Select table
             ALTRAMONI and check if there is an entry for transaction BBPPU99 (create
             shopping basket).
             Start the BBP transaction Create shopping basket using Web access:
             http://<server>:<port>/scripts/wgate/bbpstart/!
            In parallel (also on your SAP backend System) start the SAP monitor
            Transaction-Specific Dialog Monitor of monitor set SAP CCMS Monitors for
            Optional Components. What is the current dialog response time for this
            transaction? What is the MTE class name of the top node of the monitor (hint:
            MTE classes are NOT assigned to virtual nodes)?
      1-6-2 Logon to your Internet Sales/EBP system. The transaction specific information
            should be monitored centrally there.
             Start transaction RZ20. Create a new rule based monitor in your monitor set
             which shows the transaction specific information of your EBP system.
             Hint. Use the rule CCMS_GET_MTE_BY_CLASS. The name of the parameter
             MTE class is the MTE class determined in the last exercise. Ignore the error
             messages that this class does not exist on your local system.


1-7   SAP B2B Procurement Monitors for the Enterprise Buyer
      1-7-1 Your EBP system has special designed monitor templates for the EBP process.
            This EBP specific information should be monitored centrally in your Internet
            Sales/EBP system..
             Start transaction RZ21. Choose Technical Infrastructure -> Overview of
             Segments. Is your EBP system already registered?
             Start transaction RZ20. Create a new static monitor in your monitor set, which
             shows the complete BBP information of your EBP system.
            Start the new monitor. Switch between the Current System Status and the Open
            alerts view. Are there any alerts in the tree? Position at a red MTE and click
            Display Alerts.
      1-7-2 Log on to the EBP system using Internet Explorer.
             Under Application monitors select an EBP monitor.
             The monitor information in SAPGUI and the Internet Explorer are exactly the
             same.

(C) SAP AG                                ADM130                                           8-74
                                                                             Solutions

                  Unit: System Monitoring
                  Topic: Monitoring using the Alert Monitor (RZ20)


                  At the conclusion of this exercise, you will be able to:
                  Monitor the different Components of your implemented SAP solution




                  You are an administrator responsible for the system configuration.




1-1   Creating a monitor set.
      1-1-1 Log on to your EBP/CRM system (client 800). Start transaction RZ20. Create a
            monitor set ADM130-## (##: group number).
            To create your own monitor set, run transaction RZ20. To activate the
            maintenance function, choose Extras -> Activate maintenance function.
             Choose Create.
             Select New monitor set.
             Choose Continue.
             Specify the name of the monitor set: ADM130-##
             Choose Continue.
1-2   Optional: Availability monitor
      1-2-1 Check the configuration of the availability monitor.
             Start transaction SE16. Select the table entries of table CSMNSDIC where
             AVCHECK = ‘X’. Check if these entries are also in table CSMSYS.Start
             transaction SM59. Search RFC connection CCMS_SYSTEM_PING_DEST
             (type TCP/IP) and perform a connection test.
             Perform as described.
            Transaction SM59 has a search button. Be careful: RFC connection names
            are case sensitive. Click Connection test in the definition screen of RFC
            connection CCMS_SYSTEM_PING_DEST.
      1-2-2 Enter transaction RZ20. Start the SAP monitor Availability: Selected Systems of
            monitor set SAP CCMS Monitor Templates. Which systems are checked? What
            are the thresholds for triggering a yellow/red alert for the MTE Instance
            Availability?
             Go back to the entrance screen of transaction RZ20. Copy the availability
             monitor to your monitor set.

(C) SAP AG                                ADM130                                         8-75
             Perform as described.
             Open the monitor Availability: Selected Systems by double click.
             To look at threshold values, position at a leaf node Availability. Click
             Properties. For example, the threshold for green -> yellow is 75% (average
             over the last 15 minutes). One can adapt the thresholds.
             Go back to the entrance screen of transaction RZ20. If the maintenance
             function is switched on, you can use the Copy icon to copy the monitor to
             your monitor set.
1-3   Optional: ITS Monitoring
             Activate maintenance function in transaction RZ20 by choosing Extras >>
             Activate maintenance function.

             Position to your monitor and click Change.

             Position at the top node of your monitor (e.g. the name of the monitor) and click
             Create nodes.

             Choose Virtual nodes and click Continue.

             Enter ITS and click Continue.

             Position at the ITS node of your monitor and click Create nodes.

             Choose Rule node and click Continue.

             Select the rule CCMS_GET_MTE_BY_CLASS and click Continue.

             Enter <CURRENT> for the parameter R3System and ITSavailH for the
             parameter MTEClass.

             Click Continue.

             Position at the ITS node of your monitor and click Create nodes.

             Choose Rule node and click Continue.

             Select the rule CCMS_GET_MTE_BY_CLASS and click Continue.

             Enter <CURRENT> for the parameter R3System and ITSurlH for the parameter
             MTEClass.

             Click Continue.

             Click Generate monitor.




(C) SAP AG                                ADM130                                          8-76
1-4   Optional: SAPCCMSR Agent
      1-4-1 Start transaction RZ21. Choose Technical Infrastructure -> Overview of
             Segments. Is there an agent registered at your system? Whats the name of the
             RFC connection used for data collection? What's the name of the host
             monitored by SAPCCMSR?
             Search for this RFC connection in transaction SM59 (hint: the type of the RFC
             connection is TCP/IP). Perform a connection test.
             Open the monitor All Monitoring Contexts in the SAP monitor set SAP CCMS
             Technical Expert Monitors. Are there MTEs showing information from the host
             monitored by SAPCCMSR?
             Start transaction RZ21. Choose Technical Infrastructure -> Segments.
             Look at the line where Segment type is Agent. Under Data set destination
             you can see the name of the RFC connection. The RFC connection is
             SAPCCMSR.<host of SAPCCMSR>.99.
             Select the entry and click Change data. Under Host name, you can see the
             host of SAPCCMSR. Don’t change the entry!
             The connection test is done as described above.
             If you open the monitor All Monitoring Contexts in the SAP monitor set
             SAP CCMS Technical Expert Monitors, you can see the trees
                    Files_of_<host of SAPCCMSR>
                    MoniInfra_<host of SAPCCMSR>
                     _<host of SAPCCMSR>.
      1-4-2 Create a new rule based monitor in your monitor set showing the SAPCCMSR
            information Files_of...
            In the monitor All Monitoring Contexts, position at the MTE Files_of_<host
            of SAPCCMSR>. Click Properties. At the top you see the MTE class
            CcmsFileMonitoring of the node.
             Enter transaction RZ20. Point to your monitor set and click Create (hint:
             maintenance function must be switched on).
             Position at New monitor. Click Create nodes. Select Rule node and, click
             Continue. Select the rule CCMS_GET_MTE_BY_CLASS, click Continue.
             For the parameter R3system, select your Internet Sales system. For the
             parameter MTEClass, select CcmsFileMonitoring.
      Click Save and give a meaningful name to your monitor.
1-5   ALE Monitoring
      1-5-1 Log on to your SAP backend system. Start transaction BDMO. Check the
            situation of ALE monitoring: Is there an active monitoring object that displays
            information about the IDoc MBGMCR? What’s the name of the monitoring
            object?
            Log on to your EBP system. Start transaction BDMO. Click Create/activate
            monitoring objects. Which objects are marked as active?
             Go back to the entrance screen of BDMO. Select one active monitoring
             object and click Change monitoring object. Check if BBPCO is entered

(C) SAP AG                               ADM130                                         8-77
            under Message type. If yes, this is your monitoring object you are looking
            for. If not, perform with the other active monitoring objects.
      1-5-2 Log on to your Internet Sales/EBP system. The ALE information should be
            monitored centrally there.
             Start transaction RZ20. Create a new rule based monitor in your monitor set
             which shows the ALE information of the MBGMCR IDocs of your EBP
             system.
             Hint. Use the rule CCMS_GET_MTE_BY_CLASS. The MTE class name is
             ALEPfGr:<name of the monitoring object determined in the previous
             exercise>.
             Log on to your Internet Sales system.
             Enter transaction RZ20. Position at your monitor set and click Create
             (hint: maintenance function must be switched on).
             Position at New monitor. Click Create nodes. Select Rule node, click
             Continue. Select the rule CCMS_GET_MTE_BY_CLASS, click Continue.
             For the parameter R3System, select your EBP system. The MTE class
             name is ALEPfGr:<name of the monitoring object determined in the previous
             exercise.
             Click Save and give a meaningful name to your monitor.
1-6   SLA - transaction specific monitoring
      1-6-1 Log on to your SAP backend system. Start transaction SE16. Select table
             ALTRAMONI and check if there is an entry for transaction BBPPU99 (create
             shopping basket).
             Start the BBP transaction Create shopping basket using Web access:
             http://<server>:<port>/scripts/wgate/bbpstart/!
             In parallel (also on your SAP backend System) start the SAP monitor
             Transaction-Specific Dialog Monitor of monitor set SAP CCMS Monitors for
             Optional Components. What is the current dialog response time for this
             transaction? What is the MTE class name of the top node of the monitor (hint:
             MTE classes are NOT assigned to virtual nodes)?
             Perform as described.
            Position at the top node of the transaction specific monitor, which is not a
            virtual node (the MTE name is ...Dialog...). Click Properties. The MTE class
            name is ContextR3DialogFocus.
      1-6-2 Log on to your Internet Sales/EBP system. The transaction specific information
            should be monitored centrally there.
             Start transaction RZ20. Create a new rule based monitor in your monitor set
             which shows the transaction specific information of your EBP system.
             Hint. Use the rule CCMS_GET_MTE_BY_CLASS. The name of the parameter
             MTE class is the MTE class determined in the last exercise. Ignore the error
             messages that this class does not exist on your local system.
             Log on to your EBP system.
             Enter transaction RZ20. Point to your monitor set and click Create (hint:
             maintenance function must be switched on).

(C) SAP AG                                ADM130                                           8-78
             Position at New monitor. Click Create nodes. Select Rule node and, click
             Continue. Select the rule CCMS_GET_MTE_BY_CLASS, click Continue.
             For the parameter R3System, select your EBP system. The MTE class
             name is ContextR3DialogFocus.
             Click Save and give a meaningful name to your monitor.
1-7   SAP B2B Procurement Monitors for the Enterprise Buyer
      1-7-1 Your EBP system has special designed monitor templates for the EBP process.
            This EBP specific information should be monitored centrally.
             Start transaction RZ21. Select Technical Infrastructure -> Overview of
             Segments. Is your EBP system already registered?
             Start transaction RZ20. Create a new static monitor in your monitor set, which
             shows the complete BBP information of your EBP system.
             Start the new monitor. Switch between the Current System Status and the Open
             alerts view. Are there any alerts in the tree? Position at a red MTE and click
             Display Alerts.
             Log on to your Internet Sales system (if not already done).
             Start transaction RZ21. Select Technical Infrastructure -> Segments. Under
             System, your EBP system should appear.
             Enter transaction RZ20. Position at your monitor set and click Create
             (hint: maintenance function must be switched on).
             Position at New monitor. Under Selectable MTE open the tree concerning to
             your EBP system. Select the checkbox of the MTE Business to Business
             Procurement (Client). Click Save and give a meaningful name to your
             monitor.
            Perform as described.
      1-7-2 Log on to the EBP system using Internet Explorer.
             Under Application monitors select an EBP monitor.
             The monitor information in SAPGUI and the Internet Explorer are exactly the
             same.
             Perform as described.




(C) SAP AG                               ADM130                                          8-79
  Backup Scenarios


                      1. mySAP Technology              7. Interface Monitoring



                      2. Configuring Internet Sales    8. System Monitoring



                      3. Configuring EBUYER            9. Backup Scenarios


                                                       Appendix Installation Scenarios
                      4. System Administration
                                                                Transaction Codes


                      5. Software Logistics



                      6. Role Management


       SAP AG 2002




(C) SAP AG                                    ADM130                                     9-1
  Component Overview



                      Contents
                         Backup/Recovery Considerations
                         Backup of individual Components
                         Recovery of individual Components
                         Backup/Recovery Concepts


                      Objectives
                      At the end of this unit, you will be able to:
                         Describe the backup and recovery of components in a
                         mySAP.com landscape
                         Describe the backup and recovery strategies in the
                         mySAP.com landscape




       SAP AG 2002




(C) SAP AG                                       ADM130                        9-2
                              Backup/Recovery Considerations
                             Backup/Recovery Considerations Considerations
                                                Backup/Recovery
                                         Backup/Recovery Considerations




(C) SAP AG
                                 Backup/Recovery Considerations




              SAP AG 2002
                                                                                                                             Backup/Recovery Considerations




ADM130
                                                       Backup/Recovery Concepts
                                                                                  Backup/Recovery Considerations
                                                                                            Backup/Recovery Considerations




9-3
  Data Characteristics and Challenges

      Consistent Backup
           Business data distributed over several systems
           Redundant data
           Different database vendors
      Point-in-time Recovery
                                                                             e     Da
           No common checkpoint
                                                                        n tim        ta
                                                                                           lo s
                                                                    w
           Data in file systems
                                                                 Do                            s
      Controlled Shutdown/Startup
           Automated interaction between systems
           Multiple input sources per system                        Inconsistencies
      Requirements
           Distributed processes must ensure data consistency
           System failures may not have an impact on data consistency
           Consistent system copies of the whole environment must be possible
           Not intended for restore after failure of a single system

       SAP AG 2002




  With respect to backup & restore, we have to distinguish two concepts:
   Individual backup of each system component
   Backup of all system components

  It is important to note, that after a crash of a single system component, it is not necessary to restore
  the complete environment. Only the affected component has to be restored and recovered to the
  current point in time (the exact point of failure). A recovery to the current point in time is provided
  by all database systems by the means of log recovery. After recovery of this component, data
  consistency in the system environment is provided again (all open transactions are rolled back or can
  be resumed in all systems, all committed transactions are recovered !).
  Thus, a consistent backup of the complete system environment (of all systems) is not needed to
  protect against failures of single system components.
  A consistent backup of the complete environment is only needed for disaster recovery after the
  whole environment was destroyed or for setting up system copies (see section 'Consistent System
  Copies').




(C) SAP AG                                      ADM130                                                 9-4
  Requirements for Data Consistency

       Backup/Restore of a single system component
            Prevent data loss
            Ensure database recovery to current point in time (point of failure)
            Ensure data consistency between systems
            No impact on productive system caused by
            backup                                                            e      Da
            Fast backup/restore/recovery                                 n tim         ta
                                                                                             lo s
                                                                     w
            Easy handling                                         Do                             s
       Backup/Restore of the complete system
       environment
            Synchronization points                                    Inconsistencies
            Consistent system copies
       To ensure data consistency between sending and receiving system,
        never delete queue entries, not even for hanging queues



        SAP AG 2002




  Other Important data security issues: RAID protection, Implementation of HA solutions, Additional
  offline copies of database, Different devices for logs and data, DB-Log mirroring, Logs saved twice
  on disk and twice on tape, Apply logs regularly to ensure correct recovery, Test restore and recovery
  regularly, Avoid restore on production system, better restore on another system and fix problems
  afterwards
  A consistent backup of the complete system environment can be used for restoring the environment
  in case of a disaster that causes the loss of all (or most of the) systems. If a single system fails, only
  this system must be restored to the current point in time. In this case, it is not suitable to restore the
  whole system environment. Depending on the backup method used for a complete environment
  backup, a complete backup could surely be used to restore and recover just a single system. This
  might not be possible for all of the methods presented in the following. A consistent copy of the
  complete environment might be needed to setup a test landscape with production data (e.g. for
  upgrade tests, etc.). It could serve as a fallback in case of an unsuccessful upgrade or for setting
  savepoints during data migration (so you could go back to a well-defined state if one part of the
  migration fails). It is important to note, that it is not possible to create a 100% consistent copy of the
  environment by just doing point in time restores of all systems (because there is no common,
  synchronized time for all systems, there will always be some modifications that were already done
  by one system and not yet done by some other system, leading to an inconsistent state). To get a
  consistent environment copy, all methods presented in the following use some kind of mechanism to
  ‘freeze’ modifications that might result in inconsistencies between systems.




(C) SAP AG                                       ADM130                                                  9-5
  Backup Reasons

      Periodic backups
      Occasional backups, after system changes of:
          Operating system
          DBMS software
                                                                          e    Da
          SAP filesystems
                                                                     n tim       ta
                                                                                       lo s
                                                                 w
          Middleware components
                                                              Do                           s
               New installations/patches
               Initial/delta loads
                                                                 Inconsistencies
               Changed configuration files
               IAC packages
               Self-developed IACs




       SAP AG 2002




  To avoid installation and configuration of a component, all component‘s software and configuration
  files must be backed up after changes have been made.




(C) SAP AG                                    ADM130                                              9-6
  Backup/Recovery Concepts


                    Backup/Recovery Concepts
    Backup/Recovery Concepts



                                                                          Backup/Recovery Considerations
  Backup/Recovery Concepts
                                               Backup/Recovery Concepts




                                                                          Backup/Recovery Concepts
                                                                                     Backup/Recovery Concepts




                                     SAP AG 2002




(C) SAP AG                                                                               ADM130                 9-7
  Architecture CRM/EBP Server - OLTP



             CRM/EBP Server                           OLTP                   Three data
                                                                             transfer layers
              R/3 Instance                        R/3 Instance
                                                                                 Application
                                     RFC
              CRM Online                                                         Database
                                                     Plug-In
              R/3 Adapter                                                        Storage




         Database Instance                    Database Instance



              Storage Mgmt                       Storage Mgmt


                      Data                            Data


       SAP AG 2002




  For simplicity reasons, only two productive systems are displayed here. With more productive
  systems, a similar proceeding is possible.
  To create a consistent system copy, communication or data transfer between the systems must be
  stopped.
  There are three layers where data transfer (or updates of data) can be prevented:
     Application layer
     Database layer
     Storage layer
  These possibilities will be demonstrated on the following slides.




(C) SAP AG                                   ADM130                                                9-8
  One - DB (1)


  Administrative opportunity
                                                       SAP R/3                   SAP BW
          Consistent recovery to every
          point in time
          Multiple, independent and
          different software solutions
          are located in one database
                                                       SAP CRM                   SAP APO
          One logical and physical
          database instance
          Business data from different
          types of software solutions
          reside in one database
                                                        SAP EBP                  SAP SEM
          Independently changeable
          components



                                                                         RDBMS
       SAP AG 2002




  With Multiple Components in One Database SAP offers you a new option to set up your system
  landscape. Instead of using one database per system (for example, one database for enterprise
  resource planning, supply chain management, customer relationship management, data warehouse,
  portal, or analyzer), the entire system landscape uses one common database. If you install separate
  mySAP.com components on separate databases and servers, you can exploit many advantages. This
  configuration gives you the flexibility to perform separate database upgrades, and you can use
  different operating systems and databases. Because of this flexibility, this deployment option is the
  foundation for the highest possible scalability. However, administering multiple and separate
  systems has several disadvantages. With separate systems on different databases – possibly with
  different releases – you must maintain different operating systems and databases, ensure high
  availability solutions for all the systems, synchronize backup and restore operations, and cover
  different resource requirements. With Multiple Components in One Database, you can install several
  different mySAP.com components in one database, paving the way for a leaner system landscape,
  which can be particularly helpful if your system landscape is already very large. These software
  components are completely independent of each other. By “One Database” we mean one logical and
  physical database instance that contains all the data from different mySAP.com components.
  The Multiple Components in One Database option enables system landscapes with multiple
  mySAP.com components – such as SAP R/3, SAP Customer Relationship Management (SAP CRM),
  SAP Advanced Planner and Optimizer (SAP APO), SAP Business Information Warehouse (SAP
  BW), SAP Strategic Enterprise Management (SAP SEM), or SAP Workplace – to all use the same
  database.




(C) SAP AG                                    ADM130                                                9-9
  One - DB (2)

                                                                  OLTP              OLAP

                                                        SAP R/3                  SAP BW

  Performance considerations
          For performance/sizing
          reasons separate OLTP
          and OLAP systems
                                                       SAP CRM                    SAP APO
  Possible deployment option
          Maintain a high level of
          performance and good
          response times

                                                        SAP EBP                   SAP SEM




                                                           RDBMS                       RDBMS

       SAP AG 2002




  For performance reasons, online transaction processing (OLTP) and online analytical processing
  (OLAP) systems should be installed separately because they require different database parameter
  settings. However, you can install both OLTP and OLAP systems on one physical server, each with
  its own database as shown on the next slide. This separation of OLTP and OLAP components may
  not be necessary for systems where performance is not critical.
  All SAP customers can benefit from this new installation option and should consider it, regardless of
  the size of their IT landscape. Using this option could help to manage development, test, quality
  assurance, training, and smaller production systems. SAP recommends that you first use this option
  on development or test systems to gain experience. Running the Multiple Components in One
  Database option allows you to combine several mySAP.com components in one database. This
  means flexible deployment options and platform independence. It also means you can change
  options independently, implement a full range of scalability options, and use comprehensive e-
  business functions. Using the Multiple Components in One Database option also simplifies the
  administration of high-availability solutions that use multiple mySAP.com components. Initial
  estimates based on experience gained from several projects show that companies can cut
  approximately 10% of disk space and 30% of hardware backup costs (tapes, tape drives, and disk
  systems). Also, operating costs such as managing backups or high-availability solutions possibly can
  be reduced by about 40%. The savings mean reduced maintenance and operating costs overall, as
  well as a streamlined process for backup and high-availability solutions and an efficient use of your
  available resources.




(C) SAP AG                                     ADM130                                              9-10
  One - DB (3)

                                                                 OLTP             OLAP

      Administrative opportunity                       SAP R/3                  SAP BW

          Multiple solutions of the
          same kind on one database
      Reduced Total Cost of
      Ownership
                                                      SAP CRM                   SAP APO
          SAP R/3 test and
          development system
          together with mySAP CRM
          system on one database

                                                       SAP EBP                  SAP SEM




      Installed on one physical server
                                                         RDBMS                       RDBMS

       SAP AG 2002




  Remember, however, that if the database goes down so do all the mySAP.com components in that
  database. Therefore, the Multiple Components in One Database installation may not be suitable for
  large installations or mission-critical applications. Furthermore, this option may also reduce
  flexibility. For example, the database recovery may take longer.




(C) SAP AG                                    ADM130                                             9-11
  Offline Backup



                      CRM                     OLTP           Advantages
              R/3 Instance                 R/3 Instance        Consistent data
                                                               between systems
              CRM Online                                       Easy to realize
                                              Plug-In
              R/3 Adapter                                    Disadvantages
                                                               No 7x24
                                                               Several hours
                                                               downtime
          Database Instance              Database Instance
                                                               Performance loss
                                                               Batch processing
              Storage Mgmt                 Storage Mgmt


                      Data                    Data


       SAP AG 2002




  Performance loss due to buffer reset
  Batch processing must be stopped




(C) SAP AG                                ADM130                                 9-12
  Offline Backup - Delayed Synchronization


                  Backup         System 2          System 3
                  running        finished          finished Shutdown n-1 systems
                                                            and start log backup


                                      System 1
                                      finished

                 System 1
                 Online Backup             Delta Data              Log Backup


                System 2
                Online Backup         Delta Data                  Log Backup


        5       System 3
                Online Backup                        Delta Data      Log Backup
                                                                        Systems
                                                                        synchronized

                                                                  Consistent
                                                                  backup
       SAP AG 2002




  Taking an online backup followed by an offline log-backup can reduce offline time.
  All systems except one must be down at one point in time.
  Synchronization Point is the period between end of system backup and restart of first system. By
  applying the logs that were created during this time a consistent backup is achieved.

  Disadvantage: As before, but much shorter downtime.




(C) SAP AG                                     ADM130                                                9-13
  Application Level: Stop of Application


                                                  Advantages:
                      CRM          OLTP             DB stays online
              R/3 Instance      R/3 Instance        Consistent data
                                                    Easy to realize
               CRM Online
                                   Plug-In
               R/3 Adapter                        Disadvantages
                                                    No 7x24
                                                    Downtime 4-60 min.
                                                    Performance loss
          Database Instance   Database Instance
                                                    Batch processing


              Storage Mgmt      Storage Mgmt


                      Data         Data


       SAP AG 2002




(C) SAP AG                     ADM130                                  9-14
  Application Level: Stop of one Application

                                                                          Advantages
                 CRM                                OLTP                       All databases stay
                                                                               online
           R/3 Instance                         R/3 Instance
                                                                               One system stays
                                                                               online
           CRM Online                              Plug-In
           R/3 Adapter                                                         Consistent data
                                                                               Easy to realize

                                                                          Disadvantages
       Database Instance                    Database Instance                  Manual restart of
                                                                               pending RFCs
                                                                               Stopped application
          Storage Mgmt                         Storage Mgmt                         No 7x24
                                                                                    Performance loss
                                                                                    Batch processing
                Data                                Data                       Running application
                                                                                    No communication
                                                                                    possible
       SAP AG 2002




  This scenario might be applicable for a customer who uses mobile sales only. During times, when no
  mobile sales employees want to connect to the system, the CRM server could be stopped for some
  time.
  This scenario might possibly also be applicable for an Internet Sales scenario if the OLTP system is
  not needed at all times.

  If more than two systems are involved, all but one application must be stopped to get a consistency
  point.
  There might also be a serious performance impact if the online application creates very many queue
  entries while the other applications are down. Processing of these messages could decrease
  performance after restart. This method should not be used during times of high communication load.




(C) SAP AG                                    ADM130                                               9-15
  Storage Level: Stop of Write Access


                CRM                                  OLTP                      Advantages
          R/3 Instance                           R/3 Instance                       Read access
                                   RFC                                              Low impact on
          CRM Online                                                                performance
                                                    Plug-In
          R/3 Adapter                                                               Multiple times per
                                                                                    day
                                                                                    Filesystems can
                                                                                    be included in
      Database Instance                      Database Instance                      backup

                                                                               Disadvantages
                                                                                    All systems must
                                                                                    write to the same
                              Storage Mgmt                                          storage system
                                                                                    (SAN, NAS)

                                   Data


       SAP AG 2002




  Some storage systems offer the possibility to stop write accesses. If all systems store their data in the
  same storage system, this can be used to create a consistent copy.
  Compared to all methods presented before, these concepts that stop write accesses at storage level
  offer the additional advantage that filesystems can also be included in the backup.
  Possible procedure:
     Re-synchronize disk mirror. Stop write accesses (after sync is finished). This step might not be
     needed if the split is done as an atomic operation. Split off disk mirror. Resume write activity
  Notes:
     This procedure has not yet been verified. It has not yet been verified how the different databases
     will react to the suspend write on storage level. It has also not yet been verified, if there are any
     scenarios which will prevent a database restart from a copy taken this way.
     This procedure is hardware dependent, ask your storage partner for possible solutions.
  This scenario does not work if the two systems are connected to different storage subsystems and the
  stop of the write access cannot be done at exactly the same time. One system might still commit and
  write changes, while the second system is already suspended. But the changes done by the first
  system can still be transmitted to the second system and will be processed after the writing resumes.
  The disk copy of both systems will then have the modifications done on the first system but will not
  know of those that need to be done on the second system. The copy will thus be inconsistent.




(C) SAP AG                                      ADM130                                                 9-16
  Incomplete Recovery


  Recovery to current point in time not possible:
  Point-in-time / point-in-log recovery
                                                               Situation:
                                                               • IPC receives new prices via
  Possible reasons:                                              delta download at 8 a.m.
           Logfiles corrupt                                    • No logs are available, restore
                                                                 from backup at 6 a.m. is
           Tapes destroyed                                       required
           DB logically corrupt                                • Example: Logical error in
                                                                 CRM occurred 2h ago.
  Not an option, if for example
                                                               • Sales orders are already
           Single tables dropped                                 posted in OLTP, but
           Wrong transports imported                             corresponding docs are
                                                                 missing now in CRM
  Consequences:                                                ->Each system consistent on
           Data loss                                             transactional basis, but
                                                                 business process is
           Inconsistencies between systems                       inconsistent.
       SAP AG 2002




  All database systems guarantee that it is always possible to recover to the current point in time after a
  system crash occurred. This means, that all committed transactions can be recovered after a crash.
  Because of the techniques used to exchange data between systems, this also ensures that the systems
  are in a consistent state after one system had to be recovered.
  Data between systems can only be inconsistent, if one of the systems could not be recovered to the
  point of the crash, that means, a recovery to an earlier point in time had to be done.
  It is important to note, that before doing an incomplete recovery, everything else should be tried
  to prevent a point-in-time restore.
  Especially data loss for a few tables (e.g. unintentionally dropping a table), import of wrong
  transports or logical corruption are in general no reason for doing a point-in-time restore. Instead the
  system should be kept running and the errors should be fixed (import tables from test system or
  an earlier backup; correct wrong or inconsistent data; apply correcting transports...). This procedure
  becomes more important the longer the system continued running before the error was detected. The
  data loss caused by a point-in-time restore is usually more serious for business operation than the
  energy needed to fix the problems
  Thus, the only reason for an incomplete recovery are either of physical nature: the log files are
  corrupt (may also be caused by software errors) and cannot be applied, the log tapes are destroyed or
  the database is logically corrupt to a degree that it cannot be fixed at all.




(C) SAP AG                                      ADM130                                                9-17
  Incomplete Recovery - Alternatives

  Point-in-time recovery needed for one system
  Data loss, Data inconsistencies

      Restore consistent                  Point-in-time also                       Fix
       system backup                      for other systems                  inconsistencies
   • Data loss in all
     systems                          • Data loss since PIT in          • Data loss in one
   • Possibly more data                 all systems                       system
     lost than due to PIT-            • About the same data             • Least data loss
     recovery                           loss in all systems             • Chance to salvage
                                                                          data from surviving
   • No inconsistencies               • Little inconsistencies            systems
   • Possibly
     inconsistencies                                                    • Most inconsistencies
     between other
     components                                                         Some orders/business
         Order is lost                                                  documents inconsistent

                                                                                           Data
                                                                                  inconsistency
  Data loss
       SAP AG 2002




  A point-in-time recovery of one system always means a data loss and causes inconsistencies between
  the systems of a distributed environment. There is a tradeoff between the amount of inconsistencies
  that will arise and the amount of data loss.
  Restoring a consistent backup of the complete landscape prevented data inconsistencies. With the
  current techniques available (described in the previous chapter), a consistent backup of the whole
  system environment is only available for a few specific dates (which could occure well before the
  date of the point-in-time restore). Thus the data loss might be much bigger than required by the need
  to do a point-in-time recovery. As soon as it becomes possible to do a consistent backup of all
  systems every few minutes, this option will be an interesting alternative for a backup concept.
  Note: Although data of the recovered system components is consistent, there may still be other
  components that cannot be restored this way (for example, mobile client computers). In case of a
  point-in-time restore of all other system components, the mobile clients will still hold the newest
  data that will then be inconsistent to the rest. It is very important to identify all such dependencies.
  It is not possible to do a consistent restore of all systems by doing point-in-time restores for all
  participating systems. There will always be some modifications that were already done on one
  system and not yet done by some other system, leading to an inconsistent state. These inconsistencies
  will probably be very few but all systems lose data starting from the point-in-time to which recovery
  is done.




(C) SAP AG                                      ADM130                                               9-18
  Dependencies and General Recommendations

    In case of a point-in-time recovery of one system
    we generally prefer the following:
        Keep the other systems running
        Do not reset other systems holding originals of
        data
        Fix the inconsistencies as accurately as possible
        Components holding only replicated data can be
        initialized                                                            e       Da
                                                                          n tim          ta
                                                                                              l os
     Why ?                                                            w
           Data loss is kept to the absolute minimum               Do                             s
           Downtime is kept to a minimum
           Downtime of other systems is avoided
           Business must go on, long restores of the                   Inconsistencies
           whole environment can not be accepted
           Reset of other systems can cause additional
           problems or errors



       SAP AG 2002




  It is impossible to give a recommendation on recovery that is suited for all customers' needs. The
  actual decision for a backup concept including a strategy for dealing with incomplete recoveries
  must always be based on the specific situation on site. It is mainly influenced by:
     Data loss
     Inconsistencies
     Downtime
  It is necessary to evaluate to which degree each of the factors' influence could be tolerated in case of
  a point-in-time restore.
  There cannot be a general concept that can be used to automatically fix all inconsistencies. Each
  project must set up a description of what needs to be done from an application point of view if
  specific application data is lost in one of the systems.




(C) SAP AG                                      ADM130                                                9-19
  Incomplete Recovery of CRM Server - Alternatives



   Consequences:
                Data loss in CRM
                OLTP has data that is no more available in CRM
                OLTP should not be reset (data is still available in leading system)



   Alternatives:
     I          1. Restore CRM to latest possible point-in-time, keep OLTP
                   running
                2. Run report showing inconsistencies (SAP note 363602)
                3. Fix inconsistencies using download mechanism

    II
                Restore a consistent backup of both systems



          SAP AG 2002




  If the CRM system must do a point-in-time recovery the OLTP system as the leading system still has
  the relevant data (except for data that has not yet been replicated to the OLTP or data that is not
  replicated to the OLTP at all). To identify inconsistencies between CRM and OLTP there is a generic
  compare tool available (see OSS note 363602). Missing or incorrect data in CRM can be
  downloaded using the download mechanism for single objects.
  The compare tool can only be used to compare objects that exist in the OLTP with the consolidated
  database (CDB) of the CRM. It does not show objects that exist in CRM only.
  While running the compare job, processing in CRM and OLTP should be stopped and all queues
  should be empty. Otherwise, new or altered data that will be replicated correctly might show up as a
  difference.
  Note: If processing continues during the comparison, the following things should be considered:
  Running the compare twice can help to eliminate objects that were included in the list by mistake
  (because they were just being processed). Manual checks can help to identify inconsistent objects
  and segregate them from erroneously included objects. Processes and changes that only affect one of
  the databases are not a problem at all. If the CRM system is already running while the compare tool
  is still active and there are new orders created, inconsistent order numbers may appear (for example,
  the same order number for a newly created CRM order as for an old order that was lost in CRM and
  now only exists in OLTP).




(C) SAP AG                                    ADM130                                              9-20
  Incomplete Recovery of CRM Server - Alternatives


                       Last Synchronization Point         Point-in-time
                       / Last Consistent Backup           for CRM                    CRM




                                                                                          Rebuilt data
                 CRM
      I
                 OLTP

                                               Inconsistent      Lost data (e.g.    Lost data (not
                                                                                     Lost data
                                               OLTP data         CRM online)        yet replicated)



                 CRM
     II
                 OLTP

                                                                             Lost data

       SAP AG 2002




  I. Alternative Fix inconsistencies:
     Data that was not yet replicated to the OLTP is lost
     Data that was already replicated to OLTP can be identified using the compare tool. This data can
     then be downloaded manually to the CRM using the standard download mechanism. Such data
     that originates from CRM and was downloaded again from OLTP might not be trackable by its
     original document numbers because numbers might be different after the download was redone.
     All CRM data that is not replicated to the OLTP is lost (for example, activities, CRM online data)
  II. Alternative Restore Consistent System Backup
     Data from OLTP and CRM is lost
     Lost data could then possibly be reconstructed from a copy of former OLTP (but alternative (I)
     would be an easier job then because the same steps need to be done).
  III. Conceivable alternative Complete Initial Download from OLTP, no CRM restore:
     All CRM data that was not replicated to the OLTP is lost (for example, activities, CRM online
     data). In this case this affects all data ever entered in CRM (since start of production!)!
     There are two conceivable possibilities for this alternative:
     - Delete all application data from CRM, preserve customizing
     - The CRM system is set up completely new which includes customizing, and so on.
        Customizing information is lost and must be re-entered




(C) SAP AG                                     ADM130                                               9-21
  Incomplete Recovery of OLTP - Alternatives



   Consequences:
             Data loss in leading system
             CRM references non-existing OLTP data

   Alternatives:
      I      1. Restore OLTP to latest possible point-in-time, keep CRM running
             2. Fix inconsistencies as they occur
                  No compare tool available

      II     Restore a consistent backup of both systems


     III     1. Reset CRM system to the same or a slightly earlier point-in-time
                  than OLTP
             2. Run compare reports and fix inconsistencies
       SAP AG 2002




  There is no tool available to find out which data is in CRM only (missing in OLTP). The options
  here are somewhat different from the previous scenario of a CRM data loss.
     If the CRM system stays as it is, there is no tool to find out inconsistencies. The inconsistencies
     could be dealt with as they occur or they must be identified in a special project. Inconsistencies
     can be recognized for example by hanging flows that cannot be executed or that return errors.
  If it is impossible to continue operation with the danger of such inconsistencies, the CRM system
  must also be reset to a former point-in-time. This could be either the restore of a consistent backup of
  the whole environment or a restore of the CRM system following the restore of the OLTP system.
     A consistent system copy of the complete environment can only provide a consistent recovery to
     certain times (the time the backup was taken) and not to any arbitrary point-in-time. If this date is
     long before the point-in-time the OLTP itself could be recovered, the data loss is unnecessarily
     big. In that case (or if no consistent backup of the environment is available), the third alternative
     could be an option.
     If both, CRM and OLTP, need to be restored doing a point-in-time restore, the inconsistencies will
     be smaller, the smaller the time difference between the two restores. But even if the systems were
     restored to the same point-in-time, there usually will be inconsistencies (because server clocks are
     not synchronized, unless both systems run on one host). If the CRM is restored to a state shortly
     before the state of the OLTP, these inconsistencies could be identified using the compare tool.




(C) SAP AG                                      ADM130                                               9-22
  Incomplete Recovery of OLTP - Alternatives


                       Last Synchronization Point          Point-in-time
                       / Last Consistent Backup            for OLTP                   OLTP




                 CRM
      I
                 OLTP                                                                  Inconsistent
                                                                                       CRM data


                 CRM
     II
                 OLTP


                 CRM
     III
                 OLTP

       SAP AG 2002




  I. Alternative Fix Inconsistencies:
     Data from OLTP is lost.
     Data is inconsistent.
     No tool support to identify data that is only in CRM.
     The compare tool could be used to identify lost changes that were made to data that already
     existed in the OLTP before the respective point-in-time. This data could then be manually
     corrected in the OLTP.
     Lost data in OLTP might possibly be reconstructed from CRM.

  II. Alternative Restore consistent system copy:
     Data from OLTP and CRM is lost.
     Data is consistent.
     Lost data can possibly be reconstructed from a copy of former CRM.

  III. Alternative Point-in-time for all systems:
     Data from OLTP and CRM is lost.
     Data is inconsistent. Inconsistencies will probably be quite few and can be identified as previously
     described.




(C) SAP AG                                      ADM130                                               9-23
  Incomplete Recovery - Impact on Other
  Components


                 Data loss in OLTP or CRM can cause
             inconsistencies with dependent components


      OLTP data loss:                                 CRM data loss:
           IPC (up to CRM 2.0B): initial load              ITS: Download of flow and
                                                           service files
           IPC (from 2.0C): Initialize IPC
           cache                                           IMS: Download catalog files
                                                           Webserver: Publication of
                                                           multi-media files




          Actions only needed if a component's data was
          affected by changes made during the period lost
       SAP AG 2002




  Data of the Web middleware can always be downloaded from the leading systems. Data loss is not
  an issue. One disadvantage is the possible long runtimes of the initial download. Instead of
  downloading the data from CRM, second instances of each of these components could be used to
  copy data.
  This slide shows the impact of an incomplete recovery of CRM or OLTP on the other system
  components of a CRM landscape.
  After data loss in one of the main systems (OLTP or CRM), data of all depending components must
  be analyzed and possibly be restored to reflect the new situation.
  Note: If there were no changes done to the data of a dependent component during the period of data
  loss, there is of course no need to adapt the component’s data (for example, if there were no changes
  to ITS flow files they need not to be downloaded after an incomplete CRM restore).
     IMS: Download of the catalog files is needed if a new version of the catalog was created during
     the period lost. In this case, the multi-media files must also be republished to the web server
     because otherwise the names of the files are incompatible to those referenced in the HTML pages.




(C) SAP AG                                     ADM130                                              9-24
  Incomplete Recovery - Alternatives


      CRM (data loss)
           Run reports showing inconsistencies and fix inconsistencies using
           download mechanism.
           Reload data from OLTP system. Data entered in CRM Online is lost.


      OLTP (data loss)
        B CRM references non-existing OLTP data
           Keep CRM system running and fix inconsistencies as they occur.
           Reset CRM system to a slightly earlier point-in-time than OLTP.
           (if needed, keep a copy of original system for manual compare and
           tracking of lost data), run compare reports and fix inconsistencies.




       SAP AG 2002




  CRM and OLTP systems are most critical because of potential inconsistencies. Reports that will
  show inconsistencies between CRM and OLTP are currently in development. They are already
  available for customizing data. Missing data in CRM can be downloaded using the download
  mechanism for single objects.
  There cannot be a general concept that can be used to automatically fix all inconsistencies. It is
  recommended that each project set up a description of what has to be done from an application point
  of view if specific application data is lost.
  If CRM and OLTP system must both be restored doing a point-in-time restore, the inconsistencies
  will be smaller, the smaller the time difference between the two restores is. But even if the systems
  were restored to the same point-in-time there usually will be inconsistencies (because time is not
  synchronized). A consistent system copy of the complete environment cannot provide absolute
  security here, because it can only provide a consistent recovery to certain times (the time when the
  backup was taken) and not to any arbitrary point-in-time.




(C) SAP AG                                     ADM130                                              9-25
  Incomplete Recovery - Summary



  Incomplete recovery should not be an issue.
     Modern storage systems prevent hardware failures
     Backup mechanism of database systems ensure
     complete recovery
     Communication process guarantees data consistency
     between systems
     Point-in-time recovery is not an option from a business
     perspective




       SAP AG 2002




(C) SAP AG                        ADM130                       9-26
  Unit Summary



                      You are now able to:
                         Describe the backup and recovery of
                         components in a mySAP.com landscape
                         Describe the backup and recovery
                         strategies in the mySAP.com landscape




       SAP AG 2002




(C) SAP AG                              ADM130                   9-27
  Further Documentation



                      Additional information about Interface
                      Monitoring
                         service.sap.com/onedb




       SAP AG 2002




(C) SAP AG                              ADM130                 9-28
                                                        Introduction: Exercise

                   Unit: Backup Scenarios
                   Topic: Failure of Components


                   At the conclusion of this exercise, you will be able to:
                   • Describe the Problems that occur if some Components are not
                     available anymore



                   You are an administrator responsible for the system configuration.




The following exercises can by done by testing all the errors. They can be done
theoretically as well. Then you just have to think about the problems that might occur.

1-1    Loss of IPC in Internet Sales Scenario: Impact on core business process
       1-1-1 Your instructor will shut down the IPC.
      1-1-2 Which steps of the Internet Sales business process are still working, which are
            not working anymore?
       1-1-3 Is production operation still possible? If yes, are there any constraints?
1-2           Loss of IMS in Internet Sales scenario: Impact on core business process
       1-2-1 Your instructor will shut down/disconnect the IMS
       1-2-2 Which steps of the the Internet Sales business process are still working, which
             are not working anymore ?
       1-2-3 Is production operation still possible ? If yes, are there any constraints ?
1-3           Loss of CRM in Internet Sales scenario: Impact on core business process
       1-3-1 Your instructor will shut down/disconnect the CRM system.
       1-3-2 Which steps of Internet Sales business process are still working, which are not
             working anymore?
       1-3-3 Is production operation still possible? If yes, are there any constraints?
1-4    Loss of Middleware Components (ITS/SAP J2EE Engine in Internet Sales scenario):
       Impact on core business process.
       1-4-1 Your instructor will shut down/disconnect the ITS/SAP J2EE Engine of the
             Internet Sales server
       1-4-2 Which steps of the Internet Sales business process are still working, which are
             not working anymore?
       1-4-3 Is production operation still possible? If yes, are there any constraints?
(C) SAP AG                                  ADM130                                          9-29
1-5   Loss of R/3 backend in EBP scenario: Impact on core business process
      1-5-1 Your instructor will shut down/disconnect the R/3 backend system
      1-5-2 Which steps of the EBP business process are still working, which are not
            working anymore?
      1-5-3 Is production operation still possible ? If yes, are there any constraints?
1-6   Loss of requisite catalog in EBP scenario: Impact on core business process
      1-6-1 Your instructor will shut down/disconnect the requisite catalog.
      1-6-2 Which steps of the EBP business process are still working, which are not
            working anymore?
      1-6-3 Is production operation still possible? If yes, are there any constraints?




(C) SAP AG                                 ADM130                                         9-30
                                                                                Solutions

                   Unit: Backup Scenarios
                   Topic: Failure of Components


                   At the conclusion of this exercise, you will be able to:
                   Describe the Problems that occur if some Components are not available
                      anymore



                   You are an administrator responsible for the system configuration.




The following exercises can by done by testing all the errors. They can be done
theoretically as well. Then you just have to think about the problems that might occur.

1-1    Loss of IPC in Internet Sales Scenario: Impact on core business process
      Your instructor will shut down the IPC.
              Your Instructor has shut down the IPC via PCAnywhere
       1-1-2 Which steps of the Internet Sales business process are still working, which are
             not working anymore?
              As the ITS receives no pricing information, no products are displayed. You
              can´t put anything into your shopping basket.
       1-1-3 Is production operation still possible? If yes, are there any constraints?
              From the Web no production operation is possible.
1-2           Loss of IMS in Internet Sales scenario: Impact on core business process
       1-2-1 Your instructor will shut down/disconnect the IMS
              Your instructor has changed the RFC Connection to the IMS, that is read
              by the ITS.
       1-2-2 Which steps of the Internet Sales business process are still working, which are
             not working anymore ?
              From the Web there is no access to any catalog data. Therefore nothing can
              be done.




(C) SAP AG                                  ADM130                                         9-31
      1-2-3 Is production operation still possible? If yes, are there any constraints?
             From the Web no production operation is possible. A inhouse sales
             representative could still work directly on the CRM server and create sales
             orders.
1-3          Loss of CRM in Internet Sales scenario: Impact on core business process
      1-3-1 Your instructor will shut down/disconnect the CRM system.
             Your instructor has changed the RFC connection from the ITS to the CRM
             server.
      1-3-2 Which steps of the Internet Sales business process are still working, which are
            not working anymore?
             As the CRM server is need for the initial logon process, nothing can be
             done in the Web.
      1-3-3 Is production operation still possible? If yes, are there any constraints?
             No production work is possible at all.
1-4   Loss of Middleware Components (ITS/SAP J2EE Engine in Internet Sales scenario):
      Impact on core business process.
      1-4-1 Your instructor will shut down/disconnect the ITS/SAP J2EE Engine of the
            Internet Sales server
             Your instructor has shut down the ITS Instance / SAP J2EE Engine of the
             CRM system.
      1-4-2 Which steps of the Internet Sales business process are still working, which are
            not working anymore?
             From the Web no production operation is possible.
      1-4-3 Is production operation still possible? If yes, are there any constraints?
             A inhouse sales representative could still work directly on the CRM server
             and create sales orders.
1-5   Loss of R/3 backend in EBP scenario: Impact on core business process
      1-5-1 Your instructor will shut down/disconnect the R/3 backend system
             Your instructor has changed the RFC connection from the CRM/EBP
             server to the R/3 backend system.
      1-5-2 Which steps of the EBP business process are still working, which are not
            working anymore?
            Depending on EBP business scenario:
             a) If purchase order is stored in EBP, EBP scenario can operate in full
                productive mode
             b) If, distributed scenario is used (purchase order gets stored in OLTP):
                Browse catalog and save shopping basket still works. Save+confirm
                order still works. Order get queued and are not stored anymore on
                OLTP. Productive operation possible, queues are synchronized when
                OLTP comes up again
             In both scenarios no access to backend business documents is possible.


(C) SAP AG                                 ADM130                                        9-32
      1-5-3 Is production operation still possible? If yes, are there any constraints?
             Production work may be possible with some restrictions.
1-6   Loss of requisite catalog in EBP scenario: Impact on core business process
      1-6-1 Your instructor will shut down/disconnect the requisite catalog.
             Your instructor has changed catalog data on the CRM server.
      1-6-2 Which steps of the EBP business process are still working, which are not
            working anymore?
             Everything is still possible, except to fill a shopping basket with the help of
             catalog information.
      1-6-3 Is production operation still possible? If yes, are there any constraints?
             Production operation is still possible.




(C) SAP AG                                 ADM130                                        9-33
  System Administration


                      1. mySAP Technology              7. Interface Monitoring



                      2. Configuring Internet Sales    8. System Monitoring



                      3. Configuring EBUYER            9. Backup Scenarios


                                                       Appendix Installation Scenarios
                      4. System Administration
                                                                Transaction Codes


                      5. Software Logistics



                      6. Role Management


       SAP AG 2002




(C) SAP AG                                    ADM130                                     10-1
  Installation Scenarios



                      Contents
                         Technical System Environment of EBP/CRM Business
                         Scenarios




                      Objectives
                      At the end of this unit, you will be able to:
                         Describe the technical system environment of EBP/CRM




       SAP AG 2002




(C) SAP AG                                       ADM130                         10-2
  EBP Technical System Environment

 Web Clients          Web Servers                  Web Middleware      SAP System
                                                        Internet
   Intranet            Web Server (1)                 Transaction        Enterprise     To OLTP
                                                       Server (6)      Buyer System (7) and other
                                                                                            Systems




                                        WGate
                         Internal                       Internal
                       Web Server (2)                AGate Instance        EBP
  Employees                                                               System
                                                                                          RDBMS




                                        WGate
                       Administrative                Administraive
                       Web Server (4)                Agate Instance


                                                                       Catalog (8)
                                        Jrun (5)
                       Administrative
                       Web Server (4)                                       Jrun
                                                                       Servlet Engine
   Internet                                                              Requisite
                                        WGate




                         External                       External          Catalog         RDBMS
   Vendor              Web Server (3)                 Agate Instance



                      SAP Business
                      Connector (9)
    Vendor             Business
    System             Connector                                                     Or to OLTP


       SAP AG 2002




  The graphic provides an overview of the mySAP Enterprise Buyer professional edition (EBR)
  solution and its components.
    - Internet Web Server (Windows NT 4.0 Server)
    - EBR Middleware (Windows NT 4.0 Server)
    - R/3 EBR Server (all platforms)
    - HTTP port numbers:
       From intranet into Web server: 80
       From intranet (employee) into Web server: 2080
       From Internet (vendor) into Web server: 2082
       From vendor's Web server into Business Connector: 9999




(C) SAP AG                                           ADM130                                       10-3
  EBP All-in-One Implementation




                                        All-in-one Enterprise Buyer Host

        Internet                                                                                 To OLTP
                                                                                                 Systems




                                                 WGate
                                    EBP                         EBP




                                                  ITS
                                  Web Server                    ITS              EBP
                                                                                System




                                                 WGate
                                  External EBP             External EBP
                                                                                         RDBMS




                                                  ITS
                                   Web Server                   ITS

                                   Catalog                      Requisite




                                                         JRun
                                                 JRun
                                                  DLL
                                  Web Server                     Catalog
                                                                            RDBMS



         Vendor                   Business
         System                   Connector




       SAP AG 2002




  For test, demonstration, or development systems, performance is often not crucial. Security is also
  not an issue, because functions that are designed to be used over the Internet are only performed in
  the local network for testing purposes. In such a system, you can install all software components on
  one computer.
  SAP strongly recommends that you do not connect an all-in-one installation to the Internet.




(C) SAP AG                                        ADM130                                            10-4
  EBP Small Production Implementation



     Intranet         Web Middleware and Cartalog Host
                         Catalog                     Requisite




                                       JRun


                                              JRun
                                       DLL
                        Web Server                    Catalog RDBMS
                                                                            EBP Host




                                      WGate
                          EBP                        EBP




                                       ITS
                        Web Server                   ITS                                    To OLTP
                                                                       EBP                  Systems
                                               External EBP           System
                                                    ITS                        RDBMS




     Internet
                                                           Firewall

                        Inertnet Web Host
                                      WGate




                       External EBP
                                       ITS




                        Web Server


      Vendor            Business
      System            Connector



       SAP AG 2002




  The graphic shows a scenario for a small mySAP Enterprise Buyer (EBP) production system with up
  to a few hundred users.
     - For exact sizing information, go to http://service.sap.com/sizing and contact your hardware
        partner.
  The separation between Web, middleware, and catalog servers on one side and EBP server on the
  other is recommended for smooth operation of all systems. When the database systems reside on
  separate computers, the EBP server does not have to carry the load of catalog browsing and other
  purely Web based activities. You can choose either the same RDBMS for both servers or a different
  one for the EBP system.
  The separate Web server is needed to implement the security mechanisms that are needed when
  connecting a system to the Internet. You should always use a firewall to separate the network that
  includes the Web servers from the corporate network.




(C) SAP AG                                           ADM130                                     10-5
  EBP Large Production Implementation
                                                          Server Netwerk

                                                                                             Catalog DB Host




                                                             JRun
                                                 JRun
                                    Catalog




                                                 DLL
                                                                     Requisite
                                   Web Server                         Catalog
          Intranet                                                                          RDBMS




                                                  WGate
                                     EBP                        EBP
                                                              EBP
                                   Web Server                    ITS
                                                            Web Server




                                                                                                    EBP Host(s)




                                                             JRun
                                                 JRun
                                    Catalog




                                                 DLL
                                                                     Requisite
                                   Web Server                         Catalog
                                                                                             EBP                  To OLTP
                         HTTP



                                                  WGate
                         Load
                                   EBP
                                 Web Server
                                                              EBP
                                                                EBP
                                                                 ITS
                                                            Web Server
                                                                                            System                Systems
                       Balancing                                                                        RDBMS

                                                 … More Hosts



                                      DMZ
          Internet
                                         Internet Web                             Internet ITS
                                             Server                                  Server
                        Firewall




                                                          Firewall
                                                  WGate




                                    External                                     External
                                   Web Server                                      ITS

                                     Business
                                     Connector
             Vendor
             System
       SAP AG 2002




  The mySAP EBP large production implementation allows scalable installations for a thousand users
  or more.
     - For exact sizing information, go to http://service.sap.com/sizing and contact your hardware
       partner.
  The implementation also allows for strong security measures for all servers connected to the Internet.
  The firewalls and the SAProuter are not part of the EBR implementation. They are shown here
  merely to illustrate a secure Internet enabled setup. The firewall between WGate and AGate is a
  necessary component of every effective security strategy.




(C) SAP AG                                                     ADM130                                                       10-6
  CRM Business Scenario Component Overview




       SAP AG 2002




  The graphic probides an overview of the main mySAP EBP and mySAP CRM scenarios.
  Before you begin to install a component, be sure to read the SAP Notes and the installation guides
  for the component. Software requirements for each component are detailed in the respective
  installation guides.
  The OLTP system may be an SAP Basis System (R/3 System) or other enterprise resource planning
  (ERP) system that performs financial accounting and controlling.
  Scenarios:
    - Classic: mySAP Enterprise Buyer (EBP) is implemented together with one or more ERP
        systems. All materials management (MM) is mapped in the OLTP System.
    - Decoupled: Requirement coverage requests for nonproduction materials or services are directly
        processed further, and purchase orders are placed, in the EBP system. The follow-on documents
        for the purchase orders are also created in the EBP system (confirmation, goods receipt / service
        entry and invoice). You can continue to procure production materials and services, using the
        MM functions in your ERP system.




(C) SAP AG                                     ADM130                                                10-7
  CRM Internet Sales Technical System Environment




                         Internet Sales                                   APO
                        Web Application
                                                                                         RDBMS

                HTTP   SAP J2EE SAP Java
                                                       CRM
                        Engine Connector
                                                       Server
                        Server
                                                                          BW
                                                                                         RDBMS




                                                                          OLTP R/3

                                                                               Plug-In
                                                            TREX                         RDBMS
                         IPC   SAP Java
                        Server Connector     SAP                IMS
                                            Gateway
                                                        Search Engine



       SAP AG 2002




  The graphic provides an overview of the CRM business scenario and the technical environment of
  the SAP Internet Sales component.
    - Internet Web server: Windows NT 4.0 Server
    - Internet Sales Middleware: Windows NT 4.0 Server
    - SAP R/3 CRM server: all platforms




(C) SAP AG                                   ADM130                                              10-8
  CRM Minimal Internet Sales Scenario


   Intranet

   Test User                                                                        APO
                                   All-in-One Internet Sales Host
                                                                                   Server
                                       Dr.Fuzzy      IMS


                                                    SAP
                                                                    CRM/EBP         BW
                                                   Gateway
                                                                     System
                                                                                   Server

   Internet               SAP J2EE Engine                           Middleware


   Customer                                                                        OLTP
               Firewall




                                                     IPC
                                                                                  System
                                        SQL        Java VM
                                       Server
                                                   Loader
                                                   Java VM
                                                                                   Plug-In




       SAP AG 2002




  The mySAP CRM minimal Internet Sales scenario is only useful for test, demonstration, and
  development systems. It should not be used for production systems.




(C) SAP AG                                        ADM130                                      10-9
  CRM Medium Internet Sales Scenario



                                                         Web Middleware                    APO
                                                                                          Server
                                                         TREX        IMS     CRM Host
   Internet
                                                                    SAP
                            Web                                              CRM/EBP
    Customer                                                       Gateway                 BW
                           Server                                             System
                                                                                          Server
                                                        Ims.dll




                                            Firewall
                Firewall




                                    WGate
                            Web                        SAP J2EE
                           Server
                                                                             Middleware
                                                        Engine
                                                         Ipc.dll

                                                                    IPC                    OLTP
                                                                   Java VM
                                                                                          System
                                                         SQL
                                                        Server     Loader

                                                                   Java VM                Plug-In




       SAP AG 2002




  The mySAP CRM medium Internet Sales scenario is suitable for production systems with up to a
  few hundred users.
  For B2C, high availability and especially scalability is a crucial issue, but is not covered in this
  scenario.




(C) SAP AG                                                 ADM130                                   10-10
   CRM Large Internet Sales Scenario

                                                  Index Server Host             Index Server Host
                                                                   SAP
                                                 TREX     IMS                     IMS     TREX
                                                                  Gateway



                              Web
                             Server                 ITS Host
                                                                                               APO
                                                     Ims.dll
                              Web                   SAP J2EE                                  Server
                             Server                  Engine                 CRM Host
                                                      Ipc.dll
  Firewall




                                      Firewall
                                                                            CRM/EBP
                              Web                                            System
                             Server                 ITS Host                                   BW
                                                     Ims.dll                Middleware        Server
                 Load
                              Web                   SAP J2EE
               Balancing
                             Server                  Engine
                                                      Ipc.dll




                                                                                              OLTP
                                                        IPC Host                             System
                                                                  IPC

                                                                Java VM
                                                                Loader                        Plug-In
                                                                Java VM


              SAP AG 2002




   The mySAP CRM large Internet Sales scenario is suitable for production systems with hundreds or
   thousands of users, especially in the B2C scenario.
   Clients are omitted here for simplicity. Redundant Internet connections and network topology should
   be used to ensure high availability.
   As an example, load balancing between two Web servers and AGates is shown. There may be any
   number of Web servers.
   The Index Management Server (IMS) can be scaled by registering more than one IMS as RFC server
   at the Gateway. In this case, third party tools must be used to ensure consistency of the index files on
   both hosts.
   The CRM system itself scales using message server based load balancing with multiple application
   servers.




(C) SAP AG                                              ADM130                                          10-11
  Further Documentation



                      For additional information about mySAP
                      components, go to URLs:
                        service.sap.com
                        Component compatibility:
                        service.sap.com/dbosplatforms




       SAP AG 2002




(C) SAP AG                             ADM130                  10-12
  Unit Summary



                      You are now able to:

                         Describe the technical system environment of
                         mySAP EBP/CRM




       SAP AG 2002




(C) SAP AG                              ADM130                          10-13
                                                    Transactioncodes:

Transaction       Path (SAP Menu or Name/Description System
                  SAPCRM_MENU)
BBP0 (area menu) -                      SAP Business-to-     CRM
                                        Business
                                        Procurement
BD54              -                     Change View        CRM, R/3
                                        "Logical Systems":
                                        Overview
BD64              -                     Display            CRM, R/3
                                        Distribution Model
BD87              Basis Tools           Select IDocs         CRM, R/3
                  →ALE →ALE
                  Administration
                  →Monitoring →
                  Status Monitor
BDMO              -                     ALE monitoring       CRM, R/3
                                        obj.
CIF (area menu)   -                     Core Interface   R/3
                                        Advanced Planner
                                        and Optimizer
COMM_PCAT_I       Master Data →       Initial product   CRM
MS_INIT           Product Catalog → catalog replication
                  Initial Replication
COMM_PCAT_I       Master Data →      Update product      CRM
MS_UPDA           Product Catalog →  catalog replication
                  Update Replication
CRM_SHOP          Internet Sales →      Display View         CRM
                  Maintain Web          "Shop for Internet
                  Shop                  Sales": Overview
CRMD_BUS2000 Sales Orders →             Create               CRM
115          Maintain Sales             Consignment Fill-
             Orders                     up
BP                Master Data →         Process Business     CRM
                  Business Partner      Partner
                  → Maintain
                  Business Partner
(C) SAP AG                           ADM130                             10-14
ME23N        Logistics→           Display Purchase   R/3
             Materials            Order
             Management→
             Puchasing→
             Purchase Order→
             Display
MIGO         Logistics→           Goods Reiceipt     R/3
             Materials            Purchase Order
             Management→
             Inventory
             Management→
             Goods
             Movement→
             Goods Receipt→
             For Purchase
             Order→ Purchase
             order known
PFCG         Tools           Role Maintenance        R/3, CRM
             Administration
                User
             Maintenance Rol
             es
PPOMA_CRM    Master Data    General Attribute        CRM
               Organization (CRM) Change
             Model Maintain
             Organization
             Model
R3AC1        Middleware Data      Object Overview    CRM
             Exchange
             Object
             Management
             Business Objects
R3AC3        Middleware Data      Object Overview    CRM
             Exchange
             Object
             Management
             Customizing
             Objects
R3AC4        Middleware           Display View       CRM
             Delta Exchange       "Object Class
             Delta Load from      Activation":
             OLTP R/3             Overview
(C) SAP AG                     ADM130                           10-15
             Setup Delta Load
R3AC5        Middleware Data      Object Overview      CRM
             Exchange
             Object
             Management
             Condition Objects
R3AC6        Middleware           Display View         CRM
             Administraion        "Middleware
             Define Middleware    Parameter":
             Parameters           Overview
R3AM1        Middleware           Monitor Requests     CRM
             Monitoring
             Delta Exchange
             Monitor Objects
R3AS         Middleware           Start Initial Load   CRM
             Delta Exchange
             Initial Load
             Start
R3AS4        Middleware           CRM Compare          CRM
             Delta Exchange       Start
             Synchronisation
             Synchronize
             Objects
RZ20         Tools CCMS           CCMS Monitor         CRM, R/3
             Control/             Sets
             Monitoring
             Alert Monitor
RZ21         Tools CCMS           Monitoring:          CRM, R/3
             Configuration        Properties and
             Alert Monitor        Methods
SE16         Tools ABAP           Data Browser         CRM, R/3
             Workbench
             Overview Data
             Browser
SE38         Tools ABAP           ABAP Editor          CRM, R/3
             Workbench
             Development
             ABAP Editor
SE80         Tools                Object Navigator     CRM, R/3
             Workbench
             Overview
(C) SAP AG                     ADM130                             10-16
             Object Navigator
SM36         Tools CCMS          Define              CRM, R/3
             Jobs Definition     Background Job
SM37         Tools CCMS          Background Job      CRM, R/3
             Jobs                Maintenace
             Maintenance
SM58         Middleware        Transactional RFC CRM, R/3
             Monitoring
             Transactional RFC
                Display
             Transactional RFC
             Requests
SM59         Tools               RFC Destinatons     CRM, R/3
             Administration
             Administration
             Network RFC
             Destinations
SMOEAC       Middleware          Administration      CRM
             Administration      Console: Object
             Administration      Navigator
             Console
SAINT        -                   SAP Add-On          CRM, R/3
                                 Installation Tool
SCC4         Tools               Client              CRM, R/3
             Administration      Maintenance
             Administration
             Client
             Administration
             Client
             Maintenance
SKPR07       -                   KPRO IMS            CRM
                                 Monitoring
SLG1         -                   Evaluate            CRM
                                 Application Log
SMO8FD       Middleware        Display and Check CRM
             Message Flow      Flow Definitions
             Display and Check
             Flow Definitions
SMO8REORG    Middleware          Delete processed    CRM
             Message Flow        BDOCs
             Delete Processed
(C) SAP AG                    ADM130                            10-17
             Bdoc Messages
SMOGGEN      Middleware          Generate Services   CRM
             Development
             Generation
             Generation
             Generation and
             Transport →
             Generate Services
SMQ1         Middleware     qRFC Monitor             CRM, R/3
             Monitoring     (Inbound Queue)
             Queues Display
             Inbound RFC
             Queues
SMQ2         Middleware     qRFC Monitor     CRM, R/3
             Monitoring     (Outbound Queue)
             Queues Display
             Outbound RFC
             Queues
SMQR         Middleware          qRFC Monitor        CRM
             Administration      (QIN Scheduler)
             Register/Deregister
             Queues
SMW00        Middleware          Error Handler       CRM
             Message Flow        Settings
             Error Handler
             Settings
SMW01        Middleware          Display BDoc        CRM
             Monitoring          Messages
             Message Flow
             Display BDoc
             Messages
SMW02        Middleware      Display BDoc            CRM
             Monitoring Mess Messages
             age Flow        Summary
             Display BDoc
             Messages
             Summary
SMW3FDBDOC   Middleware          Change View         CRM
             Message Flow        Flow: Specific
             Define BDoc         Configuration for
             specific Flow       BDoc Type

(C) SAP AG                   ADM130                             10-18
SMW3FDSTD    Middleware           Change View         CRM
             Message Flow         Flow: Standard
             Define Standard      Configuration
             Flow
SMWMFLOW     Middleware           Display Message     CRM
             Monitoring           Flow Statistics
             Message Flow
             Display Message
             Flow Statistics
SMWMSCHEDU   Middleware     Standard qRFC             CRM
LER          Monitoring     Scheduler
             Queues Display Information
             qRFC Scheduler
             Information
SMWP         Administration     CRM Middleware        CRM
             Monitoring         Portal
             Central Monitoring
                Middleware
             Portal
SMWT         Administration   Middleware Trace CRM
             Monitoring
             Message Flow
             Display
             Middleware Trace
SPRO         Tools                Customizing         CRM
             Accelerated
             SAP
             Customizing
             Edit Project
SRMO         -                    Retrieval: Search   CRM
                                  Server Relation
                                  Monitor
ST03N        Middleware           Workload            CRM, R/3
             Monitoring
             Performance
             Workload
             Analysis
SU01         Tools                User Maintenance    CRM, R/3
             Administration
             User Maintenace
             Users

(C) SAP AG                     ADM130                            10-19
SU05         Tools             Maintain Internet    CRM, R/3
             Administration    User
             User Maintenace
             Internet Users
SU25         -                 Profile Generator:   CRM, R/3
                               Upgrade and First
                               Installation
VA03         Logistics→ Sales Display Sales         R/3
             and Distribution→ Orders
             Sales→ Order →
             Display
VD01         Logistics → Sales Create Customer      R/3
             and Distribution →
             Master Data →
             Business partners
             → Customer →
             Create → Sales
             and Distribution
VD03         Logistics→ Sales Display Customer      R/3
             and Distribution→
             Master Data→
             Business
             Partners→
             Customers→
             Display→ Sales
             and Distribution




(C) SAP AG                 ADM130                              10-20
Customizing Transactions (within SPRO SAP
Reference IMG)
Customer Relationship      Change View Partner      CRM
Management → Basic         Functions: Overview
functions → Partner
processing → Define
partner functions
General settings → Check   Units of Measurement:    CRM, R/3
units of measurement       Initial Screen
Enterprise Buyer         Change View Logical        CRM
Professional Edition →   Systems: Initial Screen
Technical Basic Settings
→ ALE Settings (Logical
System) → Distribution
(ALE) → Sending and
Receiving systems →
Logical Systems →
Define Logical System
Enterprise Buyer         Assign Client to Logical   CRM
Professional Edition →   System
Technical Basic Settings
→ ALE Settings (Logical
System) → Distribution
(ALE) → Sending and
Receiving Systems →
Logical Systems →
Assign Client to Logical
System
Enterprise Buyer         Display Distribution       CRM
Professional Edition →   Model
Technical Basic Settings
→ ALE Settings (Logical
System) → Distribution
(ALE) → Modeling and
Implementing Business
Processes → Maintain
Distribution Model and
Distribute Views
SAP Business to Business Change Definition of   CRM
Procurement → Technical Backend Systems in B2B:
Basic settings → Define Overview
(C) SAP AG                          ADM130                     10-21
backend systems
Enterprise Buyer            -                         CRM
Professional Edition →
Application Specific
Basic settings → Start
Application Monitors
Enterprise Buyer         Change View                  CRM
Professional Edition →   Customizing of the BBP
Technical Basic settings Basis System: Overview
→ Set Control Parameters
Enterprise Buyer            Change View               CRM
Professional Edition →      Determination of Target
Technical Basic settings    Systems using Product
→ Define Backend            Categories
System for Product
Category
Enterprise Buyer            Display View Action       CRM
Professional Edition →      Profile: Overview
Application Specific
Basic settings → Set
Output Actions and
Uutput Format → Define
Actions for Purchase
Order Output
Enterprise Buyer            Change View Define        CRM
Professional Edition →      Catalogs: Overview
Master Data → Define
catalogs
Enterprise Buyer            Change View                CRM
Professional Edition →      Maintenance of Objects to
Application Specific        be generated in the target
Basic Settings → Define     system
objects in backend system




(C) SAP AG                           ADM130                  10-22

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:439
posted:4/6/2012
language:Latin
pages:556