Creating a Range in BI 7.0

Question

Friends -
We have an infoObject called Zcustomer.  Zcustomer has a navigational attribute called ZEMP (this is the number of employees at the companies - numc type).   I want to create another navigational attribute called ZEMP2 where it calculates a value based on a RANGE.
For example,
Company XYZ has 50 employees
Company ABC has 100 employees
My logic for  populating ZEMP2 should be:
If ZEMP between 0 and 50  ZEMP2 = A
Else
If ZEMP Between 51 and 100 then ZEMP2 = B
Else ZEMP2 = C
What is the best practice for populating ZEMP2 when we load Zcustomer in a transformation.  Is it best to create ABAP in the transformation start routine, or do we create the logic in a Formula, or could this be done in a Hierarchy? or what?
Any suggestions would be helpful
Patrick

Answer 1

Since you're on BI 7.0, you can either do this in a Characteristic Routine or in the End Routine.
If your preference is to do this in a Characteristic Routine, you would map ZEMP to ZEMP2 and then create an ABAP routine as such:
IF source_fields-zemp BETWEEN 0 AND 50.
  RESULT = 'A'.
ELSEIF source_fields-zemp BETWEEN 51 AND 100.
  RESULT = 'B'.
ELSE.
  RESULT = 'C'.
ENDIF.
Now, if your preference is to do this in the End Routine, the code would look like this:
LOOP AT result_package
  ASSIGNING <result_fields>.
  IF <result_fields>-zemp BETWEEN 0 AND 50.
    <result_fields>-zemp2 = 'A'.
  ELSEIF <result_fields>-zemp BETWEEN 51 AND 100.
    <result_fields>-zemp2 = 'B'.
  ELSE.
    <result_fields>-zemp2 = 'C'.
  ENDIF.
ENDLOOP.
Whichever you choose, is dependent on other processing needs for this Transformation. If this is the only post-Start Routine transformation to be done, then the Characteristic Routine route would be the most efficient, because it has to go through this process no matter if there is a routine or not, whereas the End Routine would have to loop back through the entire internal table (Data Package) in order to update. However, if you already have an End Routine doing other post-process transformational logic, then the End Routine would be the most efficient place to put this code.