LSMW user-defined routine error

[Former Member]

Hi,

I have a problem with the routines in the LSMW. This is want I am doing:

1. created a project & subproject.

2. copied 4-5 objects from another project

3. copied all the user routines.

4. ran the objects fine.

After a few days I have copied a new object from the old project and used one of the routines. It gives out the message "HANDLE is not defined under DATA". As I know, this is an lsmw global variable so it should work. This variable can be found in one of the routines. I deleted all the routines and copied them again and it work.

Today I needed a new object, copied it, and it gives again this error; recopied the subroutines...still, error persist.

Please help,

Thank you very much in advanced

LE: Is there any way to adapt your conversion program, after you made modifications to the field mapping?

Message was edited by:

Daniel BALTA

[Former Member]

In Extras->User Menu you can choose to display the Display/Generate Import/Conversion Program options.

If you're struggling to work out the error, it's often a nice trick to display the conversion program and perfom a syntax check on it

[Former Member]

Hello Chris,

I have already done that and I still get this error, but only for this object. I have never declared this data "handle", but here is how 2 conversion programs look like (same project/subproject):

The program that works:

...

• Counters

data:

g_cnt_UPLOAD type i.

• Counter ct_xxxxxxxxxx: number of transferred records

data:

ct_IBIPEQUI type i,

cs_IBIPEQUI type i.

• Global data definitions and data declarations

• __GLOBAL_DATA__

DATA: objnr LIKE equi-objnr.

DATA: handle TYPE balloghndl.

INCLUDE zpmxi_appl_log.

DATA: BEGIN OF wa_tplnr OCCURS 0 ,

tplnr(50),

END OF wa_tplnr.

parameters:

p_filept no-display,

p_trfcpt no-display,

p_packge(5) type n no-display.

• Select-option for wildcard value in file names

......

And the program that doesn't work:

.....

• Counter ct_xxxxxxxxxx: number of transferred records

data:

ct_BIKSSK type i,

cs_BIKSSK type i,

ct_BIAUSP type i,

cs_BIAUSP type i.

parameters:

p_filept no-display,

p_trfcpt no-display,

p_packge(5) type n no-display.

• Select-option for wildcard value in file names

......

How do you explain this?

[Former Member]

The answer is that this variables are indeed custom, and not global. They have to be assigned in step 5 (Mantain field mapping and conversion rules).

In order to see them, go to EXTRAS->Layout and mark "Global Data Definition"