Solved: Function module (SE37)

Former Member · ‎10-23-2007

Hi all.

I have created a Function module (Tcode SE37). Its not giving any syntax error, my problem is its not displaying output.

Please look at this code and help me to correct this.

Main program.

parameters : plant type zmonthpay-dcode.

data: begin of itab2 occurs 0,

name(20),

age(2),

work(5),

end of itab2.

CALL FUNCTION 'ZP_FM1'

EXPORTING

plant = plant

tables

itab1 = itab2

.

write: itab2-name, itab2-age, itab2-work.

Function module code:-

Import parameter: plant.

Tables: itab1

FUNCTION ZP_FM1.

data: begin of itab occurs 0,

name(20),

age(2),

work(5),

end of itab.

if plant = 'AD00'.

itab-name = 'prajwe'.

itab-age = '24'.

itab-work = 'abap'.

append itab.

endif.

if plant = 'IC00'.

itab-name = 'prajwe12'.

itab-age = '25'.

itab-work = 'abap1'.

append itab.

else.

itab-name = 'prajwe13'.

itab-age = '26'.

itab-work = 'abap2'.

append itab.

endif.

move itab[] to itab1[].

append itab1.

ENDFUNCTION.

Please help me.

Regards.

Prajwal.k

Former Member · ‎10-23-2007

hi,

when u r writing itab2 values, make aloop and then try to write

loop at itab2.

write: itab2-field1, itab2-field2.

endloop.

regards

karhik,if u have still error send message

Former Member · ‎10-23-2007

Hi

see the doc of fun module and do accordingly

Function Modules are Global ABAP programs created by SAP for reusable purpose.they have IMPORT,EXPORT and TABLE parameters, and EXCEPTIONS to through when error occurs.

You can create them from TCode SE37.

Go through the following doc:

Function modules are cross-program, reusable procedures that are organized into function groups, and whose functions are implemented between the statements FUNCTION and ENDFUNCTION. Function modules and their interfaces are created in the Function Builder.

Function Module Interfaces

The parameter interface of a function module is defined in the Function Builder. It includes the definition of interface parameters and the specification of exceptions that can be triggered by a function module. The Function Builder automatically generates comment lines below the FUNCTION statement in the source code of the function module, which represent the interface of the function module with the following syntax:

Syntax

... [IMPORTING parameters]

[EXPORTING parameters]

[CHANGING parameters]

[TABLES table_parameters]

[{RAISING|EXCEPTIONS} exc1 exc2 ...]

The syntax and semantics of IMPORTING, EXPORTING, CHANGING, RAISING, and EXCEPTIONS mainly correspond to the definition of method interfaces with [CLASS-]METHODS. The additional option of defining table parameters using TABLES is obsolete.

Interface parameters

The interface parameters are defined on the relevant tab pages in the Function Builder.

IMPORTING parameters are input parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input parameter. The content of the actual parameter is passed to the input parameter when the call is made. The content of an input parameter for which 'pass by reference' is defined cannot be changed in the function module.

EXPORTING parameters are output parameters. When the function module is called, a suitable actual parameter can be specified for every output parameter. The content of an output parameter that is defined for 'pass by value' is transferred to the actual parameter if the function module is completed without errors. An output parameter that is defined for pass by reference is not initialized when the function module is called.

CHANGING parameters are input and output parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input or output parameter. When the function module is called, the content of the actual parameter is passed to the input/output parameter, and when the function module is completed, the content of the input/output parameter is passed to the actual parameter.

TABLES parameters are table parameters. Table parameters are obsolete CHANGING parameters that are typed as standard tables with a header line. If an internal table without a header line or a table body is passed as an actual parameter to a formal parameter of this type, an empty local header line is generated in the function module. If an internal table with a header line is used as an actual parameter, both the table body and the header line are passed to the function module. Pass by value is not possible in formal parameters defined using TABLES. Formal parameters defined with TABLES can be replaced by formal parameters defined with CHANGING. A local work area can be created for the internal table in the function module by using the addition LIKE LINE OF itab of the DATA statement.

Exceptions

The exception of a function module are defined on the Exceptions tab page in the Function Builder. Here you can select exception classes to define whether class-based exceptions are declared or non-class-based exception are defined. Class-based exceptions are represented in the above syntax by RAISING, and non-class-based exceptions are represented by EXCEPTIONS.

The addition RAISING is used to declare class-based exceptions that can be propagated from the function module to the caller. Exceptions in the categories CX_STATIC_CHECK and CX_DYNAMIC_CHECK must be explicitly declared, otherwise a propagation can lead to an interface violation. A violation of the interface leads to the treatable exception CX_SY_NO_HANDLER. Exceptions of the category CX_NO_CHECK are implicitly always declared. The declaration of exceptions of the category CX_STATIC_CHECK is statically checked in the syntax check. For exceptions of the category CX_DYNAMIC_CHECK, the check is not performed until runtime. In a function module in which class-based exceptions are declared with the RAISING addition, the statement CATCH SYSTEM-EXCEPTIONS cannot be used. Instead, the relevant treatable exceptions should be handled in a TRY control structure.

The addition EXCEPTIONS is used to define a list of non-class-based exceptions that can be triggered in the function module using the statements RAISE or MESSAGE RAISING. Exceptions defined in this way - as with formal parameters - are bound to the function module and cannot be propagated. If an exception of this type is triggered in a function module, and no return value has been assigned to it with the homonymous addition EXCEPTIONS of the CALL FUNCTION statement when the call was made, this leads to a runtime error.

Note

For new developments after release 6.10, SAP recommends that you work with class-based exceptions that are independent of the function module.

RFC is a technology which is used to access a functions (Modules) from

the remote systems.

If a function module is set as remote enabled which can be access from

the remote system via RFC.Eg: U can access the Remote enabled function modules in ur VB,Webdynpro,Java,Visual composer program.

A function module can be set as remote enabled by SE37->Go to ur FM->click the option Button "remote enabled".

But Normal function modules can not accessd from the remote system.

Good Example for RFC enabled function module is : BAPI(Business Application Programming Interface)

Note: All BAPIs are Remote enabled but not all remote enabled function modules are BAPI.

CALLING A FUNCTION MODULE:

1)In U ABAP Editor --> Click "Patter" ---> Selection Option Button "Call Function"

--> Write the Corresponding FM name --> Hit Enter

2)The appropriate import ,export Parameters will be displayed in ur editor

3)Pass the Values Here.

Also check these links.

http://www.geocities.com/victorav15/sapr3/abapfun.html

Check this link:

http://help.sap.com/saphelp_erp2004/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm

Check this link:

http://help.sap.com/saphelp_erp2004/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm

See the following links:

http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/26/64f623fa8911d386e70000e82011b8/content.htm

Regards

Anji

hymavathi_oruganti · ‎10-23-2007

in the fn module logic, did u declare itab in the tables column?

Former Member · ‎10-23-2007

hi hymavathi.

yes i have declared. but i have not mentioned associated type.

Former Member · ‎10-23-2007

hi,

when u r writing itab2 values, make aloop and then try to write

loop at itab2.

write: itab2-field1, itab2-field2.

endloop.

regards

karhik,if u have still error send message

Former Member · ‎10-23-2007

move itab[] to itab1[].

append itab1.

no need to do this you can do like

itab[] = itab1[]

Or you can do

loop at itab.

itab1 = itab.

endloop.

make sure that itab and itab1 is in TABLES part of FM also with sam type.

rewards if useful..............

Minal

former_member223537 · ‎10-23-2007

Import parameter: plant.

Tables: itab1

FUNCTION ZP_FM1.
data: begin of itab occurs 0,
name(20),
age(2),
work(5),
end of itab.

if plant = 'AD00'.
itab-name = 'prajwe'.
itab-age = '24'.
itab-work = 'abap'.
append itab.
endif.
if plant = 'IC00'.
itab-name = 'prajwe12'.
itab-age = '25'.
itab-work = 'abap1'.
append itab.
else.
itab-name = 'prajwe13'.
itab-age = '26'.
itab-work = 'abap2'.
append itab.
endif.

itab1[] = itab[].  "Add this line

* move itab[] to itab1[]. "COmment This

*append itab1. " COMMENT THIS


ENDFUNCTION.

former_member1345686 · ‎10-23-2007

Hi,

I wonder if the table structure itab1 is already the same with the one you used in the calling program .

break the function at the line

itab1[] = itab[].

check itab1 and itab content ; are they empty ?

break the program right after the function call, and check the following :

sy-subrc = 0 ...

if not, it means some error happened while calling the function ;

rgds,

TS WINEDYA