07 Business Content
description
Transcript of 07 Business Content
1
Product Management SAP NetWeaver, SAP AG
Business Content
2
This document includes several sections.
First we‘ll have an overview about what is standard Business Content and wheredoes business content belong to the scenario/scenario variants etc. As the next i would like to introduce the new content called content analyzer and contentbrowser which is delivered with the SAP NetWeaver 2004s, BI Content Add-On 2. finally, i would like to summarize the major features and functions of contentanalyzer and content browser.
OverviewContent AnalyzerContent BrowserSummary
3
OverviewContent AnalyzerContent BrowserSummary
4
So what is Business Content at all? Business Content delivers predefined, role-based and task-oriented information modesl. E.g. datasource, infosource, DataStore Object, InfoProviders, Queries, web templates etc. All these informationmodels provides users with the information which they exactly need to fulfill theirdaily tasks.
© SAP AG 2005
Business Content: Definition
Business Content DefinitionBusiness Content Definition
SAP BW Business Content delivers predefined, role-based and task-oriented information modelswithin BW.
SAP BW Business Content‘s objective is to make relevant information available to specific roles within an enterprise so as to provide these users with exactly the information they need to fulfill their daily tasks within their business.
5
© SAP AG 2005
Data Warehousing with SAP NetWeaver Business Intelligence –Architecture
DataSource
Opera-tionalDataStore Data Warehouse
Layer
ArchitectedData Marts
MasterData
InfoProvider
MetaData
&Docu-ments
Analytical Services
OpenHub
Service
Any Source
XMI Virtual-Provider
6
© SAP AG 2005
SAP NetWeaver 2004s BI Content Add-On 2
SAP NetWeaver 2004s BI Content Add-On 2 is based on the technology release NetWeaver 2004s BI.
This Content Add-On is released to the ramp-up customer on 24/10/2005. Mass shipment of this content add-on will start on the same date as SAP NetWeaver2004s BI.
About 43 business content scenarios are either newly developed, enhanced or improved within SAP NetWeaver 2004s BI Content Add-On 2. For details please refer to the business content list which is published on service.sap.com
7
© SAP AG 2005
Enterprise Data Warehousing – Variants & Processes
Modeling the EDW
Data ModelingMeta Data
&DocumentManage-
ment
Data Acquisition
Transformation
Data Distribution
Running the EDW
Administration & Monitoring
Data Flow Control
Performance Optimization
Information Lifecycle Management
UserManage-
ment
8
OverviewContent AnalyzerContent BrowserSummary
9
© SAP AG 2005
Functionalities of the Content Analyzer
Check programs are provided to customer to analyze inconsistencies and errors of customer defined information models (InfoObjects, InfoProviders etc).
With central transaction RSBICA you canSchedule these delivered check programs for the local system or remote system via RFC connectionCustomize the scheduling optionsDisplay the results of check programs by
Several grouping possibilitiesSeveral filter options Priorities
The results of the check programs can be loaded to the local orremote BI systems, in order to get a single point of entry for analyzing the BI landscape.
10
© SAP AG 2005
Customizing Settings of Content Analyzer
Check Type: Check ProgramJobname: Grouping of the check program
11
© SAP AG 2005
Scheduling of Check Programs
Check programs canbe scheduledfor the remote
BI System
12
© SAP AG 2005
Basic Functionality : Start
Starting the Analyzer by using SAP user menu (role: SAP_BW_Content_Administrator) or calling transaction RSBICA
13
© SAP AG 2005
Basic Functionality : Monitor
The priority fields provide an aggregated view to the objects listed in the result container.
In the “Last Update” field, the date and time of the oldest object which is available in the result container is displayed.
The date and time of the the objects will be set during the runtimeof the check programs.
The values in the monitor will change if the filter restrictions has been changed.
Result Container
Monitor
14
© SAP AG 2005
Basic Functionality : BI Content Analyzer -> Filter
15
© SAP AG 2005
Basic Functionality : Filter -> BW System
System B System C
System A
Local Check ResultTable
Consolidated System View
Local System View
DSO Object
16
© SAP AG 2005
Basic Functionality : Filter -> Check Category
InfoObject without InfoObject Catalog
Naming Convention Ignored
Object Collection : Collection Error
Object Collection : Temporary stored objects
Object Status : A version newer than D version
Object Status : D version newer than A version
Object Status : No A version available
Object Status : No D version available
Query Elements with double GUIDs
Roles having non-existing objects assigned to it
Routines with references to BW DDIC structures
*Inactive Transfer Structure
Check Categories
*not valid if the content is based on the NetWeaver2004s BI technology
17
© SAP AG 2005
Basic Functionality : Filter -> Priority
A priority can be assigned to every check category.
A default priority setting will be delivered by SAP.Can be overwritten from customers
The priority can be changed referring to special system types also.
Priority for Test SystemsPriority for Development Systems
4 priority settings are possiblevery highhighmediumlow
18
© SAP AG 2005
Basic Functionality : Filter -> Transports
System B System C
System A
Local Check ResultTable
Consolidated System View
Local System View
ViewData Store
Object
19
© SAP AG 2005
Basic Functionality : Filter -> Transports
20
© SAP AG 2005
Basic Functionality : Grouping
21
© SAP AG 2005
Basic Functionality : Grouping
Changing the tree hierarchy for individual needs.
22
© SAP AG 2005
Basic Functionality : Messages
Information and help regarding the error and proposals for solving the problem are available if the symbol ‘glass’ is displayed in the info column. The popup comes up after a double click to the row.
23
© SAP AG 2005
Business Content for Content Analyzer Architecture
RSCONTENTCHECK_E
QueryGetting detailed informationregarding the error via RRI
ReportRRI
Key : GUID
DataSource
Flexible updateIncons. Objects Messages
DataSource
0RS_OBJNAME
24
© SAP AG 2005
Business Content : IOBJ 0RS_OBJNAME
0RS_AUTHOR0RS_DATE0RS_DEVCLAS0RS_CHKGUID
Attributes
0RS_OBJNAME
0RS_OBJTYPE0RS_CCAT
CompoundedInfoObject
0RS_OBJNAME is the central object which is responsible forbuilding up the structure in the reporting.
25
To start the check program: RSBICA: execute the check reports
To have the customizing settings for check program: Settings : check execution
Start the check program: job name: the group of check types
RFC destination: check programs can be executed remotely with the currentcustomizing views. Results of the check programs are stored locally. RSBICA show the result locally(current system, table rscontact) or the ODS object result(remote results). Only if the data are loaded centrally, then the the web reporting ispossible. The execution of check program can be started remotely. Thecustomizing settings are not necessary for transport.
© SAP AG 2005
Business Content : Query / Template
26
Summary
© SAP AG 2005
APPENDIX For Check Programs
27
© SAP AG 2005
Overview of Check Programs
The Check programs analyze the system in order to find inconsistencies and error for BI Content objects.
The check programs can be started in batch mode only.
The check programs can be executed in sequence or in parallel.
Only problematic objects will be stored for BI Content Analyzerreporting .
No inverse reporting (all objects which are ok) is possible.
No narration
on this slide
28
© SAP AG 2005
General : Check Types and Check Category
You have to differentiate between Check Types and Check Categories.
Check Types
The check type will be selected in order to schedule a check program. Several check categories could be assigned to the same check type.A check type has a 2 character ID.
Check Category
The check category is used in the BI Content Analyzer in order to differentiate the results provided by the check programs. The check category is visible for the end user.A check category has a 3 character ID.
No narration
on this slide
29
© SAP AG 2005
Status Checks : General
Status Checks ( ID : ST) SAD A-version newer than D-versionSDA D-version newer than A-versionSNA No A-version availableSND No D-version available
The status checks compares the content time stamp of the A-and D-version of a BW object.
The content time stamp is assigned to every BW object.
The content time stamp will be created if an object has been activated/saved in a BW Content Development system.
The content time stamp can be changed if an object has been changed in a BW Content Development system.
No narration
on this slide
30
© SAP AG 2005
Status Checks : A-version newer than D-version
Development System
Inconsistent object statusDeveloper does not see the object version which will be delivered.Reason : An older object has been imported to the system in D-versionReason : The D-versions are not saved correct. Maybe incorrect system settings.
Test System
Inconsistent object statusIncorrect object version are visible for testersReason : Imports of A-versionsReason : Somebody changed the system settings to dev. system .
No narration
on this slide
31
© SAP AG 2005
Status Checks : D-version newer than A-versionNo A-version available
A newer version of the object is available in the D-version.
Possible reasons
The content installation failed.
The content installation did not happen up to now.
Unexpected imports to the system.
No narration
on this slide
32
© SAP AG 2005
Status Checks : No D-version available
Check will be executed in content development systems only.
Development system
Reason : Writing of D-versions does not work correct. Check system settings
Reason : Delete imports.
Test systems
In test systems it´s normal that D-versions are not written. Therefore the check will not be executed.
No narration
on this slide
33
© SAP AG 2005
Collection Checks : General
Collection Check ( ID : CE) CCE Collection ErrorCCO Temporary stored objects
The collection check is a simulation of the object collection which can be started by using transaction RSOR.
The intention is to identify objects with references to missing or locally stored objects.
No narration
on this slide
34
© SAP AG 2005
Collection Checks : Collection Error
Check should be executed in test systems.
Objects with references to missing objects will be detected.
The object collection by using transaction RSOR will end in an error message.
InfoProvider
UpdateRule Reference to a generated table
Existing Objects Non-existing Objects
Data Store Object /BIC/.....
No narration
on this slide
35
© SAP AG 2005
Collection Checks : Temporary stored objects
Check should be executed in development systems.
Objects with references to objects stored on package $TMP
There is no problem in the development systems. The problemwill be visible after a transport to a new system. The objects stored onpackage $TMP are not available in the target system.
InfoProvider
Objects assignedto normal packages
Objects stored on package $TMP
Query
InfoObject which is saved on &TMP
No narration
on this slide
36
© SAP AG 2005
Other Checks
• Inactive Transfer Structure * (not valid if the content is based on BI 7.0 technology)
• InfoObject without InfoObject Catalog
• Naming Convention Ignored
• Query Elements with double GUIDs
• Roles having non-existing objects assigned to it
• Routines with references to BW DDIC structures
No narration
on this slide
37
© SAP AG 2005
Inactive Transfer Structure
The transfer structure has been changed and is not active at the moment.
Reason
Manual change of the transfer structure.
Replication of assigned DataSources.
Problems
Data loading fails.
Imports of related objects, for example Update Rules fails also.
Solution
Activate the transfer structure again. RSA1 InfoSourceNo narration
on this slide
38
© SAP AG 2005
InfoObject without InfoObject Catalog
An InfoObject is not assigned to an InfoObject Catalog.
Reason
Missing assignment during InfoObject creation.
InfoObject Catalog is not transported.
Problems
Object is assigned to hierarchy NODESNOTCONNECTED, only
Does not follow the Content recommendations.
Solution
Assign the object to an InfoObject Catalog.No narration
on this slide
39
© SAP AG 2005
Naming Convention Ignored
Naming Conventions can be defined in the customizing.
Settings-> Global Settings
Reason
The object is assigned to a package which is maintained in the customizing, but does not follow the naming convention.
Solution
Change the name of the object according to your naming convention.
No narration
on this slide
40
© SAP AG 2005
Query Elements with double GUIDs
Due to cross transport or during the double maintenance phase, itcould be possible that query elements have more than one GUID forthe same technical description (COMPID) )
COMPUID (GUID)COMPID (Decription)
Query Elementgenerated unique key
123456789
System A
System B
System C
Transport
Sales Analysis
987654321
Sales Analysis
123456789
987654321
Sales Analysis
Query execution chooses the objects by random.123456789 or 987654321
Leads to inconsistencies if query definition changes.
No narration
on this slide
41
© SAP AG 2005
Roles having non-existing objects assigned to it
Queries, Views or Templates can be assigned to a role.
If object itself was deleted, but the assignment to the role was not deleted, this leads to the inconsistencies.
Reason
Deletion of objects.
Problem
Inconsistent object status.
Collection errors are possible
Solution
Delete the assignment to the role definition in transaction PFCG.
No narration
on this slide
42
© SAP AG 2005
Routines with references to BW DDIC structures
References to BW DDIC structure are not allowed for bwcontent delivery.
f.e. LT_SALES LIKE standard table of /BI0/SALES not allowed
Problem
Activation problems, if the routine will be activated before the referenced object is activated.
For A-version, importing problems if the referenced object is not available in the system.
No narration
on this slide
43
© SAP AG 2005
Routines with references to BW DDIC structures
Solution
Dynamic programming.
*.. data definitions for internal table and workareadata: lt_data type ref to data.
field-symbols: <t_data> type standard table.
*.. store name of structure (infocube SALES) as stringconstants: c_tabname type rstlogotab value '/BI0/FSALES'.
*.. create internal table and assign it to <t_data>create data lt_data type table of (c_tabname).
assign lt_data->* to <t_data>.No narration
on this slide
44
OverviewContent AnalyzerContent BrowserSummary
45
© SAP AG 2005
Concept of Content Browser
This Standard Business Content called Content Browser provides the reporting functionalities to enable end user discover information about the customer-defined content and SAP delivered content in the system. It helps to answer the following question:
Which SAP Business Content is available in a given area?
Which SAP Business Content is in used in the customer Business Intelligence System?
Which customer-defined content exists in the customer Business Intelligence System?
46
© SAP AG 2005
Data Flow in BI Content 3.5.3 Add-On
Relevant BI Object types are modeled as the different master data, and the relationship between these objects are modeled as transactional data.
0BCT_CB_1(Content Browser:
Object Relationships)
Query/View Attribute, text
Web Template/Wor
kbook Attribute, Text
View’s Source Query Text
Role Folder Attribute, Hierarchy,
Text
DataSourceAttribute ,Text
InfoArea Text
InfoProviderAttribute, Hierarchy,
Text
Application Components
Text
Master Data Master DataTransactional Data
DataSourceType Text
InfoSourceAttribute
47
© SAP AG 2005
Data Flow in SAP NetWeaver 2004s BI Content Add-On vers. 2
BI Object(Query,
InfoProvider, DataSource, Update Rule
etc)
Master Data Reporting
0TCTBWOBJCT_ATTR 0TCTBWOBJCT_TEXT 0TCTBWOBJCT_Hier
All BI Object types (DataSources, InfoProviders, Queries etc) and their relationships are modeled as the generic and consistent Master Data ‘BI Object’.
48
© SAP AG 2005
Content Browser in SAP NetWeaver 2004s BI ContentAdd-On vers. 2
With the role ‘SAP_BW_CONTENT_BROWSER’ you can access the content browser reports to discover SAP delivered standard business content and the existing customer-defined content in customer system.
Due to the underlying technology change and the modeling flexibility, SAP redesigned the content browser and will deliver it to customer with NetWeaver 2004s BI Content Add-On vers. 2.
There are no direct ‘migration’ between these two content models. We recommend that you apply the content browser which is delivered with NetWeaver2004s BI Content Add-On version 2. In case that you have already applied the Content Browser with BI Content 3.5.3 Add-On, you need to do the manual adjustment to migrate to the redesigned content Browser.
49
© SAP AG 2005
Delivered Webtemplates: Business Content By Role
This Web Template provides:
user-friendly interface, including icons to indicate object types.
possibilities to analyze Content related to one role or several roles simultaneously.
drill down from the Role to the related objects.
Metadata Repository information for a particular object which can be reached by clicking on the icon next to the object’s name.
50
© SAP AG 2005
Delivered Webtemplates: InfoProviders by InfoArea
This Web Template provides information about InfoProviders by InfoArea
It provides user-friendly interface, including icons to indicate object types.
It allows you to drill down from the InfoArea to related InfoProviders.
The Metadata Repository information for a particular object can be reached by clicking on the icon next to the object’s name.
51
© SAP AG 2005
See where Business Content is and isn’t used:
Overview by InfoArea with Drill down to
individual InfoProviders
With this report user can get the overview about
Number of InfoProviders which are active in the system
SAP- delivered InfoPorviders and customer- defined InfoProviders withtheir technical name
52
OverviewContent AnalyzerContent BrowserSummary
53
© SAP AG 2005
Summary
Content Analyzer and Content Browser are delivered with SAP NetWeaver 2004s, BI Content Add-On version 2, which will help customereffektively administrate, monitor and improve quality of content and also provide customer the statistical overview about the content objects.
Content Analyzer:
As Business Content, as well as a tool helps
IT Department monitor content quality in complex system landscape
Content developer find out and correct the errors and inconssitencies
Content Browser:
As Standard Business Conent helps
IT Department get a clear overview about the content and the usage of content
Customers or consultants to easily navigate ( find out) the right Business Content
54
© SAP AG 2005
Copyright 2005 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, Outlook, and PowerPoint 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, and Informix are trademarks or registered trademarks of IBM Corporation in the United States 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, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C 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. MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver 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 the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.