ABAP Function Module structure understanding

[Former Member]

Hi Friends,

I am trying to understand the function module structure.

I am invoking RFCs using SAPJCO API.

Some questions in understanding parameter types:-

In the export parameter, I see the field as structure, simple data type, etc.

for one field when I click on type, it says its of Line Type, then further when I click on line type field value, it says its a structure.

**What is Line type? it has structure inside.

**Can a structure has multiple cardinality?I mean can a strucure contain multiple rows of data?

structure can another structure, etc. so I have to check on my SAPJCO API side, that if a structure contains anotehr structure, etc.

Thanks!

[Former Member]

one more related question to it,

as my SAPJC API returns parameters fo fucntion module through:-

importParamaterList.., so lets say, I get the return type as structure.

JCO.Structure may contain elements of simpole type or it may contain structure inside.

So, will this JCO.Structure give me complete list of all elements of it, parameter/nested structure etc? Or, do I need to invoke another function module to retrieve JCO Structure parameters?

[Former Member]

Hi

I don't know which RFC you're calling anyway a structure (line type) can have some fields are another line type (so flat structure) or table type (so multiple rows).

Max

[Former Member]

Hi Max, thanks for the reply.

I am making it generic to invoke any RFC.

so The question is raised based on this:

If ZRFC contains some strucuture does it mean to be single cardinality ormultiple cardinality.

lets say Structure S1 containes F1

S1 contains F1, F2, S1a

S2 contains F1, F2 , T2a

here:-

F = Field

S = strucuture

T = table

so, what should be the cardinality for these types? should I say cardinality for S1 should be single and for S2 it should be multpiple?

and:

what is the cardinality of a structure in general ? can it be mutlple cardinality type?

I need to know the cardinality type before having data inside it, as I want to understand the metadata of an RFC.