Increased mem consumption when using SAP GDTs in Enterprise Services

[Former Member]

Hi,

at our customer - a large Bank - I've been battling to convince the Ingeration and Development teams to make use of SAP GDTs when developing customer enterprise services.

One of the arguments against it, is that the more input/output parameter are used in a service interface (SAP GDTs can contain hundreds of fields), the more memory is allocated per service call.

From an XML message transmission perspective, arguing against this is easy. Essentially only data is passed over the wire that's mandatory or needed. That's the beauty of XML, hence the message footprint on the wire is relatively small.

However, the dialogue process, processing the service request in the ABAP backend needs to allocate memory for the entire message as per design time definition - e.g. all 500 fields of the SAP GDT.

Is this statement correct?

As we are expecting huge service call volumes, this is a serious concern.

Any comments on the above are much appreciated.

Kind Regards,

Rene (+27 83 642 7141)

[Former Member]

Hi,

>However, the dialogue process, processing the service request in the ABAP backend needs to allocate memory for the entire message as per design time definition - e.g. all 500 fields of the SAP GDT.

From the ABAP perspective processing 500 fields is not a problem at all, also all those fields are useful in one way or another but if you feel that 500 fields will never be used then write another service to suppress un-necessary fields.

Bottleneck could be xml transformation if volume is too high.

Regards,

Gourav