One of the biggest modifications to DMEE has ever been made. A tool that opens and clarifies DMEE Engine processing has been implemented. This utility eliminates the requirement to debug the tool’s code in order to view and examine in detail how the DMEE tree was processed. This device is known as DMEE Trace Tool.
DMEE Trace Tool
The DMEE Trace Tool is available to assist you in analysing issues that frequently arise during the building or update of DMEE Trees. Do you not comprehend why the output file is missing the node or level? Why is the mapped value in a different format than what was anticipated? Or do you want to know how the conditions are dealt with internally? You can find the solutions with the aid of DMEE Trace Tool.
How it works in a nutshell
As you are aware, the user can only view inputs (structures) and outputs in DMEE, not the processing of the output file (files). With the DMEE Trace Tool, we started the generation process.
A user can designate a specific node or the entire tree as “to be traced.” An thorough log in XML format (Trace Log) is generated simultaneously with the output file for the chosen nodes or the entire tree. Trace Log will be recorded in the database once the file generation procedure is complete, but we didn’t stop there.
The “dmee trace aba” function we used to construct the separate transaction includes a graphical user interface for deciphering the XML Trace Log. Trace Log can be presented to the user in an interactive and natural way thanks to this method.
Enabling the DMEE Trace Tool
When you’re in display or change mode, go to the DMEE tree and right-click the node you want to investigate. The node you chose will have trace functionality enabled, along with all predecessors above it in the node hierarchy. This makes sure that, for instance, if a condition fails in one of the predecessors, the user will still obtain the complete context.
The user also has the option to trace the entire tree. In this situation, processing may take a little longer than it would without tracing and use up more system memory, especially for larger trees and/or input data.
In both cases described, “tracepoint” is valid for 5 days for the user who set it.
You can set the Trace Point for a single node (left) or for the whole tree (right).
Regardless of integration or tree type, a trace log is generated together with file generation as soon as the user enables the node or the tree with a tracepoint. Therefore, it makes no difference if the tree is run as a standalone process or as a component of Payment Medium Workbench, DMEE Test Tool, or another process.
The Initial Screen
All of the trace logs that are kept in the database are displayed on the initial screen. By selecting a specific Trace Log and clicking the glasses symbol in the application’s toolbar, users can view that Trace Log. Users have the option to delete their trace logs and import them from another system.
The table records itself contain general information about saved Trace Logs, such as Tree Type, Tree Name, the time the log was generated, who started the engine, and the Trace Log’s origin. Trace Logs can either be created directly on the present system (with the letter “S”) or uploaded externally (with the letter “E”).
The initial screen of the DMEE Trace Tool
The Detail View
Following the user’s selection of a certain Trace Log from the Initial Screen, the Detail View is shown to them. The detail view’s layout closely resembles that of the DMEE transaction. The recording of “what was done” inside the DMEE Engine is what it shows rather than the tree definition like DMEE does.
There is a tree on the left side of the screen that lists all the nodes that were marked with Tracepoint in the order that the engine processed them. The DMEE Trace Tool will also show any repetitions in the tree processing if there are any.
On the right side of the screen, the captured data are visible during the engine run. The right side differs based on the node type.
DMEE Trace Tool: Detail view
The Main Node
The visual of the main node.
Besides the general information like the Tree Type, Tree ID, and so on, the user can see how long it took to generate the file using DMEE in the “Statistics” section.
A table with skipped keys of the supplied data can be seen below the statistics section. The number of unique keys is equal to the number of repetitions of the level in the output file, as you are aware DMEE allows users to set key fields for a specific level. DMEE uses this information to build iterations across the levels.
Based on user feedback, we frequently notice that the output file is missing several iterations. Almost always, the issue is brought on by poorly defined fields, frequently as a result of the use of the length and offset.
The condition assessment tree can be displayed by the DMEE Trace Tool for conditions analysis. Each line begins with a green or red indicator that represents the outcome of the partial expression. Two expressions in the hierarchy below logical operators like AND and OR are always evaluated.
Each line continues with the kinds that are being compared, for instance, “Constant = Structure Field,” with the actual values of the fields coming last (“1 = 2,” for example).
Condition evaluation in the DMEE Trace Tool
Elements, technical nodes, XML attributes, and atoms are all mapping nodes, and each one has a mapping section. You can learn more about the internal processing of the value from this. Beginning with the source field’s value is everything. Finally, as you can see from the screenshot, the DMEE Trace Tool gives you access to all crucial conversion-related information, including length, target offset, and conversion function. It can additionally display the internal type used to handle the value.
The last field in this section is “Output value”, which is the input value after applying all conversions (length, t. offset, conversion function).
In DMEE Trace Tool, you can see how the value was transformed from the input value into the output value of the node
Aggregations are calculated on the node where the value is mapped from the input data (source node for aggregation), from the perspective of the engine, and then the value is referenced to the node where the user selected the aggregation to be outputted (target node for aggregation). You can find the method used to calculate the aggregation on each alleged source node for aggregation in the DMEE Trace Tool.
DMEE Trace Tool also highlights every source node for aggregation with yellow color.
Example of aggregations in DMEE Trace Tool
I want this!
If you want to benefit from the DMEE Trace Tool immediately, you can get it via SAP Note 3138271 – DMEE – Trace Tool.
Alternatively, DMEE Trace Tool is available for all supported releases of software component SAP_ABA from the following support packs:
- SAP_ABA 75G SP 02
- SAP_ABA 75F SP 04
- SAP_ABA 75E SP 06
- SAP_ABA 75D SP 09
- SAP_ABA 75C SP 11
- SAP_ABA 752 SP 11
- SAP_ABA 751 SP 15
- SAP_ABA 750 SP 25
- SAP_ABA 740 SP 28
- SAP_ABA 731 SP 31
- SAP_ABA 702 SP 25
- SAP_ABA 701 SP 25
- SAP_ABA 700 SP 40
The DMEE Trace Tool is here to assist you with the examination of the tree behaviour because DMEE configuration can be challenging. It can be utilised for the study of conditions, aggregations, mapping techniques, and the whole file generation process, as we taught previously (loops, missing data, etc.).