Mysap Scm Master Guide on Sap Apo 3-1

Master Master Master Master GuideGuideGuideGuide

mySAPmySAPmySAPmySAPTMTMTMTM

SupplySupplySupplySupplyChain ManagementChain ManagementChain ManagementChain Management

Using SAPUsing SAPUsing SAPUsing SAP®®®® APO 3.1, SAP EM 1.1, APO 3.1, SAP EM 1.1, APO 3.1, SAP EM 1.1, APO 3.1, SAP EM 1.1,SAP R/3 4.6CSAP R/3 4.6CSAP R/3 4.6CSAP R/3 4.6C

Document Version 2.25 - August 22, 2002

Material Number 50052179

© Copyright 2002 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG.The information contained herein may be changed without priornotice.

Some software products marketed by SAP AG and its distributorscontain proprietary software components of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® andSQL Server® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®,MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries,pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®,Netfinity®, Tivoli®, Informix and Informix® Dynamic Server

TM are

trademarks of IBM Corp. in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1®, and Motif ® are registered trademarks ofthe Open Group.

LINUX is a registered trademark of Linus Torvalds and others.

Citrix®, the Citrix logo, ICA®, Program Neighborhood ®, MetaFrame®,WinFrame®, VideoFrame®, MultiWin® and other Citrix product namesreferenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registeredtrademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

J2EE™ is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc.,used under license for technology invented and implemented byNetscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP BusinessWorkflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE,Management Cockpit, mySAP, mySAP.com, and other SAP productsand services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and inseveral other countries all over the world. MarketSet and EnterpriseBuyer are jointly owned trademarks of SAP Markets and CommerceOne. All other product and service names mentioned are thetrademarks of their respective owners.

DisclaimerSome components of this product are based on Java™. Any codechange in these components may cause unpredictable and severemalfunctions and is therefore expressively prohibited, as is anydecompilation of these components.

Any Java™ Source Code delivered with this product is only to be usedby SAP’s Support Services and may not be modified or altered in anyway.

Documentation in the SAP Service MarketplaceYou can find this documentation at the following address:http://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguides

SAP AGSAP AGSAP AGSAP AGNeurottstraße 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.comwww.sap.comwww.sap.comwww.sap.com

Typographic Conventions

Type Style Represents

Example Text Words or characters that appear onthe screen. These include fieldnames, screen titles, pushbuttons aswell as menu names, paths andoptions.

Cross-references to otherdocumentation

Example text Emphasized words or phrases inbody text, titles of graphics andtables

EXAMPLE TEXT Names of elements in the system.These include report names,program names, transaction codes,table names, and individual keywords of a programming language,when surrounded by body text, forexample, SELECT and INCLUDE.

Example text Screen output. This includes file anddirectory names and their paths,messages, names of variables andparameters, source code as well asnames of installation, upgrade anddatabase tools.

Example text Exact user entry. These are wordsor characters that you enter in thesystem exactly as they appear in thedocumentation.

<Example text> Variable user entry. Pointedbrackets indicate that you replacethese words and characters withappropriate entries.

EXAMPLE TEXT Keys on the keyboard, for example,function keys (such as F2) or theENTER key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Contents

4 August 2002

ContentsContentsContentsContents

1 Getting Started ............................................................................. 51.1 Related Information......................................................................... 7

1.1.1 Related Documentation................................................................................................71.1.2 SAP Solution Manager .................................................................................................8

1.2 Important SAP Notes .................................................................... 101.3 History of Changes ....................................................................... 11

2 mySAP SCM Overview ............................................................... 122.1 Additional Business Scenarios.................................................... 202.2 Demand Planning Overview and Implementation...................... 21

2.2.1 Demand Planning Overview .......................................................................................212.2.2 Technical System Landscape for Demand Planning ...............................................222.2.3 Overview of Demand Planning Implementation Sequence .....................................23

2.3 Multilevel ATP Check Overview and Implementation................ 252.3.1 Multilevel ATP Check Overview .................................................................................252.3.2 Technical System Landscape for Multilevel ATP Check .........................................272.3.3 Overview of Multilevel ATP Check Implementation Sequence ...............................28

2.4 Outbound Order Fulfillment Overview and Implementation ..... 302.4.1 Outbound Order Fulfillment Overview ......................................................................302.4.3 Overview of Outbound Order Fulfillment Implementation Sequence ....................34

3 Software Components Overview............................................... 373.1 SAP Components .......................................................................... 37

3.1.1 Application Components ............................................................................................373.1.2 Technology Components............................................................................................40

3.2 Non-SAP Components.................................................................. 443.2.1 Windows Terminal Server...........................................................................................44

4 References: Related Implementation / Configuration Guides. 45

1 Getting Started

August 2002 5

1 Getting StartedThis documentation was developed to provide a central starting point for the technicalimplementation and upgrade of the solution mySAP Supply Chain Management (mySAPSCM) based on SAP Advanced Planner and Optimizer (SAP APO), SAP Event Manager(SAP EM) and SAP R/3. It contains all activities for installation and configuration of mySAPSCM.

mySAP SCM consists of the following business scenarios:

� Demand and Supply Planning

- Collaborative Supply & Demand Planning

- Sales Order Oriented Planning

- Vendor Managed Inventory with SAP APO and SAP R/3

- Procurement Scheduling Agreements in Heuristic-Based SNP

� Fulfillment

- Global Available-to-Promise

- Shipment and Transportation Scheduling

- Transportation Management

- Collaborative Transportation Planning

- Third-Party Order Processing with ALE

- Cross-System Flow of Goods

- Outbound Order Fulfillment

� Procurement

- Collaborative Management of Delivery Schedules (CMDS)

- Collaborative RFQ Process

� Supply Chain Performance Management

- Performance Measurement with KPIs

In this Master Guide, the business scenarios Demand Planning, Multilevel Available toPromise Check and Outbound Order Fulfillment are exemplary described in detail:

For more information about the other business scenarios listed above, see sectionAdditional Business Scenarios [page 20].

� Demand Planning (part of Collaborative Supply & Demand Planning)

The Demand Planning business scenario represents the cyclical Demand Planningprocess consisting of:

1. Order creation and invoicing in SAP R/3

2. Uploading the (initial or) updated data to SAP BW (included in SAP APO)

3. Demand Planning in SAP APO

4. Releasing the planning results back to SAP R/3

1 Getting Started

6 August 2002

� Multilevel Available to Promise Check (part of Global Available-to-Promise)

The multilevel ATP check (MATP) business scenario is usually used in industry areas inwhich large parts of the value-added activity arise at final assembly (for example, PCassembly). The components that are required to produce an end product are checkedwhen a sales order is created.

� Outbound Order Fulfillment

The Outbound Order Fulfillment (OBOF) business scenario deals with the fulfillment ofstandard sales orders with an emphasis on transportation management and follows theoverall process from the order entry to shipment cost processing. Deliveries areperformed with direct and/or multi-stop shipments on complete load (FTL) and/or partialload( LTL) trucks. With SAP Event Manager installed, they can be monitored andcontrolled all along the transportation process.

To facilitate the implementation and upgrade process, all information within this document isordered under scenario-based aspects. You can choose among several generic businessscenarios and find all the information that is relevant for the technical implementation of aspecific business scenario in an enclosed section. Upgrade information for businessscenarios is available in separate upgrade documentation that is referenced within the MasterGuide in the respective sections.

The mySAP SCM Master Guide provides the information about which components and whichguides are required during this process.

• In section Getting Started [page 5], you get valuable information about using thisdocument and related information (documentation and SAP Notes) crucial for theinstallation and upgrade.

• In section mySAP SCM Overview [page 12], a short introduction is given to mySAP SCMand to every business scenario in an enclosed subsection.

For the business scenarios Demand Planning and Multilevel Available to Promise Check,which are exemplary described in detail in this Master Guide, also the followinginformation is given:

− An overview of each business scenario including its technical components(mandatory and optional components).

− Examples of how the different components interact and what protocols and interfacesare used (technical infrastructure examples). Depending on the actual businessprocesses that have to be implemented and other aspects (such as security orperformance), the real infrastructure might be different.

− Information about the component's software releases.

− Information about the overall installation sequence and subsequent steps.

− References to related installation and configuration guides.

− References to scenario-based upgrade guides. These guides provide informationabout the overall upgrade sequences, references to related documentation, SAPNotes and additional upgrade information.

− Information about mutual dependencies that affect two or more components withinthe business scenario.

• In section Software Components Overview [page 37], you get a short description of everysoftware component that is part of mySAP SCM.

1 Getting Started

August 2002 7

• Depending on the specific business scenario and the number of processes to beimplemented, many different installation and configuration guides are required during thebusiness scenario implementation process. In section References: RelatedImplementation / Configuration Documentation [page 45], you can find an overview of allrequired documentation referenced in this Master Guide.

You can find the most current information about the technical implementation ofmySAP SCM and the latest installation and configuration guides in SAP ServiceMarketplace: http://service.sap.com/instguides

We strongly recommend that you use the documents that are available on thesepages. These guides are updated and enhanced on a regular basis.

1.1 Related InformationRelated DocumentationThe following list contains links to crucial information for implementing mySAP SCM.

List of Related Documentation

Content Location

• The latest version of the installationand upgrade documentation formySAP SCM

• Links to related SAP Notes

SAP Service Marketplace at:http://service.sap.com/instguides

Information about released platforms SAP Service Marketplace at:http://service.sap.com/platforms

Information about mySAP SCMTechnology (like architecture, platforms,performance, configuration, backup andrecovery, high-availability, availability ofSupport Packages, COM builds)

SAP Service Marketplace at:http://service.sap.com/scm � mySAP SCMTechnology.

Information about the integration ofmySAP SCM into the mySAP.comWorkplace

SAP Service Marketplace at:http://service.sap.com/instguides

In the folder mySAP.com Workplace, see thedocumentation mySAP.com Workplace <Release>Installation Overview.

Information about network security SAP Service Marketplace at:

• SAP Security Guide:http://service.sap.com/securityguide

• mySAP.com Workplace - Network Integration Guide:http://service.sap.com/network

http://service.sap.com/instguides

http://service.sap.com/platforms


http://service.sap.com/securityguide

http://service.sap.com/network

1 Getting Started

8 August 2002

Content Location

Online documentation (SAP Library) ofSAP APO, SAP liveCache, and SAP EM

SAP Help Portal at:http://help.sap.com

• SAP APO online documentation: Choose mySAP.comCross-Industry Solutions � mySAP Supply ChainManagement � SAP Advanced Planner & Optimizer.

• SAP DB / SAP liveCache online documentation: Youcan choose the online documentation of any SAP WebAS or SAP R/3 release as long as the SAP DB versionis the same as for mySAP SCM. For example, chooseSAP Web Application Server � SAP Web ApplicationServer 6.20.

• SAP EM online documentation: Choose mySAP.comCross-Industry Solutions � mySAP Supply ChainManagement � SAP Event Manager.

Information about BAPIs (BusinessApplication Programming Interface)

• SAP Interface Repository at:http://ifr.sap.com

• BAPI Strategy in the SAP Service Marketplace at:http://service.sap.com/BAPI

• Additional information on BAPIs in the SAP ServiceMarketplace at:http://service.sap.com/technology

SAP Solution ManagerIntroductionThe SAP Solution Manager is a crucial portal to assist you with the implementation andoperation of your mySAP.com solution.

The SAP Solution Manager integrates content, tools, and methodologies for implementationand operation. It helps you to visualize your business processes and graphically maps yoursolution landscape to give you a complete overview of your production environment. It helpsto ensure the operation of your core business processes by monitoring and alerting youbefore and when issues are encountered.

Important InformationThe SAP Solution Manager must be installed before the first TeamSAP Support service isdelivered. This applies specifically to SAP EarlyWatch Alert and SAP EarlyWatch.

The SAP Solution Manager software is not part of the mySAP Supply ChainManagement delivery.

You must order the SAP Solution Manager CD in SAP Service Marketplace andagree to the specified terms and conditions.

1 Getting Started

August 2002 9

Ordering Process

1. Enter the Alias /solutionmanager in SAP Service Marketplace.

2. Choose Get the SAP Solution Manager.

3. Follow the instructions to order the SAP Solution Manager CD or download it from theSoftware Center.

InstallationThe SAP Solution Manager is installed as an add-on to one of the following platforms:

- SAP Web Application Server 6.10 or higher

- SAP R/3 4.6C

- mySAP Workplace 2.11

SAP recommends that you install the SAP Solution Manager on a standalone system,especially if you want to monitor large landscapes.

You can find a detailed description on the installation process in the SAP SolutionManager installation guide which is available in SAP Service Marketplace (Alias/solutionmanager) and on the SAP Solution Manager CD.

1 Getting Started

10 August 2002

1.2 Important SAP Notes

Read the installation notes before beginning the installation. These notes contain themost recent information regarding the installation, as well as corrections to theinstallation documentation.

Make sure that you have the most recent version of each note. You can find the SAPNotes in SAP Service Marketplace (http://service.sap.com/notes) or byusing SAPNet - R/3 Frontend.

List of Related SAP Notes

SAP NoteNumber

Title Description

523886 SCEM 1.1: Add-OnInstallation on basis 6.20

This SAP Note contains the SAP EM Add-Oninstallation steps.

523885 Collected note for Add-OnSCEMSERV

This SAP Note contains all subsequent SAP Notesrelated to SAP EM.

523883 Release strategy for Add-On SCEMSERV

This SAP Note contains information about theavailability of the SAP EM Add-On.

515537 Installation/Delta upgradePI/PI-A 2002.1

436231 Installation/Delta upgradePI/PI-A 2001.2

The corresponding SAP Note is required to installthe SAP R/3 Plug-In. For more information, seeSAP Service Marketplace at:http://service.sap.com/r3-plug-in

431502 mySAP SCM Master Guide This SAP Note is crucial for the mySAP SCMinstallation. It contains:

• Any information relating to mySAP SCM thatwas not available when the Master Guide waspublished (for example, latest componentversion requirements),

• Corrections to this mySAP SCM Master Guide.

429400 Recommendations aboutPlanning Versions for SAPAPO DP

For efficiency reasons it is recommended not touse Planning Version 000 for your DemandPlanning run, especially if you are using furtherSAP APO applications like PP/DS, CTM or SNPtogether with DP.

196998 SAPGUI resources (APO):Hardware and software

Platform support & system requirements for theSAP GUI for SAP APO

66971 Supported frontendplatforms

Supported Microsoft Windows releases for thestandard SAP GUI.

http://service.sap.com/r3-plug-in

1 Getting Started

August 2002 11

1.3 History of ChangesThe mySAP SCM Master Guide is updated on a regular basis in SAP Service Marketplace(http://service.sap.com/instguides).

Make sure you have the latest version of the mySAP SCM Master Guide by checkingSAP Service Marketplace right before the installation.

The following table provides an overview on the most important changes that were madewithin the latest versions.

Master Guide Version Important Changes

V 1.00 (November 20, 2001). ---

V 2.00 (March 21, 2002). - Technical Infrastructure updated- List of business scenarios completed, link to

additional information addedV 2.10 (June 06, 2002). --

V 2.15 (August 02, 2002). - Business scenario Outbound Order Fulfillment(OBOF) added.

- Exemplary Technical Infrastructures for thebusiness scenarios updated.

V 2.20 (August 19, 2002). - System infrastructure information updated/added.- Software component list and installation

sequence of OBOF changed.- Exemplary Technical Infrastructures for the

business scenarios updated.V 2.25 (August 22, 2002). - SAP R/3 Enterprise 4.70 removed as mandatory

component of OBOF.- OBOF installation sequence updated.- Sections Technical System Landscape for

<Business Scenario> updated.


2 mySAP SCM Overview

12 August 2002

2 mySAP SCM OverviewmySAP Supply Chain Management (mySAP SCM) offers a user friendly, powerful andcompetitive solution which enables the modeling and optimization of the whole logistic chain.In the middle of this solution we have the SAP Advanced Planner and Optimizer (SAP APO).One of the big pillars on which the IT architecture of most business scenarios of the mySAPSCM solution is based is the secure, scalable and reliable SAP client-server-architecture,which consists of presentation client, application server and database server.

With the release of the SAP Event Manager (SAP EM) as a new component of the mySAPSCM solution, SAP delivers the backbone of its suite of applications for supply chain eventmanagement. This solution gives you now total supply chain visibility that encompassesinventory and assets, plans and schedules, and process events, thereby providing you withan accurate view of your entire network.

The following three SAP presentation clients are currently available. You can choose amongthem depending on your needs and the SCM business scenario you are implementing:

To see which Microsoft Windows releases are supported, please see SAP Note66971. For the SAP APO SAP GUI, usually the same Windows releases aresupported as for the standard SAP GUI. Exceptions would be documented in SAPNote 196998.

• The SAP GUI for the Microsoft Windows environment which can be locally installed orused through a Windows Terminal Server. This presentation client option is supported forall SCM business scenarios, including the ones based on SAP APO.

• The SAP GUI for the HTML environment which only requires the installation of a WebBrowser and ITS. This presentation client option is supported for all SCM businessscenarios, including the ones based on SAP APO.

To check which transactions are compliant with SAP GUI for HTML, call transactionSE93 in your SAP APO system.

• The SAP GUI for the Java environment which can be installed in non-Microsoft Windowsplatforms. This presentation client is presently supported for SAP R/3 but not for SAPAPO.


August 2002 13

mySAP SCM ComponentsThis section gives an overview of mySAP SCM and the components of its businessscenarios.

Please note that there are software requirements for each component below whichare not explicitly mentioned in this documentation. They are documented in therelevant installation guides. All related implementation guides are listed inReferences: Related Implementation / Configuration Guides [page 45].

See the SAP Note 431502 (mySAP SCM Master Guide) for latest component versionrequirements.

List of Software Components (X = mandatory / (X) = optional)

Business ScenarioSoftware Component

DemandPlanning

MultilevelAvailable to

PromiseCheck(MATP)

OutboundOrder

Fulfillment(OBOF)

SAP APO 3.1 (based on SAP Basis 4.6D) X X X

SAP BW 2.1C (embedded into SAP APO) X X --

SAP liveCache 7.4 for SAP APO X X X

COM Routines for SAP APO 3.1 (includedin the SAP APO installation)

X X X

SAP APO Optimizer 3.1 -- -- --

SAP EM 1.1 (Add-On for SAP WebApplication Server 6.20)

-- -- X

SAP EM 1.1 - Web Communication Layer -- -- (X)

SAP R/3 Plug-In ≥ 2001.2 X X --

SAP R/3 Plug-In ≥ 2002.1 -- -- X

SAP GUI for Windows ≥ 6.10 X X --

SAP GUI for Windows ≥ 6.20 -- -- X

SAP Internet Transaction Server ≥ 6.10 forSAP APO 3.1 (if you want to use SAP GUIfor HTML or SAP Workplace)

(X) (X) --

SAP Internet Transaction Server ≥ 6.20 forSAP EM 1.1 (if you want to use SAP GUIfor HTML or SAP Workplace)

-- -- (X)

Windows Terminal Server (X) (X) (X)


14 August 2002

Integration of SAP Systems (X = mandatory / (X) = optional)

Business ScenarioSAP System

DemandPlanning

MultilevelAvailable to

Promise Check(MATP)

OutboundOrder

Fulfillment(OBOF)

Additional SAP BusinessInformation Warehouse 3.0A(additional to the SAP BW 2.1Cembedded into SAP APO, seenote box below)

(X) (X) (X)

SAP Web Application Server(6.10 or higher)

(X) (X) (X)

SAP R/3 OLTP or non-SAP OLTP X

(SAP R/3 3.1I orhigher)

X

[SD, PP]

(SAP R/3 3.1I orhigher)

(X)

(SAP R/3 4.6Cor higher)

SAP Workplace (X) (X) (X)

SAP APO uses the embedded SAP BW architecture for planning technical reasons(such as using info cubes), that is, the SAP BW embedded in SAP APO is not meantto be used for the reporting purposes of your company. If you need SAP BW for yourbusiness requirements, you will need a separate SAP BW within your componentlandscape.


August 2002 15

System InfrastructurePlanning the Technical InfrastructureThe design of the technical infrastructure for your system determines to a large degree thecost-effectiveness of the implementation. You have to determine the requirements that yoursystem must fulfill.

The following questions can help you to identify the requirements that influence the design ofthe technical infrastructure most:

• Purpose of the system

− Is it a non-production system such as a demo system or is it a development or testsystem? (Development and test systems should also be considered as "production"systems in the sense that failure of a system could result in loss of money.).

− Or is it a "true" production system in the sense that your actual business processesrun in this system? (In the following, we will refer only to this kind of system as"production system".)

• Number of users

− How many users do you expect?

− Do you expect to be able to control the number of users (as in the case of a pureintranet scenario), or do you have no control over the number of users (as in the caseof an internet enabled “Outbound Order Fulfillment”)?

• Scalability

We recommend that you plan the system to be scalable right from the start. This way youcan react to increasing demands more easily without major redesigns.

• Availability

What are the availability requirements of the system? It is desirable to have as littledowntime as possible, but guaranteeing certain service levels (such as 99.9% uptime) iscostly.

• Security / Manageability

How do you assess the security risks of the system? Security is a requirement thatinfluences the infrastructure design quite heavily, because security considerations oftendemand exactly the opposite of what is required to retain the manageability of thesystem. For example, manageability would demand that you keep your software togetheras much as possible, while network security demands that you separate your softwareinto network segments connected only over firewall systems.

Some general design principles include keeping the system as simple as possible toensure manageability and being flexible so that you can modify the system in response tonew demands.

High AvailabilityTo make your system highly available, you need to set up at least two copies of eachsoftware component of the system, so that one component can take over when the other onefails. This does not necessarily mean that you have to double the hardware, but in practicethis is usually the case. You have to take great care not to omit any part of the software orhardware (servers, network, firewalls) from the high availability concept. If the failure of onecomponent causes the entire system to fail, that component is called a single point of failure(SPOF).


16 August 2002

Note that a high availability concept should also include planned downtimes for software andserver maintenance, upgrades and the possibility of software stability problems. We do notdiscuss these topics in depth here, but you should keep in mind implementing concepts tokeep these downtimes under control.

Exemplary Technical InfrastructuresThe following diagrams show exemplary technical infrastructures of SAP APO and SAP EM,two of the main components of mySAP SCM including their sub-components and thecommunication between them.

For a short description of every component, see section Software ComponentsOverview [page 37].

Technical Infrastructure of SAP APO

liveCache Server(1 per SAP APO System)

OptimizationServer

liveCacheMemory

liveCacheFile

System

SAP APO 3.1Central Instance

Message Server

RDBMS

SAP APO 3.1Dialog Instances

Work Processes

Work Processes

Native SQL

SAP GUI

Diag

RFC

RFC


August 2002 17

Technical Infrastructure of SAP EM

LEGACYLEGACY3rd Party3rd Party

Consignment

BA

PI

ResponseChannel

TrackFct.Application

Interface

Object 2 Object 3Object 1

SAP BWSAP BW

Report.Compl.

Exec.QualitySAP_ABA

4.6C

BAPI

EventManagerEventManager

EventController

Mapping

ControlChannel

RuleProcessor

ExpectedEvent

Monitor

EH

EHEHEH

BA

PIID

oc

EDIXML

Technical Systems

Mobile Devices

RF

InternetServices

Event Generators

EventProc.

EventChannel

InternetServices

BusinessSystems

Mobile Devices

Status Retrieval

mySAP.com


18 August 2002

IntegrationSAP APO

SAP APO is the main component of mySAP SCM. It is a standalone SAP System you canuse in a heterogeneous system environment. The SAP System or ERP backend systems canbelong to the system environment.

The SAP APO system is based on technologies such as the SAP Business Framework,which provide greater scalability and better performance. It communicates with the businessprocesses in the backend system using the Business Application Programming Interfaces(BAPIs).

Furthermore SAP APO can be fully integrated within mySAP.com landscapes via definedSAP interfaces. Standard integration between SAP APO and SAP R/3 is performed via CIF /SAP R/3-Plug-In. The basic underlying CIF technology is Remote Function Call (sRFC,qRFC, tRFC). Integration with non-SAP solutions is also supported, for instance via BAPIs,due to SAP's open interface strategy.

The SAP APO system can communicate with the following SAP backend system releasesand higher:• 3.1I• 4.0B• 4.5B• 4.6B• 4.6C

For an overview about which SAP R/3 and SAP R/3 Plug-In releases are supportedfor the different SAP APO releases, see SAP Service Marketplace at:http://service.sap.com/scm � mySAP SCM Technology, then choose on theWeb page Integration � SAP APO - SAP R/3 Integration � CIF & R/3 Plug-InDocumentation and SAP Notes � SAP R/3 Plug-In � Support Matrix for SAP R/3-SAP APO - Plug-In Combinations.

SAP EM

SAP EM is an additional component of mySAP SCM and running on the standard SAP WebApplication Server architecture: No additional architecture components are required.

SAP EM 1.1 is installed as application add-on to the standard SAP Web Application Server6.20 and also requires PI_BASIS ≥ 2002.1 SP4.

SAP EM includes connections to additional mySAP.com components, such as:

• SAP R/3 4.0B only as of PI2002.2



• SAP R/3 4.6C

• SAP R/3 Enterprise with SAP R/3 Enterprise Core 4.70

The SAP Event Manager is designed to manage events across the mySAP.com systemlandscape and is therefore meant to be integrated with various systems in the landscape. Wecan distinguish between different integration categories, depending on the purpose of the


August 2002 19

integration with SAP EM. At least the three integration categories listed below are required foran SAP Event Management Scenario :

• Integration between SAP EM and the Application System (AS) which generates an EventHandler on the SAP EM server.

• Integration between SAP EM and systems sending events to the SAP EM

• Integration between SAP EM and any other system with the purpose of routingmessages, workflows and alerts to this system

For more information, see SAP Service Marketplace at:http://service.sap.com/scm � mySAP SCM Technology � Installation,Upgrade Migration � SAP EM 1.1: Installation & Upgrade Information.


20 August 2002

2.1 Additional Business ScenariosIn this Master Guide, the business scenarios Demand Planning, Multilevel Available toPromise Check and Outbound Order Fulfillment are exemplary described in detail.

For more information about the other SCM business scenarios, see the SAP Library (chooseHelp � SAP Library in your SAP System or access the SAP Library at:http://help.sap.com � mySAP Cross-Industry Solutions � SAP APO Planner andOptimizer � SAP APO 3.1).


August 2002 21

2.2 Demand Planning Overview and ImplementationThe following topics are covered:

� Overview of the Demand Planning business scenario

� Technical system landscape

� Overview of implementation sequence

2.2.1 Demand Planning Overview

See the documentation Scenario Description Demand Planning for more information.

DescriptionThe demand is planned in SAP APO based on the current data situation available from SAPR/3. The results are provided to SAP R/3.

Example TasksThe main Demand Planning task is the creation of a forecast. This is typically done usingstatistical methods. The final demand plan has to take into consideration the current ordersituation.

Additional tasks are:

• Outlier detection

• Promotion Planning

• Life Cycle Management

• Collaborative Demand Planning

Process ChainThe Demand Planning process chain is cyclical and normally looks like this:

1. Orders are created and invoiced in SAP R/3.

2. To provide the historical data for the subsequent planning, the current situation isuploaded regularly to SAP BW (embedded into SAP APO).

3. Demand Planning is carried out in SAP APO.

4. The planning results are released to Supply Planning (SAP R/3 or SNP).


22 August 2002

2.2.2 Technical System Landscape for Demand PlanningThe following diagram shows exemplary the technical infrastructure of Demand Planningincluding its components and the communication between them.


Technical Infrastructure of Demand Planning

The following diagram shows a standard Demand Planning business scenario with an SAPAPO system, SAP liveCache and the backend OLTP system (SAP R/3). For reportingreasons, you can also connect an SAP BW system. It is also possible to integrate a non-SAPOLTP system instead of the SAP R/3 system into the Demand Planning business scenario.

Intranet Clients Demand PlanningCore System

BackendOLTP

SAP R/3SystemPlug-In

RDBMS

SAP BWSystem

3.0A

RDBMS

SAP APOSystem 3.1

RDBMSSAP GUI

for Windows / HTML

(OPTIONAL)

liveCache

Basis 4.6D

For the sake of simplicity and clearness the diagram contains icons for whole SAP systems,not for single hosts. Remember that every SAP system may consist of several hosts withdifferent tasks.

You can use the SAP GUI for Windows and the SAP GUI for HTML. The usage of SAP GUIfor Windows with Windows Terminal Server is also possible.

Use the internal features of the SAP Web Application Server to provide high availability andload balancing to the SAP APO, SAP R/3 and SAP BW system.

Redundant network infrastructure should be used to ensure availability of the service. Thisincludes all active and passive network devices. Some load balancing mechanisms, such asWindows Load Balancing Server (WLBS), have no SPOF by design. Other mechanismsavoid SPOF by redundancy.


August 2002 23

For information about:

• High availability options for the SAP Web Application Server and the SAP InternetTransaction Server, see SAP Service Marketplace at:http://service.sap.com/ti

• Load balancing for the Microsoft Terminal Services, seehttp://support.microsoft.com

• The different GUI types, see SAP Service Marketplace at:http://service.sap.com/ui

• General information about the technical infrastructure of mySAP SCM, see the sectionSystem Infrastructure [page 15].

2.2.3 Overview of Demand Planning Implementation SequenceThis section lists the sequence of steps (installation, technical configuration, applicationconfiguration) required to implement the business scenario.

Demand Planning Installation

• See the SAP Note 431502 (mySAP SCM Master Guide) for latest componentversion requirements.

• For documentation referenced in the following table, see section References:Related Implementation / Configuration Guides [page 45].

No Action[Corresponding Documentation]

Remarks andsubsequent Steps[CorrespondingDocumentation]

1 Make sure that the following prerequisites are met:

• SAP R/3 System 3.1I or higher installed.

• If you want to use the SAP GUI with a terminal server,Windows Terminal Server must be installed on your frontend hosts.

• SAP Solution Manager installed.

For more information , see section SAP Solution Manager[page 8].

/

http://service.sap.com/ti

http://support.microsoft.com/

http://service.sap.com/ui


24 August 2002



2 Installation of SAP APO 3.1.

[SAP APO Installation on <Operating System>: <Database>available in the SAP Service Marketplace at:http://service.sap.com/instguides]

Installation of therequired languages

[Language Transport(BC-CTS-LAN) availablein the SAP ServiceMarketplace at:http://service. \

sap.com/ \

instguides]

3 Installation of SAP liveCache 7.4 for SAP APO.

[SAP APO liveCache Installation available in the SAP ServiceMarketplace at: http://service.sap.com/instguides]

/

4 Installation of SAP Internet Transaction Server 6.10 (orhigher) for SAP APO (optional).

[SAP@Web Installation Guide located on the ServerComponents CD]

Install the SAP ITS if youwant to use the SAP GUIfor HTML or SAPWorkplace.

5 Installation of SAP GUI 6.10 (or higher) on every host fromwhere you want to connect to SAP APO via an SAP GUI.

[SAP Front End Installation Guide / SAP-Frontend-Installationsleitfaden located on the SAP Presentation CD]

/

6 Installation of SAP R/3 Plug-In 2001.2 (or higher) for SAPAPO:

See SAP Note 436231 (Installation/Delta upgrade PI/PI-A2001.2) and SAP Service Marketplace at:http://service.sap.com/r3-plug-in

/

For efficiency reasons it is recommended not to use Planning Version 000 for yourDemand Planning run, especially if you are using further SAP APO applications likePP/DS, CTM or SNP together with DP. Further details are available in the SAP Note429400 (Recommendations about Planning Versions for SAP APO DP).

Demand Planning UpgradeThe documentation Upgrade of the SAP Demand Planning Scenario to Release SAP APO3.1: Overview describes the steps to be carried out in an upgrade process from SAP APO 3.0to 3.1 to sustain the settings.

Demand Planning ConfigurationThe documentation Configuration Guide Demand Planning describes how to setup theDemand Planning business scenario manually in the corresponding systems.



August 2002 25

2.3 Multilevel ATP Check Overview andImplementationThe following topics are covered:

� Overview of the Multilevel ATP Check business scenario



2.3.1 Multilevel ATP Check Overview

See the documentation Business Scenario Description Multilevel ATP Check(English) or Business-Scenario-Beschreibung für Mehrstufige ATP-Prüfung (Deutsch)for more information.

DescriptionThere are industry areas (for example, PC assembly) in which a large part of the value-addedactivity arises at final assembly. The assemblies on the lower production levels have alreadybeen produced or procured before the sales order comes in, but final assembly is onlyinitiated when the sales order arrives.

The multilevel ATP check (MATP) is usually used in these areas, since the components thatare required to produce an end product are checked when a sales order is created.

A particularly suitable use of the multilevel ATP check is sales order entry for configuredproducts. A sales order can only be accepted when all required components are available.Which components are needed specifically, however, depends on the configurationrequested by the customer and can only be checked at the time of sales order entry.

Supported FunctionsThe multilevel ATP check supports the following functions:

• Scope of check in the product availability check for components

• Product allocation at finished product level

• Checking against the forecast at component level

• Mapping of capacities using product allocations

• Exclusion of specific components from the check (that is, complete confirmation of thecomponents without check)

• Return of data via the components/characteristic values that have lead to a delay and/orreduction of the confirmation (missing parts list)

• Rules-based ATP check at component level, whereby a location determination generatesa stock transport requisition, a product substitution, a product substitution order in PP/DS.

• Cross-system third-party order processing at finished product level, together withmultilevel ATP check


26 August 2002

Process ChainThe Multilevel ATP Check process chain normally looks like this:

SAP APOSAP R/3

Business System Group

ATP checkFinished product

Conversion ofATP

tree structure

Planned order/PReq

Create sales order

Planned order/PReq

Planned/Production order

PReq/PO

PP

SD

PP/DS

PP/DS

ATP

Planexplosion

&scheduling

ATP check forcomponents

1. step

Plan explosion &scheduling

ATP check forcomponents

2. step

Result

ATP tree structure

ATP

ATP

PP/DS

PP/DS

Temp.qty assgmtFinished product

Temp.qty assgmt

Components

Sales order

Save sales order

SD RequirementFinished product


August 2002 27

2.3.2 Technical System Landscape for Multilevel ATP CheckThe following diagram shows exemplary the technical infrastructure of Multilevel ATP Checkincluding its components and the communication between them.


Technical Infrastructure of Multilevel ATP Check

The following diagram shows a standard Multilevel ATP Check business scenario with anSAP APO system, SAP liveCache and the backend OLTP system (SAP R/3 or SAP CRM).

It is also possible to integrate a non-SAP OLTP system instead of the SAP R/3 or the SAPCRM system into the Multilevel ATP Check business scenario.

BackendOLTP

SAP CRMSystem

RDBMS

or

Intranet Clients Multilevel ATP CheckCore System


RDBMSSAP APOSystem 3.1

RDBMSSAP GUI

for Windows / HTML

liveCache

Basis 4.6D



Use the internal features of the SAP Web Application Server to provide high availability andload balancing to the SAP APO, SAP R/3 and SAP BW system.

Redundant network infrastructure should be used to ensure availability of the service. Thisincludes all active and passive network devices. Some load balancing mechanisms, such asWindows Load Balancing Server (WLBS), have no SPOF by design. Other mechanismsavoid SPOF by redundancy.


28 August 2002






2.3.3 Overview of Multilevel ATP Check ImplementationSequenceThis section lists the sequence of steps (installation, technical configuration, applicationconfiguration) required to implement the business scenario.

Multilevel ATP Check Installation






• SAP R/3 System 3.1I or higher installed.




/





August 2002 29







sap.com/ \

instguides]



/






/

6 Installation of SAP R/3 Plug-In 2001.2 (or higher) for SAPAPO:

See SAP Note 436231 (Installation/Delta upgrade PI/PI-A2001.2) and SAP Service Marketplace at:http://service.sap.com/r3-plug-in

/

Multilevel ATP Check ConfigurationThe Configuration Guide Multilevel Available To Promise Check describes how to setup thebusiness scenario manually in the corresponding systems.



30 August 2002

2.4 Outbound Order Fulfillment Overview andImplementationThe following topics are covered:

� Overview of the Outbound Order Fulfillment business scenario



2.4.1 Outbound Order Fulfillment Overview

See the documentation Scenario Description Outbound Order Fulfillment for moreinformation.

DescriptionThe scope of the Outbound Order Fulfillment (OBOF) business scenario is the shipment ofgoods from a manufacturing company to customers using LTL (less than truckload) and FTL(full truckload) trucks (partial and complete load) which belong to different carriers.

With the integration of the SAP Event Manager the ability to perform supply chain eventmanagement is added, which implies managing of information over heterogeneous systemsand multiple tiers at every stage of the transportation process. Hereby the individualdeliveries per shipment (direct and/or multi-stop) can be monitored and controlled by thesupplier.

Supported Functions• Order creation with real-time availability check

• Interactive Vehicle Scheduling: based on the customer orders (manual or automatic),creation of a shipment plan by the TP/VS (Transportation Planning / Vehicle Scheduling)optimizer

• Consideration of individual constraints such as

− Vehicle capacity

− Limits on distance, duration and stopovers

− Capacity of handling resources

• Carrier selection including determination of transportation service provider

• OLTP transfer of deliveries and shipments

• Monitoring of deliveries

• Pick and post goods issue

• Shipment execution and costing


August 2002 31

Process ChainThree major SAP components together form this solution: Planning is done in SAP APO,SAP R/3 controls the execution part and SAP EM delivers to you supply chain visibility.

Shipper

EMAPOR/3

Create order

Create deliveries

Create shipments

Pick & Load

Shipment Costing

Check availability

Plan shipments

Select TSP

Event handlerfor shipment

Updateevent handler


32 August 2002

2.4.2 Technical System Landscape for Outbound OrderFulfillmentThe following diagram shows exemplary the technical infrastructure of Outbound OrderFulfillment including its components and the communication between them.


Technical Infrastructure of Outbound Order Fulfillment

The following diagram shows a standard Outbound Order Fulfillment business scenario withan SAP APO system, SAP liveCache, SAP EM and the backend OLTP system (SAP R/3 orSAP CRM).

It is possible to integrate a non-SAP OLTP system instead of the SAP R/3 or the SAP CRMsystem into the OBOF business scenario. You may also integrate other backend systems likeSAP BW or existing SAP R/3 systems.

Outbound OrderFulfillment - Core System

Intranet Clients BackendOLTPSAP APO

System 3.1

RDBMS

Web Browser

Fire

wal

lSAPWeb

DispatcherFire

wal

l

DMZ

RDBMS

liveCacheSAP GUIfor Windows / HTML


RDBMS

Basis 4.6D

Basis WAS 6.20

SAP EMWCL

SAP J2EE Engine

(OPTIONAL)

SAP EM

Internet Clients(OPTIONAL)


The optional SAP EM - WCL can either run on the SAP J2EE Engine of the SAP EM server(as shown in the graphic) or on a standalone SAP J2EE Engine.

For security reasons we recommend to build a Demilitarized Zone (DMZ) for internet use.Place an SAP Web Dispatcher or a reverse proxy in the DMZ to deny direct access from theinternet to the SAP EM system.


August 2002 33


Use the internal features of the SAP Web Application Server to provide high availability andload balancing to the SAP APO and SAP EM system.

Redundant Internet connections and network infrastructure should be used to ensureavailability of the service. This includes firewalls and load balancing devices. Some loadbalancing mechanisms, such as Windows Load Balancing Server (WLBS), have no SPOF bydesign. Other mechanisms avoid SPOF by redundancy. For simplicity, only single firewallsare shown in the graphic, although redundancy is required here, too.










34 August 2002

2.4.3 Overview of Outbound Order Fulfillment ImplementationSequenceThis section lists the sequence of steps (installation, technical configuration, applicationconfiguration) required to implement the business scenario.

Outbound Order Fulfillment Installation









/





sap.com/ \

instguides]



/





August 2002 35





/

6 Installation of SAP R/3 Plug-In 2002.1 SP02 (or higher) forSAP APO.

See SAP Note 515537 (Installation/Delta upgrade PI/PI-A2002.1) and SAP Service Marketplace at:http://service.sap.com/r3-plug-infor more information.

/

7 Installation of SAP EM 1.1:

SAP EM 1.1 can be installed:

• As separate system or

• As add-on to an existing SAP Web AS 6.20 or

• As add-on to an existing SAP R/3 Enterprise system withSAP R/3 Enterprise Core 4.70 (based on SAP Web AS6.20).

Note that an SAP EM 1.1 installation is not supportedas add-on to further mySAP.com components apartfrom SAP Web AS 6.20 and SAP R/3 Enterprise (thatis, you cannot install SAP EM 1.1 on top of, forexample, SAP APO, SAP BW or SAP CRM).

In case of high data volume (for example, high amountof events, event handlers and messages) it is stronglyrecommended to install SAP EM 1.1 as a separatesystem.

To install SAP EM, perform the following steps:

1. If you want to install SAP EM as separate system, installSAP Web AS 6.20.

[Installation Guide - SAP Web Application Server 6.20 on<Operating System>: <Database> available in the SAPService Marketplace at:http://service.sap.com/instguides]

2. Install the SAP EM Add-On.

[See SAP Note 523886]

/



36 August 2002



8 Installation of SAP Internet Transaction Server 6.20 (orhigher) for SAP EM (optional).


Install the SAP ITS if youwant to use the SAP GUIfor HTML.

9 Installation of SAP GUI 6.20 (or higher) on every host fromwhere you want to connect to SAP EM via an SAP GUI.


/

10 Installation of SAP R/3 Plug-In 2002.1 SP02 (or higher) forSAP EM.

See SAP Note 515537 (Installation/Delta upgrade PI/PI-A2002.1) and SAP Service Marketplace at:http://service.sap.com/r3-plug-infor more information.

/

11 Installation of SAP EM 1.1 - Web Communication Layer(optional).

[Installation Guide - SAP Event Manager - WebCommunication Layer available in the SAP ServiceMarketplace at: http://service.sap.com/instguides]

/

Outbound Order Fulfillment ConfigurationThe documentation Configuration Guide Outbound Order Fulfillment describes how to setupthe business scenario manually in the corresponding systems.


3 Software Components Overview

August 2002 37

3 Software Components OverviewThis section provides additional information about the most important mySAP SCM softwarecomponents.

3.1 SAP Components3.1.1 Application ComponentsOLTP SystemDefinitionOnLine Transaction Processing System (for example, SAP R/3 Enterprise system) that isused in the mySAP SCM environment as backend system. It is used for materialsmanagement and financials.

UseData is exchanged between the SAP APO system and a connected OLTP system.

If an SAP R/3 Enterprise system is used as OLTP system, the SAP R/3 Plug-in supports dataexchange in an SAP APO component.

Integration with other SAP components such as SAP BW is realized with data extractors.

SAP Advanced Planner and OptimizerSAP Advanced Planner and Optimizer (SAP APO) is part of the mySAP Supply ChainManagement solution suite. It is an advanced planning and scheduling tool that enables real-time decision support and collaborative network optimization across the extended supplychain. SAP APO helps companies synchronize supply chain activities with their partners andexcel at customer service and order fulfillment.

SAP APO OptimizerSAP has developed an innovative and flexible APS optimization solution which opens SAPAPO's advanced planning and scheduling capabilities to external optimization technology:The Optimization Extension Workbench. This strategy enables mySAP SCM customers totake advantage of both the mySAP SCM existing set of optimizers and company-specificoptimization software. The optimization technology integrates different planning methods inone planning system to fulfill optimization requirements:

• Optimizers, guided by global objective function based on key performance indicators. Incase of highly complex planning scenarios, optimization results improve with increasingCPU time.

• User specific optimizers, external optimizers. External optimizers can be called from theSAP APO, also as batch job.

SAP APO Optimizer can be used for Detailed Production Scheduling, Supply NetworkPlanning, Transportation Planning and Vehicle Scheduling, Sequencing.

SAP APO Optimizer is optional or not part of the SCM business scenarios.


38 August 2002

For example, SAP APO Optimizer is not part of Dynamic Pricing, Multilevel ATPCheck and Outbound Order Fulfillment.

SAP Business Information WarehouseDefinitionSAP Business Information Warehouse (SAP BW) is a powerful, flexible data-warehousingsolution that gathers and refines information from internal and external sources. It containsthe following components:

• Business Content

A broad range of predefined reporting templates geared to the specific needs of particularuser types

• Business Explorer

A powerful analysis and reporting interface

• Administrator Workbench

Tool for controlling, monitoring and maintaining all the processes involved in dataprocurement and processing within the Business Information Warehouse

UseFor mySAP SCM, there are two options to integrate SAP BW:

Embedded SAP BW

SAP APO is shipped with an embedded SAP BW 2.1C which, together with the liveCache,contributes to efficiently perform Demand Planning tasks.

SAP APO uses the embedded SAP BW architecture for planning technical reasons(such as using info cubes), that is, the SAP BW embedded in SAP APO is not meantto be used for the reporting purposes of your company.

Separate SAP BW

If you need SAP BW for your business requirements, you will need a separate SAP BWwithin your component landscape.

SAP BW 3.0A provides both operational and strategic analyses:

• For operational analysis, the data is provided on individual document level with documentheader and document item information. ODS (operation data storage) objects forpurchase orders, confirmations, invoices, contracts, bid invitations, and bids have beendefined on the basis of ODS technology of the BW.

• Data is provided on aggregated level for strategic analysis. It is possible to analyze dataaggregated according to time, vendor, product, and product category, as well asaccording to account assignments. The InfoCubes defined for this are supplied with theinformation from the ODS objects.


August 2002 39

SAP Event ManagerDefinitionStandalone or integrated component of the SAP R/3 system that offers the possibility toprocess application objects in various application systems and thereby to track events forindividual objects, processes or parts of these throughout the entire supply chain.

UseThe SAP Event Manager (SAP EM) can link, update and evaluate the event messages withthe application data from the supply chain network.

It allows you to:

• Monitor, measure and evaluate business processes

− The SAP Event Manager automatically monitors events that occur and those thathave not been reported (for example, goods issue, purchase order transfer,production end, or unreported proof of delivery).

− The SAP Event Manager can automatically transfer data to a data warehouse systemthat uses key performance indicators to create performance data for the quality ofexecution and notification.

• Employ checking processes and notify persons responsible to control events

− The SAP Event Manager checks the Supply Chain Event Management-relevantobjects as soon as they are saved in the application system.

− The SAP Event Manager can automatically inform the decision maker in criticalsituations that action is required (for example, automatic re-scheduling of thesubsequent process step when a delay has occurred).

• Exchange and query information between partners (for example, e-mail or Internet)

SAP EM - Web Communication LayerSAP front end which offers information access and full supply chain visibility for SAP EM viathe internet.


40 August 2002

3.1.2 Technology ComponentsSAP Basis / SAP Web Application ServerDefinitionSAP Web Application Server (SAP Web AS) provides the technological foundation for allother mySAP.com components. In a sense, SAP Web Application Server is the "operatingsystem" of mySAP.com. Until SAP R/3 4.6D, SAP Web Application Server was named SAPBasis.

In the past, SAP Basis was used and shipped exclusively as an integral part of SAP R/3. Thiswas also reflected by the fact that SAP Basis and SAP R/3 had identical release names andshared Support Packages.

With the introduction of mySAP.com, SAP now offers multiple components that build on SAPWeb Application Server. As a result, there is no tight naming relation between SAP WebApplication Server and SAP R/3 any more.

An SAP System consists of a database server, (optional) additional application servers, and anumber of front end computers.

The database server is the computer on which the database is installed. This server can alsoaccommodate the central instance (the SAP instance that includes the message server andenqueue server processes). If the central instance is installed on a separate applicationserver, the database server is called a standalone database server.

Additional dialog instances (SAP instances including only dialog, batch, spool, or updateprocesses) are installed on application servers.

UseBesides that SAP APO is based on SAP Basis 4.6D, it is also possible to integrate an SAPWeb Application Server into your mySAP SCM landscape.

SAP Web Application Server provides a platform for quickly developing and deployingdynamic and collaborative Web applications or other thin-client applications (WAP, PDA, andso on) and includes all proven SAP programming models and technologies. With SAP WebApplication Server, SAP natively supports open Internet standards, including such protocolsas HTTP, HTTPS, and SMTP, as well as Internet document standards like HTML and XML.

Open integration capabilities provide access to existing SAP and non-SAP applications. Allintegration facilities supported by SAP are available with SAP Web Application Server. TheJava Connector or the DCOM Connector give ABAP applications access to Java or .NETcomponents and vice versa. In addition, the Internet Communication Framework (ICF) ofSAP Web AS enables ABAP-written programs to process and distribute HTTP requestsdirectly. As a consequence, SAP Web Application Server can serve both as an HTTP serverand client. It serves as an HTTP server for bringing applications to the user via a Webbrowser either directly or via a standard Web server. It serves as an HTTP client to accessother Web applications for collecting information and data. To complete Web connectivity,SAP Web AS provides full support for sending and receiving e-mails via SMTP.

In the moment, SAP Web Application Server is not a replacement for the SAP ITS. Ifyou want to use SAP GUI for HTML or SAP Workplace, SAP Internet TransactionServer is still required.


August 2002 41

SAP GUIGenerally, the latest release of the SAP GUI software (such as SAP GUI 6.20) can be usedwith all previous SAP R/3 releases (such as 4.0B). As a result, older SAP systems can alsobenefit from the features that are only available in the newer SAP GUI releases - for example,the look and feel of EnjoySAP and support for Windows 2000.

The benefit of this downward compatibility is that you can simply install a new SAP GUIrelease instead of patching an old one. The SAP GUI maintenance strategy takes advantageof this feature. In many problem situations, the recommendation is to install a new SAP GUIrelease, because patches cannot always be provided for older SAP GUI releases even if SAPstill maintains the SAP R/3 System with the same release number.

The SAP front end software release must always be at least the same as SAP R/3. Forexample, you cannot use SAP GUI 3.1I with SAP R/3 4.0B.

SAP Internet Transaction ServerDefinitionThe SAP Internet Transaction Server (ITS) combines existing Internet technology with SAPtechnology and provides reliable access to SAP functions from the Internet or intranets.

The ITS is a gateway between one or more Web servers and one or more SAP applicationservers. Typically, the Web server is an HTTP server, but other protocols such as FTP orGopher may also be supported. It allows interactive Web access to the SAP System.

The following graphic shows how the ITS extends the three-tier client/server architecture ofthe SAP System for Internet use:

SAPSAPapplicationapplication

serverserver

SAPSAPdatabasedatabase

serverserver

InternetInternetTransactionTransactionServer (ITS)Server (ITS)

WebWebserverserver

WebWebbrowserbrowser

Request

Response

The ITS manages all requests and responses between a Web browser client and an SAPSystem server.

UseFor mySAP SCM, SAP Internet Transaction Server is required if you want to use SAP GUI forHTML or SAP Workplace.

Internet Application Components (IAC) require an ITS to make the functionality available toInternet users using a Web server.


42 August 2002

The conventional method of accessing the SAP System interactively is by using the SAPGUI, which displays SAP transaction screens and allows the user to interact directly with thesystem. It communicates with the SAP System by using a special SAP GUI protocol.

To access the SAP System with a Web browser, you need an additional component to makethe connection between SAP technology (SAP Application Servers, SAP GUI) and Webtechnology (Web servers and browsers). This is accomplished by the ITS. It is merely apresentation front end and does not do any transaction processing itself. Instead, it hands allbusiness processing to the SAP System.The ITS consists of two separate programs: WGate (Web Gateway) and AGate (ApplicationGateway), which may be on the same host or on separate hosts connected by a TCP/IPnetwork. The graphic below shows the ITS components and the communication protocolsused between them:

HTTP

WebBrowser

SAPSystem

SAP GUIRFC

WebServer W

Gat

e(W

eb G

atew

ay)

AGate(Appl. Gateway)

ITS

ISAPINSAPI

CGITCP/IP

SAPSystem

SAP liveCacheliveCache for SAP APO

liveCache is based on SAP DB technology and ensures the highest mySAP SCMperformance. liveCache is SAP's state of the art memory based computing technology forreal-time, high speed processing of very large data volumes. The main capabilities of SAP'snew memory-resident object oriented technology are the following:

• Application logic execution right where the data is stored in order to avoid network load.

• Aggregation of relational data structures retrieved from the database into applicationspecific, optimized data representations in main memory. As a result optimization andplanning tasks can be performed in minutes or seconds.

• Built-in business functionality in form of C++ object methods.

• Semantic synchronization with the SAP database.

• Ready to exploit 64-Bit technology.

For more information concerning liveCache technology infrastructure, requirements andperformance recommendations, see the SAP Service Marketplace athttp://service.sap.com/scm.

liveCache is available on Windows 2000 (or higher) and on 64-Bit UNIX (as of SAP APO3.0A).

liveCache is a required SAP APO architecture component.

For every SAP APO system, exactly one liveCache is required.


August 2002 43

COM Routines for SAP APO

ABAP Programs and the SAP APO optimizers use native SQL for communicating through thestandard SAP database interface to liveCache. liveCache has an SQL interface that is usedto communicate with the SAP instances. With native SQL, ABAP programs call storedprocedures in the liveCache that point to Component Object Model (COM) routines written inC++. An SQL class provides access from the COM routine to the SQL data.

The COM routines are part of a dynamic link library that runs in the process context of theliveCache instance.

The COM routines have direct access to the objects stored in the liveCache and canmanipulate them. This manipulation includes creation and deletion of objects in theliveCache.

SAP R/3 Plug-InsDefinitionSAP R/3 Plug-Ins are interfaces, which enable the exchange of data between one or severalSAP R/3 systems and other mySAP.com components. The SAP R/3 Plug-Ins supply themySAP.com components with transaction data and master data in real time. They also makeit possible to use mySAP.com application components like SAP APO or SAP CRM togetherwith certain mySAP.com industry-specific components. All mySAP.com industry-specificcomponents based on SAP R/3 4.6B or higher SAP R/3 releases require SAP R/3 Plug-Ins.

SAP R/3 Plug-Ins are add-ons to SAP R/3.

SAP R/3 Plug-Ins are shipped with mySAP.com application components (SAP APO, SAPBW, SAP BBP, EBP, SAP CRM, and SAP SEM) as well as with mySAP.com industry-specificcomponents based on SAP R/3 4.6B or higher SAP R/3 releases. Customers can order themost recent SAP R/3 Plug-In releases free of charge or download them from the SAP ServiceMarketplace.

UseFor SAP R/3 3.1I up to 4.5B, there are two versions of each SAP R/3 Plug-In release, a PIversion and a PI-A version. For SAP R/3 4.6B and 4.6C, only PI is available. PI-A is a subsetof PI and contains interfaces for SAP BW and SAP BBP 1.0B. For SAP R/3 3.1I, a PI-Aversion also supports SAP BBP 2.0B and Enterprise Buyer 2.0, as well as SAP CRM InternetSales. The PI version supports SAP BW, SAP BBP/Enterprise Buyer, SAP APO, SAP CRM,and SAP SEM.

For SAP R/3 3.1I, the PI versions of the SAP R/3 Plug-In releases are modifying, whichmeans that they modify SAP R/3 standard objects, and therefore require Conflict ResolutionTransports (CRTs) for their installation. For SAP R/3 4.0B to 4.6C, the PI versions of the SAPR/3 Plug-Ins are non-modifying.

The PI-A versions of the SAP R/3 Plug-In releases are generally non-modifying.

Depending on the combination of the SAP R/3 Plug-In release and version and the SAP R/3release, certain SAP R/3 Support Package levels are required to install the SAP R/3 Plug-In.

For more information and for download, see SAP Service Marketplace(http://service.sap.com/r3-plug-in).


44 August 2002

3.2 Non-SAP Components3.2.1 Windows Terminal ServerDefinitionWindows Terminal Server Edition from Microsoft is a multi-user capable application-serverbased on Windows NT 4.0.

UseWindows Terminal Server (WTS) offers the possibility to run and to administrate all programsrunning on Windows NT4.0 on a central server. Front ends are nearly unaffected by thehardware and local performance is secondary, because applications are displayed on yourscreen, but executed on the Windows Terminal Server.

For mySAP SCM, WTS is an optional component to reduce the network load of the SAP GUI.

4 References: Related Implementation / Configuration Guides

August 2002 45

4 References: Related Implementation /Configuration GuidesList of additional implementation and configuration documentation for mySAP SCM.

Relevant for whichBusiness Scenario

X = mandatory / (X) =optional

Title Purpose Where to find

Dem

and

Plan

ning

Mul

tilev

elA

TP C

heck

Out

boun

dO

rder

Fulfi

llmen

t

BusinessScenarioDescriptionMultilevel ATPCheck (English)

Business-Scenario-Beschreibung fürMehrstufige ATP-Prüfung(Deutsch)

Detaileddescription ofthis businessscenariodescription.

SAP Service Marketplace at:http://service.sap.com/ibc

� ...for mySAP SCM

-- X --

ConfigurationGuide DemandPlanning

Setting up theDemandPlanningbusinessscenariomanually inthecorrespondingsystems.



X -- --

ConfigurationGuide MultilevelAvailable ToPromise Check

Setting up theMultilevel ATPCheckbusinessscenariomanually inthecorrespondingsystems.



-- X --

ConfigurationGuide OutboundOrder Fulfillment

Setting up theOBOFbusinessscenariomanually inthecorrespondingsystems.



-- -- X


46 August 2002




Dem

and

Plan

ning

Mul

tilev

elA

TP C

heck

Out

boun

dO

rder

Fulfi

llmen

t

Installation Guide- SAP EM - WebCommunicationLayer

Installing theSAP EM -WebCommuni-cation Layer.

SAP Service Marketplace at:http://service.sap.com/ \

instguides

-- -- (X)

Installation Guide- SAP R/3Enterprise on<OperatingSystem>:<Database>

Installing theSAP R/3Enterpriseserver.


instguides

-- -- (X)

Installation Guide- SAP WebApplicationServer 6.20

Installing theSAP WebApplicationServer.


instguides

-- -- (X)

LanguageTransport (BC-CTS-LAN) 6.20

Installingrequiredlanguages.


instguides

X X X

SAP APOInstallation on<OperatingSystem>:<Database>

Installing theSAP APOsystem.


instguides

X X X

SAP APOliveCacheInstallation

Installing theSAP APOliveCache.


instguides

SAP Front EndInstallation Guide(English)

SAP-Frontend-Installations-leitfaden(Deutsch)

Installing anSAP GUI.

SAP Presentation CD X X X

SAP@WEBInstallation Guide

Installing andconfiguring theSAP InternetTransactionServer (ITS).

Server Components CD-ROM (X) (X) (X)


August 2002 47




Dem

and

Plan

ning

Mul

tilev

elA

TP C

heck

Out

boun

dO

rder

Fulfi

llmen

t

ScenarioDescriptionDemandPlanning




X -- --

ScenarioDescriptionOutbound OrderFulfillment




-- -- X

Upgrade of theSAP DemandPlanningScenario toRelease SAPAPO 3.1:Overview

Describing thesteps in anupgradeprocess fromSAP APO 3.0to 3.1 tosustain thesettings.


instguides

X -- --

Mysap Scm Master Guide on Sap Apo 3-1

Documents

Transcript of Mysap Scm Master Guide on Sap Apo 3-1