MEC Map Reverse Engineer

[Audio] Welcome to this presentation about the MEC Map Reverse Engineer tool. This tool was created to support a client migration from an older MEC environment to a new Multi-Tenant environment. The main challenge was that many of the existing maps did not have ANA-050 documentation or other technical specifications. Because of that, the client needed a practical way to understand what each map does before deciding whether each map should be migrated, redesigned, consolidated, or retired. The MEC Map Reverse Engineer tool helps address that gap by analyzing map files and generating AI-assisted technical documentation that stakeholders can review..

[Audio] This slide explains the client context and the migration challenge. The client is moving MEC integrations from a legacy environment into the Infor Multi-Tenant platform. However, several maps are missing supporting documents, including ANA-050 specifications and detailed technical designs. Without those documents, it becomes difficult to understand the business purpose of each map, the data each map uses, the APIs being called, and any technical risks that may affect migration. The key challenge is that migration assessment becomes slower and more dependent on manual reverse engineering. The tool was created to make this assessment more structured and easier to review..

[Audio] The MEC Map Reverse Engineer, or MRE, is an AI-assisted documentation tool. It automatically analyzes MEC or IEC map files and generates a structured Word report aligned with DES-020 technical design documentation. The tool reads the map XML, companion schema files, map functions, parameters, links, variables, Java logic, and other implementation details. It then turns that technical information into a more readable report that explains the purpose of the map, how the map executes, what APIs are used, how data flows, and what migration considerations may exist. The result is a practical documentation package that supports both technical review and business decision-making..

[Audio] This slide shows the high-level process. First, the agent identifies the map file in the workspace. Next, the tool parses the map content, including metadata, functions, parameters, links, and implementations. Then it reads the related schema files to understand input and output fields. After that, the tool generates a visual execution flow diagram using Mermaid. Finally, it creates a Word report with all the structured sections needed for analysis. The final deliverables normally include the map analysis document and a high-resolution flow diagram. Together, these outputs give stakeholders a clearer view of how the integration works..

[Audio] The generated documentation covers the major areas needed to understand an existing MEC map. It starts with a map overview and a purpose narrative, then provides a technical overview and execution flow. It also documents MI programs and methods, interface fields and attributes, constants, variables, and data flow links. For technical assessment, it includes error handling, Java logic summaries, performance considerations, and Multi-Tenant compliance checks. If SQL is detected, the tool adds a conditional SQL details section. This structure helps align the output with DES-020 technical design expectations while keeping the content useful for migration planning..

[Audio] This slide explains how the generated documentation supports migration decisions. Once each map has been analyzed, stakeholders can classify each map into one of four paths. A map can be migrated if the purpose is clear, the integration is still needed, and there are no major compliance concerns. A map can be redesigned if legacy patterns or technical risks are found. Similar integrations can be consolidated if the analysis shows overlap. Maps that are no longer needed can be retired instead of moved into the new environment. The report does not replace stakeholder judgment, but it gives stakeholders a structured starting point for making informed decisions..

[Audio] The tool includes several key capabilities that reduce manual reverse engineering effort. It automatically parses map files and extracts relevant technical details. It generates a DES-020 aligned report so that the content follows a clear documentation structure. It produces an execution flow diagram to help reviewers understand how the map processes data. It traces usage notes for API parameters so reviewers can see where data comes from and where data goes. It checks for Multi-Tenant compliance concerns and highlights risky patterns. It also documents SQL details when embedded SQL or stored procedures are detected. These capabilities make the review process more consistent and easier to repeat across multiple maps..

[Audio] A major value of the tool is its focus on Multi-Tenant readiness and migration risk. The tool checks Java logic for patterns that may not be suitable for the Multi-Tenant environment. When violations are found, the report identifies the affected function and provides a relevant snippet for review. If no violations are found, the report can show a pass result for the compliance check. This helps the team quickly identify which maps may be safer to migrate and which maps may need remediation or redesign. The compliance check also supports better technical planning because risks are surfaced earlier in the migration assessment process..

[Audio] The business value of the tool is centered on faster assessment, better visibility, more informed decisions, and reduced migration risk. Faster assessment comes from reducing the manual work required to understand existing maps. Better visibility comes from documenting the purpose, logic, APIs, fields, and execution flow in a readable format. More informed decisions come from giving stakeholders a practical basis for deciding whether to migrate, redesign, consolidate, or retire each map. Reduced migration risk comes from surfacing compliance concerns, SQL dependencies, and performance considerations before the actual migration work begins. Overall, the tool helps create a clearer and more structured assessment process for undocumented MEC maps..

[Audio] The recommended next step is to use the generated documentation as part of the migration review process. Start by running the analysis on candidate maps. Then review each generated report with the relevant business and technical stakeholders. After review, classify each map as migrate, redesign, consolidate, or retire. Any maps with Multi-Tenant compliance concerns or unsupported patterns should be prioritized for remediation planning. Finally, use the report as input for migration planning and technical design. The closing message is that the MEC Map Reverse Engineer helps convert undocumented MEC maps into actionable migration assessment material..