Hi, its about rutines in BW

Question

Hi friends,  this is the scenario: i m filling an ODS but some InfoObjects i m getting them througt rutines by its tables, i wanna get CERTIF_YR  and i have 0UCCONTRACT in my ODS  my question is: when i try to connect fields trhought rutines they must be key fields in its tables? this is my code to try to explain better my situation
TABLES:   /bi0/puc_device, /bi0/puccontract, /bi0/muc_devinst.                                                                               
DATA:
          lv_ucinstalla LIKE  /bi0/puccontract-ucinstalla,
          lv_uclogicnr LIKE   /bi0/muc_devinst-uclogicnr,
          lv_certif_yr LIKE   /bi0/puc_device-certif_yr.
  SELECT SINGLE ucinstalla INTO lv_ucinstalla
         FROM /bi0/puccontract
         WHERE
         uccontract = COMM_STRUCTURE-uccontract  AND
         objvers = 'A'.
  SELECT SINGLE uclogicnr INTO lv_uclogicnr
          FROM /bi0/muc_devinst
          WHERE
          uc_devinst = lv_ucinstalla    AND
         objvers  = 'A'.
                                                                                SELECT SINGLE  certif_yr INTO lv_certif_yr
          FROM /bi0/puc_device
          WHERE
          uclogicnr = lv_uclogicnr  AND objvers= 'A'.  //// here its the problem , said E:Field "UCLOGICNR" unknown / but UCLOGICNR exist in /bi0/puc_device but is not a key field in the table.
result value of the routine
  RETURNCODE=0.
  RESULT = lv_certif_yr.

Answer 1

Hi,
they don'T have to be key fileds, but for performance aspects you should read the values with their keys. OTherwise please add an index or store the information in an internal table and use read table instead. Specially if your ODS is big with many thousands or millions of records this can be a performance issue.
Your field UCLOGICNR may be /bic/uclogicnr instead if its a customer infoobject in your code or you missed an underscore: UC_LOGICNR instead.
Regards,
juergen