Assigning SMARTFORMS to output types in SPRO

Question

Hi,
I have created a test smartform and smartstyle, generated a function module, and temporarily put some code in a custom "test" program to ensure it is working, and it does (note calling the compiled version of the smartform function module name, by getting it's name from SSF_FUNCTION_MODULE_NAME) and all executes correctly.
Could anyone tell me however how I assign the smartform to execute from standard SAP via output type configuration in SPRO in SD as an example. Do we still need to specify a print program name and form routine to execute in configuration, just like SAPscript works ? I notice there is a field available for a smartform name, but then how would "whatever standard SAP is calling the smartform" know what parameters to pass into my generated function module for the smartform ? Also, does this have anything to do with the field "layout module" which is directly above the smartform field ?
Here's what I have tried: I entered the custom Z test program I created, entered the form routine name of this program which simply calls directly the function module for the smartform. (Now the smartform field in configuration is redundant) The standard SAP SAPscript print option window appears when I execute my SD transaction, and then the output option window appears which comes standard with the smartform function module call. As the smartform field in configuration is redundant going this method, I think I am going completely on the wrong route. Can someone help ?
Thanks,
Graham.

Answer 1

Hi Satish,
Yes we already have this, and it works with the following issue:-
1) The default output controller window for print options which normally appears for SAPscript pops up.
2) The default output controller window for print options which normally appears for SMARTFORM output (looks slightly different to window in 1) appears also.
IMPORTANT: If I take out the name of the SMARTFORM in the "Smartform text box" it makes no difference and still works as above. This is because my driver/print program and subroutine is calling the function module to call the smartform, so it already knows which smartform to execute.
It is like the standard SD configuration is thinking my print program is for a SAPscript which is why I get both 1 and 2 above. Note: the SMARTFORM does output.
Thanks,
Graham.