<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>interfaces on Abapinho</title><link>https://abapinho.com/en/tags/interfaces/</link><description>Recent content in interfaces on Abapinho</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2009-2026 Nuno Godinho</copyright><lastBuildDate>Mon, 16 Jul 2012 09:00:01 +0000</lastBuildDate><atom:link href="https://abapinho.com/en/tags/interfaces/index.xml" rel="self" type="application/rss+xml"/><item><title>Complex parameters in remote functions</title><link>https://abapinho.com/en/2012/07/parametros-complexos-por-rfc/</link><pubDate>Mon, 16 Jul 2012 09:00:01 +0000</pubDate><guid>https://abapinho.com/en/2012/07/parametros-complexos-por-rfc/</guid><description>&lt;p>Remote function calls (by RFC) do not support parameters with complex structures (deep structures). In other words, if any of the parameters has a structure in which one of the fields is another structure or an internal table then, hard luck, it won’t work.&lt;/p>
&lt;p>Do you give up? No, you don’t. Abapinho provides the solution: serialization.&lt;/p></description></item></channel></rss>