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

SAP Error Message - Details

• 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 tree that is being used for the payment file generation.
  Identify the node mentioned in the error message (replace &1 with the actual node name).
  Review the configuration of that node and ensure that all arguments and parameters are correctly set.
  
  
  
  Validate Arguments:
  
  Check the arguments being used in the node. Ensure that they are valid and allowed for that specific node.
  Refer to the DMEE documentation or help texts to understand the expected arguments for the node in question.
  
  
  
  Test the Configuration:
  
  After making any necessary changes, test the DMEE tree by generating a payment file to see if the error persists.
  If the error is resolved, ensure that the changes are saved and documented.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide additional guidance.
  
  
  
  Seek Help from SAP Support:
  
  If you are unable to resolve the issue, consider reaching out to SAP Support for assistance. Provide them with the error details and any relevant configuration information.
  
  
  
  Related Information:
  
  DMEE Documentation: Familiarize yourself with the DMEE documentation to understand how to configure trees and nodes properly.
  Transaction Codes: Common transaction codes related to DMEE include:
  
  DMEE: Data Medium Exchange Engine configuration.
  FBZP: Payment program configuration.
  
  
  Testing Payment Files: Use transaction codes like F110 to test payment runs and see how the DMEE tree is applied.
  
  By following these steps, you should be able to identify and correct the issue causing the DMEE_ABA393 error.