Overcome Challenges with Unit of Measure Conversion During Transformations

Unit of measure (UoM) conversion functionality can add significant flexibility and enhanced analysis capabilities. Instead of having to create custom ABAP programs, you can use the new standard functionality in SAP NetWeaver BW 7.0. Here are the steps to implement UoM conversions in transformations

Key Concept

Unit of measure (UoM) conversion refers to the act of converting quantity key figure values into other units of measure for analysis purposes. For example, orders might be taken and stored in UoMs, such as each, case, and pallet. If you try to add the values without regard for UoM, the total is meaningless. To provide a meaningful sales total, you must convert the values from the multiple source UoMs to one common UoM for analysis. The UoM conversion functionality within SAP NetWeaver BW provides this capability.

Unit of measure (UoM) conversion has always cause challenges in BI reporting. Unlike currency conversion, which applies a common multiplier to various key figure values, UoM conversion typically requires much more complex logic because each material can differ in its conversion multiplier. For example, when converting from each to case, material A has 10 eaches in a case and material B has 24 eaches in a case. The system must apply the multiplier for materials A and B based on both the individual UoM and material conversion rate for the associated material.
In SAP BW 3.x, the typical method of UoM conversion involved writing custom ABAP user exits and formula variables to provide this functionality because there was no standard functionality in SAP BW to allow automated UoM conversion. SAP now provides this functionality standard in the SAP NetWeaver BW 7.x.
You can use UoM conversion mainly in two areas: during a transformation (i.e., moving data from one structure in SAP NetWeaver BW to another in the back end) and during query processing

Comments

Anonymous said…

asf er werf 4r bgert ygdg b45 ge55t ftyerfx ndgd tyhtr

October 3, 2013 at 7:06 AM

Step by Step guide on BADI with Filter implementation

Step 1 à Before implementing filter objects to a BADI. We need to deactivate all the implementation for that BADI. Go to SE18 (BADI definition) and from there navigate to all BADI implementation to view all the active implementations for that BADI Select the BADI implementations listed on the screen and deactivate the implementation. Once done, return back to the initial screen of SE18 and proceed with next step. Step 2 à go to SE18 – BADI Definition screen and change the existing BADI definition that we created in the earlier tutorial. Select the FILTER –DEPENDENT check box under the TYPE section. This will open up the FILTER TYPE field for inputs. And do an F1 on the FILTER TYPE field. Click on the F4 on the FILTER TYPE field name and enter some search criteria to find a relevant data element. And click on the continue button Select the data element from the list to set up your filter and hit enter. Click on the save butto...

Create Data Source in SAP

Data Sources are extraction structure. Data Sources are used to extract data from various source system. In the below steps, we will see how to create a data source using a SAP table VBAK. 1) Execute transaction RSO2 2) Enter data source name to be created 3) Press Create 4) Enter description of the data source 5) Enter the name of table or view on which data source has to be created. Data Source can also be created using a View, Info set or a Function Module. 6) Save the data source 7) Execute RSO2 again and click Change 8) Select VBELN field as selection 9) Save the Data Source 11) To check whether data is getting extracted, execute transaction RSA3 12) Enter the name of data source as shown below and press 'Extraction' 13) An information message will appear stating no. of records fetched 14) Additional button 'Display list' will appear, press button 15) Select one of the data packet and double click to get records fetched 16) Data Source is ready to be used!

Operational Data Store (ODS) using SAP BW 3.5

Operational Data Store (ODS) using SAP BW 3.5 ODS consists of 'Key fields' and 'Data fields'. Data fields can also contain characteristics e.g. customer, product etc.. ODS is not used for multi-dimensional analysis like Infocube . The data from ODS can be updated with delta update into a Infocube. The data in ODS is stored in a transparent table. There is no fact or dimensional table created for ODS. Following are the steps to create an ODS: 1) Execute transaction RSA1, select the InfoArea under which you would like to create ODS. Right click the InfoArea, select 'Create ODS Object' 2) Enter ODS Object 'Name' and 'Description', press 'Create' 3) Check the box against 'BEx Reporting' to enable ODS for BEx reporting, press 'InfoObject Catalog' button to get the InfoObjects which you would like to add to ODS 4) Select the characteristics (InfoObjects) which you would like to add as 'Key fields' or 'Data fields...

SAP BI

Search This Blog