Techniques

[Former Member]

Hi,

What r the types of modularisation techniques in ABAP?

Pls gimme explanation in all.

Points sure.

[Former Member]

hi,

<b>MACRO</b>

IF YOU WANT TO REUSE THE SAME SET OF STATEMENTS MORE THAN ONCE IN A PROGRAM, YOU CAN INCLUDE THEM IN A MACRO.

DEFINE<MACRO>. <STATEMENTS> END-OF-DEFINITION.

YOU MUST SPECIFY COMPLETE STATEMENTS BETWEEN DEFINE AND END-OF-DEFINITION. THESE STATEMENTS CAN CONTAIN UP TO NINE PLACEHOLDERS (&1, &2... &9).

INCLUDE PROGRAMS

INCLUDE PROGRAMS ARE GLOBAL R/3 REPOSITORY OBJECTS. THEY ARE SOLELY FOR MODULARIZING SOURCE CODE, AND HAVE NO PARAMETER INTERFACE.

<b>SUBROUTINES</b>

THEY ARE PROCEDURES PRICIPALLY FOR LOCAL MODULARIZATION THAT IS THEY ARE GENERALLY CALLED FROM THE PROGRAM IN WHICH IT IS DEFINED.

TO DEFINE A SUBROUTINE,

FORM <SUBR> [USING] [CHANGING] ENDFORM.

USE LOCAL <F>, IF YOU WANT TO PREVENT THE VALUE OF A GLOBAL DATA OBJECT FROM BEING CHANGED INSIDE A SUBROUTINE.

WE CAN TERMINATE THE SUBROUTINE BY USING EXIT (UNCONDITIONALLY) OR CHECK (CONDITIONALLY).

TO CALL A SUBROUTINE,

PERFORM <SUBR> [USING] [CHANGING]

TO A CALL A SUBROUTINE EXTERNALLY,

PERFORM <SUBR> (<PROG>) [USING] [CHANGING] [IF FOUND]

THE IF FOUND ADDITON IS TO AVOID THE RUNTIME ERROR.

<b>FUNCTION MODULES</b>

FUNCTION MODULES ARE FOR GLOBAL MODULARIZATION, THAT IS, THEY ARE ALWAYS CALLED FROM A DIFFERENT PROGRAM. FUNCTION MODULES CONTAIN FUNCTIONS THAT ARE USED IN THE SAME FORM BY MANY DIFFERENT PROGRAMS. THEY ARE IMPORTANT IN THE R/3 SYSTEM FOR ENCAPSULATING PROCESSING LOGIC AND MAKING IT REUSABLE. FUNCTION MODULES MUST BE DEFINED IN A FUNCTION GROUP, AND CAN BE CALLED FROM ANY PROGRAM.

FUNCTION GROUPS ARE CONTAINERS FOR FUNCTION MODULES. YOU CANNOT EXECUTE A FUNCTION GROUP. WHEN YOU CALL AN FUNCTION MODULE, THE SYSTEM LOADS THE WHOLE OF ITS FUNCTION GROUP INTO THE INTERNAL SESSION OF THE CALLING PROGRAM.

TRANSACTION FOR FUNCTION BUILDER – SE37

TO CALL A FN MOD,

CALL FUNCTION ‘FN NAME’ EXPORTING IMPORTING CHANGING TABLES EXCEPTIONS.

[Former Member]

Hi

We use the SUBROUTINES and FUNCTION MODULES for Modularising technique

Subroutines are the piece of code written between FORM..ENDFORM..after defining the PERFORM <name> Using/Changing paramters

for fun modules

see this

Function Modules;

Check this matter.

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_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm

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

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

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

[Former Member]

Formal parameters are the parameters that are passed to/from subroutines.

These parameters help in passing values to the subrotuines or to get values from the subroutines to the calling program.

Go to ABAPDOCU transaction code.

OPen the node The ABAP Programming language->Modularization Techniques->Procedures->Subrotuines for some example programs that demonstrate the usage of formal parameters.

Reward points if it has been useful to you

Thanks

Murali Poli

[Former Member]

Hi,

All ABAP programs are modular in structure and made up of processing blocks (see Structure of ABAP Programs). There are two kinds of processing blocks, those that are called from outside a program by the ABAP runtime system, and those that can be called by ABAP statements in ABAP programs.

Processing blocks that are called using the ABAP runtime system:

Event blocks

Dialog modules

Processing blocks that are called from ABAP programs:

Subroutines

Function modules

Methods

The processing blocks that you call from ABAP programs are called procedures.

As well as modularization in processing blocks, ABAP allows you to modularize source code by placing ABAP statements either in local macros or global include programs.

Check this link,

http://help.sap.com/saphelp_47x200/helpdata/en/54/57fe0c786a11d194c90000e8353423/frameset.htm

Thanks,

Reward If Helpful.