Return tables in Update routines

Hi,
Can anyone send me some documents on the use of return tables in Update Routines?
email id: [email protected]
Thanks in advance,
RP

Hi Ram,
Table as a return
In general, routines in the update rules have only one return code.
If you select this field, the corresponding key figure routine no longer
 has a return code (defined in RESULT), rather a return table (defined in
 RESULT_TABLE). In this case you can create as many key figure values
 from the data record as you wish. You can find the calculated
 characteristic values in the structure ICUBE_VALUES.
Activities
If you change these values accordingly, then you fill the field for the
 relevant key figure and use this to fill RESULT_TABLE.
Regards
Happy Tony
Points == Thanks

Similar Messages

Return table In bI7.0-Bit urgent

Hi All,
I Am uploading falt file which is having the values for 0fisper and fisyear but i need to fetch the values for 0calday, 0calweek and 0calquarter, i have succesfully loaded the data in bw3.5 by using the return table for Zdaily(key figure).
Can any one tell me where to use this RETURN TABLE concept in BI.7.0..
Its bit urgent.
regards
Ram

Return Table
return table in update rules
Message was edited by:
krish

Return tables in Routines used in an Update Rule

I previously had a routine configured as an update method in an Update Rule. On the configuration screen where I specified the Routine name, I checked "Return Table".
Now I've deleted this Routine and I am using the Source Key Figure as the Update Method. However the "Return Table" box is still checked and if I uncheck it, it goes back to "Checked" status as soon as i scroll to the next key figure and then back to the original key figure.
While this doesnt sound like too serious a problem, I think it's causing my Update rules to fail during activation with the message, The field "RESULT" is unknown, but there is a fiel rows 1698." (SAP typo, not mine).
Following the suggestions in the Help for this error do not work either. When I try to choose Extras -> Display Activated Program, I receive a second message "Unable to find a tool to process the request".
Can anyone help?

Wardell,
sounds like a bug to me. Open a message to SAP support to get a fix.
Regards,
Marc
SAP NetWeaver RIG

Problem with return table(adding extra record)

Hi,gurus,
I am facing a probelm with return table, i.e it is adding body record and workarea record also to the data target. so, it is adding the actual record to data target including the workarea record to with the key figure and year values as zeros and spaces. It's quite strange.
Please help me out, thanks a lot.

Hi,
 I have an ODS with the keys fields(ZPS_TXMID,ZPS_NODE，ZPS_NODE) and data fields(ZAU_C108,ZAU_C109,0PROJECT). I have to split one record from datasource to 6 records into my ODS. I'm updating ZAU_C109 with a routine with return table. Here is the code, please check it for me:
 data: prj like /BIC/PZPS_TXMID-PROJECT.
data: ls_icube_value like ICUBE_VALUES.
clear ls_icube_value.
select single PROJECT into prj from /BIC/PZPS_TXMID
 where /BIC/ZPS_TXMID = COMM_STRUCTURE-/BIC/ZPS_TXMID.
ls_icube_value-/BIC/ZPS_TXMID = COMM_STRUCTURE-/BIC/ZPS_TXMID.
ls_icube_value-/BIC/ZAU_C108 = COMM_STRUCTURE-/BIC/ZAU_C108.
ls_icube_value-/BIC/ZPS_NODE = '1'.
ls_icube_value-/BIC/ZPS_SNODE = '0'.
ls_icube_value-PROJECT = prj.
ls_icube_value-/BIC/ZAU_C109 = COMM_STRUCTURE-/BIC/ZPS_HJHSJ.
APPEND ls_icube_value TO RESULT_TABLE.
ls_icube_value-/BIC/ZPS_NODE = '1'.
ls_icube_value-/BIC/ZPS_SNODE = '1'.
ls_icube_value-PROJECT = prj.
ls_icube_value-/BIC/ZAU_C109 = COMM_STRUCTURE-/BIC/ZPS_HPSJ.
APPEND ls_icube_value TO RESULT_TABLE.
ls_icube_value-/BIC/ZPS_NODE = '1'.
ls_icube_value-/BIC/ZPS_SNODE = '2'.
ls_icube_value-PROJECT = prj.
ls_icube_value-/BIC/ZAU_C109 = COMM_STRUCTURE-/BIC/ZAU_C101.
APPEND ls_icube_value TO RESULT_TABLE.
ls_icube_value-/BIC/ZPS_NODE = '2'.
ls_icube_value-/BIC/ZPS_SNODE = '0'.
ls_icube_value-PROJECT = prj.
ls_icube_value-/BIC/ZAU_C109 = COMM_STRUCTURE-/BIC/ZPS_TJHSJ.
APPEND ls_icube_value TO RESULT_TABLE.
ls_icube_value-/BIC/ZPS_NODE = '2'.
ls_icube_value-/BIC/ZPS_SNODE = '1'.
ls_icube_value-PROJECT = prj.
ls_icube_value-/BIC/ZAU_C109 = COMM_STRUCTURE-/BIC/ZPS_TDSJ.
APPEND ls_icube_value TO RESULT_TABLE.
ls_icube_value-/BIC/ZPS_NODE = '2'.
ls_icube_value-/BIC/ZPS_SNODE = '2'.
ls_icube_value-PROJECT = prj.
ls_icube_value-/BIC/ZAU_C109 = COMM_STRUCTURE-/BIC/ZAU_C102.
APPEND ls_icube_value TO RESULT_TABLE.
ABORT = 0.
 After loading, I checked the contents of ODS, there are 6 records(0project, ZAU_C108 are blank, other fields are correct) + 1 more record(ZPS_TXMID,0project, ZAU_C108 are correct, other fields are blank), what I expect is only 6 records with all fields being filled properly, no blanks, no extra records. Is it strange? or am I doing sth. wrong?
Your help is appreciated.

Return Tables

Hi fellow SAPians,
what is the significance of Return tables in SAP BW. I wonder can it be used for distribution purposes similar to SEM -BPS ? Cld anybody clarify me these concepts ?
thanking you in Advance,

Have a look at these posts in the help: they explain pretty well what it's all about.
" Update routines generally only have one return value. However, in the Key Figure Calculation tabstrip, you can create a routine by choosing the Return table option. The corresponding key figure routine now has a return table instead of a return value. You can now generate as many key figure values as you like from one data record."
http://help.sap.com/saphelp_nw04/helpdata/en/21/894eeee0b911d4b2d90050da4c74dc/frameset.htm (2nd part)
http://help.sap.com/saphelp_nw04/helpdata/en/7f/61fc37f456491ee10000009b38f8cf/frameset.htm

Lookup and a return table

1.0 what's a lookup and a return table, are they same thing?
2.0 how do you create it?
thanks

Hi,
a lookup table to enhance your data while loading. For instance you load sales in a cube and your source is providing the site and you require to post the Sale Organization.
In a start routine (Ttransfer or Update rules) you fill via ABAP a lookup table having the relation site to Sales Org.
In the sales org routine you read this lookup table with the key site and post the corresponding sales org in your IObj.
The return table functionality in update rules:
Imagine you are loading sales in a KF in a cube. Your requirement is have a year to date key figure stored as well in your cube.
So you load sales for January, posted to period JAN.
You would need to post this record for next 11 months as well in order to able to see YTD sales correctly when you select period FEB.
The return table enables you to post many records from 1 loaded records.
The lookup tables are created as internal table via ABAP in start routines
The return table is located in an update routine for a particular key figure and you use ABAP as well
Hoping this will answer your enquiries
Olivier.

Please tell me what this update routine do?

Hi,
Please see the update routine below for calculating the difference between two dates..In ODS I am getting different values like (30/06/2006-26/10/2005=170 & 02/02/2006-19/10/2005=0 ).
PROGRAM UPDATE_ROUTINE.
$$ begin of global - insert your declaration only below this line -
TABLES: ...
DATA: ...
*& Form calc_num_working_days
 calculate the number of working days between two dates using
 the 'GB' factory calendar
FORM calc_num_working_days USING P_DATE1
 P_DATE2
 P_NO_DAYS.
Data: FAC_DATE1 LIKE SCAL-FACDATE,
 FAC_DATE2 LIKE SCAL-FACDATE.
check p_date1 <> '00000000'.
check p_date2 <> '00000000'.
CALL FUNCTION 'DATE_CONVERT_TO_FACTORYDATE'
 EXPORTING
 CORRECT_OPTION = '-'
 DATE = p_date1
 FACTORY_CALENDAR_ID = 'GB'
 IMPORTING
DATE =
 FACTORYDATE = FAC_DATE1
WORKINGDAY_INDICATOR =
EXCEPTIONS
CALENDAR_BUFFER_NOT_LOADABLE = 1
CORRECT_OPTION_INVALID = 2
DATE_AFTER_RANGE = 3
DATE_BEFORE_RANGE = 4
DATE_INVALID = 5
FACTORY_CALENDAR_NOT_FOUND = 6
OTHERS = 7
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION 'DATE_CONVERT_TO_FACTORYDATE'
 EXPORTING
 CORRECT_OPTION = '-'
 DATE = p_date2
 FACTORY_CALENDAR_ID = 'GB'
 IMPORTING
DATE =
 FACTORYDATE = FAC_DATE2
WORKINGDAY_INDICATOR =
EXCEPTIONS
CALENDAR_BUFFER_NOT_LOADABLE = 1
CORRECT_OPTION_INVALID = 2
DATE_AFTER_RANGE = 3
DATE_BEFORE_RANGE = 4
DATE_INVALID = 5
FACTORY_CALENDAR_NOT_FOUND = 6
OTHERS = 7
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
P_No_DAYS = FAC_DATE1 - FAC_DATE2.
ENDFORM. " calc_num_working_days
$$ end of global - insert your declaration only before this line -
FORM compute_data_field
TABLES MONITOR STRUCTURE RSMONITOR "user defined monitoring
USING COMM_STRUCTURE LIKE /BIC/CS8ZSAL_O03
 RECORD_NO LIKE SY-TABIX
 RECORD_ALL LIKE SY-TABIX
 SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING RESULT LIKE /BIC/AZQS_O0400-/BIC/ZCRDQUST2
 RETURNCODE LIKE SY-SUBRC "Do not use!
 ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
$$ begin of routine - insert your code only below this line -
fill the internal table "MONITOR", to make monitor entries
Data: wa_ACREC type dats,
 wa_no_days type i.
Clear wa_ACREC.
Clear wa_no_days.
break-point.
look-up the Acceptance Received Date for the corresponding Quote:
Select single /BIC/ZCR_ACREC
into wa_ACREC
from /BIC/AZQOT_O0200
where CRM_OHGUID = COMM_STRUCTURE-CRM_QUOGUI.
IF sy-subrc <> 0. "wa_ACREC is initial.
 RESULT = 0.
ELSEIF COMM_STRUCTURE-/BIC/ZCR_PL_ON is initial.
 RESULT = 0.
ELSE.
compare AccR date with the planned-on date (in the comm_structure):
 perform calc_num_working_days
 USING COMM_STRUCTURE-/BIC/ZCR_PL_ON
 wa_ACREC
 wa_no_days.
 RESULT = wa_no_days.
ENDIF.
if abort is not equal zero, the update process will be canceled
ABORT = 0.
$$ end of routine - insert your code only before this line -
ENDFORM.

The code may return zero in case
- /BIC/AZQOT_O0200 table (ODS ZQOT_O02) has no entry for
CRM_QUOGUI value coming in the record, or, ZCR_PL_ON is blank in the record.
If both above conditions are not true, then only it calls to find the difference of date.
Another thing to note (as I understand) is that it gets the factory calendar date corresponding to these two dates and then gives you a difference of those dates. I am not sure if that will return the no_of_workdays correctly (am not on system so can't check at the moment).
However, I understand your primary concern is 0 values; those likely come because one of the conditions mentioned above is true for that record.

Urgent help required to write the code in update routine

Hi all,
i want to calculate open purchase order qty in update routine
formula is
open purchase order qty = scl qty - rec qty
where schd line date is less then or equal to 90 days from the current date.
I have written one code : but its giving error that comm_structure is not defined in abap dictionary,can any body help to write appropriate routine. this calculation i am making for MM, and data source and cube are 2lis_02_scl and cube is zc_pur01 ( made by coping the 0pur_c01), data source scl has all fields required in the foumula...here is my code
DATA: COMM_STRUCTURE LIKE /BIC/CS2LIS_02_SCL.
DATA: SCL_QTY LIKE COMM_STRUCTURE-/BIC/ZK_SCLQTY.
DATA:      GR_QTY LIKE COMM_STRUCTURE -/BIC/ZK_GRQTY.
DATA: SCL_DATE.
SCL_DATE = SY-DATUM + 90.
SELECT COMM_STRUCTURE -/BIC/ ZK_SCLQTY COMM_STRUCTURE -/BIC/ ZK_GRQTY FROM
/BIC/CS2LIS_02_SCL INTO   SCL_QTY     GR_QTY
WHERE
COMM_STRUCTURE -/0SCHED_DATE LE SCL_DATE.
IF SYSUBRC = 0
RESULT = SCL_QTY - GR_QTY.
ELSE = NOVALUE.
ENDIF.
Can any body help me soon its very urgent.
thanks

Hi Anupam,
I am not a very good ABAP Programmer, but found some things to notify u inyour code..
DATA: COMM_STRUCTURE LIKE /BIC/CS2LIS_02_SCL,
      SCL_QTY LIKE COMM_STRUCTURE-/BIC/ZK_SCLQTY,
      GR_QTY LIKE COMM_STRUCTURE -/BIC/ZK_GRQTY.
DATA SCL_DATE LIKE SY-DATUM.
SCL_DATE = SY-DATUM + 90.
SELECT COMM_STRUCTURE -/BIC/ ZK_SCLQTY COMM_STRUCTURE -/BIC/ ZK_GRQTY FROM
/BIC/CS2LIS_02_SCL INTO SCL_QTY GR_QTY
WHERE
COMM_STRUCTURE -/0SCHED_DATE LE SCL_DATE.
IF SYSUBRC = 0
RESULT = SCL_QTY - GR_QTY.
ELSE.
What should be the return value if you dont have to    calculate the result."
ENDIF.
try it.. and see..
regards,
kishore.

Update Routine & Start Routine in BI 7.0

Hi Experts,
We have recently upgraded from BI 7.0 , I am confused about where to write start routine & update routine in transformations of BI 7.0?
Please mention any pointers?
Thanks.
Sharat.

Hi
When you open the start routine you will see a routines info which gives you help on this.
A summary would be:
Update routine in transformation.
RESULT = source_field-material.
Basically you can acess the value of the record by using source_field.
Start routine.
The data comes in the form of an internal table with name SOURCE_PACKAGE.
You can access the values by looping into a work area.
LOOP AT SOURCE_PACKAGE assigning <source_fields>.
ENDLOOP.
End routine(This is a new feature in BI 7.0 where you can modify data when transformations are complete and before data is updated to info-providers)
The data comes in the form of an internal table with name RESULT_PACKAGE.
You can access the values by looping into a work area.
LOOP AT RESULT_PACKAGE assigning <result_fields>.
ENDLOOP.
Hope this helps you to understand the basics of the abap used in the transformations .
Regards
Samarpita

Update routine to populate value for field ZDOCCATG(Document category)

Hi Experts,
 I need to populate data for field ZDOCCATG(Document Category) based on the value of the below two fields,
1. 0deb_cre_lc(Debit / credit Amount)
2. 0ac_doc_typ(Belegart)
The logic is as follows:
if 0deb_cre_lc > '0'.
 if 0ac_doc_typ == 'dz'.
 ZDOCCATG = Disputes.
 else
ZDOCCATG = Invoices.
 end If.
else
if 0ac_doc_typ < '0'.
ZDOCCATG = Credits.
end if.
I need to write the update routine to get the values assigned for Document category based on these two fields. When i open the routine for the field ZDOCCATG, i can see the below screen:
PROGRAM UPDATE_ROUTINE.
$$ begin of global - insert your declaration only below this line -
TABLES: ...
DATA: ...
$$ end of global - insert your declaration only before this line -
FORM compute_data_field
TABLES MONITOR STRUCTURE RSMONITOR "user defined monitoring
USING COMM_STRUCTURE LIKE /BIC/CS80FIAR_O03 - (Communication structure)
 RECORD_NO LIKE SY-TABIX
 RECORD_ALL LIKE SY-TABIX
 SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING RESULT LIKE /BIC/AZOARFSCM00-/BIC/ZDOCCATG
 RETURNCODE LIKE SY-SUBRC "Do not use!
 ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
$$ begin of routine - insert your code only below this line -
fill the internal table "MONITOR", to make monitor entries
result value of the routine
RESULT = .
if abort is not equal zero, the update process will be canceled
ABORT = 0.
$$ end of routine - insert your code only before this line -
ENDFORM.
Please let me know the code to be inserted (based on the logic mentioned above) in the above screen . Thanks
Regards,
Kavitha Jagannath

Hi Kavitha,
 Supposing the technical name of fields is /bic/0deb_cre_lc and /bic/0ac_doc_typ use the code below at the marked position.
PROGRAM UPDATE_ROUTINE.
$$ begin of global - insert your declaration only below this line -
TABLES: ...
DATA: ...
$$ end of global - insert your declaration only before this line -
FORM compute_data_field
TABLES MONITOR STRUCTURE RSMONITOR "user defined monitoring
USING COMM_STRUCTURE LIKE /BIC/CS80FIAR_O03 - (Communication structure)
RECORD_NO LIKE SY-TABIX
RECORD_ALL LIKE SY-TABIX
SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING RESULT LIKE /BIC/AZOARFSCM00-/BIC/ZDOCCATG
RETURNCODE LIKE SY-SUBRC "Do not use!
ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
$$ begin of routine - insert your code only below this line -
fill the internal table "MONITOR", to make monitor entries
result value of the routine
<----- Paste the code below as shown here --->
if comm_structure-/bic/0deb_cre_lc > 0.
if comm_structure-/bic/0ac_doc_typ == 'DZ'.
 result = 'DISPUTES'.
else
 result = 'INVOICES'.
endIf.
elseif comm_structure-/bic/0deb_cre_lc < 0.
result = 'CREDITS'.
end if.
<----
>
if abort is not equal zero, the update process will be canceled
ABORT = 0.
$$ end of routine - insert your code only before this line -
ENDFORM.
Regards:
Jitendra
Edited by: Jitendra Gupta on Oct 15, 2009 3:05 PM

Data package's data coolection in one internal table of Update rule in bw

Hello Gurus,
I have a requirement in bw which demands to create update routine, in which I need to find the vendor for the material, which doesn't have vendor by some business rule but, here in this case data is divided into different datapackages so here in this case material data is splited over different datapackages.
One material can have n no of records with differnt plants.
My only question is like can we collect all datapackage data in one internal table.
Ex: if there are total 5 datapckages, so in update rule can we collect all these datapackages records?
Please suggest your opinion.
Thanks in advance,
Snehal.
Moderator message: please have a look in the BW forums.
Edited by: Thomas Zloch on Jan 11, 2011 1:49 PM

hi,
i think your problem is need of a work area...
Using "FOR ALL ENTRIES IN lt_zhrp" You must use " check lt_zhrp is not initial "
DATA: lt_zhrp TYPE STANDARD TABLE OF zhrp,
lt_zhrt TYPE STANDARD TABLE OF zhrt.
*new
data: wa_zhrp type lt_zhrp.
SELECT tabnr
FROM zhrp
INTO CORRESPONDING FIELDS OF TABLE lt_zhrp
WHERE objid = lv_posid.
LOOP AT lt_zhrp INTO wa_zhrp.
SELECT low
FROM zhrt
INTO CORRESPONDING FIELDS OF TABLE lt_zhrt
WHERE tabnr = wa_zhrp-tabnr " lt_zhrp-tabnr
AND attrib = 'NET_VALUE'.
ENDLOOP.
Edited by: Miguel Antunes on Apr 28, 2010 4:22 PM

Update routine for 0proc_unit conversion

Hi all,
My infoobject 0OPR_ACTWRK uses 0PROC_UNIT for units. It holds data in days and in hours. When I load it to a cube, I want to convert all values to working hours.
I figured out that I have to use an update routine in my update rules. A lot of forum threads about unit conversion mention the function module UNIT_CONVERSION_SIMPLE. Can I use this function for my problem? Or should I use a different function module?
This will be my first ABAP code, so can anyone help me and tell me what I have to fill in exactle in the routine format below?
$$ begin of routine - insert your code only below this line        -
fill the internal table "MONITOR", to make monitor entries
result value of the routine
RESULT = .
result value of the unit
UNIT = .
if the returncode is not equal zero, the result will not be updated
RETURNCODE = 0.
if abort is not equal zero, the update process will be canceled
ABORT = 0.
$$ end of routine - insert your code only before this line         -
Thanks in advance!
Regards, Pieter

Dear Pieter,
I am not infront of the system..
the following surely will give error.. :).. so post back here.. so that me or someone else will reply you..
So let us start witht he following coding in the 'Start routine'.
LOOP AT DATA_PACKAGE.
IF DATA_PACKAGE-UNIT= 'DAY'.
   DATA_PACKAGE-opr_pldwrk = DATA_PACKAGE-opr_pldwrk * 8.
ELSE.
Do nothing.
ENDIF.
MODIFY DATA_PACKAGE.
ENDLOOP.
Regards,
Hari
Message was edited by: Hari Kiran Y
Message was edited by: Hari Kiran Y

Update routine infinite loop

Hello Experts,
For loading ODS2 we are making a lookup on ODS1 for 0material based on
purchaing document number, item line item.
Is there any mistake in the start routine or update routine.
Because the load goes in infinite loop. I think update routine should be changed.
Any suggestions are appreciated
Start routine:
data: begin of itab occurs 0,
        pur_doc like /BIC/AZODS100-OI_EBELN,
        item like /BIC/AZODS100-OI_EBELP,
        material like /BIC/AZODS100-material,
      end of itab.
clear itab.
select OI_EBELN OI_EBELP MAT_PLANT from /BIC/AZODS100
         into table itab.
Update routine for 0material
loop at itab where pur_doc = COMM_STRUCTURE-OI_EBELN
                   and item = COMM_STRUCTURE-OI_EBELP.
       RESULT = itab-matplant.
endloop.

Hi,
this takes a long time, because with each record of your data packaged it is doing the loop and scanning each row of the internal table. Use the following instead.
Start routine:
types: begin of t_itab,
pur_doc like /BIC/AZODS100-OI_EBELN,
item like /BIC/AZODS100-OI_EBELP,
material like /BIC/AZODS100-material,
end of t_itab.
data: itab type hashed table of t_itab with unique key pur_doc item.
select OI_EBELN OI_EBELP MAT_PLANT from /BIC/AZODS100
into table itab order by oi_ebeln oi_ebelp mat_plant.
I hope these fields are the key of the ods object.
Update routine for 0material
data: wa_itab type t_itab.
read table itab into wa_itab with table key pur_doc = COMM_STRUCTURE-OI_EBELN
item = COMM_STRUCTURE-OI_EBELP.
if sy-subrc = 0.
RESULT = wa_itab-matplant.
else.
clear result.
endif.
Hope this helps
regards
Siggi

Currency unit in return tables

Hi @ all,
I'm working with a return table in the update rules to calculate a key figure. Is it possible, that the currency unit of the key figure is not filled automatically? The currency units in source system and target system are the same.
Thank you for your help!
Clemens

Hallo Clemens,
yes, you're right; are you sure as well to not have more COMP_CODES then 0009 and 0010?
perhaps it would be wiser to lookup the comp_code-currency from the master data of 0COMP_CODE (0CURRENCY is one of its attributes) in order to avoid having it empty and always hardcode it... This is of course if you want to derive the company code currency...
hope this helps....
let us know if you question is answered by closing the thread!
Olivier.

Where is the option "return table" in BW7.0

Is it possible to have a transformation rule return a table in stead of one single record?
I remember from teched that this option would be added in SP13, but we are at SP16 and I can't find it.

BI 7.0 does not have Return table option till now. That has been replaced by(or rather say the functinality can be acheived by) END Routine.
Thanks..
Shambhu

Return tables in Update routines

Similar Messages

Maybe you are looking for