You use BAPI-calls or RFC-calls in your Web Dynpro project but you get no data viewed? Here are some things you can do, identifying the problem. Basically, there are three steps you should do:
check your import parameters
check in ABAP-trace files, if data is transmitted at all
check your context mapping in the Web Dynpro views
Check import Parameters
First, I recommend to test the call in transaction SE37 and fill the necessary importparameters / tables. You can set RFC traget sys to NONE to simulate an RFC-call. If your input data is verified, you can execute the remote call form your external application (like Web Dynpro) and check the dev_rd trace described in the next chapter.
ABAP trace files
Since, you're connecting through a gateway to the ABAP-system, the data (input & output) can be traced. Use transaction SMGW to increase the trace level of the gateway trace to at least 3 (SMGW, Menu Goto / Gateway / Trace / Increase level). Check in ST11 the dev_rd trace file, if the level was set successfully to 3. There should be a line like: * SWITCH TRC-LEVEL from 2 TO 3
You should be able to see (you have to search for it, because the amount of data is relative huge):
The name of the RFC / BAPI you've called & the input data. This is an example of the BAPI_GET_USER_DETAIL with importparameter set to HAUCK:
So we can be sure, the call was successfull and the desired data was transmitted. Make sure to decrease the trace level again, because it's growing very fast.
Check context mapping
Your context-nodes in the views should be mapped to the Output-nodes of the controller-context. These Output nodes should be invalidated in the controller after the remote call to inform the views that there's new data.