Escolar Documentos
Profissional Documentos
Cultura Documentos
http://www.sdn.sap.com
Extraction Performance
Aggregate Maintenance
Extraction Performance
Aggregate Maintenance
Extractor
Extractor
Process Business Information Source
Warehouse System
ALE ALE
BW BW Attributes
InfoCube S-API ODS
Master Data
NEW
Texts
Update rules
BW 3.0
Update rules
Communication
Communication Structure
Structure Communication
Communication Structure
Structure
transfer
transfer structure
structure transfer
transfer structure
structure
Source
System transfer
transfer structure
structure transfer
transfer structure
structure
Extraction
Extraction Source
Source Structure
Structure Extraction
Extraction Source
Source Structure
Structure
BW BW
S-API S-API
Header DataSource
DataSource ATTR
Item
Master Data TXT
Transaction Data
Extraction Performance
Aggregate Maintenance
Determine the
extraction time:
Extraction
S-API
ALE ALE
Scheduler
Loading
Extractor
Extractor
Business Information Source
Process Warehouse System
Check SM51 /
SM50 in the
source system
Further Analysis
in case of
PERFORMANCE
problems
extracting data...
Transaction:
RSA3
Analyze
high ABAP
Runtime:
Particularly
Useful for
User Exits
Identify
expensive
SQL
Statements
Parallel processes:
distribute to different servers
avoid bottlenecks on one server
Config in table ROIDOCPRMS
Expected Results:
Avoid CPU/Memory bottlenecks on one server
Greater Throughput: Faster time to completion per request
Scenario:
Set up the parameters according to the recommendations; if upload
performance is not improved, try to find other values that fit exactly your
requirements.
Expected results:
In a resource constrained systems, reduce DataPackage size
In larger systems, increasing the package size to speed collection;
but take care not to impact communication process and unnecessarily hold work
processes in SAP source system.
Greater throughput = Faster time to completion per request
OSS note
409641 for
details If no entry was maintained, the data is
transferred with a standard setting of 10000
kbyte and 1 “Info IDOC” for each data packet.
? ?
?
?
Consider building indices on DataSource
Tables based on selection criteria
Generic extractors:
Collector jobs can be executed in parallel
InfoPackages executed in parallel to extract data
Not possible for delta extracts from one generic data source
Investigate Secondary indexes on fields used for selection
Optimize custom ‘collector’ ABAP coding
Extraction Performance
Aggregate Maintenance
ALE ALE
Scheduler
Loading
Extractor
Extractor
Business Information Source
Process Warehouse System
ALE ALE
InfoCube
Update Transfer PSA IDOC IDOC S-API
rules rules tRFC
ODS
ALE ALE
Scheduler
Loading
Extractor
Extractor
Business Information Source
Process Warehouse System
ALE ALE
InfoCube
Update Transfer PSA IDOC IDOC S-API
rules rules tRFC
ODS
Transfer Rules
ALE ALE
Scheduler
Loading
Extractor
Extractor
Business Information Source
Process Warehouse System
ALE ALE
InfoCube
Update Transfer PSA IDOC IDOC S-API
rules rules tRFC
ODS
Update Rules
Recommendations:
SINGLE SELECTs are one of the performance “killers” within these
codings; use buffers (such as internal tables) and array operations
instead.
Avoid too many library transformations, as they are interpreted at
runtime (not compiled like routines)
The transformation engine or library is new in BW 3.0
2003 SAP Labs, LLC,Know-How Netowke , Ron Silberstein26
Agenda 27
Extraction Performance
Aggregate Maintenance
ALE ALE
Scheduler
Loading
Extractor
Extractor
Business Information Source
Process Warehouse System
ALE ALE
InfoCube
Update Transfer PSA IDOC IDOC S-API
rules rules tRFC
ODS
Scenario:
High volumes of transaction data: significant DB access
(NRIV table) to fulfill number range requests.
Expected Results:
Accelerates data load performance per load request.
Note:
After the load, reset the number ranges buffer to its
original state: minimize unnecessary memory allocation.
Scenario:
Always load master data before transaction data (ODS and
InfoCube).
When completely replacing existing data, delete before load!
Expected Results:
Accelerates transaction data load performance: all master data SIDs
are created prior to transaction load, and need not be determined
during transactional data load (large overhead).
Scenario:
When completely replacing existing data, delete before load!
Expected Results:
Data deleted from PSA can reduce PSA read times
Data deleted from InfoCube reduces deletion and compression
time.
“Drop partition...“ DDL statement instead of “delete from table...“ DML
statement only takes seconds
Deleting Data also speeds data availability (aggregates, etc)
Data Packets /
Requests can not
be loaded into an
ODS object in active data change log
Doc-No.
parallel
overwriting
functionality Activation Activation
Locking on
Activation table
New/modified Activation
Doc-No. data queue
Req1
Req1
Sequential Req2 Req2
load Req3
Req3 Req 3,1,2
Staging
Staging Engine
Engine
Activation
Activation
Req1 Req1
Req2
Req2 Parallel load
Req3
Req3
Staging
Staging Engine
Engine
2003 SAP Labs, LLC,Know-How Netowke , Ron Silberstein33
ODS Activation example (BW 3.0) 34
Active data Change log
Transaction RSCUSTA2
Loads are faster as Master Data SID tables do not have to be read
and linked to the ODS data
2003 SAP Labs, LLC,Know-How Netowke , Ron Silberstein36
Further ODS Loading/Activation enhancements (3.x)37
Index maintenance
Indexes speed querying
Slow down activation
Extraction Performance
Aggregate Maintenance
System-controlled parallelism
Parallel upload by packaging the source data
Packets are created during the extraction and sent simultaneously to BW
Packet size for flat files definable in table RSADMINC (IDOCPACKSIZE)
Packet size for mySAP source systems definable in table ROIDOCPRMS
(MAXLINES)
Extraction Staging
Engine
ODS Object
Data Packets
1
2
3
Option 4
1 BTC
New in BW 3.X
Process Chains
Replacement for Event chains
Transaction RSPC
Process type :
Delete Index
Generate Index
Auto suggestion depending on
InfoPackage selected.
Extraction Performance
Aggregate Maintenance
Display aggregate
hierarchy
{Material,
Material
Basic InfoCube Group,
Customer,
Day}
{Material
Few large Group,
basis Customer,
aggregates Day}
{Material
Many small
Group,
aggregates
Month}
Change Run
Aggregates can contain
Dimension Characteristics
Navigational Attributes
Hierarchy Levels
When master data changes, the changes of the
navigational attributes/hierarchies must be applied to the
depending aggregates; this process is called change run
Newly loaded master data is not active until the change
run has been applied the changes to all aggregates
Threshold for delta and new build-up in customizing
The Change Run can be parallelized across InfoCubes;
see SAP note 534630 for more details
Check aggregate hierarchy (see Roll-Up for more details)
Try to build basis aggregates that are not affected by the
change run, i.e. no navigational attributes nor hierarchy
levels
The following slides show details on the process itself …
2003 SAP Labs, LLC,Know-How Netowke , Ron Silberstein49
Copyright 2003 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.
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®, 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 ServerTM are trademarks of IBM Corporation in USA and/or other countries.
ORACLE® is a registered trademark of ORACLE Corporation.
UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and
other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, 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 invented
and implemented by Netscape.
MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.
SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other
countries all over the world. All other product and service names mentioned are trademarks of their respective
companies.