basis bi

8/2/2019 basis bi

1/15

Moni t or ing for BI Basis (ABAP and J ava)B e s t Pr a c t i c e f o r So l u t i o n M a n a g e m e n t

Version Date: July 2008

SAP NetWeaver 7.0 (2004s) Business Intelligence

The newest version of this Best Practice can always be obtained throughthe SAP Solution Manager or the SAP Service Marketplace.

Conten ts

Applicability, Goals, and Requirements................................................................................................2

Best Practice Procedure and Verification.............................................................................................3

Preliminary Tasks..........................................................................................................................3

Procedure for the ABAP Stack.......................................................................................................3

General Tasks.........................................................................................................................3

Monitoring...............................................................................................................................5

Performance ...........................................................................................................................7

Data Consistency ....................................................................................................................9

Procedure for the Java Stack ......................................................................................................10

General Tasks.......................................................................................................................10

System Monitoring ................................................................................................................10

Further Information ...........................................................................................................................13

8/2/2019 basis bi

2/15

Best Practice: Monitoring for BI Basis (ABAP and Java)

2008 SAP AG

2

Appl ic abi l i t y, Goals , and Requirem ent s

To ensure that this Best Practice is the one you need, consider the following goals and requirements.

Goal of Using this ServiceThis document provides recommendations about jobs and tasks that have to be performed on aregular basis in the area SAP basis to ensure good system performance and stability in a BI system.Separate documents about periodic jobs are available for the area of reporting (BW-BEX) andwarehouse management (BW-WHM).

Alternative Practices

You can get SAP experts to deliver this Best Practice if you order the Solution ManagementOptimization (SMO) service known as the System Administration Workshop. For further detailsconcerning this service, refer to SAP Service Marketplace http://service.sap.com/supportservicesSAP System Administration.

Staff and Skills RequirementsFor optimal benefit, you should make sure that you have experience in the following areas:

Knowledge of standard SAP application and database monitors

Experience in job scheduling in an SAP environment

System Requirements

This document refers to NetWeaver 7.0 (2004s) BI systems.

For this document to be of relevance and benefit to all administrators, it will not cover features orrestrictions that belong to any particular database or operating system in detail.

Duration and Timing

Periodic jobs and tasks have to be performed in a BI system on an ongoing basis. The time requiredlargely depends on the size of the BI system.
http://service.sap.com/supportserviceshttp://service.sap.com/supportservices

8/2/2019 basis bi

3/15


2008 SAP AG

3

Best Prac t ice Proc edure and Ver i f i ca t ion

Pre l iminar y Task s

It is recommended that this Best Practice be read completely before any given recommendations areimplemented. We strongly advise against direct changes in the production environment, andrecommend first testing any changes in a test system.

Proc edure for the ABAP Stac k

General TasksEarlyWatch AlertFrequency: Weekly

The free SAP EarlyWatch Alert service can be used to facilitate BI maintenance. It offers a uniqueapplication and basis perspective on the system. Use the SAP EarlyWatch alert as part of the systemmonitoring strategy. It is also a good information source and checklist which can be used in meetingsbetween the application and basis teams. SAP Note 207223 describes how to activate the EarlyWatch Alert.

Support Package Stack StrategyFrequency: Depends on the scenario used

To keep the system up-to-date, SAP recommends implementing Support Package Stacks into thesystem landscape on a regular basis. This should prevent already known and fixed bugs affecting yourbusiness and allow you to make use of product improvements. Details about the SAPrecommendations for support package stacks can be found in SAP Note 1055581.

To guarantee an optimal level of support from the SAP side, the system has to have an up-to-datestatus.

Therefore, a periodical maintenance window has to be planned by the application team in cooperationwith the IT department to implement and test these Support Packages or Patches in the customer-specific Business Scenario (at least each quarter of a year). It is recommended to apply SupportPackage Stacks, which are usually delivered quarterly (see http://service.sap.com/sp-stacks).

Corrections are only brought out in notes if problems are caused by applying SAP Support Packagesor Patches. In such cases as these, the matter is referred to in the SAPBWNEWS. SAPBWNEWS isbrought up-to-date with every BW Support Package stored as notes in SAP Service Marketplace. Formore detailed information, check the current information in the SAP Service Marketplace:http://service.sap.com/bi Services & Implementation Support Package News
http://service.sap.com/sp-stackshttp://service.sap.com/sp-stackshttp://service.sap.com/bihttp://service.sap.com/bihttp://service.sap.com/sp-stacks

8/2/2019 basis bi

4/15


2008 SAP AG

4

Backup StrategyFrequency: Daily

A backup and restore concept needs to be created. This concept should define how to backup and

restore each individual system component.A B&R concept must also take into account possible procedures in case of a point-in-time recovery ofone of the system components. A procedure must be defined and tested to handle cases wherespecific application data is lost in one of the systems. A vital factor for the operability of a restore incase of an emergency is the thorough testing of procedures and training of administrators on restoreand recovery scenarios.

For details, refer to the Best Practice document "Backup and Restore for mySAP Business Suite",which is available either through the SAP Solution Manager in the SAP Service Marketplacehttp://service.sap.com/atg

This document lists, among many other contents, suggestions and recommendations on:

Backup and recovery procedures for all individual components of your system landscape

Procedures for performing a landscape-wide backup and recovery

Dealing with point-in-time restores

The document also contains an example of how to set up a viable Backup and Recovery procedure ina mySAP.com landscape.SAP Note 731682 provides an overview about experiences, risks and recommendations about backupin OLTP and BI systems. Backup and recovery for the BI Accelerator is covered in the how to guideHow To Perform a SAP NetWeaver BI Accelerator Backup and Recovery.

Transport WindowFrequency: Weekly

Transports and SAP Notes should be applied to the productive BW system in a defined time windowwhen no data uploads are taking place.

There should be clearly defined guidelines for the conditions which require the productive system tobe opened for emergency corrections - this should only be done on an exceptional basis. In general,all changes (except the explicitly allowed ones in the BW transport system) should be made in thedevelopment system and transported via the quality assurance and test systems to the productiveenvironment. Well defined and documented test scenarios should be used, and, if necessary, adaptedto ensure the quality of all transports released to the productive environment.

When transports, notes, or support packages are applied in the source system, this may also have aneffect on the extraction structures or the extraction process for SAP BI. Fields and/or programs can bechanged or simply deactivated. It can be the case that some BI extractions do not work after these

changes or that deltas may be lost. The BI team may also lose valuable time investigating theseissues because they were not aware of these standard program modifications.

There should be a procedure in place to inform people from the BI team before notes are applied inSAP source systems that may have an influence on extraction or updating. The BI team has to havethe possibility to take necessary actions (for example, load delta data). As this dependency may notalways be mentioned in the note itself, awareness of these interactions should be created in the SAPsource system team. There should be a special awareness of notes in the following components:

BW-BCT* (affecting extraction logic)

BC-BW (affecting delta queue and/or Service-API)

All components where data is extracted from SAP systems

These notes should be investigated very carefully to verify if there are changes in structures, updating,or extraction logic. It is very important to note that prior to support package and Plug In upgrades inthe source system, it is necessary to empty the delta queues for all DataSources.
http://service.sap.com/atghttps://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e066bf8b-eaf8-2a10-35be-e8fec11aa262https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e066bf8b-eaf8-2a10-35be-e8fec11aa262https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e066bf8b-eaf8-2a10-35be-e8fec11aa262http://service.sap.com/atg

8/2/2019 basis bi

5/15


2008 SAP AG

5

Monitoring

Basis Jobs

Frequency: Hourly to monthly, depending on the specific job.There are a number of jobs that have to run periodically in a live BI installation, for example, to deleteoutdated jobs. You can easily schedule these jobs as follows: Transaction SM36 press button'Standard jobs'.

Refer to SAP Note 16083 for details.

8/2/2019 basis bi

6/15


2008 SAP AG

6

Basis MonitoringFrequency: Daily

The normal basis monitoring also has to be performed on a BI system, including (among others) thefollowing logs and monitors:

System Log (transaction SM21)

ABAP Runtime Errors (transaction ST22)

Operation System Monitor (transaction ST06N)

This monitor provides an overview of the current CPU, memory, I/O and network load on anapplication server instance. You can also access a 24-hour overview of the hardware/OS load.Important indicators are CPU utilization, memory pages out / in (indicates swapping,depending on operating system), disk utilization (indicates I/O bottlenecks) and LANthroughput (indicates network problems).The CPU utilization should be less than 70%; notmore than 20% of the physical memory should be swapped.

Tune Summary (transaction ST02)

Ensure that the instance parameters are set as recommended in SAP Note 1044441. Thesingle-record buffer usually contains BI master data tables. The generic buffer contains mostBW-specific control tables (RS*-tables). The table buffer call statistics can be monitored intransaction ST10. It shows buffer type, usage, and invalidations. In case master data tablesget very large, investigate the recommendations provided in SAP Note 550784 regarding thedeactivation of the table buffering. The Export/Import Shared memory contains the OLAPquery cache. Note that the Export/Import Shared Memory does not swap. Usually, the Export /Import buffer is also used intensively in BI systems intensively. Ensure that the Export / Importbuffer as well as the Export / Import shared memory are large enough.

Lock entry monitor (SM12)

Database monitor (transaction ST04)

The database monitor checks important performance indicators in the database, such asdatabase size, database buffer quality and database indexes. The detailed functionalitydepends on the underlying database management system.- Data buffer quality (should be usually at least > 90%)- Check exclusive lock-waits for detecting deadlocks- Check DB log for special DB problemsEnsure that you configured your database according to the SAP Note relevant to yourdatabase management system. SAP Note 1044441 provides an overview of relevant SAPNotes for all database management system.

Table/Index Overview (transaction DB02)

The Table/Index Overview (direct access with transaction DB02 or using transaction ST04)reports on the tablespaces, tables, and indexes. You can see the space statistics (total and

free space) and its temporal growth, and you can check for missing indexes (be sure torefresh the space statistics regularly).

Ensure that alerts are triggered in the most important areas. This can be done using the ComputingCenter Monitoring System (CCMS, transaction RZ20).

8/2/2019 basis bi

7/15


2008 SAP AG

7

Performance

Process OverviewTransactions SM50 and SM66 give an overview of all running processes in your BI system. Theyprovide information like user, current program, run time, CPU (additional button in the menu bar), andstatus.

Workload Monitor

The Workload Monitor (transaction ST03) shows important overall key performance indicators (KPIs)for the system performance. It monitors:

Distribution of response times.

Transactions with the highest response time and database time.

Memory usage for each transaction or each user per dialog step.

Note: For a BI system the entity dialog step is not really meaningful, the numbers here should betaken with care.

The expert mode provides:

Switch toexpert mode

8/2/2019 basis bi

8/15


2008 SAP AG

8

Information on BI queries, structured by runtime share, number of runs, and much more. Thisreport is also available aggregated on the InfoProvider. The data displayed here can also be foundin the MultiProvider 0TCT_MC01 and the related BI queries

Information about the data loads and process chains.

Transaction ST03 should be the starting point for a performance analysis.

Calculate StatisticsFrequency: Daily

For database performance reasons, it is essential to ensure that the database cost-based optimizerstatistics (CBO statistics) are collected at the optimum time and in the recommended way.

Depending on the database management system used, statistics are calculated differently.

Oracle: SAP Note 1020260, section 8 of SAP Note 1013912.Remark:Ensure that all relevant bug fixes are implemented; especially the optimizer merge fixavailable for the Oracle Patch set that is in use.

Microsoft SQL Server: The SQL Server updates the table statistics automatically if theAuto create statistics and Auto updates statistics database options are set. These settings arethe default settings in SAP installations and you should normally not change them. InvestigateSAP Note 849062 for BI specific details.

IBM DB2 for Linux, UNIX and Windows: SAP Note 801011 describes BI-specific settings that arerelevant in case AUTORUNSTATS is not used.

IBM DB2 for Z/OS: Investigate the SAP Notes 915398.

MAXDB: SAP Note 797667 provides an overview about statistics creation for MAXDB.

Usually, it is not required to calculate database CBO statistics from within process chains. In somecases however, this might be required. One scenario might be if an InfoCube or Data store object iscompletely deleted and refilled. No CBO statistics are available now until they are created by the

standard procedure. Users might start running queries, however, directly after the data loads havebeen completed. The performance is severely impacted now, as no CBO statistics are available. If thisis the case, consider integrating a statistics collection method for the affected InfoProvider into therelevant Process Chain(s). Statistics collection comes as a standard process in the Process Chainmaintenance.

Index Maintenance and MonitoringFrequency: Weekly

The type of indexes and the administration possibilities can be quite different in SAP BI compared toOLTP Systems (for example SAP ECC).

Assign responsibility for the creation, maintenance, and monitoring of indexes. Responsible teammembers should have a good understanding of the performance values of indexes, but also themaintenance costs. They should also have a good awareness of the data flows and should regularlycheck for missing and degenerated indexes. You should be aware that the secondary indexes of thefact tables (/BI*/F) might be dropped intentionally during data load (and are rebuiltafter the load finished).

Tools and logs which can be used to detect degenerated indexes include:

Transaction RSRV

The Data Warehousing Workbench Right click on the InfoCube Manage Performancetab

Transaction ST04 (DB02) Missing indexes

If you use Oracle as DMBS, further information on index fragmentation is available in SAP Note771929.

8/2/2019 basis bi

9/15


2008 SAP AG

9

SQL TraceThe SQL trace (transaction ST05) records all activities on the database, and enables you to checklong runtimes on a DB table or several similar accesses to the same data.

Some tips for reading execution plans:

Read the hierarchy from the inside out

At the same level: read a set of operations from top to bottom

Try to avoid unspecified full table scans; generally prefer index accesses (unless the table isvery small or a large fraction of the table content has to be read anyway)

Short descriptions of some of the execution plan tree nodes:

Full Table Scan: Accesses every record of a table

Clustered Index Scan (MS SQL Server): access through clustered primary index; comparableto full table scan

Nested Loop: For each relevant row in the first table, the matching rows in the other table

have to be determined Hash Join: the smaller table is used to build up a hash table on the join key (optimal: in

memory); then the larger table is scanned and joined with the hashed table

Bitmap Merge / Bitmap And (only ORACLE): Disjunction respectively conjunction of bitmapindexes

Partition Range Iterator: the process is executed for every partition

ABAP Runtime AnalysisThe ABAP runtime analysis (transaction SE30) traces the activities spent in different parts of coding(SQL, specific function modules). It states the number of executions, gross time (for global

optimization), and net time (for local optimization). The gross time includes the times of all called sub-routines; the net time includes only the actual time spent in the mentioned module.

Single Transaction AnalysisThe single transaction analysis (Transaction ST12) offers a central point of performance analysis andcan be seen as a combination of the ABAP Runtime Analysis and the SQL Trace. Details can befound in SAP Note 755977.

Data ConsistencySchedule RSRV ChecksFrequency: Weekly, important checks daily.

Use transaction RSRV to analyze the important BI Objects in the system. This transaction alsoprovides repair functionality for some tests. These tests only check the intrinsic technical consistencyof BI Objects such as foreign key relations of the underlying tables, missing indexes and so on. Theydo not analyze any business logic or semantic correctness of data.

Missing table indexes or inconsistencies in master or transactional data can have a negative impact onyour system performance or lead to missing information in your BI reporting.

You can schedule the tests in RSRV to be run regularly in the background by defining a specific testpackage for your core business process and needs. Weekly checking (for example, at the weekend)

8/2/2019 basis bi

10/15


2008 SAP AG

10

should be adequate in general, but important checks (for example, missing table indexes) could bealso performed on a more frequent basis (for example, daily).

Another option is to start these checks based on an event (for example, tests are triggered after dataloading).

If you do so, make sure that the application log is checked regularly for the results and recommended

necessary corrections are made in time.When the results of the checks are displayed in the application log, you can double-click on themessage. You will then see the message again on the right hand side with additional buttons for longtexts and details (scroll to the right side) if applicable.For more general information about the analysis and repair environment, check the SAP onlinedocumentation.

Proc edure for the Java Stac k

General Tasks

Support Package Stack StrategyPlease check the general remarks about the support package stack strategy in the section of theABAP stack. Details about BI Java Support Packages and Patches can be found in SAP Note1072576.

Backup StrategyPlease check the general remarks about the backup strategy in the section of the ABAP stack.Note:

In addition to the database backup, the filesystem /usr/sap// has to be saved for BI Java.

File System CleanupFrequency: Weekly

The Java Enterprise Edition engine writes log files and traces to the file system. During normaloperations, the amount of data is rather small, so no problem is expected. Depending on the settingsof the java virtual machines, heap dumps might be written to the file system in the case of anOutofMemory error. These heap dumps are useful for analyzing memory problems, but they can fill upthe file system if they are not deleted regularly. This deletion job can be automated by a cron job thatdeletes all heap dumps older than seven days.

System Monitoring

Basic Monitoring ToolsA prerequisite for effective monitoring of a Java-based system is running Solution ManagerDiagnostics with Wily Introscope. A detailed installation instruction is beyond the scope of thisdocument. If your BI system is not yet instrumented and connected to an SMD, refer to thedocumentation at http://service.sap.com/diagnostics/.

Also not covered here is the connection of your Java instance to the central monitoring system (CEN).Step by step instructions for this can be found in SDN SAP NetWeaver Capabilities Lifecycle

Management Operations.
http://help.sap.com/saphelp_nw70/helpdata/EN/92/1d733b73a8f706e10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/92/1d733b73a8f706e10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/92/1d733b73a8f706e10000000a11402f/frameset.htmhttp://service.sap.com/diagnostics/http://service.sap.com/diagnostics/https://www.sdn.sap.com/irj/sdn/indexhttps://www.sdn.sap.com/irj/sdn/indexhttp://service.sap.com/diagnostics/http://help.sap.com/saphelp_nw70/helpdata/EN/92/1d733b73a8f706e10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw70/helpdata/EN/92/1d733b73a8f706e10000000a11402f/frameset.htm

8/2/2019 basis bi

11/15


2008 SAP AG

11

Proactive Monitoring TasksRegular proactive monitoring is a prerequisite for ensuring a stable and well performing BI system.The monitoring will highlight trends in response time, memory usage, navigation steps and so on. Itensures that potential risks and problems are identified early and that they can be solved before theend-users are affected by them.

The sections below describe some typical areas that should be monitored regularly. Depending onthe end-user requirements, additional performance indicators have to be taken into account. Thesecustomer-specific indicators are not discussed in this document.

Garbage Collection

Frequency: Daily

The garbage collection (GC) is one of the most important features of the Java virtual machine. Toachieve a good performance, it has to be assured that there are not too many full garbage collectionsand that the average garbage collection time is small. As rule of thumb, the GC time should be lessthan 5% of the elapsed time and the number of full garbage collections should be much smaller thanthe number of minor GCs.

Information about the GC can be found in Wily Introscope and in the Solution Manager Diagnostics(SMD). If the latter is used, go to E2E Workload Analysis, select BI Java and Java Memory Usageto get an overview of the GC time and the full GC fraction.

An increase in GC time or in the number of full GCs should be analyzed. If necessary, the Javamemory parameters have to be adjusted.

Heap Usage

Frequency: Daily

Memory shortages can cause severe problems like Out of Memory dumps and high GC times.Therefore, the heap usage of the Java stack should be monitored regularly. Information about it can

be found in Wily Introscope and SMD.

In the SMD, navigate to Workload Analysis Java Memory Analysis. The heap consumption should

look like a saw tooth:

The bottom line of the graph should be horizontal (see green line); a positive slope indicates a memoryleak. In this case, a deeper analysis is required and if the memory leak is inside an SAP delivered

routine, a message should be opened at SAP.

Error Log Analysis

Frequency: Daily

To recognize potential problems soon the traces of the Java Enterprise Edition engine have to bechecked regularly. There are several tools available for this, for example, Visual Administrator, logviewer, and SMD. Not surprisingly, the log viewer is the most powerful tool for this purpose it isdesigned specifically for viewing the logs. However, in this short best practice document we will focuson SMD. The SMD has the advantage that it is a single point of entry for all systems.

The J2EE logs can be found in Exceptions log viewer.

8/2/2019 basis bi

12/15


2008 SAP AG

12

Typically, the default trace contains the most critical errors, but the other trace files should also bechecked regularly.

The errors in the trace files have to be analyzed and solved if they affect the system.

8/2/2019 basis bi

13/15


2008 SAP AG

13

Fur t her In form at ion

Overview about Jobs and Tasks

The table below lists all the jobs and tasks, which are discussed in this Best Practice.

Area Job / Task Frequency

EarlyWatch Alert Weekly

Support Package Strategy Depending on scenario

Backup Strategy Daily

General Tasks

Transport Window Weekly

Basis Jobs Hourly to monthly, dependingon the specific job.

Monitoring - Basis

Basis Monitoring Daily

Data Consistency Schedule RSRV Checks Weekly, important checksdaily.

BI-Table Names

Most BI tables follow a strict naming convention. The most important table names are listed in thetable below. In the table below, the prefix /BI* is a place-holder for either the prefix /BI0 or the prefix/BIC. The prefix /BI0/ is used by Business Content objects delivered by SAP, the prefix /BIC is usedby customer-defined objects (unless an own namespace as outlined in SAP note 401778 is used).

Table Name Item

/BI*/A00 Active Data Store Object (DSO) Table

/BI*/A40 Activation queue of the DSO

/BI*/B PSA-Table / DSO activation queue

/BI*/D InfoCube Dimension table

/BI*/E InfoCube Facttable for compressed requests

/BI*/E Aggregate Facttable for compressed requests

/BI*/F InfoCube Facttable for new requests

/BI*/F Aggregate Facttable for new requests

/BI*/M View of Master data tables (/BI*/P*, /BI*/Q*)

/BI*/P Characteristic: Master Data (Time independent)

/BI*/Q Characteristic: Master Data (Time dependent)

/BI*/S Characteristic: SID Table

/BI*/X Characteristic: Attribute SID Table (time independent)

/BI*/Y Characteristic: Attribute SID Table (time dependent)

/BI*/H Hierarchy table

/BI*/I Hierarchy table (SID Structure)

8/2/2019 basis bi

14/15


2008 SAP AG

14

/BI*/J Hierarchy table (Hierarchy Intervals)

/BI*/K Hierarchy table (Conversion of Hierarchy Nodes SID)

/BI0/01*, /BI0/02*, /BI0/06*, /BI0/0D*, /BI0/0P* Temporary database objects (see SAP Note 1139396)

Important Transactions

Transaction Description

DB02 Tables and Indexes Monitor

LISTCUBE List viewer for InfoCubes

LISTSCHEMA Show InfoCube schema

RRMX/RRMXP Start the BEx Analyzer / Start the BEx Analyzer for specific workbook or query

RSA1 / RSA1OLD BI Data Warehousing Workbench / BW Administrator Workbench

RSA3 Extractor Checker (source system)

RSA7 BI Delta Queue Monitor (source system)

RSMO Upload Monitor

RSPC Process Chain Maintenance

RSRCACHE Cache Monitor

RSRQ Data Load Monitor for a Request

RSRT Query Monitor

RSTT BI Trace Tool

RSECADMIN Management of Analysis Authorizations

SE11 ABAP Dictionary: Initial Screen

SE12 ABAP Dictionary: Initial Screen (Display mode)

SE16 Data Browser

SE30 ABAP Runtime AnalysisSE37 ABAP Function Modules

SE38 ABAP Editor

SLG1 Application Log

SM21 System Log Analysis

SM37 Simple Job Selection

SM50 Work Process Overview

SM51 SAP Servers

SM59 Configuration of RFC connections

SM66 Systemwide Work Process Overview

ST02 Setups/Tune Buffers

ST03 Performance,SAP Statistics, Workload

ST04 DB Performance Monitor

ST05 Performance trace

ST06 Operating System Monitor

ST10 Table Call Statistics

ST12 Single Transaction Analysis

ST22 ABAP Runtime Errors

STAD Statistics display for all systems

STAT Local Transaction Statistics

8/2/2019 basis bi

15/15


2008 SAP AG

15

Feedback and Questions

Send any feedback by formulating an SAP customer message to component SV-SMG athttp://service.sap.com/messagein the SAP Service Marketplace.

Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission 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 ofother software vendors.Microsoft

, WINDOWS

, NT

, EXCEL

, Word

, PowerPoint

and SQL Server

are registered trademarks of

Microsoft Corporation.IBM

, DB2

, OS/2

, DB2/6000

, Parallel Sysplex

, MVS/ESA

, RS/6000

, AIX

, S/390

, AS/400

, OS/390

, and

OS/400

are registered trademarks of IBM Corporation.ORACLE

is a registered trademark of ORACLE Corporation.

INFORMIX

-OnLine for SAP and Informix

Dynamic ServerTM

are registered trademarks of Informix SoftwareIncorporated.UNIX

, X/Open

, OSF/1

, and Motif

are registered trademarks of the Open Group.

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 SunMicrosystems, Inc., used under license for technology invented and implemented by Netscape.SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch,BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registeredtrademarks of SAP AG in Germany and in several other countries all over the world. All other products mentionedare trademarks or registered trademarks of their respective companies.Disclaimer: SAP AG assumes no responsibility for errors or omissions in these materials. These materials areprovided as is without a warranty of any kind, either express or implied, including but not limited to, the impliedwarranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, orconsequential damages that may result from the use of these materials. SAP does not warrant the accuracy orcompleteness of the information, text, graphics, links or other items contained within these materials. SAP has nocontrol over the information that you may access through the use of hot links contained in these materials anddoes not endorse your use of third party Web pages nor provide any warranty whatsoever relating to third partyWeb pages.
http://service.sap.com/messagehttp://service.sap.com/messagehttp://service.sap.com/message

Date post:	05-Apr-2018
Category:	Documents
Upload:	satyakosaraju
View:	223 times
Download:	0 times

basis bi

Documents