Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Nested input tables


We´re having problems to call an RFM from Web Dynpro (version 2.0.15). Our input structure looks as follows:


L Filter - Structure

L Filter Item - Table

L Filter Key - Table

This is the code:

wdContext.nodeZaf_Afa_Ws_Sok_Input().bind( new Zaf_Afa_Ws_Sok_Input() );

Zafa_Wsrequest_Filter filter = new Zafa_Wsrequest_Filter();

Zafa_Wsrequest_Filteritem FNRFilterItem = new Zafa_Wsrequest_Filteritem();

Zafa_Wsrequest_Filterkey FNRFilterKey =new Zafa_Wsrequest_Filterkey();

FNRFilterKey.setValue( wdContext.nodeSearchAttributes().currentSearchAttributesElement().getFnr());



// add item to filter

filter.addFilteritem( FNRFilterItem );

// bind filter to RFC

wdContext.nodeZaf_Afa_Ws_Sok_Input().nodeIs_Filter().bind( filter) ;



When debugging the java code the model gets all the data, but when looking at the ABAP code all tables are "initial".

An idea anyone how to solve this?


Regards Sophie

Former Member
Former Member replied


Sadly, I cannot find anywhere document regarding Adaptive RFC Model "do-es" and "don't-s" but there was a strong point that nested tables must not be used.

Moreover, in our own project we found and reported a bug with tables as input parameter (instead of table parameter), that cause tables to break output structure handling (they were erroneously duplicated in output). I'm not sure whether or not this bug was fixed since last autumn '05.

So, in brief: don't use table parameters as import/export and do not use nested tables. Re-write your RFM or expose it via other RFM with simple structure.

Valery Silaev

EPAM System

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question