SAP BW staging engine needs to know full metadata and data content definitions (structures) from its SAP R/3 data source (extraction engine layer). This is achieved by importing metadata from the source SAP R/3.
The SAP BW specific content and environment setup process in SAP R/3 is very similar to the SAP R/3 OLTP release upgrade. To verify that the SAP R/3 OLTP instance is properly upgraded with the SAP BW add-on, list table AVERS using transaction SE16. It must list BW-BCT, as shown .
SAP provides several transports to load business content in SAP R/3. The actual number of transports varies based on your SAP R/3 version (3.0D through 4.6B) and the SAP BW version . These upgrade programs load objects in SAP R/3 for SAP BW data extractors in terms of database tables, InfoObject definitions, Extract structures, Extract programs, and other programs needed to build and set up data extraction schemes for SAP BW.
Metadata Management in SAP OLTP
After installing business content in SAP R/3, we need to create a logical system name using transaction SM59 for SAP R/3 instance as a data source. We will use this instance logical name to connect SAP BW to SAP R/3. Transaction SM59 requires special user privileges. In the SAP R/3 OLTP environment, the basis administrator usually has privileges to create logical system names.In the SAP BW development environment, a few SAP BW developers may require Basis-level privileges to define logical system names for data sources.Metadata is stored in several tables, both in SAP BW and SAP R/3.
Table RODIOBJ contains metadata for all InfoObjects in the source system defining its associated key figures, characteristics, time, and unit of measure in tables RODKYF, RODCHA, RODTIM, and RODUNI, respectively. Table RODIOBJCMP contains only the compounded InfoObjects associated with an InfoObject for the source system.
After defining a source system and testing RFC level connections to the source system, you are ready to load metadata for InfoSources and other SAP BW specific objects defined in SAP R/3. Click the Source systems tabstrip. Expand the Source systems tree, and then right-click the Source System you want to load metadata from.
After updating metadata in SAP BW, go to the InfoSources and InfoObjects tabstrips. Expand the respective object trees. Many new entries are now listed as a result of the metadata update. You need this metadata before activating predefined SAP business content such as InfoSources, transfer rules, communication structures, update rules, InfoCubes, queries, key performance indicators, and channels.
For non-SAP R/3 data sources, first you define a data source in SAP BW for a flat file. Then depending on the content of the flat file, you may create a new InfoSource for master or transaction data.
If the flat file contains master data, it must have only one type of master data InfoObject. In other words, from one file you cannot load master data for customers and material.
Related Posts
Data ware house building statagies
Construction of data ware house
How to get better performace with data ware house?
ABAP TOPIC WISE COMPLETE COURSE
BDC OOPS ABAP ALE IDOC'S BADI BAPI Syntax Check
Interview Questions ALV Reports with sample code ABAP complete course
ABAP Dictionary SAP Scripts Script Controls Smart Forms
Work Flow Work Flow MM Work Flow SD Communication Interface
No comments:
Post a Comment