How To Fix DMEE_ABA393 - Error in checks for node &1: argument &2 is not allowed

DMEE_ABA393 - Overview

• Message type: E = Error

• Message class: DMEE_ABA - Messages for Data Medium Exchange Engine

• Message number: 393

• Message text: Error in checks for node &1: argument &2 is not allowed

What causes this issue?

As the argument for the check condition, you have entered the reference
ID of a technical node that is defined as an aggregation node with
mapping to a target field.
This is not allowed because in this case, at the time of the check, only
the current sum (of all previously processed nodes) is used and not the
absolute sum (of all nodes defined in the aggregation).
You can only use an aggregation node with the mapping procedure <zk>No
Mapping</> in a check condition.

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?

Create a second technical aggregation node that contains the same
aggregation entries as the first one, but specify <zk>No Mapping</> as
the mapping procedure. It is only used as an argument in a check
condition.

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_ABA393 - Error in checks for node &1: argument &2 is not allowed ?

  The SAP error message DMEE_ABA393 typically occurs in the context of the Data Medium Exchange Engine (DMEE) when generating payment files, particularly in the ABA (Australian Bankers' Association) format. This error indicates that there is an issue with the configuration of the DMEE tree, specifically related to the arguments being used in a node.
  
  Cause:
  The error message "Error in checks for node &1: argument &2 is not allowed" suggests that:
  
  There is a node in the DMEE tree that is configured incorrectly.
  An argument that is being passed to a node is not valid or not allowed in the context of that node.
  This could be due to a misconfiguration in the DMEE tree structure, such as using an incorrect field or parameter that does not meet the expected criteria.
  
  
  Solution:
  To resolve the DMEE_ABA393 error, you can follow these steps:
  
  
  Check the DMEE Tree Configuration:
  
  Go to the DMEE transaction (usually transaction code DMEE).
  Open the relevant DMEE