Installing Standard Business Content in BI.

Goto Adminitsration and select the BI Content in right panel,below screen will
appear.In this case we are trying to install FIAP ODS: 0FIAP_O03.
In the below screen select Grouping as IN DATAFLOW BEFORE AND AFTWDS.
With the in dataflow before and aftrwds option, objects that are interdependent will be
collected and activated together.
Collection mode: collect automatically option

Drag the STANDARD ods into right panel. After the process is done the below
screen appears.
Next step is to Install (Activate).Below screen gives different options available in the
Install drop down list.
Use the Install in background option when activating a large object.

Screen before installation:

After installation is completed.Generally the installed Object can be found in the
standard Financial accounting infoarea at the infoprovider.
In our case it has been dragged into our infoarea tomcruise.below is the screen shot
before and after installation with respect to our infoarea tomcruise.

After installation complete below is the screen with respect to our infoarea
tomcruise.
GENERAL INFO:

Collection Object Grouping

Use
The Grouping function allows you to choose which BI Content objects you want to collect. By
default, only those objects are collected that are absolutely necessary in order to activate an
object. If you want to collect the objects that are required to activate all the objects that are
collected at the same time, you can select these objects accordingly.

Features
You can group objects in the following ways:
Required Objects Only
Only those objects that are really required for the action (copying or transporting the selected
objects) are taken into account (minimal selection).

The following applies for InfoObjects and InfoCubes, for example:

■ With InfoObjects, the corresponding attributes are collected, as are the
application components to which the InfoObjects are assigned.
■ With InfoCubes, the InfoObjects contained in the InfoCube are collected
along with the InfoArea.
Data Flow Before
The objects that pass data to a collected object are collected.

If your start point is an InfoCube, all the objects that are in the data flow before the
InfoCube, and are therefore necessary for providing data to the InfoCube, are
collected. This includes transformation rules and InfoSources, for example.
In order to activate these objects, all the corresponding objects required for these
objects have to be collected in addition. To activate an InfoSource, you may also
require InfoObjects that are not contained in the InfoCube and have therefore not
been collected yet. However, the objects that are in the data flow before the
additional objects are not collected.
The following figure illustrates this in more detail:
Note the following when activating DataSources:
DataSources are activated remotely from the BI system and are thus subject to an authorization
check. You need role SAP_RO_BCTRA in the source system. For information about how to
assign the role, see Changing Standard Roles. Authorization object S_RO_BCTRA is checked.
This authorization applies to all the DataSources in a source system.
The D versions of the DataSources are available in the BI system if they were replicated to the BI
system when you connected to the source system or replicated an application component or
source system.
In BI, the system collects the DataSources for those objects that are one level (at most) before
the selected object. This is sufficient to provide transaction and master data.

For example, if this object is an InfoCube, the following DataSources are collected:
● DataSources from which the corresponding InfoSource supplies
transaction data to the InfoCube (see above graphic)
● DataSources that contain the original master data of the InfoObjects
contained in the InfoCube (characteristics of the InfoProvider as well
as their display and navigation attributes). No DataSources are
collected for the attributes of these InfoObjects.
When the objects are collected, the system checks the authorizations remotely. If you do not
have authorization to activate the DataSource, the system produces a warning.
If you install BI Content in the BI system in the active version, the results of the authorization
check are taken from the cache.
If you do not have the necessary authorization, the system produces a warning for the
DataSource. Errors are shown for the corresponding source-system-dependent objects
(transformations, transfer rules, transfer structure, InfoPackage, process chain, process variant).
In this case, you can use Customizing for the extractors to manually install the required BI
Content DataSources in the source system, replicate them in the BI system, and then transfer the
corresponding source-system-dependent objects from BI Content into BI again.
If you have the required authorization, the active versions of the DataSources are installed in the
source system and replicated in the BI system. The source-system-dependent objects are
activated in the BI system.

BI Service API with Release SAP NetWeaver 2004s (Plug-In Basis 2005.1) in the
source system and BI is prerequisite to remote activation. If this prerequisite is not
fulfilled, you have to activate DataSources in the source system and replicate them
in BI afterwards.
Data Flow Afterwards
The objects that receive data from a collected object are collected.

If your start point is an InfoCube, all the objects that are in the data flow after the
InfoCube, and are therefore reporting objects that display the data stored in the
InfoCube, are collected. This includes queries and Web templates, for example. In
order to activate these objects, all the corresponding objects required for these
objects have to be collected in addition. To activate a role, you may also require
additional workbooks that are based on other InfoCubes. However, the objects that
are in the data flow after the additional objects are not collected. The additional
workbooks cannot be used for reporting unless they are installed from the BI
Content by some other means.
The following figure illustrates this in more detail:

Data Flow Before and Afterwards

All objects that pass or receive data are collected.

For example, when using an InfoCube, the objects necessary for activating the
InfoCube are collected together with other objects that are required for activating
 those objects collected as well. This includes objects positioned both before and
after the InfoCube in the data flow.
Based on the InfoCube, the evaluation string and all incoming data streams are then
activated. In this way the data streams are completed, enabling a complete
evaluation in the workbooks.

If you set the In Data Flow Before and Afterwards or In Data Flow Afterwards
indicators, the system does not collect all objects. This is due to performance
reasons.
Optional Objects
In the context menu, you can select the Add Optional Objects option. The where-used list is
called and all objects that use the selected object are added. In addition, all objects required for
these objects are collected. Otherwise it may not be possible to activate these objects.
For example, an InfoCube can be used by transformation rules and queries.

Procedure
...

The following is an overview of the individual steps in the procedure: These steps are
subsequently explained in more detail.
1. Navigate to the Data Warehousing Workbench to install BI Content (object selection,
installation settings, starting installation).
2. Assign relevant source systems.
3. Group objects to be included, determine mode of collection for the objects.
4. Determine the view of the objects.
5. Transfer the objects to Collected Objects.
6. Check the settings for the Collected Objects with reference to the Install,Match or
Copy and Active Version Available functions.
7. Make settings in the selection list and Transfer.
8. Correct errors.

1. Navigate to the Data Warehousing Workbench to Install BI Content

...

From the main Business Intelligence menu, choose Modeling → Data Warehousing
Workbench: BI Content. If you are already in the Data Warehousing Workbench, select
the BI Content functional area by clicking on the corresponding pushbutton in the left-
hand navigation window, or by choosing the path Goto → Install BI Content.
The Data Warehousing Workbench for installing BI Content has three navigation
windows:
• ● In the left-hand window you determine the view of the objects in the middle area
of the screen.
• ● In the middle window, you select the objects that you want to activate.
• ● In the right-hand window, you make the settings for installing the BI Content.
The right-hand window also contains an overview of the objects you have selected,
and it is here that you start installation of BI Content.
 In the Data Warehousing Workbench, you use the Navigation Window On/Off
pushbutton in the toolbar to display or hide the left-hand navigation window. The
rest of this section assumes that the left-hand navigation window is displayed.
2. Assign Relevant Source Systems
If you want to assign a source system, select the Source System Assignment
function. The Choose Source System by Default? dialog box appears.
Select one or more source systems by setting the corresponding indicators in the Default
Assignment column.

Only ever select the source systems that you really need, otherwise you may have
to wait unnecessarily when objects are collected.

The assignment of the source system is only relevant for source-system dependent
objects (such as transfer rules, file DataSources, and InfoPackages). If more than
one source system is available, only those objects assigned to the specified source
system are collected ready for the transfer. Objects that have not been assigned to
the specified source systems are ignored.
For more information about the special features inherent in activating process
chains that can reference source-system dependent objects, see the Customer
Content documentation, under Process Chains and Process Variants.
If you do not select a source system, all the source systems are assigned automatically.
You can change your selection later using the Source System Assignment
function.
3. Group Objects To Be Included, Determine Mode of Collection for Objects
Make the settings you require from the following selection lists on the right-hand side of
the screen:
• ● Grouping
Choose the objects that you want the system to include. The groupings combine the
objects from a particular area. You have the following options:
• ○ Only Necessary Objects (default setting)
• ○ Data Flow Before
• ○ Data Flow Afterwards
• ○ Data Flow Before and Afterwards
For more information about groupings, see Collection Object Grouping.

If you change the default setting (Only Necessary Objects), the new setting
becomes the default setting for your user.

The grouping selection has an impact on system performance during BI Content

installation. For more information, see View of Objects and Object-Specific
Recommendations.
• ● Collection Mode
 Select how you want to collect the objects:
• ○ Collect Automatically (default setting): The data is collected when the objects
are selected.
• ○ Start Manual Collection: The data is only collected when you choose
Collect Dependent Objects.

Set the collection mode to Start Manual Collection. You can select all the objects
without having to wait.
4. Determine View of Objects
In the left-hand navigation window, specify how you want the objects to be displayed.
For more information, see View of Objects and Object-Specific Recommendations.
5. Transfer the Objects to Collected Objects
In the central area of the screen, select the objects that you want to install, and drag and
drop them into the right-hand Collected Objects area of the screen.

The Find Object function allows you to use strings of characters (for example,
0CUST) or wild card searches (for example, 0CUST_*B) to search for objects.
Input help is available for every type of object: Double-click on the Select
Objects icon in the tree structure of the corresponding object type to display the
Input Help for Metadata screen. Select the required objects. Choose Transfer
Selection.

If you implement BI Service API Releases lower than 7.0 in the source system, you
have to install the active version of the BI Content DataSources in the source
system and replicate them in the BI system before you can use them for transferring
data into BI. For more information, see Installing BI Content DataSources and
Metadata Upload for SAP Systems.
In the Collected Objects area of the screen, the system displays the selected objects and
all dependent objects. Collected objects are stored by default in the repository cache. This
reduces the time it takes to access these objects when you want to use them again.

When you transfer objects into the Collected Objectsarea of the screen, these
objects are also added to the tree structure of the corresponding object type in the
central area of the screen and stored for your user. This personal object list can
be called up each time the program is restarted.
If you want to remove objects from your personal list, select the objects that you
want to remove and choose the Remove Object from Display option from the
context menu or click on the icon.
Objects that are listed in several tree structures can only be changed in the place where
they first appear. All additional instances of these objects are grayed out so you cannot
modify them.
6. Check Settings for Collected Objects
Check the following columns in the Collected Objects area of the screen:
• ● Install
The following BI Content objects are highlighted in this column by default:
• ○ Objects that are being transferred for the first time. There is not an active
version of these objects in the system.
• ○ BI Content objects that have been redelivered in a new version. These objects
can be identified by the Content time stamp in the corresponding object tables.
When setting this indicator, check whether the checkbox refers to a folder of an individual
object: If the checkbox refers to a folder, the indicator is set for all the objects that belong to
this folder. If the checkbox refers to an individual object, the indicator is set for a single
object and the indicators for the other objects in the folder are not changed. The same
applies if you deselect this indicator.
In the context menu, the following options are available for the installation:
...

a. Install All Below

The object in the selected hierarchy level and all objects in the lower levels of
the hierarchy are selected as to Install.
b. Do Not Install All Below
The Install indicators are deselected for the object in the selected hierarchy
level and all objects in the lower levels of the hierarchy.
• ● Match (X) or Copy
If the SAP delivery version and the active version can be matched, a checkbox is displayed
in this column.
With the most important object types, the active version and the SAP delivery version can
be matched.

Note that the InfoSource TRCS supports the match, but the 3.x InfoSource ISTD
does not.

From a technical point of view, the SAP delivery version (D version) is matched
against the M version. As in most cases the M version is identical to the active
version (A version) in a customer system, this is referred to as a match between the
D and A versions for reasons of simplification.
When a match is performed, particular properties of the object are compared in the A
version and the D version. First it has to be decided whether these properties can be
matched automatically or whether this has to be done manually. If you are sure that the
object will be used in the same way after you install BI Content, you can perform an
automatic match for those properties. When performing matches manually you have to
decide whether the characteristics of a property from the active version are to be retained,
or whether the characteristics are to be copied from the delivery version.

Example of an automatic match:

Additional customer-specific attributes have been added to an InfoObject in the A
version. In the D version, two additional attributes have been delivered by SAP that
do not contain the customer-specific attributes. To be able to use the additional
attributes, the delivery version has to be reinstalled from BI Content. At the same
time, the customer-specific attributes are to be retained. In this case, you have to
set the indicator (X) in the checkbox. After installing the BI Content, the additional
attributes are available and the customer-specific enhancements have been
 retained automatically. However, if you have not checked the match field, the
customer-specific enhancements in the A version are lost.

Example of a manual match:

An InfoObject has a different text in the A version than in the D version. In this case
the two versions have to be matched manually. When BI Content is installed, a
details screen appears which asks you to specify whether the text should be
transferred from the active version or from the D version.

The Match indicator is set by default to prevent the customer version being overwritten
unintentionally. If the BI Content of the SAP delivery version is to be matched against the
active version, you have to set the Install indicator separately.
The active version is overwritten with the delivery version if:
• ○ The match indicator is not set, and
• ○ The install indicator is set.
In other words, the delivery version is copied to the active version.

If the Install indicator is not set, the object is not copied or matched. In this case, the
Match indicator has no effect.
In the context menu, two options are available:
...

a. Merge All Below

The object in the selected hierarchy level and all objects in the lower levels of the
hierarchy are selected as to Match.
b. Copy All Below
The Match indicators are removed for the object in the selected hierarchy level and
all objects in the lower levels of the hierarchy. If the Install indicator is also set, these
objects are copied from the delivery version to the active version.
The most important properties that are taken into account when versions are
matched are listed below.
When referring to InfoObjects it is important to differentiate between:
■ Characteristics
■ Time characteristics
■ Key figures and
■ Units
Valid for All InfoObjects Named Above:

Properties Matched Automatically: Properties Matched Manually:

• ● Texts • ● Attribute only (indicator)
• ● Description • ● Short and long text (description)
If texts/descriptions in the delivery • ● Time dependency of attributes
version do not yet exist in the active • ● Transfer routine
version, they are transferred.

Valid for Characteristics

Properties Matched Automatically: Properties Matched Manually:

• ● Compounding
New InfoObjects are included in
compounding
• ● Referenced characteristic
Reference characteristics are
transferred automatically. A warning is
issued.
• ● Attributes / navigation attributes
New attributes are included.
If an attribute is added by the
customer, the settings for this attribute
are transferred (for example, F4
sequence).
• ● Application components
If the entry for the active version is
initial, the delivery version is used.
Valid for Key Figures
Properties Matched Automatically:
Valid for Units
Properties Matched Automatically:
When referring to InfoProviders it is important to differentiate between:
• ○ MultiProviders
• ● BEx display
• ● Characteristic constants
• ● Default member
• ● Authorizations (indicator and
field)
• ● Selection (CHASEL)
• ● InfoObject is document attribute
• ● Data type
• ● Length
• ● Output length
• ● Conversion routine
• ● Lower case allowed (indicator)
• ● Contains master data (indicator)
• ● Master data is authorization
relevant (indicator)
• ● Export DataSource (indicator)
• ● F4 query design
• ● F4 query runtime
• ● Check DataStore object
• ● Contains text tables (indicator)
• ● Texts are language-dependent
(indicator)
• ● Short, medium and long texts
exist (each with indicator)
• ● Default currency
• ● GIS attribute
• ● Hierarchies exist (indicator)
Properties Matched Manually:
• ● Type of key figure
• ● Fixed unit
• ● Fixed currency
• ● Aggregation
• ● Exception Aggregation
Properties Matched Manually:
• ● See the table above (Valid for
Characteristics), if these properties
are also relevant for the units.
 • ○ InfoCubes
• ○ DataStore objects and
• ○ InfoObjects
InfoObjects are discussed above (see the first table Valid for All Objects Named
Above).
Valid for All InfoProviders Named Above:

Properties Matched Automatically: Properties Matched Manually:

• ● New InfoObjects • ● Manual matching is not
If InfoObjects in the delivery version do necessary.
not yet exist in the active version, they
are transferred.

Valid for MultiProviders

Properties Matched Automatically: Properties Matched Manually:

• ● New InfoProviders • ● Manual matching is not
If InfoProviders in the delivery version necessary.
do not yet exist in the active version,
they are transferred.

Valid for InfoCubes

Properties Matched Automatically: Properties Matched Manually:

• ● New dimensions • ● Manual matching is not
If dimensions in the delivery version do necessary.
not yet exist in the active version, they
are transferred.
With the InfoObject catalog object type, InfoObjects that are assigned to a catalog in the
delivery version are transferred to the active version automatically. Manual matching is not
necessary.
With the transfer rule object type, those objects that exist in the delivery version but are not
yet contained in the active version (for example, additional attributes) are added
automatically when the match is performed. Manual matching is not necessary.
With the process chain object type, those objects that exist in the delivery version but are
not yet contained in the active version (for example, additional objects in the process chain)
are added automatically when the match is performed. Manual matching is not necessary.

• ● Active Version Available

In this column, the following display options are available:
• ○ : The object is available in an active version. You decide whether you want
to retain this version or reinstall the latest version of the object.
• ○ Date symbol: The object is already available in an active version. However,
the active version belongs to an older BI Content release. We recommend that you
install the latest version.
• ○ Gray symbol : An activated version of the object is available in the system.
However, the object status is inactive. If an object version is activated, this
indicates that all metadata for the object can be created successfully. The inactive
 object status indicates that the processed object is inconsistent and cannot
currently be used for processing data. Transfer the object again from the SAP
delivery version (D version). If this is not enough to change the object status from
“inactive” to “active”, the object has to be postprocessed. In the activation log,
you can find notes on postprocessing.

Postprocessing: An InfoObject may have status inactive if changes have been made
to the structure at field level. Postprocessing the object involves converting the
relevant tables in accordance with the activation log.
• ○ No indicator: The object is not available in an active version.
7. Make Settings in the Selection List and Install.
Make the required settings in the Install selection list:
Installation Type

Installation Type Information

Simulate installation The system runs a test to see whether any
errors are likely to occur during the installation.
However, not all errors that may occur can be
identified during simulation: Some error
messages can only be generated when a real A
version (not just a simulation) is available in the
system. You should, therefore, only use the
simulation function as a rough guide to help
you identify and remove basic errors.
Install The selected objects are installed immediately.
Install in Background The selected objects are installed in the
background.
Install and Transport The selected objects are installed immediately
and then written to a transport request.

We recommend that you use the Install in Background option because installing a
large number of objects can take a long time. Modifying objects that are already
active can take an especially long time. Make sure that when you install objects in
the background, the versions are not matched. It is always the delivery version that
is installed. They are not matched against any available customer versions.
8. Correct Errors
You can find out if errors occurred during the installation of BI Content by displaying a
log. Choose the Log pushbutton to access the log. In the relevant maintenance
transaction, repair any errors that occurred during the installation. Install the BI Content
again.