How To Fix FL397 - &1 (tipo &2) puede reducir el rendimiento en RFC (con serial.clás.)

SAP Error Message - Details

• Message type: E = Error

• Message class: FL - Function Builder messages

• Message number: 397

• Message text: &1 (tipo &2) puede reducir el rendimiento en RFC (con serial.clás.)

¿Qué causa este problema?

This parameter contains a data type that can result in high memory
consumption and poor system performance when using the classic RFC
serialization. Performance is particularly badly affected if you have a
slow network connection (with high latency) or low bandwidth. This
affects IMPORTING, EXPORTING, and CHANGING parameters, which use deep
data types. Deep data types are tables or flat structures that contain
at least one field of variable length (for example, String/XString).

Respuesta del sistema

El sistema emite un mensaje de error y no le permitirá continuar con esta transacción hasta que se resuelva el error.

¿Cómo arreglar este error?

Use other serialization variants if possible. You can set these in
destination maintenance (transaction SM59).
The new fast serialization is always the fastest and is generally
compatible with classic serialization. Unfortunately, this serialization
is not available in older systems.
If your communication partner does not support the new serialization,
you can use basXML serialization (available in SAP NetWeaver 2007 and
higher). In destination maintenance, you can set either 'basXML' or
'basXML forced'. If you select 'basXML', the function module must be
available on the client side and the basXML flag must be set in the
function module. If you select 'basXML forced', it is not necessary to
select the 'basXML' property in the function module.
Caution: The basXML serialization serializes the data in an XML-like
intermediate format. When converted to text, there can be rounding
differences, for example, in binary floating point numbers. Also, errors
in the data content (for example, letters in NUMC fields) can result in
terminations.
If you cannot use the new serialization or the basXML protocol, please
check whether you can replace strings with fixed-length character
fields. Tables of structures that only contain fixed-length fields can
be transferred using the TABLES parameter (which gives significantly
better performance).
If you have decided on a new serialization or are prepared to accept the
effect on performance, you can suppress the warning with the pseudo
comment
<SE>##RFC_PERFORMANCE_OK</>
after the function statement.
Example:
<SE>FUNCTION MYFUNC ##RFC_PERFORMANCE_OK. </>

Procedimiento para Administradoras de Sistemas

Extracto de mensaje de error del sistema SAP. Copyright SAP SE.