Sap TBW10 4

TBW10
271
Lesson: Loading flat files
Exercise 10: Attribute data

load/text from a CSV file
Duration of the exercise: 40 Minutes
Objectives of the Exercises

At the end of this exercise, you will be able to:
Load master data using the flat file interface
Use transforms to attributes and texts
Create formulas using the formula editor
Business Case
You receives data from the cost center in comma separated file (CSV) from
another system. The files have information about the attributes and texts of its
InfoObjeto of cost center of 13 characters (COSTC##).
System Data
System:
Assigned system
Principal:
800
User ID:
Assigned user ID
Key of access:
Assigned password
Parameterizations of the system:
1.
To load flat files, participants need a local disk drive with both write and
read access.
This may be the N:\ drive in to terminal server (Citrix) environment.

The flat files are downloaded via document integration from a link on the User
Menu. They are also available as attachments in the Shared Folders
(transaction OS04) in the folder Training/BW310/ in the file Material for
BW310 (this is a back up, use the path in the exercise as a first choice to
get the files).
Task 1: Preparation
To prepare the following year, then a download the CSV files necessary to your
workstation.
1.
In the SAP menu Easy Access, select User Menu

Files
Drawings Model for scenarios of flat files (double click) and between
In the SAP Web Application Server.
Continued on next page
14-10-2008
2008 SAP AG. All rights reserved.
Chapter 4: acquisition of data from other systems
TBW10
On the left, on the shortcut menu of master data of cost center 1,

select Record target as... To make a download of the CSV file on your
workstation.
Specify your local directory depending on the environment in its class.
Council: Follow the instructions provided by your instructor. The
directory and drive available depend on the environment of the
course. Select the
Unit N:\, for example, if you are in a Citrix environment.
Save the file with the name T_COSTCENTER_MD01.csv.
Task 2 - Set global transfer routines

The values of the external cost center have a length of 13 characters. This
coincides exactly with the length of its characteristics (COSTC InfoObjeto##).
However, you should still check again the global transfer routines for its
characteristic COSTC##. Since the three-character prefix is required only if the
data are not loaded using the flat file interface, you must implement a test in the
routine that discover from what source system data is loaded.
1.
Access your InfoObjeto COSTC## and Select the modify mode. In

the General tab, access the existing transfer routine in the modify mode.
2.
Modify the routine of global transfer.

Insert a new line below the line *$*$ begin of routine insert your code only below this line, and complete the
new line as follows.
*$*$ home of the routine: Insert your code only below this line
Check source_system <> 'I_EXTERN'.
Shift result right by 3 places.
Result(3) = source_system.
Returncode = 0.
*$*$ end of the routine: Insert your code only before this line
Attention: Be sure to use the correct capitalization of the
technical name for the source system.
14-10-2008
TBW10
Check the syntax of the modification and record the transfer routine.
Then select Its InfoObjeto.
Task 3 - Creation of a source of file data plane for

the upload of master data
To distribute information on attributes and texts to the respective tables of its
characteristic of cost center, create a data source for the upload of
Flat files and remove the CSV file using the flat file interface.
1.
Create a data source for the interface of flat file.

From the Workbench, go to the view of a system data source
source I_Extern. Locate your application component of the Group ##
(ZT_BW310_GR##), select Create data source on the shortcut menu and
enter the following values.
Field Name
Value
Data Source
Costc##_MD_flatfile
Source system
I_EXTERN
Data source data class
Master Data Attributes
2.
In the Update screen of the data source, enter brief descriptions, stockings
and explanatory (Gr ## MD from the flat file) for your data source on the
label General Information.
3.
Insert all the necessary information on the labels removal, Proposal,

and Fields.
In the Label Removal, select your file plan for master data using the
functionality Explore. Select 1 row of header that is ignored. The format of
the data should be separated by spacer (for example, separated by commas).
Enter ; as a separator character data and " as an escape character.
In the proposed label, select Load sample data and see the list of
proposals. Make sure that all of the fields are marked with a copy to the
list of fields. This list proposal derives from the header line and the
contents of your flat file.
In the Label Fields can get a list of all the possible fields for the data
source that derives from the proposal. At this point you need to check if
the classes of field and lengths are correct (if they match with the file that
has received or that will receive). In some cases, the proposal will not be
accurate, and shall adjust the classes and the lengths of the fields in the
label fields.
14-10-2008
TBW10
This happens with the field length and the data class for the
object SOCIETY CO (CO_area). To be able to load the information with
success you need to make sure that the class data for co_area is fixed
at CHAR, length 4. An easy way to do this is using 0CO_AREA as
InfoObjeto model, in order to properly get the kind of field and the lengths.
Active
Your data source.
Then go to the label Pres.prel. And see the data that will load the BI
system.
Return to the source tree of data using the back button
Task 4: Creating transforms

Connect your data source with the attributes and text tables of its features
InfoObjeto COSTC##. To do this, create transformations between the two
objects. You need to create a set of transforms to do a upload text data, and
another to populate the data attributes.
1.
Create the transformations for the attribute data. In the shortcut menu of
your data source costc##_MD_flatfile, select Create transformation and
enter the following values in the target area of the transformation.
Field Name
Value
Object Class
InfoObjeto
Object subclass
Attributes
Name
Costc##
Make sure that the following data are correct for the source area of the
transformation.
2.
Field Name
Value
Object Class
Data Source
Data Source
Costc##_MD_flatfile
Source system
I_Extern
Update the transformations to make an upload of data attributes from your

file flat in the feature COSTC##.
Some of the attributes of its characteristic can be filled out by using direct
mapping to fields in the data source. Connect to the fields in the data source
to the left of the table with the InfoObjetos its characteristic as shown on the
right side of the table below.
14-10-2008
TBW10
3.
Data Source Field
InfoObjeto
CO_AREA
0CO_AREA
CostcenterNeu
COSTC##
BUS_AREA
0BUS_AREA
COMP_CODE
0COMP_CODE
PROFIT_CTR
0PROFIT_CTR
RESP_PERS
0RESP_PERS
Manually update the transformations for the InfoObjetos 0DATETO,

0DATEFROM and 0CURRENCY, because the file level does not
provide data to these fields. Create the following Transforms.
InfoObjeto
Transformation
0DATETO
Constant: 31.12.9999
0DATEFROM
Create a date formula to assign the

current date to the data load process. To do
this, use the system field SYST-datum in
the formula editor.
0CURRENCY
Data reading teachers: InfoObjeto

source 0CO_AREA
Activate your changes and return to the previous screen.

4.
Create transforms to do a upload of the text information in the flat file to

the text table of its InfoObjeto. Select Create Transform from the context
menu of your data source costc##_MD_flatfile and enter the following
values in the target area of the transformation.
Field Name
Value
Object Class
InfoObjeto
Object subclass
Texts
Name
Costc##
transformation.
14-10-2008
5.
TBW10
Field Name
Value
Object Class
Data Source
Data Source
Costc##_MD_flatfile
Source system
I_Extern
Update the transformations to make an upload text data from your flat
file to the feature COSTC##.
Some of the InfoObjetos its characteristic can be filled out by using direct
mapping to fields in the data source. Connect to the fields in the source of
data in the table on the left with the InfoObjetos its characteristic as shown
in the following table.
6.
Data Source Field
InfoObjeto
CO_AREA
0CO_AREA
CostcenterNeu
COSTC##
TXTMD
0TXTSH
TXTMD
0TXTMD
Update the transformations for the InfoObjetos 0DATETO, 0DATEFROM,

and 0LANGU because the file level does not supplied the data for those
fields. Create the following Transforms.
InfoObjeto
Transformation
0DATETO
0DATEFROM
Create a date formula to assign the current

date to the data load process. To do this, use
the system field SYST-datum in the formula
editor.
0LANGU
Create a formula of language to assign the system

language for the data load process. To do this, use
the system field SYST-LANGU/language on the
formula editor.
14-10-2008
TBW10
Task 5 - Creation of a InfoPaquete and loading data to

PSA
After having defined the data flow, load the data of your file plane to the
corresponding PSA table.
1.
Create a InfoPaquete for your data source costc##_MD_flatfile. In the

view of the source of data for the source system I_Extern, select Create
Package info from the context menu of your data source. Fill in the
description file data plane teachers Gr 01.
2.
In the Label Removal, check the parameter settings and make sure your flat
file will be charged. The parameterizations are taken from its definition of
the data source. The data should be updated in PSA only. Make sure it is
selected the full update mode.
Record the options.
3.
Start the InfoPaquete and verify the treatment in the monitor.

In the Label Anticipate, select Start Load dat.inmediat.
Start.
Task 6: Creation of processes for

transferring data to make an upload of master data in
the destination
Create and schedule processes for transferring data, one for the attribute and
another for text data, to load the master data from the PSA table to the data tables
teachers of his InfoObjeto of features.
1.
Load the data attributes from the table PSA to the attribute table of its
InfoObjeto of features. In the window Workbench - Modeling, open
The view of InfoSitio and locate your application component (Group##).
Below its characteristics (COSTC InfoObjeto##) you will find three
structures for hierarchies, attributes and texts. Select the structure of
attributes and find the folder data transfer process under
The structure. From its context menu, select Create Data Transfer process.
In the dialog window, fill in the following information.
Field Name
Value
Data Transfer Process
GR## attribute data of

the cost center of the
flat file
Object class (destination the DWP) InfoObjeto

Object Subtype (destination
the DWP)
Attributes
14-10-2008
2.
TBW10
Field Name
Value
Name (destination of the DWP
Costc##
Object class (source the DWP)
Data Source
Data source (source the DWP)
Costc##_MD_flatfile
Source system (source of PTD)
I_Extern
Update the labels removal, Update, and run its process of data transfer
with:
Pull mode = Full.
Treatment of errors = Updating of valid records, without reporting
(request red)
Record and enable its data transfer process. Run the data transfer
process and verify the data load on the monitor
Requests. Note the entire data stream and verify the data that has been
transferred to the system.
3.
To load the text data from the PSA table to the tables in the text of its
characteristic InfoObjeto, proceed in the same way as with the attributes. In
the window Workbench - Modeling, open the view of InfoSitio and locate
your application component (Group##). Under its characteristics (COSTC
InfoObjeto##) you will find a structure for texts, Cost Center (texts), with a
folder data transfer process. From its context menu, select Create Data
Transfer process. In the dialog window, fill in the following information.
Field Name
Value
GR## Text Data

The cost center of the
flat file
4.

the DWP)
Texts
Name (destination the DWP)
Costc##
Data Source
Costc##_MD_flatfile
I_Extern
with:
310
2008 SAP AG. Reservados todos los derechos.
14-10-2008
TBW10
Pull mode = Complete

Treatment of errors = Updating of valid records, without reporting (request
red)
14-10-2008
311
TBW10
Solution 10: Attribute data

load/text from a CSV file
Task 1: Preparation
To prepare the following year, then a download the CSV files necessary to your
workstation.
1.
In the SAP menu Easy Access, select User Menu

Files
Drawings Model for scenarios of flat files (double click) and between
In the SAP Web Application Server.
On the left, on the shortcut menu of master data of cost center 1,

select Record target as... To make a download of the CSV file on your
workstation.
Specify your local directory depending on the environment in its class.
Council: Follow the instructions provided by your instructor. The
directory and drive available depend on the environment of the
course. Select the unit N:\, for example, if you are in a Citrix
environment.
Save the file with the name T_COSTCENTER_MD01.csv.
a)
Follow the instructions in the previous exercise.
312
14-10-2008
TBW10
Task 2 - Set global transfer routines

The values of the external cost center have a length of 13 characters. This
coincides exactly with the length of its characteristics (COSTC InfoObjeto##).
However, you should still check again the global transfer routines for its
characteristic COSTC##. Since the three-character prefix is required only if the
data are not loaded using the flat file interface, you must implement a test in the
routine that discover from what source system data is loaded.
1.
Access your InfoObjeto COSTC## and Select the modify mode. In

the General tab, access the existing transfer routine in the modify mode.
a)
In the SAP screen Easy Access, select Menu SAP

Modeling
Workbench: Modeling
InfoObjetos
Training BW
Customer Training BW
BW310 Data
Group##.
Warehousing
In its InfoObjeto COSTC## select Modify from the shortcut menu.

b)
In the General tab, in the area of routine transfer, select

Update
2.
Modify the routine of global transfer.

Insert a new line below the line *$*$ begin of routine insert your code only below this line, and complete the
new line as follows.
*$*$ home of the routine: Insert your code only below this line
Check source_system <> 'I_EXTERN'.
Shift result right by 3 places.
Result(3) = source_system.
Returncode = 0.
*$*$ end of the routine: Insert your code only before this line
Attention: Be sure to use the correct capitalization of the
technical name for the source system.
14-10-2008
313
TBW10
Check the syntax of the modification and record the transfer routine.
Then select Its InfoObjeto.
a)
Position the cursor at the start of the line move result and select
Enter to insert a new line.
b)
Complete the codification of the new line as specified before.
c)
Select Check
d)
Select Record
e)
Active
Its InfoObjeto and leave the update the InfoObjeto by
selecting
.
.
.
Task 3 - Creation of a source of file data plane for the

upload of master data
To distribute information on attributes and texts to the respective tables of its
characteristic of cost center, create a data source for the upload of
Flat files and remove the CSV file using the flat file interface.
1.

From the Workbench, go to the view of a system data source
source I_Extern. Locate your application component of the Group ##
(ZT_BW310_GR##), select Create data source on the shortcut menu and
enter the following values.
314
14-10-2008
TBW10
Field Name
Value
Data Source
Costc##_MD_flatfile
Source system
I_EXTERN
Master Data Attributes
a)
In the Workbench, select Modeling

Data Sources.
Select the source system I_Extern using the button Select source system.
b)
Select Training BW
## (ZT_BW310_GR##).
c)
BW 310 Data Warehousing
Group
On the shortcut menu for the application component Group ##,

select Create data sources.
Tip: You may need to select the icon Hide/Show empty
folders to view your application component.
2.
3.
d)
Enter the required information as specified above.
e)
Select Transfer
In the Update screen of the data source, enter brief descriptions, stockings
and explanatory (Gr ## MD from the flat file) for your data source on the
a)
Change to modify mode by selecting Edit Data Source

, if necessary .
b)
Enter Gr ## MD from the flat file as brief

description, media and explanatory.

and Fields.
In the Label Removal, select your file plan for master data using the
functionality Explore. Select 1 row of header that is ignored. The format of
the data should be separated by spacer (for example, separated by commas).
Enter ; as a separator character data and " as an escape character.
In the proposed label, select Load sample data and see the list of
proposals. Make sure that all of the fields are marked with a copy to the
list of fields. This list proposal derives from the header line and the
contents of your flat file.
14-10-2008
315
TBW10
In the Label Fields can get a list of all the possible fields for the data
source that derives from the proposal. At this point you need to check if
the classes of field and lengths are correct (if they match with the file that
has received or that will receive). In some cases, the proposal will not be
accurate, and shall adjust the classes and the lengths of the fields in the
label fields.
This happens with the field length and the data class for the
object SOCIETY CO (CO_area). To be able to load the information with
success you need to make sure that the class data for co_area is fixed
at CHAR, length 4. An easy way to do this is using 0CO_AREA as
InfoObjeto model, in order to properly get the kind of field and the lengths.
Active
Your data source.
Then go to the label Pres.prel. And see the data that will load the BI system.
316
14-10-2008
TBW10
Return to the source tree of data using the back button

a)
In the Label Removal, set the following options:

Description
Value
Adapter
Load file class

from
the
workstation
Name of the file
[path for your flat file]
Header rows that

should be ignored
Data Format
Separated by spacer (for

example, separated by commas)
Data separator
character
Escape symbol
"
of
text
local
b)
To obtain a proposal of the system, make sure that the proposed label,
the converter field contains the value separated by spacer.... Enter a
number (100, for example) for the number of records. Then select the
button to load sample data.
c)
For the proposed fields are copied from the list in the field, verify
all bookmarks in the first column, copy in the list of fields.
d)
Check the list of fields in the Label field. Although it may be that the
proposal is not perfect, will allow the data is loaded with one exception.
For the first column (SOCIETY CO) add the InfoObjeto 0CO_area in
the column of the model of InfoObjeto and then press Enter and
finally copy. This will copy the lengths of field and the kind of data of
0CO_area in their field labels.
e)
Active
f)
In the Label Preview, you will get a preview of your data by entering
a number (100, for example) for the No. field of data records. Then
select the button Read data from the Print Preview. Check if the data
fits correctly in the fields in your data source.
g)
Return to the source tree of data by selecting Back
Your data source.
14-10-2008
317
TBW10

Connect your data source with the attributes and text tables of its features
InfoObjeto COSTC##. To do this, create transformations between the two
objects. You need to create a set of transforms to do a upload text data, and
another to populate the data attributes.
1.
Create the transformations for the attribute data. In the shortcut menu of
your data source costc##_MD_flatfile, select Create transformation and
enter the following values in the target area of the transformation.
Field Name
Value
Object Class
InfoObjeto
Object subclass
Attributes
Name
Costc##
transformation.
Field Name
Value
Object Class
Data Source
Data Source
Costc##_MD_flatfile
Source system
I_Extern
a)

Inforea selecting Training BW Group
##.
Data Sources. Go to your

BW310 Data Warehousing
2.
b)
Select Create Transform in the shortcut menu for the data source
costc##_MD_flatfile.
c)
In the dialog window, fill in the information as shown in the

preceding table.
Update the transformations to make an upload of data attributes from your

file flat in the feature COSTC##.
Some of the attributes of its characteristic can be filled out by using direct
mapping to fields in the data source. Connect to the fields in the data source
to the left of the table with the InfoObjetos its characteristic as shown on the
right side of the table below.
318
14-10-2008
TBW10
3.
Data Source Field
InfoObjeto
CO_AREA
0CO_AREA
CostcenterNeu
COSTC##
BUS_AREA
0BUS_AREA
COMP_CODE
0COMP_CODE
PROFIT_CTR
0PROFIT_CTR
RESP_PERS
0RESP_PERS
a)
You may need to change the way your screen of transforms from
Display to modify.
b)
Create the necessary allocations between the fields of the data source
and the InfoObjetos by dragging them with the mouse.
Manually update the transformations for the InfoObjetos 0DATETO,

0DATEFROM and 0CURRENCY, because the file level does not
provide data to these fields. Create the following Transforms.
InfoObjeto
Transformation
0DATETO
0DATEFROM
Create a date formula to assign the

current date to the data load process. To do
this, use the system field SYST-datum in
the formula editor.
0CURRENCY
Data reading teachers: InfoObjeto

source 0CO_AREA
14-10-2008
319
TBW10
4.
a)
Double click on the transformation of the InfoObjeto 0DATETO to

enter in the dialog window Rule Details. In the drop-down box rule
class, select Constant e enter 31.12.9999 in the field constant
value.
b)
Select the Pad Transfer values to confirm and continue.
c)
By double clicking on the transformation of 0DATEFFROM shall

enter in the dialog window Rule Details. Enter current date as
the description and select formula in the drop down window class
rule. You may receive a message
Warning that the formula does not have input fields, simply accept the
warning message and continue.
d)
In the formula editor you can easily create assignments and simple
encodings. On the left side of the selection field, select System
fields from the drop-down menu. Add the field SYST-DATUM (current
date) to its formula by double clicking on it.
e)
Verify your formula and abandon the formula editor by selecting

Back .
f)
Confirm the transformation with the pushbutton transfer values.
g)
Double click on the transformation of the InfoObjeto 0currency to

enter in the dialog window Rule Details. First select Read master
data from drop-down box Class Rule.
Then add the field CO_AREA to the source fields of the rule using
the Add button field source . In addition,
Enter 0CO_AREA In the Assignment field IO. And finally press F4 in
the field InfoObjeto font, to get 0CO_AREA as info object source.
h)
i)
Active
Their transformations.
Create transforms to do a upload of the text information in the flat file to

the text table of its InfoObjeto. Select Create Transform from the context
menu of your data source costc##_MD_flatfile and enter the following
values in the target area of the transformation.
320
14-10-2008
TBW10
Field Name
Value
Object Class
InfoObjeto
Object subclass
Texts
Name
Costc##
transformation.
14-10-2008
321
TBW10
Field Name
Value
Object Class
Data Source
Data Source
Costc##_MD_flatfile
Source system
I_Extern
a)

Inforea selecting Training BW Group
##.
Data Sources. Go to the

5.
b)
On the shortcut menu for the data source costc##_MD_flatfile,

select Create Transform.
c)

preceding table.
Update the transformations to make an upload text data from your flat
file to the feature COSTC##.
Some of the InfoObjetos its characteristic can be filled out by using direct
mapping to fields in the data source. Connect to the fields in the source of
data in the table on the left with the InfoObjetos its characteristic as shown
in the following table.
Data Source Field
InfoObjeto
CO_AREA
0CO_AREA
CostcenterNeu
COSTC##
TXTMD
0TXTSH
TXTMD
0TXTMD
a)
Tip: You may first need to change the way your screen of
transforms from Display to modify.
6.
Update the transformations for the InfoObjetos 0DATETO, 0DATEFROM,

and 0LANGU because the file level does not supplied the data for those
fields. Create the following Transforms.
322
14-10-2008
TBW10
InfoObjeto
Transformation
0DATETO
0DATEFROM
Create a date formula to assign the current

date to the data load process. To do this, use
the system field SYST-datum in the formula
editor.
0LANGU
Create a formula of language to assign the system

language for the data load process. To do this, use
the system field SYST-LANGU/language on the
formula editor.

a)
Double click on the transformation of the InfoObjeto 0DATETO to

enter in the dialog window Rule Details. In the drop-down box rule
class, select Constant e enter 31.12.9999 in the field constant
value.
b)
c)
By double clicking on the transformation of 0DATEFFROM shall

enter in the dialog window Rule Details. Enter current date as
the description and select formula in the pop-up window for the class
of the rule.
d)
fields from the drop-down menu. Insert the field SYSTDATUM (current date) by double-clicking its formula.
e)
Leave the formula editor by selecting Back And confirm

the transform using the pushbutton transfer values.
f)
Select the transform for 0LANGU by double-clicking on the table

field central. Register language as the description and
select formula in the drop down window class rule.
g)
Fields in the drop-down menu. Insert the field SYSTLANGU (language key) by double-clicking its formula.
h)
Leave the formula editor by selecting Back And confirm the

transform using the pushbutton transfer values.
i)
Select Enable
14-10-2008
323
TBW10

PSA
After having defined the data flow, load the data of your file plane to the
corresponding PSA table.
1.
Create a InfoPaquete for your data source costc##_MD_flatfile. In the

view of the source of data for the source system I_Extern, select Create
Package info from the context menu of your data source. Fill in the
description file data plane teachers Gr 01.
a)
Select Workbench Administrator

Modeling
Sources of
Data. Make sure that you get the view of the source of data for the
source system I_extern.
b)
Select Training BW
BW Data
Group ##
Warehousing
(ZT_BW310_GR##). Select Create InfoPaquete in the shortcut menu of
your data source.
2.
c)
Enter file data plane teachers GR## as the description of the

InfoPaquete.
d)
Select Record.
the data source. The data should be updated in PSA only. Make sure it is
selected the full update mode.
324
14-10-2008
TBW10
Record the options.

a)
In the Label Removal, make sure that the following are correct
parameterizations.
Description
Value
Adapter
Load file class

from
the
workstation
Name of the file
[path for your flat file]
Header rows that

should be ignored
Data Format

example, separated by
commas)
;
Data separator
character
Escape symbol
3.
of
text
local
"
b)
In the Label Process, select the option only PSA.
c)
In the Label Update, select the update mode

Full.

Start.
a)
In the Label Anticipate, select Start loading data immediately

And start the data load process by selecting .
b)
Select to verify the data load process in the monitor.
Task 6: Creation of processes for

transferring data to make an upload of master data in
the destination
Create and schedule processes for transferring data, one for the attribute and
another for text data, to load the master data from the PSA table to the data tables
teachers of his InfoObjeto of features.
1.
Load the data attributes from the table PSA to the attribute table of its
InfoObjeto of features. In the window Workbench - Modeling, open
The view of InfoSitio and locate your application component (Group##).
Below its characteristics (COSTC InfoObjeto##) you will find three
structures for hierarchies, attributes and texts. Select the structure of
attributes and find the folder data transfer process under
14-10-2008
325
TBW10
The structure. From its context menu, select Create Data Transfer process.
In the dialog window, fill in the following information.
Field Name
Value
GR## attribute data of

the cost center of the
flat file

the DWP)
Attributes
Name (destination of the DWP
Costc##
Data Source
Costc##_MD_flatfile
I_Extern
a)
To reach its InfoCubo of feature, select Workbench

Modeling
InfoSitios
Training BW
BW310 Data
Warehousing
Group ##
Costc##.
Tip: To refresh the tree to refresh the display.
2.
b)
In the shortcut menu of the folder data transfer process below the
structure cost center (attribute), select Create Data Transfer
process and enter the values as listed in the above table.
c)
Select Continue (Enter)
with:
Pull mode = Full.
(request red)
326
14-10-2008
TBW10
3.
a)
In the Label Removal, select the Full removal mode.
b)
In the Label Update, select for the treatment of errors:

Update of valid records, without reporting (request red).
c)
In the Label run, select the mode of treatment removal in series,

parallel treatment immediately.
d)
Active
e)
Select the Run button

process.
f)
Check the flow of data in the monitor of request.
g)
Verify the data transferred to BI through the navigation on the

workbench in view of the InfoSitio and then to its Inforea Group##.
Select Update master data in the shortcut menu of your InfoObjeto
(COSTC##) . Verify the cost centers that have an ID that starts
with 123.
h)
Select Run
i)
View the entire data stream in the workbench. Go to the view InfoSitio,
navigate to your Inforea Group## and deploy the entire data stream
below its characteristic costc##. Alternatively, select Show Data
flow in the shortcut menu of the Object Info.
The process of transfer of data.

In the Label Run to start the data transfer
To load the text data from the PSA table to the tables in the text of its
characteristic InfoObjeto, proceed in the same way as with the attributes. In
the window Workbench - Modeling, open the view of InfoSitio and locate
your application component (Group##). Under its characteristics (COSTC
InfoObjeto##) you will find a structure for texts, Cost Center (texts), with a
folder data transfer process. From its context menu, select Create Data
Transfer process. In the dialog window, fill in the following information.
Field Name
Value
GR## text data of the

cost center of the
flat file
14-10-2008
327
TBW10
Field Name
Value

the DWP)
Texts
Costc##
Data Source
Costc##_MD_flatfile
I_Extern
a)
To reach its InfoObjeto, Select Workbench

Modeling
InfoSitios
Training BW
BW310 Data Warehousing Group
##
Costc##.
4.
b)
In the shortcut menu of the folder data transfer process under the
structure of text, select Create Data Transfer process and enter the
values as they appear in the list of the table.
c)
with:
Pull mode = Complete
(request red)
328
14-10-2008
TBW10
14-10-2008
a)
In the Label Removal, select the Full removal mode.
b)
In the Label Update, select for the treatment of errors

c)

d)
Active
e)

process.
f)
Verify the process of transfer of data on the monitor of the request.
g)

workbench to the sight of InfoSitio, in its Inforea Group##, and
select Manage master data in the shortcut menu of your InfoObjeto
GR##HUB1. Verify the cost centers that have an ID that starts
with 123*.
h)
Select Run
i)
View the entire data stream in the workbench. Go to the view InfoSitio,
navigate to your Inforea Group## and deploy the entire data stream
below its characteristic costc##. Alternatively, select Show Data
flow in the shortcut menu of the Object Info.

329
330
TBW10
14-10-2008
TBW10
297
Exercise 11: Loading data variables

from CSV files

Load data variables through the interface of file
Create transforms using the formula editor
Business Case
Each month, your organization evaluates combined data from SAP systems and
external systems. These reports are based on the InfoCubo of cost centers.
The flat files in .csv format have been created for variable data from external
systems, and now must be executed a upload of data in its InfoCubo.
System Data
System:
Assigned system
Principal:
800
User ID:
Assigned user ID
Key of access:
Assigned password
Parameterizations of the system: (not necessary as we are loading via
Application Server)

transaction data
To run the upload of data variables from a flat file, you must first create a source
of file data plane.
1.

From the Workbench, go to the view of the data source. Make sure that
displays the tree of source of data for the source system I_extern. Go to the
component of the Application Group ## (ZT_BW310_GR##), select Create
data source from the shortcut menu and enter the following values.
14-10-2008
331
TBW10
Field Name
Input Value
Data Source
Costc##_td_flatfile
Source system
I_Extern
Variable Data
2.
In the update of your data source, enter Flat File Gr## TD as brief
descriptions, stockings and explanatory for your data source on the
3.

and Fields.
The flat file for the variable data has been stored in the application server;
therefore, select Adapter load
class
of
text
from
application server on the label removal.
Select the flat file for the variable data using the functionality
Explore. In the dialog window, select Files to11. Select
DIR_TRANS
Training
CSV
T_COSTCENTER_trans01.csv.
Double click on the file and select Copy Name.
Select 1 row of header that is ignored. The format of the data should
be separated by spacer (for example, separated by commas). Enter ; as a
separator character data and " as an escape character. Specify direct
entry as number format, . As a thousands separator, and , as a decimal point
character.
In the proposed label, select the pad loading sample data and see the list
of proposals. Make sure that all of the fields are marked with a copy to the
list of fields. This list proposal derives from the header line of your flat file
and your data records.
In the Label Fields can get a list of all the possible fields for the data source
that derives from the proposal. Check if the fields are correct for your data
source. For the fiscal year Period field, you need to ensure that data can be
extracted from the file level to correct data format within BI. Therefore, we
use in InfoObjeto BI 0FISCPER as InfoObjeto model.
First select your data source with the push button
Then go to the tag Pres.prel. And see the data that will load the BI system.
Return to the source tree of data using the Back button
332
14-10-2008
TBW10

Connect your data source to your InfoCubo Gr##HUB1. To do this, create
transformations between the two objects.
1.
From the shortcut menu of your data source costc##_td_flatfile,

select Create transformation and enter the following values.
Field Name
Value
Object Class
InfoCubo
Name
GR##HUB1
transformation.
2.
Field Name
Value
Object Class
Data Source
Data Source
Costc##_td_flatfile
Source system
I_Extern
Update the transformations to run the upload of data variables from your
file plan in its InfoCubo GR##HUB1.
Some of the InfoObjetos its InfoCubo can be filled out by using direct
mapping to fields in the data source. Connect the fields in the data source
with the InfoObjetos its InfoCubo as shown in the following table.
Data Source Field
InfoCubo
CO_AREA
0CO_AREA
COPCCENTERNEU
COSTC##
BUS_AREA
[no assignment]
COMP_CODE
[no assignment]
PROFIT_CTR
[no assignment]
COPCELMNT
0COSTELMNT
VERSION
0Version
VTYPE
0VTYPE
METYPE
0METYPE
VTDETAIL
0VTDETAIL
14-10-2008
333
3.
TBW10
Data Source Field
InfoCubo
VALUATION
0valuation
CURTYPE
0CURTYPE
AMOUNT
AMOUNT##
QUANTITY
0Quantity
CURRENCY
AMOUNT##
UNIT
0Quantity
FISCPER
0FISCPER
Manually update the transformations for the InfoObjetos 0FISCVARNT

(fiscal year variant), and 0DB_CR_IND (Indicator sender/receiver)
because the flat file did not provide data for those fields.
InfoObjeto
Transformation
0FISCVARNT
Constant: K4
0db_CR_IND
Formula:
If (amount < 0 , 'C' , 'D')
The Indicator feature sender/receiver (0DB_CR_IND) is used in reporting

to distinguish between creditor and debtor. The flat files do not provide this
information directly. For this reason, you can obtain this indicator of the
sign +/- together to the amount.
Do this by creating a formula with the description should/have:
If the amount is less than 0, the system assigns the indicator C. On the
other hand, the system assigns the indicator D.
Assign the Amount field as a field source of the rule.
The characteristics for the information of trading partners are maintained in
initial form (blank). The data source does not provide this information.
334
14-10-2008
TBW10

the PSA
After you have defined your data flow, load the data from the file to the PSA
level table.
1.
Create a InfoPaquete for your data source costc##_td_flatfile.

Select SAP Easy Access
Modeling
Workbench: Modeling
Data sources and make sure it is in the View source of data for the
external system I_extern. Go to the component of the application
Training BW
BW Data
Group ## (ZT_BW310_GR##).
Warehousing
In the shortcut menu of your data source costc##_td_flatfile, select Create
InfoPaquete. Enter file data plane variables GR## as the description of
the InfoPaquete.
2.
the data source. The data should be transferred to Only PSA and you should
select the full update mode.
Record the options.
3.

Start.
Task 4: Creation of processes for transferring data to

run a upload of master data in the destination
Create and schedule a process of transfer of data to load the data variables from
the PSA table to the fact table of its InfoCubo.
1.
Load the data variables from the PSA table to the fact table of its InfoCubo.
In the window Workbench - Modeling, open the view of InfoSitio and
locate your application component (Group##). Under its InfoCubo
GR##HUB1 you will find the folder Data Transfer Process. From its
context menu, select Create Data Transfer process. In the dialog window,
enter the following information.
Field Name
Value
GR## transaction data

of the cost center of
the flat file
Object class (destination the DWP) InfoCubo

Gr##cube1
14-10-2008
335
2.
TBW10
Field Name
Value
Data Source
Costc##_td_flatfile
I_Extern
with:
Pull mode = Delta
(request red)
Record and enable its data transfer process. Run the data transfer process
and verify the data load on the monitor.
3.
Note the transferred data. Use the target browser data and verify the cost
centers that begin with 123*. Alternatively, you could create a query BEx
to visualize the data.
Check the flow of data that supplied the data for its InfoCubo.
336
14-10-2008
TBW10
Solution 11: Loading data variables from

CSV files
transaction data
To run the upload of data variables from a flat file, you must first create a source
of file data plane.
1.

From the Workbench, go to the view of the data source. Make sure that
displays the tree of source of data for the source system I_extern. Go to the
component of the Application Group ## (ZT_BW310_GR##), select Create
data source from the shortcut menu and enter the following values.
Field Name
Input Value
Data Source
Costc##_td_flatfile
Source system
I_Extern
Variable Data
a)
In the Workbench, select SAP Easy Access

Modeling
Workbench: Modeling
Data Sources. Make sure that gets
The tree of the source of data for the source system I_EXTERN,
using pushbutton Select source system. From the shortcut menu for
the application component Group ##, select Create data source.
Tip: It may be necessary to select the icon Hide/Show

empty folders to view your application component.
b)
Enter the information specified above.
c)
Select Transfer
14-10-2008
337
2.
3.
TBW10
In the update of your data source, enter Flat File Gr## TD as brief
descriptions, stockings and explanatory for your data source on the
a)
Change to modify mode using the button Edit Data Source

necessary .
, if
b)
Enter Flat File Gr ## TD as brief description, media and

explanatory.

and Fields.
The flat file for the variable data has been stored in the application server;
therefore, select Adapter load
class
of
text
from
application server on the label removal.
Select the flat file for the variable data using the functionality
Explore. In the dialog window, select Files to11. Select
DIR_TRANS
Training
CSV
T_COSTCENTER_trans01.csv.
Double click on the file and select Copy Name.
Select 1 row of header that is ignored. The format of the data should
be separated by spacer (for example, separated by commas). Enter ; as a
separator character data and " as an escape character. Specify direct
entry as number format, . As a thousands separator, and , as a decimal point
character.
In the proposed label, select the pad loading sample data and see the list
of proposals. Make sure that all of the fields are marked with a copy to the
list of fields. This list proposal derives from the header line of your flat file
and your data records.
In the Label Fields can get a list of all the possible fields for the data source
that derives from the proposal. Check if the fields are correct for your data
source. For the fiscal year Period field, you need to ensure that data can be
extracted from the file level to correct data format within BI. Therefore, we
use in InfoObjeto BI 0FISCPER as InfoObjeto model.
First select your data source with the push button
Then go to the tag Pres.prel. And see the data that will load the BI system.
Return to the source tree of data using the Back button
a)
In the Label Removal , enter the following values.
338
14-10-2008
TBW10
Field Name
Input Value
Adapter
Load file of
Class of text from the
Application Server
DIR_TRANS
Training
CSV
T_COSTCENB_trans01.csv.
Name of the file
Header rows that should be

ignored
Data Format
Separated by Spacer
Data separator character
Escape symbol
"
Number Format
Direct Entry
Thousands separator
character
Separator character of
decimal points
.
,
b)
In the proposed label: Make sure that the Converter

field contains separated by spacer and enter a number (20, for
example) for Number of records.
c)
Select the button to load sample data.
d)
For the proposed fields are copied from the list in the field, verify
all bookmarks in the first column, copy in the list of fields.
e)
Make sure that the fields of ratio AMOUNT AND QUANTITY, the
format indicates the external format and that the length of both fields
is at least of 11 digits (this could be fixed by default).
f)
In the Label fields , you will get a list of the possible fields for the
data source. This derives from the proposal. For the
field FISCPER Enter the object model info 0FISCPER. Then press
enter and copy. This will replace the field length and the class
information with the InfoObjeto 0FISCPER. Finally check if other
fields have the length and the class necessary for the parsing of your
file.
g)
Check
And Active
Your data source.
14-10-2008
339
TBW10
h)
In the Label Preview , you will get a preview of your data by

entering a number (20, for example) for the No. field data
records and selecting the button Read data from print preview.
Check if the data fits correctly in the fields in your data source.
i)
Return to the source tree of data by selecting Back

Connect your data source to your InfoCubo Gr##HUB1. To do this, create
transformations between the two objects.
1.
From the shortcut menu of your data source costc##_td_flatfile,

select Create transformation and enter the following values.
Field Name
Value
Object Class
InfoCubo
Name
GR##HUB1
transformation.
Field Name
Value
Object Class
Data Source
Data Source
Costc##_td_flatfile
Source system
I_Extern
a)

Modeling
Workbench: Modeling
Data Sources. Then select Training BW
BW310 Data Warehousing Group ## to access your Inforea.
2.
b)
Select Create transformations in the shortcut menu for the data

source costc##_MD_flatfile.
c)

preceding table.
Update the transformations to run the upload of data variables from your
file plan in its InfoCubo GR##HUB1.
Some of the InfoObjetos its InfoCubo can be filled out by using direct
mapping to fields in the data source. Connect the fields in the data source
with the InfoObjetos its InfoCubo as shown in the following table.
340
14-10-2008
TBW10
Data Source Field
InfoCubo
CO_AREA
0CO_AREA
COPCCENTERNEU
COSTC##
BUS_AREA
[no assignment]
COMP_CODE
[no assignment]
PROFIT_CTR
[no assignment]
COPCELMNT
0COSTELMNT
VERSION
0Version
VTYPE
0VTYPE
METYPE
0METYPE
VTDETAIL
0VTDETAIL
VALUATION
0valuation
CURTYPE
0CURTYPE
AMOUNT
AMOUNT##
QUANTITY
0Quantity
CURRENCY
AMOUNT##
UNIT
0Quantity
FISCPER
0FISCPER
A)
Tip: You may need to modify the way it transforms from
screen display to modify.
3.
Manually update the transformations for the InfoObjetos 0FISCVARNT

(fiscal year variant), and 0DB_CR_IND (Indicator sender/receiver)
because the flat file did not provide data for those fields.
InfoObjeto
Transformation
0FISCVARNT
Constant: K4
0db_CR_IND
Formula:
If (amount < 0 , 'C' , 'D')
14-10-2008
341
TBW10
The Indicator feature sender/receiver (0DB_CR_IND) is used in reporting

to distinguish between creditor and debtor. The flat files do not provide this
information directly. For this reason, you can obtain this indicator of the
sign +/- together to the amount.
Do this by creating a formula with the description should/have:
If the amount is less than 0, the system assigns the indicator C. On the
other hand, the system assigns the indicator D.
Assign the Amount field as a field source of the rule.
The characteristics for the information of trading partners are maintained in
initial form (blank). The data source does not provide this information.
342
14-10-2008
TBW10

a)
Double click on the transformation of the InfoObjeto 0FISCVARNT

to enter in the dialog window Rule Details. In the drop-down box rule
class, select Constant and enter K4 in the Value field constant. Select
the Pad Transfer values to confirm and continue.
b)
To create the formula for the indicator sender/receiver, double click on

the field 0DB_CR_IND of the central table.
c)
First assign the Amount field as a field source of the rule. It

selected the Insert Row button
In the dialog window Rule
Details.
d)
Select the Amount field in the following dialog window and

select Confirm .
e)
Enter Must/having as description and select formula in the drop

down window class rule.
Enter the formula editor.
f)
In the Formula editor, create the formula: If (amount < 0 , 'C' , 'D')
Press the pushbutton if.
Double-click on the source field amount.
Enter< by pressing the relevant button. Insert 0 using
the pushbutton Number.
Move your cursor after the first comma of the formula and enter the
constant value C. Then scroll behind the second comma and enter the
constant value D.
g)
Check
The formula.
h)
Exit the formula editor by selecting Back
i)
Assign your formula using the pushbutton transfer values.
j)
Activate your changes.

the PSA
After you have defined your data flow, load the data from the file to the PSA
level table.
1.
Create a InfoPaquete for your data source costc##_td_flatfile.
14-10-2008
343
TBW10

Modeling
Workbench: Modeling
Data sources and make sure it is in the View source of data for the
external system I_extern. Go to the component of the application
Training BW
BW Data Warehousing Group ## (ZT_BW310_GR##).
In the shortcut menu of your data source costc##_td_flatfile, select Create
InfoPaquete. Enter file data plane variables GR## as the description of
the InfoPaquete.
2.
a)
On the shortcut menu for the data source costc##_td_flatfile,

select Create InfoPaquete.
b)
In the Description field, enter the name of the InfoPaquete. File

Transaction Data Plane GR##, and select Record .
the data source. The data should be transferred to Only PSA and you should
select the full update mode.
Record the options.
a)
In the Label Removal, make sure that the following are correct
parameterizations.
Description
Value
Adapter
Load file class of text

from
the
Application
Server
Name of the file
File path
Header rows that

should be ignored
Data Format

example, separated by
commas)
;
Data separator
character
Escape symbol
3.
"
b)
In the Label Process, select the option only PSA.
c)
In the Label Update, select the update mode

Full Update. Record the options.
344
14-10-2008
TBW10
Start.
a)
In the Label Anticipate, select Start loading data immediately

And start the data load process by selecting .
b)
Verify the data load process in the monitor.
Task 4: Creation of processes for transferring data to

run a upload of master data in the destination
Create and schedule a process of transfer of data to load the data variables from
the PSA table to the fact table of its InfoCubo.
1.
Load the data variables from the PSA table to the fact table of its InfoCubo.
In the window Workbench - Modeling, open the view of InfoSitio and
locate your application component (Group##). Under its InfoCubo
GR##HUB1 you will find the folder Data Transfer Process. From its
context menu, select Create Data Transfer process. In the dialog window,
enter the following information.
Field Name
Value
GR## transaction data

of the cost center of
the flat file
Object class (destination the DWP) InfoCubo

Gr##cube1
Data Source
Costc##_td_flatfile
I_Extern
a)
To reach your InfoObjeto, select SAP Easy Access

Modeling
Workbench:Modeling
InfoSitios
Group ##.
Training BW

b)
Under the InfoCubo, select Create Data Transfer process in the

context menu of the folder data transfer process and enter the values
as listed in the above table.
c)
.
14-10-2008
345
2.
TBW10
with:
Pull mode = Delta
(request red)
Record and enable its data transfer process. Run the data transfer process and
verify the data load on the monitor.
3.
a)
In the Label Removal, select the mode of removal Delta.
b)
In the Label Update, select for the treatment of errors:

c)

d)
Active
e)

process.
f)
Verify the process of transfer of data on the monitor of the request.

Note the transferred data. Use the target browser data and verify the cost
centers that begin with 123*. Alternatively, you could create a query BEx
to visualize the data.
Check the flow of data that supplied the data for its InfoCubo.
346
a)

workbench in view of the InfoSitio and then to its Inforea
Group##.
b)
Select Manage from the shortcut menu of your InfoCubo GR##HUB1.

Select your InfoCubo in the upper table and select Content .
c)
Select the pad selecting fields to output and then a few through the
corresponding checkbox; finally select To confirm your entries.
d)
Verify (filter) the cost centers that have an ID that starts with 123*
and select Run .
e)
View the entire data stream in the workbench. Go to the view of

InfoSitio, navigate to your Inforea Group## and deploy the entire
data stream below its InfoCubo GR##HUB1.
f)
View the data transferred using the BEx Analyzer and the BEx
Query Designer.
14-10-2008
TBW10
Summary of the lesson

You should now be able to:
Define the data flow when using flat files to Load master data and variable
data
Explain the technical details of the interfaces of file and file formats
Design transformations using formulas and InfoFuentes BI
Explain the purpose of the stack and filters of errors in the Data
Transfer Process
Preview the data that would be charged from a data source using flat files
More information
The course SAP BW350 provides a detailed explanation of the items that are
mentioned here. If you cannot attend, use the Web sites included in the body of
the lesson to learn more.
14-10-2008
347
Resumen del captulo
TBW10
Chapter Summary
348
Identify tools for removing and explain why you would use each one of
them
Describe the removal from other databases using DB Connect
Describe the form of removal from other sources using the set Java-based
tools you Connect
Describe the reasons for the load with XML sources using SAP XI
Define the data flow when using flat files to Load master data and variable
data
Explain the technical details of the interfaces of file and file formats
Design transformations using formulas and InfoFuentes BI
Explain the purpose of the stack and filters of errors in the Data
Transfer Process
Preview the data that would be charged from a data source using flat files
14-10-2008
TBW10
Examine sus conocimientos
315
Examine their knowledge

1.
What are true about DB Connect?

Select the answer(s) correct(s).
2.
A
B
C
D
It is faster than you connect.

It is faster than the file interface
It is slower than you Connect
It is the slowest of the options
XML would be good for:

3.
A
B
C
D
Load a shopping cart of an Internet application

Load 10,000 records efficiently
Remove a SAP R/3 system
Remove another BI system
In what areas can help the stack of errors?

4.
A
B
C
D
Identification of erroneous records

Automatic mounting of bad records
Reduction of its dependence on the temporary file
Improving the load times
Using the class of the rule of formula, you can develop a transformation
logic defined by the user without the need to know syntax ABAP.
Say if these statements are true or false.
14-10-2008
Correct
False
349
316
TBW10
Answers
1.
What are true about DB Connect?

Answer: A, B
DB Connect is the fastest of the external methods.
2.
XML would be good for:

Answer: A
The removal tool XML is used to work with small quantities of records of
Internet applications.
3.
In what areas can help the stack of errors?

Answer: A
The temporary file allows you to view the status of the records in several
points of the transformation. Using this feature with the treatment of errors
can see when (at which transformation step) occurred
The error.
4.
Using the class of the rule of formula, you can develop a transformation
logic defined by the user without the need to know syntax ABAP.
Response: Correct
This is true. If you are in the expert mode, you may need to know a little
more, because the system does not verify their logic until the end. In
normal mode, is checked on the fly.
350
14-10-2008
Chapter 5
Business Content
317
In prior instructor note, we said user requirements are the hardest part of a
BI/EDW project This unit shows the students how to leverage our expertise in
business software to establish baselines for the requirement gathering process.
In the Business Content unit, participants are given an overview of the information
model as well as the delivered objects. They also become familiar with technical
concepts, such as the activation of Business Content for example.
Emphasize the advantages provided by Business Content.
If you want to use objects from Business Content in a demonstration, check the
activation status of these objects beforehand.
Chapter Summary
In this unit you will learn what are the components of Business Content and its
applications. With Business Content your project will be driven decisively in the
phase of "requirements definition" of your project BI.
The first lesson is focused in the search of the content you provide SAP, through
the repository of metadata. That is a task for functional members of the project
team recognizable in the business processes involved. Another lesson focuses on
how, from a technical point of view, you can enable this content for use on your
system.
Objectives of the Chapter

At the end of this chapter you will be able to:
14-10-2008
Identify the Content delivered based on roles and sectors
Explain why the content delivered is so valuable
To find the Business Content BI delivered with the metadata repository
Contents of demonstration of reinforcement for start end-user training
Explain the creation of versions SAP BI
351
Captulo 5: Business Content
Describe how to enable content objects
Describe what happens with objects during an upgrade
TBW10
Content of the Chapter

Lesson: Discover Business Content (repository of metadata)...................353
Demo:
Demo
the
MetaData
Repository
Browser
exercise . . .362 Exercise 12: (Optional) Discover Business Content
with the metadata repository browser ...................................................... 365
Lesson: Activation of Business Content.......................................................... 371
Procedure: Installing Business Content....................................................377
Demo: Demo: Activation and match functionality...................................377
352
14-10-2008
TBW10
Lesson:
318
Leccin: Descubrir Business Content (repository de metadatos)
Discover Business Content (repository of metadata)

Duration of the lesson: 25 Minutes

This lesson highlights the objects delivered of SAP Business Content. It also
focuses on the repository of metadata, a powerful tool to find the content
delivered.
Lesson Objectives
At the end of this lesson you will be able to:
This chapter informs participants about available BI Content, and how to find it.
The next lesson in this unit talks about and activation of BI Content.
Business Case
The team of BI want to examine the Business Content to see which objects could
solve their needs of reporting of the cost center. Although Business Content does
not comply with all the requirements, at least will not work from scratch.
Motivation and foundation of Business Content

With Business Content, SAP offers a model of predefined information that helps
you to control and optimize each of the areas of process, both within and outside
the company. Collects and structure the information and prepares it for later use.
Business Content is a preconfigured information model based on industrial
sectors and the roles that include.
14-10-2008
353
TBW10
Business Content includes the following objects:
SAP and non-SAP Extractors
Data Sources (structures of removal)
InfoObjetos
Transformations
InfoSitios (for example, InfoCubos and datastore objects)
Queries/Workbooks
Models (reporting Web-based)
Roles
The following image shows a list of objects next to its icon identifier.
The next to graphics are copies of each other, one just shows icons and the next
shows the answer. Tell the students not to cheat and see how many they know the
description for. Tell them that without cheating it will be nearly impossible for
them to get them all, as there are many icons and associated terms that we have
not discussed.
Chart 137: Objects of Business Content: With the words
354
14-10-2008
TBW10
A client can strengthen the Business Content in three ways. If you choose either of
these three ways, your project will be implemented much faster than a draft
generic, and with BI a probability of success much higher:
Use Business Content without adjustments

Unlikely, this happens perhaps a 10% of the times
Modify the Business Content delivered

Unlike other SAP products, the creation of versions allows both a client
version as a SAP version of the same object. In addition, may be different.
Copy Business Content

In this option, Business Content is used as the starting point (a model).
The new objects are created in the namespace of the client that is no
longer bound to the Business Content (this is how the majority of SAP
products).
Content based on roles and in
industrial sectors
Business Content presents specific contents of application and specific

industrial sector. The specific content of application includes data from the
following areas:
Management of relationship with the customer
Management of relationship with the supplier
Supply Chain Management
Management of the life cycle of a product
Finance
Human Resources
Exchanges (related to oil and gas)
When BI provides content based on industrial sectors, it normally does to support

the industrial sector specific functionality delivered by the OLTP
products intended for industrial sectors of SAP. An example is SAP Retail and
SAP applications for oil and gas.
14-10-2008
355
TBW10
Chart 138: specific content of industrial sector
Note: The specific content of industrial sector includes specific processes

in the industrial sector, ratios and roles for various sectors
Industrial. For more information and an updated list,
see Http://www.sap.com/solutions/businessmaps. You may need to make
a download of the composer of maps of the SAP solution or consult the
appropriate PDF.
BI has, at the time of writing this, various amounts of business content for the
industrial sectors that are listed below. Talk with your account representative SAP
to get the full picture and updated.
Sectoral solutions
aerospace and defense
clothing and footwear
Automotive
Chemical Industry
Consumer Goods
Management of resale and distribution
Health
Pharmaceutic
al Average
Insurance
356
14-10-2008
TBW10
Oil and gas

Public Sector
Trade Real
Estate
The use of Business Content presents many advantages with respect to the option
of starting by your account. Some of these appear in the following list:
All the technical prerequisites and related with the content needed to
connect SAP systems and external already exist, is therefore considerably
shortens the deployment process.
The entries of the customers have made of business content what it is today.
Business Content is currently extended in working groups SAP in close
collaboration with clients.
The InfoCubos are already optimized for performance, both storage

and data analysis.
The analysis and the predefined reports can be used as examples and
prototypes of content for projects. Can also be used as a final
requirement of production. When content is used as an aid prototype the
user already works with the BI application complete and may specify of
corresponding shape what information is missing for the project settings.
With their professional tools, BI offers a beneficial solution and reliable

that account with their own supervision (technical content), controlled
release of content updates (administration of releases and versions), and
a high quality and consistency.
Business Content contains a variety of objects that simplify and accelerate the
implementation of a BI system. Is structured hierarchically. You can make
selections in each level when transferring Business Content. For example, you do
not need to use the ETL process provided by our content if you like the hub
delivered. You can generate each item individually or all items dependent from
each other: from roles, queries and workbooks to InfoSitios to InfoObjetos and
the process of transformation of data (ETL). You provide all the pieces of the
puzzle.
14-10-2008
357
TBW10
Chart 139: A hierarchical structure of Business Content
Say, for example, that a regional sales director needs access to a wide spectrum
of information that would enable it to take effective decisions. A role of business
content groups the data in the form of queries and workbooks that contain
exactly the type of information that is needed by the director of sales.
Chart 140: Example: Regional Sales Director
358
14-10-2008
TBW10
Metadata Repository
Metadata means "data about data." Metadata is information descriptive technique
on the objects used to build your application, in this case a BI system. The
metadata about a InfoCubo would include the names of the InfoObjetos and
dimension tables used in the InfoCubo, as well as the date on which it was
designed and the person who last modified the design. Would not include a record
in the InfoCubo, because that are data, not metadata. Another example would be
the data on a InfoObjeto; these would include the metadata field length, who
created it and when it was created. It would also include any other information
about the screens used to create the InfoObjeto.
Each object has its own metadata table to store the technical information about
that object. There are metadata tables to store information about InfoCubos,
InfoObjetos, DataStore objects and everything else.
When all the metadata tables are contained in a group, we have a repository of
metadata. To observe the objects and the relations between them, we have a tool
of navigation of the repository of metadata.
Note: To simplify, does not distinguish between the collection of metadata
tables and the tool to access and view them, we simply use the same term,
repository of metadata.
There is also a new InfoCubo (0BWTC_C08) that contains the data as all other
objects of Business Content. This allows, for example, create a query that lists all
the queries of a Inforea.
Note: The new metadata InfoCubo BI is explained in the course SAP
BW330.
Basic functions of the repository of metadata
(RMD)
You can access the repository of metadata from the Workbench (DWW) using the
pushbutton Repository Metadata. The following image is displayed.
14-10-2008
359
TBW10
Chart 141: initial screen of the metadata repository
You can start your search by selecting the Search link in the repository
metadata or by selecting one of the icons of objects in the right area of the
window. In this last option, after displaying the list, you can use CTRL+F to
find the object that you are interested in using a search term. Do not forget to
select the category of the objects that you want before you select the object on
the screen. Using the appropriate link in the area
Left side of the screen, you can configure the right area of the screen to include
only those objects enabled, such as the objects of Business Content that you are
currently using and the who created their customers, or simply Business Content.
There are many options and sets of various information available while browsing
the repository. You can view, for example, all the queries of a InfoSitio or
characteristics that constitute the InfoSitio in itself.
Data Flow Charts

An excellent feature is the data flow charts. The data source and the flow of data
are of interest when working with multiaplicaciones analysis.
Using the function data flow in the repository of metadata, the source can
withstand graphically the data flow throughout the route to the destination for
each object that has been previously selected. This includes roles, InfoCubos,
queries and workbooks.
360
14-10-2008
TBW10
Chart 142: Data flow for the metadata repository
Using the activated section (not BI Content)of the metadata repository select the
infocube icon as a starting point then use Cntrl F to search and find the cube build
in class. Access this cube FFthen select show data flow, to demo the above feature.
Viewing and navigation of the star schema

Another feature that offers RMD is a graph of the star schema to its contents or
our content. As in the previous data flow, you can "click" on the chart of the star
schema. For example, you can navigate to the master of a InfoObjeto by
selecting it in one of the tables of dimension of InfoCubo.
14-10-2008
361
TBW10
Chart 143: repository of metadata: Display of star schema
Demo:
Demo the MetaData Repository Browser exercise
Objective
Show the features of the MDRB
System Data
System:
Same as class
Principal:
Same as class
User ID:
Same as class
Key of access:
Same as classsame ace class
Parameterizations of the system: None
1.
Demo the exercise. Or you could have worked it in during the presentation
of the slides above. Note the search engine sometimes does not work, one
option would be to use the Control (Cntrl) key +F to perform the search.
Other areas of Business Content

There are other features and tools that provides SAP in Business Content and that
will be useful to you.
362
14-10-2008
TBW10
SAP DemoContent
With SAP DemoContent are delivered sample data along with the metadata of
Business Content. They can therefore be displayed quickly complete scenarios of
demonstration of different lines of business, and exposure to SAP NetWeaver
Business Intelligence can be obtained even before receiving real data from
His side OLTP.
As SAP DemoContent is specially designed for demos, has its own nomenclature.
The technical names of all objects DemoContent begin with 0D_. In this way, are
completely independent of the objects to store the actual data from your company.
Nor are appropriate for a productive use; however, you can use them as models if
you want.
SAP DemoContent offers you a demonstration scenario that can be activated in
a few steps. To transfer a specific object of SAP DemoContent,
Select InfoCubos
SAP demonstration and select the objects DemoContent
You want to transfer.
The following sample cubes are in SAP DemoContent but more can be added with
each package of support.
Cube sample to shopping cart
Cube sample for account of results (CO_PA)
Cube sample for Sales

Note: You can find additional information in the online
documentation of BI.
Show DemoContent via InfoArea with a search control (F) on 0D.
Integration of Dun & Bradstreet

Dun & Bradstreet (D&B) is one of the leading suppliers in external data from
market. The available data consist of information on companies and structural
information on groups of companies and business groups (the
14-10-2008
363
TBW10
"Family Tree" of a company), and is a proven and valuable business tool both for
marketing as for shopping. The objectives of integrating data from D&B are the
following:
Connect operational data of sales with marketing data
Identify new key customers
Determine new markets
Benchmarking with the industrial zone

Note: Search sap.com for more information. A suitable place to
begin your search is Http://www.sap.Com/solution- tions/businesssuite/srm/pdf/BWP_SID_Strategic_Sourcing.pdf for
D&B involved with the origin of transmission of orders.
A class CRM/BI called CR900 is also dedicated to this integration.
Contents of customers and partners

The content that customers or SAP Consulting partners bring to their divisions or
its customers refers to an expert in the sector of goat milk. If you wish, could
create a sales InfoCubo of goat milk and provided to all its customers. Another
option would be for a very important client, for example the United States
Department of Defense, create InfoCubos free global definition and handing them
over to draft BI of the army and the Navy as the content of the client. The
functionality of the content of customers or partners extends and expands the
options for using Business Content delivered by SAP. The concept and the
technical conversion of content of customer and partner are very similar to the
content delivered directly by SAP.
The content of customers extends to the following areas:
364
The development of an infrastructure of specific customer systems
The delivery of SAP Business Content by SAP
The development of specific content of client on the part of customers
The alteration of SAP Business Content
Content delivery of clients by the clients to their own customers
14-10-2008
TBW10
329
Exercise 12: (Optional) Discover

Business Content with the metadata
repository browser

Use the repository of metadata to search Business Content
Check if an object of Business Content is already active
Business Case
It has introduced a BI system in your company or is already in use. It seems that
now there are more requirements of report of controlling. He would like to know
if there is already a InfoCubo of controlling available in Business Content for the
accounting of cost centers that you can use in place of the InfoCubo that you
have created yourself.
Council: below to access the metadata tables using the browser tool
repository of metadata. But there is no
No formal tool with that name, you are only referred to as metadata
repository, and is accessed by a push button with that name.
System Data
System:
Assigned System
Principal:
800
User ID:
Assigned User ID
Key of access:
Assigned password
Parameterizations of the system:
Task: Use the
Metadata Repository Browser
Get a summary of the InfoCubos in the area of accounting for cost center. To do
this, search for this InfoCubo in the list of characteristics and ratios. Display the
breakdown of network data flow and get a general view of the queries that are in
the InfoCubo.
1.
Open the repository of metadata and change to the area Business Content.
You will get a list of all the object classes available.
14-10-2008
365
2.
TBW10
Select the object class InfoCubo. You will get a list of all InfoCubos of
Business Content, sorted alphabetically.
Locate InfoCubos in the area of accounting for cost centers that begin
with co-OM-CEC. Do this by opening the search functionality
with CTRL+F and entering the search string.
3.
How many InfoCubos found for this area?
4.
It is mainly the InfoCubo costs and charges. Look closely at the

characteristics and ratios of this InfoCubo.
5.
What ratios are available in the InfoCubo?
6.
Are there any navigation attribute enabled for this InfoCubo?
7.
Discover what dimensions are defined for this InfoCubo. Note the star
schema of the InfoCubo.
366
14-10-2008
TBW10
14-10-2008
8.
What dimension can find the InfoObjeto indicator

sender/receiver?
9.
Branching your search toward the objects connected to the repository of

metadata and verify if the InfoCubo 0CEC_C11 is active and present in the
system. Are you available?
10.
An alternative to the browser of the repository of metadata is the SAP

Help Portal: help.sap.com. Here you can check the current Business
Content.
367
TBW10
Solution 12: (Optional) Discover

Business Content with the metadata
repository browser
Task: Use the
Metadata Repository Browser
Get a summary of the InfoCubos in the area of accounting for cost center. To do
this, search for this InfoCubo in the list of characteristics and ratios. Display the
breakdown of network data flow and get a general view of the queries that are in
the InfoCubo.
1.
2.
Open the repository of metadata and change to the area Business Content.
You will get a list of all the object classes available.
a)
Select Menu SAP Easy Access

Repository Metadata.
b)
Select Business Content
Modeling
Workbench:
Local objects.
Select the object class InfoCubo. You will get a list of all InfoCubos of
Business Content, sorted alphabetically.
Locate InfoCubos in the area of accounting for cost centers that begin
with co-OM-CEC. Do this by opening the search functionality
with CTRL+F and entering the search string.
3.
a)
Select the object class InfoCubos.
b)
Press CTRL+F to open the search field and enter

CO-OM-CEC. Start the search by selecting Find Next. It should be
located in the appropriate InfoCubos.
How many InfoCubos found for this area?

Answer: You should see four InfoCubos with a description that begins by
co-OM-CEC, but this could be modified to the extent that new content is
added.
4.
5.
It is mainly the InfoCubo costs and charges. Look closely at the

characteristics and ratios of this InfoCubo.
a)
Select the InfoCubo 0CEC_C11.
b)
To verify the characteristics and ratios, scroll down.
What ratios are available in the InfoCubo?

Answer: The ratios 0AMOUNT AND 0quantity are available.
368
14-10-2008
TBW10
6.
Are there any navigation attribute enabled for this InfoCubo?

Answer: The center of benefit is the only attribute activated navigation
for this InfoCubo.
7.
Discover what dimensions are defined for this InfoCubo. Note the star
schema of the InfoCubo.
a)
8.
Select the link InfoCubo - schematic display as star schema.
What dimension can find the InfoObjeto indicator

sender/receiver?
Answer: The InfoObjeto indicator sender/receiver is included in the cost
element dimension.
9.
10.
Branching your search toward the objects connected to the repository of

metadata and verify if the InfoCubo 0CEC_C11 is active and present in the
system. Are you available?
a)
In the repository of metadata, choose Objects activated.
b)
You will get a list of the object classes. Select the object
class InfoCubos.
c)
All InfoCubos are displayed in the system that are present in the
active version. To know the InfoCubo 0CEC_C11, use the search
functionality.
An alternative to the browser of the repository of metadata is the SAP

Help Portal: help.sap.com. Here you can check the current Business
Content.
a)
14-10-2008
369
TBW10

370
14-10-2008
TBW10
Lesson:
334
Leccin: Activacin de Business Content
Activation of Business Content

Duration of the lesson: 45 Minutes

In this lesson you will learn how to transfer or activate Business Content so that
you can use it really.
Lesson Objectives
In this lesson you will demo activation BI content, make sure the students
DO NOT FOLLOW along. Tell them to stay out of this area as it could cause a
lot of trouble.
Business Case
The team members with functional knowledge of its deployment team BI have
revised Business Content by areas using the navigator of the repository of
metadata. You have been advised that believe that some objects are ideally
suited to your needs and others are quite
Appropriate, but it will take some modifications after activation. Its task is to
review the repository of metadata and determine which objects are ideally suited
to your business needs; then you must activate them for their use and subsequent
improvement by using the tools in BI.
Versions of metadata objects

BI allows upgrade of three different versions of the same object. For example, in a
version of the InfoObjeto 0COSTCENTER, field length should be 10 characters,
in another 12 and in the third, 13.
Versions of the objects of Business Content
14-10-2008
Version
Meaning
E(ntrega)
Version of Business Content
A(ctivo)
Active Version
M(odificado)
Modified Version
371
TBW10
The only version really involved in data storage is the active version, which is
entirely under the control of the client. The objects of Business Content is first
delivered in version D, which means that the objects exist in the system, but
cannot be used for models and applications. An object of Business Content is
transferred to an active version if it is transferred from the content. If an object of
BI content is modified, in order to store the object with different options, you
assign the M version (modified). The modified version can be considered a
version pending, but in this state, once again, is not used for any real work in the
BI system. If the technical team approves this version pending, or more
technically modified, should be activated and become the active version (A). This
is the only version that really counts. The version of Business Content is not
editable by the client. The second aspect to take into account of this is that SAP
does not alter its versions (M and A), even during an upgrade to a new release.
Note: The creation of versions in BI is not like the creation of versions in
other SAP products. For example, in the majority of SAP products can
retrieve any modifications made with an ABAP program
Because it records the history of all the different versions of the program.
This is not true in the case of SAP BI. If you enable an object, you cannot
return to a client version (M OR A) above the object. However, you can
return to the version of Business Content, since you cannot modify it.
Before using Business Content you must first transfer the identified objects to an
active version. BI provides a simplified activation process to do this in the that
can activate specifically the objects or scenarios required by dragging and
dropping. To maintain consistency, all relevant components and dependent can be
triggered automatically and simultaneously.
Once you have completed the activation process and the data is loaded, you can
use the entire Stage.
Note: Before activating parts of Business Content, you can find more
detailed information on the technical content and the Business Content
of individual components in the documentation online BI of SAP Help
Portal at Help.sap.com
Or more specifically, in Http://help.sap.cOm/saphelp_nw04S/helpdata/IN/C1/EA683cc5e8CA68E10000000To114084/content.htm
Activation of Business Content

The transfer of business content or more technically, the modification of a
version D of Business Content by a client version A, is best performed with the
GUI of activation of Business Content. However, before using this GUI, note the
following image, which follows an object through the initial activation and a
subsequent improvement by part of SAP in the next release or in a package of
support.
372
14-10-2008
TBW10
Chart 144: Creating versions of SAP Objects BI
Follow-up of the black arrows in the image above:

1.
SAP Business Objects delivery content in version D; subsequent changes

are recorded in the M. once revised and approved by the client, version M
is activated and becomes the active client version (A).
2.
SAP delivers Business Content Objects in a version D new as part of an

upgrade. The customer can compare the new Business Content with your
version of the client is active and adopt (copy) the new version or combined
with yours (in some cases). It then becomes the new active version.
The actual process of activation of Business Content is greatly simplified using

the administration of business content using the pushbutton Business Content of
the workbench.
14-10-2008
373
TBW10
Chart 145: Simple Installation of Business Content
In the use of this GUI, initially (1) You must select a procedure of grouping. The
procedure of grouping determines what objects related content must be taken into
account for the activation. For example, a InfoCubo will not activate unless
activated first the InfoObjetos. The groupings to meet all the objects in a single
area:
Only the necessary objects: Only including those additional objects that
are needed to activate the objects you have selected (selection minimum)
Preceding data flow: collected all objects that pass data to another
object
Data Flow later: collect all the objects that get data the initial object
Previous data flow and later: collect all the objects that deliver and
receive data
Security for the copy system: With this option you can collect only some of
the objects for a transport request; this request can be added once again after
you have made a copy of System
If you selected to start the collection mode manually, the scene or object can be
selected in the first place; however, it is worth making the grouping option first.
374
14-10-2008
TBW10
Then (2), you can search for individual objects or complete scenarios of Business
Content at different levels:
By Inforeas InfoSitios: List of InfoCubos, aggregates, DataStore, and

InfoObjetos objects (that have data teachers) according to the Inforeas
InfoObjetos by application components: List of InfoObjetos according to

the catalogs of Inforeas e InfoObjetos
InfoFuentes by application components
Roles: List of roles by Industry
Object classes: List of all objects classified according to the class (as
Inforea or InfoCubo). The aid for entries is available for each class. You
can add the selected objects to the tree. This list of personnel objects is
classified for each user and is available each time the user starts the program.
Objects in patches BI: List of all support packages of BI installed. It also

lists the new objects or which are delivered again with each support
package.
Transport Request: List of all objects by transport request
Packages: List of all objects by package (formerly known as a class of

development)
Following the selection of the strategy of previous search, you can move the
stage or the selected object by dragging and dropping it on the window
Collected objects. Assuming that the collection is configured to start
automatically, (in seconds) will be ready for the final step, (3) Install Business
Content objects.
Continuing with the example shown in the graph in the window on the
right, called collected objects, are displayed all the dependent objects that
belong to the selected role. The scope of the objects is specified by grouping.
If there are objects that belong to the role that have not yet been transferred, the
transfer is compulsory and is indicated with a marker in the column Install. You
can leave any objects for the roles that have already copied in the existing version,
or you can return to copy. If it is possible to combine the version of content and
the active version; shall be indicated in the column support (X) or Copy.
With the function you install , you can simulate the transfer of Business Content
or really perform, either directly or as a background process. A third option
involves the transport.
Note: As the transport is a basic task, it will be covered in the BW360.
Normally do not begin from a role to take all
Above objects, because that would imply too many objects, which
would add complexity.
14-10-2008
375
TBW10
Merger and copy during an upgrade

It is necessary to have a special explanation to mention what happens to their
client version enabled once activated and subsequently amended, so that it is
different to the original version delivered.
What happens if SAP modify an object that you (the customer) already use
and that have been modified by the needs of enterprise own? Do we will
lose our modifications?
Do not happen anything to his active version, unless he so desires or who
commits a big mistake.
Remember that your versions (the client) are modified and enabled. SAP does
not overwrite never during the upgrade. Only deliver versions D new and
improved during the upgrades. If you do nothing, there shall be no
Changes in their versions controlled by the client. If you try to install your
business content again, overwritten, merged or ignore the difference between the
two versions.
If you select or leave checked the check box to install and do not select the
checkbox merge, the client version is deleted and replaced by the new version of
Business Content. If you mark both combined ( if available) as Install, SAP will
attempt to combine the two objects. The total would be composed of the
properties of the two combined objects (where possible) and would be recorded
as a new version of client is active.
Tip: The Merge option could also be called "compare and merge if you
want".
Even if the merger is selected, for some properties the customer can select in the
dialog which you want to transfer. For example, you cannot combine field lengths
of 10 and 15 characters and get 25; should take one or the other. On the other
hand, if you added an attribute to 0Material and SAP had also added another
different, when you choose to combine the end result would be an object with the
new attributes of both.
Not all objects support the merger. Particularly, this includes transformations
and queries. If you do not perform a combination or if this option is not
available, adopts the version delivered by SAP and active client versions are
overwritten when the Business Content.
Note: Business Content can be a powerful tool, but if you do not have
sufficient knowledge, can be dangerous. This tool should only be within
the reach of a few administrators for your company because ignorance
could potentially overwrite its enlargements in
Business Content.
376
14-10-2008
TBW10
Installation of Business Content

340
1.
Navigate to the Workbench to Install Business Content (selection of

objects, options for the transfer and the start of the transfer).
2.
Assign relevant source systems.
3.
Group the objects that should be included and determine the mode of
collection for the objects.
4.
Determine the view of the objects from which you want to start its installation.
5.
Transfer the objects into collected.
6.
Check the options for the objects compiled with reference to the functions
available to install, merge or copy and functions available in the active
version.
7.
Perform the parameterizations of the selection list and transfer them.
8.
Please correct the errors.

Note: You can find a detailed version of this
procedure in the SAP Help Portal:
Help.sap.com, or Http://help.sap.cOm/saphelp_NW70/helpdata/IN/e3/E60138fede083of10000009b38f8cf/frameset.htm.
Demo: Demo: Activation and match functionality

Objective
To demo the activating and merging BI Content
System Data
System:
Same as class
Principal:
Same as class
User ID:
Class (You might need to use your training ID,
with the profile SAP_ALL if authorizations for this task have been removed
for the student IDs).
Key of access:
Same as class
Parameterizations of the system: This demo only supports one BW310 class
on the same box. You will have to tailor it if someone else is teaching BW310
On your box. For example you could use the Content Object 0AB_DS01 and a
different inactive InfoObject.
14-10-2008
377
TBW10
1.
Explain that we will cover many of the necessary steps for content
activation. Then say the following to the students: Please feel free to access
the help above when you get back to your real job, but do not, follow along
with me while I do this demo!
2.
I want to show you the delivered version of to BI Content DataStore

Object 0AB_DS03, it only exists in the Content version, and it includes
some objects which are themselves not active, as well as some that are.
Access transaction RSDODS and change the version to the content version.
If you do not do this then you will not find the object 0AB_DS03, as it only
exists in the Content version. Display the delivered version of the DataStore
Object. Show 0AB_ABART - Settlement Type In agency Business, it is one
object that is currently inactive.
3.
Then go to the BI Content GUI access it from the DWW.
4.
Select the Source System Assignment icon in the center top of the screen,
and assign the source system T90CLNT090.
This list contains just the systems that feed data to your BI system and it
would in most cases be ok to have them all checked. The system will then
find dependant objects (transformations and data sources) from all these
systems. As a side note, a new feature in BI 7.0 is the remote activation of
the BI Content data sources on the source system, for prior releases this had
to be done in transaction SBIW in the source system itself (covered in
BW350).
5.
Ensure that the collected objects window is on, and select the grouping
icon to Only Necessary Objects.
In this case I am just doing a demo, but if I wanted to actually load data in
this DSO, I would select all objects before in the data flow.
6.
7.
The GUI should be set to INFOPROVIDERS by INFOAREA on the far left

pane as a default. Instead, select the object types option on the far left pane.
Now expand Data StoreObjects and the select the Select Objects icon. The
DSO 0AB_DS03 should be close to the top of the list, select it with the
cursor and then hit the TRANSFER button, to move the object to the
collection window.
Collection should start automatically.
After collection, you should see many objects in the collected objects
window. We are not going to activate this DSO, because if we did we would
need to activate all the objects that are now displayed in th install section,
besides taking a while, it would ruin the demos by other instructors on the
same box, OS lets just look. Notice, the match box is not checked for any
objects that have not yet been installed, but it is checked for the objects that
have already been installed (with the calendar icon, like 0CO_AREA). Also
note that the match choice is not always available.
378
14-10-2008
TBW10
8.
Now lets focus on just a simple InfoObject, this one does not even have
any master data, 0AB_ABART. Drag and remove the 0AB_DS03 from
the
Collected window and start a new collection for the InfoObject
0AB_ABART. Following the steps above, but this time for the object type
pick InfoObjects.
9.
After the very quick collection, install the InfoObject via the Install button.
We will do a very quick collection because this InfoObject hast thou not
dependent master data. Lets look at the log at the bottom of the screen.
Green is good Red is bad.
10.
Now we are going to make some changes and activate these changes in our
InfoObject. Change the InfoObject 0AB_ABART in transaction RSD1.
For example select the with master data check box and add costc##, as an
attribute (co_area will be needed due to compounding), also add the medium
text and a-check short text. Then activate the InfoObject. Read the warnings
but activate anyhow. Leave this transaction and return to the main menu!
11.
Return to the BI Content GUI and remove and reinsert 0AB_ABART in the
collection window with drag and drop. It should be under the selected
objects already. Select the Install check box for 0AB_ABART, and this
time a-check the defaulted match option, which is available for this object
type.
Install the object and then return to RSD1 and access the active version again.
Because we did not choose the match option, our changes are overwritten!!
12.
Return to change the InfoObject 0AB_ABART again in transaction RSD1.

Show that the settings reverted back to the BI Content settings. Now repeat
the changes again: select the with master data check box and add costc##, as
an attribute, also again change from short to medium text but this time add
time dependency to the text table . Activate the changes, read the warnings
but activate anyhow. Leave this transaction.
13.
Return to the BI Content GUI (start it from the main menu) to ensure it gets
a fresh start, then remove and reinsert 0AB_ABART in the collection
window. It should be under the selected objects already. Select the install
check-box, and this time leave the defaulted match check-box as well, which
is available for this object type. Install the object.
Because we selected match, we are given choices where to match is not
exactly clear (e.g. time dependency on the text table). Do we want to keep
the active versions settings, or do we want the settings of the deliver content?
In our case we want to keep the settings of the active version, with the
exception of short text, where we want to keep the delivered version on
"Yes".
Then return to RSD1 and access the active version again. Because we
did match, this time our changes are not overwritten, the object is just
"improved" !
14-10-2008
379
TBW10
Discussion with moderator

Should you use our content and change it or copy our content leaving no
connection to the original content.
Questions for discussion

Use the following questions to the course participants take part in the discussion.
You can also use your own questions.
Why is it better that just a few people in your company have access to BI Content
activation?
Why does it make sense to only activate the objects you need?
Tip: Do you want to deal with this "match"decision?
What would happen to all the follow on BI content if the customer made a copy
of 0material into Cmaterial or Zmaterial?
Tip: You would be making the decision, that all follow on objects must
be changed, as they refer to the original 0material. Is this what
You want to do?
380
14-10-2008
TBW10

More information
See help.sap.com for more information on this topic.
14-10-2008
381
Resumen del captulo
TBW10
Chapter Summary
382
14-10-2008
TBW10
Examine their knowledge
343
1.
Some advantages of Business Content are:
2.
A
B
C
D
Is preconfigured and has a global reach.

Accelerates the deployment.
Costs millions of additional dollars.
Enables the rapid creation of prototypes.
The
you locate Business Content available.
It is a tool that helps
Fill in the blanks to complete the sentences.
14-10-2008
383
344
TBW10
Answers
1.
Some advantages of Business Content are:

Answer: A, B, D
Business Content is virtually free with the purchase of SAP BI. There
could be exceptions, so you should contact your account representative
SAP.
2.
The repository of metadata is a tool that helps you locate Business

Content available.
Answer: Metadata Repository
You can also use a metadata InfoCubo SAP NetWeaver BI 2040s new,
and run reports BEx with lists of objects BI. (This is in BW330)
384
14-10-2008
Chapter 6
Other InfoSitios
345
This unit enter the DataStore object, which is an additional data target in BI, in
fairly good details. In addition, we go in some detail on multiproviders, in a
summary way we address the remaining InfoProviders.
Chapter Summary
In this unit you will learn about the functions and technical properties of the rest
of InfoSitios and a InfoCubo.. Also we will identify and distinguishes between
the InfoSitios that contain data in physical form and which are not. The main
theme of this unit will be the DataStore objects and the multisite.
Objectives of the Chapter

At the end of this chapter you will be able to:
14-10-2008
Describe the structure of the objects DataStore (ODS)
Appoint and define the classes of objects DataStore
Compare PSA, DataStore and InfoCubos objects
Position DataStore objects within the Data Warehouse of a company
Load and activate data in a standard DataStore object
Integrate a new object in an existing data flow
Define the terms and InfoSitio destination
Explain the different tools in SAP BI for special reporting requirements
Explain when to use VirtualProviders
Describe how SAP BI supports the operational reporting in real time
Build a multi-site
Enumerate some uses and limitations for multisite
Explain queries for a multi-site
Explain the uses of InfoSets BI
385
Captulo 6: Otros InfoSitios
TBW10
Set the difference between classical and InfoSets InfoSets BI
Content of the Chapter

Lesson: DataStore Objects................................................................................. 387
Procedure: Creation and fill a DataStore object..................................... 408
Demo: Creating a DataStore object and filling it.....................................408
Procedure: Fill of destinations of data connected with a data transfer
process (delta or full) .................................................................................... 412
Demo: Demo Second Exercise of the lesson, to integrate the new
cube connected to your existing DSO ..................................................... 412
Exercise 13: Creation of a standard DataStore object..........................413
Exercise 14: DataStore objects in the data flow (optional).................. 429
Lesson: VirtualProviders and real-time data acquisition............................. 437
Demo: Direct access and virtual cubes.....................................................444
Lesson: multisite and InfoSets BI...................................................................... 451
Demo: Demo both exercise if you have time, if not leave the query one
out!. .................................................................................................................. 459
Demo: InfoSet..................................................................................................462
Exercise 15: Definition of multi-site............................................................ 465
Exercise 16: (Optional) Create a query of multisite............................... 471
386
14-10-2008
TBW10
Leccin: Objetos DataStore
DataStore Objects
Lesson:
347
Duration of the lesson: 120 minutes

This lesson explains the DataStore objects, how they are structured and the
ways in which it can be used. After building a DataStore object, we will study
the more complicated aspects, which include the integration of new objects in
the flows of existing data.
Lesson Objectives
Describe the structure of the objects DataStore (ODS)
Appoint and define the classes of objects DataStore
Compare PSA, DataStore and InfoCubos objects
Position DataStore objects within the Data Warehouse of a company
Load and activate data in a standard DataStore object
Integrate a new object in an existing data flow
This lesson introduces the DataStore Object in its role as an additional data target.
Explain that this is such an important topic we need cover it in detail. We have
two lesson, the first is in this unit, the second one is in the administration unit.
Also explain that in 3.x this object was called an Operational Data Store (ODS),
but to keep consistency and meaning in our terms, we now call them DSOs.
Business Case
Your company is about to remove a system of reporting of old sales. Although not
finished with its decisions of InfoCubo modeling, your sales team has decided to
use a DataStore object to store data from this old system before it disappears.
To ensure that this is a correct decision, you want to evaluate the DataStore
objects and their features and functions. You also want to make sure that you can
add a InfoCubo to the flow of data in the future.
DataStore object: use and features

A DataStore object is used to store consolidated data and cleansed (variable data
or data teachers) to document level (atomic level). Although the DataStore
objects can store data teachers, and there are valid reasons to do so, mainly
stored data variables detailed. The Objects
14-10-2008
387
TBW10
DataStore are positioned in the design of general warehouse, as shown

below. Can be used to support the detailed reporting
Operations, or be part of the store in which can be used to accumulate years of
data "potentially required".
Chart 146: DataStore objects: Use
One very important difference between objects and InfoCubos DataStore is that
the DataStore objects have the option of overwriting records, while the InfoCubos
no. Here is a big difference! The cubes create a new record if the features are not
exactly the same in two different records. For example, don't I would like a new
record if you loaded the same customer order once with status Pending and
another with status closed? I think that he realizes that the answer in most cases is
no.
388
14-10-2008
TBW10
Features and functions of DataStore objects
Designed to record data purged at a document level

-
Consolidated or overwritten
Overwrite function
The features that do not form part of the record identifier (key) are
always overwritten (for example, order status)
The ratios (for example, the volume of sales or the number of lines of
document) can be fixed in Overwrite, Add or do not update
Reporting by BEx
The direct reporting is optional (DataStore is used for objects

positioned in the DataStore section operations)
May not be available** for objects DataStore used for staging and
storage functions of raw data in the section of the store of your
architecture
** would not be granted any authorization to inform users of these

objects DataStore
The normal reporting scenarios involve a breakdown from the

InfoCubo the DataStore object
Given that an object DataStore is designed as a table, contains key fields

(Number and position of document, for example) and data fields. The data fields
can not only be ratios but also character fields (status of order, customer or time,
for example). You can use a delta update to update object data DataStore on
InfoCubos connected or in additional DataStore objects or data tables teachers
(attributes or texts) on the same system or on different systems.
On the contrary that the memories of multidimensional data for InfoCubos, data
in the DataStore objects are stored in database tables flat and transparent. The
fact and dimension tables are not created.
With the DataStore objects can not only update ratios on a cumulated basis, as
with the InfoCubos, but also overwrite data fields. This is especially important for
transaction-level documents that are modified on the source system. In this case,
the modifications of documents not only involve numeric fields, such as order
amounts, but also non-numeric fields as recipients of goods, delivery date and
status. Given that the OLTP system overwrites these records when changes occur,
the DataStore objects must often be modeled to overwrite the corresponding fields
and updated to the current value in BI.
14-10-2008
389
TBW10
Object classes DataStore

SAP BI distinguishes between three DataStore object classes: Update standard,
optimized for writing and direct upgrade. These three classes of DataStore objects
are shown in the following image.
Note: We are going to focus on the standard DataStore objects. In the
course SAP BW330 (data modeling) there is more information available
on
The other two classes. Use the image below as a starting point. After you
learn the details of a standard DataStore object, will be in a more
advantageous position to learn the uses and the complexity of the other
two classes.
Chart 147: Three different kinds of objects DataStore
The DataStore object consists of three standard tables (queue of activation,

active data table and log of amendments). Is fully integrated into the process of
staging. In other words, the data can be uploaded and downloaded from the
DataStore objects during the staging process. Use a log of changes means that all
modifications are also written and are available as uploads delta to connected data
destinations.
Optimized for writing is a new object type DataStore. It is addressed to the
warehouse level of architecture and has the advantage of a faster loads.
A direct upgrade DataStore object (transactional ODS previous 3.x) has only
the table with data assets. This means that is not integrated so easily in the staging
process. Instead, this object class DataStore is populated using APIs and can be
read through a BAPI. The following code is delivered for this use:
BAPI BAPI_ODSO_READ_DATA_UC
390
14-10-2008
TBW10
RSDRI_ODSO_INSERT
RSDRI_ODSO_INSERT_RFC
RSDRI_ODSO_MODIFY RSDRI_ODSO_MODI
FY_RFC RSDRI_ODSO RSDRI_UPDATE_ODS
O_UPDATE_RFC RSDRI_ODSO_DELETE_RF
C
Although we do not allow much time to focus on this object class DataStore, it
may be found in the common use by professional analysts front end and behindthe-scenes in SEM BCS. The following image shows where you normally use the
DataStore objects of direct upgrade.
Chart 148: object uses a direct upgrade DataStore
We have hours more to spend learning about Standard DSOs in this and one more
lesson in this class, so you have not learned it all yet!
14-10-2008
391
TBW10
Comparison of PSA, DataStore and InfoCubos objects

The PSA store data source raw, the InfoCubos stored summary data and there
are three classes of objects DataStore. Here is a quick comparison of these three
objects before they let us go deeper into the standard DataStore objects.
Comparison of PSA// InfoCubo DataStore object
392
Objeccough/Properti
es
Method, u
Persistent
Staging
Area
Inter- memory
DataStor
e Object
InfoCubo
se
media/currentnization/restructu
ring- turar
destinations after
loading errors
Harmonization/
consolidation
and mass storage
(as part of the
store on an
Enterprise Data
Warehouse)
Aggregation/Op
- timizacin
query
performance
Data Storage
Buffer Memory
for master data
and variables:
approx. 30-60
days (date can be
stored for a long
period of time if
you do not use
any object
DataStore)
Storage for
variable data and,
less frequently,
consolidated
master data:
permanent, 1-10
years.
Storage for
variable data:
permanent, 5-10
years.
Data Source
Dependent on
data
source
(dependent on
the
source
system)
Purified data
(independent of
the source
system)
Purified data
(independent of
the source
system)
14-10-2008
TBW10
Handling
(during charging)
Add
Modimodify/add/Borrar
Add
Architecture
Tables relational
databases, key
dependent on
request
Tables relationa
l databases,
standardized,
the records have
a key business
relevance
Star Schema
BI, not
normalized
Reporting
High
granularity of
data (Access
using query of
InfoSet); is not
normally used
in reports
High
granularity of
data (reporting
flat)
Low granularity
of data (reporting multidimensional)
The primary use of the Persistent Staging Area is temporarily store the data from
the source system before being transferred to the destinations of actual data.
Therefore, you cannot modify the data of the BI system before
The PSA. Here are only makes a copy of the data from the source system
(memory buffer incoming).
The DataStore objects are used mainly to harmonize or consolidate data. Are
especially appropriate for this use, since they provide a number of different
options. For example, you can influence the data flow before the DataStore
objects (PTD) using the configuration of different classes of update (Overwrite,
Add, no update). On the other hand, objects DataStore are formed by flat tables
that can be read in a simple way (serve as distribution tables, for example). The
objects themselves contain many functions (determination delta, for example).
Taking into account all these properties, objects DataStore cover many of the
demands that are made within the staging process.
The InfoCubos are designed on the concept of star schema, which is a
multidimensional structure optimized for reporting. The InfoCubos allow the
definition of aggregated views stored persistently (added).
In the last unit of this class we will see how these aggregates improve
performance in reporting.
14-10-2008
393
TBW10
Data History
If you compare the history of these three objects, you can see that the data of the
PSA normally are not preserved during more than a month. This implies that the
DataStore objects are also included in a scenario of staging. If this is not the case,
it makes sense to use the PSA as permanent memory for the data supplied by the
source system.
The data are normally retained for a few years in DataStore and InfoCubos
objects. The difference here is that the data is stored in granular form in the
DataStore objects and on an aggregated basis in the InfoCubos.
Note: You may have auditing requirements that may require you to
maintain data PSA during more time.
Data Source
The PSA data is stored in the form of transfer structure. Is dependent on the source
system (assigned uniquely to a source of data).
The data is always updated in a DataStore object from a data transfer process
(DWP). Optionally, a InfoFuente can be found in the process of staging and the
InfoFuente can supply data from one or more (other) source systems or from
another DataStore object that is in the same BI system.
Note: Technically, it is also possible to connect a source of export data
generated from a InfoCubo to an object DataStore. Without
However, this flow of objects of hub to DataStore is used in practice very
infrequently. Normally, the flow is from the DataStore to InfoCubo object,
and not the other way around.
Data Manipulation
You can also observe differences between the three objects if analyzes the
manipulation of data by an upload of new data (in the area of the staging process).
The new records is always added to the PSA and the InfoCubos, since both
objects store the technical key of the charging process.
Running a upload of new records with standard DataStore objects can modify
previously existing records (overwriting or adding values) or even by deleting
them.
Note: It is possible to delete records when the connected data source
provides images of cleared (technically: 0RECORDMODE = D). You
can also add new records provided that there are no longer any records
that have the same key in the system.
394
14-10-2008
TBW10
The PSA is stored in the database through a transparent table by data source.
Each of these tables has a key (technical), which consists of a request, a data
packet and a data record number. All other fields are fields without key. A
DataStore object is also stored in a transparent table in the database. However,
this is a key semantics (related to the company) and may be determined by the
responsible for modeling (order number and position, for example). All fields
without key is indicated as data fields.
A InfoCubo is represented by multiple tables, given that it is structured in
accordance with the star schema. It consists of a fact table and up to 16
dimension tables. The combination of the keys to the dimension tables forms the
key of the fact table. During the charging process, the ratios are added to existing
records if the features are the same, and if not sent new records.
Reporting
The PSA cannot be used in reporting BEx. The PSA tables can only be available
for reporting through InfoSets classics (no specific BI).
The DataStore and the InfoCubos objects can be used in the reporting
immediately. However, the type of reporting is different in each case. In most
cases, the reports very selective are defined for objects DataStore, for example,
the reports in the requested all the invoices for one customer for a specific
month. These reports often are activated using the interface report/report, from
a report defined in a InfoCubo. Due to a new feature SAP NetWeaver 7.0, the
three classes of objects can be notified directly in DataStore BEx. Although it is
possible to direct access, many times their queries should be directed first to
InfoCubos and then to the object level DataStore with RRI (BW305/306).
The reporting multidimensional, mainly at an aggregate level, is carried out
in InfoCubos.
Positioning of DataStore objects in the data flow

In many situations, it is necessary, or at least advantageous, incorporate
additional views to the staging process. BI allows you to integrate one or more
objects DataStore on the flow of data between the PSA and the InfoCubos.
Normally, these objects DataStore store data in a detailed level and can be used
to harmonize and consolidate data before being stored in multidimensional
InfoCubos in aggregated form.
As can be seen in the right side of the chart PSA / Object DataStore / InfoCubo,
the integration of DataStore objects in the data flow is optional. It is also possible
to update data from a to a InfoCubo InfoFuente directly and do not use DataStore
objects at all. On the left side of
14-10-2008
395
TBW10
The picture you can see an example of a scenario in which an object DataStore is
incorporated between a and a InfoCubo InfoFuente. It could also incorporate
multiple objects DataStore on this point, one after the other.
Tip: The number of objects DataStore that you must implement greatly
depends on the complexity of the scenario to implement. In addition, a
DataStore object can also be the end of a process of staging. In other
words, a InfoCubo not necessarily has to be updated from a DataStore
object.
Chart 149: PSA / Object DataStore / InfoCubo: Integrated Data Flow
From the perspective of implementation, you can distinguish between three

classes of objects DataStore on various positions of the data flow based on its
use:
396
14-10-2008
TBW10
Details of the examples are in the section that follows this short list.
1.
The DataStore objects with data from source systems similar (a debuggee
customer order for the type of disclaimer or simply availability for future
needs)
2.
Technically required DataStore Objects

Harmonization of methods delta (some sources of data must pass through
objects to their characteristics DataStore delta)
Harmonization of data types and lengths
Harmonization of data (see the global master data ID)
3.
The DataStore objects related with applications used to carry out specific
requests for reporting or upload (a DataStore combined to
orders/deliveries)
Similar source data

In this case, the data is stored in the same way that has delivered the system data
source source. If you want to keep a complete history of data modifications,
often must include a temporary reference consisting in the key for the object
DataStore.
Technically Required
14-10-2008
397
TBW10
In these objects DataStore, the data is stored in a harmonized way. The

harmonization process encompasses several aspects:
Harmonization of variant data types and lengths

An example could be that in which the customer number has 10 characters
in the source system, but 13 characters in another system. BI needs to
harmonize the length of the customer number. You can do this by
implementing a DataStore object in which the customer has a customer
number of 13 characters. You must perform the necessary changes before
you deploy this object DataStore.
Harmonization of different methods delta of the source system

A DataStore object can convert different methods delta from source
systems (delta additive and After-Image for records musts) in a single delta
with a class. This ensures that the additional attached destinations (in
particular InfoCubos) is to provide them with a suitable delta method. This
harmonization is especially useful when deriving a delta, whenever a
system font only be able to extract uploads complete.
Note: The Delta is a complicated matter. This is explained in more
detail in the course SAP BW350.
Harmonization of data
He often has to harmonize the content of actual data. This may involve
characteristics (materials, for example) and ratios (benefits). An example
would be the derivation of a number of single global material from the
numbers of local subsidiary material. For example, in the first source system,
the material number 100 is a "fighter plane." A second source system said
that the same part number is "toilet paper." As a result, a number of global
material is derived in BI, which provides numbers of overall material only.
The master data management works with BI to support this scenario and
many others.
Enterprise Application Specific

These DataStore objects are typically used to prepare data for certain scenarios of
reporting. A possible example would be the combination of reports and deliveries
in a DataStore object, as well as to derive status or quantities
Of delivery that have yet to be delivered. Due to chronic infracoberturas, you
may want your users only notify before sales that have been delivered.
398
14-10-2008
TBW10
Architecture and features of standard DataStore

objects
The standard DataStore objects consist of three tables:
Active data table

Here is where you stored the current status of the data. This table contains
a key semantics (related to the company) that can be defined by the
responsible for modeling (order number, position, sharing, for example). It
is also very important that the key is correctly
Defined by the responsible for the modeling, since a match in the key starts a
special delta treatment during the activation phase (explained later). The
reporting by BEx also uses this table.
Modify log table

During the execution of activation, the modifications are stored in the log of
changes. At this point you can find the complete history of the changes,
given that the content of the log of modifications are not automatically
deleted. The targets that are connected are updated from the log of changes
if they receive data from the DataStore object in the delta method. The log
of changes is a table PSA and can also be updated in the PSA tree of the
workbench. The log of modifications has technical key that consists of a
request, a data packet and a data record number.
Table of the activation queue

During the DWP, records are written first in this table. This step is necessary
because of the complex logic that then requires the activation process and
which is explained in detail in one of the following sections of this lesson.
14-10-2008
399
TBW10
Chart 150: a scheme for a standard DataStore object
Modeling and creating DataStore objects

The GUI used to build an object DataStore is very similar to that used to build a
InfoCubo. Setting different selection lists to select InfoObjetos in the upper left
area of the GUI. With Drag and drop or with the option of direct input to the
shortcut menu, the InfoObjetos are added to the right areas of the object
DataStore. Finally, decisions can be made on the empowerment of attributes of
navigation and the creation of indexes defined by the user.
Options of the DataStore objects

The most important question when objects are modeled DataStore is: What
InfoObjetos form the key fields in the DataStore object and what InfoObjetos
represent the fields of data? To ask such questions, must forget what you
learned about the modeling InfoCubos, since the design and the use of the two
objects are completely different.
400
14-10-2008
TBW10
Chart 151: design GUI DataStore objects
When modele an object DataStore, should take into account the following:
1.
What InfoObjetos must contain the DataStore object?
2.
What objects defined in a unique way the process? These objects do not
depend on each other and normally form the key for the object DataStore.
Many times tell the students the key is the same as it is in the source tables
on the OLTP system.
3.
All other objects, i.e. those objects that are dependent in some way of the
individual objects in the second step, usually make up the data fields of the
DataStore object.
A DataStore object that should contain information of invoice header level and
position only receives the invoice number for InfoObjeto and position of
invoice as key fields. The rest of objects, such as the client, the material and
the income, should be modeled as data fields. It may be that the dependencies
are not easy to model if, for example, the data should not be updated in the
DataStore object in a level of document or individual item of document. In this
case, it makes sense to deduct these relationships using a model of relationship
of entry (BW330).
14-10-2008
401
TBW10
More decisions are necessary in the two end sections of the GUI:
What navigation attributes ( nav attribute.) must be enabled for this

object DataStore?
For InfoObjetos on which often is notified, indexes can be added using

the final section of the GUI. It is desirable to define secondary indexes
whenever an object DataStore is used for reporting.
Note: This is explained in more detail in BW330 and BW360. Finally,
you should also pay attention to the following techniques:
Do you want to enable the fastest possible speed for the DataStore object
when you use in the reporting BEx? If so, should select the marker generate
SID in the Activation. This flag should be set only when you need to use the
DataStore object in the reporting efficient. This is due to the fact that slow
down the performance when loading data in this object DataStore. The
reporting can still take place with objects in the DataStore that were not
generated SID during activation; simply will be slower. This is also a
prerequisite to the parameterisation of the marker of data records only.
With the bookmark object class DataStore will determine whether

should or not used a standard DataStore object optimized for writing or
direct upgrade.
:could fix the marker data records only if the InfoFuente connected to the
object DataStore only delivers unique records. The result is a performance
improvement. In this context, "unique" means that a combination of keys
that already appears in the DataStore object must not be loaded more than
once, otherwise an error will occur.
The marker set status of quality automatically on OK causes the status of

data quality is set to OK after upload it without technical errors. It is a
prerequisite that must be fulfilled in order to activate and continue updating
data in data destinations connected.
Attention: We recommend that you always select this status
indicator of quality automatic. If the status of quality is not set
automatically in OK, you would need to manually set the status in
the administration of the DataStore object before you can activate
the data. In theory, this is done after a trader review the accuracy of
the data. Although it seems a good idea, it is not likely to happen
except during the validation of data and charging processes that are
part of your project.
402
If the marker enable data automatically is set, data is activated directly

from the queue of activation after having attained the status of
quality OK.
14-10-2008
TBW10
In a similar way, the process of automatically refresh data can be selected

in the Data Destinations connected (cubes or other objects DataStore
successive). If is set, the upgrade starts directly after activating the data with
success. Do this by setting the marker automatically Refresh Data.
Tip: The last two options to automate the load and activation of
successive destinies are normally debatable. These options are
often ignored in most of the cases, because in a
Production environment the chains of process are used to load
objects DataStore. When you use the chains of process, are ignored
these options.
Demo the first exercise to create a DSO at this point.
Load and Activation in DataStore objects

A standard DataStore object has three tables. Before we have described the
three tables and the use of each one of them, but we only explained that uses a
process of transfer of data to load the first. In the next section we will examine
the activation process of DataStore objects, which is the technical term used to
describe the way in which these tables get data.
In addition we will see an example to illustrate what exactly happens when data is
transferred and subsequently are activated in a DataStore object.
Suppose you are loaded two requests Requests1 and requests2 in a DataStore
object. This can occur sequentially or in parallel. The loading process counts both
requests in a queue of activation.
Council: we have not yet commented really the concept of load
applications. At this point, let us think of an application or in a more
specific way, in a request ID as an identifier for a load of records. If you
load new records each night during a year we 365 Request ID in our
destination, in this case a DataStore object. In addition, while we learn
new terms, a package is a subset of records (perhaps 20,000) in a request.
BI creates packages to better manage the system memory.
14-10-2008
403
TBW10
Chart 152: Loading Data in the queue of activation of a standard DataStore

object
The implementation of activation (activate the data in the activation queue so

that it can be used) can be activated automatically, including as part of a chain
of process, or manually initiated. The data is classified at
Principle of the implementation of activation. This takes place in the first place,
according to the key semantics of the Datastore object (i.e., the table with the
active data). Then the data is sorted according to the technical key of the queue of
activation. This is the same as the sequence of upload with the different data
records. The collating sequence ensures that the activation can be run in parallel.
This is because all data records that belong to the same key semantics are not
distributed among multiple processes.
The number of data records to activate determines how many activation processes
are initiated. You can set if the processes must be run in parallel or in series.
Note: The parallel treatment is explained in detail in BW360
(performance setting).
The user can choose if the modifications that are called from the different load
requests must be combined together in a request for a log of changes or if a
request for a log of changes must be generated for each request charged in a
manner similar to a load request
That identifies when you have loaded the records, a request for a log of
changes identifies when enabled the records and moved to the log of modifications
from the queue of activation. This should happen in the most
404
14-10-2008
TBW10
Of the cases, on a daily basis as a minimum. This option appears in the GUI of
activation (Shortcut menu in a DataStore object) under the denomination does
not condense applications in a request when it occurs the activation.
.
Note: The generation of a request for a log of changes to each request for
uploading data influences the erase options of the requests. If the
checkbox is checked and there is exactly a load request for an application
for a log of changes, will be possible to erase
Individual loading requests of the DataStore object and in the successive
destinies. This is because there is always a one-to-one relationship
between a load request and a request for the log of changes. Therefore, if
you want to have the ability to monitor the loads of the DataStore object
until its InfoCubo should check this box. The counterpart is that they use
more system resources.
Example of object activation DataStore

The following image shows that were previously activated the load requests1
with order number 4711 and a value of 10. The data record with quantity 10
was sent to an active table and the log of changes (with a request for a log of
specific modifications). After you activate a request, clears
Automatically from the queue of activation, as indicated by the red line of
strikethrough. The next step that it shows is that the same order (4711) was
loaded in the queue of activation with another load request (perhaps the next day).
We know that the order was changed to 30 because the key (4711) coincides with
a record that is currently in the queue of activation.
Tip: The type of update Overwrite is used for this ratio of "value".
14-10-2008
405
TBW10
Chart 153: Example of activation: First load enabled
In the following image, you enable this new request. The new data record
overwrites then to that existing in the active table of the DataStore object. This
creates an updated value of 30 for ordering the active table. It also introduces a
new record in the log of changes, as it has a key new technique.
During activation of ratios in overtype mode, the activation process creates a
record with signs invested and places it in the log of changes. In this case, it is a
record for a value 4711 -10. As a result, at the end of the execution of the
activation, appear three data records two requests in the log of changes. In our
example, both records
Loaded belong to the same key semantics: NO. doc.. For this reason, the table with
the data assets has only one entry. Once more, after the activation satisfactory, the
activation queue is empty. The application numbers generated by the activation on
the log of changes are not the same as those of the queue of activation, since
documented two systems of different events.
406
14-10-2008
TBW10
Chart 154: Example of activation: Offset data created by the activation

process
Note: If the DataStore object was not in the data flow in this example,
and the source data flowed directly to a InfoCubo,
InfoCubo would add the 10 to 30 and would get an incorrect value of 40.
If instead we had the data in the log of modifications to the InfoCubo, 10,
-10 and 30 are added to the correct value of 30. In this example, it
required a DataStore object in the data flow before the InfoCubo. It is not
always necessary, but many times it is desirable.
14-10-2008
407
TBW10
Creation and fill a
DataStore object
367
1.
Create a standard DataStore object using the shortcut menu in a

Inforea InfoSitio tag of the workbench.
2.
Create a data transfer process to pass data to your DataStore object.
3.
Create a string of process by completing the following steps:

1.
Load a InfoPaquete to PSA
2.
Run a DWP to pass data to your DataStore object
3.
Select the data in the DataStore object
4.
Optionally, schedule a DWP thereafter to load from the log of changes

to your DataStore object to the InfoCubos connected
Demo: Creating a DataStore object and filling it

Objective
Defining and Loading DataStore Objects
System Data
System:
Assigned system
Principal:
800
User ID:
Assigned user ID
Key of access:
Assigned password
Parameterizations of the system: No other settings are necessary.
Use the objects and steps in the exercise.
1.
Create a new DataStore Object. (First part of exercise 1), unless you already
demoed this as noted in the instructor note above.
2.
Load data into your DataStore Object and activate it (second part of
exercise 1).
Integration of a new destination of data in an existing

data flow
The following advanced topic is an annex to the business case of the
beginning of this lesson. Has accomplished its goal of replicate and store old
data in an object DataStore BI. You must now decide if you pass these
detailed data to a InfoCubo added.
408
14-10-2008
TBW10
This is a real world example that occurs in many situations. It often happens that
several destinations of data already supplied with data from an object DataStore
and the destinations of additional data must be connected to it.
In the complex example shown in the picture the scene to integrate a new data
destination, the DataStore object source already provides two connected data
destinations: a DataStore and a InfoCubo object. Already there has been a delta
update for the two destinations of data. As a result, data destinations already
contain data. Now it is necessary to connect a new destination of data to the
DataStore object source. In this case, is an additional InfoCubo.
Council: The following applies regardless of whether connects an object
or a InfoCubo additional datastore.
Our scenario is more complex than many others in the destinations of data
previously connected have taken deltas to the DataStore object source. As a result,
data destinations have a set of consistent data. The whole set of data, content in
the DataStore object source (and also in the two destinations of pre-existing data),
you must transfer now to the destination data just connected. Then you must
supply three destinations with any newly created delta.
Chart 155: Integrate a new destination
14-10-2008
409
TBW10
There are several ways to transfer a set of existing data to a newly connected
destination:
1.
Rebuild the new destination of data

**** Only for destinations filled with data flow objects, 3.x old (updating
rules)***
2.
Use the data transfer process based on delta
3.
Use the data transfer process of upload complete and PTD delta
The options can be distinguished from each other according to the way in which
they are designed in the workbench. Given that the characteristic of reconstruction
is only available with the objects of flow of old data, we will not explain this
option in class.
Reconstruct the old feature of 3.5 is not designed to work with the BI 7.0
dataflow. Slides referring to the reconstruct tab have been removed!
Data Destinations fill connected with a

Data transfer process (delta or full)
Another option would be to create and run a new process of transfer of data based
on a transformation that is created between the original source and its new target
object. You can design and execute this method completely in the context menu of
the destination, or to use chains of process for implementation.
The options available in this method are the delta load or the load complete.
The selection you make depends on how to create the DWP. In the delta option,
data is read from the log of changes, just as in the option of reconstruction.
A special feature of the use of PTD with the complete option is that the data can
be read from the active table of the DataStore object source. Here, the system
reads the current status of the data. The modifications made in the past (from the
log of changes) are not transferred to the new destinations. For this reason, you
can also use this option when the applications are deleted regularly from the log
of changes. The entire stage in this case could involve the implementation of a
single time throughout the DWP, followed by daily executions the DWP delta.
Moreover, in the real world, this PTD delta would be integrated into the chain of
existing process or in a new lower chain connected to the already existing for its
automatic execution.
Note: Using the option on the shortcut menu additional functions in the
DataStore object source, the techniques 3.x prior to upload destinations
Successive are also available.
410
14-10-2008

Sap TBW10 4

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Sap TBW10 4

Transféré par

Droits d'auteur :

Formats disponibles

TBW10

Lesson: Loading flat files

Exercise 10: Attribute data

Objectives of the Exercises

Load master data using the flat file interface

Use transforms to attributes and texts

Create formulas using the formula editor

This may be the N:\ drive in to terminal server (Citrix) environment.

In the SAP menu Easy Access, select User Menu

Continued on next page

2008 SAP AG. All rights reserved.

Chapter 4: acquisition of data from other systems

On the left, on the shortcut menu of master data of cost center 1,

Task 2 - Set global transfer routines

Access your InfoObjeto COSTC## and Select the modify mode. In

Modify the routine of global transfer.

Continued on next page

2008 SAP AG. All rights reserved.

Lesson: Loading flat files

Task 3 - Creation of a source of file data plane for

Create a data source for the interface of flat file.

Data source data class

Master Data Attributes

Insert all the necessary information on the labels removal, Proposal,

2008 SAP AG. All rights reserved.

Chapter 4: acquisition of data from other systems

Your data source.

Task 4: Creating transforms

Update the transformations to make an upload of data attributes from your

2008 SAP AG. All rights reserved.

Lesson: Loading flat files

Data Source Field

Manually update the transformations for the InfoObjetos 0DATETO,

Create a date formula to assign the

Data reading teachers: InfoObjeto

Activate your changes and return to the previous screen.

Create transforms to do a upload of the text information in the flat file to

Continued on next page

2008 SAP AG. All rights reserved.

Chapter 4: acquisition of data from other systems

Data Source Field

Update the transformations for the InfoObjetos 0DATETO, 0DATEFROM,

Create a date formula to assign the current

Create a formula of language to assign the system

Activate your changes and return to the previous screen.

Continued on next page

2008 SAP AG. All rights reserved.

Lesson: Loading flat files

Task 5 - Creation of a InfoPaquete and loading data to

Create a InfoPaquete for your data source costc##_MD_flatfile. In the

Start the InfoPaquete and verify the treatment in the monitor.

Task 6: Creation of processes for

Data Transfer Process

GR## attribute data of

Object class (destination the DWP) InfoObjeto

Continued on next page

2008 SAP AG. All rights reserved.

Chapter 4: acquisition of data from other systems

Name (destination of the DWP

Object class (source the DWP)

Data source (source the DWP)

Source system (source of PTD)

Data Transfer Process