Академический Документы
Профессиональный Документы
Культура Документы
12 June 2015
Transfer of Archived SAP ERP Data to SAP NetWeaver BW 2
Table of Contents
1 Introduction ......................................................................... 4
1 Introduction
Data Warehouse systems enable efficient access to data from heterogeneous
information sources, suitable storage and end user-specific representation of
information that has been gathered in this way.
Data from almost any source can be used for data procurement and provision in
the SAP BW system. Main sources are SAP systems that are implemented in the
company. The data procurement layer (also called the ETL process layer) is used
to extract, transfer and load this data into the BW system.
A growing number of customers need to extract archived data from an ERP source
system and load it into a BW system. This documentation describes two methods
to fulfill this task.
In the first method extractors from BI Content are used. Chapter 2 lists all
DataSources from SAP BI Content which are able to select archived data, together
with DataSources from PBS.
The second method, described in chapter 3, is based on data transfer through flat
files. It is a generic method which allows the user to transfer any structured data to
SAP NetWeaver BW.
Transfer of Archived SAP ERP Data to SAP NetWeaver BW 5
The SAP BI Content provides a set of standardized DataSources which are widely
used by customers. However, only a small percentage supports the extraction of
archived data. In order to allow our customers the extraction of indexed data from
archive, many PBS archive add ons now contain a selected number of archive-
enabled DataSources and load reports.
Table 1 and Table 2 list all DataSources for transactional data from SAP BI
Content which are able to select archived data. In addition, all DataSources that
are provided by a specific PBS archive add on are added to the list. Table 3 and
Table 4 list all supported DataSources for master data (attrobutes and texts) from
SAP BI Content.
In general, DataSources use two different methods to select archived data: either
direct access to archive in the DataSource itself, or indirect access through
selecting archived data via initial load. The second method is especially used in all
DataSources from Logistics by using communication structures from the Logistics
Information System (LIS, see Table 2).
Now, the second method will be described more in detail. In order to extract data
from Logistics, all DataSources from BI Content use an indirect access method.
First the data is stored in LIS tables as a buffer. Then the extractor reads from
these LIS tables. To build initial data loads for SAP NetWeaver BW, first you need
to populate the corresponding LIS tables with the related transaction. Hence, for
archive access these transactions must be able to select archived data.
Table 5 lists all DataSources from Logistics with their corresponding transactions
for an initial load. In addition, the transactions and related programs are listed in
Table 6. In case of PBS versions, the supported SAP release is added to the
program name together with a release date.
More module-specific details about using PBS extractors and load programs can
be found in chapter 5.
Transfer of Archived SAP ERP Data to SAP NetWeaver BW 6
Table 1: DataSources with archive selection from SAP BI Content and PBS
archive add ons (Part 1: Transactional Data without Logistics)
Transfer of Archived SAP ERP Data to SAP NetWeaver BW 7
Table 2: DataSources with archive selection from SAP BI Content and PBS
archive add ons (Part 2: Transactional Data -> Logistics)
Table 3: DataSources with archive selection from SAP BI Content and PBS
archive add ons (Part 3: Master Data -> Attributes)
Transfer of Archived SAP ERP Data to SAP NetWeaver BW 8
Table 4: DataSources with archive selection from SAP BI Content and PBS
archive add ons (Part 4: Master Data -> Texts)
*) This function is only used for making corrections to initial stocks and should only
be used in exceptional cases. For further details, see SAP Notes 79083 and
111691.
Transfer of Archived SAP ERP Data to SAP NetWeaver BW 10
3.1 Extract Archived Data from SAP ERP and SAP R/3
Call CMM extract report /PBS/CMM_LIS_ITEM_EKKO (via SE38). From ECC 5.0
or higher, you can also call transaction /PBS/CMME_EXPORT. In order to extract
only archived data, use ‘3’ for the data source (Archive only). Use ‘Item list’ as list
layout, and use ‘Export to file’ as output option. Specify file name and destination
for the extract file.
Use Settings Layout Change to change the layout, i.e. the containing fields
and the desired order. Save the layout structure as a new display variant, which
you can choose in the selection screen of the extract report.
Transfer of Archived SAP ERP Data to SAP NetWeaver BW 13
After extraction you will get an extract file in the following format. The first 8 lines
describe the field structure (technical name, long/short description, type, length and
decimal places). After this the extracted data is listed whereas each row is
separated by tabs. Each line is terminated by CR LF.
In the next step the data has to be transferred from the source system to the BW
system or at least to the client workstation (front end).
The FTP transfer should be done in two steps. First, use binary mode from source
to front end. Then use text mode from front end to destination to ensure that all
lines are correctly terminated (CR LF in Windows servers, LF in UNIX servers).
Transfer of Archived SAP ERP Data to SAP NetWeaver BW 15
Importing data from flat files requires the definition of a flat file source system in
SAP NetWeaver BW.
Make sure you have defined such a source system. If not, please proceed as
follows. From the Data Warehousing Workbench, click the Source Systems
tabstrip. Select the appearing Source Systems node, right-click, and choose
Create. From the generated list, select File System as shown in Diagram 5.
Now a DataSource has to be created. In BW release 7.x two types of DataSources
are available: NetWeaver 7 DataSources and 3.x DataSources. In the following
chapter we will refer to the new type of DataSources.
From the source systems tabstrip in the DW Workbench, double-click on the
generated source system. Select or create an application component, right-click,
and select Create DataSource. From the appearing window, choose the data type
of the DataSource: transaction data, master data text or master data attributes. In
this example we are using the transaction data type. After that, you have to set the
options as shown in Diagram 6. The most important options are as follows:
Data Format: Separated with separator (for example, CSV)
Data separator: 009 Hex
Number of header rows: 08
After setting the options the DataSource must be activated.
It is recommended to check the parameters with the ‘Preview’ function in the
DataSource definition. Possible problems concerning the data layout (e.g.
incompatible format) can be detected that way in an early stage.
Transfer of Archived SAP ERP Data to SAP NetWeaver BW 16
In the next step you have to connect the DataSource to a destination by defining a
transformation. In SAP NetWeaver BW the following BW object types can be used
as destination: InfoSources, InfoCubes and DataStore Objects.
In this example we are using an InfoSource as a destination. If there is no
adequate InfoSource it has to be created. From the Data Warehousing Workbench,
click the InfoSources tabstrip. Select an InfoArea, right-click, and choose ‘Create
InfoSource’. In the appearing window an InfoSource structure with appropriate
InfoObjects has to be constructed, corresponding to the flat file field definitions (see
Diagram 7). If necessary, the related InfoObjects must be created as well.
After defining DataSource and InfoSource the transfer rules have to be set. These
rules assign the InfoObjects of the InfoSource to the corresponding fields in the
DataSource. In SAP NetWeaver BW a so-called transformation is used for that
purpose.
Transfer of Archived SAP ERP Data to SAP NetWeaver BW 17
When saving your DataSource, you will be asked to specify which fields are used
for selection or should be hidden (see diagram below).
In order to complete the DataSource definition, you have to press the Save button
again.
5 Module-specific Features
5.1 PBS archive add on CFI
The support of selected DataSources for archive access is available for SAP
Release 4.6C and above. For SAP Release 4.6C the extractors and programs are
delivered in a separate transport.
Each DataSource can be activated individually for PBS archive access. To do this,
you merely select the corresponding checkbox and start the program. For
productive use, deactivate the button Test Run. It is possible to reset to the SAP
standard settings at any time.
The PBS BW extractors for DataSources 0FI_AR_4, 0FI_AP_4, 0FI_GL_4 and
0FI_TX_4 only support the update modes F (full) and C (initialization).
Recommendation:
1. Activation of PBS BW extractors
2. Execution of extraction in the modes F or C
3. Resetting of BW extractors to the SAP standard
4. Execution of delta extraction before the SAP data archiving
The BW DataSources extracts which you have changed to PBS extractors need to
be replicated again in the BW system.
Transfer of Archived SAP ERP Data to SAP NetWeaver BW 26
Support for the adjustment can be provided by the PBS Conversion Tool (see the
separate manual in the software delivery or in the PBS menu under
'Documentation Guide') or for specific adjustments, the PBS Archive Access
Tutorial via transaction /PBS/UTIL_ACCESS_ARC.
Transfer of Archived SAP ERP Data to SAP NetWeaver BW 28
The support of selected DataSources for archive access is available in the PBS
archive add on CCO from SAP Release 4.6C.
The support of selected DataSources for archive access is available in the PBS
archive add on CCOPA from SAP Release 4.6C.
The support of selected DataSources for archive access is available in the PBS
archive add on CPS from SAP ERP 6.0.
The corresponding SAP extractors must be activated in the ERP system. Otherwise an
error message will appear.
Data sources for line items are not supported with the PBS archive add on CPS.
The support is based on the following assumption: connecting the PBS archive add on
CPS to the DataSources is only required for the initial load of ERP data into the BW
system. After completing the initial load process from database and archive, all
subsequent delta extractions are accessing the database only.
The transaction shows a list of all available BW extractors with PBS archive access. Each
Data Source can separately be activated for PBS archive access. It is also possible to
activate all listed extractors at once. To do this, please mark the selected lines in the list
Transfer of Archived SAP ERP Data to SAP NetWeaver BW 31
of available extractors, and then push button . Now the new DataSource extractor is
shown in the list. In productive environment the change must be saved in addition by
using . Returning to SAP standard is possible at any time.