Mapping DataSources back to R/3 is a big problem for everyone working with BW. Unfortunately, there is no general rule to find the fields. Learn how the fields are mapped for certain extractors.
Dear BW Expert,
I am trying to determine how SAP BW maps the fields defined in InfoSources and DataSources back to R/3 fields and, more importantly, to R/3 tables. When you view DataSources via RSA5 or extract structures via SE80, you only see names of fields and structures. Nothing tells you which SAP tables are used. I am very interested in understanding this functionality because I think it is critical to be able to map tables as well as fields. Some fields exist in multiple tables, and in many cases you must be able to determine which tables are specifically used and mapped in order to effectively design, develop, and test BW solutions.
Garrett Platek, Bayer Corp.
This is a big problem for everyone working with BW. Unfortunately, there is no general rule to find the fields. I am able to tell how the fields are mapped for certain extractors.
Logistics: To find the corresponding R/3 fields, go to the Logistics extractor cockpit and then to the specific extractor for which you want to know the fields. In the extractor mapping, you can see the structure name for BW, which is built from the table name, field name, and prefix for BW (MC): MCTABLE-FIELD. For example, Figure 1 shows that the first structure field is MCLIKP ABLAD, which means that this structure is generating this field from table LIKP and the field in the table is ABLAD.
Figure 1
The BW extract structures for the Logistics module
CO-PA: When you configure CO-PA in R/3, the system generates four tables (XXXX stands for the name of the operating concern that you use): CE1XXXX, CE2XXXX, CE3XXXX, and CE4XXXX. The extractor in R/3 for CO-PA is taking most of the fields from tables CE1 and CE2, usually on a one-to-one basis. Exceptions are: field PLIKZ (plan/actual indicator in CEYXXXX) is mapped to field WRTTP in the extract structure. The field PALEDGER (currency type) is split into two fields CURTYPE and VALUTYP. PLIKZ is mapped to InfoObject 0VTYPE in BW, and the values in R/3 (1and 2) are changed to 010 and 020.
Generic extractors: These are easy as they are defined by the person who configures BW. Just look in the DataSource definition and for the field View/table. In Figure 2, the example is ZBWFI_KNB4. You will see either the table or the name of a view. If it is a view, go to transaction code SE11 and look for the definition of the view. This will give you the table names that are behind it.
Figure 2
Finding a table name for a generic extractor
Frank Bulacher
Frank Bulacher is manager of SAP CH at Alstom Switzerland. He has worked in BI for more than 14 years in the United States and Europe. Prior to that, he was a consultant in data warehousing and SAP FI/CO. His career has taken him to top-tier and boutique companies. Frank is a graduate of the University of Augsburg in Germany and the University of Wales in Swansea, UK, with majors in banking and computer science.
You may contact the author at f.bulacher@gmail.com.
If you have comments about this article or publication, or would like to submit an article idea, please contact the editor.
Premium