Function module in crystal reports using tables as input

Question

We had a function module created with a few import parameters. We successfully linked it in crystal and were able to retrieve the data.
To accommodate the requirement of being able to pick multiple values for some of the parameters, the import parameters were changed to tables. When testing in ECC, we are able to retrieve the data using the function module.
However, when we're using the same approach as before in crystal reports, we are not able to retrieve the data.
Is it possible in crystal to pass the input parameters to tables ?
Any ideas what I might be doing wrong?
Thanks,
Mat

Answer 1

Hi John,
The solution is very simple. 
You create a function module in ECC (t-code SE37) that will receive you input parameters, process them, and export a table with your results.
In the function module you define an input parameter using a CHAR120 data type (ex. PERNR).
In the function module source code you add logic to split the input parameter
[SPLIT i_PERNR AT ',' INTO TABLE itab_PERNRS.]
You then create a crystal report against your function module.
In your crystal report you create a parameter using type "string" (ex. I_PERNR).
When you execute the crystal report, you input a comma delimited string in the parameter.
[00001234,00005678,00009123]
The function module will receive the string of values, split the string to an internal table, and process accordingly.
I still have no solution for the 120 character restriction in the CR->ECC interface.  In the meantime, I get around this by creating multiple parameters (PERNR1, PERNR2, PERNR3, etc.). 
Each parameter is set up to pass a string of 120 characters to ECC.
The function module is set up to concatenate the parameters before splitting.
[CONCATENATE PERNR1 PERNR2 PERNR3 into I_PERNR]
Hope this helps.