regarding fm

[Vijay]

hi all,

i just want to know the functionality of four radio buttons ie

<b>

1 start immediately

2 immediate start, no restart

3 start delayed

4. coll. run</b>

in the attributes of fm.

and the <b>update</b> functional module

regards

vijay

[Former Member]

Hi

see the doc

Start update immediately

The function module is processed immediately in the update task.

Update is started immediately, no restart possible

The function module will be edited in the update task. It cannot be updated subsequently.

Start of update delayed

The function module is processed in the update task as a low priority item. You use delayed update primarily for database changes that are not time-critical (e.g. statistical updates).

Update triggered by collector

- For internal use only -

Definition

A number of similar function modules that previously used to run individually in the V2 update process can be grouped together and run collectively.

The reasons for processing them collectively are as follows:

the data of all the calls are read and processed internally

database updates are not made until the internal processing is complete

For further information, refer to the ABAP/4 documentation under IMPORT FROM LOGFILE and UPDATE.

Regards

Anji

[naimesh_patel]

All these options are used when we have to call the FM in the UPDATE TASK.

Generally we use the first option.

From online help...

<b>1. Start update immediately</b>

The function module is processed immediately in the update task.

<b>2. Update is started immediately, no restart possible</b>

The function module will be edited in the update task. It cannot be updated subsequently.

<b>3. Start of update delayed</b>

The function module is processed in the update task as a low priority item. You use delayed update primarily for database changes that are not time-critical (e.g. statistical updates).

<b>4.Update triggered by collector</b>

- For internal use only -

Definition

A number of similar function modules that previously used to run individually in the V2 update process can be grouped together and run collectively.

The reasons for processing them collectively are as follows:

the data of all the calls are read and processed internally

database updates are not made until the internal processing is complete

For further information, refer to the ABAP/4 documentation under IMPORT FROM LOGFILE and UPDATE.

Regards,

Naimesh Patel