2007 Feb 21 7:14 PM
On Monday I asked in another thread, how to retrieve table meta data using RFCs ()
Having a closer look on what information I got I realized, that this wasn't the exact information I was looking for, although the answers from Ferry have been very good.
What I am actually looking for isn't meta information of tables, but information about the "Associated Type" that is associated with every import, export, or table parameter of a function module.
If I double-click on one of those types in transaction se37 after choosing a function module, I get a wonderful overview about the structure including 'component', 'component type', 'data type', 'length', etc.
Is there an RFC I can call that gives me exactly this meta information by giving an associated type?
Best,
Stefan
2007 Feb 21 10:50 PM
Hi Stefan
Does FM RFC_GET_FUNCTION_INTERFACE help you? It looks like there are some other interesting FMs in the same function group, RFC1, and also RFC2 ...
Regards
Glen
On Monday I asked in another thread, how to retrieve table meta data using RFCs ()
Having a closer look on what information I got I realized, that this wasn't the exact information I was looking for, although the answers from Ferry have been very good.
What I am actually looking for isn't meta information of tables, but information about the "Associated Type" that is associated with every import, export, or table parameter of a function module.
If I double-click on one of those types in transaction se37 after choosing a function module, I get a wonderful overview about the structure including 'component', 'component type', 'data type', 'length', etc.
Is there an RFC I can call that gives me exactly this meta information by giving an associated type?
Best,
Stefan
2007 Feb 21 10:50 PM
Hi Stefan
Does FM RFC_GET_FUNCTION_INTERFACE help you? It looks like there are some other interesting FMs in the same function group, RFC1, and also RFC2 ...
Regards
Glen
2007 Feb 22 1:04 AM
Thanks Glen
I had a look on the proposed function module.
The good thing, it gives me information about the parameter naming for example table name and field name.
But it won't give me more detailed information about the table and the field.
Nevertheless
RFC1::RFC_GET_NAMETAB seems to give me what I need. So your call for RFC1 and RFC2 was a good one.
Thanks again.
Stefan