Version changes in Function Module

[Former Member]

hi

if got a task which tells tht there is a version change in Development and Production. systems..

i found that the changes r nothing but the commented line which are in production but not in development.. so does this makes any difference in executing the FM output..

reply me asap....

[Former Member]

Hi,

If it's just the comments you will not have any problems in executing the FM.

Regards,

Raghavendra

[seshatalpasai_madala]

Hi,

If there is no code change then there will not be any change in the behaviour, but make sure the all the PERFORM statements. Check if any of these routinses are changed. You can also just create a dumy transport request and edit the FM once and activate it and release it to be on safe side.

Regards,

Sesh

[Former Member]

Hi

If you are sure that the only difference between the two versions is only those commented lines... then absolutely no difference in executing the FM.

You check out clearly; even the interface of the FM (means export, import, tables exceptions, etc..)

Regards

Surya.

[Former Member]

hi Satheesh,

If the changes are only as you mentioned...it will not make in difference in the execution and output.

But you need to check the following points also, while dealing with function modules:

1. Go to the main program of the function module and check whether all the 'F' includes (function group name followed by F01, F02...etc), 'I' includes, if any, 'O' includes, if any and the TOP include...

2. Check for differences for the parameters (import export and tables)

3. check for differences in the structure underlying these parameters.

Hope this helps.

Sajan.

[Former Member]

ya i checked this in the se37 Tcode.

utilities->version->version management

i got this as version changes

Contents unchanged:

1 1 FUNCTION Z_SD_SALESDOC_GETDETAIL_202S.

2 2 *"

3 3 ""Global interface:

... ... ...

184 184 * processed via the MSO system. If relevant the osgrade flag is set

185 185 * and MSO will return an array of serial numbers to be processed.

186 186 *"

Lines not available in version of the REMOTE system:

187 * R3DK911594 Neil Kleinberg - eContract Project 1426

188 * Add SERVICE_SKU flag to ITEM_TAB to return whether or not the material

189 * is a SERVICE_SKU.

190 *"

Contents unchanged:

191 187

192 188

193 189 DATA : F1 TYPE I,

... ... ...

2576 2572 endloop.

2577 2573

2578 2574 ENDFORM. "USE_SSD_SCHEDULING_LOGIC

[seshatalpasai_madala]

Hi

The following line are code changes so better arrange for a trasport from your DEV to PROD system.

191 187

192 188

193 189 DATA : F1 TYPE I,

... ... ...

2576 2572 endloop.

2577 2573

2578 2574 ENDFORM. "USE_SSD_SCHEDULING_LOGIC

Regards,

Sesh

[Former Member]

Compare the Changes between Dev and Production and if there are only comment changes no problem with the execution.

But if it is some thing else(code changes) then you have to Transport the changes to Production.

Regards

Vijay