1 Overview 8 Backup&Recovery 2 Software Maintenance 9 Optimizer 3 Sizing&Platform 10 Performance 4 Interface 11 Others 5 APO&BW 6 CIF 7 liveCache

Basic Sizing Dependencies & Facts (1) Characteristic Combinations liveCache Main Memory The number of characteristic combinations is not the product of all products, locations, customers, and so on: Not all combinations are relevant for your planning run Key Figures liveCache Main Memory In the planning area, you can distribute your key figures between liveCache and BW InfoCube As of APO 3.0A, default is 100% key figures in liveCache Orders liveCache Main Memory DP Planning Versions liveCache Main Memory Do you really need all your versions in liveCache? You can also store versions in BW InfoCubes

Basic Sizing Dependencies & Facts (2) SNP Versions liveCache Main Memory Are you really using 100% copies of your active versions? Are all versions equally big? Are all users using all versions in parallel? Periods in Planning Horizon liveCache Main Memory Duration of Planning Run liveCache CPU Can you afford a bigger duration of your planning run? Retention Period Disk Optimizer : No. of Variables Optimizer Main Memory Optimizer : No. of Constraints Optimizer Main Memory Duration of Optimizer Run Optimizer CPU

T-Shirt Sizing (DB/Appl./LC) Small System Business Environment Recommended Sizing Install all APO components in one machine i) ii) based on 50 products, 10 locations, 10 customers planning run on detailed level where 1000 CC are planned. based on 5 components, 2 operations, 2 activities Central machine 300 SAPS(1-2 CPU) 1GB RAM 20GB HD

T-Shirt Sizing (DB/Appl./LC) Medium System Business Environment Recommended Sizing LC and Optimizer in separate machines. DB and Appl. Servers on the same server possible. i) ii) based on 500 products, 20 locations, 100 customers planning run on detailed level where 1000 CC are planned. based on 5 components, 2 operations, 2 activities DB and Appl. 1000 SAPS(4-6 CPU) 3GB RAM 50GB HD liveCache 500 SAPS(2-3 CPU) 4GB RAM 50GB HD Orientive rule of HD sizing liveCache Hard Disk = (2 to 4) x RAM space liveCache Dev Space = 2 x Data Cache

T-Shirt Sizing (DB/Appl./LC) Large System Business Environment Recommended Sizing LC and Optimizer in separate machines. DB and Appl. Servers on the same server possible. i) ii) based on 5000 products, 50 locations, 1000 customers planning run on aggregated level where 40000 CC on aggregated level are planned. based on 5 components, 2 operations, 2 activities DB and Appl. 2000 SAPS(8-10 CPU) 4GB RAM 50GB HD liveCache 1000 SAPS(4-5 CPU) 16GB RAM(50% for DataCache) 50GB HD Orientive rule of HD sizing liveCache Hard Disk = (2 to 4) x RAM space liveCache Dev Space = 2 x Data Cache

T-Shirt Sizing (DB/Appl./LC) XLarge System Business Environment Recommended Sizing LC and Optimizer in separate machines. DB and Appl. Servers on the same server possible. i) ii) based on 50000 products, 100 locations, 10000 customers planning run on aggregated level where 40000 CC on aggregated level are planned. based on 5 components, 5 operations, 5 activities DB and Appl. 5000 SAPS(>=20 CPU) 8GB RAM 300GB HD liveCache 4000 SAPS(>=16 CPU) 80GB RAM(50% for DataCache) 250GB HD Orientive rule of HD sizing liveCache Hard Disk = (2 to 4) x RAM space liveCache Dev Space = 2 x Data Cache

T-Shirt Sizing (Optimizer) Sizing Matrix Optimizer is not storage relevant. Faster CPU Better than More RAM

Sizing Consideration Based on QuickSizer Data Cache DevSpace 60 – 70% of physical RAM OMS History DevSpace At least 2 x physical RAM or minimum 3GB

APO GUI SAPGui Version Operating System CPU Clock Video RAM Version 6.10 above with APO Add-on SAPGui for Java – Not supported Operating System NT / W2K Strongly Recommended Problems with Windows 95/98 CPU Clock Minimum Pentium 133Mhz, Recommended 350Mhz Video RAM Minimum 2 MB, Recommended 4 MB Graphic intensive nature(1024 x 768, 32768 colors) Front-End Main Memory Minimum 64MB, Recommended 128 MB APO Known memory leak with Windows 95, lose GDI resources after several graphically intensive transactions, fix not available until version 4.6. Possible conflicts with other types of R/3 GUIs, traditional and Business Information Warehouse. There is no universal GUI available at this time. ActiveX controls (.ocx files) must be updated frequently for the graphical functions of APO. Check OSS and sapservx for the latest information and file downloads. The user must have local administrative rights to install the GUI if it is a Windows NT machine since the ActiveX controls must be located locally on the desktop machine. Recommended screen resolution: min. 1024x768 (with 4MB video memory). Recommended color palette: min. 32768 colors - better would be „True Color“. Tests show the performance of the front-end PC improves significantly with 4 MB VRAM as opposed to 2 MB, because of the graphic intensive nature of the APO GUI.

APO Platform APO Database & Application Server liveCache & Optimizer DB2/390 as DB server is supported as of APO 3.0A. OS/390 is only supported as DB server for APO 3.0A, not as application server. zLinux is currently not supported for SAP APO. For more details, please see SAP Note 0492641. OS/400 is NOT supported for any APO release also DB2/400.