topic Subroutines in Application Development and Automation Discussions

Subroutines

Former Member — Tue, 31 Jul 2007 05:01:36 GMT

Hi,

I want to pass an internal table by using subroutines. Now I want to have two subroutines one changing the contents of the internal table and the other without changing the internal table contents.

Re: Subroutines

Former Member — Tue, 31 Jul 2007 05:04:27 GMT

Hi Ravikanth,

Refer this link,it will provide u sample code for all.

http://help.sap.com/saphelp_nw2004s/helpdata/en/9f/db979035c111d1829f0000e829fbfe/content.htm

hope this helps.

Re: Subroutines

Former Member — Tue, 31 Jul 2007 05:04:37 GMT

We use TABLES parameters for passing the internal tables to subroutines and Internal tables are always passed by reference

see the doc

PERFORM - parameter_list

Syntax

... [TABLES itab1 itab2 ...]

[USING a1 a2 ...]

[CHANGING a1 a2 ...].

Extras:

1. ... TABLES itab1 itab2 ...

2. ... USING a1 a2 ...

3. ... CHANGING a1 a2 ...

Effect

These additions assign actual parameters to the formal parameters from the parameter interface for the subroutine subr. You can specify all data objects whose data type matches the typing of the corresponding formal parameter (see Check Typing) as actual parameters. Each formal parameter assumes all the properties of the actual parameter assigned to it when it is called.

Addition 1

... TABLES itab1 itab2 ...

Effect

If you specify the addition TABLES, each table parameter t1 t2 ... for the subroutine called that is defined with the addition TABLES to the FORM statement must be assigned an internal table itab as the actual parameter. The assignment of the actual parameters to the formal parameters takes place using their positions in the lists t1 t2 ... and itab1 itab2 ... .

You can only specify standard tables for itab. Transfer takes place by means of a reference. If a specified table itab has a header line, this is also transferred; otherwise, the header line in the corresponding table parameter t is blank when it is called.

Note

Use of table parameters in the interface for subroutines is obsolete but a large number of subroutines have not yet been converted to appropriately typed USING or CHANGING parameters, so that they must still be supplied with data by the TABLES addition to the PERFORM statement.

Example

Static call of the internal subroutine select_sflight transferring a table parameter.

PARAMETERS: p_carr TYPE sflight-carrid,

p_conn TYPE sflight-connid.

DATA sflight_tab TYPE STANDARD TABLE OF sflight.

...

PERFORM select_sflight TABLES sflight_tab

USING p_carr p_conn.

...

FORM select_sflight TABLES flight_tab LIKE sflight_tab

USING f_carr TYPE sflight-carrid

f_conn TYPE sflight-connid.

SELECT *

FROM sflight

INTO TABLE flight_tab

WHERE carrid = f_carr AND

connid = f_conn.

ENDFORM.

Addition 2

... USING a1 a2 ...

Addition 3

... CHANGING a1 a2 ...

Effect

If you specify the additions USING and CHANGING, an actual parameter a1 a2 ... of the appropriate type must be assigned to each of the formal parameters u1 u2 ... and c1 c2 ... defined with the same additions to the FORM statement. The actual parameters specified after USING and CHANGING form one shared list. They are assigned to the formal parameters after the position in the shared list. The type of parameter transfer is defined with the additions USING and CHANGING to the FORM statement. The addition USING must be before CHANGING. Otherwise, the assignment of the actual parameters to the additions USING and CHANGING is irrelevant to the PERFORM statement. It is also irrelevant whether only one or both of the additions is specified.

Notes

For the sake of program documentation, we advise that you specify the additions USING and CHANGING in the FORM statement according to the definition of the parameter interface.

In non-Unicode programs, you can address memory area outside an actual parameter if an actual parameter a1 a2 ... is assigned offset or length specifications. In non-Unicode programs, the length is set to the length of the current parameter if an offset is specified without a length. Both of these lead to warnings in the syntax check and to syntax errors in Unicode programs. The rules for the ASSIGN statement apply to the addressable memory area in non-Unicode programs as well.

Example

The following five PERFORM statements mean the same but only the fourth is recommended, since it is the only one that documents the interface of the subroutine called.

DATA: a1 TYPE string,

a2 TYPE string,

a3 TYPE string,

a4 TYPE string.

PERFORM test USING a1 a2 a3 a4.

PERFORM test CHANGING a1 a2 a3 a4.

PERFORM test USING a1 CHANGING a2 a3 a4.

PERFORM test USING a1 a2 CHANGING a3 a4.

PERFORM test USING a1 a2 a3 CHANGING a4.

...

FORM test USING p1 TYPE string

p2 TYPE string

CHANGING value(p3) TYPE string

value(p4) TYPE string.

...

ENDFORM.

<b>Reward points for useful Answers</b>

Regards

Anji

Re: Subroutines

seshatalpasai_madala — Tue, 31 Jul 2007 05:05:28 GMT

Hi,

If you dont want to change the internal table then use USING and VALUE().

IF you want to change then use CHANGING.


TYPES: tab_type type table of SPFLI.

DATA: itab type tab_type.

PERFORM no_change using itab. "no change

PERFORM change changing itab. "with change

form no_change using value(p_tab) type tab_type.
* cannot change here
endform.

form change changing p_itab type tab_type.
* can change here
endform.

Regards,

Sesh

Re: Subroutines

Vijay — Tue, 31 Jul 2007 05:05:47 GMT



1)perform sub_routine using itab. "changing the contents of the internal table

form sub_routine using p_itab.
code.. to change p_itab. Changes will be reflected to itab also
endform

2) perform sub_routine changing itab."without changing the internal table contents

form sub_routine changing p_itab.
code.. to change p_itab. Changes wont be reflected to itab

<b>reward if useful</b>

endform

Re: Subroutines

Former Member — Tue, 31 Jul 2007 05:28:32 GMT

Hi,

Check the following example:

PROGRAM FORM_TEST.

TYPES: BEGIN OF LINE,

COL1 TYPE I,

COL2 TYPE I,

END OF LINE.

DATA: ITAB TYPE STANDARD TABLE OF LINE WITH HEADER LINE,

JTAB TYPE STANDARD TABLE OF LINE.

PERFORM FILL TABLES ITAB.

MOVE ITAB[] TO JTAB.

PERFORM OUT TABLES JTAB.

FORM FILL TABLES F_ITAB LIKE ITAB[].

DO 3 TIMES.

F_ITAB-COL1 = SY-INDEX.

F_ITAB-COL2 = SY-INDEX ** 2.

APPEND F_ITAB.

ENDDO.

ENDFORM.

FORM OUT TABLES F_ITAB LIKE JTAB.

LOOP AT F_ITAB.

WRITE: / F_ITAB-COL1, F_ITAB-COL2.

ENDLOOP.

ENDFORM.

The produces the following output:

1 1

2 4

3 9

In this example, an internal table ITAB is declared with a header line and an

internal table JTAB is declared without a header line. The actual parameter ITAB

is passed to the formal parameter F_ITAB of the subroutine FILL in the TABLES

addition. The header line is passed with it. After the body of the table has been

copied from ITAB to JTAB, the actual parameter is passed to the formal

parameter F_ITAB of the subroutine OUT using the TABLES addition. The

header line F_ITAB, which is not passed, is generated automatically in the

subroutine.

Regards,

Bhaskar