the Node Reference doesn‘t work in DMEE Format

[#1]

dear experts,

we created a DMEE file /Z_MO_HSBC via 100558: Map Format Data. 

for the business, when total amount < 200000, it can be handle as Easy Transfer . so we created Technical Node SUM  with type aggregation .

and then, we want to use this value into condition for the Technical Node: FPSFlg , but this Node Reference doesn't work.

could you please kindly tell me how we can achieve this function.

Best Regards，

Li

[HenrikeGroetecke]

Hello,

Thank you very much for your question.

Here is the question our internal chatbot provides. Please check whether it helps you resolve the issue.

Kind regards,
Henrike

#AI-Generated Content

DMEE: Why Node Reference to Aggregation Node Fails — and How to Solve It

Root Cause: DMEE Processing Sequence

This is a fundamental processing-order constraint in DMEE. The engine processes the format tree top-down and left-to-right in a single pass. The critical issue is:

• Your SUM (Aggregation) technical node accumulates values incrementally as it iterates over payment items (line by line).
• At the moment DMEE evaluates the condition on FPSFlg, the loop has not yet completed — the SUM node's final accumulated value is therefore not yet available (it is still zero or incomplete at that point in the processing pass).
• A Node Reference in a condition resolves the current value of the referenced node at the instant the condition is checked — for an aggregation node still mid-loop, that value is meaningless.

This is why the Node Reference to SUM appears to do nothing or always returns 0.

---

The Three Valid Solutions

Solution 1 — Reference the Source Field Directly (Recommended)

This is the cleanest approach. The SAP payment program (F110 / SAPF110V) already computes the total payment amount at run time. It is available in the payment medium data structure before DMEE starts its tree traversal.

Scenario Field to Reference

Classic payment program	REGUH-ZBTR (total house-bank amount)
Payment Medium Workbench	The corresponding amount field at the payment header level in your data selection

Steps in the FPSFlg condition:

1. Open the node FPSFlg → go to the Condition tab.
2. Set the Left-Hand Side type to Source Field (not "Node Reference").
3. Enter the data structure/field (e.g., REGUH-ZBTR).
4. Set the operator to < and the Right-Hand Side constant to 200000.

This bypasses the aggregation node entirely, because the source data already has the answer.

---

Solution 2 — Restructure the Tree Using a Pre-Aggregation Level

If you genuinely need to aggregate in DMEE (e.g., summing across multiple line items into a group total), the aggregation node must complete its loop before the node consuming its result is evaluated. This requires restructuring:

[Header Loop / Company Code Level]
   └── [SUM]  ← Aggregation node lives HERE, at the PARENT level
               ← It completes before children of this level are processed
   └── [FPSFlg]  ← Now evaluated AFTER SUM is finalized for this header
       └── [Condition: Node Reference → SUM < 200000]

The rule is: the referenced aggregation node must be a preceding sibling (or at a parent level) that closes its loop before FPSFlg is reached. If SUM and FPSFlg are inside the same repeating loop, the reference will always see an incomplete value.

---

Solution 3 — Use a Formula with ABAP User Exit (DMEEX)

In the Extended DMEE (DMEEX), node conditions support Formulas that can call custom function modules. You can write a short function module that:

1. Reads the payment total from REGUH for the current payment run.
2. Returns a flag ('X' or ' ') based on the threshold.

Then in FPSFlg's Value tab or Condition tab, reference the formula result. This gives full flexibility but requires an ABAP enhancement.

Note for S/4HANA Cloud Public Edition: In-app extensibility is restricted. You can use Key User Extensibility tools, but classical ABAP user exits in DMEE are typically not available in the Public Cloud edition. Solution 1 (direct source field reference) is therefore the most practical path for your environment.

---

Summary

Approach Works in S/4HANA Cloud PE? Complexity

Source Field Reference (REGUH-ZBTR)	Yes	Low
Tree restructure (aggregation at parent level)	Yes	Medium
ABAP User Exit / Formula	Not in Public Edition	High

The reason your Node Reference to SUM does not work is not a configuration mistake — it is a documented behavioral constraint: aggregation values are only finalized after their iteration completes, but node reference conditions are evaluated during (not after) the same iteration. Pointing directly to the source data field is both simpler and more reliable.

---

Useful SAP Help Portal references:

• Reference Conditions (DMEE)
• Extended Data Medium Exchange Engine (DMEEX)

Generated by AI