Smartforms Dump

[Former Member]

Guyz,

My smartforms dumping in testing environment but not in development environment ....

dump details :

PERFORM_NOT_FOUND

Call (PERFORM) to a non-existent routine.

This may be due to any of the following reasons:

1. One of the programs "SAPLSTXBC " or "/1BCDWB/SAPLSF00000007 " is currently

being developed.

The name "%WI1 " of the called routine may be incorrect, or

the routine "%WI1 " is not yet implemented in the program

"/1BCDWB/SAPLSF00000007 ".

-

2. If the program SAPMSSY1 is involved in the runtime error, one of

the function modules called via RFC is not flagged as remote-capable.

(see Transaction SE37 Goto -> Administration -> RFC flag)

3. There is an inconsistency in the system. The versions of the

programs "SAPLSTXBC " and "/1BCDWB/SAPLSF00000007 " do not match.

UPON DEBUGGING AND COMPARING BOTH DEV & TESTING ENVIRONMENTS I FOUND that program /1BCDWB/SAPLSF00000007 is not matching across the env.... in Dev i have include " INCLUDE /1BCDWB/LSF00000007F01." but not in staging....

upon checking transport logs for this transport in staging i didn't find any unsuccessful/warning messages against smartforms....but in the same transport i have few other table types, structures out of which there is a warning for a view with RC = 4....

DOES ANY BODY KNOWS HOW THIS SYSTEM GENERATED PROGRAM IS MISMATCHING IN VERSIONS ???? should i reimport the same transport into staging environment pls ?

Quick reply into this is very much appreciated and ofcourse POINTS will be rewarded ...

thanks in advance

[Former Member]

Guyz,

My smartforms dumping in testing environment but not in development environment ....

dump details :

PERFORM_NOT_FOUND

Call (PERFORM) to a non-existent routine.

This may be due to any of the following reasons:

1. One of the programs "SAPLSTXBC " or "/1BCDWB/SAPLSF00000007 " is currently

being developed.

The name "%WI1 " of the called routine may be incorrect, or

the routine "%WI1 " is not yet implemented in the program

"/1BCDWB/SAPLSF00000007 ".

-

2. If the program SAPMSSY1 is involved in the runtime error, one of

the function modules called via RFC is not flagged as remote-capable.

(see Transaction SE37 Goto -> Administration -> RFC flag)

3. There is an inconsistency in the system. The versions of the

programs "SAPLSTXBC " and "/1BCDWB/SAPLSF00000007 " do not match.

UPON DEBUGGING AND COMPARING BOTH DEV & TESTING ENVIRONMENTS I FOUND that program /1BCDWB/SAPLSF00000007 is not matching across the env.... in Dev i have include " INCLUDE /1BCDWB/LSF00000007F01." but not in staging....

upon checking transport logs for this transport in staging i didn't find any unsuccessful/warning messages against smartforms....but in the same transport i have few other table types, structures out of which there is a warning for a view with RC = 4....

DOES ANY BODY KNOWS HOW THIS SYSTEM GENERATED PROGRAM IS MISMATCHING IN VERSIONS ???? should i reimport the same transport into staging environment pls ?

Quick reply into this is very much appreciated and ofcourse POINTS will be rewarded ...

thanks in advance

[Former Member]

Why don't you do a SYNTAX CHECK or try to ACTIVATE the SMART Form in the test environment, that should point out the exact error.

Regards,

Ravi

[Former Member]

Hi Sridhar,

Just jump into the Function module which generated by your smartform and do a global search on "%WI1", you should have the element and its related perform(generated by smartform). Make sure "WI1" is available in your smartform and its corresponding code.

Regards,

Raghav

[Former Member]

Raghav - ""%WI1", you should have the element and its related perform(generated by smartform). Make sure "WI1" is available in your smartform and its corresponding code"

As dump informed sub-routine '%WI1' isn't avilable in test environment...in fact program 1BCDWB/SAPLSF00000007 is just empty...with two sub-routine having nothing inside them....

Ravi - Syntax check in test env worked fine...can't activate in test env as we don't have access to 'CHANGE' ....

[Former Member]

GUYZ --- SOLVED

I generated the smartforms instead of activating...it worked like a charm ....i'll award points as promised....

Thanks for ur time guyz....

[Former Member]

You shouldn't be calling the smartform function module name directly because it may different in different systems. Use FM 'SSF_FUNCTION_MODULE_NAME' to get the internal name of you smartform function module.