Smartform Dumping..Please help....

[Former Member]

Hi Guys,

I am developing a new smartform for the PO in MM(AFS ).

I know, I am putting too much stuff inside an item loop (item, vas, sizes, HTS, texts etc, putting more than 30 templates and 20 more required). Do we have any chance to avoid this dumping including any OSS notes?

I am pasting the dump message below.

************************************

<i>While generating program "/1BCDWB/SAPLSF00000009", the system discovered that

an ABAP

event block, a control structure (such as IF... ENDIF or LOOP...

ENDLOOP) or a routine (such as a FORM routine) is too big.

The resulting jump is too great to be generated.

The jump may be no greater than 32768 for the internal load format

(corresponding to around 10,000 ABAP statements).

However, the jump in this case would have been 32819.</i>

******************************************

Please help me and it is urgent...

Thanks

Ashok

[Former Member]

Hi

Go to ST22 and open this short dump message in ST22.

When you display this dump message in ST22 you can go to the exact line of source code where the dump is being created.

Then analyse that part of code (Loop, Conditions, Function modules, Query etc)..If any part of code consumes more buffer / execution time, try to optimize (performance) such part of code.

If you face specific issues there let us explain more.

Bala

[Former Member]

Hi Bala, I am pasting the code below from ST22. At line 1847, the dump occurs. I am put too many templates in side item loop. I knew that, but is there any way to get rid of this dump?

Thanks

Ashok

1835 EXPORTING MODE = %OPEN

1836 EXCEPTIONS OTHERS = 1.

1837 IF SY-SUBRC <> 0. RAISE ERROR. ENDIF.

1838 CALL FUNCTION 'SSFCOMP_XSF_SECTION'

1839 EXPORTING NAME = 'ITEM_LOOP'

1840 MODE = %OPEN

1841 EXCEPTIONS OTHERS = 1.

1842 IF SY-SUBRC <> 0. RAISE ERROR. ENDIF.

1843 CALL FUNCTION 'SSFCOMP_XSF_BODY'

1844 EXPORTING MODE = %OPEN

1845 EXCEPTIONS OTHERS = 1.

1846 IF SY-SUBRC <> 0. RAISE ERROR. ENDIF.

>>>>> LOOP AT I_ITEMS INTO W_ITEMS .

1848 CALL FUNCTION 'SSFCOMP_TABLE_BEGIN'

1849 EXPORTING I_DEFINITION = 'ITEM_HEADER_TEMPLATE1'

1850 EXCEPTIONS OTHERS = 1.

1851 IF SY-SUBRC <> 0. RAISE ERROR. ENDIF.

1852 CALL FUNCTION 'SSFCOMP_XSF_BODY'

1853 EXPORTING MODE = %OPEN

1854 EXCEPTIONS OTHERS = 1.

1855 IF SY-SUBRC <> 0. RAISE ERROR. ENDIF.

1856 CALL FUNCTION 'SSFCOMP_TABLE_GOTO_CELL'

1857 EXPORTING I_ROW = 001

1858 I_COL = 001

1859 EXCEPTIONS OTHERS = 1.

1860 IF SY-SUBRC <> 0. RAISE ERROR. ENDIF.

1861 REFRESH %INPUTFIELDS.

1862 FILL_TEXTAREA 'F' 0 0 ' '.

1863 PERFORM %WRITE_TEXT USING 'IH_ITEM_NO' SPACE SPACE 'P' SPACE %INPUTFIELDS %TEXTAREA.

1864 IF %WEXIT <> SPACE. EXIT. ENDIF.

1865 CALL FUNCTION 'SSFCOMP_TABLE_GOTO_CELL'

1866 EXPORTING I_ROW = 001

[Former Member]

Hi Ashok

That loop has huge number of function module calls and perform statements. That is the reason you are getting this dump.

1. You try to avoid atleast few FM calls inside this loop. Try to optimize the performance as much as possible.

2. Second good way is you can solve this issue with the help of your basis team. There is some setting in basis to allot the available buffer for program execution. They have to increase that buffer/memory level for program execution. I have solved this scenarion by increasing that buffer/memory level. This way will help you certainly.

Bala