尤尼佳11_20B_UPGRADE_GUIDE_0700.docVIP

BW 2.0B Functional Upgrade Guide SAP Business Information Warehouse This paper is intended as a guideline for the functional consultant leading a BW 2.0b upgrade project. It points out common practises, pitfalls and tipstricks during the technical upgrade from BW1.2b or BW2.0a to BW2.0b. Where applicable, related Sapnet (OSS) notes are indicated in brackets [#…]. Version of 07/24/00 Data Staging and Storage: In order to make loaded data available for reporting, the quality check flag needs to be set. This flag was set by default (non-changeable) in BW12b, in BW20b it is not set by default. [#314268] Even after activating the automatism “technical ok implies quality ok” [#314268], data are not available for reporting. If no new data is loaded into the cube, for each infocube upgraded, it is required to enter (just once) into the “manage infocube” maintenance, and press the “refresh” button for requests. BW Statistics infocube contains incompatible changes. [# 309955] Current kernel patch level (690 or above) for R/3 source OLTP system is required in case of an R/3 OLTP Release 4.5a. [#311409] In case of master data infosources, with BW2.0b now one separate infopackage is required for attributes, for texts and for hierarchies. (In case of BW1.2b, one infopackage could cover all loads for an infoobject.) Hence, some infopackages need to be created manually after the upgrade. There is a parameter available defining the details for PSA (former 1.2b “ODS”) partitioning. This parameter can be set via Customizing (transaction SPRO) BW Customizing IMG Business Information Warehouse Links to Other Systems Maintain Control Parameters for the Data Transfer Partition Size. Execute ABAP report SAP_CREATE_E_FACTTABLES in order to create missing “E” type fact-tables for infocubes created prior to the upgrade. [#316790] The BW12b/BW20a “ODS” was renamed with BW2.0b into “PSA” (Persistant Staging Area). ODS tables created prior to the upgrade (as well as the