3
votes

Not really critical question, but i'm curious

I am working on a form and sometimes the generated function name is /1BCDWB/SF00000473, and sometimes /1BCDWB/SF00000472. This goes back and forth.

Does anyone know what's the idea behind this? Cuz i'm quite sure it's not a bug (or i might be wrong on that).

3
check this out, trying to get a SAP stack exchange started area51.stackexchange.com/proposals/41621/… - Jared

3 Answers

4
votes

It is not a bug. You always have to use SSF_FUNCTION_MODULE_NAME to determine the actual function module name and call it dynamically using CALL FUNCTION l_function_module.

1
votes

Smartform FMs are tracked by internal numbering and thats saved in the table STXFADMI. You would always notice the different number in Development System if you have deleted any existing Form. Similarly, you would also notice the different number in your Quality system based on the sequence the forms are imported in QAS and the forms as well (as test forms are not migrated to QAS.

Similar behavior is also true for Adobe Form generated FMs.

1
votes

You need to understand that every smartform has a different interface and hence the automatically generated function module needs to have different import parameters.

Due to this reason the 'SSF*' FMs generate a FM specific for your smartform. The name of the 'generated' FM changes when you migrate from one system to another. And that's the reason why you should use a variable while calling the 'generated' fm and not hardcode it.

The same goes with Adobe form as someone has rightly said in this thread.