Managing BW system in a Global Environment

Steve Slatzer, Director, Avnet Surya Muvvala, Lead Consultant, Seal

Agenda

• Introduction - Avnet

• Data Targets Administration

• Performance

• Data Loads Automation / Process Chains

• Data Validations

Agenda

• System Copy Strategies

• System Oriented Maintenance

• Upgrade

• Support Packages

• Q&A

54.3%

18.8%

26.9%

EM CM AC

$4.84B

$1.68B

$2.40B

32.5%

7.9%

59.6%

Americas EMEA Asia

FY02 Revenues $8.92B

$5.32B$2.90B

$0.70B

About Avnet, Inc.• Incorporated in 1955

– NYSE: AVT

– June 30 fiscal year end $2B market cap 11,000 employees• More than 60 countries• Serving the technology supply

chain– Electronics mfg sector (EM)

– Electronics mfg & PC integration (AC)

– IT end equipment sector (CM)

Avnet Global Coverage

Avnet SubsidiaryAvnet AgentBoth

$ B

ILL

ION

S

5-YEAR CAGR = 9.3%

Avnet, Inc. Revenue History

$5.73$6.33 $6.81

$9.92

$12.81

$8.92

$0.00

$2.00

$4.00

$6.00

$8.00

$10.00

$12.00

$14.00

FY97 FY98 FY99 FY00 FY01 FY02

Avnet Business Warehouse Overview

• Central repository for financial data to support SEM and end user reporting -- “A Single Source for the Financial Truth”

• Provides a framework to easily store data from both legacy and R/3 systems

• Highly scalable. Able to meet the global needs of Avnet.

• Powerful role-based query tool allows users to easily manipulate data and perform ad-hoc analysis

• Finance users began using the new system in Jan. 2002(~300 users)

SAP SEM / BW System

Business Warehouse (BW) Millennium GL Balances,

Journals, A/P, and

Fixed Assets

HR CensusData

Genesis Sales/COS

Hyperion Data

Financial Data from Other

Systems

SAP R/3 Data From Apollo and ARISE

End User Reporting

Business Planning Balanced Scorecard Management Cockpit

Consolidation

eExpenseData

(Concur)Global Book/Bill

Data

SAP Business Warehouse (BW)

Millennium BPSInfoCube

Hyperion BPSInfoCube

FixedAsset ODS

MillenniumFixed Assets

HR CensusFeed

CensusODS

JournalODS

Millennium G/LBalances

MillenniumG/L

Journals

MillenniumA/P

Detail

GenesisSales / Cost of

Sales Feed(Multiple Feeds)

Millennium G/LInfoCube

ConsolidationsInfoCube

(Hyperion)

A/P ODS

GenesisSales /COS

ODS's (3)

MonthlyHyperion Extract

Files

Drill-Thru

REVISED2/7/2003

Drill-Thru

AvnetAthena Project

SAP BW Production Flow

eExpenseODS

ConcureExpense

System

Global Booking &Billings

(populated throughBPS)

Genesis Sales / Cost of Sales

InfoCube

SAP Business Warehouse (BW)

REVISED2/7/2003

ARISE G/LBalancesInfoCube

ARISE CCAInfoCube

(Costs & Allocations)

ARISE PCAInfoCube

(Profit CenterAccounting)

ARISE SAP R/3(PEP)

AvnetAthena Project

SAP BW/SEM Production FlowApollo G/LBalancesInfoCube

Apollo CCAInfoCube

(Costs & Allocations)

Apollo CO/PAInfoCube

(ProfitabilityAnalysis)

Apollo SAP R/3(PEE)

Apollo A/RBalancesInfoCube

Apollo A/RAging

InfoCube

CO/PAODS

A/RODS

Drill-Thru

Drill-Thru

Landscape

Arise Development

ARISE_DEP

DEP Client 015

Apollo Development

DEE140

DEE Client 140

Everest Development R/3

R3DCLI401

DGI Client 401

EBV Development

C11CLNT001

C11 Client 001

Athena Development BW

DCB050

DCB

Athena Production BW

PCB050

PCB

Athena Quality BW

QCB050

QCB

Arise Quality

ARISE_Q45

QEP Client 045

Everest Production R/3

R3PCLI200

PGI 400

Everest Quality R/3

R3QCLI301

QGI 301

Everest Quality R/3

R3DCLI400

QGI 400

Legacy Systems

Data Targets Administration – InfoCubes

• Aggregates – Statistics Cubes, RSDDSTAT– Do not compress the data in aggregates as soon as they are

filled • Some of the important OSS Notes on aggregates

Note 166433 Options for Finding AggregatesNote 202469 Tracing Queries with AggregatesNote 176606 Aggregate Change RunNote 388069 Change Run MonitorNote 484536 Filling Aggregates of Large InfoCubesNote 388069 Monitor the Change RunNote 125681 Exception AggregationNote 189150 Non-Cum. Key Figures before AggregationNote 99010 Using RSRTRACE

Data Targets Administration – InfoCubes (cont’d)

• Statistics– Recommended to keep to update – If the data is more than 1 million records since last update,

strongly suggested to maintain the statistics– RSAR*– Issues with SAP_ANALYZE_ALL_INFOCUBES use

BRCONNECT instead– Set the percentage up to 100%, if the data is less than 10 million

records

• Indexes – Creation, Deletion– SAP_UPDATE_DBDIFF and

SAP_INFOCUBE_INDEXES_REPAIR– Both for cubes and aggregates

Data Targets Administration – InfoCubes (cont’d)

Important OSS Notes422264309955551552

Data Targets Administration – InfoCubes (cont’d)

• Selective Deletion – RSDRD_DELETE_FACTS – can be used to generate a program

for scheduling the selective deletion process in the background

• Compression of InfoCubes– Some of the cubes are compressed automatically as soon as the

data is load– Suggested to compress the cubes after validation of the data

• Auto Further Processing– Quality Check OK– Roll up is done – Compression is done as soon as the data load is done

Data Targets Administration – InfoCubes (cont’d)

• Strategy for Archiving of Data from cubes shall be planned before loading any data

• Partitioning of the Cube also has to be done before loading any data

• Periodically all the aggregates built on InfoCubes shall be validated. Higher the aggregates lower the performance

Data Targets Administration – InfoCubes (cont’d)

• Read Mode on Queries shall be monitored• Analyze the data in dimension tables and fact

tables with the help of T Code RSRV, regularly• Delete the statistics of the cubes from the

statistical cubes, periodically

Data Targets Administration – ODS

• Selective Deletion of Requests

• Selective Deletion of Active Table Records

• Deletion of Change Log Records

• Simulation of update from ODS to data targets

Source: SAP

Data Targets Administration – ODS (cont’d)

• Steps on Deleting Requests in ODS after updating into subsequent data targets (Pre-Requisite – Data is available in PSA)

– Delete the request from the data target (Cube)– Create a new infopackage on Data mart (8*) – Delete the initialization flag– Delete the request from ODS– Load the data up to PSA– Load the data for the infosource from PSA to ODS/Cube– Delete the data from PSA of data mart (8*)

BW Administration – Different Components

• Delete the PSA Data Regularly• Analyze the InfoObjects for SID values etc as needed,

repair the objects, if necessary with Transaction Codes – RSD1 and RSRV

• Regularly extract the global settings from different source systems – currencies, exchange rates, fiscal periods, UOMs etc

• Understand the Transport Connection and the need in creating BEx transports

• Authorizations and Security – Profiles may need to be updated or created

Performance – SQL Trace

• Performance can be improved for query access– Use trace tools ST05 – Used for analyzing database accesses to reduce

the database load

Performance – SQL Trace (cont’d)

Entries in RSDDSTAT

Source: SAP

Performance – DB Statistics (cont’d)

Source: SAP

Source: SAP

Performance – Accessing DB Tables

Source: SAP

• BW accesses DB tables via one of the following techniques– Index Unique Scan

– Index Range Scan

– Full Table Scan

– Concatenation

• Investigate the execution plan to troubleshoot performance issues

Source: SAP

Performance – Accessing DB Tables (cont’d)

• Use DB05 to determine if an index is needed– Displays selectivity of field combinations

• Determine an index is needed

– Also tells you which fields are appropriate for your index

Source: SAP

Performance – DB Statistics

Source: SAP

Source: SAP

• Execute program RSANAORA periodically using SE38– If the statistics are not maintained properly, data loads and

access will take more time– This program updates the statistics

– The database then always chooses the most efficient path

Data Loads Automation

• It is stronlgy suggested to use Process Chains for automation of data loads

• SAP GUI and BW Add-On are needed for accessing this Transaction

• Process Chains shall be adjusted after the Go-Live

• Plan data loads to extract the data from different source systems depending up on their local times – Europe, Asia, North America etc

Data Loads Automation (cont’d)

• Bolt-On ABAP Programs needed to automate the loads– Function Modules

• SO_NEW_DOCUMENT_SEND_API1 – to send mails• RSDDK_INFOCUBE_AGGREGAT_USED – to find the

aggregates created for an infocube • RSDDK_AGGREGATES_ACTIVATE – to activate

aggregates• RSDDK_AGGREGATES_FILL – to fill the aggregates• BAPI_IPAK_* - to start, change, delete an infopackage• BAPI_ISREQUEST_GETSTATUS – to find the status of a

request• RSSM_SLEEP_DEBUG – to wait for a process to complete

Data Loads Automation (cont’d)

• RSD_CUBE_F4 – to get the list of cubes• RSAPO_CLOSE_TRANS_REQUEST – to close the open

requests in Transactional InfoCubes• DD_TBIX_GET – to get the secondary indexes on an any

table (ODS)• DD_DROP_INDEX - to delete the secondary indexes on any

table (ODS)• DD_CREATE_INDEX – to create the secondary indexes on

any table (ODS)• RSDU_INFOCUBE_INDEXES_DROP – to drop the

secondary indexes on infocubes• RSDU_INFOCUBE_INDEXES_REPAIR – to rebuild the

secondary indexes after data loads

Process Chains

• Creating Process Chain is user friendly

• Data Load, Activation of data and subsequent loads to data targets can be accomplished

• New Process Chains can also be created in ABAP OO

• T Code RSPC• Can be transported• Can be monitored thru T Code

BWCCMS

Source: SAP

Data Validations

• Use/Create R3 ABAP Reports for BW data validations

• Schedule background jobs for these reports• Develop BEx queries for validation of the data• Schedule these queries in the background

with the help of Reporting Agent• Ensure that the selection parameters on R3

and BW are same• If the data comes from non-r3 systems,

develop custom solutions to ensure both BW and the source system data is in sync.

System Copy / Refresh

• Understand BW and R3 systems and their configurations

• Define a Strategy for System Copies / Refresh

• Careful Planning – Analyze the type of system copy and the associated impacts

• Consider the data consistency issues

• Understand Transport Connection in BW

• Use the feature of System Copy in Transport Connection

System Copy / Refresh (cont’d)

• Procedure to save BW Objects for System Copy

• Go To RSA1 – Transport Connection

• Select the source system

• Select the Grouping Mode as Save for System Copy

• Select the source system dependent objects

System Copy / Refresh (cont’d)

• Save the objects in a Transport – assign a development class

• Add any other objects, if needed

• Check the transport logs

• Release the transport

• Tips and Hints for Modifying BW Objects in Production

• BW Objects like InfoProviders, Transfer Rules, InfoObjects are not recommended to be developed in Production System directly

• Developments in Production are to be done only by qualified and skilled people

• Synchronize or re-develop the objects in other systems with the objects developed in Production

System Copy / Refresh (cont’d)

• In BW, some of the objects like Queries, InfoPackages, Aggregates can be modified in Production System though the system is locked for modifications

• Refer OSS Notes regarding system copy / refresh

• 184754 - Procedure after BW database copy

• 184322 – Procedure after DB Copy of BW source systems

• 184586 - System change option and BW

• 337950 - Queries (and other objects) cannot be edited

• 116432 - Setting default client in BW

System Copy / Refresh (cont’d)

• Types of System Refreshes in BW

• System Copy – BW and Source System in Parallel

• Easy but resource intensive – normally used to copy the production systems to TEST boxes for Business and Technical Reasons

• Most common use is during the Upgrade of systems

• To have the production like data in other environments

• Data Objects Consistency Issues

• System Refresh – BW and Source System in Parallel

• Minimal Steps to perform and re-connect systems

• Delta Extractor Status is maintained

System Copy / Refresh (cont’d)

• System Refresh – Only BW

• BW Objects have to be synchronized

• Data in BW needs synchronization with the Source Systems

• If multiple source systems is feeding BW, use 0LOGSYS object in data models

• System Refresh – Only Source Systems

• BW Objects have to be synchronized

• Data in BW needs synchronization with the Source Systems

• If multiple source systems is feeding BW, use 0LOGSYS object in data models

System Copy / Refresh (cont’d)

• Steps in General After System Copy / Refresh

• On Target BW – Following Actions Shall be performed

• Go To SM59 – Change the Target Host name as dummy

• Run BDLS – each one for changing the logical system name of and Target BW and one for each Target Source System

• Create new RFC destinations in SM59 for Target BW and for Target Source System

• On Target BW – Following Actions Shall be performed

• Perform the steps as described above in each Source System

• From Target BW, right click on each source system – Restore the source system

Important Activities on System side

• View Oracle Alert Log• Backups and validate their success• Audit Transaction DB24 (Verify all DB Jobs have completed

successfully)• Audit Transaction DB02• Check for any space critical objects or missing indices• Check DB data files – current sizes and verify that tablespaces are >

90% (DB02)• Clean up of SAP/Oracle log files• Oracle ‘check’ (DB24)• Oracle Cost Based Optimizer, Next Extent Application (DB24)• Review Contents of UNIX email accounts (elm or mailx)• View UNIX system log (/var/adm/syslog/syslog.log)• Check SAPOSCOL status and log file on all app.servers (SM51 -

>ST06)

Important Activities on System side (cont’d)

• Audit Transaction SP01 (Output/Print Controller)• Audit UNIX print queues (ll/var/spool/lp/request)• Review Contents of UNIX email account (elm or mailx)• Audit Transaction STMS for issues and “0” queues• Audit Transaction SM21 (Review SAP system log)• Audit Transaction SM37 (Background Job Analysis)• Audit Transaction ST22 (SAP short dumps)• Audit Transaction SM12 (Lock Entreis) look for RED• Audit Transaction SM13 (Update Records)• Review SAP Office inbox sizes (program RSSOINBO)• Audit Transaction SCOT (Mail Gateway) for ALL Clients (View ->

System Status)• Monitor the workloads thru ST03N – Expert Mode – BW Data Loads

Suggested System Settings

DataBase Buffers Quality (%) >= 94

Schedule brconnect -f next ('sapdba -next') weekly

for information about BRCONNECT and SAPDBA, see SAP Note 403704

Oracle Parameters:- parallel_max_servers

- parallel_threads_per_cpu

- processes

- sessions

- timed_statistics

48

1

320

390

TRUE

Buffer Settings- zcsa/table_buffer_area

- rsdb/obj/buffersize

65001000

32000

Suggested System Settings

Extended Memory Size em/initial_size_MB 6138

Memory Management - es/use_shared_memory

- es/use_mprotect

TRUE

TRUE

App. Server OS Kernel Parameters - maxdsiz_64bit 4294967296

App. Server OS Kernel Parameters - maxdsiz_64bit 4294967296

Archiving

• Archiving Process:– Select Data Target to be archived

– Configure Archive object– Configure Archiving processes– Test Archiving process– Archive data– Validate Archived data– Delete data– Move archive data to storage subsystem (optional)

• Administration– T Code for Archiving Administration – SARA– Archiving sessions can be scheduled and monitored– Only one Archiving object can be defined for one

data target

Source: SAP

Steps - Upgrade

• Planning

• Pre-Upgrade Activities

• SAP GUI Deployment

• Upgrade

Plug-Ins

BW

• Post-Upgrade Activities

OverviewPlanning Pre-Upgrade Upgrade Post-Upgrade

Resources

Schedules

Test Plans

SP Checks

InfoObjects – Active

Cleansing

Char. Conversion

BW

SAP GUI Deploy

Plug-InHardware & Software

Project Plan Validations

Customizing

OSS Notes

Training

Resolutions

ProductionQualityDevelopmentTest

Approvals

Issues

SEMTesting

Document

Copy

CopySAP

Alpha Conversion

Check Internal values

System locked

Conversion running

Edit Characteristics

T Code : RSMDCNVEXIT

Help Document

Source: SAP

Convert Int. Values

Values before and after Convn.

Char. Exists

100,000 records in SID table – 1 to 2 min

Estimate the Time

Managing Support Packages

• Adopt a strategy for applying support packages on BW and the connected SAP source systems

• Apply Support Packages in Sandbox and test before applying them on to – Dev, Q and P boxes

• No transports shall take place from DEV to Q or PRD systems, if they are not in sync with the SPs

• Always look for the latest Support Packages and apply to the one before the latest support package

• After applying SPs, execute SPAU to look for modified ABAP Objects and decide whether to accept the changes or not

Managing Support Packages (cont’d)

• Before applying any support packages on any R3 source system, complete all delta loads from this source system

• Activate the Source system, if BW system is upgraded. For any other issues, RESTORE the source system

• Inform BW resources when ever SPs have to be applied on source systems

• www.service.sap.com/patches - for downloading Support Packages

Key Points to Take Home

• Managing BW System has – TWO Important Considerations

– Data Management and System Management

• BW and Source Systems Administrators have to work hand-in-hand

• A strategy has to be in place for System Copies• All the Data Targets need administration constantly• Statistics, Indexes and Aggregates have to be monitored

constantly• Archiving shall be planned during the design phase of

Data Targets

Click to add text

Contact Details

Surya MuvvalaSurya MuvvalaLead Consultant (BI Solutions)Lead Consultant (BI Solutions)

Seal Consulting, IncSeal Consulting, Incsurya.muvvala@sealconsult.comwww.sealconsult.comPhone: (732) 417-9595Cell: (480) 225-9666

Surya MuvvalaSurya MuvvalaLead Consultant (BI Solutions)Lead Consultant (BI Solutions)

Seal Consulting, IncSeal Consulting, Incsurya.muvvala@sealconsult.comwww.sealconsult.comPhone: (732) 417-9595Cell: (480) 225-9666

Steve SlatzerSteve Slatzer

Director, Avnet Corp. FinanceDirector, Avnet Corp. Finance

Avnet IncAvnet Inc

steve.slatzer@avnet.com

www.avnet.com

Steve SlatzerSteve Slatzer

Director, Avnet Corp. FinanceDirector, Avnet Corp. Finance

Avnet IncAvnet Inc

steve.slatzer@avnet.com

www.avnet.com

Customer

Partner

Thank you for attending!

Please remember to complete and return your evaluation form following this session.

Session Code: 306