RFC input Table parameter holds how many rows

[former_member849899]

Hi experts,

I have create one custom RFC to assign roles to user which takes input in table parameter it_user_details which is of type se11 structure. Structure components names are user_id, role_name.

Now there can be role wise multiple entries in input table.

My question is - How many records we can pass to this table at a time? Is there any limit for number of records?

Thanks in advance.

[former_member849899]

Hi experts,

I have create one custom RFC to assign roles to user which takes input in table parameter it_user_details which is of type se11 structure. Structure components names are user_id, role_name.

Now there can be role wise multiple entries in input table.

My question is - How many records we can pass to this table at a time? Is there any limit for number of records?

Thanks in advance.

[sergei-u-niq]

an internal table can contain arbitrary many rows.

[michael_piesche]

I am not aware of any actual limitiations in the amount of table rows for interface parameters. Of course there can be potential problems (network, timeout, memory ...) if there are billions and billions of records with lots of data to be send, but so far I have never encountered a problem that was due to the amount of table rows. The 'only' main drawback with 'too many' records will be the performance of calling the RFC and sending or receiving those records.

How many table rows are you expecting? Even if it is millions in your case with only two rather short attributes, I wouldnt worry too much about it. Of course since you are obviously aware of a large amount of data to be sent, you should still observe and analyse the RFC and its functionality and performance when using it in the production the first time.

There can be of course 'limitations' within the logic of the function that has to work with those records, e.g. if the records are used to select data from a database (e.g. for a SQL SELECT WHERE IN statement, the limitations could be around 10'000), but that would not be a limitation of the interface, but of the logic/coding not appropriately handling large amounts of data.

[michael_piesche]

pankaj_p, is your question answered, do you still have open or new issues with your question? Please add comments if still issues exist, upvote or accept answers if answers are valuable or sufficient to solve your problem, add and describe your own answer if you found a totally different solution to your problem, close question with appropriate tag if discussion about the question can be ended.

[FredericGirod]

the limit is linked to the memory limit specified in the instance parameters (rz10).

Simplified it is : memory size / row size = number of entries possible

[Sandra_Rossi]

It depends on the memory available at the time the RFC-enabled function module runs, so it depends of the amount of memory used by other sessions in the server...

In short, don't bother !