Key Concept |
In SAP NetWeaver 2004s, SAP has introduced a new way to transform data that replaces the widely used transfer and update rules in the previous BW releases. New in SAP NetWeaver 2004s is an item called transformations. Transformations serve the same purpose as BW’s transfer and update rules — consolidating, cleansing, and integrating data. However, the major benefits of transformations include a new graphical user interface, the introduction of end routines and expert routines, and an easy-to-implement unit of measure (UOM) conversion. Users who have implemented significant custom transformation logic have to migrate to ABAP Objects as part of their upgrade to SAP NetWeaver 2004s functionality. |
Most SAP NetWeaver BI customers use routines to transform data such as unit of measure (UOM) conversions and lookups against master data tables in update and transfer rules. In the BI capabilities of SAP NetWeaver 2004s, SAP has introduced transformations, a new method for applying business and technical logic to data. Transformations replace transfer and update rules. Once you decide to migrate, you need to understand how to perform this migration. I will provide guidance and examples to enable the migration to the new transformation process.
You may choose to execute a technical upgrade and preserve the objects built with BW 3.x. Transaction RSA1OLD allows you to continue working with 3.x objects. Thus, you have the option to migrate to newer objects when your project timeline and budget permit. In other words, upgrading to SAP NetWeaver 2004s does not mandate you to use the concepts introduced in the new release and your investment in this area of SAP BW thus far does not go to waste. However, migrating your objects to the new transformation process has some distinct advantages.
No comments:
Post a Comment