Professional Documents
Culture Documents
Guidelines for
Implementing SAP
NetWeaver BI Business
Content in a Customer
System
Contributing Speakers
Jie Deng
Product Manager, SAP AG
Scott Cairncross
Consultant BI RIG US, SAP Labs LLC
Amelia Lo
Consultant BI RIG US, SAP Labs LLC
Learning Objectives
Processes
Key Figures
Strategically and
operationally
Results of processes
Information Deployment
Roles, Tasks
Data Presentation
Data Analysis
Queries, Webtemplates
InfoProviders
Version
11
M(odified)
A(ctive)
D(elivery)
Delivery from SAP
SAP AG 2005, SAP TechEd 05 / IM204 / 10
11
11
11
11
Install BC
11
= active
D - Version
= delivered
M - Version
= modified
Exceptions:
Transfer structures do not have D-versions, they have shadow tables
Roles do not have D-Versions
A-version = SAP_BWC_* (only relevant for customer systems)
D-version = SAP_BW_* (will be delivered)
Only A version objects are exported from the development system
These objects are imported into the target system into either the A-Version or the
M-Version, depending on the object type. The M-Version objects are activated after
import. Examples are:
A -Version : Currency translation type, InfoObject Catalog
M -Version : InfoObject, InfoCube
SAP AG 2005, SAP TechEd 05 / IM204 / 11
Define content
model
Find predefined
content
Role 1
Key figures?
Reports?
InfoCubes?
DataSources?
.....?
Tasks
Extractors, InfoCubes,
DataSources...?
Analyze gaps
between
customer
requirements
and Business
Content
Use/enhance/modify SAP BI
Business Content
or implement customer Content
Top-Down Scenario
Top-Down Scenario:
Based on the requirements of the reports to analyze which other business
content objects (data flow downwards) are needed in this scenario.
Customer
Requirements
Material
Month
Sales Amount
Invoice Amount
100-100
06.2005
100,000 EUR
90,000 EUR
100-100
05.2005
150,000 EUR
100,000 EUR
......
......
....
.......
BI
Rough Content
model to be
defined
R/3
Sales Information
Invoice Information
Top-Down Scenario
Bottom-Up Scenario :
Based on the source information to analyze which other Business Content
objects (data flow upwards) are needed in this scenario.
To Be Defined
Rough Content
Model
Order Nr.
Material
Sales Amount
Quantity
4711
100-100
100,000 EUR
100 PC
4712
100-110
150,000 EUR
50 PC
......
......
....
.......
R/3
Customer
Requirements
SAP AG 2005, SAP TechEd 05 / IM204 / 16
InfoProviders, etc)
Sales Order
Mixed Scenario
Mixed Scenario:
The top-down-scenario and the bottom-up-scenario cannot be totally
separated in the real customer environment. Applying them in parallel
makes the process of defining content model more efficient.
Customer
Requirements
Material
Month
Sales Amount
Invoice Amount
100-100
06.2005
100,000 EUR
90,000 EUR
100-100
05.2005
150,000 EUR
100,000 EUR
......
......
....
.......
BI
To Be Defined
Rough Content
Model
R/3
Customer
Requirements
SAP AG 2005, SAP TechEd 05 / IM204 / 17
Sales Information
Invoice Information
Sales Order
Invoices
Newsletter:
Informs customers about important/critical changes/issues for each Content area.
Includes: NetWeaver Newsletter, could also be the newsletter which is sent from different
solutions (ERP, CRM etc).
How-To Paper:
Provides recommendation/tip/approach to modeling Customer Content. It is published in the
Service Marketplace.
BI Info-Index:
Lists specific topics. Relevant how-to-paper will also be linked here.
1.
1. Click
Click on
on the
the required
required
information
information
Content Browser
This Web template provides:
A user-friendly interface, including icons to indicate object types.
Options for analyzing Content related to one role or several roles
simultaneously.
Drilldown from the role to the related objects.
Metadata Repository information for a particular object that can be
reached by clicking on the icon next to the objects name.
Business
Blueprint
Realization
Go Live and
Roll-out
Maintenance and
Continuous
Improvement
Install/Activate SAP BI
Business Content
Match = Changes/modification will be kept and merged with the new SAP BW
Business Content version
Customizing settings to SAP BW Business Content is dominant in case, matching is not
possible !
Version
11
M(odified)
A(ctive)
D(elivery)
11
11
Install BC
(copy)
11
22
22
44
44
11
22
22
22
44
11
11
33
33
33
Modify BC
2nd delivery
from SAP
2nd match
BC
Version
11
M(odified)
A(ctive)
D(elivery)
11
11
Install BC
(copy)
11
22
22
33
33
11
22
22
22
33
11
11
33
33
33
Modify BC
2nd delivery
from SAP
2nd install
BC (copy)
Aggregate
Application
SourceSystem
DataSource (3.x)
Query View
Update Rule
Transformation (NetWeaver2004s)
InfoArea
Role
InfoSet
Web Item
InfoSet (Classic)
Web Template
InfoSet Query
Workbook
InfoPackage
InfoPackage Group
Object
Object is
is active,
active,
but
but there
there is
is aa newer
newer
D-Version
D-Version
Object
Object is
is active
active
Object
Object not
not active
active
A
A description
description
of
of the
the tool
tool can
can
be
displayed
be displayed in
in
aa separate
separate
window
window
1.
1. Select
Select one
one or
or
several
several objects
objects
3.
3. Start
Start
installation
installation ononline
line or
or in
in batch
batch
2.
2. Drag
Drag &
& Drop
Drop
objects
objects (or
(or use
use
context
context menu)
menu)
1.
1. Select
Select available
available objects
objects
with
with several
several trees
trees
InfoProvider
InfoObjects
InfoSources
1.
1. Select
Select available
available objects
objects
with
with several
several trees
trees
Roles
By Types
By Patches
InfoPackages
2.
2. Drag
Drag &
& Drop
Drop objects
objects
(or
(or use
use context
context menu)
menu)
Required
Required objects
objects are
are
collected
and
displayed
collected and displayed in
in
the
central
frame
the central frame
3.
3. Start
Start installation
installation ononline
line (or
(or in
in batch)
batch)
Objects
Objects that
that are
are not
not yet
yet
active
active or
or outdated
outdated are
are
installed
installed by
by default
default
InfoCubes,
InfoCubes, InfoObjects,
InfoObjects, ...
... can
can
be
be matched
matched with
with activated
activated
version
version (default)
(default)
Outdated
Outdated content
content is
is marked
marked
with
with aa date
date icon
icon
Objects
Objects already
already activated
activated and
and
identical
identical to
to the
the delivered
delivered ones
ones are
are
indicated
by
green
LED
indicated by green LED
Collect
Collect immediately
immediately
after
drag&drop
after drag&drop or
or
start
start manually
manually
Collected
Collected objects
objects can
can
include
include required
required ones
ones
only
only or
or objects
objects in
in the
the
dataflow
dataflow
As of NetWeaver2004s, the option in data flow before also collects the relevant DataSources:
Transactional DataSources
Master data of the InfoObjects contained in the InfoCube originate (characteristics of the
InfoProvider as well as their display and navigation attributes)
SAP AG 2005, SAP TechEd 05 / IM204 / 43
Object
Object Maintenance
Maintenance
Check
Check Category:
Category: D
D version
version
newer
than
A
version,
newer than A version, No
No
A
A version
version available
available
Support
Support Packages
Packages
You can activate the content via a role using data flow before. Objects which are in data
flow before (queries, InfoProviders, Update Rules, InfoSources, etc) will be collected
and activated
You can use the bottom-up approach, using the data flow as orientation (first the
data source, then up through the InfoSource, the info provider, and finally the query
elements). For this approach, you need to know exactly which objects are in the data
flow.
Use the In data flow before and after option only if you want to collect and install a
small number of objects.
Enhance Query
Enhance InfoProvider
InfoSource
(Not Mandatory as of
NetWeaver2004s)
DataSource
Enhance InfoSource
Extract Structure
Extractor
Enhance DataSource
Transaction Data
Master Data
Texts
Hierarchies
* As of NetWeaver2004s
SAP NetWeaver BI
DataSource
User exit
made on the
way to BI
Extraction Structure
Communication Structure
User exit
made in R/3
Transaction data:
Master data:
Texts:
Hierarchies:
EXIT_SAPLRSAP_001
EXIT_SAPLRSAP_002
EXIT_SAPLRSAP_003
EXIT_SAPLRSAP_004
Please note:
This option can be applied to every DataSource.
The content of enhanced fields is not visible in delta queue. These will be updated
during the upload into BI.
You can run Extractor Checker (transaction RSA3) for test purposes to verify
whether these enhanced fields were correctly updated.
A delta of these enhanced fields cannot be extracted to BI (only the after image can
be extracted to BI).
When changing an extraction structure, all data containers in the corresponding
data flow have to be empty!
SAP AG 2005, SAP TechEd 05 / IM204 / 50
No
Customer Append:
SAP offers the standard enhancement (e.g.MCS10001) for DataSources that are connected
to the logistic customizing cockpit (EXIT_SAPLMC*).
E.g. in SD area:
Header data:
Position data:
Please note:
EXIT_SAPLMCS1_001
EXIT_SAPLMCS1_002
This option can only be applied to DataSources which are available in the Logistic Customizing Cockpit.
Fields, that are dynamically calculated during transaction can not be enhanced via
the above function
modules.
Delta (before and after image) can be extracted into BI.
When changing an extraction structure, all data containers in the corresponding data flow have to be
empty!
SAP AG 2005, SAP TechEd 05 / IM204 / 51
Please note:
This option can be applied to every DataSource.
Enhanced fields, that are only relevant for statistical calculation (BI) are
also visible in the standard R/3 table.
Delta can be extracted into BI (before and after image).
When changing an extract structure, all data containers in the
corresponding data flow have to be empty!
Install
Do you enhance
transactional data or
master data?
Which object
Types are they?
Above InfoProviders
(Queries, Web
templates etc)
Transactional Data
Master Data
Apply
Enhancement/Modifi
-cation
Which kinds of
Enhancements?
Simply changing
attributes of
characteristics
Apply
Enhanceme
nts/Modification
Changing
compounding objects
of characteristics
Apply
Enhancement/Modification
. Adjustments for related
content objects have to be
done manually!
Copy or create
customer objects
Changing key
figures
Below InfoProviders
(Update Rules,
Transformation,InfoSo
urces)
Enhance or modify
SAP BI Business
Content objects.
Further automatic
content installation
should not be done!!
Demo
Demo
Top-Down Scenario
Top-Down Scenario:
Customer would like to compare the delivered quantity and billed quantity
based on the item level
Customer
Requirements
Delivery
Delivery
Item
Billing
Billing Item
Delivered
Quantity
Billed
Quantity
80000
10
123456
10
100 PC
99 PC
85000
10
123456
20
200 PC
200 PC
......
......
....
.....
......
.......
BI
InfoProviders, etc)
Rough Content
model to be
defined
R/3
Delivery Information
Invoice Information
Delivery
Item
Invoice
Invoice
Item
Delivered
Quan
Invoiced
Quan
Overall
Delivery
process.
status
80000
10
123456
10
100
99
85000
10
123456
20
200
200
......
......
....
.....
......
.......
...
Delivery Data
+ Billing Data
BI
Delivery Item
data
Create customer
append and
update it with SAPI
customer function
Billing Item
Data
R/3
Delivery Item Data
2LIS_12_VCITM
element
category
VGTYP
Processing
staus:
ZGBSTA
Implementation Steps
Prerequisite:
DataSources and related business Content Objects have been already
activated in R/3 and BI:
Transfer field VGTYP from communication structure to extraction structure
via Logistic Customizing Cockpit and then activate DataSource
2lis_13_VDITM.
With transaction se11 to create customer append for field ZGBSTA on the
extraction structure.
Use transaction CMOD to create a project. If the project is already available,
please assign the development to the project.
Use function module EXIT_SAPLRSAP_001 to update field ZGBSTA.
Activate the project.
Activate the DataSource via Logistic Customizing Cockpit (LBWE)or
DataSource Maintenance (RSA6).
Replicate DataSource 2lis_13_vditm into BI.
Create two DSO Objects which are connected to InfoSource 2lis_12_vcitm and
2lis_13_vditm.
Create one consolidated DSO object based on two line-item DSO Objects.
Create Query based on the consolidated DSO Object.
SAP AG 2005, SAP TechEd 05 / IM204 / 61
Scenario Description
Several subsidiaries of your company have extended requirements
for reporting.
After analyzing these requirements, you conclude that an
enhancement of the existing central data model in the SAP
Business Information Warehouse is appropriate.
You want to deliver the newly developed Content to the
subsidiaries in a straightforward way. To do this, you use the SAP
Add-On Assembly Kit.
Each subsidiary can decide which of the enhancements it wants to
use productively. In addition, you want to maintain the Content as
cost-effectively as possible. To achieve this you decide to develop
deliverable Content objects in the SAP Customer Content.
11
22
A(ctive)
11
11
D(elivery)
11
11
11
M(odified)
create
Subsidiary
Export (D Object)
activate change
import
M(odified)
11
44
A(ctive)
11
11
11
11
D(elivery)
11
Content activation
SAP AG 2005, SAP TechEd 05 / IM204 / 64
change
Export (D Version)
InfoObject
0MATERIAL
InfoObject
/ABC/IO01
InfoCube
/ABC/IC1
InfoObject
/ABC/IO01
Subsidiary
import
InfoCube
/ABC/IC1
InfoObject
0MATERIAL
SAP AG 2005, SAP TechEd 05 / IM204 / 65
InfoObject
/ABC/IO01
Advantages:
Good handling of dependencies between SAP Content and Partner
Content during creation of delivery
Development of Business Content in D versions
During import, changed objects are not overwritten
Steps
Required steps for developing certified
Partner Content
Registration for certification
mailto: icc@sap.com
Prerequisites: Namespace
Namespaces in the SAP Business Information Warehouse
SAP namespace (objects starting with 0)
Customer namespace (objects starting with A-Z)
Registered namespaces (/ABC/...)
Prerequisite: Namespace
SAP objects can be copied to the customer namespace or to the
registered customer namespace after activation and then
enhanced.
Advantage: After upgrade and activation these objects will not be
modified.
Disadvantage: Corrections or upgrades will not be applied to these
objects automatically and have to be done manually (can be very timeconsuming).
Prerequisite: Namespace
Namespace for the development of
BI objects
Reserving two namespaces in BI,
SAP Note 401778
Reserving a namespace in OLTP,
SAP Note 084282
RSOCONTENT
Restrictions:
SAP BI Content objects (D versions) cannot be changed.
RSA2 for dataSource development is not available in the source
system.
Integration of own documentation is not possible.
Certification
General Framework
Certification by department Integration and Certification Center (ICC)
Fee: 5000 EUR (EMEA) or 8000 USD (Americas)
Certificate issued and the tag line (logo) SAP certified integration awarded
Features
Tools for creating deliveries
Transactions for import already available
in customer systems
Import possible without access at
operating-system level
Benefits
Definition of installation prerequisites
and installation sequence
Simplified maintenance and consolidated
distribution of functional enhancements
SAP Core System
Business
blueprint
Realization
Work plans
Resource plans
Budget plans
Planning
Supports role assessment
Go live and
roll-out
Maintenance and
continuous
improvement
Business
blueprint
Realization
Pilot
implementation
testing
Pilot
Speeds up pilot development
Go-live and
roll out
Implementation
Speeds up application configuration and development
Supports cross-use and phased use
Testing
Predefined content is already checked against and
optimized for cross-component interdependencies
Faster configuration and development earlier ROI
SAP AG 2005, SAP TechEd 05 / IM204 / 81
Maintenance and
continuous
improvement
Project
preparation
Business
blueprint
Realization
Go-live and
roll out
Maintenance and
continuous
improvement
Monitoring
enhancements
Query
InfoSource
DataSource
Extraction Structure
Extractor
InfoCube
Greater
Difficulty
Greater
Ease
SAP AG 2005, SAP TechEd 05 / IM204 / 83
Roles
Web templates
Crystal Reports
Workbooks
Queries
Data mining models
Variables
Data targets
InfoCubes/MultiProvider
s/
Data Store Objects
InfoSources
InfoObjects
Process chains
DataSources
R/3 extractor programs
.............
Query
InfoCube
InfoSource
DataSource
DataSource
Extraction Structure
Extractor
Query
InfoCube
InfoSource
DataSource
Extraction Structure
Extractor
Non-SAP
DataSources
Query
InfoCube
InfoSource
DataSource
DataSource
Extraction
Extraction Structure
Structure
Extractor
InfoSource
DataSource
DataSource
Extraction
Extraction Structure
Structure
Extractor
InfoCube
InfoSource
DataSource
DataSource
Extraction
Extraction Structure
Structure
Extractor
General Recommendations
When And Why to Use The Standard
Get Content running quickly to gain experience.
By using all layers of the Business Information Warehouse you will
gain familiarity with the product at all levels of the BI Platform
developing product knowledge quickly.
Summary
SAP recommends the following procedure of implementing Business Content in a
customer system:
Define
tasks/projects/roles
Identify
Search
Use/enhance
You can use different channels depending on the stage of your project to search
for and find predefined SAP BI Business Content.
Business Content has different version. The customer version of Business
Content objects are not affected after installing upgrade or support packages.
When deciding whether to copy or use/enhance/modify SAP BI Business Content
object, consider the object type.
Customers and partners can develop and deliver their own content using SAP
namespace.
In general, SAP recommends you use or enhance Business Content objects
which are in the dataflow from DataSources to InfoProviders. You can use
Business Content query/Workbook/Web template as a template to create your
own objects based on the individual business requirements.
SAP AG 2005, SAP TechEd 05 / IM204 / 90
SAP BI Business
Content Details:
General
Information
developed by
Customers and
Partners
SAP Analytics
Solution content
Industry Content
BI Content 3.5.3
Add-On Details:
Business
Content
Support
Packages
Business
Content List
Availability
http://service.sap.com/ep-content
http://www.sdn.sap.com
http://www.iviewstudio.com
SAP AG 2005, SAP TechEd 05 / IM204 / 97
Further Information
Public Web:
www.sap.com
SAP Developer Network: www.sdn.sap.com Business Information
Warehouse
SAP Customer Services Network: www.sap.com/services/
NetWeaver Developers Guide: www.sdn.sap.com/sdn/developersguide.sdn
Questions?
Q&A
SAP AG 2005, SAP TechEd 05 / IM204 / 99
Feedback
Please complete your session evaluation.
Be courteous deposit your trash,
and do not take the handouts for the following session.
Thank You !
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.
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.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
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.