The following steps constitute a high-level procedure for transporting BW objects from a development system to other systems:
|System landscape||The system landscape specifies the role of each system and the paths for transporting objects among those systems.|
|Development class||A development class is a group of objects that are logically related.|
For Further Information
• OSS Note 0325470, "Activities After Client Copy in BW Source Systems."
• OSS Note 0323323, "Transport of All Activated Objects of a System."
• OSS Note 0356018, "Standard Transport System Activation in BW."
• OSS Note 0184322, "Procedure after DB Copy of BW Source Systems."
• OSS Note 0301192, "Procedure After Upgrading an R/3 Source System."
• OSS Note 0325525, "Copying and Renaming Systems in a BW Environment."
So far we have covered most BW topics, but not all. Appendix A introduces ASAP for BW, a BW implementation methodology developed by SAP. Appendix B gives an overview of the SAP Basis 3-tier architecture.
Part I. Guided Tours
Business Scenario and SAP BW
Creating an InfoCube
Loading Data into the InfoCube
Checking Data Quality
Creating Queries and Workbooks
Managing User Authorization
Part II. Advanced Topics
Aggregates and Multi-Cubes
Operational Data Store (ODS)
Generic R/3 Data Extraction
Appendix A. BW Implementation Methodology
Appendix B. SAP Basis Overview
Appendix C. Glossary
Appendix D. Bibliography