BO BI4.0 Repository Diagnostic Tool User Guide (4.0 SP2 PDF

Business Intelligence Platform Repository Diagnostic Tool User Guide
SAP BusinessObjects Business Intelligence platform 4.0 Feature Pack 3
2012-03-19
Copyright 2011 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP
BusinessObjects Explorer, StreamWork, 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
other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports,
Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks of Business
Objects Software Ltd. Business Objects is an SAP company.Sybase and Adaptive Server, iAnywhere,
Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP
company. All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National product
specifications may vary.These materials are subject to change without notice. These materials are
provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only,
without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services
are those that are set forth in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an additional warranty.
2012-03-19
Contents
Chapter 1 Document History...................................................................................................................5
Chapter 2 Repository Diagnostic Tool.....................................................................................................7
Chapter 3 Using the Repository Diagnostic Tool.....................................................................................9

3.1 To use the Repository Diagnostic Tool.....................................................................................9
3.2 Repository Diagnostic Tool Parameters.................................................................................10
Chapter 4 Inconsistencies between the CMS and the FRS...................................................................17
Chapter 5 Inconsistences in the CMS metadata...................................................................................19
Appendix A More Information...................................................................................................................23
Index 27
3 2012-03-19
Contents
4 2012-03-19
Document History
Document History
The following table provides an overview of the most important document changes.
Version Date Description
SAP BusinessObjects Business Intelligence November, 2011 First release of this document.
platform 4.0
5 2012-03-19
Document History
6 2012-03-19
Repository Diagnostic Tool
The Repository Diagnostic Tool (RDT) is a command-line tool that scans, diagnoses, and repairs
inconsistencies that may occur between your Central Management Server (CMS) system database
and the File Repository Servers (FRS) filestore, or inconsistencies that can occur in the metadata of
InfoObjects stored in the CMS database.
During normal operations, it is unusual for the CMS system database to have inconsistencies. However,
inconsistencies may occur during unexpected events such as disaster recovery, back-up restoration,
or network outages. During these events, the CMS system database may be interrupted while performing
a task. This can cause inconsistencies with objects in the CMS system database.
The RDT scans the CMS system database and identifies inconsistencies in such objects as reports,
users, user groups, folders, servers, universes, universe connections, and other objects.
The RDT scans for two types of inconsistencies.

Object to file inconsistencies.
These are inconsistencies that can occur between InfoObjects in the CMS database and the
corresponding files in the File Repositories. For example, a file that is stored in the FRS may be
missing a corresponding object in the CMS system database.
InfoObject metadata inconsistencies.
These are inconsistencies that may exist in an InfoObject's object definition (metadata) in the CMS
database. For example, an InfoObject may reference another InfoObject that does not exist in the
CMS database.
The RDT peforms two functions, depending on the parameters that you provide when you run the tool:
It scans the CMS system database and FRS filestore, reports inconsistencies, and outputs a log file
in XML format with suggested actions to repair the inconsistencies.
It scans and repairs the inconsistencies identified in the CMS system database and FRS, and outputs
the actions taken to a log file in XML format.
7 2012-03-19
8 2012-03-19
Using the Repository Diagnostic Tool
The Repository Diagnostic Tool (RDT) is available on any machine with a Central Configuration Manager
(CCM) installed on it. This command-line tool scans, diagnoses, and repairs inconsistencies that may
occur between the Central Management Server (CMS) system database and the File Repository Servers
(FRS) filestore, or inconsistencies that may occur in an InfoObject's metadata.
It is recommended that you back up your CMS database and FRS filestore, and run the RDT against
the backed-up version while your SAP BusinessObjects Business Intelligence platform services are
down. If this is not possible, RDT can be run on an active database.
If you want to run RDT on an active database please keep the following considerations in mind:
RDT will use one database connection while it runs.
The RDT will only check the consistency of the database to the point in time where it started running.
Any inconsistencies that occur while the RDT is running will not be logged or fixed.
It is recommended that the host machine running RDT have memory above the normal system
recommendations available for processing RDT transactions:
A database of 50,000 info objects or less should have an additional 350 Mb available for
processing
A database of 50,000 to 400,000 info objects should have an additional 1.7 Gb available for
processing
A database of 400,000 to 1,000,000 info objects should have an additional 4 Gb available for
processing
RDT does not have to be run from your CMS server, running it on a sepeate machine can help
reduce any impact on system performance.
The tool may have a moderate impact on database performance while being run.
The RDT does not require the CMS service to be running, the RDT runs directly against the CMS
database.
3.1 To use the Repository Diagnostic Tool
1. If you are running the tool on a Windows computer, open a command window and run the following
command.
<INSTALLDIR>\SAP BusinessObjects Enterprise XI 4.0\win64_x64\reposcan.exe
<arguments>, where <arguments> is the list of parameters that you want to specify.
9 2012-03-19
2. If you are running the tool on a Unix computer, open a /usr/bin/sh compatible shell, and run the
following command.
.<INSTALLDIR>/sap_bobj/enterprise_xi40/<platform>/boe_reposcan.sh <argu
ments> where <platform> is either linux_x64, solaris_sparcv9, hpux_ia64, or aix_rs6000_64,
and <arguments> is the list of parameters that you want to specify.
The Repository Diagnostic Tool scans your repository for inconsistencies. Depending on the parameters
that you specify, it either diagnoses and logs inconsistencies, or it repairs inconsistences and logs the
action that it takes.
Repo_Scan_yyyy_mm_dd_hh_mm_ss.xml lists the inconsistencies that the tool finds. If you had the
tool repair the discrepancies that it finds, it also creates the file Repo_Re
pair_yyyy_mm_dd_hh_mm_ss.xml. This file details which objects are repaired and any orpahned
files that were deleted. If there are inconsistencies that could not be repaired these will also be listed.
The path to the log files can be specified by the outputdir parameter. If this parameter is not specified,
the default directory for the log files is <INSTALLDIR>\SAP BusinessObjects Enterprise XI
4.0\reposcan on Windows, and ./sap_bobj/enterprise_xi40/reposcan on Unix.
Note:
The application also provides a default XSL file that is used with the XML file to produce an HTML page.
The XSL file is stored in <INSTALLDIR>\SAP BusinessObjects Enterprise XI 4.0\reposcan
on Windows, and ./sap_bobj/enterprisexi_40/reposcan on Unix
For a list of the warning messages and recommended actions that the RDT takes when it finds
inconsistencies, see Inconsistences in CMS metadata and Inconsistencies between the CMS and FRS
.
Related Topics
Inconsistences in the CMS metadata
Inconsistencies between the CMS and the FRS
3.2 Repository Diagnostic Tool Parameters
The RDT accepts the parameters in the following table:

Note:
Command-line arguments override any parameter file entries while executing.
10 2012-03-19
Table 3-1: General Parameters
Optional or
Parameter Description
Mandatory
The type of driver used to connect to the CMS

database. Accepted values are:
db2databasesubsystem
maxdbdatabasesubsystem
dbdriver Mandatory
mysqldatabasesubsystem
oracledatabasesubsystem
sqlserverdatabasesubsystem
sybasedatabasesubsystem
The connection details that are used to connect to

the CMS database.
connect Mandatory For example: -connect

"UID=root;PWD=<pass
word>;DSN=<dsn>;HOSTNAME=<host
name>;PORT=<portnumber>"
Enter the cluster key for your BI platform deploy-

ment. For more information on cluster keys see
dbkey Mandatory
Securing BI Platform in the SAP BusinessObjects
Business Intelligence Platform Administrator Guide.
The file path of the Input File Repository Server.
Note:
inputfrsdir Mandatory The user account you are logged on with is used to
execute the command-line tool. It must have full
control to the file location.
The file path of the Output File Repository Server.
Note:
outputfrsdir Mandatory The user account you are logged on with is used to
execute the command-line tool. It must have full
control to the file location.
11 2012-03-19
Optional or
Mandatory
The file path where the RDT writes the log files.
The default value is <INSTALLDIR>\SAP

outputdir Optional BusinessObjects Enterprise XI
4.0\reposcan on Windows, and
./sap_bobj/enterprise_xi40/reposcan on
Unix.
The number of approximate errors to scan. This

helps ensure optimum performance. The upper
count Optional count is 2e31 - 1. A value of 0 is interpreted as the
entire repository.
The default value is 0.
Tells the RDT to repair all inconsistencies it may

find. The default behavior is to only report inconsis-
tencies but not to perform any repairs. If the -repair
parameter exists on the command line, the RDT
repair Optional reports and repairs all inconsistencies.
Caution:
This proccess will delete any orphaned objects or
files in the repository database.
Specifies whether the RDT scans the CMS and FRS

for inconsistencies. Acceptable values are True and
scanfrs Optional False.
The default value is True.
Specifies whether the RDT scans the CMS for incon-

sistencies between InfoObjects. Acceptable values
scancms Optional are True and False.
The default value is True.
12 2012-03-19
Optional or
Mandatory
Specifies the User ID to replace missing or invalid

IDs for scheduled objects. If no value is provided,
the RDT does not replace the invalid IDs. If the
submitterid Optional provided User ID doesn't exist in the CMS, the RDT
prompts for a valid ID.
This parameter is only used when the RDT operates

in repair mode.
Specifies the object in the CMS database to start

the scan for. For example, if you've already scanned
startid Optional the first 500 objects in your repository, you can set
-startid=501 to start a new scan at the 501st object.
Specifies the file path to a parameter file. The pa-

rameter file is a text file that lists each command-
line option and its values. The file should have one
parameter per line.
optionsfile Optional Note:
With this option, you can set all parameters in a Text
file as described above. Use this option to point to
the parameter file without entering the parameters
on the command-line.
This parameter is used when you copy the reposito-

ry database. You must run the tool on the newly
created copy, which will update the copy to prevent
it from clustering with the source system servers. If
the copy will not be able to communicate with the
source system, this is not necessary. It should only
syscopy Optional
be used with the mandatary parameters and not be
combined with other optional parameters in this list.
Note:
Be careful not run RDT with the syscopy parameter
on your source system.
The following parameters are used if the Repository Diagnostic Tool is running on an active clustered
CMS.
13 2012-03-19
Table 3-2: Using the RDT against a clustered CMS
Optional or
Mandatory
The port number that the RDT uses to commu-

nicate to the CMS. Accepts whole, positive
requestport Optional numbers. By default, the tool uses the value
from the operating system of the machine that
the RDT is running on.
Whether the RDT uses the numeric IP address

instead of the hostname for communication
between the CMS and the machine that the
numericip Optional RDT is running on. Acceptable values are True
and False.
The default value is False.
The ipv6 name of the machine that the RDT is

running on. Accepts a string.
ipv6 Optional
The default value is the hostname of the ma-
chine that the RDT is running on.
The ipv4 name of the machine that the RDT is

running on. Accepts a string.
port Optional
The default value is the hostname of the ma-
chine that the RDT is running on.
The number of threads to use. Accepts whole,

threads Optional positive numbers.
The following parameters are used when the RDT uses SSL to communicate with the CMS database
that it scans.
14 2012-03-19
Table 3-3: Using the RDT with SSL
Optional or
Mandatory
Specifies whether the tool should run in SSL

protocol Optional mode.
The only accepted value is ssl.
ssl_certdir Optional The directory that contains the SSL certificates.
ssl_trustedcertificate Optional The file name of the certificate.
ssl_mycertificate Optional The file name of the signed certificate.
The file name of the file that contains the pri-

ssl_mykey Optional
vate SSL key.
The file name of the file that contains SSL

ssl_mykey_passphrase Optional
passphrase.
Example:
The following example scans the CMS and FRS for both kinds of inconsistencies, and repairs the
inconsistencies that it finds.
reposcan.exe
-dbdriver mysqldatabasesubsystem
-connect UID=root;PWD=Password1;DSN=myDsn;HOSTNAME=myHostname;PORT=3306
-dbkey <cluster key>
-repair
-inputfrsdirC:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore\Input
-outputfrsdir C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI
4.0\FileStore\Output
15 2012-03-19
16 2012-03-19
The following table describes the inconsistencies that may between a Central Management Server
(CMS) data base and the File Repository Servers (FRS) that are recognized by the Repository Diagnostic
Tool (RDT). The table has 4 columns:
Warning Message
The warning message that is written to the scan and repair log files.
Inconsistency
An explanation of the inconsistency that the RDT finds for the object.
Recommendation
The recommended action that the RDT should take when it finds an inconsistency. This is found in
the scan log file.
Action
The action that the RDT takes to repair an inconsistency. This is found in the repair log file.
17 2012-03-19
Warning Message Inconsistency Recommendation Action
The object exists in the Allow the application The RDT removes
<Object Name> object
CMS database, but there to remove the missing the object from the
<Object Type> (Object
is no corresponding file in files from the object's CMS database.
ID: <ID>) is referencing
the FRS. file list.
some files that do not exist
in the FRS (<File Name>)
The file exists in the FRS, Please republish the When you republish
<File Name> exists in the
but there is no correspond- file. The application will the file, an object is
Input or Output FRS, but
ing file in the CMS not publish this file for created in the CMS
there is no corresponding
database. you. database.
InfoObject in the repository.
The size of the file does Allow the application The RDT updates
<Object Type> Object
not match the InfoObject to update the object the file size in the
<Object Name> (Object
file size. with the correct file CMS database.
ID <ID>) has a file size
size.
<Size>. The stored file size
is <Size> which does not
match the actual file size
<Size>.
The FRS folder is empty. Allow the application The RDT removes
<Folder Path> contains
to remove the directo- the empty directory.
no files.
ry.
18 2012-03-19
The following table describes the inconsistencies that can occur in the metadata of the objects that are
in a Central Management Server (CMS) system data base that are recognized by the Repository
Diagnostic Tool (RDT). The table has 4 columns:
Warning Message
The warning message that is written to the scan and repair log files.
Inconsistency
An explanation of the inconsistency that the RDT finds for the object.
Recommendation
The recommended action that the RDT should take when it finds an inconsistency. This is found in
the scan log file.
Action
The action that the RDT takes to repair an inconsistency. This is found in the repair log file.
19 2012-03-19
<Object Type> Object The object has a Allow RDT to move the The RDT moves the ob-
<Object Name> (Object missing or invalid object to the BO Repair ject and any child objects
ID: <Object Parent Object ID. folder. to a repair folder. Only the
Name><ID>)'s parent ob- administrator has access
ject is missing (Parent to this folder.
Object ID = <ID>).
<Object Type> Object The object has a Allow the RDT to assign The RDT assigns the val-
<Object Name> (Object missing or invalid the object to the Adminis- ue of the Administrator's
ID: <ID>)'s owner object Owner Object ID. trator. ID to the objects Owner
is missing (Owner Object ID.
ID = <ID>).
If you provide a value from

<Object Type> Object The object has a The recommendation that
the -submitterid parame-
<Object Name> (Object missing or invalid the RDT displays depends
ter, the RDT applies the
ID: <ID>)'s submitter ob- Submitter Object ID. on whether you've provid-
value for the object's sub-
ject is missing (Submitter ed a value for the -submit-
mitter ID.
Object ID = <ID> ). terid parameter.
If you provide this pa- If you don't provide a val-
rameter, the recom- ue for this parameter, the
mendation is Allow RDT takes no action.
the application to up- When you reschedule the
date the object with object, the CMS applies a
the provided submitter new ID.
ID.
If you don't provide this
parameter, the recom-
mendation is
Reschedule the object
or submit a user ID to
use to replace the in-
valid submitter ID.
<Object Type> Object The object's last Allow the application to When you reschedule the
'<Object Name>' (Object sucessful instance recalculate the property. object, the CMS automati-
ID: <ID>)'s last success- is missing or invalid. cally recalculates the ID.
ful instance property
refers to a missing object
(Object ID = <ID>).
20 2012-03-19
<Object Type> Object The object refer- Reschedule the object When you reschedule the
'<Object Name>' (Ob- ences a calendar with an existing calendar. object, the CMS applies a
ject ID: <ID>)'s calendar that doesn't exist. No action can be taken by calendar to the object.
object is missing (Calen- this application.
dar ID = <ID>).
<Object Type> Object The preferred serv- Reschedule the object When you reschedule the
'<Object Name>' (Object er does not exist. and choose an existing object, the CMS applies a
ID: <ID>) 's required server group. No action server group to the object.
scheduling server group can be taken by this appli-
is missing (Server Group cation.
Object ID = <ID>)..
<Object Type> Object The event or events Allow the application to The RDT removes the
'<Object Name>' (Object that this object is remove the missing missing events.
ID: <ID>)'s list of events waiting on does not events from the object's
to wait for contains miss- exist. list of events to wait for.
ing object(s) (Object ID(s)
= <ID>).
<Object Type> Object This object triggers Allow the application to The RDT removes the
'<Object Name>' (Object an event that does remove the missing missing events.
ID: <ID>)'s list of events not exist. events from the object's
to trigger contains missing list of events to trigger.
object(s) (Object ID(s) =
<ID>).
21 2012-03-19
<Object Type> Object Orphaned Access Allow the application to The RDT removes the
'<Object Name>' (Object Control entry. remove the missing princi- missing principal(s).
ID: <ID>) Access Control pal(s) from the object's
List references a missing Access Control List.
principal (Object ID =
<ID>).
<Object Type> Object The preferred serv- Allow the tool to remove The RDT removes the ob-
'<Object Name>' (Object er does not exist. the object's invalid entries jects missing entries from
ID: <ID>) has invalid from its Server Group list. the object's server group
Server Group entries list.
<Server Group
Entries>.
<Object Type> Object A specific user ac- Allow the application to The RDT consolidates the
<Object Name> (Object count has multiple consolidate multiple Fa- user's Favorites folders
ID: <ID>) has multiple favorites folders. vorites folders into a sin- into a single folder.
Favorites folders. gle Favorites folder.
22 2012-03-19
More Information
More Information
Information Resource Location
SAP product information http://www.sap.com
http://help.sap.com/businessobjects
Access the most up-to-date English documentation covering all SAP

BusinessObjects products at the SAP Help Portal:
http://help.sap.com/bobi (Business Intelligence)
http://help.sap.com/boepm (Enterprise Performance Management)
http://help.sap.com/boeim (Enterprise Information Management)
SAP Help Portal
Certain guides linked to from the SAP Help Portal are stored on the SAP
Service Marketplace. Customers with a maintenance agreement have
an authorized user ID to access this site. To obtain an ID, contact your
customer support representative.
To find a comprehensive list of product documentation in all supported
languages, visit:http://help.sap.com/boall.
23 2012-03-19
More Information
http://service.sap.com/bosap-support
The SAP Support Portal contains information about Customer Support

programs and services. It also has links to a wide range of technical in-
formation and downloads. Customers with a maintenance agreement
have an authorized user ID to access this site. To obtain an ID, contact
your customer support representative.
[Sean McGregor - Feb 2012] [Updating this More Information page to
align with new help portal goals. Product pages on help.sap.com now
contain links to release notes, install guides, PAM, and other support
portal materials so I've removed all this content below and merged the
SAP Support Portal "Online customer support" row that previously existed at the bottom into
this row which had the same URL above.]
Installation guides: https://service.sap.com/bosap-instguides
Release notes: http://service.sap.com/releasenotes
The SAP Service Marketplace stores certain installation guides, upgrade
and migration guides, deployment guides, release notes and Supported
Platforms documents. Customers with a maintenance agreement have
an authorized user ID to access this site. Contact your customer support
representative to obtain an ID. If you are redirected to the SAP Service
Marketplace from the SAP Help Portal, use the menu in the navigation
pane on the left to locate the category containing the documentation you
want to access.
http://www.sdn.sap.com/irj/sdn/bi-sdk-dev
Developer resources
https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibrary
SAP BusinessObjects articles on http://www.sdn.sap.com/irj/boc/articles

the SAP Community Network These articles were formerly known as technical papers.
https://service.sap.com/notes
Notes
These notes were formerly known as Knowledge Base articles.
Forums on the SAP Community

https://www.sdn.sap.com/irj/scn/forums
Network
http://www.sap.com/services/education
Training From traditional classroom learning to targeted e-learning seminars, we

can offer a training package to suit your learning needs and preferred
learning style.
24 2012-03-19
More Information
http://www.sap.com/services/bysubject/businessobjectsconsulting
Consultants can accompany you from the initial analysis stage to the
Consulting delivery of your deployment project. Expertise is available in topics such
as relational and multidimensional databases, connectivity, database
design tools, and customized embedding technology.
25 2012-03-19
More Information
26 2012-03-19
Index
D repository diagnostic tool (continued)
overview 7
document history 5
R parameters 9
repository diagnostic tool table of inconsistencies
inconsistencies recommendations 17, 19
diagnose and repair 7 using
object to file 7 Windows and Unix 9
scenarios 7
27 2012-03-19
Index
28 2012-03-19

BO BI4.0 Repository Diagnostic Tool User Guide (4.0 SP2 PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

BO BI4.0 Repository Diagnostic Tool User Guide (4.0 SP2 PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Business Intelligence Platform Repository Diagnostic Tool User Guide

SAP BusinessObjects Business Intelligence platform 4.0 Feature Pack 3

Chapter 1 Document History...................................................................................................................5

Chapter 2 Repository Diagnostic Tool.....................................................................................................7

Chapter 3 Using the Repository Diagnostic Tool.....................................................................................9

Chapter 4 Inconsistencies between the CMS and the FRS...................................................................17

Chapter 5 Inconsistences in the CMS metadata...................................................................................19

Appendix A More Information...................................................................................................................23

Version Date Description

Repository Diagnostic Tool

The RDT scans for two types of inconsistencies.

Using the Repository Diagnostic Tool

3.1 To use the Repository Diagnostic Tool

3.2 Repository Diagnostic Tool Parameters

The RDT accepts the parameters in the following table:

Table 3-1: General Parameters

The type of driver used to connect to the CMS

The connection details that are used to connect to

connect Mandatory For example: -connect

Enter the cluster key for your BI platform deploy-

The file path of the Input File Repository Server.

The file path of the Output File Repository Server.

The default value is <INSTALLDIR>\SAP

The number of approximate errors to scan. This

The default value is 0.

Tells the RDT to repair all inconsistencies it may

Specifies whether the RDT scans the CMS and FRS

The default value is True.

Specifies whether the RDT scans the CMS for incon-

The default value is True.

Specifies the User ID to replace missing or invalid

This parameter is only used when the RDT operates

Specifies the object in the CMS database to start

The default value is 1.

Specifies the file path to a parameter file. The pa-

This parameter is used when you copy the reposito-

Table 3-2: Using the RDT against a clustered CMS

The port number that the RDT uses to commu-

Whether the RDT uses the numeric IP address

The default value is False.

The ipv6 name of the machine that the RDT is

The ipv4 name of the machine that the RDT is

The number of threads to use. Accepts whole,

Table 3-3: Using the RDT with SSL

Specifies whether the tool should run in SSL

The only accepted value is ssl.

ssl_certdir Optional The directory that contains the SSL certificates.

ssl_trustedcertificate Optional The file name of the certificate.

ssl_mycertificate Optional The file name of the signed certificate.

The file name of the file that contains the pri-

The file name of the file that contains SSL

Inconsistencies between the CMS and the FRS

Warning Message Inconsistency Recommendation Action

Inconsistences in the CMS metadata

Warning Message Inconsistency Recommendation Action

If you provide a value from

Warning Message Inconsistency Recommendation Action

Warning Message Inconsistency Recommendation Action

Information Resource Location

SAP product information http://www.sap.com

Access the most up-to-date English documentation covering all SAP

Information Resource Location

The SAP Support Portal contains information about Customer Support