SAP-modulepool

[Former Member]

hai,

Plz Explain abt chain&endchain with on change and on request.

[Former Member]

hi rao,

it is used for validating a group of fields.

in b/w chanin and end chain we write the 'field' statement and a one module statement in that module we can validate that fields

[Former Member]

hi srinu,

The Chain endchain method is a way of input checks in dialog modules.

Suppose you have input fields f1, f2 , f3 etc.

If you write the foll. st,

CHAIN.

FIELD: <f1>, <f 2>,...

MODULE <mod1>.

FIELD: <g1>, <g 2>,...

MODULE <mod2>.

...

ENDCHAIN.

When this command is used, all of the fields on the screen that belong to the processing chain (all of the fields listed in the field statements) are made ready for input again. Other fields are not ready for input. Whenever the MODULE statement appears within a processing chain, even if there is only one FIELD attached to it, all of the fields in the chain (not only the affected field) are made ready for input again, allowing the user to enter new values. If the fields in the processing chain are only checked once, the PAI processing continues directly after the FIELD statement, and the preceding modules are not called again.

Check this out

http://help.sap.com/saphelp_nw04/helpdata/en/9f/dbabbd35c111d1829f0000e829fbfe/content.htm

http://help.sap.com/saphelp_47x200/helpdata/en/d1/801ca2454211d189710000e8322d00/frameset.htm

Regards,

Naveen

[vinod_gunaware2]

<b>Conditional Module Calls</b>

Simple module calls are processed in the sequence in which they appear in the screen flow logic. However, the syntax of the screen language also allows you to make PAI module calls dependent on certain conditions by using the MODULE statement together with the FIELD statement. You can apply conditions to both single fields and groups of fields. Conditional module calls can help you to reduce the runtime of your program, particularly with modules that communicate with database tables.

<b>Conditions for Single Screen Fields</b>

You can ensure that a PAI module is only called when a certain condition applies by using the following statement:

FIELD <f> MODULE <mod> ON INPUT|REQUEST|*-INPUT.

The additions have the following effects:

ON INPUT

The ABAP module is called only if the field contains a value other than its initial value. This initial value is determined by the data type of the field: Space for character fields, zero for numeric fields. Even if the user enters the initial value of the screen as the initial value, the module is not called. (ON REQUEST, on the other hand, does trigger the call in this case.)

<b>

ON REQUEST</b>

The module <mod> is only called if the user has entered something in the field. This includes cases when the user overwrites an existing value with the same value, or explicitly enters the initial value.

In general, the ON REQUEST condition is triggered through any form of "manual input". As well as user input, the following additional methods of entering values also call the module:

The element attribute PARAMETER-ID (SPA/GPA parameters).

The element attribute HOLD DATA

CALL TRANSACTION ... USING

Automatic settings of particular global fields

ON *-INPUT

The ABAP module is called if the user has entered a "*" in the first character of the field, and the field has the attribute *-entry in the Screen Painter. When the input field is passed to the program, the * is removed. * behaves like an initial field in the ON INPUT condition.

The functions of the FIELD statement for controlling data transport also apply when you use MODULE.

Conditions for Multiple Screen Fields

To ensure that one or more PAI modules are only called when several screen fields meet a particular condition, you must combine the calls in the flow logic to form a processing chain. You define processing chains as follows:

CHAIN.

...

ENDCHAIN.

All flow logic statements between CHAIN and ENDCHAIN belong to a processing chain. The fields in the various FIELD statements are combined, and can be used in shared conditions.

CHAIN.

FIELD: <f1>, <f 2>,...

MODULE <mod1> ON CHAIN-INPUT|CHAIN-REQUEST.

FIELD: <g1>, <g 2>,...

MODULE <mod2> ON CHAIN-INPUT|CHAIN-REQUEST.

...

ENDCHAIN.

The additions ON CHAIN-INPUT and ON CHAIN-REQUEST work like the additions ON INPUT and ON REQUEST that you use for individual fields. The exception is that the module is called whenever at least one of the fields listed in a preceding FIELD statement within the chain meets the condition. So <mod1> is called when one of the fields <fi> meets the condition. <mod2> is called when one of the fields <f i> or <g i> meets the condition.

Within a processing chain, you can combine individual FIELD statements with a MODULE statement to set a condition for a single field within the chain:

CHAIN.

FIELD: <f1>, <f 2>,...

FIELD <f> MODULE <mod1> ON INPUT|REQUEST|*-INPUT

|CHAIN-INPUT|CHAIN-REQUEST.

MODULE <mod2> ON CHAIN-INPUT|CHAIN-REQUEST.

ENDCHAIN.

The module <mod1> is called when screen field <f> meets the specified condition for individual fields. <mod2> is called when one of the fields <fi> or <f> meets the condition. If you use the addition ON CHAIN-INPUT or ON CHAIN-REQUEST with FIELD <f>, the condition also applies to the entire chain and module <mod1> and <mod2> are both called.

In cases where you apply conditions to various combinations of screen fields, it is worth setting up a separate processing chain for each combination and calling different modules from within it.

The functions of the FIELD statement for controlling data transport also apply when you use processing chains. Within a processing chain, screen fields are not transported until the FIELD statement. Processing chains also have another function for the FIELDS statements that they contain. This is described in the section on validity checks.

Calling Modules after Cursor Selection

You can specify that a module should only be called if the cursor is positioned on a particular screen element. To do this, use the statement

MODULE <mod> AT CURSOR-SELECTION.

The module <mod> is called whenever the function code of the user action is CS with function type S. If you use this statement, it is best to assign the function code CS to function key F2. This also assigns it to the mouse double-click.

The module is called in the sequence in which it occurs in the flow logic. It does not bypass the automatic input checks. Data is transported from screen fields in the order in which it is defined by the FIELD statements. The function code is empty, and neither SY-UCOMM nor the OK_CODE field is affected. You can also combine this MODULE statement with the FIELD statement:

FIELD <f> MODULE <mod> AT CURSOR-SELECTION.

or, for more than one field:

CHAIN.

FIELD: <f1>, <f 2>,...

MODULE <mod> AT CURSOR-SELECTION.

ENDCHAIN.

The module <mod> is only called if the cursor is positioned on an input/output field <f> or an input/output field <fi> in the processing chain. You can only apply this statement to input/output fields.

The call hierarchy of the different combinations is as follows:

If a MODULE... AT CURSOR-SELECTION statement is executed that was combined with FIELD, a statement without FIELD is not executed.

If a statement using FIELD appears more than once for the same screen field <f>, only the first statement is executed.

If a statement without FIELD occurs more than once, only the last statement is executed.

It is irrelevant whether the statements occur within a CHAIN ... ENDCHAIN block or not.

Conditional module calls

PROGRAM DEMO_DYNPRO_ON_CONDITION.

DATA: OK_CODE LIKE SY-UCOMM,

INPUT1(20), INPUT2(20), INPUT3(20),

FLD(20).

CALL SCREEN 100.

MODULE INIT_SCREEN_100 OUTPUT.

SET PF-STATUS 'STATUS_100'.

ENDMODULE.

MODULE CANCEL INPUT.

LEAVE PROGRAM.

ENDMODULE.

MODULE CURSOR INPUT.

GET CURSOR FIELD FLD.

MESSAGE I888(BCTRAIN) WITH TEXT-001 FLD.

ENDMODULE.

MODULE MODULE_1 INPUT.

MESSAGE I888(BCTRAIN) WITH TEXT-002.

ENDMODULE.

MODULE MODULE_2 INPUT.

MESSAGE I888(BCTRAIN) WITH TEXT-003.

ENDMODULE.

MODULE MODULE_* INPUT.

MESSAGE I888(BCTRAIN) WITH TEXT-004 INPUT3.

ENDMODULE.

MODULE C1 INPUT.

MESSAGE I888(BCTRAIN) WITH TEXT-005 '1'.

ENDMODULE.

MODULE C2 INPUT.

MESSAGE I888(BCTRAIN) WITH TEXT-005 '2' TEXT-006 '3'.

ENDMODULE.

The next screen (statically defined) for screen 100 is itself. It has the following layout:

The screen fields INPUT1, INPUT2, and INPUT3 are assigned to the input fields. The function code of the pushbutton is EXECUTE.

In the GUI status STATUS_100, the icon (F12) is active with function code CANCEL and function type E. The function key F2 is also active with function code CS and function type S. The F8 key is active with the function code EXECUTE and no special function type.

The screen flow logic is as follows:

PROCESS BEFORE OUTPUT.

MODULE INIT_SCREEN_100.

PROCESS AFTER INPUT.

MODULE CANCEL AT EXIT-COMMAND.

CHAIN.

FIELD: INPUT1, INPUT2.

MODULE MODULE_1 ON CHAIN-INPUT.

FIELD INPUT3 MODULE MODULE_* ON *-INPUT.

MODULE MODULE_2 ON CHAIN-REQUEST.

ENDCHAIN.

FIELD INPUT1 MODULE C1 AT CURSOR-SELECTION.

CHAIN.

FIELD: INPUT2, INPUT3.

MODULE C2 AT CURSOR-SELECTION.

ENDCHAIN.

MODULE CURSOR AT CURSOR-SELECTION.

The program uses information messages to show which modules are called following user interaction and which data is transported.

Whenever one of the input fields 1 or 2 is not initial, the system calls the module MODULE_1 for any user interaction.

Whenever one of the three input fields is changed, the system calls the module MODULE_2 for any user interaction.

Whenever input field 3 contains a * entry, the system calls module MODULE_* for any user interaction.

If the user chooses F2 or double-clicks a text field on the screen, the system calls the module CURSOR.

If the user chooses F2 or double-clicks input field 1, the system calls the module C1.

If the user chooses F2 or double-clicks input field 2 or 3, the system calls the module CURSOR. Module C2 is never executed, since the MODULE ... AT CURSOR SELECTION statement occurs twice, and only the last is processed.

regards

vinod