Upload
rafaelsi
View
12
Download
5
Embed Size (px)
DESCRIPTION
IT SAPSD Performance
Citation preview
SAP SD Performance Tuning- Xbox and the Need for Speed -
Christoph Schuler, Cindi McCutchenSAP Application SupportMicrosoft Corporation
Agenda
SAP at Microsoft – Quick FactsSAP at Microsoft – Quick Facts• Why Performance Tuning• SAP Service Offerings• Project Approach & Best Practices• Tuning for Xbox
– Changes Implemented– Summary of Results– Lessons Learned
• Modules implemented:SD, MM, FI, CO, AM, HR, BW, APO
• 875 GB in a single, central Database; 6 GB/wk growth
• 2,000 named users; 50,000+ total users• > 600 concurrent users; heavy EDI usage• 0.5 - 2 sec response time globally
(incl. WAN connectivity)• 99.9+% availability• Platform: SQL Server 2000, Windows .NET
server
SAP at MicrosoftQuick Facts
Why Performance Tuning ?
• Business need for data throughput– Xbox Launch North America, Nov. ’01:
Peak volumes Existing XboxXbox ChangeSales orders / day ~ 5,000 + 7,600+ 7,600 + 152 %Deliveries / day ~ 5,000 + 11,400+ 11,400 + 228 %Sales orders / hour * ~ 250 + 2,500+ 2,500 + 1,000 %Deliveries / hour * ~ 1,000 + 2,500+ 2,500 + 250 %* Each order & delivery with 10 line items
Why Performance Tuning ?
• System availability & supportability– Prevention of:
• Cross-module increase in response time• Business disruptions• Penalties• End user frustration• Increased support costs
• System scalability– Ability to handle future growth
SAP Service Offerings
Focus on critical SD business processes 50+ recommendations to improve performance
InterfaceInterface Management Management
Technical Solution Optimization (TSO)Technical Solution Optimization (TSO)Now: Solutions Management Optimization (SMO)Now: Solutions Management Optimization (SMO)
Business ProcessBusiness ProcessOptimizationOptimization
Data Mgmt. &Data Mgmt. &ArchivingArchiving
Jun ‘00:• EDI Interface• GBI Interface
Sep ‘00:• Sales Orders• Backorder Resch.• Deliveries• Billing
Oct ‘00:• FI Archiving
Project Approach
• Project team– Functional – Basis/Technical– Development– Stress Test– Consulting (BUIT & SAP)
• Project timeline– Driven by business need
• Repetitive cycle– One item at a time
• Project metrics– e.g. seconds/document
Analysis
Test
Change
TestBest Practices• Have an original baseline test• Automate tests and standardize your
data & configuration• Include anticipated new functionality
(e.g. routing, allocations)• Consider systems external to SAP• Make test as realistic as possible !
Analysis
Test
Change
AnalysisBest Practices• Define your metrics (e.g. sec/doc,
response time, etc..)• Carefully document results and
improvements with each cycle• Review results and plan for next
changes to be implemented and tested
Analysis
Test
Change
AnalysisUseful Tools & Transactions
• Systemwide work process overview – SM66• Workload monitor – ST03• SQL trace - ST05• SQL trace interpreter - SQLR• Application analysis – ST14• Table access statistics – ST10• Memory configuration monitor – ST02• R/3 OS monitor – ST06• IDoc monitor – WE05• Gateway Monitor - SMGW• Windows PerfMon – CPU utilization
Analysis
Test
Change
AnalysisProcess Overview - SM66
• Quick overview of all work processes• Look for:
– Long-running processes– “Stopped” processes– Highly utilized servers– Processes accessing the same tables
Analysis
Test
Change
AnalysisDatabase Trace - ST05
• Important tool to analyze database performance problems
• Look for:– Most “expensive” database accesses
(Trace Summary)– Repetitive database accesses
Analysis
Test
Change
ChangeBest Practices
• Changes may include:– OSS notes
(> 2,600 performance notes for 4.5B)– ABAP code optimization– Configuration – Technical settings– Hardware– Business process or logic
• Carefully document changes made
Analysis Change
Agenda
• Why Performance Tuning• SAP Service OfferingsSAP Service Offerings• Project Approach & Best PracticesTuning for Xbox
– Changes Implemented– Summary of Results– Lessons Learned
Microsoft (SAP System)
Tuning for Xbox
SalesSalesOrderOrder
Distribution Distribution WarehouseWarehouse
Sales Order(EDI 850)1
RetailerRetailer
Tuning for Xbox1 – Sales Order Processing• Switch to parallel processing of
inbound IDocs Partner profile change: ’Immediate’ to
‘Background’ (via WE20) Server group configuration with resource
parameters (via RZ12) –OSS 384971 Schedule program RBDAPP01 Specify packet size and ‘Parallel’ posting option
• Deactivate IDoc syntax check• Increase of program buffer
Tuning for Xbox1 – Sales Order Processing• SD number range buffering
Table NRIV - Object RV_BELEG (via SNRO) Local buffering by work process ID Exclusion of sales orgs (OSS note 424486)
• ABAP code improvements VA01 user exits Elimination of repetitive table reads
• Table buffering Monitor access statistics (via ST10)
Tuning for Xbox
SalesSalesOrderOrder
2Rescheduling
RetailerRetailer
Sales Order(EDI 850)1
Distribution Distribution WarehouseWarehouse
Microsoft (SAP System)
Tuning for Xbox2 - Backorder Rescheduling• Cleanup of old orders• Program SDV03V02 by plant – daily
Evaluation of program SDV03V01• Modification (repair) of SDV03V02
Due to SD number buffering Take order creation date & time into account
• Custom pre-processing program Dynamic job builder and distribute workload over
several processes Utilize standard SAP programs
Tuning for Xbox
SalesSalesOrderOrder DeliveryDelivery
2
RetailerRetailer
Sales Order(EDI 850)1
Distribution Distribution WarehouseWarehouse
Ship Order (EDI 940)
3Rescheduling
Microsoft (SAP System)
Tuning for Xbox3 – Delivery (EDI Ship Order)• Custom pre-processing program:
Dynamic job builder and distribute workload over several processes
Utilize standard SAP program (RV50SBT1)• Additional index on table VBBE• Separation of output from document
creation Schedule RSNAST00 to process output Schedule RSEOUT00 to process IDocs and
combine into files
Tuning for Xbox3 – Delivery (EDI Ship Order)• Deactivate IDoc Syntax Check• SD number range buffering• Activate shared locking
For availability checking group level for ATP (via OVZ2)
• Evaluate program RVV50R1T (VL10) instead of current DDL Program was evaluated but not implemented Server group functionality is available in SAP
version 4.6c
Tuning for Xbox
SalesSalesOrderOrder DeliveryDelivery GoodsGoods
IssueIssue
Ship Order (EDI 940)
Ship Confirm (EDI 945)
Shipment
3
4
52Rescheduling
Sales Order(EDI 850)1
Distribution Distribution WarehouseWarehouse
RetailerRetailer
Microsoft (SAP System)
Tuning for Xbox5 – Post Goods Issue (EDI Ship Confirm)• Switch to parallel processing of
inbound IDocs via RBDAPP01 Same as sales order processing Table Locking – MVER (OSS Note 318581)
• Prevent plant locking Allow IDOC to be reprocessed (from a status 64)
instead of going into an error (status 51)• Activate ‘Late exclusive enqueue’
For material movements via OMJI (OSS 192423)• Deactivate IDoc syntax check
Tuning for Xbox
Distribution Distribution WarehouseWarehouse
SalesSalesOrderOrder DeliveryDelivery BillingBillingGoodsGoods
IssueIssue
Invoice(EDI 810)
Shipment4
6
2
Sales Order(EDI 850)1
Ship Order (EDI 940)
Ship Confirm (EDI 945)
3 5Rescheduling
RetailerRetailer
Microsoft (SAP System)
Tuning for Xbox6- Billing• SD number range buffering
Exclude certain countries due to legal requirements (OSS Note 23835, 363901)
• Parallel processing of billing due list Program RV60SBAT, specify ‘Number of jobs’
• Separation of output from document creation Schedule RSNAST00 to process output Schedule RSEOUT00 to process IDocs
Tuning for XboxAdditional Changes Implemented• ATP server (Available to Promise)
Information in OSS note 99999 Installed on central instance
• Tax solution (Vertex) upgrade Use ‘Registered RFC mode’ (OSS 63930)
• APO RFC calls (Advanced Planning Optimizer) RFC queue in R/3 spawning ARFC* jobs
Tuning for XboxSummary of Testing Results• SD Core Transactions:
1
1
7
2
20
4
12
4
0 5 10 15 20 25
Sales Orders
Deliveries
PGI
Billing
Seconds / Document (10 lines)
BeforeAfter
Tuning for XboxSummary of Results
0.001.002.003.004.00
s/Orders/Delivery
Xbox Transaction Volume
Xbox Transaction Performance
010,00020,00030,000
Oct-01 Nov-01 Dec-01 Jan-02
OrdersDeliveries
Tuning for XboxSummary of Lessons Learned• Utilize SAP/OSS resources • Assemble a project team with a wide
range of knowledge• Only test ONE change at a time• Be prepared to spend about 80% of your
time testing• And learn to hide from the Basis team
References
• “SAP R/3 Performance Optimization” by Thomas Schneider, Sybex
• “ALE, EDI & IDoc Technologies for SAP” by Arvind Nagpal, Prima Tech
Questions??
• Cindi McCutchen & Christoph Schuler
• Microsoft Corporation• Email: [email protected] or