How To Fix DMEE_PAYMFORMAT360 - Node &1: aggregation with aggregation type 2 not possible for node &2

DMEE_PAYMFORMAT360 - Overview

• Message type: E = Error

• Message class: DMEE_PAYMFORMAT - Messages for DMEE Payment Formats

• Message number: 360

• Message text: Node &1: aggregation with aggregation type 2 not possible for node &2

What causes this issue?

For node &V1&, you have specified an aggregation using node &V2&.
However, node &V2& is of type &V3&. For such a node, aggregation with
<DS:DE.DMEE_AGG_TYPE>aggregation type</> 2 is not possible.

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?

If you would like to aggregate based on the number of occurrences of a
segment, instead use a reference to an element within the segment in the
definition of the aggregation.

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 DMEE_PAYMFORMAT360 - Node &1: aggregation with aggregation type 2 not possible for node &2 ?

  The SAP error message "DMEE_PAYMFORMAT360 Node &1: aggregation with aggregation type 2 not possible for node &2" typically occurs in the context of the DMEE (Data Medium Exchange Engine) configuration, particularly when dealing with payment formats. This error indicates that there is an issue with the aggregation settings for a specific node in the DMEE tree structure.
  
  Cause:
  
  
  Aggregation Type Misconfiguration: The error suggests that the aggregation type set for a node is not compatible with the data being processed. Aggregation type 2 usually refers to a specific way of aggregating data, and if the node does not have the necessary data structure or if the data is not suitable for this type of aggregation, the error will occur.
  
  
  Node 
  Configuration Issues: The nodes in the DMEE tree may not be properly configured to allow for the specified aggregation. This could be due to incorrect settings in the DMEE tree or missing attributes