How To Fix FL379 - In RFC, it is possible to use boxed components only with basXML protocol

SAP Error Message - Details

• Message type: E = Error

• Message class: FL - Function Builder messages

• Message number: 379

• Message text: In RFC, it is possible to use boxed components only with basXML protocol

What causes this issue?

With RFCs, boxed components are allowed for IMPORT/EXPORT/CHANGING
parameters only if the indicator basXML Protocol is set for the function
module.
With TABLES parameters, no boxed components may be used because
structures with boxed components are deep.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

In transaction SE37, set the flag 'basXML-Supported' if you wish to use
DDIC types with boxed components for parameter typing.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FL379 - In RFC, it is possible to use boxed components only with basXML protocol ?

  The SAP error message FL379 indicates that there is an issue with the use of boxed components in Remote Function Calls (RFC) when the basXML protocol is not being used. This error typically arises in scenarios where you are trying to use certain types of data structures (boxed components) that are not compatible with the current communication protocol.
  Cause:
  The primary cause of this error is the attempt to use boxed components in an RFC call without the basXML protocol. Boxed components are complex data types that can encapsulate multiple fields or structures. The basXML protocol is specifically designed to handle these types of data structures, while other protocols may not support them.
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Use basXML Protocol: Ensure that your RFC calls are configured to use the basXML protocol. This may involve changing the settings in your RFC destination or modifying the code that initiates the RFC call.
  
  
  Modify Data Structures: If using basXML is not feasible, consider modifying your data structures to avoid using boxed components. Instead, use simpler data types or structures that are compatible with the current protocol.
  
  
  Check RFC Destination Settings: Verify the settings of your RFC destination in transaction SM59. Ensure that the destination is set up to support the basXML protocol if you intend to use boxed components.
  
  
  Review Documentation: Consult the SAP documentation for RFC and basXML to understand the limitations and requirements for using boxed components. This can provide insights into best practices and alternative approaches.
  
  
  Testing: After making changes, test the RFC calls to ensure that the error is resolved and that the data is being transmitted correctly.
  
  
  Related Information:
  
  RFC (Remote Function Call): A protocol used in SAP systems to enable communication between different SAP systems or between SAP and non-SAP systems.
  basXML Protocol: A protocol that allows for the serialization of complex data types in XML format, making it suitable for web services and other integrations.
  Boxed Components: These are complex data types in SAP that can encapsulate multiple fields or structures, often used in function modules and methods.
  
  If the issue persists after trying the above solutions, consider reaching out to SAP support or consulting with a technical expert who specializes in SAP integrations.